Mac was famous for first professional (avid/1) and consumer (Adobe
Premiere) NLEs, Amiga was famous for specialized video editing hardware
(Video Toaster) or whole new clone (Draco), but apparently even Atari (also
m68k based computer) had some promising program in late 90x?
> try to encode 8 and/or 12 bit h265 with normal and multibit build??
Test done several times before. Each result is the same for multibit
and unpatched build.
(I think it's better that way too, with everything always working. As
long as the same happens to others)
--
Cin mailing list
ah, apparently only command line x265 encoder prints this line as I
remember it:
x265 [error]: No input file. Run x265 --help for a list of options.
$ thirdparty/x265_3.5/8bit/x265 --version
x265 [info]: HEVC encoder version 3.5+1-f0c1022b6
x265 [info]: build info [Linux][clang 12.0.0][32
still a bit strange, shouldn't encoder string from mediainfo indicate
8+10+12 bit instead of just 10?
'x265 3.5+1-f0c1022b6:[Linux][GCC 10.2.1][64 bit] 10bit'
try to encode 8 and/or 12 bit h265 with normal and multibit build??
full mediainfo:
$ mediainfo
If you have built in that directory before, do a "make clean" before
building. The build process might not detect all changes.
MatN
On Tue, 2 Nov 2021 18:53:13 +0300
Andrew Randrianasulu via Cin wrote:
> hm, yes, no libx265 in sight... so, hopefully your cin build uses
> statically-linked
hm, yes, no libx265 in sight... so, hopefully your cin build uses
statically-linked ffmpeg/x265... but then I have no idea why it works for
you even without patches... anyway, working is better than non-working!
I also have no idea why appimage (32 bit) fail for you.. may be deleting
(!) some
On Tuesday, November 2, 2021, Andrea paz
wrote:
> I wouldn't know where to use ldd; could you give me the exact command?
ldd path_to_cin?
and see if it links with external libx265..
But I mostly hoped Phyllis will look into this.
> I tried the following paths:
>
> $ cd
I wouldn't know where to use ldd; could you give me the exact command?
I tried the following paths:
$ cd /home/paz/cinelerra5/cinelerra-5.1/thirdparty/x265_3.5
$ ldd x265
linux-vdso.so.1 (0x7ffc797f4000)
libpthread.so.0 => /usr/lib/libpthread.so.0 (0x7f6f51401000)
On Tuesday, November 2, 2021, Andrea paz via Cin
wrote:
> > CinX
>
> Recently Andrew has worked on many patches to extend the encoding of
> CinGG; for example the "compile_multibit_X265.txt" patch. I guess
> compiling CinGG with this patch is equivalent to using
> CinGG-multibit.AppImage. I
> CinX
Recently Andrew has worked on many patches to extend the encoding of
CinGG; for example the "compile_multibit_X265.txt" patch. I guess
compiling CinGG with this patch is equivalent to using
CinGG-multibit.AppImage. I produced "test-multibit1.mp4" with the
multibit appimage and I produced
Den 02.11.2021 11:53, skrev Andrea paz via Cin:
All perfect installation and appimage. Thank you.
Two questions:
1- I also tried to build OpenCV along with the source and had no
errors. But the plugins don't appear in the plugins list. Instead
putting manually the plugins in ".../bin/plugins"
All perfect installation and appimage. Thank you.
Two questions:
1- I also tried to build OpenCV along with the source and had no
errors. But the plugins don't appear in the plugins list. Instead
putting manually the plugins in ".../bin/plugins" everything works
normally. (PS: OpenCV has been
Il giorno dom 31 ott 2021 alle ore 21:39 Phyllis Smith via Cin
ha scritto:
>
> The October 31, 2021 CinGG releases are at:
>
> https://cinelerra-gg.org/download/images/CinGG-20211031-x86_64.AppImage
> https://cinelerra-gg.org/download/images/CinGG-20211031-x86_64-older_distros.AppImage
>
13 matches
Mail list logo
