Page 1 of 2 12 LastLast
Results 1 to 10 of 20

Thread: ThumbJam (iPhone) w/ OSCulator - only two Event Types available

  1. #1

    ThumbJam (iPhone) w/ OSCulator - only two Event Types available

    I have had OSCulator working fine with OSCemote so I'm confident OSCulator is working fine.

    I haven't been able to find much information about this online, so I assume OSC support in Thumb Jam is pretty new and it's early days yet. That said I've tried to get ThumbJam to talk to OSCulator so that I can convert to MIDI and use it to drive Reason. I'm able to get an OSC connection and when I send a note from ThumbJam I get the following messages appearing in OSCulator:


    And all four entries show a 'yellow square' to indicate activity. So that's good.

    However when I click on 'Event Type' in the column to the right, the drop-down menu only contains two selectable entries: "OSC Routing" and "Console Log". This is in direct contract with the menu I see when using OSCemote, which shows a *lot* of possibilities, including MIDI CC messages.

    I spent quite a while exploring OSCulator, reading the manual (did I miss something?), and comparing OSCemote configurations with my new one, but I haven't been able to get past this, so I'm turning to the forums for help. Does anyone know why OSCulator only has these two supported Event Types for these incoming ThumbJam messages?

  2. #2
    It looks like a nice application, full of features, I'll have to try it!
    By reading the user guide, I can give you some hints:

    Actually, you should have access to four menus. This has to do with the nature of OSC message. The OSC message you are seeing is composed of 3 arguments. So you have a menu to act on the message with all of its arguments (/tj/1/note), and you can also act on the three arguments.

    The menu you are referring to if the message configuration. It is most of the time not useful, unless you want to do something with the OSC message as a whole. This is why you can only route it (OSC Routing), or print it (Console Log).

    If you try to assign an event to one of the three arguments, you will have access to the Events that deals with numeric values. In Thumbjam's user's manual, the arguments of this message are described to be:
    • 0 = note pitch
    • 1 = velocity
    • 2 = on / off status

    In OSCulator, the way to use this data is as follows :
    • On the first argument (0), assign an Event type "Note Param" and use "Pitch" as the value
    • Second argument (1), use "Note Param" with "Velocity"
    • For the third argument (2), use a "MIDI Note w/ Params" event and use "/tj/1/note" as the Value. This will tell OSCulator to fetch the note parameters from the /tj/1/note message.

    This should generate MIDI note as desired.
    As I have not tried yet, there is a small adjustment you might need to do. Thumbjam's manual says that the first argument output the note as MIDI values (0 to 127), therefore if you think the notes do not sound normally, you might have to adjust the input scaling. To do this, flip to the scalings view (Command-F), and change the Input Max value of the first argument (0) to 127 instead of 1.0. Remember to do this only if it is needed.

    I hope this answers your question.

    For more information on OSC messages :
    And on MIDI Notes with Parameters :


  3. #3
    Thank you Cam, that's excellent info and it has enabled me to get some promising results. For some reason I had missed that you could set Event Types for 0,1,2.

    I do find that I need to make an adjustment - however it's not 0-127 as you suggest, it seems to be 0-24, although it is an octave too high. I'm still playing around with this and hope to find the right range soon.

    Also, ThumbJam seems to send multiple messages during sustain, perhaps because it is trying to send pitch-bend messages as I slightly tilt the iPhone. I turned off the sending of pitchbend via OSC but it still seems to send them. Is it possible to somehow filter these messages in OSCulator so that they don't retrigger MIDI notes?

    Thanks again!

  4. #4
    Hmm, not quite understanding the range translation - I find that changing the top or bottom limits affects the entire range. I had something at 52-93 that seemed to map around C0, but C1 was wrong, and when I change the upper limit it seems to change where C0 maps to. There's something about the way this maps that I'm not understanding.

    Is there some sort of 'real-time debugging view' or 'log' that I can use to see how the translation is happening so that I can understand the mapping?

    Do I need to adjust the output range too, or keep that as 0.0 to 1.0?

  5. #5
    For reference, I've also posted about this on the ThumbJam forums, here:

  6. #6
    Very good analysis.
    And good job using the MIDI debug mode.

  7. #7

    It's weird that the OSCulator patch I created is so similar to the one that Jesse created, and yet mine behaves differently - if you feel inclined, maybe you could download both patches and see what the internal difference between them is?

  8. #8
    Sure, please attach the files on this forum, I'll have a try!
    You can also send them by email if you prefer (camille at osculator dot net).

  9. #9
    Ok, I have attached two zip files.

    The first - "" - is my attempt at a simple OSCulator patch.

    The second - "" - is the TJ author's patch, that he created in response to my question on the TJ forum. You can see all the details on that site I linked to before.

    Both patches *appear* very similar in OSCulator - apart from the Console Log event - yet behave quite differently. I'd be interested to know if the files differ internally in some subtle way that would explain the difference in behaviour. Thanks! :)
    Attached Files Attached Files

  10. #10

    There is a difference in the two files which is the address of the note message.
    One file has the /tj/1/note message, and in the other it is /tj/note.

    However I have noticed a cool thing:

    Thumbjam is able to send a MIDI stream over OSC, and OSCulator has a built-in OSC to MIDI decoder. When you see the message /tj/midi, click on the Event Type menu and choose Send to MIDI.
    In the Value column, choose the value corresponding to the MIDI out you want to use (either a physical interface or OSCulator's virtual output).

    This should enable you to use the full MIDI capabilities of Thumbjam without having to deal with the MIDI Note /w Params.


Page 1 of 2 12 LastLast

Tags for this Thread


Posting Permissions

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