The following warnings occurred: | |||||||||||||||
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.3.12-nmm1 (Linux)
|
[BUG] Hybrid 2022.11.28.1, y4m bad sequence header issue - Printable Version +- Selur's Little Message Board (https://forum.selur.net) +-- Forum: Hybrid - Support (https://forum.selur.net/forum-1.html) +--- Forum: Problems & Questions (https://forum.selur.net/forum-3.html) +--- Thread: [BUG] Hybrid 2022.11.28.1, y4m bad sequence header issue (/thread-2977.html) Pages:
1
2
|
Hybrid 2022.11.28.1, y4m bad sequence header issue - Nickme - 09.12.2022 Hi Selur, I am using Hybrid 2022.11.28.1 on windows 11 ARM (through parallels desktop on MacBook m1). Earlier version was working good. But after updating to this version, settings the error, x264 output: y4m [error]: bad sequence header magic x264 [error]: could not open input file `-' Debug zip file is attached. I am simply putting input file. defining output file name. selected deinterlacing QTGMC with bob option checked. x264 output. Here is video file: https://drive.google.com/file/d/18L6aI8B7CpSInwG6LU7C6jNx94bt3VGk/view?usp=share_link Please, read the 'Infos needed to fix&reproduce bugs,..'-sticky before you post about a problem. RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Selur - 09.12.2022 Will look at it after work and report back. Quote: y4m [error]: bad sequence header magicusually indicates an issue with the Vapoursynth script -> does the Vapoursynth preview work properly ? At a first glance, the used script: # Imports "C:\Program Files (x86)\Hybrid\64bit\Vapoursynth\vspipe.exe" "C:\Users\kiaara\Downloads\encodingTempSynthSkript_2022-12-09@06_17_43_1510.vpy" - -c y4m | "C:\Program Files (x86)\Hybrid\64bit\x264.exe" --preset veryfast --pass 1 --bitrate 1500 --profile high --level 4.1 --direct auto --b-adapt 0 --sync-lookahead 6 --qcomp 0.50 --rc-lookahead 40 --qpmax 51 --aq-mode 0 --sar 64:45 --non-deterministic --range tv --stats "C:\Users\kiaara\Downloads\1_2022-12-09@06_17_43_1510_02.stats" --demuxer y4m --input-range tv --fps 25/1 --output-depth 8 --output NUL - Cu Selur Ps.: One only thing that seems strange is that Hybrid is installed under 'C:/Program Files (x86)' as a 64bit application it normally should be installed under 'C:/Program Files'. (Reencoding the file, works fine here) RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Nickme - 09.12.2022 1. Vaporsynth preview gives error, attaching .vpy file showed when I clicked preview. Quote:2022-12-09 12:50:11.817 2. Hybrid took C:/Program Files (x86) location installation by default. I didn't change anything while installing. Edit 1: I just uninstalled it completely. Installed again, this time in C:/Program Files/ folder. Still getting same error. RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Selur - 09.12.2022 Okay, issue seems to be with fft3dfilter.dll or libfftw3f-3.dll which fft3dfilter.dll uses. :/ I could probably modify Hybrid to use Neo-FFT3DFilter, but that also relies on libfftw3f-3.dll. So to know whether fft3dfilter or libfftw3f-3 is the problem, a. use a progressive source b. enable Filtering->Vapoursynth->Denoise->FFT3DFilter and check the Vapoursynth preview. This should also crash, since it uses fft3dfilter.dll. Then enable Filtering->Vapoursynth->Denoise->FFT3DFilter->Neo in which case instead of FFT3DFilter, Neo-FFT3DFilter will be used. So try the Vapoursynth Preview again, if it works then let me know and I'll adjust Hybrid and QTGMC so that it can use Neo-FFT3DFilter instead of FFT3DFilter. If that fails to, your best option is to try to replace the libfftw3f-3.dll with the latest version from http://www.fftw.org/install/windows.html, that might help. Cu Selur RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Selur - 09.12.2022 Send you a link to a dev version (via pm) which has an additional 'Neo'-option for QTGMC which tells Hybrid/QTGMC to use Neo-FFT3DFilter instead of the normal FFT3DFilter. Cu Selur RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Nickme - 10.12.2022 (09.12.2022, 16:10)Selur Wrote: Send you a link to a dev version (via pm) which has an additional 'Neo'-option for QTGMC which tells Hybrid/QTGMC to use Neo-FFT3DFilter instead of the normal FFT3DFilter. Thanks for the new build, Selur. Both issues still exist in your new build also. I uninstalled older one completely. Installed your new build from PM. log file is attached here. RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Selur - 10.12.2022 In the debug output you did not try the 'neo'-option, so fft3dfilter.dll was still used and nothing was gained from using the new verison. Please try, whether it works with the 'neo'-option enabled. Cu Selur RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Nickme - 10.12.2022 (10.12.2022, 07:29)Selur Wrote: In the debug output you did not try the 'neo'-option, so fft3dfilter.dll was still used and nothing was gained from using the new verison. Thanks Selur. I forgot to check Neo box earlier. Both the issues got resolved now Another thing is, I am encoding x264 mp4 file with mp3 audio. but getting this issue. My final video mp4 file is without audio. Am I doing something wrong here. I tried changing temp folder also but getting same issue so reverted to default. debug file is attached. Attaching screenshots of settings. added new job with id 2022-12-10@11_40_31_1910 RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Selur - 10.12.2022 Quote:debug file is attached. Attaching screenshots of settings.Nope, debug output isn't attached. Without a debug output I have no clue what is happening. Quote:I forgot to check Neo box earlier. Both the issues got resolved nowOkay, so it is an incompatibility with fft3dfilter and your system. Happy that using neo-fft3dfilter helps. Cu Selur RE: Hybrid 2022.11.28.1, y4m bad sequence header issue - Nickme - 10.12.2022 (10.12.2022, 08:33)Selur Wrote:Quote:debug file is attached. Attaching screenshots of settings.Nope, debug output isn't attached. Without a debug output I have no clue what is happening. Sorry. here it is. |