Selur's Little Message Board

Hello,

This is my first post on the forum, so please forgive me if I am not following the right process.

I have a collection of PAL 25fps S-VHS-C videos taken with a Panasonic NV-S7 Camcorder.  I played them from a Panasonic NV-HS930 via a Video-2-Mac adaptor and either QuickTime and OBS on a 2013 model Mac running MacOs Catalina Version 10.15.7.  Hybrid and QTGMC did a great job of de-interlacing them, but the quality was variable as I do not have a timebase corrector.  The audio input to Hybrid was AAC. 

I have asked a professional company to digitise my tapes, as they have a timebase corrector and other equipment superior to mine.  They have provided a sample video for me with PCM audio.  I have managed to make this work with Hybrid, but only if I output X.264 with AAC audio to an .mp4 file.  To make it work, I have to customise the audio handling by selecting a custom audio setting on the Base page and Audio Encoding Audio Format AAC on the Audio page.

When I try the same audio settings while outputting to a .mov file with either X.264 or ProRes, Hybrid fails to create an output file.  I think the failure may be occurring at the muxing stage.  If I change the audio setting to ignore, then Hybrid processes the input file with no problem.

Ideally, I would like to create a ProRes output file with passthrough to recreate the original PCM audio.  AAC would also be OK, but I can't make it work with ProRes.

I would be most grateful for any help you could provide on this please.

Thanks, Graham

Did I quick test here and I had no problem converting video to ProRes and audio to PCM and muxing it into a mov file.
I need a debug output to know what is happening.
Read the sticky [INFO] Infos needed to fix&reproduce bugs,.. and create a debug output that includes the analyisis of the source the job creation and the job processing.

If the muxing fails, the debug output should contain the used calls and probably some error message,...

Cu Selur

(14.01.2022, 23:27)Selur Wrote: [ -> ]Did I quick test here and I had no problem converting video to ProRes and audio to PCM and muxing it into a mov file.
I need a debug output to know what is happening.
Read the sticky [INFO] Infos needed to fix&reproduce bugs,.. and create a debug output that includes the analyisis of the source the job creation and the job processing.

If the muxing fails, the debug output should contain the used calls and probably some error message,...

Cu Selur

Thanks for your very prompt reply.  I had a look at the debug file, but I was unable to home in on the particular message that highlighted the problem - except that there was an error message near the end, which seemed to indicate a muxing problem.  I have WeTransferred the debug file and a trimmed 10 second clip to you, as I was unable to upload them on this forum.  

Would you mind giving them a quick check please?

Thanks,

Graham

It's a bug in Hybrid (which was fixed in the last release, you are using an older one).
the call using is:
Problem ist the definition of the DAR "-aspect 1.36574e+09:1000000000" this is wrong, happens here:
using "-aspect 1.36574" should work.

-> try latest public release (old jobs need to be recreated) at least here it properly uses "-aspect 1.36574".
(If you replace this in the above call, you could also call the call inside a terminal window and it should create the file.)

Cu Selur

Ps.: have to go to bed now.

(14.01.2022, 23:41)Selur Wrote: [ -> ]It's a bug in Hybrid (which was fixed in the last release, you are using an older one).
the call using is:

Code:

"/Applications/Hybrid.app/Contents/MacOS/ffmpeg" -y  -r 25/1 -i "/private/var/folders/8p/1hb1pnd90jndy5krc74xjdgc0000gn/T/Sample MVL Movie - Hybrid Output_2022-01-14@21_13_02_3410_07.mov" -i "/private/var/folders/8p/1hb1pnd90jndy5krc74xjdgc0000gn/T/iId_6_aid_0_lang_en_2022-01-14@21_13_02_3410_05.aac" -vcodec copy -acodec copy -metadata encoding_tool="Hybrid 2021.07.18.1" -map 0:0 -map 1:0  -aspect 1.36574e+09:1000000000 -r 25/1 -f mov "/Users/Study/Movies/Sample MVL Movie - Hybrid Output.mov"'

Problem ist the definition of the DAR "-aspect 1.36574e+09:1000000000" this is wrong, happens here:

Code:

2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9: parToDar,...
2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9:  width: 720
2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9:  height: 576
2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9:  par string: 59:54
2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9:  par double: 1.36574074
2022.01.14 - 21:13:02_macOS 10.15 (64bit)_2021.07.18.1 - level 9:  -> DAR: 1.36574e+09:1000000000

using "-aspect 1.36574" should work.

-> try latest public release (old jobs need to be recreated) at least here it properly uses  "-aspect 1.36574".
(If you replace this in the above call, you could also call the call inside a terminal window and it should create the file.)

Cu Selur

Ps.: have to go to bed now.

Hi Selur,

Thanks for your help.  I followed deleted Hybrid and QTGMC by following these instructions https://forum.selur.net/thread-1279.html 

I deleted all the Hybrid components, as per the instructions.  I ran the uninstall script that was in the VapourSynth folder on my desktop, which seemed to delete all of its components.  I did not delete D2V Witch, as I was not aware of its existence, until later.

I have downloaded the latest version of the software, Hybrid_2021.12.12.1.dmg, from https://www.selur.de/downloads 
I am running MacOs 10.15.7, rather than the version 10.16 quoted on the download site, so I hope that it still works OK on my version.

I installed VapourSynth, then Hybrid and rebooted my Mac.  I did not install XQuartz or vulkansdk, as it said that they were optional and I do not know what they do.

I reran the job and got the same result as before, so the latest version does not seem to have fixed the problem.

2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9: parToDar,...
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9:  width: 720
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9:  height: 576
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9:  par string: 59:54
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9:  dar double: 1.36574074
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9: -> No known fraction found for 1.36574,...
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9: decimalToFractionPrecise: 1.36574074
2022.01.16 - 21:38:45_macOS 10.15 (64bit)_2021.12.12.1 - level 9:  -> DAR: 1.36574e+09:1000000000

I'm afraid I don't know how to follow your advice that using "-aspect 1.36574" should work. I could not find anywhere in Hybrid to choose this parameter. Am I missing something?

Then, I ran the job again with the audio ignored and it ran perfectly as before.  

I have sent you debug files for the two runs that I did.  

Thanks again for your help.
Graham

Did you recreate the job or use the old one?
Will look at it after work.

(17.01.2022, 06:02)Selur Wrote: [ -> ]Did you recreate the job or use the old one?
Will look at it after work.

Hi Selur,

Every time I run Hybrid, I configure the job from the beginning.  I select the following:

Base: input file name, tick Generate box for output file name, default container (mov), processing video (ProRes) and audio (passthrough which fails and ignore which works), 
ProRes: profile ProRes 422 Proxy, or a higher quality
Filtering De-Interlace: QTGMC(VapourSynth), various speed settings tried, tick Bob box to generate 50 fps
Config: output path
Internals: create debug file

Otherwise, I take all the Hybrid defaults.

Thanks, Graham

Try to delete folder ~/Library/Application Support/Hybrid This will reset all legacy settings for real

@GrahamF: send you a link to a dev version for testing which hopefully fixes the issue.

Cu Selur

(17.01.2022, 18:32)Selur Wrote: [ -> ]@GrahamF: send you a link to a dev version for testing which hopefully fixes the issue.

Cu Selur

Thanks.  I tried clicking on the download link, but I got the message: "The requested URL was not found on this server."