This thread is exclusively for feedback/info (features/bugs) about the latest versions of Avidemux v2.8.1
https://github.com/mean00/avidemux2 (https://github.com/mean00/avidemux2)
Latest dev builds https://www.avidemux.org/nightly/ (https://www.avidemux.org/nightly/)
New nightly 220125
-very quick method to add partial filters using the Ctrl+F keyboard shortcut
-in View/Theme menu you can select a "Light theme" and a "Dark theme" besides the default one.
-fixed maximized window on windows
Previous nightlies (after release)
-fix crash copying to clipboard when selection extends to the end of video
-New filter: 3D LUT, currently cube and haldclut (8 bit png) files supported
-loading image sequence, the frame rate can be defined in the Preferences
-improved indexer of the Matroska demuxer
-lavc (sw decoding) threading up to 16 threads
-x265 and libaom version upgrades
-A-law audio decoder
-other fixes and improvements
New nightly 220130
-delogoHQ filter: fixed darkening, better quality blur gradient
-theme switching bugfixes
-HDR RGB tone mappers: more accurate colors, performance improvements
Quote from: szlldm on February 01, 2022, 12:47:38 AM-delogoHQ filter: fixed darkening, better quality blur gradient
Would like to try this, but no MacOS Catalina version yet.
New nightly 220207
-video information has been extended with pixel format and colorspace informations
-mouse wheel can be reversed for navigation
-post processing (deinterlacing and deblocking) now actually works
-keyframe navigation errors in case of h264 videos have been fixed
-opus audio channel mapping issues have been fixed
New nightly 220330
-E-AC3 support
-adaptive HDR/RGB tonemappers + performance&quality improvements
-GUI can handle up to 32 audio tracks
-encoding priority can be lowered on *nix (Mac,Linux,...)
-new audio downmix options: stereo headphones and (virtual) surround headphones
-volume setting is saved
+bugfixes
Quote from: szlldm on March 30, 2022, 10:15:14 AM-E-AC3 support
To avoid confusion, I would like to add that support for E-AC3 in demuxers, in libavformat-based muxers and in the libavcodec-based audio decoder plugin was present in Avidemux for quite a few years. However, the ability to handle multiple E-AC3 frames (one so-called independent frame followed by one or more dependent frames which may provide additional channels with custom layouts) in a single audio packet is new.
With vsWin64/Avidemux_2.8.1 VC++ 64bits 220323.exe version and Resample FPS filter hangs Avidemux when starting encoding.
Chosen codec: HEVC(x265), Resample FPS filter with motion compensation option.
That bug occurred in version 2.8.0 either.
Without frame interpolation or with Blend its working.
Could you please reproduce the issue and prior to restarting Avidemux, provide admlog.txt from %localappdata%\avidemux\ folder? Could you please also test whether the latest available MinGW ("win64") build exhibits the same problem?
Upon a quick test on Linux, I could not reproduce a hang with x265 and Resample FPS (30000/1001 --> 25 fps) filter with motion compensation enabled.
Tried /win64/avidemux_r220330_win64Qt5_131.zip
Its just closing itself without any sign when starting encoding.
How can I upload the txt files here?
Quote from: Norbi on April 17, 2022, 01:43:52 AMHow can I upload the txt files here?
When you use the reply button instead of "quick reply", you can attach files up to 512 KiB to your reply. Else please use pastebin, WeTransfer, Mega, Dropbox or Google Drive and either post the link in your reply or send me the link via PM in case CleanTalk interferes with posting.
Ok, I attached both versions admlog after hanging/closing.
admlog_vc.txt
admlog_qt5.txt
The issue is now fixed (https://github.com/mean00/avidemux2/commit/87a735d75a65e7685f6d13dc53adadc5b5cc3545) by szlldm, please try a future nightly.
Thank you for your report.
Option "optimize" does not function anymore !!!
I have the follwing line in my custom py-files (batch script for many files):
adm.setContainer("MP4", "muxerType=0", "optimize=0", "forceAspectRatio=False", "aspectRatio=1", "rotation=0", "clockfreq=0")
Since I updated to version 2.8.1 the option "optimize" is not processed anymore.
AviDemux always moves the entries to the beginning of the file (optimize=1), so changes with the windows dialog take now 1 to 2 minutes :-(
When I use this script as a custom configuration, option 1 is selected although a zero is set in the script. When I set the option in the dialog for "mp4 files" to "no optimizing", the output has the right format.
Please fix it fast as possible !!!
Quote from: axst on April 18, 2022, 08:37:12 PMI have the follwing line in my custom py-files (batch script for many files):
adm.setContainer("MP4", "muxerType=0", "optimize=0", "forceAspectRatio=False", "aspectRatio=1", "rotation=0", "clockfreq=0")
This configuration is incomplete as muxers expect (and always expected) the full parameter list, which would be in case of MP4 muxer
adm.setContainer("MP4", "muxerType=0", "optimize=0", "forceAspectRatio=False", "displayWidth=1280", "aspectRatio=1", "rotation=0", "clockfreq=0")(the value of displayWidth is ignored if forceAspectRatio is
false or aspectRatio is not equal 4). I am not sure at the moment whether we may safely change parameter list parsing for muxers to accept those with some parameters missing. Relaxed parsing would allow to handle situations like yours gracefully.
New nightly 220501
-ffNvEnc encoder has more configuration options
-VideoToolbox HEVC encoder on macOS
Audio filter department got a major upgrade:
-configurable Compressor (DRC)
-3 band Equalizer
-channel gain adjusment
-channel delay adjusment
-channel remap
-custom "Frame rate change" a.k.a. audio stretch with pitch adjusment
+bugfixes (non-ASCII characters in a path; motion interpolation)
Also (not directly related to nightlies) native build now possible on Mac/arm64
New nightly 220507
-bugfixes
New nightly 220617
-new HiDPI compatible buttons
-the Backward/Forward one minute buttons can be configured (1/2/4/60 sec) by scrolling over them
previous nightly builds:
-new filter: Decimate
-update bundled FFmpeg to 4.4.2 release
-VDPAU support for VP9
-save resize algorithm choise in filters
+bugfixes
Quote from: szlldm on June 18, 2022, 08:59:32 PM-VDPAU support for VP9
Not in the official nightlies, unfortunately: the platform used to generate "modern" appImages for old but not really ancient distributions like Ubuntu 20.04.x (Debian Buster) has a libvdpau version too old to support this feature.
To be able to decode VP9 using an NVIDIA graphics card (it must be a pretty recent one) with the closed-source NVIDIA driver, please install libvdpau headers (e.g.
libvdpau-devel on Fedora) and build Avidemux from source. The libvdpau version must be at least 1.4 or newer.
A new win64 (https://avidemux.org/nightly/win64/) (i.e. cross-compiled on Linux for 64-bit Windows) nightly build, r220620:
- Support for decoding 8-bit VP9 in hardware on Windows via DXVA2 added, presumes a graphics card capable of decoding VP9 (e.g. NVIDIA GPUs from Turing on).
I have the 220620 build, there's a bug with setting markers for cuts. After I set the initial A and B markers on the timeline, when I set another A (start) point, it was registered as a B (end) point instead.
There is an option in the Preferences for that.
Quote from: eumagga0x2a on June 25, 2022, 07:08:03 AMThere is an option in the Preferences for that.
Thanks it works.
Quote from: eumagga0x2a on April 19, 2022, 10:25:58 PMQuote from: axst on April 18, 2022, 08:37:12 PMI have the follwing line in my custom py-files (batch script for many files):
adm.setContainer("MP4", "muxerType=0", "optimize=0", "forceAspectRatio=False", "aspectRatio=1", "rotation=0", "clockfreq=0")
This configuration is incomplete as muxers expect (and always expected) the full parameter list, which would be in case of MP4 muxer
adm.setContainer("MP4", "muxerType=0", "optimize=0", "forceAspectRatio=False", "displayWidth=1280", "aspectRatio=1", "rotation=0", "clockfreq=0")
(the value of displayWidth is ignored if forceAspectRatio is false or aspectRatio is not equal 4). I am not sure at the moment whether we may safely change parameter list parsing for muxers to accept those with some parameters missing. Relaxed parsing would allow to handle situations like yours gracefully.
It would make sense to set missing parameters to sensible default values IMO. It allows for more readable scripts and avoids script breakage when a new option is added.
Just installed latest vsWin64 nightly (2.8.1 VC++ 220618), nice new buttons (and they scale properly on 4k, not the "ugly" aliased upscale like before), and I'm glad the bug that caused error with NVENC encode when using B-frames is fixed :D
just tried latest nightly (I am using v2.7.9 dev).
Changes I liked:
- Time was changed to start at 0 for first frame
- Improved Audio-meter
- The Zoom display in the toolbar.
- You can backward/forward 60s while playing.
- dark theme available on Windows.
But I prefer the old toolbar buttons (@1080p).
Things that could be improved:
- Playing a video with mono audio, I get a dual Audio-meter display.
- Trimming at the start or the end of a video should display a red cut point, it's an edit.
In v2.7.9-dev, it was possible to manually create segments by selecting and cutting/pasting in place. This could be useful for visualization/navigation purposes, but this no longer seems to work ?
Possibly there needs to be a distinction made between edits (red mark) and a new bookmarks feature (ex: green mark).
In the crop filter, it would be good to have at least one extra value for cropping to portrait mode. Currently in the locked AR combo-box there is only 1:1 and 9/16=0.5625.
Sometimes 9/16 is too narrow. The intermediate value would be 3/4=0.75
In x264 codec configuration gui, the "Frame > minimum gop size" is capped at 100, which corresponds to 4s keyframes at 25fps. Could the cap be increased (ex: cap at 300) to allow forcing a longer keyframe interval ?
Quote from: butterw on June 29, 2022, 04:17:11 PM- You can backward/forward 60s while playing.
Not only 60s but also 4s, 2s and 1s. Try to rotate mouse wheel (or scroll using touchpad) atop of the 60s buttons (all kudos to szlldm).
Quote from: butterw on June 29, 2022, 04:17:11 PMBut I prefer the old toolbar buttons (@1080p).
Just the toolbar or both toolbar and navigation?
Quote from: butterw on June 29, 2022, 04:17:11 PM- Playing a video with mono audio, I get a dual Audio-meter display.
Because you remix to Stereo. I am not sure that the ancient win32 audio device interface we use works with anything else, it definitely doesn't work you multichannel audio. Don't know about mono.
Quote from: butterw on June 29, 2022, 04:17:11 PMIn v2.7.9-dev, it was possible to manually create segments by selecting and cutting/pasting in place. This could be useful for visualization/navigation purposes, but this no longer seems to work ?
Contiguous segments, misappropriated to serve as surrogate chapters, breaking copy mode, are now automatically joined. Yes, a true support for chapters is nice to have.
Quote from: butterw on June 29, 2022, 04:17:11 PMBut I prefer the old toolbar buttons (@1080p).
Quote from: eumagga0x2a on June 30, 2022, 09:56:57 PMJust the toolbar or both toolbar and navigation?
Both toolbar and navigation icons.
the old icons had a simpler design which made them more readable.
The new icons are large. It's more difficult to see whether play filtered is activated.
- Up/down Arrows also do not intuitively suggest Open/Save to me.
v2.8 changelog: Timestamps in format 00:00:00.000 like copied to clipboard by pressing CTRL+SHIFT+C can be pasted into the "Go to Time" dialog using CTRL+V.
[Issue with 30fps video !!!]
Copy frame pts 00:00:06.033 and paste into "Go to time" dialog >> seeks to the previous frame 00:00:06.000
if I change to 00:00:06.034 it seeks to the correct frame.
Quote from: butterw on July 01, 2022, 12:25:52 AMUp/down Arrows also do not intuitively suggest Open/Save to me
How does a "floppy disc", an obsolete technology - unknown since the last century/millenium - suggest better ;D ?
With big shiny arrows pointing in every direction, I got confused. ;)
IMO it would be best to provide users with the option to use the old icon set, unless there is reason why this approach is entirely unrealistic.
Quote from: butterw on July 01, 2022, 12:58:32 AMCopy frame pts 00:00:06.033 and paste into "Go to time" dialog >> seeks to the previous frame 00:00:06.000
I agree that this is counter-intuitive, but not more than that :-)
Quote from: eumagga0x2a on July 01, 2022, 06:36:03 PMQuote from: butterw on July 01, 2022, 12:58:32 AMCopy frame pts 00:00:06.033 and paste into "Go to time" dialog >> seeks to the previous frame 00:00:06.000
I agree that this is counter-intuitive, but not more than that :-)
Not being able to reliably seek to the correct frame in a video editing program is a serious flaw.
"Go to time" rounding/seeking to previous frame- seeks OK with 25fps videos.
- with 30fps, once every 3 frames it gets the frame correct...
- with ntsc, you almost always get the previous frame instead.
Either the pts needs to be output/entered with microsecond precision for this to work, or the "Go to Time" needs to be able to figure out the correct frame.
[GUI suggestion] Add a tooltip on the thumb slider, because it is not obvious how to use it: "fast-forward with mouse wheel".
Quote from: butterw on July 01, 2022, 08:38:00 PMEither the pts needs to be output/entered with microsecond precision for this to work, or the "Go to Time" needs to be able to figure out the correct frame.
As Avidemux always rounds down timestamps shown in the time display, I have to agree that the result of a cycle "Ctrl+Shift+C" --> "Ctrl+T" --> "Ctrl+V" --> "Return" indeed looks bad if timestamps are not an exact multiple of a millisecond. Fixed in the code a couple of days ago.
Quote from: butterw on July 06, 2022, 08:35:35 AMAdd a tooltip on the thumb slider, because it is not obvious how to use it: "fast-forward with mouse wheel".
This is actually not the way how to use it. The main way of operation is to grab the slider and keep it deflected from the neutral position to seek backward or forward, then release. However, two years ago I added the ability to deflect it using mouse wheel, just because I felt it to be counter-intuitive that you could not do it.
A tooltip would be almost always triggered during normal operation of thumb slider. This would be very annoying, IMHO.
I was thinking the interface tooltips should time-out after maybe 2s. But I agree these tooltips can be a hinderance, and also that they are not well suited for long text.
With regards to the thumb slider and how to use the interface, some basic updated user instructions are needed and should be available via the help menu together with the release notes/changelog. There are only a couple things that aren't obvious IMO (ex: how to use the thumb slider to fast forward, Ctrl-V in Go to Time, the MarkerB frame isn't saved now, etc.).
[Thumb slider control]
It takes 9 scrolls for me to reach max speed on the thumb slider, so I did assume something was wrong. At the same time holding the mouse button for longer periods of time can be tiring. How about using the right mouse button click on the thumb slider for a set and hold option ?
New nightly 220802 available
The main changes since the previous official nightly build from July 20:
- A button to open HDR tone mapper configuration dialog added to toolbar, visible when such conversion is applicable
- Peak memory footprint of the internal RubberBand library reduced
- pal2film and film2pal audio filters rolled back to the old implementation (faster)
- The logo image in "Add logo" video filter has been made draggable
- Buttons to seek to the start and to the end of selection added to on-the-fly preview of video filters
New nightly 220903
-Audio stretch use new library (soundtouch), providing better quality
-OpenGL acceleration in filter previews
Hi, latest 2 Nightly versions are with this error when open, sorry for my english, i'm Spanish:
(https://i.ibb.co/9rhr0YD/Error-2-Latest-Nightly-Avidemux.png)
Note: Deleted user name and others directories from image at latest Windows 10 Pro X64.
Possible fix? Thanks in advanced.
This are the Buids i'm comment with same problem;
https://avidemux.org/nightly/win64/avidemux_r220802_win64Qt5_141.zip
https://avidemux.org/nightly/win64/avidemux_r220903_win64Qt5_142.zip
You have installed into (or over) a directory which contained files (the obsolete "horizontalFlip" video filter) from older versions. Please make sure you never mix files from different versions or compiler types (i.e. never mix VC++ and MinGW binaries).
Quote from: eumagga0x2a on September 04, 2022, 02:03:31 PMYou have installed into (or over) a directory which contained files (the obsolete "horizontalFlip" video filter) from older versions. Please make sure you never mix files from different versions or compiler types (i.e. never mix VC++ and MinGW binaries).
Hi, only decompress at same directory of older version from July. Now deleted and create new directory with latest version and solved. Thanks for advise.
Here are the nightly builds for all supported 64-bit platforms, which were built on different days but from the very same code (square brackets around the period between basename and extension serve the purpose to fool the forum software which else would interpret them as URLs):
- avidemuxUniversal_amd64_220903_169[.]app => appImages for very ancient Linux distributions (https://avidemux.org/nightly/appImage4/)
- avidemuxLinux_GLIBC_2.28_amd64_220903_0937[.]app => appImages for Linux distribution from current ones back to Debian Buster or Ubuntu 20.04 (https://avidemux.org/nightly/appImage4Buster/)
- Avidemux_2.8.1 VC++ 64bits 220905[.]exe => Native build for Windows, compiled on Windows with Microsoft Visual Studio (https://avidemux.org/nightly/vsWin64/)
- avidemux_2.8.1 r220903_win64[.]exe and avidemux_r220903_win64Qt5_142[.]zip => Builds for Windows, cross-compiled on Linux (https://avidemux.org/nightly/win64/)
- Avidemux 2.8.1 Qt6 220904-02h26m_40a2ab7628f[.]dmg => Builds for macOS, built on and for Monterey (https://avidemux.org/nightly/osx_monterey/)
These nightlies are as close to being Release Candidates as only possible – it is high time to report regressions which evaded discovery so far.
Avidemux 2.8.1 has been released, therefore setting this topic non-sticky. Nightlies of the next release cycle will be discussed in a new topic.