Avidemux Forum

Hi,
If I open an .avs file, the color matrix is always BT.709, even if I set BT.601 at the script output; is there a way to make avidemux use the BT.601?
Thanks.

Bonjour,

Ma meilleure hypothèse est que le nombre d'images de référence par défault avec des préréglages "slow" (cinq refs), "slower" (huit refs), etc. dépasse la limite de votre matériel. En cas de doute, veuillez joindre le résultat d'analyse par MediaInfo d'une vidéo que votre TV est capable de lire et d'autre qu'il ne l'est pas à votre réponse.

Plus le préréglage est lent, plus la compression est importante. Il est probable que vos appareils ne prennent pas en charge la compression plus élevée de ces préréglages plus lents.

Bonjour.

Pourriez-vous m'indiquer pourquoi mes vidéos sont incompatibles sur mes TV et moniteur en fonction du -preset utilisé.

en effet, en x264
Utiliser la config avancée : non
Preset       : de Slow à placebo
Tuning       : animation
Profil       : high
Fast Décode  : non et oui
Zero latency : non
Fast 1 Pass  : non
Encoding mod : Average Bitrate (two pass)
Débit moyen  : 4'000 kb/s


J'ai testé tous les preset, seuls ceux de "ultrafast" à "médium" rendent une vidéo compatible avec les lecteurs intégrés à mes moniteurs et TV.

Bonjour,

Désolé, ce n'est pas possible.

Bonjour

Est il possible de couper automatiquement tous les silences d'une vidéo avec Avidemux ?
Et si oui, comment ? Auriez-vous un lien vers un tuto svp ?

Merci :-)

VA-API and other hw accels are available in the graphical app only.

I'll look into adding the developer package for libass to convenience scripts both for Debian-derivatives and for Fedora, thanks.

Quote from: eumagga0x2a on September 27, 2023, 03:09:48 PMActually, 2.8.1 is very old, quite a lot of issues have been fixed since then. You might want to build Avidemu from source (which is very easy on Linux) using the latest git master.

Thanks for the detailed explanation. I kept failing to build on Ubuntu 23.04, and then after installing libass-dev, the build succeeded!

And even in the latest version, there seems to be an issue with VAAPI not working properly only in the CLI, but it's possible that I'm missing something or it's something else, so I'll look into it a bit more, thanks.

Quote from: sark on September 28, 2023, 06:51:44 PMThere are currently ten 2.8.2 versions that are pre Sept 2023. Are these considered unbroken?

Yes, take the latest pre-Sept one or build from the current git master yourself. The issue is presumably with official packaging, not with code, albeit the dependency on libbrotlidec looks strange for me. I cannot rule out that MXE has changed something again. It is a fast moving target, difficult to chase.

Quote from: sark on September 28, 2023, 06:51:44 PMHow does this affect the zipped r230924 Qt5.8 version. I'm having no issues with this (Win 7 offline).

I cannot test on obsolete platforms like Windows 7, but on Windows 10 and 11, icu4c libraries, now needed by Qt, are not packaged by the official packaging scripts, making it impossible to run at least the graphical executable (the command line one might be fine).

Additionally, the NSIS installer fails to elevate with the shipped UAC.dll, making it impossible to use the installer the way it is intended to be used.

Quote from: eumagga0x2a on September 27, 2023, 08:46:45 PM

Quote from: tecc on September 27, 2023, 08:11:32 PMInstalling the 2.8.2 nightly results in this error message:

Was I unclear?

Quote from: eumagga0x2a on September 25, 2023, 04:49:11 PMOnly builds prior to Sept 2023, see https://avidemux.org/smif/index.php/topic,20301.0.html

There are currently ten 2.8.2 versions that are pre Sept 2023. Are these considered unbroken?
Also. How does this affect the zipped r230924 Qt5.8 version. I'm having no issues with this (Win 7 offline). Is there any reason to step back a build. Or is this just an executable issue, and only affecting installation.