overlayers
Posted: Wed Jan 12, 2005 5:28 pmthank you! it works, but on the whole it seems not very good idea..
Page 1 of 1
Posted: Wed Jan 12, 2005 5:28 pmPosted: Wed Jan 12, 2005 8:55 pmPosted: Thu Jan 13, 2005 1:20 pmPosted: Fri Jan 14, 2005 11:37 amPosted: Sat Jan 15, 2005 6:28 pmPosted: Wed Jan 19, 2005 4:46 pmhigh!
thank you! it works, but on the whole it seems not very good idea..
thank you! it works, but on the whole it seems not very good idea..
Posted: Tue Feb 01, 2005 1:27 pmhigh!
another thing.. how about a "control scene"? i mean, it can be a *.r4 file with fixed name - control.r4 for example, and it must be placed under the main scene and stay always there, no matter what happens with overlays and rendered scene. if R4 can't find this file - nothing changes, but if this file exist - it may contain code for global variables, just like Jussi's beat detection code. "beat" and "beat_count" vars can be accessible from custom scenes. it also may be usefull like some kind of timeline, or playlist - it will demand of creation of grafical interface, which will generate this "control.r4"? basically, i can use ordinary overlay file, but if one day i press the button, which will launch all ovarlays removal code - it will kill all undertaking..
another thing.. how about a "control scene"? i mean, it can be a *.r4 file with fixed name - control.r4 for example, and it must be placed under the main scene and stay always there, no matter what happens with overlays and rendered scene. if R4 can't find this file - nothing changes, but if this file exist - it may contain code for global variables, just like Jussi's beat detection code. "beat" and "beat_count" vars can be accessible from custom scenes. it also may be usefull like some kind of timeline, or playlist - it will demand of creation of grafical interface, which will generate this "control.r4"? basically, i can use ordinary overlay file, but if one day i press the button, which will launch all ovarlays removal code - it will kill all undertaking..