[ SOLVED ] No subtitle filters with Avidemux 2.7.4 (Linux).

Started by Gandalf, January 06, 2021, 07:04:12 AM

Previous topic - Next topic

Gandalf

I am trying to add subtitles (file extension .srt) to a video, but when I click on the "Subtitles" category in the "Filters" section the "Available filters" column is empty. How do I remedy that situation?

eumagga0x2a

2.7.4 is a legacy, unsupported version. If your distribution has glibc in version 2.28 or later, please try the latest appImage from https://avidemux.org/nightly/appImage4Buster/ or build from source (git master) yourself.

Gandalf


eumagga0x2a

The .app files in https://avidemux.org/nightly/appImage4Buster/ are named

avidemuxLinux_GLIBC_a.bc_amd64_YYMMDD_NNNN.app

where the sequence a.bc is the minimum glibc version required (2.28 as on Debian Buster), YY are the last two digits of the year, MM is the month of the year with leading zero and DD is the day of month with leading zero. NNNN represent the build number.

As I checked, the latest nightly build was 210104.

The latest and meanwhile very outdated release is 2.7.6, current nightlies report themselves 2.7.7 in anticipation of the next release, due in near future.

Gandalf

Quote from: eumagga0x2a on January 06, 2021, 07:58:06 AM2.7.4 is a legacy, unsupported version. If your distribution has glibc in version 2.28 or later, please try the latest appImage from https://avidemux.org/nightly/appImage4Buster/ or build from source (git master) yourself.
I just installed version 2.7.6 today, and I forgot to mention before that my operating system is Slackware Linus 14.2 (64-bit). So how do I get the subtitle filters to show up (the version of glibc on my system is 2.23).

eumagga0x2a

Quote from: Gandalf on January 14, 2021, 10:47:50 PMthe version of glibc on my system is 2.23

Old-style appImages from https://avidemux.org/nightly/appImage4 are the only option besides compiling from source then.

Gandalf

I tried that, and it can't initialize the audio device (and I tried them all).

eumagga0x2a

Could you please launch the appImage in terminal, redirect stdout and stderr to file and post that file?

The only audio device which really should work is PulseAudio (PulseAudioSimple). If it fails with the old-style appImage, does it fail when you build yourself from git master too?

Gandalf

Quote from: Gandalf on January 06, 2021, 06:42:39 PMWhat it the latest version of Avidemux?
Never mind, I found out what the latest version is and have since downloaded and installed it - but I sill don't see any subtitle filters for it. Is there any way to correct that (I use Slackware 14.2 (64-bit) as my operating system)?

Gandalf

#9
Quote from: eumagga0x2a on January 15, 2021, 04:37:01 AMCould you please launch the appImage in terminal, redirect stdout and stderr to file and post that file?

The only audio device which really should work is PulseAudio (PulseAudioSimple). If it fails with the old-style appImage, does it fail when you build yourself from git master too?
When I use the appImage I see the subtitle settings (which seems to work okay), but I don't hear sound from it - and the only choices for audio device are "Dummy" and "OSS". However, when I use the compiled version, I get sound (with the corect choices for the "audio device' settings - but NO subtitle filter(s). Unfortunately I'm not certain how to do a redirect of stdout or stderr with Linux (which is my operating system).

eumagga0x2a

Please run

bash bootStrap.bash --with-system-libass > ~/admCmakeLog.txt 2>&1
in Avidemux top source directory (avidemux2 wherever you have cloned the repository), search-replace your user name and the path in the generated admCmakeLog.txt file with a placeholder if you wish, then ZIP-compress it and attach to your reply.

Avidemux looks for system libass using pkg-config, it also needs fontconfig, freetype and fribidi headers to enable the feature. If Slackware does something no other distribution is doing and pkg-config is not usable there, you are out of luck.

Gandalf

Here is the file that you requestedYou cannot view this attachment.

eumagga0x2a

Avidemux bootstrap script expects /tmp to be writable. You need either to edit the script to point it to a different location for build logs or to ensure that this expectation is met.

Apart from that, I don't recommend building 2.7.6. There are no known noteworthy new issues with the current git master while dozens of major bugs, present in 2.7.6, have been resolved in the meantime.

Gandalf

I always build Slackware packages as "root" (if that information is of any help). And since you don't recommend building 2.7.6, what DO you recommend?

eumagga0x2a

Quote from: Gandalf on January 17, 2021, 12:31:04 AMI always build Slackware packages as "root"

This is a terrible, very dangerous practice. You really shouldn't.

Quote from: Gandalf on January 17, 2021, 12:31:04 AMAnd since you don't recommend building 2.7.6, what DO you recommend?

As mentioned already on three occasions in this topic, I recommend building Avidemux from the git master:

git clone https://github.com/mean00/avidemux2.git && cd avidemux2 && git submodule update --init --recursive && bash bootStrap.bash --with-system-libass > ~/admCmakeLog.txt 2>&1