Avidemux Forum

Thank you. The log uploaded to pastebin was generated by a VC++ nightly build from Jan 1 2025. It falls into a period of big code reshuffle and Visual Studio build node changes, thus exhibiting many regressions. In the log, probing for AV1 support in NVDEC succeeds, but a later get_format call doesn't find a hw accel for the pixel format. This may be a regression specific to that transitory phase of code reorganization and build node rebuild.

Please make sure you really run the r241212 cross-compiled build. In doubt, please uninstall the VC++ build from that very unstable phase (there is a warning pinned in this forum that is however directed to those who compile Avidemux themselves, but, of course, it applies to everyone).

File is attached to this post, or alternatively I've also uploaded it to pastebin at https://pastebin.com/sbu2kHSM

Ich habe dieses Problem mit den fehlenden I-Frame-Flags bei allen ARD-DVB-T2-Programmen ab ca. Febr. 2024 bemerkt. Dagegen sind die bei allen Programmen im ZDF-Bouquet (noch) vorhanden, sowie auch in der ARD-Mediathek, d.h. auch in den heruntergeladenen Kopien.
Ich habe einige - z.T. notdürftige - Workarounds gefunden:
1. Werbung und z.T. auch Trailer für kommende Beiträge haben oft noch die Flags, so dass man den grössten Teil von Vor- und Nachlauf auch mit AviDemux leicht entfernen kann. (Sehr gut ist die Werbung von Babble, weil meist direkt vor und nach dem Film.)
2. Die beschnittenen Aufnahmen unbedingt im .TS-Format belassen! Dann kann man sie fast ohne Einbußen mit VCL und MpvNet abspielen, also auch vor- und zurückspulen etc. Scheint, das die die I-Frames im Stream an den Inhalten erkennen können, wie übrigens auch die dümmsten Player, nur dann darf man höchstens stoppen. Nach Spulen springen die aber wieder zum nächsten I-Frame.
3. Wenn garnichts mehr hilft, suche ich die Zeiten (leider gibts nur diese) von Anfang und Ende des Films mit MpvNet. Ich habe mir schon vor Jahren ein Programm gebastelt, mit dem man Teile aufs Byte genau aus Filestreams herausschneiden kann. Input sind Gesamtdauer und Filegröße. Daraus wird die Durchschnitts-Datanrate bestimmt und eine Näherung für Anfangs- und End-Byteposition errechnet. 
Manchmal passt es sehr gut, manchmal ist aber auch einiges Trial und Error notwendig. Zum Glück kopiert mein Programm einen 2-Stunden-Film in wenigen Sekunden heraus (mit SSD's).
4. Mit ffmpeg soll das auch möglich sein, habe das mangels tieferer Kenntnissen aber noch nicht geschafft.
5. (Wish for AviDemux-Developer: Check box or so to switch off the automatic keyframe search and jump to.) Mit AviDemux könnte das ein Kinderspiel sein, wenn der nicht immer (verdammt noch mal !!!) nach dem nächsten I-Frame-Flag suchen und dahin vor- bzw. zurückspringen würde. Wenn man ihn nämlich mit Wiedergabe an die richtige Stelle laufen lässt, (das kann aber lange dauern) und dort schneidet, meckert er zwar, aber die Bildstörung dauert i.d.R. nur Zehntelsekunden mit VCL und MpvNet.

The problem is likely related to audio track being Mono (and something not yet identified as monaural tracks I created locally work just fine). You might try enabling remixing to Stereo. Also please test the lavc (libavcodec) AAC encoder rather than that by FDK.

Quote from: Rhapsody on January 14, 2025, 10:42:40 PMIs there something I can send you like my settings file to try and figure out why this isn't working, in this case?

Please provide admlog.txt from %localappdata%\avidemux\ (when in non-portable mode) or from subdirectory "settings" or the program directory (when in portable mode) created by launching Avidemux, loading the sample video and closing Avidemux. You may or rather should anonymize it by consistently replacing paths in it with placeholders and ZIP-compress it prior to attaching it to your reply.

I must add that Avidemux forum has problems with HTTP2, e.g. it is not possible to download attachments over HTTP2. At least Firefox allows to work around this issue by disabling the protocol: set network.http.http2.enabled to false and restart the browser.

Quote from: eumagga0x2a on January 14, 2025, 11:15:10 AMJust tried on Windows 11 on a PC with NVIDIA Geforce RTX 3050:

The official r241212 build: playing the sample works fine via DXVA2 and NVDEC.

My own cross-compiled build with experimental features built into libaom: playing the sample works via software decoder which is libaom (requires VU meter to be hidden to keep up with the frame rate), DXVA2 and NVDEC.

The drawback of enabling experimental features in libaom is that it requires the library to be built as a static library instead of a shared one. This increases the size of the installation by approx. 7 MiB.

241212 is definitely the version I'm using. Is there something I can send you like my settings file to try and figure out why this isn't working, in this case?

Edit: Just checked the decoder in use (I never noticed that it shows it at the bottom, thank you Geo_log) and it says the decoder in use is Lavcodec despite the HW Accel section having the DXVA2 and NVDEC options checked, and the Threading section having the Multi-threading option disabled.

Related thread regarding UI, but not same issue so hoping it's ok I make a new topic on this
gui warning (feature request)

Avidemux v2.8.2 (241212_ce994de41a6)
Compiler: GCC 13.3.0
Build Target: Microsoft Windows (x86-64)
User Interface: Qt (5.15.15)
Operating System: Microsoft Windows (6.2.9200; 64-bit)
Time: Wed Jan 08 14:25:30 2025

0: C:\Users\keirg\tools\portable\avidemux_64\avidemux.exe

ffprobe output of the input video file (should give at least as detailed output as mediainfo, doesn't need any installing as it is pre-installed on my Linux Fedora KDE computer at home)
$ ffprobe Grunnopplæring.mp4 -hide_banner
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Grunnopplæring.mp4':
  Metadata:
    major_brand     : isom
    minor_version   : 512
    compatible_brands: isomiso2
    creation_time   : 2024-10-09T11:15:22.000000Z
  Duration: 01:47:04.64, start: 0.000000, bitrate: 424 kb/s
  Stream #0:0[0x2](eng): Video: h264 (libopenh264) (Baseline) (avc1 / 0x31637661), yuv420p(progressive), 1920x1080, 371 kb/s, 16 fps, 16 tbr, 10k tbn (default)
      Metadata:
        creation_time   : 2024-10-09T11:15:22.000000Z
        vendor_id       : [0][0][0][0]
  Stream #0:1[0x1](eng): Audio: aac (libfdk_aac) (mp4a / 0x6134706D), 16000 Hz, mono, s16, 51 kb/s (default)
      Metadata:
        creation_time   : 2024-10-09T11:15:22.000000Z
        vendor_id       : [0][0][0][0]

Different practical output tests to see what works and what does not work

• setContainer = MKV ; audioCodec = FDK_AAC ; Corrupted audo
• setContainer = MKV ; audioCodec = PCM ; Normal audible audo
• setContainer = MKV ; audioCodec = AC3 ; Error message, unable to continue
• setContainer = MKV ; audioCodec = Copy ; Normal audible audo

Error message when selecting AC3 audio format (cannot copy plain text in W11)
You cannot view this attachment.

Set of sample py files - file name indicate success or not (forum wouldn't allow me to upload the last one with pcm, but the cut time stamps where the same as the others)
You cannot view this attachment.
You cannot view this attachment.
You cannot view this attachment. 



Edit: Idea about possible reason for this issue
Ok, so I just litterally did the ffprobe command a couple of minutes before I posted the thread. I now realize the audio bitrate of the original audio track is way lower (51 kb/s) than what I specified as output.
Can this be the sole cause of the issue I ran into ?

Press Abort, does not work either while enconding

Quote13:07:45-058 [DIA_encodingQt4::pauseButtonPressed] StopReq
Alternate - "The encoding is paused. Do you want to resume or abort?": "Resume" or "Abort"
Alternate: the first option chosen
  2% done   frames: 2660   elapsed: 00:00:05,176
  3% done   frames: 3398   elapsed: 00:00:06,178
  3% done   frames: 4217   elapsed: 00:00:07,179
13:07:49-641 [DIA_encodingQt4::pauseButtonPressed] StopReq
Alternate - "The encoding is paused. Do you want to resume or abort?": "Resume" or "Abort"
Alternate: the first option chosen

Just noticed, when I logged in under Wayland, So I'm back in x11. And see what you can dig up. Thanks.

On Wayland nothing works (without a workaround) as long as the mean00/wayland branch is not yet merged into master. That said, please keep using an X11 session for Avidemux for now.