RE: GF 3.1 Beta Testing

[JayPro]

I Hear tell via a fellow poster that this is already going on.

Is this for Windows users only, coz I haven't gotten any beta-tester alerts via e mail?

Thanks.

EDIT: Or are we both confusing this with v3.0.1?

[Rovastar]

I got mine of September the 5th.

It works well and seems speedier. Although this is hard to tell on quick PCs anyway.

It is version 3.1

=================
G-Force 3.1d3 beta
==================
You are receiving this email b/c you have been placed on the G-Force 3.1
beta testing list. I'll send email to this list whenever there's a new
beta posted.

If you proceed to the download purchased products page at soundspectrum.com,
you'll see an addition item available for download (G-Force 3.1 beta). If
you don't see it, please let me know asap and I'll fix it. Mac OS users
won't see a 3.1 beta until a couple weeks (see below notes).


Notes:

- The G-Force toolbar for Mac OS X will be released in 3.1 but it won't be
ready for testing until a couple weeks from now (so, mac users, be patient
and look for it then--it's going to be really sharp!!). I can't wait until
the mac testers get a first look at it!

- The version history in the beta download as well as the version history on
the site contains what's new in 3.1.

- I've gotten a pile of config submissions in the last several weeks, and I
have not yet added them to the 3.1 beta build -- we'll see them in following
beta releases.

- As always, please submit Dr. Watson crash logs (or Mac OS X crash reports)
if a crash occurs. See the following for instructions:

http://forums.soundspectrum.com/viewtopic.php?t=599

Now that VectorC has completely replaced all the computational guts in place
since G-Force 1.0, there'll probably be some kinks that come up. The issues
will appear as a crash or as a WaveShape, FlowField, or ColorMap not
behaving/drawing properly. Please keep a sharp lookout for any indications
that something may not be computed properly.

- Config authors: VectorC offers a pile of new built-in functions and this
is our chance to add any remaining ones that would make sense. At the
bottom of this email, I've appended a list of all the VectorC built-in one
and two argument functions (excuse the look of them--I just pasted them from
a header file). Please go through them and then think about some functions
that would be nice to also have. For example, way back Rovastar and I
agreed on the importance of having atan2( x, y ), so that was one of the
first functions I added.


So, please download the 3.1 there and start beating on it and I look forward
to hearing any feedback you have. In general, most of the new things in 3.1
are performance and stability related.

Meanwhile, we should see a mac beta in not too long (with the toolbar) as
well as WhiteCap 5 for both platforms.

Thanks,
Andy








// 1 - Unary, element-wise, ii,ff
VC_OP_ABS = 0x10,
VC_OP_SQR = 0x11,
VC_OP_CUBE = 0x12,
VC_OP_POS = 0x14,
VC_OP_SIGN = 0x15,
VC_OP_SQ_WAVE = 0x16,
VC_OP_NEGATE = 0x17,
VC_OP_TRANSPOSE = 0x18,
VC_OP_INVERT = 0x19,
VC_OP_SRAND = 0x1A,


// 2 - Unary, element-wise, ff
VC_OP_SIN = 0x1D,
VC_OP_COS = 0x1E,
VC_OP_TAN = 0x1F,
VC_OP_ASIN = 0x20,
VC_OP_ACOS = 0x21,
VC_OP_ATAN = 0x22,
VC_OP_LN = 0x23,
VC_OP_EXP = 0x24,
VC_OP_TRI_WAVE = 0x25,
VC_OP_WRAP = 0x26,
VC_OP_TRUNC = 0x27,
VC_OP_FLOOR = 0x28,
VC_OP_ROUND = 0x29,
VC_OP_CLAMP = 0x2A,
VC_OP_FLIP = 0x2B,


// 3 - Unary, element-wise, f*
VC_OP_CONV_TO_FLOAT = 0x32,

// 4 - Unary, element-wise, fi, ff
VC_OP_RND = 0x34,
VC_OP_LOG10 = 0x35,
VC_OP_SQRT = 0x36,

// 5 - Unary, element-wise, i*
VC_OP_CONV_TO_INT = 0x38,

// 6 - Unary, element-wise, if,ii
VC_OP_LOGICAL_NOT = 0x3A,
VC_OP_BITWISE_NOT = 0x3B,



// 1 - Binary, element-wise, communitive, iii,fff
VC_OP_ADD = 0x40,
VC_OP_MULTIPLY = 0x41,
VC_OP_DOT_PRODUCT = 0x42,
VC_OP_MIN = 0x43,
VC_OP_MAX = 0x44,
VC_OP_HYPOT = 0x45,
VC_OP_HYPOTSQR = 0x46,
VC_OP_DIM = 0x47,

// 2 - Binary, element-wise, communitive, iii,iff
VC_OP_LOGICAL_NOT_EQUAL = 0x48,
VC_OP_LOGICAL_EQUAL = 0x49,


// 3 - Binary, element-wise, communitive, iii
VC_OP_BITWISE_AND = 0x4A,
VC_OP_BITWISE_OR = 0x4B,
VC_OP_BITWISE_XOR = 0x4C,
VC_OP_LOGICAL_AND = 0x4D,
VC_OP_LOGICAL_OR = 0x4E,


// 4 - Binary, element-wise, non-communitive, iii,fff
VC_OP_SUBTRACT = 0x50,
VC_OP_DIVIDE = 0x52,
VC_OP_MODULO = 0x54,

// 6 - Binary, element-wise, non-communitive, iii,iff
VC_OP_LOGICAL_LT = 0x5B,
VC_OP_LOGICAL_LTOET = 0x5D,

// 7 - Binary, element-wise, non-communitive, iii
VC_OP_SHIFT_LEFT = 0x60,
VC_OP_SHIFT_RIGHT = 0x62,

// 8 - Binary, element-wise, non-communitive, fii,fff
VC_OP_ATAN2 = 0x66,
VC_OP_X_TO_Y = 0x68,

// 9 - Binary, element-wise, non-communitive, fff
VC_OP_HYPOTLEG = 0x6C,
==============================

[Rovastar]

I was just about to check if there was a new versions for Mac users and it is not expecting my license key on the download page. :/

So maybe something is broken.

[JayPro]

Thanks for the info; I suppose I'll hafta be patient for a little bit longer.

Would you mind terribly if you could shoot me an e-mail containing that list of functions he added?
I'd just like to take a gander at them so I can see what's in store.

Thanks.

EDIT: Oops. Apparently that list in your last post. Never mind.

So does this mean that the basic GF language will remain as is, only with the additions of the funcs aforementioned?

[Orbstah]

well andy said the mac version 3.1 will be available on the download page soon for beta testing so keep your eyes peeled Jaypro. think i got that mail to purely coz last year i was on pc beta testing. But now i am full time Mac again, aaaaaahhh blisss

[JayPro]

Orb;

Just to veer off-topic for a millisecond:

I got your note; and things should be on their way towards being dealt with.

PS From 1 Macster to Another: Welcome Home, m8. Welcome Home.

[Orbstah]

amen to that, dont let me wander off again like that

cheers for the other thing too, its just something that really annoys me

[chkman]

Please go through them and then think about some functions
that would be nice to also have

How about all the logical functions? I've been wanting a < function that would return 0 or 1....

[Linvincible]

Hi guys,

with that 3.1 beta, have you noticed any difference in the handling of B variables?

cause, on 2 of my configs, they look to be calculated "more often"

I use a B var to control either the pen thickness or wave translation, proportionally to sound level.
in the first case where I used it to set the pen's thickness, different portions of the wave are drown in different thickness
in the second one where I used it for a displacement of the whole wave, different portions of the wave are displaced differently instead of the full thing beeing simply translated

It didn't do that with 3.0, it's like B var in 3.1 are behaving like C var did in 3.0


here is one of the configs to see what I mean
it's a scrolling vertical bar, speed of the bar is proportionnal to sound level
in 3.0 it stays a bar
but in 3.1 it becomes a wave...

Aspc=0,
ConB=1,


A0="0"
B0="abs(mag(s))"
B1="A0*B1"
B2="0"


X0="B2"
Y0="2*s-1"

Pen="fft(s)^.5+.05*B0"

LWdt="5+100*B0",

B1="B1+.005"
B1="B1-trnc(B1)+B0/12"
B2="2*B1-1"
A0="1"

Meta="reactive=5, detail=5, density=5, morphable=3",

Vers=260

[chkman]

Yes, a problem with calculating variables (in my case C vars) under the 3.1 beta when the variable references itself. I believe the problem is in your line:
B1="A0*B1"
B1 is refering to itself in the assignment. I believe that B1 is zero as it is being mulitplied by A0 which results in B1 being assigned a zero.

The problem is in my colormaps where I am incrementing a variable for each color in the palette. The colors should become brighter as the palette approaches the 'pen' but they remain zero except where I have other factors like sin(t) etc.

The new 'vector engine' does things differently than before. Andy said he could fix the problem but I haven't heard from him for two weeks now. I am thinking that it must be a lot of work to keep the variables alive under the new system. I am hopeful that he can work around it. I do want 10 times faster but I'd hate to lose current configs like your waves and my colormaps. I don't want to be stuck in time with 3.0.

Just have to wait and see for now...

P.S. These lines too:
B1="B1+.005"
B1="B1-trnc(B1)+B0/12"