No announcement yet.

AVS fails to work [Trying to fix with v2.91 TEST #1]

  • Filter
  • Time
  • Show
Clear All
new posts

  • AVS fails to work [Trying to fix with v2.91 TEST #1]

    Hi all

    Am trying to use AVS and it fails to work at all. Using windows 7 and latest version of winamp.

    All other visualisations work (milkdrop,geiss etc) yet when I try to use AVS I get a screen that is either very light cyan or a faun colour and no visualisations at all.

    Anyone know if there is a fix for this or is this because of the operating system I am using?


  • #2
    There have been a few reported issues already concerning compatibility with newer Winamp versions and newer Windows versions.
    AVS 2.81d was made in late 2006 and was but a small upgrade of 2.81b, which was made in late 2003/early 2004, about when Winamp 5 was introduced. The sourcecode is very fragile and although it is open sourced today, nobody has been able (yet) to make serious improvement. In a way, it's surprising that there haven't been any issues earlier.

    One of the suggestions that have been posted, is to disable Aero when you're running Winamp.
    Right-click winamp.exe and go to properties. Go to the compatibility tab and check 'Disable desktop composition' or something alike.

    You could read some relevant threads on these forums, and try to mess around yourself. If you get it to work, and also if you don't, please keep us informed of your progress. Others who are reading this benefit from it as well.
    Jesus loves you [yes, you] so much, he even died for you so that you will not need to die, but live forever


    • #3
      thanks will check this and report back asap.


      • #4
        ok have tried this and have also tried using windows xp compatability mode and it starts to crash winamp


        • #5
          winamp 5.6 works best with avs 2.9, but avs 2.9 isn't working as good as 2.81d (and previous incarnations). so you need to downgrade winamp to version 5.5 and use it with avs 2.81 for full compatibility. it stinks, but that's the way you have to go.
          NSIS IDE for Atom | NSIS for Visual Studio Code | NSIS for Sublime Text | NSIS.docset


          • #6
            I have this problem too, but with Windows XP.

            I actually liked in the past the Unconed - Speeder3k.

            This one actually is nice to watch, because its not just some random eye stuff, it is something like a track you drive. This is much better.

            At milkdrop I didnt find such a visualization so far.

            But unfortunately avs doesnt run for me. Same problem here.


            • #7
              You're a genius. I recently upgraded to Windows 7 from XP and then upgraded to the latest version of Winamp (561) and AVS didn't work. I tried various suggestions on other threads (such as lowering the resolution) but they didn't work. Finally I found this thread, uninstalled 561, and then installed 558. Now AVS works!

              Winamp shouldn't release an upgrade if it doesn't work with AVS IMO. Or they should unbundle AVS. It's such an important part of Winamp for me that if AVS doesn't work, I don't want to upgrade.


              • #8
                AVS was reverted to the version everyone kept saying was the one that works which now seems to have been a load of fud from the complainers and hence causes the few Vista / Win7 AVS users immediare crashes again *grr*

                AVS should just be split from the distro and provided separately - and i was shot down for that suggestion even though it's the only way when there's no developement resources to work on a dead plug-in which no one can get working compile (especially since most of the issue is coming from the ape's used by the presets which no one has code for).

                WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog


                • #9
                  i hate to admit it, but i agree that splitting avs from winamp would be the best solution (this will be the end of avs, but still it makes more sense than shipping a broken product!) so i was wondering under what terms the dll can be distributed. (i'm not sure if the same conditions as for the source apply)
                  NSIS IDE for Atom | NSIS for Visual Studio Code | NSIS for Sublime Text | NSIS.docset


                  • #10
                    so since it's all screwed up with all of the versions floating about, the following is going to happen and then i need input on what will happen after that...

                    rather than just shipping 2.81d and it not working on Vista and higher, we're going to include 2.82 in the installer and install 2.82 on Vista and higher (as it's DEP friendlier and less prone to crashing - ignoring the preset display issues, etc) and install 2.81d on XP and before (where that version seems to behave better).

                    that is to alleviate the posts about it just not working (something is better than nothing).


                    and so for the future, i now have a local build of chavs 2.9 which i've been flipping through presets to get it to crash and then trying to fix those crashes there and then (i'm doing this all on Win7 x64 so the fact it runs at all is welcome).

                    after re-reading everything, is it even worth me trying to sort out a 2.91 based on chavs (which sadly is based on the 2.81b source code) or just put this to bed and forget about it ? i'm willing to put in the time (if only to get it to a point were we don't get crash reports about it continually) but is this something that will help (and yes i know people don't care much now) ?

                    from what i can see, the main things that aren't right with the chavs base are:
                    • still randomly crashes (have seen it and fixed 2 issues so far)
                    • issues with rand(..) as per
                    • people don't like the ui / want it changed to one of the typically used mods (if so which one ?)
                    • version resource is messed up
                    • not doing presets correctly compared to 2.8x ? (not sure what can be done about that)
                      main example is "convolution.ape" which is incompatible with Vista an up - blocking loading of it for the time being so it gives a UI indicator in the preset editor instead of bombing out, etc
                    • fullscreen mode won't hold without using compatibility mode
                    • overlay mode just shows a solid colour instead of the preset
                    • anything else??

                    as issues are deemed 'resolved' i'll strike them through, as well as adding anything new (assuming anyone cares and reports anything).

                    WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog


                    • #11
                      In case anyone is looking for the chavs source:
             -- git clone WDL from too, it has the latest EEL (which chavs needs).

                      The convolution filter doesn't work in chavs (but I guess that falls under "not doing presets correctly"?)

                      A unified working version of AVS that works nicely with modern OSes and Winamp versions can't be a bad thing.
                      I'm a fan of the improvements chavs brings, and as it seems that Justin hasn't worked on chavs since his initial chavs post, fixing the bugs in it may get a couple more people to try out the improved syntax.

                      But whatever happens, presets that use the GVM APE will still cause crashes. (I assume)


                      • #12
                        i'd really need examples or something specific to know what to look at / attempt to fix as i've no idea what the expected behaviour of the convolution filter or what uses the gvm ape to target testing / fixes for it.

                        WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog


                        • #13
                          First off, thank you very much for still wanting to fix this beast. I mean it.

                          The convolution filter is like a custom blur filter. It works per pixel and can copy that pixel to (or remove from) the surrounding pixels.

                          The GVM is a variable manager. I added example presets for both effects. The GVM has a help window if you hit the [?] in the bottom right of the window. I remember that Jheriko lost the sourcecode for it, but I'm confident he'll help you if you have specific questions.
                          Attached Files
                          Jesus loves you [yes, you] so much, he even died for you so that you will not need to die, but live forever


                          • #14
                            well from what i've seen (haven't tried with the examples) is GVM only crashed when there was a preset transition due to an issue in HeapFree(..) (so some form of memory freeing issue which could be just down to AVS built with a different compiler and abi differences).

                            i've still to try it out but some extra exception handling in AVS during that phase should help resolve the crash issue.

                            my main thing from friday night and a few hours today) has been looking into not being able to use AVS in full-screen or overlay modes and if anything, it's looking like trying to move over to use Direct3D instead of DirectDraw to be able to do what's needed (seeing as the DirectDraw interface has been legacy since Vista).

                            alas i need to read up on that as it's not a simple change from what i've taken in so far (and i could probably do something with re-using Milkdrop's code but that's one heck of a beast to combine into AVS when i don't think most of it's functionality is needed (i.e. just need enough to get the generated frames onto the screen - i believe a Direct3D Surface may be what's needed since we've using DirectDraw Surfaces already).

                            WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog


                            • #15
                              ok, just tried the GVM example from above and with 2.82 (2.81d or 2.83 won't run for me on my dev machine) and i get a reasonably consistent crash when transitioning away from the preset.

                              using my build with some extra exception handling on where the crash appears to be triggered, the GVM error still happens but AVS keeps going (i just get the odd 'beep' due to how i'm testing for it when forcing it to go through all of the presets quickly).

                              and just had a look at the other ones and #3 shows the issue the best i think (moving blob which should have blurred edges - when comparing 2.82 vs 2.81d on XP) .

                              so the convolution filter comes from convolution.ape i assume?

                              WACUP Project <‖> "Winamp Ramblings" - Indie Winamp Dev Blog