Digital Performer 1.41Y

[P.O.]

Jeez, I can' believe Yamaha went for such a sick, twisted numbering scheme for the CBX sysex data!!

Where one byte would have perfectly done the job they decided to split the data byte, put the low nybble and high nybble each in their own byte, pad each with $30, and call the job done!

that confirmed by my own notes from 15 years ago I stumbled upon, and by the sysex stucture unveiled by IIO. If the data value is zero, it gives you two bytes values of $30 each. depraved!

I'm still trying to understand the sysex format for the CBX. I'll setup a system where I can intercept and read the MIDI packets going to it.

[cyberish]

Does this guy knows about? : https://www.youtube.com/watch?v=nuu1oxEcZuE

[IIO]

if he had a textfile with just a list of the sysex control data  that could help to save a lot of work.

[P.O.]

here we go:
----------------------------------------------------
here are my observations on the sysex MIDI messages sent by "MixdownCBX-D5" to CBX.

Source switch set to "DAT"
F0 43 78 40 00 40 00 00 02 30 32 F7

Source switch set to "analog"
F0 43 78 40 00 40 00 00 02 30 33 F7


first four are always the same. F0 Sysex header, 43 78 Yamaha ID and sub-ID, 40 parameter dump.
next 00 is channel nr. 40 denotes a "common" parameter (most of the time it is 00, ch message)
00 is parameter nr. 00 02 is byte count (never changes), 30 32 are the parameter's value, in Yamaha's twisted value (zero is 30 30, 127 is 37 46), F7 is sysex trailer.

ch. 1's volume set to "0"
F0 43 78 40 00 00 0C 00 02 30 30 F7

ch. 1's volume set to "127"
F0 43 78 40 00 00 0C 00 02 37 46 F7

ch. 1's volume (in "FX sends" block) set to "0"
F0 43 78 40 00 00 06 00 02 30 30 F7

ch. 1's send 1 (in "FX sends" block) set to "0"
F0 43 78 40 00 00 10 00 02 30 30 F7

ch. 1's send 2 (in "FX sends" block) set to "0"
F0 43 78 40 00 00 11 00 02 30 30 F7

ch. 2's volume (in "FX sends" block) set to "0"
F0 43 78 40 01 00 06 00 02 30 30 F7

ch. 2's send 1 (in "FX sends" block) set to "0"
F0 43 78 40 01 00 10 00 02 30 30 F7

ch. 2's send 2 (in "FX sends" block) set to "0"
F0 43 78 40 01 00 11 00 02 30 30 F7

FX return "FX 1L" vol 1 set to 0 (note this is a "common" parameter)
F0 43 78 40 00 40 14 00 02 30 30 F7

FX return "FX 1L" assigned to "out 2"  (note this is a "common" parameter)
F0 43 78 40 00 40 0C 00 02 30 31 F7

FX return "FX 1R" vol 1 set to 0 (note this is a "common" parameter)
F0 43 78 40 00 40 16 00 02 30 30 F7

FX return "FX 1R" assigned to "out 2"  (note this is a "common" parameter)
F0 43 78 40 00 40 0E 00 02 30 31 F7

FX nr change to 1
F0 43 78 40 00 40 27 00 02 30 31 F7

EQ mode "on" (DEQ)
F0 43 78 40 00 40 20 00 02 30 32 F7

EQ mode "off" (THRU)
F0 43 78 40 00 40 20 00 02 30 31 F7
------------------------------------------------------

I still can't put my finger on that elusive "input rec monitor" thing...  it should be
F0 43 78 40 00 00 00 00 02 30 31 F7 for ch1 and
F0 43 78 40 01 00 11 00 02 30 31 F7 for ch 2, but it doesn't work!!!
When I arm the tracks in Logic Audio, the switch works because I see audio on the output meters, but NO MIDI command gets sent!
I'm stumped by this one. Very frustrating, as this command is crucial to the project.

P.O.

[P.O.]

As for the guy on YouTube, he has made himself a neat SYSEX-sending editor for his CBX. For the video, he plays an audio loop probably from a hard drive. What we want to do is process audio from the CBX's analog input: that's the crucial thing we're stumbling on.
Granted, if we could put our hands on his editor, our job would be mostly done. But it works in windoze

[P.O.]

Here is a map of most of the parameter numbers as seen on the "MixdownCBX-D5" panel:
first, all the numbers are in decimal, NOT hex.
numbers in the white circles are CHANNEL parameters, and they're repeated for each channel block (but with different channel numbers, sysex's string fifth position)
numbers in yellow circles are COMMON parameters, channel numbers do not apply and these commands are the ones with hex40 in sysex's string sixth position.

P.O.

[IIO]

– post edited because i wrote bullshit –

if you look at my test patch again you will see that i am also using hex values.
simply because in many manuals the chart is in hex, too.

so where it says...

Source switch set to "DAT"
F0 43 78 40 00 40 00 00 02 30 32 F7

Source switch set to "analog"
F0 43 78 40 00 40 00 00 02 30 33 F7

...i would love to have a source for this data in the form of a text file:

"Source Switch",
DAT,
0 30 32

"Source Switch",
Analog,
0 30 33

where 0 is the parameter number and the rest the value,

and similar for parameters with 7 or 14 bits of range e.g.

"Lowpass Filter A",
Frequency

...where the missing parameter values mean the range of 0x00 - 0x7F.
 
-

there are several ways how to find out what data is needed for a device.
one method is the manual, the other method is using a soft- or hardware (such as a max patch or your masterkeyboard) which reads what the device is responding to requests.

but both methods are not perfect. for example you still have to type all the nickname of the parameters yourself in both cases. compared to VST parameters in a sofware, dealing with MIDIfied parameters of a hardware device always is a pain in the ass.

the main thing what worries me (and stops me from building a bunch of editors for myself) is that both, a manual or the request responses can be still incomplete.

and it really sucks to start a range of 2 or 7 bit with 48 50 ... that doesnt make any sense to somebody who started with programming on a personal computer in 2001 and not on a midi hardware in 1984. today anyone would represent a 7 bit parameter in the range of 0 0 to 0 127 or 0x00 to 0x7F.

[supernova777]

P.O.>>.
any chance of you actually sharing the studio vision pro 3.0 disks?
i use mediafire.com but any filesharing service will work as long as u put inside a stuffit file
or macbinary the cd image (hopefully using adaptec toast 4.0?)

[P.O.]

Sorry I haven't been here in a while...

I remember I started working on a package some while ago, but I didn't get to finish it. It's not an easy thing, as it's not on a CD, but diskettes!

I hope to get around this by fall. right now I have way too many projects going on...

[GaryN]

P.O.>>.
any chance of you actually sharing the studio vision pro 3.0 disks?
i use mediafire.com but any filesharing service will work as long as u put inside a stuffit file
or macbinary the cd image (hopefully using adaptec toast 4.0?)

You now know that won't work…

[MacTron]

I have a Studio Vision Pro v2.08 and Vision 3.0.3 cracks. I have never tried them. I can attach them if someone is interested in trying them.

[supernova777]

I have a Studio Vision Pro v2.08 and Vision 3.0.3 cracks. I have never tried them. I can attach them if someone is interested in trying them.

does anyone have the install sources for those version?

[cyberish]

Did anybody here went further with those CBX-D5 investigations? 

[P.O.]

This quest is stuck by the inability to switch the "rec monitor" from digital to analog. It is the first, necessary step that will allow us to use the CBX as an external processor box. The rest after that should be easy pie, but I have not succeded in cracking this function.

[cyberish]

I've a the original installation floppies (2 of them) of the CBX extension for Logic 2.5. Could this be of any help?
(Actually how do I properly copy a floppy into a floppy image? )

[supernova777]

by using the program "diskCopy" to create a .img file?

[IIO]

actually i think one should just get a TC fireworx or a H3000 instead.

[P.O.]

IIO, I have no TC fireworx or a H3000. I have a CBX-D5. The idea here is to make good of hardware that would otherwise be boat anchor.

Cyberish, the CBX extension might be pertinent if you got Logic, but in this case I'm not sure it would be of any use. I think CBX support was incorporated into Logic afterwards... I do think you should nevertheless upload it here, as I'm sure someone will eventually need it.

[supernova777]

I have no TC fireworx or a H3000. I have a CBX-D5. The idea here is to make good of hardware that would otherwise be boat anchor.

cant u just simply use the cbx-d5 in the way in which it was originally meant to be used + have it fucntion normally?

[P.O.]

The CBX-D5 is a 2 in, 4 out audio converter/processor that works with SCSI.
For doing digital audio, I have MUCH lighter/compact/capable/dependable systems to do that now. Not counting the fact that software to use the CBX are very few, very limited, and quite unstable. What is of interest in that machine is the built-in audio processor, which is like a SPX-900. If it could be just be used as an external SPX-900, I'd have something of useful.