Which older configs to transfer to 3.1?

[willrob]

I know I can use my own Color maps in the new G-Force, but which of the hundred of Flowfields and waveshaps will work with the new engine? Should they all still work? Will it be trial and error? Obvioulsy items with the same name as the new configs should be discarded. But what about the Extras on the web page?

And still no Mac tool Bar....sigh.

And no way to use Themes, the folder for which now has contents.

[JayPro]

I'm just beginning to run thru my unbundled-in-3.1 effects; and there's no telling how many of them aren't gonna work unless I spend hours on end plodding thru each one.

Yes, vectorC engine does it's job rather nicely in telling me something like "(float) expected" or "invalid token" (???) when I come to a "defective" waveshape; but as I mentioned before in another post, this gives me exactly zero indication as to how to rectify the problem via the new code.

(EDIT:And it particularly doesn't help when I'm getting effects that still don't look the way I know they should, even if no error text shows at all. )

I spent half a decade---i.e. as long as this app's been in existence---authoring (read: winging it with) dozens of configs, and only now does this math-challenged moderator get an inkling of what "fcn" does what.

But now, as much as I truly appreciate GF's newest quantum leap, it's almost as if it were midyear-2000 again.

Surely there'll be a resolution to this (meaning most likely that I'll hafta either A. bite the bullet and [OMG] actually learn the updated code or B. chuck alot of my babies out with their bathwater).

But till then, I'll just hafta spend some time separating sheep from goats.

[willrob]

From my experience so far it appears that only Waveshapes are causing errors. At least it appears that way: in verbose mode I get an error message only when the waveshape is changed. So far the flowfields and colormaps seem ok.

The new engine is much faster at switching flowfield (via the keyboard s key). Where my dual G4 used to pause, it now switches quickly to the next ff.

One irritating new "feature" is the continual reappearance of the G-Force splash screen whenever I return to the visualizer. In previous versions, when one first launched (in iTunes) G-Force, its splash and copyright info would appear. But if you stopped and returned to your song list to hunt for a title and then restarted the visualizer, the splash screen didn't reappear. Now it seems to be there every time I go back and forth. If I quit iTunes and relaunch I would expect it to be there, but not once it's launched.

[Rovastar]

Are any of the probelm configs have the following commands in

Depreciated

sgn(x) use sign(x)
atan2(x) use atan2(y,x)
flor(x) use floor(x)
trnc(x) use trunc(x)
clip(x) use clamp(x)
seed(x) use srand(x)

[andy55]

Yes, vectorC engine does it's job rather nicely in telling me something like "(float) expected" or "invalid token" (???) when I come to a "defective" waveshape; but as I mentioned before in another post, this gives me exactly zero indication as to how to rectify the problem via the new code.

In general, all of those errors were there before, it's just that the previous engine was silent (and typically set things to zero where applicable). So, in other words, the problems/errors in your past configs have been there the whole time. Common things to check for are unbalanced parens, typos, and invalid commenting. Im many submissions, I notice that people just freely type into a config. Keep in mind all comments need to be proceeded by a "//" or be enclosed by "/*" and "*/".

It definitely stinks that people with their configs have to go through and correct stuff, but there's not much I can do if it wasn't right/valid to begin with. And as for WaveShapes that just look "different" (without any errors listed), please send them to me.

andy

[andy55]

One irritating new "feature" is the continual reappearance of the G-Force splash screen whenever I return to the visualizer. In previous versions, when one first launched (in iTunes) G-Force, its splash and copyright info would appear. But if you stopped and returned to your song list to hunt for a title and then restarted the visualizer, the splash screen didn't reappear. Now it seems to be there every time I go back and forth. If I quit iTunes and relaunch I would expect it to be there, but not once it's launched.

It's a tough situation: In prior versions, all the resources would be tied up until you decided to quit iTunes. Another issue was that w/ the toolbar--unless the GF instance is destroyed, the toolbar basiclally is controlling something that isn't visible, which can be confusing to the user. I'm open to suggestions--perhaps if we made the delay something longer--like 10 or 15 seconds?

andy

[andy55]

Are any of the probelm configs have the following commands in

Depreciated

sgn(x) use sign(x)
atan2(x) use atan2(y,x)
flor(x) use floor(x)
trnc(x) use trunc(x)
clip(x) use clamp(x)
seed(x) use srand(x)

Only atan2(x) will cause an error -- all the other ones are translated before compilation.

andy

[JayPro]

Yes, vectorC engine does it's job rather nicely in telling me something like "(float) expected" or "invalid token" (???) when I come to a "defective" waveshape; but as I mentioned before in another post, this gives me exactly zero indication as to how to rectify the problem via the new code.

In general, all of those errors were there before, it's just that the previous engine was silent (and typically set things to zero where applicable). So, in other words, the problems/errors in your past configs have been there the whole time. Common things to check for are unbalanced parens, typos, and invalid commenting. Im many submissions, I notice that people just freely type into a config. Keep in mind all comments need to be proceeded by a "//" or be enclosed by "/*" and "*/".

It definitely stinks that people with their configs have to go through and correct stuff, but there's not much I can do if it wasn't right/valid to begin with. And as for WaveShapes that just look "different" (without any errors listed), please send them to me.

andy

But the issue here is precisely that the effects in question *worked properly* pre-3.1. Syntax is okay. There's commenting-out where needed. You know that I'm a *major* stickler for that kind of thing.

BTW, could the fact that a waveshape that I know is supposed to look a certain way in pre-3.1 now looks a bit different be due to that FFT level you tweaked with?