Man-Tk
It would be good to save configs ... for ex. :
Vci+audio8dj
Time code + Rmx
Etc
we don't want to waste time with our differents options to play .
Another : save played songs in RED after a crash or restart .
Vci+audio8dj
Time code + Rmx
Etc
we don't want to waste time with our differents options to play .
Another : save played songs in RED after a crash or restart .
geposted Wed 02 Jun 10 @ 7:18 am
JoeyKJ
This would be good to have....
Joey....
Joey....
geposted Wed 02 Jun 10 @ 12:15 pm
sischo
Already posted in the past but nothing done in this direction.
geposted Wed 02 Jun 10 @ 1:07 pm
GadgetMan
Maybe we could have a script verb called "snapshot" with parameters "save" and "load". This would then allow us to map them to the keyboard, skins and/or controllers.
The snapshot verb would:
a) Capture the current play and side lists
b) The track loaded on to each deck, note which one is playing and the position in the file (time elapsed)
c) Whether automix is enabled
d) anything else we can think of...
Chances are, crashguard wouldn't be able to capture the relevant information as the program would already be unstable when it kicks in. But with nested scripts. you could probably add this to a few commonly used actions like "load" or "play" so that the snapshot is taken frequently.
Just a thought...
Roy
The snapshot verb would:
a) Capture the current play and side lists
b) The track loaded on to each deck, note which one is playing and the position in the file (time elapsed)
c) Whether automix is enabled
d) anything else we can think of...
Chances are, crashguard wouldn't be able to capture the relevant information as the program would already be unstable when it kicks in. But with nested scripts. you could probably add this to a few commonly used actions like "load" or "play" so that the snapshot is taken frequently.
Just a thought...
Roy
geposted Thu 03 Jun 10 @ 3:43 am