Avidemux Forum

Version 2.8.2 241212 - 64 bits displays a black screen where the video should be.  So does 2.8.2 241214 VC++ 64bits.

I had it working before, but then it had a black screen.  I played with other versions then it started working again.  Now it's back to the black screen.  So I uninstalled all versions, rebooted, reinstalled 2.8.2 241214 VC++ 64bits and still a black screen.  I reinstalled all other versions and still a black screen.  I have no idea how to fix it.

Version 2.8.2 250109 VC++ 64bits works, but doesn't have H264.
Version 2.8.1 VC++ 64bits works, but encodes with fractional frame rates (at least windows says it does).
Version 2.8.0 VC++ 64bits works, but also encodes with fractional frame rates.

I'd like to continue experimenting, but I can't find a working version higher than 2.7.8 to experiment with.

Quote from: eumagga0x2a on January 17, 2025, 09:05:43 AMIf you don't want quantizer being increased (equal to quality being reduced) where the CRF algorithm thinks this is permissible without the viewer noticing, just use the constant quantizer (CQ) mode.

Good idea except theoretically it should make the file bigger, but in reality I just spent a few hours encoding AVIs in CR, CQ, and 2-pass and didn't observe any difference in anything.

CR = 25 = 11,387kbps = 81.4mb
CQ = 30 = 11,268kbps = 80.6mb
2P =    = 11,386kbps = 81.4mb

Even the encoding times were the same because each pass of the 2-pass goes faster, so the total time is the same time as a single pass of CQ or CR.

I can't see any difference in quality.  I compared frame by frame deer moving their legs and heads in fast motion and I saw zero difference between the 3 encodings.  No difference with the original AVI either.

The only difference I noticed is the extradata.

CR = 43
CQ = 44
2P = 44

I can join the 2P and CQ in copy mode, but not CR because it's an odd number.

Now I'm wondering do CQ, CR, 2P really do anything differently, other than muddle the extradata.

CQ should be a bigger file than CR because the whole point of CR is to make a smaller file by blurring fast motion which no one can see anyway.  But my example the CQ was smaller.

That experiment was on 2.7.8.  I will repeat on 2.8.2 241212

Quote from: MilosP008 on February 07, 2025, 06:44:07 PM

Quote from: szlldm on March 03, 2021, 08:35:16 PMMaybe you overlooked it:

QuoteYou save with copy mode the preceding half, then the part after the bad segment (both cut at keyframe). Fix and reencode the bad part, then append the 3 part together.

If there is a problem with the audio after appending, you still can merge in the audio fom the original file.

You still didn't answer the question, i have the same issue, i need to encode only stuff that i cutted and not whole video so i wont wait 2 hours for encoding

I do that all the time without issue and I really don't know much about this stuff. I would cut the video into 3 pieces at the key frames.  1st piece ends with the key frame just before the error.  Save that as Video A.  The 2nd piece is the small piece with the error.  Save that as Video B.  The 3rd piece is what's left.  Save that as Video C.

Edit Video B and reencode using the exact same parameters as before.  Then drop Video A into the avidemux window, then drop Video B into the window, then drop Video C into the window.  Select copy for audio and video.  Click save.

Be sure to use version 2.7.8 or newer.

The op is correct.

I tried 2.5.6, 2.6.8 64bit, 2.7.1 64bit, 2.7.6 VC++ 64bit, 2.7.8 64bit, 2.7.8 VC++ 64bit, 2.8.2 64bit 241212.

All versions from 2.7.6 and down have the default 1:2 zoom, which is really nice because the app doesn't suddenly enlarge, covering the folder I was working from.

All versions from 2.7.8 and up have the default 1:1 zoom, which is frustrating since I have to stop adding videos to resize the window out of my way.  I don't know why anyone would want to have an app suddenly balloon out to cover everything on the screen, and with no option to stop it.

I used the same video, same pc, same monitor.  The only difference is the versions, so the OP is perfectly correct.

Why it hasn't been fixed in 6 years is puzzling.  Maybe it doesn't do that in linux?

I'd love to find a way to fix that.  I searched the program folders and registry but can't find anything relating to zoom.  I even tried switching the exe's from the 2.7.6 and 2.7.8 folders, but lots of errors were generated.

It seems like an easy fix would be to simply use 2.7.6, but unfortunately every version under 2.7.8 will not append H264 videos in copy mode without the resultant video being garbled even if the extradata is exactly the same.

Example:  I encode AVI1 with H264 2-pass.  I encode AVI2 with H264 2-pass.  I then join the videos in copy mode.  Result is garbled in versions less than 2.7.8, but not in 2.7.8 or greater.

Something big changed from version 2.7.6 to 2.7.8 that fixed the problem of joining videos but introduced the zoom problem.

Quote from: Elstar` on February 23, 2025, 12:17:08 AMRemember to turn off mbtree (Advanced RC -> Macroblock-tree Rate Control) and psy_rd (Analysis -> Psychovisual Rate, Trellis = 0,00), else you will see much more blurred video in output.

Yes, but inactive by default unless you enable the Use Advanced Cofiguration checkbox.

Quote from: sark on February 21, 2025, 04:21:36 PMIf you select AVC(x264) in the Video Output list, and then in the Configure settings, set the slider to 18, you should produce output that is indistinguishable from the original.

Remember to turn off mbtree (Advanced RC -> Macroblock-tree Rate Control) and psy_rd (Analysis -> Psychovisual Rate, Trellis = 0,00), else you will see much more blurred video in output.

Ok, I'll wait for news.
It will be useful to be able to open and cut long DVR recordings in Avidemux.
Thank you very much!

Got the samples, thank you. The segfault is fixed in code, will contemplate our options regarding support for video codecs beyond MPEG-2 in MPEG-PS.

Yes, CleanTalk external antispam service is a disaster, topped only by not using it.

Moved to the main forum as the issues are presumably not Windows-specific.

Quote from: DinoAB on February 22, 2025, 12:37:49 AMI would like to convert convert a folder of VOB files to MPG

VOBs are MPG (with a different filename extension).

Quote from: DinoAB on February 22, 2025, 12:37:49 AMWhen there are multiple VOB files in the folder for the analog video (8 mm family movies) that I digitized.

Would you please attach the textual output of MediaInfo application for such a VOB file which you are able to play e.g. in VLC to your reply? Don't try to post it inline as CleanTalk might block the post then.

I tried again, I get same message:

An error has occurred
CleanTalk: *** Forbidden. HTTP links blacklisted. Message seems to be spam. Anti-Spam by CleanTalk. ***
It seems that the forum has not been repaired yet, a bot named CleanTalk interferes with my messages and disturb them.

Here is the ID on WeTransfer:
t-P1OIYSoWES

Thank you.