How many times have you said to yourself, "I wish I could have saved that one..."
Suppose that at the start of a song, all the *exact* initial conditions of GF were stashed away -- initial script, song, and most importantly, the random number seeds, both at start and every time (rnd) is called. And suppose you could save this data at end of song.
Then wouldn't it be possible to do an exact playback of the GF visualization of that song?
Possible to Record and Playback a G-Force Visualization?
Moderators: BTT, andy55, b.dwall, juxtiphi
A log files of each session would be great. Then we could script more easily. Trying to watch the configs in verbose mode is difficult, due to rapid changes, inability to write them down fast enough (a tape recorder would help here I guess) and the ever changing backgrounds—dark text on a dark field for example.
Not if it's like the Mac version, which takes what seems like hours, plus it converts audio and visualization to a quicktime movie.Orbstah wrote:soundspectrum Darkroom PC version would solve yer problems
I'm suggesting something that works in real time, can be saved as a small file, and can then be played back in yer music player of choice.
oh i see, i think that would be difficult especially when you start to get over 1000 mp3 on your drive, coz not only have you got to go check the mp3 then look for a config file it would then have to go load the configs, i think the delays would be unaceptable and it would be hard to get any thing on the screen quick enough, imo
I'll come to bed once i've seen everything in G-Force.
Hey Argent & willrob!
I think I get what you mean... Are you suggesting something like:
00:00 Start G-Force
00:01 Colormap1.txt
00:02 Waveshape1.txt
00:03 Flowfield1.txt
00:04 TrackTitle1: ArtistName1: AlbumName1
00:05 Colormap2.txt
00:06 Waveshape2.txt
00:07 Flowfiel2.txt
00:08 Colormap3.txt
00:09 Flowfield3.txt
00:10 Flowfield4.txt
00:11 TrackTitle2: ArtistName2: AlbumName2
00:12 Waveshape3.txt
00:13 Colormap4.txt
...
where 00:00 - 00:13 are actual clock times or elapsed times from G-Force start
???
Basically, a running log file of just what G-Force is actually doing at a gross level? Kinda like what you would get by constantly hitting the L-key and writing yourself notes real fast? I suggested this to Andy almost a year ago and he said he would consider it for his 'to-do' list. Of course, that probably makes it item 2,765,287 on his list, so we will never see it in this lifetime!
I thought it would be a great idea, except I didn't think of the time-stamp idea, which would make it even better. It should be easy to do, since the information is already availably for the R-key, and it shouldn't take up too much resource since it is only writing to a text file a couple times a minute. It could just be a push-down text stack of some arbitrary length, such as 1-2000 levels, and every time a new item gets pushed into the stack, the oldest gets pushed out the bottom. The viewer could access and save the stack at any time (if it wasn't file-locked by G-Force), or if it was locked, it could be saved to the Desktop by a single G-Force keystroke, just like taking a snapshot, as Stack-1, -2, -3... It wouldn't be a 'genu-whine' automatic script writer, but it would sure give us a starting point for writing a script to repeat a desired show!
HEY ANDY!!! Listen up!
I'm not the only one who wants something like this!
Take care, guys.
I think I get what you mean... Are you suggesting something like:
00:00 Start G-Force
00:01 Colormap1.txt
00:02 Waveshape1.txt
00:03 Flowfield1.txt
00:04 TrackTitle1: ArtistName1: AlbumName1
00:05 Colormap2.txt
00:06 Waveshape2.txt
00:07 Flowfiel2.txt
00:08 Colormap3.txt
00:09 Flowfield3.txt
00:10 Flowfield4.txt
00:11 TrackTitle2: ArtistName2: AlbumName2
00:12 Waveshape3.txt
00:13 Colormap4.txt
...
where 00:00 - 00:13 are actual clock times or elapsed times from G-Force start
???
Basically, a running log file of just what G-Force is actually doing at a gross level? Kinda like what you would get by constantly hitting the L-key and writing yourself notes real fast? I suggested this to Andy almost a year ago and he said he would consider it for his 'to-do' list. Of course, that probably makes it item 2,765,287 on his list, so we will never see it in this lifetime!
I thought it would be a great idea, except I didn't think of the time-stamp idea, which would make it even better. It should be easy to do, since the information is already availably for the R-key, and it shouldn't take up too much resource since it is only writing to a text file a couple times a minute. It could just be a push-down text stack of some arbitrary length, such as 1-2000 levels, and every time a new item gets pushed into the stack, the oldest gets pushed out the bottom. The viewer could access and save the stack at any time (if it wasn't file-locked by G-Force), or if it was locked, it could be saved to the Desktop by a single G-Force keystroke, just like taking a snapshot, as Stack-1, -2, -3... It wouldn't be a 'genu-whine' automatic script writer, but it would sure give us a starting point for writing a script to repeat a desired show!
HEY ANDY!!! Listen up!
I'm not the only one who wants something like this!
Take care, guys.
Exactly so!
Except that I suspect the timing would need to be much finer-grained:
00:000000 Start G-Force
/* in boot.txt */
SetPref( PREF_COLORMAP_INTERVAL, "15 + rnd( 30 )" );
/* save PREF_COLORMAP_INTERVAL away for later replay */
SetPref( PREF_WAVESHAPE_INTERVAL, "15 + rnd( 20 )" );
/* save PREF_WAVESHAPE_INTERVAL away for later replay */
/* etc etc, save every randomly computed variable */
/* end of boot.txt /*
00:010121 Colormap1.txt
...
Pretty complicated. I would guess it might be easier to trigger an exception every time something should be stashed away -- let the handler do the heavy lifting.
Except that I suspect the timing would need to be much finer-grained:
00:000000 Start G-Force
/* in boot.txt */
SetPref( PREF_COLORMAP_INTERVAL, "15 + rnd( 30 )" );
/* save PREF_COLORMAP_INTERVAL away for later replay */
SetPref( PREF_WAVESHAPE_INTERVAL, "15 + rnd( 20 )" );
/* save PREF_WAVESHAPE_INTERVAL away for later replay */
/* etc etc, save every randomly computed variable */
/* end of boot.txt /*
00:010121 Colormap1.txt
...
Pretty complicated. I would guess it might be easier to trigger an exception every time something should be stashed away -- let the handler do the heavy lifting.
I was just trying to keep it simple, practical, and to describe it in a general sense, though your refenence to time precision does need to be addressed. I think that precision should be kept at whatever level Andy already uses in controlling G-Force. This proposed config-logging needs to take up a minimum of overhead, since G-Force is already so CPU intensive, and the more time it spends doing crap like this, the less time it has to draw purdy-pichers! Since most G-Force time-sense seems to be rounded to the nearest second, that should be adequate in most instances; there is no need for much higher resolution, since delays caused by processor and/or read/write delays could produce larger differences, depending on variable machine loading.
There is no need to measure with a micrometer when you are trimming with a hatchet.
Take care.
There is no need to measure with a micrometer when you are trimming with a hatchet.
Take care.