Trying to compare AVS versions: visbot archive seems messed up

[LigH]

When I developed my Ultra Visualizer (yay, took me several attempts but eventually I got it uploaded there), I found that AVS versions 2.81b and 2.81d don't display the SuperScope renderer which is required for my spectrums and phase display. This may have been a compatibility issue with Windows Vista+ (running Windows 10 here).

AVS version 2.82 works well. Never had any crashes with my preset, I guess the numerous reports were caused by different kinds of presets.

Now I got curious if any newer versions do exist. And this quickly started to confuse me. So there is apparently a version 2.83 in the archive of the visbot network. Which identifies as version 2.2 in internal dialogs. 

Also there are seemingly newer versions like: vis_chavs-2.9.dll / vis_chavsmod-2.9.dll / vis_chavsmod-2.9.1.dll ... which appear to be exact copies of that same 7-zip archive as the one I downloaded as version 2.83. 

For some reason, I guess all the files the visbot archive sends me are the same, actually with vis_avs-2.2.dll inside. In case this is a fault of my webbrowser, and you are able to download the correct files, please share them!

I looked hard for any other sources but only found either dead links or github repos with sources only.

[LigH]

There is a download link for version 2.83 on the MusicBee site (outsourced to MediaFire).

AFAICS it works well too (WACUP 1.99.45.23528 32b + crash fix update; foobar2000 v2.25.7 32b + Shpeck [Winamp vis plugins wrapper] 0.3.7).

[dro]

2.81<letter> builds were the VC6 compiles which can & do have issues after Windows XP but was the last to seemingly render all of the presets in the expected manner.

2.82 was a re-compile using a newer compiler (VS2008 iirc) as part of trying to avoid DEP/NX related issues which was needed for Vista+ to work. It however breaks some presets & couldn't avoid the ape sub plug-ins that it uses from failing.

2.83 was only officially provided with winamp as the localised version of the plug-in & was rolled back to 2.82 since it broke a bunch of presets based on the crap I got at the time about it. That's why winamp ended up installing 2.81d or 2.82 depending on the OS.

chavs was an unrelated update by justin along with my other attempt at a 2.9 at the time he also released a version causing 2 to have the 2.9 moniker.

The versioning in the dlls themselves were often missing or broken depending on how / where / what has hacked at it to create it. So if that 2.83 is even valid is imho potentially questionable as it'd require musicbee stubbing out winamp 5.5+ localisation api.

There's also the attempt by grandchild to make a new contained version of AVS along with merging / re-creating the ape sub plug-ins. Though I've no idea what's going on with that nowadays as when I last looked it couldn't be built with the MSVC compiler & I just don't have the time / interest to screw around with visualisations as it doesn't interest me.

tl;dr: AVS is & has always been a mess & just use the version of the plug-in that works for you.

[LigH]

Thanks DrO. I will make an issue in grandchild's github repo and see if there is any reply. If not, I will just use what works for me.

[LigH]

grandchild found a possible reason for an UI issue which makes the fullscreen settings not remember the previously selected video mode. Might it be a kind of API problem? I tested it only with 3rd party hosts, grandchild said he can't reproduce it with an original Winamp.

[dro]

I don't know as that'd involve having to look at source code that I don't like looking at nor do I remember how well AVS followed the settings location api that winamp 2.9x introduced (via the IPC_GET* SendMessage stuff). I think it does but there's no guarantee if you're using external solutions that they properly implement the support for it. If you're not using wacup for avs then you really need to be trying to ask those providing the host implementation that you're having issues with as me guessing isn't helpful for either of us.