[monokinetic]

Hello all,
I think I may have found a problem with transmitting SysEx using MBSeqV4. I'm running version 4.054.

I have the MBSeq set up to use the router function to send MIDI from USB1 > OUT1 and IN1 > USB1, because I wanted to send SysEx from my Mac to my MB FM while using the MBSeq but I just couldn't get the SysEx to work. So decided to monitor the SysEx coming out of the MBSeq and compare it to what my other MIDI interface - a MIDISPORT2x2 - sends.

Here's the results:

with MIDISPORT OUT A connected back to MIDISPORT IN A =

[MIDI OUT][13:10:17:000042]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7]
[MIDI IN ][13:10:17:000052]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 06 08 00 1c 01 f7]

with MBSeq OUT 1 connected to MIDISPORT IN A =

[MIDI OUT][13:08:49:000819]: [MIDIbox SEQ V4 Port 1][f0 00 00 7e 49 00 06 08 00 1c 02 f7]
[MIDI IN ][13:08:49:000833]: [MIDISPORT 2x2 Port A][f0 00 00 7e 49 00 7e 49 00 06 08 00 06 08 00 1c 02 f7]
[MIDI IN ][13:08:49:000834]: [MIDISPORT 2x2 Port A][f0 1c 02 f7]

I've tried this test with 2 different pieces of software now (Cubase 6 and Ctrlr v5), exactly the same behaviour.

My guess is that something is wrong here. Any ideas?

David

[TK.]

Hi David,

I remember that I had similar SysEx issues with my MIDIsport2x2 on a Mac back in January.
They vanished after I used a GM5 based MIDI interface instead - haven't used the MIDIsport2x2 anymore...
It was working very reliable under Win98 and WinXP years ago, but it seems that the Mac driver is buggy.

MBFM SysEx transfers via MBSEQ: you have to assign a different device ID either to MBFM or MBSEQ.

Best Regards, Thorsten.

[igi]

Hi!

I also have a problem with sending sysex thru MBseq V4 4.054.
Router: IN:USB Ch1. OUT:out4(any) ch.1

On MIDI monitor is show incoming SYSex, but on out port only on start and stop sysex massage is shown.
I try use C6 and PCto550, but all the same.
I have no problems sending sysex directly without MB SEQ V4.
I'm using PC with win XP.

Thanks and Best regards, IGI