Only map the first row of slots? Not if I can help it.
http://youtu.be/SuzDxwzv5Sg
Printable View
Only map the first row of slots? Not if I can help it.
http://youtu.be/SuzDxwzv5Sg
the million dollar question is, will you be sharing your map?
Nice, it's also been done with lemur here and they're sharing it. ;)
http://forum.djtechtools.com/showthread.php?t=52674
And is it really full functionality? Can you capture loops and assign them to all 64 slots? Can you change the source for capture actions? Can you set the quantize values or turn quantize on/off? Can you change the playback speed of any of the slots? Can you nudge a sample? Do the pads on the iPad change color according to the color of the sample?
The million dollar question is .... HOW?!Quote:
Originally Posted by djlotus
Well the capture future captures to the highlighted slot in the remix decks. So if slot A2 is highlighted and you press captur (button asigned) it will load into the 2. slot of sampler A.
This should mean that you could map 1 button to one of these (capture/deleate/trigger) to a sampler and then 16 button to highlight slots
Great achievement. But no need to keep it a secret from us, better strike with the honor before someone else will do it. I mean, not even a week further and I've already seen more people being capable of more things NI wants you to do without the F1.
Still, great achievement (once again).
To answer some questions.
Yes I will be sharing this once I put some documentation/instructions together for it.
I hadn't seen the lemur project but from the looks of it mine is very similar. I'm basically translating midi signals into mouse commands. The mouse commands happen so fast you don't even see them and I haven't noticed any sort of lag at all. Best part is this will work with ANY controller.
As far as functionality, anything that can be done with the mouse in regards to the remix decks can also be done via midi controller.
I'll get more up once everything is a bit more polished.
Also, is the LED feedback working too?
Interesting. Presumably different screen resolutions will need different templates. Just goes to show that this basic (non-LED) mapping should have been made available in the controller manager in the first place!