![]() I understand that sometimes anomalies can occur if all the hardware equipment has issues if the system clock times are misaligned. The times I see unexpected behavior is when the media cache also lies on the remote drives instead of locally. We are talking 50 x 1 hour plus episodes that have to be re-branded and re-exported. ![]() There is simply too much data for any of the local drives on the PC and none of them are protected. It also doesn't establish of that is the issue as a second pass at the show and it rendered out correctly. The shared drive is a 10GBe QNAP NAS which is primary work area - everything from there is backed up to another NAS. It's random not consistent so obviously a hard one to track down. This test is helpful in tracking down where the source of the issue is. Sure, I understand, however, I wanted to see if there's something wrong with the computer, media, or storage. I really need AME to work correctly with SMB shares. Bitrate: VBR, 1 pass, Target 16.00 Mbps, Max 16.00 Mbps Output File: Q:\Cosy project\watch folder\Output\000000 Master_YouTube 1080p HD.mp4 Source File: Q:\Cosy project\watch folder\000000 Master.MOV Reading from file: Q:\Cosy project\watch folder\Beginner Guide to Quilting Master.movĬomponent: ImporterQuickTime of type ImporterĪnd here is a successful encode in the same session Writing to file: \\?\Q:\Cosy project\watch folder\Output\XXXXXXX_YouTube 1080p HD.mp4 I suspect an SMB error and I note the ? in the path name - its a mapped network drive and that path name should be the name of the server - I have blanked out the output name: To put this in perspective Avid exported the full 3 hour DNxHD quicktime to the same drive - a much larger file, with no issue. I have check things like quotas etc to make sure that is not the issue. These encodes can be over 2 hours long and the one failed over the weekend was about 3 hours program length. ![]() It is not a permissions error as some files will successfully encode (even in the same session) - we are using a watch folder and I've now seen this same error three times on a drive with over 5TBs of space. I have experienced the same or similar problem. We could just stay out of the media drive while videos are encoding, but we're transferring/encoding multiple video files to this drive throughout the day. We did some experimenting with exporting, and noticed that it usually fails whenever we go to the location of the video export (the SMB Network Drive) but when we export to other locations (The desktop or another server) it exports without any problems. The drive we're exporting to is on an SMB Network and has about 3.2TB of free space. Whenever we export or convert footage to this format, we receive the following error: We're trying to encode video files into an H.264 Formatġ920x1080 Square Pixels 23.973 fps, progressive
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |