14.10.2022, 16:16
The file size should not be an issue, especially since the file ffmpeg couldn't access was only 432MB and the error directly came while ffmpeg was collecting the input data.
One thing I normally do on any of my drives is to disable the Windows search indexing, maybe that is related to it.
Assuming the files are still there, what happens if you call:
inside a Windows command prompt? If my guess, that something different was accessing the file was right this should work.
Since input&output lie on the same drive, it might be a network issue if the drive is a network drive,..
Cu Selur
One thing I normally do on any of my drives is to disable the Windows search indexing, maybe that is related to it.
Assuming the files are still there, what happens if you call:
"C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y -r 30000/1001 -i "S:\KENNY\JokeBox-TEMP\JokeBox-Dec21-Sony-DMR_2022-10-13@15_18_19_5410_04.mov" -i "S:\KENNY\JokeBox-TEMP\iId_5_aid_0_lang_en_2022-10-13@15_18_19_5410_01.wav" -i "S:\KENNY\JokeBox-TEMP\iId_6_aid_1_lang_en_2022-10-13@15_18_19_5410_02.wav" -vcodec copy -acodec copy -metadata encoding_tool="Hybrid 2022.07.19.1" -map 0:0 -map 1:0 -map 2:0 -aspect 1920:1080 -r 30000/1001 -f mov "S:\KENNY\JokeBox-OUT\JokeBox-Dec21-Sony-DMR.mov"
Since input&output lie on the same drive, it might be a network issue if the drive is a network drive,..
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.