View Bug Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001057 | DCP-o-matic | Bugs | public | 2017-03-07 16:06 | 2023-12-22 22:33 |
Reporter | carl | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | acknowledged | Resolution | open | ||
Summary | 0001057: Inaccurate progress reporting | ||||
Description | I have this project which required using existing DCP but I had to add burned-in subtitles. The original unencrypted IOP DCP was 410 GB in size and was divided into 14 reels. It run for 4 hours and 15 minutes. Once this was accomplished I created another DCP project and imported those 14 new DCP’s , and this time set an option of burning-in subtitles on each reel. When I hit create DCP, DOM calculated the needed encoding time as about 800 hours. However I have noticed that the progress indicator moved much faster than the estimated time would suggest from the beginning, as it transcoded about 11 percent of the project in about 15 minutes. This morning I checked the situation. The project was finished and the final run time was 7 hours 21 minutes and 11 seconds. I am just letting you know this, as one probably could not expect DOM to be a 100 % precise in those estimations. | ||||
Tags | No tags attached. | ||||
Branch | |||||
Estimated weeks required | |||||
Estimated work required | Average | ||||
|
I met this before and I guess it happens so because remaining time is calculated from current decoding speed (fps) and total count of frames, though actually decoding does not happening, only copying existing files. If you spotted, decoding speed during making VF DCP is below 1fps, that is why remaining time was so huge. |