Attachment 13090
Hey nem0nic,
Is this deck switching driven with different midi massages by hardware or modifier is used with four values?
Printable View
Attachment 13090
Hey nem0nic,
Is this deck switching driven with different midi massages by hardware or modifier is used with four values?
Midi massages? Sounds soothing.
The deck switching is done via firmware. It's implemented this way because Traktor isn't the only software out there, and not everyone supports modifiers or variable tracking.Quote:
Is this deck switching driven with different midi massages by hardware or modifier is used with four values?
That is pretty cool - giving more layering opportunities to other software then Traktor as well, it was my guess thought. Is there option to switch it of if someone wants to use only one layer of controls or to map this section like a standard controller?Quote:
Originally Posted by nem0nic
Brilliant, I'm planning on remapping the Deck D page as an FX module, and the other 3 pages as is to have access to jogs/pitch faders when needed. Can't wait for these.
No, there isn't a flat mapping.Quote:
Is there option to switch it of if someone wants to use only one layer of controls or to map this section like a standard controller?
We could have implemented a flat mapping, but then a user would have to remember use conditions and deal with double mappings. By changing the decks in the device, we present the user with the easiest possible mapping scenario. It's a 1:1 mapping at that point, and very easy to accomplish via MIDI Learn.
Do any of the others have any cool firmware features? Multiple layers, etc? :)
meaning there's no way to make that button just send a midi message instead?Quote:
Originally Posted by nem0nic
can we at least change the number of decks, so that we don't have to hit the button three times to get from deck 2 back to deck 1?
Yes! :DQuote:
Do any of the others have any cool firmware features? Multiple layers, etc?
Yes, the decks cycle if your mapping is set up that way (and to support 4 decks it would be). Of course, if you (for instance) had 2 PL-1s to control 4 decks and wanted them to do a deck toggle, you would just double map the decks to the same 2 virtual decks.Quote:
meaning there's no way to make that button just send a midi message instead?
But the deck button also sends a note itself every time it's pressed (the same note every time). This is mostly for people that want to set a modifier state or track a deck variable in software.
Am i misunderstanding something, or does that mean (in traktor at least) every time you change a mapping, you'd have to duplicate it and re-learn all of the commands for the second virtual deck....? Plus then you'd have to remember that (for the left PL-1) that 1&3 on the Pl-1 = Deck A, and 2&4 = deck C....Quote:
Originally Posted by nem0nic