Avidemux Forum

Working script, but I need to change the output location to a different folder other than the input folder (c:\tmp).

Since it will be saved to a different folder, I want to use the same filename that is being loaded (like in this one), but without the ".edit.mp4"


ext="mp4"
inputFolder="c:\\tmp\\"
#
def convert(filein):
    if(0 == adm.loadVideo(filein)):
        ui.displayError("oops","cannot load "+filein)
        raise
    adm.videoCodec("Copy")
    adm.audioClearTracks()
    adm.setSourceTrackLanguage(0,"und")
    if adm.audioTotalTracksCount() <= 0:
            raise("Cannot add audio track 0, total tracks: " + str(adm.audioTotalTracksCount()))
    adm.audioAddTrack(0)
    adm.audioCodec(0, "Lame")
    adm.audioSetDrc(0, 1)
    adm.audioSetShift(0, 0, 0)
    adm.audioSetNormalize2(0, 2, 150, -30)
    adm.setContainer("MP4", "muxerType=0", "optimize=1", "forceAspectRatio=False", "aspectRatio=1", "displayWidth=1280", "rotation=0", "clockfreq=0")
    adm.save(filein+".edit.mp4")

    print("Done")

#
# Main
#
ui=Gui()
adm=Avidemux()
#
list=get_folder_content(inputFolder,ext)
if(list is None):
    raise
for i in list:
        convert(i)
print("Done")



Thanks a lot eumagga0x2a! You have solved my problem as by using the latest version available, fast conversion has come back again!! . However, if possible, I would like to keep the thread open in case other slow conversion-related problems may arise.

You need to know the frame by frame image rate for the original media.  29.97 fps is a NTSC US Standard TV playback speed.  Any 24 fps original movie can be converted to playback in 29.97 by adding in a 3:2 pulldown which is a staggered repeat every 4th frame.  We cannot see this happening and often no one looks closely at the frame by frame sequence to check for this issue.  It's usually there on films converted to DVD or films from standard TV recording.

Showing frame by frame you get this in a 3:2 pulldown.

A B C D D E

Frame D is duplicated and playback is 29.97 fps.  Now, how do you get the new number?

29.97 * 4/5 = 23.976

This can take away the duplicate D frame.  The problem becomes it is not easy to do this precisely because the editing software tries to guess where the duplicate frames are, but any time someone has edited the master or if the editing software cannot find the duplicate frames, it will miss or get out of order.  So, the answer to that is either to have production quality editor with a original master media or just set the frames to blend when you convert the fsp.  This way, any missed frame is smoothed over.

All well and good, but what happens if 29.97 fps is converted to a slower fps, without any attempt to find the duplicate frames or if the original media was already converted to some other fps like 25 fps for PAL TV in the UK, or 30 fps because many editors have that as a default setting?  Then you have a messed up copy that is far from being master original.  Now changing the fps again, can really mess it up and cause stuttering.

So, it's important to look closely and with what the media is exactly.  Open it in the editor and advance frame by frame to see if the 29.97 fps was converted from an original 24 fps using a 3:2 pulldown and duplicating the 4th frame. Every 4th frame will duplicate. If so, then you want to set the filter to remove the 3:2 pulldown go to 23.976 fps and blend the frames.

If the media is has different staggered frames, is an old film running at 30 fps, or all frames are already blended, then it's already been copied and the only option is if you have to edit it, try to leave the fps alone and maybe it will play back without stuttering with the new codec or whatever you are doing.

If the media is 25 fps and it's a US / Canadian film, it's probably just been sped up for playback in the UK. If there are no repeated frames, then changing the fps to 24 with the first filter that also changes the speed and length of the content could make people sound better and the music back to the correct tuning. Sometimes you can spot this if the media length is 24/25 as long as it is suppose to be.

Hope that helps.

Please start by...

1) ...using the latest available official appImage or build Avidemux from source yourself (best);

2) ...providing some usable information, i.e. the properties of the source MKV and MP4 files you are converting (re-encoding) as reported by MediaInfo (do not paste the textual output of MediaInfo into the body of a post, but attach it to your reply instead), the filter chain in use, the settings of the video encoder plugin in Avidemux etc.

Quote from: sl1pkn07 on December 30, 2025, 12:39:55 AMneeds fix for use to "new" API v4

Ideally, yes. Disabling VapourSynth >= 73 to fix build for now: https://github.com/mean00/avidemux2/commit/23b1d8fb1e931660a1a8f1f3cab20186a7b74eb0

Thank you for the heads-up.

Ouch and Bingo:
the solution is provided by the 7z command line switch/value "-t#", which type-triggers the 7z extractor to operate in parser mode,
eg.:  7z x afile.exe  -t#
Solved ..

And for to grep only the .7z files from the setup container: using the -i switch:
eg.:  7z x afile.exe  -t#    -i!*.7z

Hi

vapoursynth removes recently the support for VSScript API3 https://github.com/vapoursynth/vapoursynth/commit/ae7fa51078eacc75f0a6fba16eb4de9c21c6a80e

this means avidemux stop build due missing file in https://github.com/mean00/avidemux2/blob/master/avidemux_plugins/ADM_demuxers/VapourSynth/ADM_vsProxy.h#L20

needs fix for use to "new" API v4

greetings

Actually a simple expansion of these 7z archives contained in the setup exe: 7.7z, 9.7z, 11.7z, 13.7z, 15.7z, 17.7z
is fully sufficient to create a functional Avidemux installation without setup execution, start menu entries, registry entries (maybe others).

So the question would be only: how to extract those files from the setup exe via command line?
Searched around in the net without result yet (remark: i didn't try some python scripts as i don't want to install Python solely for this special purpose).

Hi All

For a few years I've been using avidemux appImage with my laptop acer extensa 5235 released in 2009 and made up of 4 GB of ram and Intel Celeron T3300 bits as a CPU running on a Linux Mint 22.1 Xia xfce version. However, this year I've noticed a dramatic increase in time when converting mkv files into mp4 ones compared to past years' smoother and faster conversions. I've runned via terminal the command nice -n -15 avidemux to give more priority to it but it says that it's impossible to use the commmand, while the mp4-to-mp4 resize-based conversions still run fast and very well. How can I make mkv-to-mp4 conversions faster? Do you have any tips about it?

WT,
Your encoding settings will impact quality.  You are probably not using settings that give the results you wish for.  You can experiement with higher quality settings till you get what you want.  The problem is that many setting changes are not well understood.

For example: Multi pass with variable bit rate should never be used for any streaming media copy.  Most people don't understand why that is true.  Variable bit rate introduces different number of TCP packets to each full frame sequence and when the player needs to have all packets delivered prior to playing a sequence, a variable bit rate will constantly create differently timed caching and this can cause packets to be out of order and the cache limit reached per the TCP packet settings and the player can drop a video sequence as invalid and request it again.  This causes stuttering in the video playback of streaming video over TCP.  It becomes even worse if the is a mobile packet encapsulation for users with mobile connected Internet.  So Constant Bit Rate is always preferred, even though variable does an excellent job, if media playback is direct.

Another tip is to make sure any crop or aspect ratio change results in pixels sizes for width and height that are divisible by 16 (1st preference), 8 or at least 4 as (2nd and 4rd preferences).  If you don't pick these sizes, then encoding quality will be deminished because h.264 is looking to fill in at least 8 x 8 pixel blocks.

In anycase, here are the settings I use for conversion of H.265 to H.264 with AAC audio for 1080P only.  If it is widescreen, you can get away with 2200 instead.  These settings are high to get the quality you want.  A typical Core i7 or similar without hardware encoding will take 5 hours + for a 2 hour media.  If you want the quality and go faster, you need a faster computer or hardware encoding.  Setting the encoding time down to real time or 2 hours per 2 hour media, will end up looking not so nice for h.264 1080P.  You get what you pay for.  You want faster encoding speeds, spend more on your hardware, otherwise put up with the long encoding time.  Go find something else to do, while waiting for the computer to finish encoding.

Custom Config 2400 1080P.json

Quote{
    "useAdvancedConfiguration" : true,
    "general" : {
        "params" : "CBR=2400",
        "threads" : 0,
        "preset" : "medium",
        "tuning" : "none",
        "profile" : "high",
        "fast_decode" : false,
        "zero_latency" : false,
        "fast_first_pass" : true,
        "blueray_compatibility" : false,
        "fake_interlaced" : false
    },
    "level" : -1,
    "vui" : {
        "sar_height" : 1,
        "sar_width" : 1,
        "overscan" : 0,
        "vidformat" : 5,
        "fullrange" : false,
        "colorprim" : 2,
        "transfer" : 2,
        "colmatrix" : 2,
        "chroma_loc" : 0
    },
    "MaxRefFrames" : 3,
    "MinIdr" : 25,
    "MaxIdr" : 125,
    "i_scenecut_threshold" : 40,
    "intra_refresh" : false,
    "MaxBFrame" : 3,
    "i_bframe_adaptive" : 2,
    "i_bframe_bias" : 0,
    "i_bframe_pyramid" : 2,
    "b_deblocking_filter" : true,
    "i_deblocking_filter_alphac0" : 0,
    "i_deblocking_filter_beta" : 0,
    "cabac" : true,
    "interlaced" : false,
    "constrained_intra" : false,
    "tff" : true,
    "fake_interlaced" : false,
    "analyze" : {
        "b_8x8" : true,
        "b_i4x4" : true,
        "b_i8x8" : true,
        "b_p8x8" : true,
        "b_p16x16" : false,
        "b_b16x16" : true,
        "weighted_pred" : 2,
        "weighted_bipred" : true,
        "direct_mv_pred" : 1,
        "chroma_offset" : 0,
        "me_method" : 1,
        "me_range" : 16,
        "mv_range" : -1,
        "mv_range_thread" : -1,
        "subpel_refine" : 10,
        "chroma_me" : true,
        "mixed_references" : true,
        "trellis" : 2,
        "psy_rd" : 1,
        "psy_trellis" : 0,
        "fast_pskip" : true,
        "dct_decimate" : true,
        "noise_reduction" : 0,
        "psy" : true,
        "intra_luma" : 11,
        "inter_luma" : 21
    },
    "ratecontrol" : {
        "rc_method" : 0,
        "qp_constant" : 0,
        "qp_min" : 10,
        "qp_max" : 51,
        "qp_step" : 4,
        "bitrate" : 0,
        "rate_tolerance" : 1,
        "vbv_max_bitrate" : 0,
        "vbv_buffer_size" : 0,
        "vbv_buffer_init" : 1,
        "ip_factor" : 1.4,
        "pb_factor" : 1.3,
        "aq_mode" : 2,
        "aq_strength" : 1,
        "mb_tree" : true,
        "lookahead" : 40
    }
}