Avidemux Forum

Oh god...

>>> "Please provide a small example of this cr@p, or at least its Mediainfo."

What "mediainfo"? It's HEVC!! Self-explanatory! A compressed video file that decompresses/decodes on the fly during playback, which causes long pauses and hangs when manually jumping to random points in the movie, hence why HEVC sucks. Annoying as hell.

AVC does not do that, as it is not compressed, and the very reason why I want HEVC files converted to AVC.

Most times, a HEVC will convert to AVC without any undesired results that cannot be explained or corrected. I use the Constant Bitrate Single Pass @ 2500kbps (or higher, if necessary, which I do not find out til after 2 hours of converting time is wasted), in hopes that the output comes as close to a video bitrate of 2500kbps without going over (the occasional 2501 is acceptable) or less than 2495.

But every now and then, a HEVC file comes along that pulls this half-ass nonsense. HEVCs are smaller than AVC so they should always yield a bigger file size with a bitrate close to the value (2500+) that I entered, but it's slashing to much smaller instead.

I cannot see anything in the source file's details that would be a red flag. I use VLC and Mp3Tag ediotr to see this info (if it's available - another strike against HEVC is that all but the audio bitrate, run time, and filesize shows as blank in Mp3Tag editor - no aspect ratio dimensions, no video bitrate).

These problematic HEVCs appear no different from the other ones that convert easily ; same aspect ratio (1920x800-1080p), same audio codec (AAC), same audio bitrate (224kbps), same audio sample frequency (48kHz), same framerate (23.98 or 24 fps), and same container (mp4).

Since posting this topic, I suspect the only workaround is to take whatever LOW video bitrate output is yielded from an initial conversion, double it, and if the sum is more/less than 2500, then (respectively) subtract/add the difference to the target value preset of 2500, after DOUBLING it first (to 5000), and then modify accordingly until the desired outcome is achieved...? I have yet to test this theory for consistency and reliability, though... but based on the 2 recent experiences I had where this bizarre phenomenon occurred, it looks that way.

It's hard enough to obtain the desired 2500kbps (acceptable variable range of 2495-2501) - with no way to even get an estimated output BEFORE encoding so I am not re-encoding all day long trying to hit the target - without these random HEVCs adding to the hassle by pulling a "shrinkflation" stunt for no apparent reason.


>>> "What are these encoding options now?"

Whatever Avidemux 2·7·1 offers. I am honestly not sure what you are asking me here. I get the feeling even if knew and I told you, it would make no difference cos you'd be as clueless as I am as to the reason for this "HEVC half-ass" conversion issue.

I also doubt upgrading anything will even be possible (I assume that will be the default reply/suggestion from many ; the one-size-fits-all answer to everything, whether it makes practical sense or not - "juss UPGRADE, bruh!").

Sadly, I must be cautious with upgrading since I have an older system (XP 32bit) that I prefer, cos I have over a decade of work created on that platform, comprised of thousands of files that are dependent on unique-to-32bit programs that created and opens those files. If something won't run (is not supported) on XP 32bit, then it's useless to me, and I cannot afford newer computers, so even if I was open to an upgrade, finances say no.


>>> "You can use Avidemux in the portable mode, just download new version from https://avidemux.org/nightly/ to a new folder and  rename avidemux.exe to avidemux_portable.exe"

Portable shmortable. I have no idea what that means or anything about that. Sounds like bigger problems in a smaller filesize.

I see, the audio tracks configuration dialog exhibits a very minor issue of pre-selecting the first source track for every disabled output track on dialog construction, even if the number of active output tracks is less than the number of source tracks. The issue with that is that simply enabling a formely disabled output track will create a configuration (multiple use of the same source track) which Avidemux doesn't support yet, displaying a corresponding error message on accepting the dialog.

IMHO, a better approach would be to set combo box index to a source track not already in use and, as an enhancement, to add a "Restore default" button.

The lack of differentiation between source tracks (in dropdown menus) and output tracks (the "Track 1", "Track 2" etc. labels in the leftmost column of the dialog) may cause some confusion as well.

I have a video file with multiple audio tracks. When I try to go to Audio > Select Track and disable some of them to check which one is which, the next time I go back all the tracks just appear to be the same and track 1 is always enabled. If I try to disable it and enable track 2, when I check again just track 1 is enabled.

I second this request! I would love to have RIFE as an interpolation option. =:o}

Thanks dosdan2!!!

Quote from: scar69 on August 05, 2025, 05:59:57 PMfor %%f in (*.avi) do %avidemux% --output-format %outputformat% --load "%%f" --save "%%f.mp4" --quit

Use %%F and "%%~dpnF.mp4". The use of upper-case F is importand here so the command interpreter does not  confuse it with %%~f which is also a valid parameter extension.

Here's a test example, with 5 AVIs in the current root directory of "D:". How not to include the ".avi" in the full pathname and include ".mp4" instead:

dir /b *.avi

! x264.avi
60frames.avi
Dream World 038.avi
GA1.avi
Testfile_atempo.avi

Create TEST1.BAT

@echo off
for %%F in (*.avi) do echo "%%~dpnF.mp4"

Run TEST1.BAT

"D:\! x264.mp4"
"D:\60frames.mp4"
"D:\Dream World 038.mp4"
"D:\GA1.mp4"
"D:\Testfile_atempo.mp4"

For an explanation of the parameter extensions used here, see https://ss64.com/nt/syntax-args.html

Thank you @Geo_log - I'll have a look at this tomorrow 

I am trying to convert some classic 80's adult from avi to mp4. Through a google search I found a batch script that does work but the only issue I am having is the resulting file is named *****.avi. Is there a way for the script to remove the .avi from the file name so I don't need to manually rename each file? Here is the script I am using...

set avidemux="C:\Program Files\Avidemux 2.8 VC++ 64bits\avidemux.exe"

set outputformat=MP4

for %%f in (*.avi) do %avidemux% --output-format %outputformat% --load "%%f" --save "%%f.mp4" --quit

TIA

I figured out how to make h.265/x.265 mkvs work when you turn them inside out into mp4's for smart TV playback via fat32 formatted USB.

First of all 265 has a different exit loop than 264 so the MP4 always looks like corruption. You have to use a hex editor on the MP4 output file. It depends on the 265 that is used. There are 2 different versions of 265 and I'm not talking about h and x. I'm taking about 10 bit and 12 bit. The MP4 doesn't know how to exit loop. And well, we see garbled corruption instead of cartoons. I did some research. I went to college for computer science programming Soo I know a thing or 2. I figured out that the first exit loop for h.265 10 bit is 160 or five 32's. Computers like even numbers better to run so you should probably make it ten 16's either way the answer for h.265 10 bit is 160. 160 is the first exit loop that exists in math for 10 bit that also matches an 8 bit machine. The other version of h.265 is 12 bit and it's first exit loop is 96. Three 32's or six 16's. You have to edit the outputted MP4 with a hex editor and change the exit loop number accordingly. Cheers!!

If you perform a search (top right corner of the page, "Entire forum" option) for "Video is late by" you will find two links with explanations:

Quote from: eumagga0x2a on January 04, 2024, 07:24:40 AM"video is late by XX ms" warnings .. - This is a feature kindly contributed by szlldm and a purely informational one. Before that, there was no way to detect and especially to quantify loss of sync due to slow decoding / post-processing during playback.

and further on that topic:

Quote from: eumagga0x2a on January 05, 2024, 12:58:49 AMkeep using "DXVA2" (actually, DirectX) video display on Windows whenever possible

I downloaded your file and played it without messades with Adidemux 241212 with Preference -> HW Accel -> all boxes ticked ON.