Matthew
Active Member
I had a runaway recording the other day on my T2 that reported its length too short (49mins) the film it was scheduled to record was 150mins long (SD) yet the recording was 4.5GB, the recording played back past the 49 mins OK but all sort of stuff would not work, like any skip went back to 49mins. I did not bother to check just how long the recording had run for.
The auto ad detect ran (and could not be stopped!) it took 1.5 hrs but all bookmarks found ended up around 49min mark so no good.
I wanted the recorded film so tried a number of steps, shrinking/decrypting did not help.
In the end I manually scanned the recording to the end of the film and set a bookmark, then did a crop, the cropped file reported the correct length, I then ran add detect again and cropped again. The final file is 1.3GB 115mins.
The original schedule was set from within the webif.
Is there a better/quicker way to fix a file with an erroneous reported length?
The auto ad detect ran (and could not be stopped!) it took 1.5 hrs but all bookmarks found ended up around 49min mark so no good.
I wanted the recorded film so tried a number of steps, shrinking/decrypting did not help.
In the end I manually scanned the recording to the end of the film and set a bookmark, then did a crop, the cropped file reported the correct length, I then ran add detect again and cropped again. The final file is 1.3GB 115mins.
The original schedule was set from within the webif.
Is there a better/quicker way to fix a file with an erroneous reported length?
