I'm so sorry to say this, but this was genuine user error.  I did not run ```make install``` as it said to do, and when I did that the error messages went away and Cinelerra started up with hardware encoding enabled.

I'm so sorry to waste you and the other subscriber's time.

On Mon, Sep 9, 2024 at 6:48 PM Phyllis Smith <phylsmith2017@gmail.com> wrote:

The error messages in error_log are the blacklisted ffmpeg filters that do not work and which should NOT even load.

The file in cinelerra-5.1/ffmpeg/plugin.opts contains the non-working filters, preceded by a # sign (for example, aap or acrossfade, etc).  That file is copied to cinelerra-5.1/bin/ffmpeg/plugin.opts in the build.  If it is not there, then the build must have failed.

Can you check your build log for the word "Error" -- file is named "log" in the cinelerra-5.1 directory.  Not sure how you ran the build but for now, could you do the build again using the cinelerra-5.1/bld.sh file if that is not what you used? which records the building on a file in that same directory, called "log".

On Mon, Sep 9, 2024 at 4:20 PM Justin Wayland via Cin <cin@lists.cinelerra-gg.org> wrote:

I compiled Cinelerra-GG from source on openSUSE Tumbleweed and succeeded at building it, but when I tried to run it all I got was the opening window and the error log attached to this message. This happened regardless of whether I ran it in XWayland or X.  The AppImage provided on the website works.

The debug data was empty.

Any help would be appreciated.

-Justin

--
Cin mailing list
Cin@lists.cinelerra-gg.org
https://lists.cinelerra-gg.org/mailman/listinfo/cin