Congrats on your new DDJ-FLX10 ! !
Could it be that its the Key: COLOR_FX_PARAM that is needed to select the CFX ?
(making a guess .... don't have the controller)
with maybe a mapping of like:
to in above case, to always set/select the inner knobs to be say "vocals" and outter CFX knobs to be "loop roll"
Additionally, and one could add a different function to the shift-CFX also .. either with the SHIFT_VERSIONoftheKey or within the mapping... with additional query for shift.
Note: changing the mapping like this will not allow one to have other CFX on the knobs, as one has mapped them to always be in one state.
if one wanted to just have vocal as your starting point.. and have the choice to have other CFX, then GroovinDJ's idea of adding to maybe, both KB's and the Controller's.. ONINIT
(or some variation) would be what you want.
The ONINIT solution would IMO be the perferred, allowing for more flexibility.
Could it be that its the Key: COLOR_FX_PARAM that is needed to select the CFX ?
(making a guess .... don't have the controller)
with maybe a mapping of like:
action_deck 1 ? filter & filter_selectcolorfx 'vocals' : action_deck 2 ? filter & filter_selectcolorfx 'vocals' : action_deck 3 ? filter & filter_selectcolorfx 'loop roll' : action_deck 4 ? filter & filter_selectcolorfx 'loop roll' : nothing
to in above case, to always set/select the inner knobs to be say "vocals" and outter CFX knobs to be "loop roll"
Additionally, and one could add a different function to the shift-CFX also .. either with the SHIFT_VERSIONoftheKey or within the mapping... with additional query for shift.
Note: changing the mapping like this will not allow one to have other CFX on the knobs, as one has mapped them to always be in one state.
if one wanted to just have vocal as your starting point.. and have the choice to have other CFX, then GroovinDJ's idea of adding to maybe, both KB's and the Controller's.. ONINIT
(deck all filter_selectcolorfx 'vocals') & ....
(or some variation) would be what you want.
The ONINIT solution would IMO be the perferred, allowing for more flexibility.
Posted Fri 26 Jul 24 @ 1:21 pm
All sorted on the mapping, thanks!
Only other issue is that I can't get stems split to work. I'm holding down shift then double pressing the relevant stem button but nothing is being cloned to another deck?
Only other issue is that I can't get stems split to work. I'm holding down shift then double pressing the relevant stem button but nothing is being cloned to another deck?
Posted Fri 26 Jul 24 @ 3:29 pm
You do that on the empty Deck, right ? Not the one you want to do the Split.
So if Deck 1 is loaded and u want to split it, you do the double-press on the other Deck 2
So if Deck 1 is loaded and u want to split it, you do the double-press on the other Deck 2
Posted Fri 26 Jul 24 @ 4:14 pm
Ah that will probably be it. I'm running a 2 deck skin and just expected the cloned stem to be loaded to an empty deck.
Posted Fri 26 Jul 24 @ 4:16 pm
https://www.virtualdj.com/manuals/hardware/pioneer/ddjflx10/layout/decks.html
It's all there. Also check the StemsSplitLeftRight setting
It's all there. Also check the StemsSplitLeftRight setting
Posted Fri 26 Jul 24 @ 4:18 pm
I did read the manual in detail but missed the part about it being on an empty deck. Thanks for the clarification.
Posted Fri 26 Jul 24 @ 4:36 pm
Did a club gig with the FLX10 last night and it's seriously impressive. Having the dedicated stems buttons for the channels and FX is brilliant.
Only one issue though, I've noticed sometimes when using the jog dials to move the waveform for example to set a cue point sometimes the jog dials don't respond properly. They will move the wave back and forward but sometimes stop and do nothing.
anyone else noticed this?
Only one issue though, I've noticed sometimes when using the jog dials to move the waveform for example to set a cue point sometimes the jog dials don't respond properly. They will move the wave back and forward but sometimes stop and do nothing.
anyone else noticed this?
Posted Sun 04 Aug 24 @ 6:03 pm
On all Pioneer controllers there's a case where when you use SHIFT+JOG to seek through the track, the MIDI can stuck and the JOG stops working properly.
To "fix it", all you have to do is to use SHIFT+JOG again, and make sure that you lift your hand from the jog BEFORE you let go of the SHIFT button.
I don't know if that was what you experienced, but if it happens to you again, just remember to try SHIFT+JOG to see if it solves the issue.
To "fix it", all you have to do is to use SHIFT+JOG again, and make sure that you lift your hand from the jog BEFORE you let go of the SHIFT button.
I don't know if that was what you experienced, but if it happens to you again, just remember to try SHIFT+JOG to see if it solves the issue.
Posted Mon 05 Aug 24 @ 6:30 am
Just tried again and it's not that.
Seems when I'm moving the jog wheel to set the cue slowly it's not registering properly. When I move it faster it moves the waveform accordingly but to set an accurate cue point it needs to be moved slowly and that's when it's just not responding.
Seems when I'm moving the jog wheel to set the cue slowly it's not registering properly. When I move it faster it moves the waveform accordingly but to set an accurate cue point it needs to be moved slowly and that's when it's just not responding.
Posted Mon 16 Sep 24 @ 10:47 am
There is a hardware vibration protection in MIDI protocol of the FLX10 (usedby VirtualDJ and Serato), which was causing this "dead" operation in slow jog movements.
In next update, VDJ will be using the HID mode for Jogs (used also in RB), so you wont get this issue.
EDIT. Actually we forced this change in current Early Access Build 8314. It's a silent update, so you need to restart your EA twice to get this. In the LICENSES tab, you should get Build 8314.2099
In next update, VDJ will be using the HID mode for Jogs (used also in RB), so you wont get this issue.
EDIT. Actually we forced this change in current Early Access Build 8314. It's a silent update, so you need to restart your EA twice to get this. In the LICENSES tab, you should get Build 8314.2099
Posted Mon 16 Sep 24 @ 12:02 pm
Wow that's amazing. Thank you!
Posted Mon 16 Sep 24 @ 12:58 pm
Just loaded the new EA and the jog movement for cue is perfect now. Nice job team and thanks for the fix.
Posted Mon 16 Sep 24 @ 6:59 pm
djdad wrote :
There is a hardware vibration protection in MIDI protocol of the FLX10 (usedby VirtualDJ and Serato), which was causing this "dead" operation in slow jog movements.
In next update, VDJ will be using the HID mode for Jogs (used also in RB), so you wont get this issue.
EDIT. Actually we forced this change in current Early Access Build 8314. It's a silent update, so you need to restart your EA twice to get this. In the LICENSES tab, you should get Build 8314.2099
In next update, VDJ will be using the HID mode for Jogs (used also in RB), so you wont get this issue.
EDIT. Actually we forced this change in current Early Access Build 8314. It's a silent update, so you need to restart your EA twice to get this. In the LICENSES tab, you should get Build 8314.2099
Is it fixed in the regular "standard" update yet (BUILD 8336 (2024-10-07))?
Posted Tue 08 Oct 24 @ 5:51 pm
Well yes as its a later version number.
Posted Tue 08 Oct 24 @ 6:10 pm
kradcliffe wrote :
Well yes as its a later version number.
Perfect thanks
Posted Tue 08 Oct 24 @ 7:19 pm
Hi!!
I've recently noticed that the GAIN has stopped working well, instead of noticing its effect on the master output, I only notice it on the headphones. I can't think of what could be happening.
The audio settings are as usual: canali 1 and 2 for the master and channel 3 and 4 for the headphones, and the audio device is ASIO FLX-10.
It doesn't matter if you use Autogain or not.
I can't think of what can happen and even less how to lend it.
Thank you!!
I've recently noticed that the GAIN has stopped working well, instead of noticing its effect on the master output, I only notice it on the headphones. I can't think of what could be happening.
The audio settings are as usual: canali 1 and 2 for the master and channel 3 and 4 for the headphones, and the audio device is ASIO FLX-10.
It doesn't matter if you use Autogain or not.
I can't think of what can happen and even less how to lend it.
Thank you!!
Posted Thu 24 Oct 24 @ 9:12 am
Using the factory default mapper for the flx10?
Posted Thu 24 Oct 24 @ 9:24 am
Thanks!!
Never imagine these issue could come from the map.
If i use factory works well, but in my map gain knoob is gain,
so where could be the fail?
forget say, that gains knoobs work correctly and can see if i move it on screen...
Never imagine these issue could come from the map.
If i use factory works well, but in my map gain knoob is gain,
so where could be the fail?
forget say, that gains knoobs work correctly and can see if i move it on screen...
Posted Thu 24 Oct 24 @ 9:37 am
You'll have to check what you changed then :)
Edit: If the knobs were also not moving on-screen, I'd guess you removed or corrupted the GAIN key?
Edit: If the knobs were also not moving on-screen, I'd guess you removed or corrupted the GAIN key?
Posted Thu 24 Oct 24 @ 9:42 am
Thanks for support!!!
I fix it. i do a copy paste of ONINIT to my map.
setting_setsession was i need .
thanks!!
I fix it. i do a copy paste of ONINIT to my map.
setting_setsession 'fxProcessing' 'Post-fader' & fake_master on & fake_hp on & fake_hpmix on & set_var "$SHIF" 0
setting_setsession was i need .
thanks!!
Posted Thu 24 Oct 24 @ 10:02 am