![]() ![]() No RGB midi out set up for the buttons yet, so if you make one, feel free to share it. So if you look into the constant I’ve left in there, you can call any of your buttons or sliders in multiple ways. You could also switch it out for say a touchOSC list of inputs. This method gets powerful if you want to drop in a new midi device but have all your scripts/ops still work when you hit a different devices’ “b1” for example. Again, you’ll notice the f1 is referred to as “template” in this case. Any table you put in “modules” can be called using. ![]() Place “modules” in your /local on the same level as “maps” “midi” and “time”. I’ve also attached a COMP called “modules”. No idea why this is, I can load in the sequencer TSI and the pads. but nothing else happens, Ive plenty of youtube videos etc and nothing like it happens. For example I get the same midi note triggered by the NI modifier buttons as the first row of launch buttons. I have a Kontrol F1, when connected and Traktor is started the four lights blink with deck assignment, when I push the encoder the display changes to whatever deck ive selected ie Deck C. When you go into TD, switch your f1 to midi mode by hitting “shift+browse”.Įven though it has a “midi mode”, the f1 is a “controller”, it’s NI programming can do some funky things. I had a problem with an effect mapping I’d left on. ![]() You’ll need to make sure you go into Traktor’s Controller Editor and use the default midi mapping. Place it in (/local/midi/userdevices) and it’d be a good idea for now to rename it to “template”. I have attached an f1 map, which had originally been named “template” in my network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |