Just to keep the conversation alive here: still the same exact issue using v23 (2023) of Premiere Pro and Media Encoder, no improvement.
Export to NAS (Synology in our case) and the last few seconds of the file are corrupted, picture freezes and the audio stops. Can confirm that the file size is smaller than it's supposed to be and that even though the metadata indicates a full file, the frames at the end of the stream are missing, causing a decoding error.
For example, processing a file just now that reports 2698 frames in the metadata, decoding through ffmpeg stalls out at frame 2511 in this particular render:
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] Packet corrupt (stream = 0, dts = 2513511).
[NULL @ 0x7f899e70aa40] Invalid NAL unit size (34318 > 7428).
[NULL @ 0x7f899e70aa40] missing picture in access unit with size 7432
renderbugtest.mp4: corrupt input packet in stream 0
[h264 @ 0x7f899e4d5ac0] Invalid NAL unit size (34318 > 7428).
[h264 @ 0x7f899e4d5ac0] Error splitting the input into NAL units.
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 0, offset 0xbac890a: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 0, offset 0xbae87d2: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 0, offset 0xbaf7c4e: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb05a22: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb05d6e: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb06058: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb063cc: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb06714: partial file
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb06df3: partial file
Error while decoding stream #0:0: Invalid data found when processing input
[mov,mp4,m4a,3gp,3g2,mj2 @ 0x7f899e709cc0] stream 1, offset 0xbb0711a: partial file
frame= 2511 fps=899 q=-0.0 Lsize=N/A time=00:00:41.89 bitrate=N/A speed= 15x
It seems like a pretty fair indication that the file is truncated.
Interestingly, the point at which it's truncated seems to vary from render to render of the exact same material. Normally we connect to our NAS over 10GbE with ping latency well below 1ms. We also saw truncation over WiFi with 2-3ms latency, although over the course of a couple of dozen tests, it seemed to get closer to the end of the file over WiFi: the files on average were less heavily truncated.
Hard to declare that as definitely significant without more testing, but sharing the observation anyway, since closing a file out without all the data written may have a faint smell of some kind of race condition.
43
Replies
AdChoices