AVS acting weird since winamp update

I am still curious why it went wrong. I've compiled avs using .net 2002/2003 before and there weren't any big problems that I can remember... need to try it under 2005 still though. 2005's project conversion is not as good, it fails to convert some of my 2003 projects nicely.. god knows what it might do with a vc6.0 project :P

from what i've seen any compiles other than a msvc6 one never seem to work quite right for avs (random crashes, etc) so i'm pretty much confused by it all, heh

-daz

linesize is broken in the "fixed" version

annoying.

nevermind

my bad

eh? so is it broken or not?

-daz

Broken function

i've discovered that gmegabuf is also broken.
i to prove this i used Grand-Childs text renderer superscope preset and found it to not be working. concluesion gmegabufs.
i hope this helps.

Nanakiwurkz have you read this topic?


(Download vis_avs.dll 2.81d from the link on the thread)

Thanks DrO

NOT broken. It was my mistake.

rightio. i was starting to worry that i'd made a broken build after all of the issues beforehand with the 2.81c build.

the complete zip of altered files is in this for anyone wanting to build avs on their own upto the 2.81d spec

-daz

/me downloads one of Jheriko's preset
/me craps all over Jheriko because it's not working
...weeks later...
/me tests one of his old presets
/me notices a slight inconsistency with previous behaviour
/me investigates further
/me notices that linesize is not working
/me checks AVS version
/me curses at the genius who included a new AVS version without mentioning it in the changelog

who or what is making this and can we shoot them!!!

I have noticed than in 5.32 the avs's are actually more reactive and able to run faster and smoother with less CPU Usage...

I accepted it and went on deleted those which would no long respond, or feel short of full respond...I did have to delete some good ones.. But we had to sacrifice a few things to actually have an improvement possibly..( gets dagger, mask, and cloak..)

In the meantime, you could download The Private Compilation 2006, ( AVS Presets Thread )which will be a folder of 312 avs's that work.. on its way to be published .. may be awhile .. cause of the site having some maintenance things going on.. ( must have hired a new guy with ideas..)LOL

I just now found this thread after trying to solve the ssue and figure out what it was but this .. So now I am going to go have a look-see at this attached file..

lol
you aren't seriously advocating the use of presets whose non-shittiness depends on bugs that are already fixed?

I would say with some political plausible denial.."NO.. and then again most definitely not" but if thats what you make of it then..uhmm..

"GO RIGHT ON AHEAD!"

LMAO

eh, tomy, just to be sure, by now you have downloaded the winamp update pack from the thread linked on the prev. page?

yes i did
until today i wasnt aware of an avs update (to 2.81c) though, because it was not mentioned anywhere but on the forums (which i dont read regularly anymore)
hence me saying that the bugs are already fixed

i just *hope* that the next WA-update comes soon and that the new AVS is not again forgotten, because the average watcher doesn't know about or downloads the update pack i guess [i wouldn't have known about it, hadn't the thread being linked here]

I downloaded the AVS source last night to mess around with it. The source on the download page http://www.nullsoft.com/free/avs/ is not the latest source. There is the zip file on this thread from Dr0 (I didn't see it last night)... but still... it would be nice if it the page was updated

Incidentally I updated it to compile on .net 2005 with no problems... at least that I could find (i.e. not the original problem from this thread). The only changes I had to make were simple, mostly casts to clear up ambiguities, some default parameters removed from function pointers, etc...

I did notice, however, that there are somethings which are quite sensitive to optimisation. e.g. "Whole Program Optimisation" fails, because it puts off generating some things until link, which means that some of the evallib hax don't work. There was something else but I can't remember it now...

Does anyone know if/when the source will be updated?

Originally posted by jheriko ...I did notice, however, that there are somethings which are quite sensitive to optimisation. e.g. "Whole Program Optimisation" fails, because it puts off generating some things until link, which means that some of the evallib hax don't work. There was something else but I can't remember it now...

does that mean there is still space for speed optimization? [because for the things it does, avs is quite fast, imo] or does it just mean there's some awkward programming work in there?

Originally posted by jheriko
Does anyone know if/when the source will be updated?

ni idea since i don't know who has access to the cvs on that/bundle but i'll try to see what can be done. the main issue with non msvc6 compiles is that things can't be optimised as you've pointed out and also it's not a known reliable compile (hence why sticking to building it at least for the moment in an environment which it was designed/created in)

Grandchild: it won't be forgotten since it's already in the internal builds, it was just how the release was pushed before i got a chance to remind the devs to include it - the joys of uk/us time differences and me unfortunately working late on the day of release 🙁 and i'm sure that it'll be added as a comment in the release notes (was an oversight in the other version when 2.81c appeared - the devs/myself are people at the end of the day and it does happen 😉 )

the optimisations jheriko are refering to are build options for speed/size but generally there's little to be noticed even when not running dlls in such a manner without those optimisations from what i've experienced over the years (maybe a few percent if that).

Mattfury: blame me and then blame the nullsoft build machine (since i made a initial build that worked and then was recompiled by nullsoft and then i re-did the build and that's now the one in the pack/next winamp build). still not sure why the nullsoft build failed when that was done with the same project in msvc6 *shrugs*

-daz

Originally posted by DrO
the optimisations jheriko are refering to are build options for speed/size but generally there's little to be noticed even when not running dlls in such a manner without those optimisations from what i've experienced over the years (maybe a few percent if that).
-daz

Don't confuse your ability to write awesomely optimised code from the start with a lack of functionality. If you write sufficiently terrible code they can make a very noticeable change. 🙂

It also depends on the structure of the program. "Whole program optimisation" has a larger impact if your project has hundreds of small seperate files, for instance. Inline expansion only has an effect if you aren't already using inline where appropriate or using classes with inline definitions. etc...

I think I have access to the cvs through sourceforge, I seem to remember accessing it once, but my computer is in shambles atm. It heavily crashes over pretty much anything (AVS, emulated games, screensavers.. they all make it reboot on the spot at random) so it will be a while (i need to get an SATA cable this weekend and reinstall loads of junk) before I bother to check that out..

Just a little reminder... this still hasn't been fixed. 🙁