h264 NAS

Hello @williams58505389,

Thanks for the message. It’s been a long time since you filed this bug. I apologize for the lack of a response. Are you still having this issue? If so, the team will need more info from you to reproduce the bug. Can you provide the information required here? How do I write a bug report?

 

I'll move your post to the Discussions board while we await your information.

 

Thanks,


Kevin

You should check, if any of your folders is accidentally write protected.

Could anyone test with Influx importer, suffixing the file with .influx ? This way we'll know if the issue comes from the NAS or from Adobe importer, it could help solve the problem and maybe find a workaround

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.

(EDIT: after a few days, H264 exports stopped working again, it was just temporary luck)

I don't know if this is pure luck but I got it working somehow.
In DSM, under File Services > SMB Advanced Settings, I changed the Minimum SMB protocol from SMB2 to SMB 1 (Max is set to SMB3) and checked the "Enable SMB2 Lease"

I then connected again to the NAS in SMB:// and now it is working. Not sure if this is a long term solution.

Riccardo maybe it's not about CBR vs. VBR but about 1 pass and 2 pass ? In general I would suggest testing others exporters, or moving to the NAS after export

Having the same problem, and our workaround (*so far* seems to be solid for us) is to spec VBR 2-pass in the export options under video>bitrate settings>bitrate encoding (instead of the default 1-pass VBR the H264 preset normally has).

Exporting with 2-pass spec'd to our network locations, again *so far*, seems to create non-corrupted files, and is a bit faster than the pro res to H264 option (we had been using).

Also worth noting apparently Adobe knows about the bug:
https://piunikaweb.com/2021/12/21/audio-video-glitch-when-exporting-h264-files-from-premiere-pro-to-nas-ack/

We're having the same issue. Have there been any solves?

Same issue: corrupted mp4 when export in h264 on a Nas via Ethernet. works fine when exporting with the same specs on my desktop. My colleague works with the same Nas, same cables, same version of the premiere but he exports correctly. the switch between VBR/CBR doesn't work for me: no fixes? thanks!

Why hasn't this been fixed yet!!
It's been close to a year and this bug is still there. The only work around is to export as CBR instead of VBR.