Problem with MCU display sysex

husker · Post by **husker** » Thu Oct 13, 2005 6:56 am

Hi there,

I have developed a small application to to emulate the MCU display, for use in conjunction with MCU emulation on devices like the Behringer BCR/BCF2000.

Link here: http://www.xmlconsulting.co.nz/husker/huskervu.htm

One of the users of the app is experiencing a problem with the top line of the display not updating reliably.

I actually get the same problem on my laptop, but not on my music PC.

I've traced it to a problem in Live itself. Even without running huskervu, and just monitoring sysex with MIDI-OX I can still see the problem.

Typically you should see both lines refreshed, like this:

00034BF8 1 -- F0 Buffer: 64 Bytes System Exclusive

SYSX: F0 00 00 66 14 12 00 31 41 75 64 69 6F 20 32 65 77 72

SYSX: 77 72 20 33 41 75 64 69 6F 20 34 41 75 64 69 6F 20 35

SYSX: 4D 49 44 49 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 F7

00034BF8 1 -- F0 Buffer: 64 Bytes System Exclusive

SYSX: F0 00 00 66 14 12 38 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 F7

If you see the 12 00 in the first sysex, then the 12 38 in the second, you can see the start character as its supposed to be.

When it goes bad, this is what happens:

0005032A 1 -- F0 Buffer: 64 Bytes System Exclusive

SYSX: F0 00 00 66 14 12 38 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 F7

0005032A 1 -- F0 Buffer: 64 Bytes System Exclusive

SYSX: F0 00 00 66 14 12 38 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20

SYSX: 20 20 20 20 20 20 20 20 20 F7

You just get line 2 repeated.

Interesting to note, that it only happens if you have an audio driver enabled.

Let me know if you need any further info.

Namihei · Post by **Namihei** » Sun Oct 16, 2005 6:07 am

This is a serious problem for me.
I wish 5.0.3 come soon.

husker · Post by **husker** » Mon Oct 17, 2005 8:15 pm

Hi there Namihei,

I did get a response on this from Ableton from my email sent to [email protected]

They can't recreate the problem at this point, so maybe you can send them an email with details of your setup as well, it may help.

Cheers.

Namihei · Post by **Namihei** » Mon Oct 17, 2005 11:41 pm

thanks,husker

I sent a email to ableton.
My setup is extremely standard.
I can't understand why this problem doesn't happen to everyone.

husker · Post by **husker** » Tue Oct 18, 2005 12:04 am

Something PC specific...everything works fine on my DAW PC, but not on my laptop. Hopefully they can recreate the problem on one of their setups...

funkster1 · Post by **funkster1** » Tue Oct 25, 2005 6:11 pm

Cheers husker,
sorry that I only come back to you now, but I've been away a few days and didn't have the time yet to test the sysex stuff.
However, it also happens on Cubase SX 2.2.0.39 and 3.0.2/3.1.

You say it doesn't happen on your DAW; here it does. And my DAW is extremely well tuned/streamlined, maybe too well?

My friend's PC is very similar to mine and he's using Cubase SX 2/3, while I'm using LIVE 5.02. Could you tell me maybe what services you're running (seems easier/faster than naming the services which are disabled)?

I'll test/monitor SX's sysex output tomorrow afternoon in my friends place and send you the results.

Regards
Raphael

husker · Post by **husker** » Tue Oct 25, 2005 8:13 pm

We may be dealing with a different (or multiple) problems here. The problem in this thread is specific to Live, and can be seen monitoring the sysex in MidiOx event without running huskervu. I know SX sends out bad sysex on occasion, which version 1.0.1 of huskervu seems to cope with (according to djsubject). The Live5 problem is not badly formed sysex as such, it just repeats line 2 and misses out line 1 intermittently.

I don't have any special tuning on my DAW (I don't find it necessary), so as far as services running....all! If huskervu works at all for you, then I don't think services will be a problem/related.

It's all in the sysex, so if you can post the sysex you get that would be great.

cheers.

grfld · Post by **grfld** » Wed Nov 30, 2005 9:42 am

At first: great deal! huskervu solved my biggest problem with live and my behringer bcf2000! And i really like the feature to choose my own font and size for the window.

At second: For me, there's seems to be the same problem with the display update like the one reported above.

Just editing my post... I have the same problems, too.

Just for info: If i use BCFview from Behringer, this bug seems to hang my setup, after this happens, only automatation from live to bcf work, no commands from the controller will be send back to live. I have to restart BCFview and Live.

auboutdurouleau · Post by **auboutdurouleau** » Fri Dec 23, 2005 11:55 am

hi folks !

no solution for this bug ???

CopyRightJustice · Post by **CopyRightJustice** » Tue Feb 28, 2006 12:03 am

no news on this problem

auboutdurouleau · Post by **auboutdurouleau** » Tue Feb 28, 2006 6:02 am

hi juju,

I found a solution for my configuration. It seems to be a midiyoke issue.
I use then one of my "true" midi port on my emu soundcard for midi output from Live and midi input in Bome Translator (feedback preset). I continu to use midiyoke for the others virtual connexions.

ciao

Here's a map of my patch

Input

In: Microkontrol Port A --> Bome Translator
Out: Bome --> Bidule thru Yoke 1
In: Bidule --> Live thru Yoke 2

Output :

Live --> Bome thru EmuPort1
Bome (EmuPort1) --> huskervu thru Yoke 3
Huskervu (Yoke 3) --> MicroKontrol CTRL

Bonus :

I've found that when i monitor Yoke 3 and Mk CTRL through MidiOx, the pads used for navigation (9-16) ----> light on !!!! then i have really usable navigation buttons (start, stop, rec, loop, plug and so on).

All this help me a little bit to wait for a real MicroKontrol support from Ableton or some genious nerd to develop a XP version of the LCXemu.

CopyRightJustice · Post by **CopyRightJustice** » Tue Feb 28, 2006 10:22 am

Thanks I shall try.
Whats the reason for this? is it the through speed of the of the yoke? or maybe the "midi data interval" (bcr2000)setting which adjusts the SysEx transmission rate, assuming the display's use SysEx I'l have a fiddle.

cheers