xXCpt_NemoXx
I'm sure there is an explanation and thereby a solution for this, but it presently eludes me. On my FLX10 I have the key shift_browse_enc_push mapped to holding 150 ? unload : browser_zoom. When on deck 1 on the FLX 10 it will unload deck 1, but when on deck 3 it unloads deck 2. Obviously I would like it to unlock deck 3. Why is it doing this and how would I fix it?
Posted Wed 24 Apr 24 @ 9:23 pm
xXCpt_NemoXx
Also this key unloads deck 3 when performed on deck 2.
Posted Wed 24 Apr 24 @ 10:47 pm
locoDog
how about deck 4? sounds like a bug to me.
Posted Wed 24 Apr 24 @ 11:43 pm
xXCpt_NemoXx
No. They unload the correct decks otherwise. I suspect it is something to do with the ordering of the decks in VirtualDJ not corresponding fully to the order in which they are assigned.
Posted Thu 25 Apr 24 @ 1:57 am
xXCpt_NemoXx
It would be really great if someone could possibly give me a more definitive answer to whether or not this is in fact a bug.
I took the time to check the midi messages being sent and they appear to be working normally as far as I can tell:
399999.00s: Chan 1 Note on D#4 (144 63 0) < Shift button up
399492.00s: Chan 7 Note on A6 (150 93 0) < Browse knob out
399371.00s: Chan 7 Note on A6 (150 93 127) < Browse knob in
398678.00s: Chan 1 Note on D#4 (144 63 127) < Shift button down
394182.00s: Chan 7 Note on A#4 (150 70 0) < Browse knob out
394099.00s: Chan 7 Note on A#4 (150 70 127) < Browse knob in
I took the time to check the midi messages being sent and they appear to be working normally as far as I can tell:
399999.00s: Chan 1 Note on D#4 (144 63 0) < Shift button up
399492.00s: Chan 7 Note on A6 (150 93 0) < Browse knob out
399371.00s: Chan 7 Note on A6 (150 93 127) < Browse knob in
398678.00s: Chan 1 Note on D#4 (144 63 127) < Shift button down
394182.00s: Chan 7 Note on A#4 (150 70 0) < Browse knob out
394099.00s: Chan 7 Note on A#4 (150 70 127) < Browse knob in
Posted 5 days ago @ 5:41 am
djdad
Indeed there was a typo in the definition, the keys were inverted for Decks 2,3
It's fixed now.
If you are running latest released Build 8124, try to restart to get a "silent" update to Build 8124.2056
It's fixed now.
If you are running latest released Build 8124, try to restart to get a "silent" update to Build 8124.2056
Posted 5 days ago @ 7:20 am
xXCpt_NemoXx
I really appreciate you checking and fixing it.
Posted 4 days ago @ 5:57 pm