justin
26th November 2003 23:36 UTC
2.8 alpha 2 :)
http://firehose.net/~deadbeef/avs28alpha2.zip
added eval code for effect lists (heh had to do a big hack to fix the broken
structure of effect list configs)..
also added new text formatting stuff, like $(title), $(reg00), $(playpos), etc.
also fixed the alpha clamping bug in dmove (I think) :)
I'm gonna take a look at having presets be able to disable most of the keyboard action forwarding to winamp/etc... so a game preset could request that the keyboard stuff be ignored... anyway =)
-Justin
Shock Value
26th November 2003 23:43 UTC
Effect list coding... I was JUST thinking about how this would be useful! Very nice. This makes something I'm working on much better looking and faster. I'll have to check out the text formatting stuff too.
EDIT: That text formatting is nice, but unfortunately the text component itself is kind of hard to use. Setting a position and size is difficult across different resolutions, and besides the text itself, nothing is dynamic. Texer II-like functionality, except with text, would be awesome, but I have no idea how hard this would be to implement. It's just that I don't see myself using the text component much due to these problems. Great work though. AVS is getting so much better with each new release.
Yathosho
27th November 2003 01:09 UTC
Re: 2.8 alpha 2 :)
Originally posted by justin
also added new text formatting stuff, like $(title), $(reg00), $(playpos), etc.
S-uper_T-oast
27th November 2003 01:40 UTC
All i can say is, JUMPING JEEHOZAFET YEAH! Justin you are my god.
[Ishan]
27th November 2003 03:08 UTC
oh man ! i'm gonna faint :weird: Hail Justin!:D
Jaak
27th November 2003 05:30 UTC
:(
All this is very nice, but still no vectors, no arrays...
bohoo...
:p:D
UnConeD
27th November 2003 05:52 UTC
It's not that simple Jaak ;).
[Ishan]
27th November 2003 06:09 UTC
whats the $(playpos) in the text formatiing??
sidd
27th November 2003 06:09 UTC
Woow, impressive.
New line character in text would be nice.
Also, how about the trackpos and tracklen available as numerical values in the standard evallib. That way we could make purty slide bars and things with superscope. :)
Tuggummi
27th November 2003 06:11 UTC
Thanks Justin :)
Magic.X
27th November 2003 07:10 UTC
!
OMFG THIS IS SO COOL!!!
I took a look at the new effect lists and found out that values for enabled are not stored permantently.
To code a simple onbeat on/off switch, the following code should be sufficient:
FRAME:
enabled=if(beat,bnot(enabled),enabled);
Instead i had to code the following to make it work:
INIT:
e=enabled;
FRAME:
e=if(beat,bnot(e),e);
enabled=e;
It seems as if enabled was reinitialized from the checkbox each frame.
And could you please use b instead of beat? I've gotten used to b (which is still missing in normal movements) and having two diffrent expressions will confuse the hell out of newbies.
:)
skupers
27th November 2003 07:11 UTC
I can hardly keep up with all those new features. It'll take months before we've seen what all these features are capable of. And I would like to thank you for this. :)
UnConeD
27th November 2003 07:17 UTC
MagicX: normal movements are *static*. They don't use onbeat. By the way, overriding by UI-settable options has always been the standard (e.g. red/green/blue in scope).
Tuggummi
27th November 2003 07:18 UTC
Magic, nobody uses B ;) Well nobody else anyway :p Why use it when you can just define it yourself? I've never quite understanded it...
Magic.X
27th November 2003 07:21 UTC
Me too!
Some ideas for render/text
I'd like to access
$(artist)
$(album)
$(streamname)
too.
Positioning should be codeable and optional word wrapping should be available.
Yathosho
27th November 2003 08:41 UTC
Quote:
Deamon
27th November 2003 14:27 UTC
omfg sweet :)
[Ishan]
27th November 2003 14:37 UTC
can anyone explain me about $playpos and all?
Yathosho
27th November 2003 15:06 UTC
Originally posted by [Ishan]
can anyone explain me about $playpos and all?
you could've found out yourself by simply putting $(playpos) into the render/text. it displays the play position of the sound file you listen to :)
Shock Value
28th November 2003 00:36 UTC
I don't know if this has been said, but there are issues with getkbmouse(1) and getkbmouse(2) and pixel doubling. When in doubling mode, the mouse x and y values are centered in the upper left quadrant of the window, instead of the center of the window.
horse-fly
28th November 2003 05:00 UTC
Originally posted by S-uper_T-oast
All i can say is, JUMPING JEEHOZAFET YEAH! Justin you are my god.
that was from a satellite tv commercial!!!
btw: those text options will rock my socks
EDIT: what does $(playpos:2) do?
[Ishan]
28th November 2003 13:46 UTC
how silly of me!:)
S-uper_T-oast
28th November 2003 23:50 UTC
Originally posted by Horse-Fly
that was from a satellite tv commercial!!!
That commercial is Hilarious.
$(playpos) gives the current playpos counting up
$(playpos.n) gives the current playpos with n digits after the second spot (miliseconds, decisecond?, etc...)(maximum three)
Don't know about $(playpos
:) though, maybe a typo?
zamuz
29th November 2003 00:01 UTC
keep em coming justin, maybe one of these days i'll actually try using these new features :)
UnConeD
29th November 2003 03:31 UTC
By the way, the parameter that defines the key is not an ASCII code, but a virtual key code. I've attached the list for those who don't have MSDN handy ;).
Deamon
29th November 2003 10:23 UTC
thanks for that one UCD :). This comes in handy.
jheriko
29th November 2003 19:54 UTC
Originally posted by killahbite
i'm wondering if jheriko is (still) working on text ii. that was a completely overworked text renderer supporting multiline text and text-pages (like frames, more advanced than the current ";").
I forgot about that ages ago, might be an idea to go back to it if the final AVS2.8 is lacking more text features.
UnConeD
2nd December 2003 22:17 UTC
By the way, my list shows key values in hexadecimal. You will need to convert them to decimal for use in AVS, e.g. using the Windows calculator.
Originally posted by siddhartha_one New line character in text would be nice. i'm wondering if jheriko is (still) working on text ii. that was a completely overworked text renderer supporting multiline text and text-pages (like frames, more advanced than the current ";"). |