Avidemux Forum

EDIT: This is not the current dev version thread.

This thread is exclusively for feedback/info (features/bugs) about the dev versions of Avidemux v2.7
https://github.com/mean00/avidemux2

Latest dev builds (x64) http://www.avidemux.org/nightly/
The win64 builds (cross-compiled with MinGW) are also provided as ZIP archives.
ffmpeg version

updated to FFmpeg v4.4:
- 210611 mouse wheel hover over thumb scroller now works. new: cut prev/next point display, ! toolbar buttons change.
- 210510

based on FFmpeg v4.2.4 (x264 core 155):
- 210426 new: Filters can be disabled. !!! in this version disabled filters are enabled with the project script save.
- 210326
- v2.7.8 Mar 06 2021 +fix for some hevc .ts files
- v2.7.7 Mar 04 2021
- 210215 linux/mac: doesn't have the new time display LCD font.

Known issues:
- [Win/video output: dxva2] GUI becomes unresponsive when video frame rate (ex:59.94fps) is close to monitor refresh rate (ex: 60Hz).

Release Changelog

In the Color Temperature Filter, the second parameter is called "U-V plane angle of Attack" (range [0-180] with a default value of 30).

Is this some kind of Tint adjustment ? If so, that would be a better name...

Yes, it is the hue angle. Looks like a trap for translators.

The Color Temperature filter do shear mapping along the UV plane in the YUV 3D space. The amount is set be the Temperature, the direction is set by the Angle. That 30 deg direction happens to connect the yellow and the blue areas of the chroma plane.
I dont think that hue (==rotating the chroma plane) would be the most accurate replacement, but feel free to change it

Would UV angle be OK ?

"Chroma angle"? "Chroma transformation angle"?

Quote from: szlldm on February 18, 2021, 02:26:10 AMI dont think that hue (==rotating the chroma plane) would be the most accurate replacement

But it is effectively modifying hue + saturation in one step, no?

It is incredibly important to get wording, grammar, case and punctuation right from the start on, before translators – myself included – submit updates. Later changes mean that the hell of identifying and often manually fixing all affected translations ensues, including languages I have no idea about.

The description of artPixelize needs a fix too. It cannot be just "Pixelize" as lrelease will create just a single source for both the name and description.

In the Crop GUI, the position of the Autocrop button between OK and Cancel seems odd. It would be more logical to place it to the Right of the Reset Button.

Edit: Also AutoCrop on black borders often comes up 2 pixels short on both sides ex: 640x480 input, Autocrop top/bottom:58 vs real: 60.

Quote from: butterw on February 22, 2021, 03:18:27 PMn the Crop GUI, the position of the Autocrop button between OK and Cancel seems odd.

So does Qt following platform guidelines. We have no say in that.

1) Can Avidemux get QAAC support? Officially its seems copyright protected, so software cant be packed with it. But possible for custom support like in foobar- if exists in folder= use it, add some option for it. QAAC q wins vs FDK aac.
Presets example (at least possible can be helpful to somebody):
.aac for video ~200kb/s --tvbr 91 --ignorelength --adts --gapless-mode 1 - -o %d
.m4a iTunes Standart ~128kb/s -s -a 128 -q 1 --ignorelength - -o %d
.m4a iTunes Plus ~256kb/s -s -v256 -q 2 --ignorelength - -o %d
.m4a Alac -s -A --ignorelength - -o %d

2) Good if will be more that 1 default preset.
3) If working with many files but need use same resize same eq presets how possible save it like preset or?
4) VHS is great! But is possible to add tint filter but by mask. I mean mask for shadows or highlights or midtones. Coloring by mask its really cool thing for film effects or some other creative ideas.
5) Connect Avidemux with Reaper daw can be great idea at this time.

in r210228_win64Qt5_54 portable:
! I'm getting a weird "digital clock" style font in the time display. 

Same here. It's hard to read. It's much better if set to bold.

Quote from: szlldm on March 01, 2021, 04:07:21 PMIt's much better if set to bold.

This option has been carefully evaluated and discarded as the E1234 font, now bundled with Avidemux, doesn't have a native bold variant and synthetic emboldening doesn't match the gradients of fonts elsewhere in the GUI.

The digital clock design solves the long-standing issue of variable width font used to display rapidly changing numbers. This was causing shifting during playback, especially bad in on-the-fly filter preview. In absence of a viable solution with platform-specific monospace fonts, this one makes IMHO a lot of sense from usability and design POV.

Quartz watches with liquid crystal displays were an incredible hype in the days of my youth, so I am used to the look. It may be slightly more difficult to read in stop mode, but I think it is vastly better readable during playback (at least I could hardly read the display before this change).

To clarify the choice, here are the requirements:

1. Fixed width, so no shifting

2. Available on every target platform (Linux, macOS, Windows from 7 on)

3. If we cannot rely on a platform-specific font, then the font must have a compatible license allowing redistribution and bundling.

4. Nice to have: small size as we need just 12 characters.