Accesso rapido:  

Forum: Old versions

Topic: Hot CUES..........

Questo argomento è obsoleto e potrebbe contenere informazioni obsolete o errate.

Ok I'm using an Ecler NUO4 and it has a very limited number of buttons and knobs. Here's what I'm trying to do........
Example, I have a button mapped for hot cue 1 for each deck. Let's say I'm playing a track that has 3 hot cues. Now when I press the button it will play from hot cue 1 and I get to the 2nd hot cue I now want that button to work with hot cue 2. Basically I want the button to work with the hot cue that was just past. So if I have not gotten to hot cue 2 yet when I hit the button it goes back to hot cue 1 but if I have past hot cue 2 when I hit the button it goes to hot cue 2 and so on and so on. Is this even possible if so any help would be great.....

Hope that all makes sense
Huey

 

Inviato Sun 14 Aug 11 @ 8:38 pm
Thats a tough one huey, I don't think it is possible to do it that way yet but it shouldn't be hard for an update as vdj is capable of recording and recalling the last cue point used, when you use "cue" it will jump back to the last used cue point. But work arounds are my business and the only way I see being able to do it is to use songpos_remain...

songpos_remain : get the remaining time in %. if used with a parameter (in % or ms), returns true if the time left is less or equal than the value

the problem though is that you can't map based on the elapsed time which would be much more useful, anyway if all of your tracks were the same length (3 mins) you could probably use

songpos_remain 60000ms ? deck # goto_cue 3 : songpos_remain 120000ms ? deck # goto_cue 1 : songpos_remain 180000ms ? deck # goto_cue 1

it would work like
3 mins remain - go to cue 1
2 mins remain - go to cue 2
1 mins remain - go to cue 3

so you can see that an elapsed time would do a pretty good job at it

or maybe use %

songpos_remain 33.3% ? deck # goto_cue 4 : songpos_remain 66.6% ? deck # goto_cue 3 : songpos_remain 99% ? deck # goto_cue 2 : goto_cue 1

33.3% remain - go to cue 4
66.6% remain - go to cue 3
99% remain - go to cue 2
100% remain - go to cue 1

untested... good luck bro
 

Inviato Mon 15 Aug 11 @ 9:19 am
I thought it might be a lot of work, lol! Well I've give that a try but its looking like ill have to wait.

Thanks for looking bro
Huey
 

Inviato Mon 15 Aug 11 @ 9:59 am
just had a better idea, but it would mean doing your hot cues again from scratch, but you could do it in batches of 30 second intervals and depending on the remaining time of the track it would set or go to the relevant cue then easily be able to recall the exact cue later on.

songpos_remain 30000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 24 : songpos_remain 60000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 23 : songpos_remain 90000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 22 : songpos_remain 120000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 21 : songpos_remain 150000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 20 : songpos_remain 180000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 19 : songpos_remain 210000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 18 : songpos_remain 240000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 17 : songpos_remain 270000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 16 : songpos_remain 300000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 15 : songpos_remain 330000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 14 : songpos_remain 360000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 13 : songpos_remain 390000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 12 : songpos_remain 420000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # deck # set_cue 11 : songpos_remain 450000ms ? deck # cue 24 ? deck # goto_cue 24 : deck # set_cue 10


just replace # with default or the relevant deck number if it is for your mixer
 

Inviato Mon 15 Aug 11 @ 10:20 am


(Vecchi argomenti e forum sono automaticamente chiusi)