do you have a link to a post that summarizes your ideas? some new prics to add in vectorc can be quickly and easily added depending on their spec.jerohm wrote: Selfishly, I could suggest several, easy(?) to implement, Config language enhancements along the same lines as 'select()' and 'choice()', but I am willing to accept baby steps.
G-Force 4/Toolbar
Moderators: BTT, andy55, b.dwall, juxtiphi
-
JayPro
- Posts: 738
- Joined: Sat May 01, 2004 10:51 pm
- Location: Huntington Station, Long Island, New York
@jerohm;
With all due respect, Andy seemed to have made it abundantly clear that the basic coding language that as if by miracle makes the FlowField will remain intact. Indeed I agree with you this is the beauty and *insane* genius of AoM's flagship product. This whole argument, as you know though, is strictly about the "new" GUI; so I'm not quite sure whence this trepidation over why G-Force from a visually conceptual standpoint would somehow be compromised in any way.
In short, the VectorC aspect of GF programming is here to stay...and *all* of the neat effects that can be made with it.
OTOH, your unhappiness over the elimination of the Toolbar from a specialist's POV is definitely understandable. But as one whose math and programming skills...never mind simple *arithmetic*...are near flat-line, I simply cannot understand as you can how the Toolbar can be used to evaluate scripting capabilities. Matter of fact, the only reason why I found the entire config coding process easier *before* the GF2.5 recension (i.e. making the syntax more C++-like) was out of constant noodling with the functions and looking at all the pretty things they did. At least I now have a better understanding of r versus theta, if nothing else.
But as I said before, the only thing that kept this language pre-2.5 from being at least *somewhat* intuitive was my piss-poor math. But now, it's as if I'll have to tackle the basics of C++ if I want to make configs. It may be more understandable to some; but it's something I fear I won't be able to teach myself with great success.
"G-Force Syntax for Dummies", anyone?
I'll just leave the scripting aspect to people who don't make me tilt my head like a bemused dog whenever they try to explain to me what they do and how they do it.
But back to the point: For my purposes, the Toolbar has always seemed IMPOV bloated and redundant. Quite frankly, the user would be *most* appreciative of the product if the whole of its functionality came in one neat little package...as it were.
2¢.
With all due respect, Andy seemed to have made it abundantly clear that the basic coding language that as if by miracle makes the FlowField will remain intact. Indeed I agree with you this is the beauty and *insane* genius of AoM's flagship product. This whole argument, as you know though, is strictly about the "new" GUI; so I'm not quite sure whence this trepidation over why G-Force from a visually conceptual standpoint would somehow be compromised in any way.
In short, the VectorC aspect of GF programming is here to stay...and *all* of the neat effects that can be made with it.
OTOH, your unhappiness over the elimination of the Toolbar from a specialist's POV is definitely understandable. But as one whose math and programming skills...never mind simple *arithmetic*...are near flat-line, I simply cannot understand as you can how the Toolbar can be used to evaluate scripting capabilities. Matter of fact, the only reason why I found the entire config coding process easier *before* the GF2.5 recension (i.e. making the syntax more C++-like) was out of constant noodling with the functions and looking at all the pretty things they did. At least I now have a better understanding of r versus theta, if nothing else.
But as I said before, the only thing that kept this language pre-2.5 from being at least *somewhat* intuitive was my piss-poor math. But now, it's as if I'll have to tackle the basics of C++ if I want to make configs. It may be more understandable to some; but it's something I fear I won't be able to teach myself with great success.
"G-Force Syntax for Dummies", anyone?
I'll just leave the scripting aspect to people who don't make me tilt my head like a bemused dog whenever they try to explain to me what they do and how they do it.
But back to the point: For my purposes, the Toolbar has always seemed IMPOV bloated and redundant. Quite frankly, the user would be *most* appreciative of the product if the whole of its functionality came in one neat little package...as it were.
2¢.
"God is syntax."
// *** Somewhat Inconsistent Implementation ***andy55 wrote: do you have a link to a post that summarizes your ideas? some new prics to add in vectorc can be quickly and easily added depending on their spec.
// *** Only operates on inSrce(row[0]) ***
//
// Performs a gaussian smoothing/covolution on inSrce using |inSigma| to determine
// the radius of the smooth (the radius of influence is about 4*inSigma).
// If inSigma < 0, the boundaries of inSrce are wrapped (resulting in a "wrapped"
// or "circluar" blur).
float smooth( float inSrce, float inSigma ); // Screws me every time!
==============================
//
// Shuffle - randomly shuffle columns from x (based on the global random seed)
//
// The idea here is the same a shuffling a deck of playing cards. After the operation, column values could be accessed
// using "float col( float inValue, int inColNum );" and would be guaranteed to only see the original column values.
// in some random order (no duplicates, unless duplicates are in original data set).
float shuffle( float x );
==============================
// Similiar to the construct 'rnd(vector(Cols, 1))' which returns a row of 'Cols' columns with random values[0,1] inclusive,
// but instead,
// returns a row of 'Cols' columns within a discrete set of random values
//
// Conceptually (Only, Not syntactically correct):
//
// "choice(vector(Cols, {2,7,9}))"
==============================
(less important since normalized fft() data, but still useful)
// *** Returns the smaller of two values
float min( float a ); // Returns min 'col' for each 'row'
float min( float a, float b ); // ** Current ** Implementation
// *** Returns the larger of two values
float max( float a ); // Returns max 'col' for each 'row'
float max( float a, float b ); // ** Current ** Implementation
==============================
A way to determine being run as a WaveShape or Particle when Avars are initialized
Currently it can only be determined (WS == (t>0)&&(dt==0)) ... too late for Avars
==============================
Bvar="select(Id, Bvar, DoTask0)" // Should be a highly optimized construct (if not already)
==============================
Read Only Access to system variable current FPS
==============================
'ConB' to allow expressions (i.e., same as 'Num' is handled)
==============================
'Pen' and 'Lwdt' to allow multi-dimensions(rows) that map/control unique [X_,Y_] pairs in a single task
==============================
Shape Library Facility
Allow X,Y corrodinate set to be calculated ONCE and stored for access by other configs. This would allow
for user generated shapes to be reused in various presentations. For example, the playing card suit shapes.
It also cuts down the config complexity when presentaiton is the objective. If you are still on the fence, watch
the video http://www.youtube.com/watch?v=81ZADUnns0I
// =======================================
// *** Scripts should be able to be 'slideshowed' - People who can't write Configs SHOULD be able
// *** to handle this and replay their favorite combinations.
// *** User Interactivity!! ***
// *** Script time specification needs a relative format, i.e., +0:05 five seconds from NOW
// *** Script directive to map 0-63 GrayScale(Black->White), and compress Color map to
// remaining locations 64-255. This would allow generic control over displaying Sprites in B&W
most of what I can think of now... thanks for consideration
jrm
Last edited by jerohm on Sat Aug 04, 2012 6:06 pm, edited 1 time in total.
yeah but what about being able to control G-force from another screen in real time?JayPro wrote:
But back to the point: For my purposes, the Toolbar has always seemed IMPOV bloated and redundant. Quite frankly, the user would be *most* appreciative of the product if the whole of its functionality came in one neat little package...as it were.
2¢.
having themes isnt realy the same as having spontanious control over the configs, or what am I missing?
I for one being around since version 1 of G-force and have been using the commercial version for 4 years now, that is used for controlling G-force from a remote system over a network. Would we be losing this function and what would be replacing it. I have many things setup for instance can take pictures of people entering for a party at home tranferred into laptop and overlap picture using laptop with tool bar running during different times. Along with being able to set configs and clear toolbar and have just that highlighted to run. So my only question would be what replaces it and would it only be a set programmed function or would there be some kind of remote too it ?????
Hello DireWolf
You may not make use of the G-Force Toolbar however, I can assure you many users find it an essential tool for both customising, and testing configs in G-Force. I for one am yet to be convinced the planned new GUI will allow such flexibility as the current Toolbar. Once it's gone it's gone, and all those wanting a standard GUI across all SoundSpectrum products will I believe regret the removal of the G-Force Toolbar.
Regards BTT
You may not make use of the G-Force Toolbar however, I can assure you many users find it an essential tool for both customising, and testing configs in G-Force. I for one am yet to be convinced the planned new GUI will allow such flexibility as the current Toolbar. Once it's gone it's gone, and all those wanting a standard GUI across all SoundSpectrum products will I believe regret the removal of the G-Force Toolbar.
Regards BTT
I hope the keyboard works with J.River Media Center.BTT wrote:Hello DireWolf
You may not make use of the G-Force Toolbar however, I can assure you many users find it an essential tool for both customising, and testing configs in G-Force. I for one am yet to be convinced the planned new GUI will allow such flexibility as the current Toolbar. Once it's gone it's gone, and all those wanting a standard GUI across all SoundSpectrum products will I believe regret the removal of the G-Force Toolbar.
Regards BTT
Aeon 3.0.0 Platinum does not work.
Hugs,
Fabricio, from Brazil.
Licensed User
Hello Fabricio
If you are having problems with your keyboard, and J River Media Centre you should bring this to the attention of SoundSpectrum.
http://www.soundspectrum.com/support/
Regards BTT
If you are having problems with your keyboard, and J River Media Centre you should bring this to the attention of SoundSpectrum.
http://www.soundspectrum.com/support/
Regards BTT
Friend,BTT wrote:Hello Fabricio
If you are having problems with your keyboard, and J River Media Centre you should bring this to the attention of SoundSpectrum.
http://www.soundspectrum.com/support/
Regards BTT
I sent email for a long time, but did not respond.
Thank you for your attention.
Fabricio, from Brazil.
Licensed User
Warning: I sent e-mail about the Aeon. Some time ago I sent the email.BTT wrote:Hello Fabricio
If you gave SoundSpectrum details of your problem on the link I have given you they would have sent you an automated email with a ticket number. Give me the ticket number, and I will contact SoundSpectrum on your behalf.
Regards BTT
I'll find the e-mail. I hope I have not deleted the email.
Now, I'll email about the G-Force.
Hugs,
Fabricio, from Brazil.
Edit .....
I remember now:
I reported the bug (keyboard, J.River Media Center) when I answered the e-mail the soundspectrum (about my problem of password to download the aeon (beta and final)).
Do you understand? I did not get ticket number.
Fabricio, from Brazil.
Licensed User