Hi Leila, I used an Apple Silicon Macbook using FFmpeg 7.1.1 from homebrew just there to process a v210 with similar specs using your command and couldn't replicate the issue. I'd be curious to know if you got the error with any other format, for example with a a basic h264 command like:
ffmpeg -i /Volumes/Preservationworking/Work/Preservation\ \(FFV1\,\ mkv\)\ \(96kHz\,\ 24-bit\)/UA-F003035_pres.mov -c:v libx264 -crf 21 -pix_fmt yuv420p /Volumes/Preservationworking/Work/Preservation\ \(FFV1\,\ mkv\)\ \(96kHz\,\ 24-bit\)/UA-F003035_pres.mp4 Your decoding looks like it didn't trigger any errors and it got past frame 41, unlike your FFV1/MKV command. When running the command on the other mac where you get a successful outcome, is this connected to the same storage device? I don't see any of the usual errors that I would expect to see if there was corruption in the source file or there was some sort of error on an FFv1/MKV level. Is there any chance that this could be to do with the connection to the connected Volume on that Mac? Are you able to run this command on local or external storage on the same mac with the same input file to see if it gets past frame 41 at the very least (i imagine you may not have the disk space to process the whole file, but your output died in the first two seconds. Best, Kierane _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
