Open markfaine opened 5 years ago
Your right about ffmpeg -n
causing the error. But that last command you sent should work. Idk why ffmpeg is erroring out on it. Make sure your ffmpeg is up to date.
As for the documentation error, pull requests are welcome.
Just read about you compiling from source. Try a stable release.
@FallingSnow I tried a stable release and it looks like I'm still getting the same error:
ffmpeg version 4.2.1-static https://johnvansickle.com/ffmpeg/ Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 6.3.0 (Debian 6.3.0-18+deb9u1) 20170516
configuration: --enable-gpl --enable-version3 --enable-static --disable-debug --disable-ffplay --disable-indev=sndio --disable-outdev=sndio --cc=gcc-6 --enable-fontconfig --enable-frei0r --enable-gnutls --enable-gmp --enable-libgme --enable-gray --enable-libaom --enable-libfribidi --enable-libass --enable-libvmaf --enable-libfreetype --enable-libmp3lame --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-librubberband --enable-libsoxr --enable-libspeex --enable-libsrt --enable-libvorbis --enable-libopus --enable-libtheora --enable-libvidstab --enable-libvo-amrwbenc --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxml2 --enable-libdav1d --enable-libxvid --enable-libzvbi --enable-libzimg
[matroska @ 0x709b280] Invalid stream specifier: 0:1.
Last message repeated 1 times
Thanks
It could be specific to the videos I've been trying it on since I've found several like it that also give the same error but I just found another that does seem to be encoding.
I experience this as well on some files but not others.
@mjc Yes, it's the same for me. I had to try many different files to find some that work.
Looks like it happens more often with --he-audio
and/or loudnorm
as well but I don't understand the code well enough to quite know what is being done wrong yet. EDIT: nevermind I was not reading the log correctly
@markfaine can you try the patch here and see if it works for you at least some of the time? I need to also apply it to subtitle defaults but this should fix videos with no subtitles.
Sure. I will try it soon and report back. Thanks.
It's working so far. I've only just started the first video and it worked straight away. Just one video though, I'll try a few more and get back to you. I'm using commit 6fe44eb.
I was able to process over a hundred videos with only a few failures which are likely not related to this issue. I'd say it is definitely a success. Thanks
I was able to process over a hundred videos with only a few failures which are likely not related to this issue. I'd say it is definitely a success. Thanks
I found some more similar fixes and added them to the PR, can you try the newest commit there on the rest of them?
Sure, no problem.
ffmpeg compiled from source (yesterday) using the guide on the ffpmeg site
h265 installed using npm with -global option
When I run with the following command line:
h265ize --debug -g /media/mark/Backup/h265ize_tmp -d /media/mark/Backup/h265ize -f mkv -n en --10bit -q 30 "/volume1/video/television/The 100/Season 01/02 -The 100 - Earth Skills.mkv"
The result is:
If I run the generated ffmpeg command manually I see the error message:
This seems to be due to the
ffmpeg -n
at the beginning. I'm not sure why that is there and it looks like it should be a language value. If I remove it I get another error:Any help would be appreciated. Sorry for so much text but I just wanted to give you complete info.
Also, there seems to be a documentation issue in the readme. https://github.com/FallingSnow/h265ize#creating-10bit--12bit-encodes
There doesn't seem to be a --bitstream option now. It looks to have been replaced with --10bit or --12bit, etc.