Ive been using 2.7.4 version and find it very stable in XP and Win7. Only one quibble is the auto crop option. I can't test the newer 2.7.6 version as it crashes for me in Win7. I was trying to crop out tiny black bars from a 4.3 ntsc dvd vob and get 6 on the left and 8 on the right. Reset the counter and press autocrop and all kind of figures come up. Play the video, stop and reset, then press autocrop and different numbers again. I've tried with a few inputs DVD etc, and the autocrop throws up inconsistent numbers each time. Is it broken? Apologies if it has been fixed on 2.7.6. Thanks.
Also my vob has two audio streams which is shown in aviDemux audio option menu. Is there any way to select just the first audio track-disable the 2nd one)without having to encode the first e.g to aac and copy the second in every test encode I did? Thanks.
Quote from: xtro on October 11, 2020, 02:37:48 PMI can't test the newer 2.7.6 version as it crashes for me in Win7
Which one? The regular 64-bit one or the legacy? They are significantly different. Have you verified that their md5 checksums match those published on http://fixounet.free.fr/avidemux/download.html? Is there a particular action triggers a crash? If you use "DXVA2" (actually, DirectX) video output, you should switch to the unaccelerated "Qt" to rule out problems with graphics drivers.
If your Windows 7 is 64-bit, please try the latest nightly (preferably both VC++ (https://avidemux.org/nightly/vsWin64) and the MinGW (https://avidemux.org/nightly/win64)).
Quote from: xtro on October 11, 2020, 02:37:48 PMI was trying to crop out tiny black bars from a 4.3 ntsc dvd vob and get 6 on the left and 8 on the right.
I would discourage from using non-standard resolutions, no matter what.
Quote from: xtro on October 11, 2020, 02:37:48 PMReset the counter and press autocrop and all kind of figures come up. Play the video, stop and reset, then press autocrop and different numbers again.
Autocrop evaluates the currently displayed picture only, it doesn't scan the whole movie. If you experience that it cuts away parts of the picture which are not black (or really very dark), then this might be a bug.
If the video has noisy borders like in digitized video tapes, this might interfere with the way autocrop detects black borders. You should use the "blacken border" filter then.
Quote from: xtro on October 11, 2020, 02:37:48 PMApologies if it has been fixed on 2.7.6.
The autocrop feature hasn't been touched since 2.7.1, so definitely not.
Official version from the Avidemux homepage itself: The 32 bit Legacy one 2.7.6 crashes on XP after indexing a file. Installs okay. The 64 bit for Win 7 et al installs fine as above but crashes too after indexing. So I reverted back to 2.7.4 and 2.7.5 for Win 7 and Win10.
Regarding clicking on autocrop. The feature sometimes moves the video around in a small box, leaving background green or screen cut in half. I am manual cropping instead now as it might be graphic driver clash?
Quote from: xtro on October 12, 2020, 09:13:56 AMThe 32 bit Legacy one 2.7.6 crashes on XP after indexing a file. Installs okay. The 64 bit for Win 7 et al installs fine as above but crashes too after indexing.
Did you try as requested with the "Qt" video display instead of "DXVA2" or "OpenGL"?
In Avidemux main window "Edit" --> "Preferences" --> "Display" --> "Video display: [Qt]". 2.7.4/5 are no more supported.
Yes, I did indeed and still got crashes in Win7. I'm going to reformat the hard drive now just in case there are lingering bad sectors on the hard disk and also rule out driver clashes etc. A clean install on a fresh installation might do the trick. Thanks.
This would not explain why 2.7.4/5 works. Is hw accelerated decoding in Avidemux enabled? If yes, please disable. If the latest nightly still crashes, please provide admlog.txt from %localappdata% from such a crash.
Maybe obvious, but nevertheless: never mix different Avidemux builds in one and the same directory and never run multiple Avidemux builds simultaneously.