Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: TouchOSC + Osculator + Traktor...how to make a LED work?

  1. #1

    TouchOSC + Osculator + Traktor...how to make a LED work?

    Hello guys, i will explain the example i wanna get...
    I use traktor scratch pro with my own mapping of touchosc / osculator.
    I have for example the LOOP SET parameter in traktor, only works fine with a PUSH button from touchOSC, when i click on the parameter LOOP gets activated in traktor, but i cant see any led or something that advise me that the LOOP IS ON. Just wanna get this working, i mean, click on the loop button, the loop begins, the led turns on, i click again on the loop button, the loop ends, the led turns off.
    I know it has to be a message back from Traktor maybe? by creating a /midi/cc.... but how to setup the led to response with the push button?
    Many thanks!

  2. #2
    I made the led work by assignating a chanel to it and creating a manual message on Osculator with the "/midi/cc...." the problem is that the LED is not staying HOLD. i press the LOOP button and the led illuminates for less than a second, how to make the led stay on during the loop is on?? thanks

  3. #3
    You might want to check what is the value of the MIDI message you receive by opening a Quick Look window (press space bar on the /midi/cc message you want to monitor). If it is not steadily running at max value (or 127) when the loop is playing this might explain why it only stays on for a short moment. There is a similar "issue" with Live.
    To solve the problem you can change the scaling on the MIDI message by showing the scalings page (Command-F).
    Besides, I think I've I've seen that TouchOSC now lights on a LED for every value greater than 0, this is with the latest version.

  4. #4
    basically, you just have to create a routing "out" of traktor... that will be routed by touchOSC back into the ipad. Route this to the LED or, better, route it back to your LOOP button. It doesn't matter if it's a push or a toggle button, it'll be "on" as long as your loop is active.

    Hope this helps.

  5. #5
    hey there.

    i have a problem with traktor sending a led output to osculator, too.

    i basically copied the midifighter layout from djtechtools to a page of touchosc and it works like a charme, except the led feedback.

    for example. i have one button (push16, midi note D#2) which play/pauses a track in traktor.
    in the traktor mapping there's a out for play/pause but the button in touchosc doent light up constantly. (in traktor the mapping is actually D#3 for in and out)
    when i press it, it lights, when i remove my finger it switches back to unlit.
    i messed around with the settings with no luck..

    btw i got a normal led to light up (beat phase monitor), so touchosc receives data..

    thanks fpr helping

  6. #6
    well, i got this far:

    by implementing a /1/push on an osc routing on trigger, i got the play button to light up, but only when i press play in the software. if i press play in touchosc it blinks as long as i have my finger on it.. what to do?

    besides that problem, it seems that i only can get one led per midi channel. if i map a led in osculator a new entry comes up: /midi/note3 (for channel 3) but every other output note on that channel triggers the same entry.. i'm confused..
    Last edited by weltraumpapst; 03-23-2011 at 11:35 AM.

  7. #7
    Hi,

    I think it has to do with the MIDI values send by Traktor which are not sustained through all the playing. Ableton Live has a similar behavior (which is discussed here).

    Basically, you would need to the change the scaling of the /midi/ccX/Y message so that it will send a positive value at all times.

    You might also want to try this other solution: change your OSC Routing in the OSC Routing Editor and set "Route when:" to "The value crosses 0.5 in any direction" (cf screenshot). I think that would prevent the routing from being triggered with a value that would not light the led.

    Because Traktor and Live are not the same, I can't telle exactly how the previous suggestions need to be tweaked in order to make it work. Use the Quick Look windows to see what is sent from Traktor, and modify your settings accordingly.

    Best,
    Cam
    Attached Images Attached Images

  8. #8
    thanks for the reply.. ill try that..

    do you have an answer to this?

    "besides that problem, it seems that i only can get one led per midi channel. if i map a led in osculator a new entry comes up: /midi/note3 (for channel 3) but every other output note on that channel triggers the same entry.. i'm confused.. "
    Last edited by weltraumpapst; 03-23-2011 at 08:02 PM.

  9. #9
    changing to ""The value crosses 0.5 in any direction" didnt help

    just to clear up:

    it is right to just map the "velocity" value to a oscrouting or do i have to map trigger or the whole midi/note/x ?
    Last edited by weltraumpapst; 03-23-2011 at 08:15 PM.

  10. #10
    Sorry, I missed that point.
    As you found out the /midi/note message contains information for every channel.
    You need to extract the information from that message in order to separate the different channels.
    To do that, select the "channel" argument of the note message, and do Edit->Demux. Then send notes again (by activating the command in Traktor that send the notes I guess). This will reveal the sub messages that are specific to each channel.

    Let me know if that answered your question.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •