avs 2.7pre2 woo hoo

Lots of fixes for issues described in the last post, and other stuff:

• made config change detection a little more accurate
• made superscope/dmove/shift/etc reinit on edit work right (Now variables are cleared on edit, always, but the init code is run too)
• made trans / movement only replace usereval with preseteval if editted
• fixed trans / movement backwards compatible stuff (no crashy at least)
• updated eval documentation stuff, need people to write docs for it, too.. heheh (see the help then send me the docs)
• lots of ui cleanups (more edit room!)
• fixed some fullscreen new fbresize bugs
• updated fullscreen overlay mode some

-J

*DROOL*

Mmm... a lot of room in sscs...
This is getting better and better...
*me hands more beer to Justin*

Could you add the beat value to the extended APE sdk too? It's currently passed by value, making a clean Custom BPM II impossible (well I have managed to get around this by declaring ->render(...) as naked and writing into the calling function's stack in the epilog code, but it's an ugly hack to say the least).

cool, i like this,

about the mini-tuts in the helpfile, ask atero to use the docs & stuff from avs primer1.75

I got only one request:

Really useful would be self definable global varjables... to use something like regrx (rotation x) otherways the code will get really messy :P

Originally posted by Jack the king
I got only one request:

Really useful would be self definable global varjables... to use something like regrx (rotation x) otherways the code will get really messy :P

Well, I'd suggest you just use globals sparingly.

The main reason I have against self definable global variables, is
scope. Once a preset creates a global variable, does that mean it is there forever? Do we have a limited number of globals? How do you handle these things?

-Justin

Originally posted by UnConeD
Could you add the beat value to the extended APE sdk too? It's currently passed by value, making a clean Custom BPM II impossible (well I have managed to get around this by declaring ->render(...) as naked and writing into the calling function's stack in the epilog code, but it's an ugly hack to say the least).

Actually there is already a way to do this.
In your render() function, you can return one of the two values (actually you can just set those bits in the return value):

#define SET_BEAT 0x10000000
#define CLR_BEAT 0x20000000

SET_BEAT changes the beat status to "beat", CLR_BEAT clears it to
"no beat" 🙂

-Justin

Just updated the zip, with a fix to the dynamic distance modifier (it would at certain resolutions at certain times cause a crash). Woot.

-J

no, you can't make me 1337 by packaging the primer with wa5, i won't allow it! YOU'LL NEVER CATCH ME ALIVE! NEVAR!11

😁

if i get some time next weekend I'll update teh primer...



(and next time could you update teh old thread? kinda pointless to make a new one...)

/me hides from the administrative powers of teh j

Originally posted by Atero
no, you can't make me 1337 by packaging the primer with wa5, i won't allow it! YOU'LL NEVER CATCH ME ALIVE! NEVAR!11

😁

if i get some time next weekend I'll update teh primer...



(and next time could you update teh old thread? kinda pointless to make a new one...)

/me hides from the administrative powers of teh j

Hehe if you want to make a trimmed down version of each section,
to put in there, that'd be rad. You could put links to the full primer in there, too, I suppose.

Or if you don't want to, maybe I could edit it? Or if you don't
want that, I'll be sad. 🙁

-J

again, really nice 🙂 but, as if you haven't heard this yet, please get rid of the window snapping. i know it'll be gone when wa5 is released, but... well i really hate it.

thanks btw 🙂

Why can't you just package the full thing with it? It's not like you have to put each file in the config dialogue. Just put a help menu up there and make one of the options "Help on [currently selected component]" or something.
And since I know jack diddly about windows help files you'll have to do it yourself 😛

I'm very, very very pished but i must comment./ must must must comment, so much backsapacing alreadfy. ah tho shell with it. JUsdtinh, you pwn teh.. uhh place. just is teh pqwnage, ja that will do. Now i must return tpo my lair and perform certain deeds involving females and some sort of booze.... god damn readin through this is like agrammmatical nightmare of sme sort, involving the simpsonms and principal skinner amd his thing, erm, shuit#

anyway, JYSRTIUN IS TEH PWMAGE,

omg. how much did you drink anyway?



on second thought i don't think i want to know. just...stay in bed...and don't break anything....

You think that was bad - look at his thread in the Recycle Bin(the new forum on these forums).

It makes even less since.

Those 'ol superscope examples dont load until you edit the boxes...

Nice new help 🙂.

btw, is the fact that the recycling bin forum is listed in the vis category meant to be some sniggered remark towards us visjunkies?

it's not in the vis group.

It's not in any group. They just get thrown down to the end.

If you notice - there is a slight difference - there is some gray space to the left of the AVS forums and such, but white space to the left of the recycle bin.

hehe this is awesome😁

Originally posted by justin
Well, I'd suggest you just use globals sparingly.

The main reason I have against self definable global variables, is
scope. Once a preset creates a global variable, does that mean it is there forever? Do we have a limited number of globals? How do you handle these things?

-Justin

Oh well... all is true
Seems we just must start using // and /* */
🙁

I love the round up/round down function with blur 🙂

[edit]
Is it possible to make the Color modifier work with coords? To make things like "red=if(above(x,0),1,0);" (for example) possible? Shouldn't be to hard, it works in Superscopes, I bet it can work this way as well.

Hope you can find some time to do this.
[/edit]

[edit2]
Beat detection doesn't seem to work correctly over here with Color Modifier, though I'm not sure yet how to use it correctly. Maybe somebody could post a simple preset which uses color modifier with Beat Detection?
[/edit2]

[edit3]
Never mind edit 2, I think I got it now. Sorry for the inconvience
[/edit3]

I was also wondering why color modifier doesn't have the ability to use x and y. I think that could make things really cool. Would make it pretty easy to make some nice morphing alpha-blended channels. Fun.

there is probably 4 or 5 posts scattered around the forums at the moment which explain why the color mod cant use coords.

And there is a preset here using color mod and beat detection:


[edit]
i fealt rude saying that...so.. this thread http://forums.winamp.com/showthread....hreadid=149042 explains the color mod pretty well. the bottom line is, it doesnt work witht he individual pixels when recoloring, it just uses a color-map-like method.
[/edit]

thanks sidd. That thread must have slipped passed me, as a lot has these last couple of days.

i think the new avs version should have some often used dynamic movements in a preset list (similiar to movement). most people here might disagree, but think of the non-techies too! i'm particularly thinking of basic DMs, like rotation, zooms etc.

this would allow newbies to have some more variety (and maybe stop using water/rotoblitter/mirror combinations only).

Or the ability to add custom DMs/SSCs to the list (to make it easier to add the 3D conversion template).

Or just add a funtion to roto blitter to move on the x and y axis.

Globals, 256 vars, subdirs, color modifier - im getting so horny

And it would be possible to make a coloring tool using x,y,d,r just relpace alpha blend whith red,green and blue channels

Originally posted by siddhartha_one
there is probably 4 or 5 posts scattered around the forums at the moment which explain why the color mod cant use coords.

And there is a preset here using color mod and beat detection:

New Dynamics Rock! - Winamp & Shoutcast Forums

http://forums.winamp.com/showthread.php?s=&threadid=149154

Share your AVS Presets with the rest of the community... They'll love you for it.

[edit]
i fealt rude saying that...so.. this thread http://forums.winamp.com/showthread....hreadid=149042 explains the color mod pretty well. the bottom line is, it doesnt work witht he individual pixels when recoloring, it just uses a color-map-like method.
[/edit]

Somehow i dont think so... it wouöd be same as dm with rgb and THAT would be slow as hell

So Justin...
Are you going to force me to use wa2.9x or the other wa3 half-breeds or are you going to make this new AVS version compatible with the old&true wa2 versions? (like 2.81, which i happen to like&use and wouldn't change for anything)

Tugg I think it works with w8.1 already (at least it does for me).

Justin could you give ColorMod a recalculate on beat thing.
That could make some stuff faster IMHO?