This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

[HELP] Upscale - crashed on muxing
#1
The job was almost complete, but crashed during muxing. The separate video and audio files are in the temp folder, but no final muxed file.


Attached Files
.zip   HybridDebugOutput.txt.zip (Size: 980,7 KB / Downloads: 18)
Reply
#2
Accroding to the debug output, the muxing 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"
aborts with:
S:\KENNY\JokeBox-TEMP\iId_5_aid_0_lang_en_2022-10-13@15_18_19_5410_01.wav: Permission denied
According to the log, the file was created (432.546 MB) and not deleted, so my guess is that some antivirus tool is overprotective, the file is open by some tool or if it lies on a network share there is some network or right problem.

Cu Selur
Reply
#3
The final file would have been around 80GB. I have no anti-virus software, and no networking. Very strange.
Reply
#4
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:
"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"
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
Reply
#5
Here's what I get:


Quote:PS S:\>
>> "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"
At line:2 char:44
+ "C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y  -r 30000/1001 -i "S:\K ...
+                                            ~~
Unexpected token '-y' in expression or statement.
At line:2 char:48
+ "C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y  -r 30000/1001 -i "S:\K ...
+                                                ~~
Unexpected token '-r' in expression or statement.
    + CategoryInfo          : ParserError: (Smile [], ParentContainsErrorRecordException
    + FullyQualifiedErrorId : UnexpectedToken

PS S:\>
Reply
#6
Looks like you didn't open a Windows Command Prompt, but a Power Shell.

Cu Selur
Reply
#7
The command prompt is running. Does this mean it is re-encoding the file?

It says permission denied for WAV file ending _01wav.
Reply
#8
Quote:Does this mean it is re-encoding the file?
The call should multiplex the file, not re-encode it.
Quote:It says permission denied for WAV file ending _01wav.
Okay, that is the same message Hybrid gets, so it's likely not caused by indexing since that should be finished.
Question is why isn't ffmpeg allowed to access the file. :/
Can you playback the file?
You check the file permissions of the file, is there something uncommon?

Cu Selur
Reply
#9
It's a capture I did on a Mac. I've upscaled dozens of these captures with no problem, so it's a mystery to me. I wouldn't mind, but the upscale took 16 hours to not complete  Confused
Reply
#10
You already got the files, so the only step left is the muxing (= combining of the files).

Quote:It's a capture I did on a Mac.
And you are accessing the files from Windows, how?
Networkshare?
VM share?
If the file is still accessible from MacOS some process there might be accessing/scanning the file and hindering Windows/ffmpeg to access it.

Cu Selur
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)