|previous by date||index||next by date|
|previous in topic||topic list|
>> I'm using a PC-1600x, a Rev. 1 MKS-80, a Studio 5LX, and running OMSThe Studio 5LX works fine without Cubase, using a patch that sends the
>> 2.3.8 and Cubase Audio XT 3.0.7 PPC on an 8100/110.
>> Yes, thank you, that solved the problem. When I connected the PC-1600x
>> directly to the MKS-80 everything worked fine. "STUPID @$%#&!! OPCODE!!"
>> Yet, I swore to soon. The Studio 5LX wasn't the problem.
>Actually I have Studio 5LX now (and a Studio 4 before it when I was
>messing with the Peavy which shares most oif the 5's concepts). The
>thing is the manuals are kind of thick and get into all kinds of obscure
>features not how to get something simple running. This might be your
>problem, I know I've run into other people on the net who like I did
>essentially thought the same---
>> As it turns out, Cubase is the problem. It's clearly buggy. It canIn mode III (SysEx mode), my MKS-80 seems to echo everything thru its MIDI
>> record parameter values from 0 to 100, it can play back parameter values
>> from 0 to 100, but it can't thru parameter values from 0 to 100 (or play
>> them while recording). This doesn't come as much as a shock as one would
>> think. Until version 3.0.7 Cubase couldn't even record SysEx through
>> "STUPID %$#@&∗!! STEINBERG!!!"
> The MKS I believe echos the SYSEX back out it's MIDI out so you want to
>be very wary if you have the midi out on the MKS going to back into the
>I don't know whats going on with cubase but I'd think it would justYou would think so, but apparently that isn't the case. Cubase seems to
>record the sysex or not or choke, not interpret it to filter out values
>burried in a Sysex string without a lot of special code.
>We aren't talking about CC#s where this sort of filtering is commonplace.I don't think its specifically intentional, although I agree something
>The parameter values for the MKS contained in the SYSEX are within a string
>of several bytes which changes from company to company, I don't think
>its realistic that Steinberg is saying hey lets interpret this whole
>sysex string unique to the MKS just to drop the higher values but leave
>the rest alone so it still makes the MKS respond, something more messed
>up is going on.
>(or maybe you are looking at hex numbers when you thinkThat's not it -- I'm looking at the MKS-80's LCD display.
>you are seeing decimal numbers)