Internal engine and ffmpeg
I continue here what we started in MantiBT #646 since my problems are not with the issue. I tried making a build that uses system ffmpeg instead of CinGG's internal one. The behavior is the usual, even though the internal engine for exr is active, ffmpeg is used. The result is the same: clipped exr images except one. Maybe I am doing something wrong in the copy/paste I do during compilation? I report the exact steps (not from root): git clone --depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 cd /home/paz/cinelerra5/cinelerra-5.1 [patching here] ./autogen.sh ./configure --with-single-user --with-config-dir=/home/paz/.bcast6 --with-booby ### .bcast5 is for appimage make 2>&1 | tee /tmp/cin5.log && make install mv Makefile Makefile.cfg cp Makefile.devel Makefile (Curiosity: what are the last 2 steps for?) Do you guys have any improvements to propose to this set of steps? If these steps are correct then I can only think that it is Arch, although I don't see how...
вт, 21 нояб. 2023 г., 13:22 Andrea paz via Cin <[email protected]>:
I continue here what we started in MantiBT #646 since my problems are not with the issue. I tried making a build that uses system ffmpeg instead of CinGG's internal one. The behavior is the usual, even though the internal engine for exr is active, ffmpeg is used. The result is the same: clipped exr images except one. Maybe I am doing something wrong in the copy/paste I do during compilation? I report the exact steps (not from root):
git clone --depth 1 "git://git.cinelerra-gg.org/goodguy/cinelerra.git" cinelerra5 cd /home/paz/cinelerra5/cinelerra-5.1 [patching here] ./autogen.sh ./configure --with-single-user --with-config-dir=/home/paz/.bcast6 --with-booby ### .bcast5 is for appimage make 2>&1 | tee /tmp/cin5.log && make install mv Makefile Makefile.cfg cp Makefile.devel Makefile
(Curiosity: what are the last 2 steps for?)
I think last two lines replace Makefile with special debug version so NEXT rebuild will have more debug info. I think you can omit them if you are not intended to debug with gdb. I build without booby switch and without custom config dir. Are you sure all config files that created there are ok? If you copy Cinelerra_rc from .bcast5 dir - does it work better for this particular case? Do you guys have any improvements to propose to this set of steps?
If these steps are correct then I can only think that it is Arch, although I don't see how... -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
I build without booby switch and without custom config dir. Are you sure all config files that created there are ok? If you copy Cinelerra_rc from .bcast5 dir - does it work better for this particular case?
Good idea, but the result is still the same. The internal engine does not work and ffmpeg is used.
вт, 21 нояб. 2023 г., 16:18 Andrea paz <[email protected]>:
I build without booby switch and without custom config dir. Are you sure all config files that created there are ok? If you copy Cinelerra_rc from .bcast5 dir - does it work better for this particular case?
Good idea, but the result is still the same. The internal engine does not work and ffmpeg is used.
Does any other image format works on input? png, tiff, gif, tga .... ? Any wav audio?
Lately I have been having some problems with Arch updates, CinGG was not working well for me but I don't know if the problems were related. Now I did a new build of CinGG with the new patches and everything works fine. Even the images that were giving me clipping problems now show HDR values. Thank you. Now, quietly, I try to look at the code of the main Color Correction plugins. If I find strings that refer to clipping, I'll try to make corrections. If all goes well (or I don't find anything, too) we might consider doing an appimage with your patches so that others can also test the 32-bit floating operation.
participants (2)
-
Andrea paz -
Andrew Randrianasulu