LAUNCHPAD mapping 4 decks 4 traktor (w/ leds)
LAUNCHPAD mapping 4 decks 4 traktor (w/ leds) Posted on: 11.12.2009 by Jay Mcelhenny So, I bought a launchpad because i wanted all those buttons, for hot cues, and other such fun.... plus the fact that you could get LED feedback was auh sum!but damn if that thing was difficult to figure out!!! first, its meant to play with ableton. Anything else requires novation's automap which is a pain to use with traktor. I thought i was bound by this marriage believeing that the only way to get midi messages from launchpad to other softwware, mainly traktor, was while the automap server was running. Needless to say, that whole thing was terrible. But then i noticed something in traktor's midi controller setup...... if you select "general midi" and choose "launchpad" for in/out ports guess what? you can send midi messages directly from launchpad to traktor like any other controller. Then its all a matter of figuring out what you want to do. I have searched the web and all my searches ended up with results = 0. I couldn't find a good explanation, nor a fully mapped out launchpad, specially nothing complete with responsive LEDs (but i knew it was possible cause i saw a youtube vid of some dude doing such stuff). So after many hours of reading, testing, configuring, etc... i got my launchpad to work. Not sure i'll keep this mapping entirely, but for now, its cool to see that what i put on paper actually works in practice. So first off, here's my setup so if you have something similar, you can try it out and see if it works: - MacBook 13" (os x 10.5) - traktor pro - novation launchpad that's it as far as this particular experiment goes. I don't really have the resources nor time to try the different combinations of operating systems, drivers, and traktor versions, but if anyone wants to give this a go for other setups, please please do so and share your feedback. I'm sure i'm not the only one who would like to know more about this. There are some gotcha's to all this: 1. you don't have to run automap (which is not really a gotcha but a note) 2. I'm not sure if launchpad is meant to run the way i've done it, but whatever, it works for me now and seems stable 3. i'm by no means a midi expert nor programmer and i'm still learning a lot 4. i don't guarantee this will work, but if it does and people like it, auh sum! Here is a detailed view of the mapping: MAPPING-VIEW (description in caption) So here's what you have to do: 1. download the tsi files i have created (4 total, 1 for each deck. I don't like flipping through huge mapping files in the small traktor window, sorry) A-Deck TSI [download] B-Deck TSI [download] C-Deck TSI [download] D-Deck TSI [download] 2. open traktor first and import the files. 3. make sure that for each mapping file, launchpad is selected as in/out ports. (not sure if the mapping files do this automagically) 4. once imported, close traktor 5. connect your launchpad via usb (all LEDs will/should be off) 6. open traktor 7. once its ready to receive midi, click on all the buttons and it will light them up according to their current state. It should look like this photo: INITIALIZATION PICTURE (description in caption) Here are some other photos with explanations in the captions: HOTCUE STATES PICTURE (description in caption) FULLY LOADED PICTURE (description in caption) I don't have a complete understanding still of some of the concepts and discovered some on a fluke. However, i will say this, what i'm really hoping for is that some of you see what i did (hopefully it works on your setup) and can play around with it more. Also, please leave any feedback as to what you believe or suggestions or anything. I'll try to help out as much as i can since i'm usually pretty busy (i'm surprised i even got this going). Anyhow, thanks again... migz | |
| Stephanie Nespor 12.03.2010 | Hello everybody. I create .tsi file for Launchpad, too. Click the following link to see a picures with config--> http://picasaweb.google.com/10343562...27112217717378 If it's on yr interest please contact me and I'll share this by sending via-mail (1,34Mb). ...have a good mapping;-) |
| marija dunn 12.03.2010 | At that time I thought I had a conceptual solution, but atm I dont remember it... Thinking about it now, depending on the specific case, I believe it should be possible by outputting some value to a virtual midi cable, receive it back again in another midi page in traktor to set a modifier, and use multiple Add out-> modifier to output certain values to the launchpad, or use it as a condition for other output controls. I haven't tested this though, it might bring up other problems. atm I use bome or max/msp to have more control, I also (mainly) use them because of the crackling/latency caused by updating multiple leds at once using direct messages from traktor to the launchpad. |
| Joella Roelfs 13.03.2010 | Thanks again ejac. I alredy know Midi-OX but Midisniffer is easier to understand. I've figured out that the reason must be my mac os x (Snow Leopard) because I booted my macbookpro into WinXP and there the hotcue status and led behaviour just goes well. Nevertheless, I still don't know what exactly the reason is and also I also don't know how to get the status led's working properly with katapult, which is kind of a bummer, because it makes the launchpad so much more attractive. Another question regarding different colors for the type of hotcue. You wrote:
note: now it could behave strangely in combination, because this tells traktor to set the midi value to 12 when the hotcue is not fadein, but the other rule will say that when it is in a certain range it will output 60, so depending on which rule gets executed first, the behavior will differ. And afaik there is no way of knowing that order, or telling traktor which order to do it in. This is another major headache i get from traktor, but it can be solved by a lot of work and modifier-magic)
|
| marija dunn 11.03.2010 | What do you mean with failed? Does it act weird only with hotcues? If yes, then the launchpad is probably fine. If experienced odd behavior too, because playing with max/msp I sent some messages to the launchpad that set it in a different state, maybe that happened too (though if that happened probably nothing would work). There is a way to reset and test the launchpad (got that from the developers reference on the novation website): reset: send a cc message on channel 1, number 0, velocity/value 0 test: send a cc message on channel 1, number 0, velocity/value 127 (this will set all leds to full lighting, meaning they will light up amber (= green full & red full). To debug I sometimes use bome's midi translater with a virtual midi cable to inspect which messages are sent exactly. Bome's is not free, but i found a handy free program: midi sniffer. So to debug get the free programs: http://www.maplemidi.com/Maple_driver.html http://www.rtcs.co.za/downloads.htm then let traktor output to a virtual cable, use the same cable as input for the midi sniffer and find out which messages get sent exactly. And see if it is what you expect it to be. Bome can send any midi message to any midi device, which is also handy to test stuff. |
| Joella Roelfs 11.03.2010 |
Originally Posted by ejac
It's is somewhat strange that the mapping with katapult works except the hotcue states. I really don't know the reason for that behaviour. Maybe my Lauchpad is broken ... Regards Tristan |
| marija dunn 11.03.2010 | There where some issues with the hotcue implementation of the original .tsi from misterMigz, I posted a fixed version with explanation here Hotcue states are output when a hotcue is mapped, deleted, when a track is loaded, and when deck focus changes (maybe some others that I dont know about). Normally the hotcue stat is not sent when triggering it (after all the hotcue state doesn't change), and it should not behave the way you describe. A minimal test (not using midikatapult) that should work:
This should cause the specified led to light bright red when a hotcue is mapped to mapping 1 of deck A and turn off again when that mapping is deleted. (for an explanation on how it works, see the link in the first sentence of this post) btw: make sure automap is not running |
| Joella Roelfs 10.03.2010 | Is there anyway to keep the led's on after pressing the according hotcue button. I cant believe that this is so difficult. Head over at midikatapult for more details (tsi + mapping jpeg). EDIT: I've also tried the tsi from this thread but no one gives me a constant lightning if a hotcue is stored. I must make some basic things wrong. |
| marija dunn 07.03.2010 | @BornSlippy yes, I experienced the same thing, and talked about it in this post I'll repeat it here and add some new insights I gained since then:
Originally Posted by ejac
Originally Posted by Launchpad programmer's reference
I've experienced this behavior on 3 separate machines, with different windows versions. I am amazed that not more ppl are complaining about it, because it drove me crazy. One real solution, as I have experienced, is to route all midi through another program that will accept the midi messages from traktor without delay, and uses its own queuing system to output the translated (or same) midi messages to launchpad. I have done some experiments with bome's midi translator and max/msp, they both solve the problem. (maybe there are free programs that can do just that, atm i havent researched that) Another solution is to not update more than 1 led at a time, but that limits the possibilities enormously. For example: changing deck focus will output all hotcue states, loop states, the sync state, ... So any combination of those will result in a hiccup when deck focus changes, or a new track is loaded. Another is to increase the latency of your audio driver, but of course there are many reasons why you wouldn't want to do that. But if it really matters you can eliminate the hiccups like that. |
| Pasquale Foegen 06.03.2010 | hey guys first of all i want to say i googled alot and this thread is absolute gold!! thanks so much for all the posts. using all the advice i have made a tsi suitable for me i have just traktor and launchpad no mixer(considering and x1 looks great!) however i am experiencing a major issue i really need some help with please! so i have my volumes for deck a and b (just a beginner not using four decks yet) and the 4 eq controls mapped out vertically on the launchpad. Also a beat phase for deck a and b so i can see which is playing, and ive found its great cos if they are flashing slightly off it means my beatmatching is slightly off. I then spent hours doing the outs for different colour leds so i know which deck is which and what volume they are at without looking at computer screen. the problem is, since i put the outs for the leds in whenever i press a button on launchpad, its creates a terrible sound like a glitch or lag sound in the track!! im worried its due to my Laptop being abit slow maybe? i have an acer aspire 5315 its intel celeron 2GHZ with 1GB DDR2 Ram. so for now ive taken off the leds, just relying on traktor screen to see whats going on, but i loved the lights its such a shhame!! any advice or help pls guys?
Originally Posted by faeruithir
|
| Leota Saniuk 06.03.2010 | yeah together with katapult faders can really be quite powerful. there is also a todo item to use the multi coloring to make the gradual fader automation visually more granular. plus another todo item to make it possible to dynamically adjust the speed of automated faders. |
| marija dunn 06.03.2010 | @faeruithir I saw this video by djranking s before buying one, he talks about the buttonquality http://www.youtube.com/watch?v=KSNnCz8zfow When I got mine I was actually pleasantly surprised by the feel, because I was expecting worse: the video wasn't totally convincing to me and it is so cheap. My first surprise was that they felt a little rubbery, I expected hard plastic. They do have that double click feel that the guy in the video talks about, but they are very usable for rapid button action. Probably not as good as those arcadebuttons on the midifighter, or the drumpads of an akai sampler or m-audio trigger finger. You can tap them lightly on the corners, if you like a light feel and that works very well (I tend to use them like that for rapid action). Or just use enough force in the middle, then you will barely feel the double action. I would say, if you mainly want to use it to do controllerism bashing, then the others might be more suitable, but the launchpad can for sure be used like that, the buttons work well and predictable, but feel a little less precise (mushy idd describes the feeling well). I like that they always fire a midi message. For example with the Xone 1D and the behringer bcf2000 (my friends got these) I sometimes experience a dropout, by which I mean that I for sure push a button, but noting happens. With my novation remote zero sl mk1 when using the drumpads on low sensitivity settings I sometimes get a double hit, meaning 2 messages get sent in stead of one (which is not a problem if the setting is a little higher than minimum). With the launchpad I haven't had any experiences like that. The main advantage is of course the very programmable leds. They give you much feedback, and keep your eyes of the screen. Sliding the buttons to imitate a fader does not feel easy/good to me, I tend not to use it like that, but it is doable for sure (and you can program it like that with traktor if you were wondering). With the midikatapult software though, you can push for example the upper button of a programmed slider and that slider will slowly (you can program how much time it takes) be increased to that point. But I really like a real slider for this, with buttons the resolution is pretty big, and for most cases not enough for me. |
| Leota Saniuk 05.03.2010 | check out midikatapult.com if you are wondering about some advanced use for the LP |
| Sharolyn Narramore 05.03.2010 | the sliding is possible but only in certain applications(ableton, monome apps). I havent seen it implemented in a traktor setup but anythings possible nowadays. regarding the LP's pads. They are a bit clicky/mushy for me. If you've ever used mpc pads, there is a slight "click" there but the pads are nice and stiff. The LPs pad are waaaaaaay mushier to me. When u hit a pad you'll feel it sink down and then click, it doesnt affect drumming/cueing though. Other then that the LP is top notch, you should really get to a store and try it out in person. |
| Susann Blachford 05.03.2010 | Hey guys, I've been believeing about getting a launchpad. For you guys that own one, you know the demo video where the guy slides his finger across the launchpad effortlessly and uses the buttons like faders? I just wanted to know if this was actually possible, or just something they kinda faked. I've heard complaints that launchpad buttons were too clicky for this...whats the feel of the buttons? |
| Reece Murray 04.03.2010 | Dude, my bad- it's been ages since I looked at this. You're totally right, it's one beat, not one bar. I got the idea of sequential confused with when they were needed. (The tsi that I have this built into simply moves between 4 leds in a square pattern, so it looks like a rotation). As you said, something like a clock counter thru bomes could get the functionality how you want it. |
| marija dunn 04.03.2010 | Thx, it seems though that my beat phase output makes one cycle per beat, not per bar ... which of course is essential for this to work. Atm I have traktor pro 1.2.4. |
| Reece Murray 03.03.2010 | No problem. Set an output command of Beat Phase Monitor to the first led you want to light. Set the midi range from 0 min, to whatever maximum you want to designate as the color. The controller range sets when in the 1 bar cycle you want the led to light, and for how long. So if the first led is set to 0.00 min to 0.20 max, you get a flash starting on beat one for a duration of almost one beat. The next Beat Phase Monitor output will be set to the next note # you want to light, with a range for example of 0.25 min to 0.45 max. This would set off the next led 0.05 of a bar after the first, also with a duration of 0.20. Get the idea? The ranges can overlap too, but the limitation of this command is data from one bar. So you could have 8 or more leds fire off in sequence, but the cycle would repeat after one bar. The range control is kind of weird too - it doesn't go from 0.00 to 1.00, but I believe it's actually -0.50 to +0.50, so keep that in mind. But the cycle still starts at 0.00. Then it goes up to +0.50 (which is the same as -0.50), and counts back up towards zero. So a series of leds could be 1) 0 to 0.20, 2) 0.25 to 0.45, 3) -0.50 to -0.30, 4) -0.25 to -0.05 |
| marija dunn 03.03.2010 | @Zac Kyoti: If you find the time, I would like to know how you did that, and I believe ju1c380x would appreciate an explanation also. If you dont find time, then would you be so kind to attach that tsi, I will try to figure it out myself. thx |
| Reece Murray 02.03.2010 | @ejac: I have the sequential led lighting programmed into one of my tsi's right now. So I know it works. Granted it's only for one bar. No additional midi routing, no Bomes. |
| marija dunn 02.03.2010 | Afaik sequentially lighting the leds to the beat is not possible with traktor alone, even for one bar. For this to work there should be a way to count the beats (probably using a modifier, so you can use it as a conditional, afaik there is no other way). Beats could only be counted using the beat phase output, but afaik there is no way to use the beat phase to set/adjust a modifier. The shortest way around this would be to use a virtual midi cable, output the beat phase to it, and receive it back in traktor again, where you use it to increase a modifier. Then use play/pauze to reset the modifier. Then use that modifier as conditional to output the beat phase to specific pads on the launchpad, so that depending on the modifier state a certain led blinks to the beat. Or just use modifier output to set the led color, that way the led stays lit until the next beat, is more sequencer like. Then there is the issue of loops, also a fun believeing exercise, and a lot of programming work to get that one right when I dare believe about its implementation. |
| Reece Murray 01.03.2010 |
Originally Posted by ju1c380x
|
| marija dunn 01.03.2010 |
Originally Posted by ju1c380x
Originally Posted by ju1c380x
The first beat might be associated by when a track starts playing, given you always start a track on a down beat. I wouldnt know atm how to detect the midi clock signal. You could only use this signal if you use the master clock in traktor and sync your tracks to it. The beat phase is dependent on a particular track, and can be output by a midi cc or note signal in traktors controller manager. (as you probably know, but that makes I would know how to receive this in another program) You could use bome's midi translator or max/msp (maybe others i dont know about?) in combination with a virtual midi cable to receive these messages, and produce the appropriate output midi messages to your launchpad. But a complete explanation on how to do this in one of these would be a lot of work (i wouldn't know without making "a patch" myself). Also, these programs aren't free. |
| Roxanna Supancic 02.03.2010 |
Originally Posted by ejac
and i know its not possible with just traktor. im not talking about a beat phase monitor, im talking about like on beat one the volume arrow LED on the launch pad would light up lets say red. then on beat 2 the first arrow LED would shut off and the one below it (the pan arrow) would light up red and they would continue to do that down all 8 arrows and then repeat (hence the sequencer) what i want to know is HOW is this possible and what do i need to do to get this to work. hope this clears stuff up and thanks for the help ! |
| marija dunn 01.03.2010 | I was wondering what that beat phase monitor did exactly, the manual or its addendum don't give an explanation afaik, and I haven't had the opportunity to try it. It would be a nice idea to let the playbutton pulse to the beat, I do accidentally push the wrong play/pauze button when I'm in a hurry, the pulsing would definitely help diminish that. |
| Reece Murray 01.03.2010 |
Originally Posted by ju1c380x
I like having a beat synced led for each individual deck though (mostly just an indicator to me if a deck is stopped or playing, but it's a nice quick indicator of synchronization too). |
| marija dunn 01.03.2010 | @ju1c380x: plz explain
|
| Roxanna Supancic 27.02.2010 | QUESTION: is it possible to have the vol-arm arrows LED sequence to the beat ? what i mean is for beat one the vol arrow LED lights up a color, then next beat the pan arrow below it lights up and the one above it turns off and so on. if possible could someone tell me how to achieve this ? btw this is the greatest thread on the greatest website |
| Kellye Bakker 22.02.2010 | @ejac Hey I got it right finally. I disabled all the launchpad controls and realized traktor was still reacting to some launchpad's keys so i found out the problem was in the midi configuration of my korg zero8 wich was "all midi ports" in "in" and "out" configurations. Thanks for the help I'm gonna shred it tomorrow's evening gig xDD |
| Cherryl Coyle 21.02.2010 | I'm tempted to try mapping my launchpad like the MIDIFighter...hrm.. |
| marija dunn 17.02.2010 | I got that info from the launchpad programmer's reference on the novation site. They use the term amber for yellow. Lets see what 126 means 126 is in binary 1111110 following the reference, they say that bit 6 (its the first bit, they give the bits following nrs: 6 5 4 3 2 1 0) should always be 0, don't believe they explain why, yours is 1, don't know what effect that has. bit 5 and 4 control the green color (there are 4 possible values with 2 bits: 0 0 = 0 = off; 0 1 = 1 = low; 1 0 = 2 = mid; 1 1 = 3 = high) Bit 0 and 1 control the red color in the same way. bit 3 and 4 are used for double buffering (which is important if a lot of leds are updated at the same time, and if i understand correctly can also be used the let the led flash (should get more into that, is a cool feature)), and if not used should be 1, but actually it doesn't seem to really matter. So 126 = 1 11 11 10 is green high (1 1) and red mid (1 0), which results in a bright yellowish color (equal amounts of green and red are apparently called amber) 62 = 0 11 11 10 is the same color, and I mentioned that as a color you can use, but I don't know much about color names... following that logic: 0 11 10 10 = 58 0 11 01 10 = 54 0 11 00 10 = 50 are all also that same bright yellow color (though could be that one of those values will be sent to the buffer and will not update the current color, haven't got my launchpad here to try) |
| Sharleen Binckley 17.02.2010 |
Originally Posted by ejac
|
| marija dunn 17.02.2010 | @dodge: That issue was known: http://djranking s.com/community /showthr...8363#post88363 @MisterMigz: Maybe it wouldn't be a bad idea to link to this in the first post, or update it with corrected versions of the .tsi files. |
| Sharleen Binckley 16.02.2010 | @MisterMigz Really feeling this shit man, nice work. I've changed it around a bit to suit my needs but yeah, top stuff. I understand how everything works now. I even got all the buttons associated with looping (loop in, size, loop active etc) to light up brighter than their regular state when ever loop is activated. It's pretty slick man. By they way I dont know if you had any issues with hot cue buttons not working properly, but I found the controller range needed to be on min 0 and max 5 to get all the cues to work as they should. Might have just been my set up but who knows. Peace |
| marija dunn 16.02.2010 | @evolu7ion_vii Do some work to exclude things: for example disable input for deck A and B settings in traktor, do you still have the problem? yes, then you know its coming from the other settings no, then you know its coming from those settings There are probably other things like that you could try to get closer to the origin of the problem. Try to create the minimal conditions needed to cause this behavior, share them, so other ppl can test it and maybe give useful feedback. Also, I use bome midi translator or a max/msp patch and Maple Virtual Midi Cable to inspect which midi messages are sent exactly. It helps a lot when debugging mappings, or exploring seemingly odd behavior. But it takes some time to set it up and understand. Those programs do much more than only that, maybe there are better tools out there to simply inspect midi messages.. |
| Sharleen Binckley 15.02.2010 | @AnalogDog. Hey man, you got any pics of what you have done with your buttons? I am going to be getting some of those 3M pads like you recommended but would like to see what you have done. Am I right in saying that what you have done is print onto a clear sheet then use the 3M pads to stick down, basically meaning there is a clear print in between the button itself and the 3M sticky pad? Also, unless I missed a post somewhere can you elaborate a bit more on what you are using the spray for? I don't get why you are using a waterproof spray when you have used the 3M pads to stick to the buttons. I'm a bit lost. Thanks in advance for the help |
| Leota Saniuk 15.02.2010 | if you really need those faders the choice is obvious. if you need something mobile get the launchpad. in terms of "hacker" community the launchpad also seems like the better choice. it also should be cheaper. |
| Flor Whysong 14.02.2010 | Hello peeps , Still deciding weather to get Launchpad or APC20 . Both falls <200 What u believe guys ? |
| Kellye Bakker 14.02.2010 | Hello. First of all congrat to the developer, really nice job! I'm experiencing some problems though with the hotcues of decks C and D. By parts: - The problem is only with hotcues keys - Decks A and B work perfectly and do not interfeer with any other deck. - Hotcues in Deck C and D, (some of them), also trigger hotcues in decks A and B - that's the problem. Notes: - All in/out ports are selected to the launchpad - "Device Target"'s are all in "Focus" mode - "Assigment"'s are set to the correspondent deck (A B C & D) In more detail: - Hotcue 1 of Deck C also triggers Hotcue 1 of Deck A - Hotcue 2 of Deck C also triggers Hotcue 2 of Deck A - Hotcue 3 of Deck C works fine - Hotcue 4 of Deck C also triggers Hotcue 4 of Deck A - Hotcue 5 of Deck C also triggers Hotcue 1 of Deck B - Hotcue 6 of Deck C also triggers Hotcue 2 of Deck B - Hotcue 7 of Deck C also triggers Hotcue 3 of Deck B - Hotcue 8 of Deck C also triggers Hotcue 4 of Deck B - Hotcue 1 of Deck D also triggers Hotcue 5 of Deck A - Hotcue 2 of Deck D also triggers Hotcue 6 of Deck A - Hotcue 3 of Deck D also triggers Hotcue 7 of Deck A - Hotcue 4 of Deck D also triggers Hotcue 8 of Deck A - Hotcue 5 of Deck D also triggers Hotcue 5 of Deck B - Hotcue 6 of Deck D also triggers Hotcue 6 of Deck B - Hotcue 7 of Deck D also triggers Hotcue 7 of Deck B - Hotcue 8 of Deck D also triggers Hotcue 8 of Deck B Anyone experiencing this or able to help? Thank you in advance. |
| Casey Ari 08.02.2010 | This thread really delivered! Thanks so much everyone for the useful info. People love the launch pad when they see it they just want to push buttons! |
| marija dunn 04.02.2010 | @AMADO: Check out my updated versions of those .tsi files, there were some errors in the original ones. @lsmith: I also checked out the katapult software, its an ok start, but its far from userfriendly imho, at this point in time it gives too little surplus value for me to pay for it. I was dreaming about such software myself, because of the hassle to program traktor outputs, and above all because of the delay/latency I talked about in my previous post (edit 2 in the above link). But I'm afraid that, for me, Katapult is not the solution, maybe after a few updates it will be... You still have to program traktor outputs, then map them via commands in a textfile to the launchpad. Kind of like the takeover feature, where you can let a fader or knob move from one value to another with some user chosen delay/speed. Also they should add more default settings/mappings, especially if they ask money for it! Their Website and documentation are very ok though. In my vision of the perfect launchpad-traktor helper application, there is a .tsi file for traktor that outputs every parameter traktor can output to a different midi cc/note/..., so the program knows everything that is going on in traktor. Then all assignment can and should be done via learn in the helper application: Learn for input AND output, why not even at the same time. And also traktor control learn like ableton, meaning, that you push a button with your mouse on traktor (the app gets informed because all actions are output to it) and then push a button on the launchpad to assign. Then the sky is the limit . btw, lsmith: Thanks for those other links, very interesting stuff, tried some of them, really fun! EDIT: actually Bome's midi translator does some of the stuff i was dreaming about, trying it out right now some time later: wow, its a very good program, very flexible, midi learn from launchpad and traktor, you can add as many rules as you want, you can use global and local vars to remember stuff, easily disable/re-enable settings, copy-paste a lot, type things in you can also choose from a list (this is not possible in traktor midimapping, grrr). some time later: good as it is to circumvent the latency issues, making several pages to switch between is not that easy: to be able to use pages on the launcpad, bome must remember every output of traktor, which is possible, but bome 1.6 has only 72 global variables, so not enough to remember all settings. There is a workaround with a modulo operator or bitwise comparison, so several values can be stored in one variable, but it will make it not easy to understand, extend, maintain, ... And bome doesnt have these operators, but they could be simulated with the operators it has So new approach: gonna try max/msp. Have worked with puredate a free alternative, so i hope to get some results. some time later: took some time to get anything going, but managed to make 2 pages with each 1 button, which led gets updated on page change . So I'll probably be able to make what I want, and hopefully be able to share it here |
<< Back to Post and find Controller MappingsReply