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.

Missing audio on ProRes 32 bit float, and 24 bit pcm
#11
Here is the info you requested:

1-  The problem seems to be related more to the length of the ProRes file rather than the audio format.

2-  I have added the resulting HybridDebugOutput.tar file requested

3-  Load the file into Hybrid
4-  Under the Base Tab, select Processing Video to ProRes  
5-  Under the Base Tab, select audio Passthrough All
6-  Next to the Generate check box put in a filename and path for the output file
7-  Under the PreRes tab, select  PreRes 422 HQ
6-  Check the Filtering Tab that Vaporsynth is selected
8-  Check the Filtering Tab that auto deinterlace handling  QTGMC (Vaporsynth) is selected.
9-  Check the Filtering Tab that Neo is selected
10-  Under the Chapter Tab, deselect Auto adjust chapter names, and Import chapters on an input change
11-  Under the Base Tab, add a job to the queue and start processing  (lower right corner icon)

4-  Attempt to playback output file using VLC.


NOTE:  The Part 1 and Part 2 files I put in my dropbox are examples of shorter files that did product audio and the source file.  Also an output of the long file that has no audio.

Thanks,

-david BTW


Attached Files
.tar   HybridDebugOutput.tar (Size: 16,78 MB / Downloads: 6)
Reply
#12
Processing of the muxing call:
"C:\Program Files\Hybrid\64bit\ffmpeg.exe" -y  -r 30000/1001 -i "C:\Users\dave\AppData\Local\Temp\Crazy For You Initial Capture Sync To Make Debug File deinterlace_1_2025-11-11@21_59_53_4610_03.mov" -i "C:\Users\dave\AppData\Local\Temp\iId_1_aid_0_2025-11-11@21_59_53_4610_01.wav" -metadata encoding_tool="Hybrid 2025.07.27.1" -c:v copy -c:1 copy -map 0:0  -map 1:0  -aspect 1.3468013470 -r 30000/1001 -f mov "E:\Crazy For You New Capture\Crazy for You New Initial Capture\Capture\Crazy For You Initial Capture Sync To Make Debug File deinterlace.mov"
Aborts with:
[vost#0:0/copy @ 000001e7f18d1d00] Error submitting a packet to the muxer: No space left on device
    Last message repeated 1 times
[out#0/mov @ 000001e7f2580b40] Error muxing a packet
[out#0/mov @ 000001e7f2580b40] Task finished with error code: -28 (No space left on device)

received after crash/abort (ffmpeg): [out#0/mov @ 000001e7f2580b40] Terminating thread with return code -28 (No space left on device)
[out#0/mov @ 000001e7f2580b40] Error writing trailer: No space left on device
[out#0/mov @ 000001e7f2580b40] Error closing file: No space left on device
=> you might want to:
a. clear your temp folder
b. change the location of the temp folder
c. make sure you have enough space on your drive

Cu Selur

Ps.: I gave up downloading the file damn dropbox download aborts after 45min and doesn't resume,... (tried it multiple times)
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#13
So sorry on Dropbox.  

Still the out of space error is interesting.  I will work on clearing sufficient space on the files and let you know what I learn.  My previous work showed plenty of space, but you may have discovered the problem from the debug files.  And it would correlate to the size of the files and length.

I will report back

-david BTW
Reply
#14
I moved the files and directory over to a standard hard disc and now the files complete with 2 TB of free space.  I was using a 2 TB SSD drive with other stuff on it, and event though it was not full, there must have been some temp files or other that definitely got too full.  I don't know how much free space is needed at this point. There was 1/2 a TB left but that wasn't enough.

I was using the SSD to capture the original analog inputs because the computer wasn't able to keep up with the real-time stream to a hard disc under all conditions.  Capturing to the SSD solved that problem for me.  I will just use it for capturing now and do the processing on large videos on the hard disc.

Thanks very much for your help.  I sent you a little donation for your great program and help.

-david BTW
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)