8 Replies Latest reply: Sep 17, 2008 10:37 PM by sbgb
sbgb Level 1 Level 1 (0 points)
Hello, I am trying to record sysex midi dumps FROM (Jomox Xbase888) TO Logic Pro 8 but I can't get the two devices to communicate. Can somebody help out? Many thanks. Seb

Mac Pro, Mac OS X (10.4.11)
  • 1. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    Bee Jay Level 6 Level 6 (10,895 points)
    Connect the MIDI OUT of your Jomox to a spare MIDI IN connected to your computer.

    Select a track that's not routed out of Logic anywhere - the safest way is to control-click on a track, select reasign track object and choose "No output". This means Logic won't echo through the incoming sysex back out again.

    Hit record in Logic.

    Initiate the dump from the Jomox.

    When done, you should see a new region appear in Logic with one or more little "x" symbols in it - these are the sysex events.

    If you don't get these, check you aren't filtering sysex events in Logic's preferences or the MIDI interface you are using.
  • 2. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    sbgb Level 1 Level 1 (0 points)
    thanks for the quick reply. I haven't been able to work it. Apparently logic pro is known to make problems with sysex data (?) Jomox said the sysex dumper tool can also record sysex from the 888. Do you know this program?
  • 3. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    Bee Jay Level 6 Level 6 (10,895 points)
    I never had problems with sysex dumps in Logic for fifteen years, even big dumps.

    El Schwartzerini said on another forum there was a known bug with sysex that I haven't encountered or been able to recreate - but that's not the source of your troubles anyway if you just can't record sysex. When you start a dump, do you see "x" events in the transport? If not, Logic is not seeing the sysex so you are filtering it out somewhere.
  • 4. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    sbgb Level 1 Level 1 (0 points)
    OK - after a few tweaks, I finally got that "x" event in the transport bar (though now it's displayed with a "v" (little check mark) instead AND (no data inside the bar)

    What I want in the end is for Logic to reproduce EXACTLY the sequence in the 888 sequencer without having to use the 888 internal sequencer (set on MID). THANKS. S.
  • 5. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    Bee Jay Level 6 Level 6 (10,895 points)
    What I want in the end is for Logic to reproduce EXACTLY the sequence in the 888 sequencer without having to use the 888 internal sequencer (set on MID)


    Well that's nothing to do with sysex - sysex just saves a backup of the devices' memory contents to Logic. Logic can't do anything with it.

    What you need to do is sync the two devices via MIDI and record the notes from one to the other.
  • 6. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    sbgb Level 1 Level 1 (0 points)
    Well, I was told that I would get the same (ext. 888 sequencer feel) when reading the sysex data. Inputting the midi notes into Logic doesn't get me the same result or vibe compared to when the two devices are synced.
    1/How can I record the sequence directly to Logic? (In the past, I've created drums patterns directly from Logic - today, I realize I want to create them 888 and export them to Logic?

    2/ How do I set Logic so that the 888 starts with STEP 1 every time I press PLSAY in Logic? (No matter I am in the track)
    When in sync mode, the 888 devices will start ON TIME on 1 (cycle range) but I try to start anywhere else in the track, it won't sync anymore, the 888 patterns will start on a random order.

    3/ The 888 won't sync with Logic unless I set Logic's "Delay transmission" parameter to -36ms -- is this normal? Shouldn't newer devices sync directly?

    Many thanks in advance for your answers Sébastien
  • 7. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    Bee Jay Level 6 Level 6 (10,895 points)
    Well, I was told that I would get the same (ext. 888 sequencer feel) when reading the sysex data.


    Sysex is not a way to transfer files between different devices, it is a way to back up a particular devices' data. Logic does not *see into* or understand any data in a sysex dump, it simply records it, or plays it back. You cannot transfer sequences into another sequencer or DAW using sysex. You have to do it via MIDI, or any MIDI file/export/import that the device in question has.

    Inputting the midi notes into Logic doesn't get me the same result or vibe compared to when the two devices are synced.


    Probably because you are trying to dump the whole sequence at once, and you are running out of MIDI bandwidth (or you are quantising in Logic on the way in). Play in a part at a time for better timing.

    When in sync mode, the 888 devices will start ON TIME on 1 (cycle range) but I try to start anywhere else in the track, it won't sync anymore, the 888 patterns will start on a random order.


    MIDI clock does not carry position info at all, it simply caries timing. If your device supports Song Position Pointers, that will work, or better still, use MIDI Time Code instead of MIDI clock.

    Logic supports all these things, but whether your other device does I don't know - check it's manual.

    The 888 won't sync with Logic unless I set Logic's "Delay transmission" parameter to -36ms -- is this normal?


    Dunno, it depends on your device, or whether you have any latency inducing plugins running that's delaying Logic's audio stream...
  • 8. Re: Problems with sysex midi dumps (Jomox Xbase 888 > Logic Pro 8)
    sbgb Level 1 Level 1 (0 points)
    I will follow your advice and look into all of this further. Thank you. S.