Windows installer "bug"

[TCmullet]

I don't often upgrade, but realized it's been over a year since I did so.  My version has been 2.7.1.  I see that you're up to 2.7.8.  I downloaded and ran the Win 64 installer.  But Avidemux still says it's on 2.7.1.   Was there something else I needed to do to use the new version?  I've never had to before. (At least not that I can remember.)

[eumagga0x2a]

I see that you're up to 2.7.8

It is the last release, very much outdated. Please use the latest (or better, the next to be uploaded) 2.8.0 nightly.

I downloaded and ran the Win 64 installer.  But Avidemux still says it's on 2.7.1.  Was there something else I needed to do to use the new version?

There are VC++ ("vcWin64") and MinGW ("win64") builds. They can coexist, but should never share the same install directory. Make sure you run the right version, the installer of VC++ builds doesn't create the shortcut on desktop (it does create a folder in the start menu).

[TCmullet]

You got me confused on several fronts.  But you gave me enough of a clue to go forward.  I DO have it installed now.  Please let me explain the confusion.

> It is the last release, very much outdated.

Yes, 2.7.8 is the last release, but it's not outdated as it's the MOST recent release.  2.7.1 is the one very much outdated.  I do not use "nightly builds" as they are rapidly out of date.  I only use official released versions.

My problem was that I paid attention to the wording of the download page, which says "Avidemux 64-bit Windows Installer".  That says to me that if I download and run that executable file, 64-bit Avidemux for Windows will be installed.  Since 2.7.1, I actually did run this for 2.7.3, 2.7.5 and 2.7.6 but apparently I didn't bother to look to see that the version had changed.  (Obviously, it hadn't.)  But now I learn that all that does is install the VC++ runtime package needed to run Avidemux.

Today is the first hint that I also need to download the "mingw" installer, too.  Once I did that (just now), then I now DO have 2.7.8 installed.

The confusion could have been avoided if you had named the runtime installer properly.  "VC++ Runtime 64-bit Windows installer" instead of "Avidemux 64-bit Windows installer".

If I ever noticed the "mingw" item in the past, I would have concluded that "That's an extra utility of some sort.  I only want the core program".  Whatever "min gw" is, it could have been expanded to indicate that THIS is the Avidemux program.

I hope my words are clear enough so I don't have to make screen shots to get my points across.

Though I may sound negative, I do want you all to know that I greatly appreciate this marvelous tool, both past versions and the current one, which obviously is the best so far.

[eumagga0x2a]

I'm sorry, but you got it really wrong. The VC++ version is not a runtime for anything, it is a completely different Avidemux build type. Both the NSIS installer for MinGW builds and QtIFW installer for VC++ builds install 64-bit Avidemux for Windows, just different types of the same application. MinGW (gcc) and VC++ (Microsoft Visual Studio C++) are totally different compilers which both read the source code and output (different, incompatible)  64-bit binaries capable to run on Windows.

Yes, 2.7.8 is the last release, but it's not outdated as it's the MOST recent release.

Yes, it is currently the last one. No, it is terribly outdated. The next one is a few days away, almost identical with currently the latest 2.8.0 nightly from Nov. 20 (there will be a few important fixes to the MpegTS demuxer, a small fix for the Matroska demuxer and a zoom level indicator, not yet present in that nightly).

I do not use "nightly builds" as they are rapidly out of date.

So is the official release. Please see release builds as snapshots, just a little bit more polished than ordinary nightlies but without the fixes added to more recent nightlies.

[TCmullet]

Then please explain why for last couple years when I run "Avidemux 64-bit Windows Installer" for the various releases since 2.7.1, it does NOT install Avidemux. If it had, it would have overlaid my 2.7.1.  But my 2.7.1 continued untouched until today when I also ran the minGW file.

[butterw]

There are 2 different builds (with default install folders), it seems you had installed the mingw version rather than VC.

I run a portable install in its own folder by renaming the exe to avidemux_portable.exe.