[Cin] Cinx - 10-bit h264 and/or h265
Terje J Hanssen
terje at nordland-teknikk.no
Mon Jan 7 11:10:34 CET 2019
Thanks for the replies, Phyllis and Adrew.
Either it is my installation or just me. Actually I thought of both the
Leap 15 system's and Cinelerra's bundled ffmpeg and libs.
But so far I have not been able to find or use the latter "ffmpeg4.1" or
"x264-snapshot-20180118-2245" as shown below. I have removed and
re-installed the latest Cinelerra and Cinelerra10-bit packages on Leap
15 according to the standard installation procedures, in case there was
something left from my previous Leap 42.3 to Leap 15 upgrade.
Here is the output from my installation:
# which cin cinx
/usr/bin/cin
/usr/bin/cinx
# find / -name ffmpeg
find: ‘/run/user/1000/gvfs’: Permission denied
/home/cin/ffmpeg
/usr/share/ffmpeg
/usr/share/cin/ffmpeg
/usr/share/cinx/ffmpeg
/usr/bin/ffmpeg
# find / -name ffmpeg4.1
find: ‘/run/user/1000/gvfs’: Permission denied
# /home/cin/ffmpeg/ffmpeg -h encoder=libx264
-bash: /home/cin/ffmpeg/ffmpeg: No such file or directory
# /usr/share/ffmpeg/ffmpeg -h encoder=libx264
-bash: /usr/share/ffmpeg/ffmpeg: No such file or directory
# /usr/share/cin/ffmpeg/ffmpeg -h encoder=libx264
-bash: /usr/share/cin/ffmpeg/ffmpeg: No such file or directory
# /usr/share/cinx/ffmpeg/ffmpeg -h encoder=libx264
-bash: /usr/share/cinx/ffmpeg/ffmpeg: No such file or directory
and regarding x264 and x265 respectively:
# find / -name x264-snapshot-20180118-2245
find: ‘/run/user/1000/gvfs’: Permission denied
# find / -name libx264*
find: ‘/run/user/1000/gvfs’: Permission denied
/usr/lib64/libx264.so.152
/usr/lib64/libx264.so.148
# find / -name x265*
find: ‘/run/user/1000/gvfs’: Permission denied
# find / -name libx265*
find: ‘/run/user/1000/gvfs’: Permission denied
/usr/lib64/libx265.so.130
/usr/lib64/libx265.so.165
/usr/lib64/libx265.so.146
/usr/lib64/libx265.so.151
/usr/lib64/libx265.so.116
I expect your output was from Fedora.
Do you have a chance to test and possibly confirm/clarify this on your
Leap 15 installation?
> I have locally corrected the manual to use 10-bit everywhere it makes
> sense, except for when the meaning is actually talking about 10 bits.
> I do not think I will be able to get gg to change the name
> Cinelerra10bit accordingly, but will try.
The package names are not a big deal. Yet, if so - maybe Cinelerrax264
and Cinelerrax265 would be better options, when the Cinelerra x264
version now should be able to handle both 8-bit and 10-bit color depth(?)
Thanks,
Terje
Den 07.01.2019 03:49, skrev Phyllis Smith:
> Terje: mystery solved. Andrew's response jostled my brain and here is
> the answer for Cinelerra usage.
>
> You ran the command using the operating system (Leap 15) ffmpeg package.
> If you run the command using cd to cinelerra path
> /thirdpackage/ffmpeg4.1 then ./ffmpeg -h encoder=libx264 see:
>
> Supported pixel formats: yuv420p yuvj420p yuv422p yuvj422p yuv444p
> yuvj444p nv12 nv16 nv21 yuv420p10le yuv422p10le yuv444p10le nv20l
>
> This is exactly why cinelerra likes to include the thirdparty packages
> with it so as to know what is actually being used as opposed to what
> the O/S has installed.
>
> For x265, I have:
>
> Supported pixel formats: yuv420p yuv422p yuv444p gbrp gray
>
> Might be different for CINX. gg/Phyllis
>
>
>
> Meldingsteksten vil bli nedlastet etter behov.
More information about the Cin
mailing list