Anmelden:     

Forum: General Discussion

Topic: Still tuning the MTP

Dieses Thema ist veraltet und kann veraltete oder falsche Informationen enthalten.

Hi, all.

My Effect Select knob can also be pressed in - can anyone please advise how to map 'press in and twist' to adjust the move_loop parameter? I'd ideally like both sides to adjust the appropriate loop.

Can anyone help?

Ta
Mike
 
geposted Mon 25 Feb 13 @ 1:04 pm
Further investigation has revealed VDJ recognises both FX_SELECT_BTN and FX_SELECT from my MTP.

Am I able to combine both somehow to loop_move + or - 10ms on deck 1 and deck 2 respectively?

Ta again,
Mike
 
Hi, all.

Me again.

Now, having read this article http://www.virtualdj.com/forums/175305/General_Discussion/Mapping_question___.html, I wonder if this is the beginnings of fixing my dilema...

This also interested me - http://www.virtualdj.com/wiki/Use%20a%20combination%20of%20buttons%20to%20trigger%20two%20different%20actions.html

Can anyone advise if this is the way forward to finetune my loop issue? And what do I need to open and edit (and where do I find it?!) to try it?

Does anyone know if I can do this with my Mixtrack Pro? Or am I stuck using my keyboard to adjust my loops..?

Ta
Mike
 
You just need to map it similar to a SHIFT button but using a different variable name to avoid any conflict, e.g:

FX_SELECT_BTN:

set 'fxselect' 1 while_pressed

FX_SELECT:

var 'fxselect' ? param_greater 0 ? loop_move +10ms : loop_move -10ms : fx_select

...Or to perform loop_move on both decks:

var 'fxselect' ? param_greater 0 ? deck left loop_move +10ms & deck right loop_move +10ms : deck left loop_move -10ms & deck right loop_move -10ms : fx_select

See: http://www.virtualdj.com/wiki/How%20do%20I%20change%20the%20mapping%20for%20a%20button.html
 
Thank you! This has been bugging me for ages! I tried remapping the pitch shift buttons, too, but that wouldn't play nicely either. I'll give these a try now.

Ta
Mike
 
I've tried your code, and this is what happens now: nb - I only tried using the left deck.

Scenario 1:
Open Config, Mappers, press Key Learn, and press FX_SELECT_BUTTON, then enter your code as below:
set 'fxselect' 1 while_pressed

Open Config, Mappers, press Key Learn, and twist FX_SELECT, then enter your code below:
var 'fxselect' ? param_greater 0 ? loop_move +10ms : loop_move -10ms : fx_select

Result:
A frozen effects menu, and no manipulation of the loop position with the knob pressed and turned either way.

Scenario 2:
Open Config, Mappers, press Key Learn, and press FX_SELECT_BUTTON, then enter your code as below:
set 'fxselect' 1 while_pressed

Open Config, Mappers, press Key Learn, and twist FX_SELECT, then enter your code below:
var 'fxselect' ? param_greater 0 ? deck left loop_move +10ms & deck right loop_move +10ms : deck left loop_move -10ms & deck right loop_move -10ms : fx_select

Result:
As above.

What is it I'm missing?

Would it be easier to configure say, when my LOOP_MODE button is active, I can use the jogwheels to adjust the loop?

Ta
Mike
 
fx_select should be effect select, i.e:

var 'fxselect' ? param_greater 0 ? loop_move +10ms : loop_move -10ms : effect select

Is the knob an endless encoder (Keeps turning with no stopping point)? If not, then loop_move will not work. This function cannot be assigned to an absolute knob (One with min/max, similar to EQ knobs.)
 
Sorry to be a pain, but no joy with this one either I'm afraid, although this does keep my effects menu active, pressing and twisting does not adjust the loop.

Forgive me if its me being real stoopid...

Furthermore, the knob turns indefinitely, although with a satisfying little click, instead of smoothly, like for example, my EQ knobs.. Would that make a difference?

Ta
Mike
 
If it turns indefinitely then it is an endless encoder. It's common for these to move in clicks, which makes it easier to make small adjustments 1 step (click) at a time.

Depending on the type of encoder, you may need to use either of the following:

var 'fxselect' ? param_greater 50% ? loop_move +10ms : loop_move -10ms : effect select

var 'fxselect' ? param_greater 0% ? loop_move +10ms : loop_move -10ms : effect select

You could also try:

var 'fxselect' ? loop_move : effect select

(This will move 1 beat left/right rather than 10ms.)
 
By jove, I think we're nearly there!

I've tried both your lines of script, and with both, while it now adjusts the loop thank you, I can only adjust backwards, irrespective of which way I turn the knob.

Again, thanks for your continued support (I'd never have figured this out), and if we can nail this last little gremlin, you'll make a grown man a happy little boy...

Ta
Mike
 


(Alte Themen und Foren werden automatisch geschlossen)