avs 2.7pre3 yay

OK just want to give you guys the latest build



what's new:

• fixed memory leak in evallib introduced in 2.7pre2
• added seperate debug window with register watch, compilation error listing
• made variable clearing on recompile optional for development
• woo undo/redo system (thanks largely to mig) - not ideal but definately handy
• fixed/upgraded the trans / movement functionality, pretty usable for starting with a particular preset and editting
• added blend modes to misc / buffer save
• made effect lists expanded by default on load
• made y/u nav wrap again 🙂

Going to add Unconed's simpler APEs soon, I think.

Also, for the eval help, will probalby just include a .html (AVS primer stripped down?) and have AVS spawn on demand, perhaps to the right section. Sound good to ppl?

(edit: oh yeah, need to add Ctrl+Z and Ctrl+Y for undo/redo eh)
-Justin

ok, cool, so justin when can we expect a 2.7final ver?

Originally posted by Montana
ok, cool, so justin when can we expect a 2.7final ver?

I guess with Winamp 5, say, mid to late october =)

-Justin

justin can you add a option to just save, because the current save option is a "save as"-option.

Wow, W5 is that close? Awesomeness! ::can't wait::

BTW, just a nitpick: "Preset may have been edited" not editted. 😉

EDIT AGAIN: one more thing, perhaps a fixed-space font (ie. courier) for comments? It'd definitely help with ASCII art/formatting.

Yay. Sounding good.

made effect lists expanded by default on load

And a disable this feature button to go with it? 😉 Im too used to the old way and i think it's pretty confusing if all the effect list's are just spreaded out. (just take my "moon of mana" from bitmapped II and you can see why...)

avs 2.7final with wa5final in late october? I LOVE YOU GUYS! GREAT!

And indeed it would be nice to have a fixed-space font for the comment screen. ASCII pictures are sweet to use in the intro presets of new packs.

I dont like that wa5 comes out so early... 🙁
that means its prolly full of bugs and... even Nullsoft cant make avs rock in so little time... 🙁

hehe thanx justin😁 you pwn.

It seems that WA5 is just WA2 with some extras tacked on. It's supposedly not buggy at all. Hopefully things will be good with it.
I know the new AVS kicks ass.

ndd: needs a seperate rtf comment for backwards compatibility 🙂 otherwise it'd fuxor things like skupers's comments

Justin?!

With this version of avs(pre) I have experienced some very weird crashes this happens allways (with one exeption) when I'm coding a ssc...
I can not say what causes this but I'm sure there is a bug in it (d'uh)...
This crash even sucks more than usual onese :P that give me a chance to save my preset 😔, i must say this REALLY sucks.

If it's needed i can send the preset whan i was/am working on, it has crashed allready 3 times.
If i get more info about those crashes then ill let you know.
Oh, once it crashed when it was loading preset, it cant be varjable limit... prolly it is about global varjables... or maybe not.
help... 🙁

Also, for the eval help, will probalby just include a .html (AVS primer stripped down?) and have AVS spawn on demand, perhaps to the right section. Sound good to ppl?

personaly i think it would be better to add it to 'expression help'... and add a tutorial option...
well, maybe its not that good idea...


Mind my english if its really bad 😛

Originally posted by uNDefineD
one more thing, perhaps a fixed-space font (ie. courier) for comments? It'd definitely help with ASCII art/formatting.

terminal 6pt

*Jawn*
Now i got after few crashes an error
The instruction at "0x77f5b13b" referenced memory at "0x00000014" the memory could not be "read"

🙁

Am I really only who has this problem... or is it about winamp... maybe ill reinstall it... or... 😔

SSC crashes? I had problems with 2.7pre1, the SSC dissapeared, while editing it. Though I have not had any problems with version 2 and 3. Could you please post the avs you were working on, and tell what went wrong exactly, and also when exactly?

ok here we go

2 time when i was pasting and editing those getosc(1/16,0,0)'s
once when i loaded the preset
and i THIIINK it was few time whan i was just coding the point code


it crashed wile loading and few time when editing code...

I think it cant be about global varjable coz the secong ssc doesnt use global varjables :P
i have no idea... maybe it me... :S

I really like the solid grid, though nothing seems to go wrong here. I played around with your code a bit, most of the time fucking it up, though nothing weird like crashes. Also I loaded the presets about 10 times. No crashes at that as well.

Sorry mate, but I think it's just your comp. Bad installation maybe?

i hope so... but i doupt so... but maybe 😁

anyways... tomorrow ill reinstall the wa and dl the avs2.70pre3 again and ill see...
...now i really need sleep.

Originally posted by Atero
ndd: needs a seperate rtf comment for backwards compatibility 🙂 otherwise it'd fuxor things like skupers's comments

Perhaps a switching option would work?

BTW, I haven't been having any problems with 2.7 thus far.

YAY jheriko pack 9 intro works with this version.

Question for justin-
What is the deal with the laser "plugin" we have found lying around in the code?

It's for compatibility with those cool(yet really expensive) lasers that some nice clubs and such have. They can create cool laser shows using it. I don't know if a final version was ever actually released. May be wrong though...

You mean using a laser to project AVS output?! Coooool.

EDIT: Found a bug - when using U and Y to scroll presets, it only scrolls within the selected "random" dir, ie. I was viewing a Jaak preset and it jumped straight to one of mine instead of the next Jaak one, because the random dir was set to uNDefineD.

I also had that with older AVS versions...

Just a minor peeve. Any chance of having double menus or just more added on when needed because scrolling through endless presets is tedious and irritating. Especially when it scrolls as slow as the avs menu does.

i'm amazed

you wait two years for a new version of AVS, and then 3 come along all at once...

good stuff, global variables, evallib... gosh thats going to take me a while to figure out how to program.

i have 2 probablly unreasonable and unpopular requests..,

1) more scratch area or global variables, enough to allow my midi recieving plugin to transmit a whole 16 channels of midi events

2) a way of syncing redraw on windowed or 'overlay' output to stop those horrible horizontal tearing lines...

this isn't 3 versions - it's just one version - these are all prereleases. Make sure you wait until the final version comes out before you start any major development - a lot may change.

1. 100 globals isn't enough??
2. Turn off "resize image" under display.

Don't think this was mentioned before, but entering variables with charector lengths over eight, store the variable using only the first eight charectors. ie: abcdefgh=0; abcdefghi=1; If you would then try to recall abcdefgh, it would return 1, and trying to use abcdefghi would result in your code not working.