Page 9 of 20
Posted: Mon Oct 03, 2005 2:19 am
by djsubject
all is well intill the first part of this code kiks in
Code: Select all
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
00064352 1 -- F0 Buffer: 15 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 48 53 6B 69 2D 44 50 31 F7
00064353 1 -- F0 Buffer: 9 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 6B 32 F7
00064F0B 1 -- F0 Buffer: 19 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 01 20 20 20 20 20 20 20 20 20 20 20
SYSX: F7
00065AC3 1 -- F0 Buffer: 43 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 15 20 20 20 20 20 20 20 41 6C 6C 4F
SYSX: 75 74 31 4D 75 6C 74 69 4F 75 56 65 6C 6F 63 69 74 20
SYSX: 56 6F 6C 75 6D 65 F7
then the msg pops up
hope this is of some help
Subz
Posted: Mon Oct 03, 2005 2:47 am
by husker
Hmmmm...that looks OK. Sending the same sysex to huskervu here does not cause a problem. What happens if you restart huskervu when it crashes, and continue on in SX (without restarting SX)? Also, can you try shutting down huskervu before you do the last bit, and see if there is another sysex msg (huskervu crashing may stop MidiOx seeing it).
cheers.
Posted: Mon Oct 03, 2005 3:09 am
by djsubject
husker wrote:Hmmmm...that looks OK. Sending the same sysex to huskervu here does not cause a problem. What happens if you restart huskervu when it crashes, and continue on in SX (without restarting SX)? Also, can you try shutting down huskervu before you do the last bit, and see if there is another sysex msg (huskervu crashing may stop MidiOx seeing it).
cheers.
ok so i closed huskervu & went through 3 channels of vst paramaters
Code: Select all
TIMESTAMP IN PORT STATUS DATA1 DATA2 CHAN NOTE EVENT
003621C9 1 -- F0 Buffer: 17 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 6B 32 F7 53 74 61 74 69 6F 6E F7
003621C9 1 -- F0 Buffer: 9 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 00 4F 53
003621CA 1 -- F0 Buffer: 64 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 00 4F 53 43 76 6F 69 63 4F 53 43 75
SYSX: 6E 69 73 4F 53 43 76 63 6F 64 4F 53 43 70 6F 72 74 4F
SYSX: 53 43 31 32 53 79 4F 53 43 73 74 61 72 4F 53 43 75 6E
SYSX: 69 73 6F 73 63 31 77 61 76 F7
0036289F 1 -- F0 Buffer: 9 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 00 6F 73
003628A0 1 -- F0 Buffer: 64 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 00 6F 73 63 31 6F 63 74 6F 73 63 31
SYSX: 73 65 6D 6F 73 63 31 63 65 6E 6F 73 63 31 6D 6F 64 6F
SYSX: 73 63 20 31 20 31 6F 73 63 31 50 57 4D 6F 73 63 31 50
SYSX: 57 4D 6F 73 63 31 50 57 4D F7
00362EDC 1 -- F0 Buffer: 9 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 04 50 57
00362EDD 1 -- F0 Buffer: 57 Bytes System Exclusive
SYSX: F0 00 00 66 14 12 04 50 57 4D 6F 73 63 32 77 61 76 6F
SYSX: 73 63 32 6F 63 74 6F 73 63 32 73 65 6D 6F 73 63 32 63
SYSX: 65 6E 6F 73 63 32 6D 6F 64 6F 73 63 20 32 20 31 6F 73
SYSX: 63 32 F7
subz
Posted: Mon Oct 03, 2005 3:42 am
by husker
whoaaaaaaaa! that's some seriously f**ked up looking sysex. Do Steinberg have *any* idea what they are doing!?!
Sysex MUST start with F0 and end with F7...
What VST is it... maybe there are some strange characters in the parameter names that SX isn't filtering propertly? Is there a ÷ character in one of the parameters by any chance?
I'll need to do another version of huskervu that ignores such garbage (it should anyway I suppose
)
cheers.
Posted: Mon Oct 03, 2005 7:12 am
by husker
OK, version 1.0.1 now posted. Should handle whatever sysex sx can throw at it. cheers.
(Live sysex is pefectly formed btw
)
http://www.xmlconsulting.co.nz/husker/huskervu.htm
Posted: Mon Oct 03, 2005 10:00 am
by djsubject
husker wrote:whoaaaaaaaa! that's some seriously f**ked up looking sysex. Do Steinberg have *any* idea what they are doing!?!
Sysex MUST start with F0 and end with F7...
What VST is it... maybe there are some strange characters in the parameter names that SX isn't filtering propertly? Is there a ÷ character in one of the parameters by any chance?
I'll need to do another version of huskervu that ignores such garbage (it should anyway I suppose
)
cheers.
it happens with all vst's & vsti's
& the ÷ is there quite allot using sx (top right corner)
downloading 1.01 now
thanx for the quick update for a app yoy dont even use
thank you thankyou
Subz
Posted: Mon Oct 03, 2005 10:06 am
by djsubject
that fixed it!
thankyou husker
Subz
Posted: Mon Oct 03, 2005 10:09 am
by funkster1
Hi husker,
I have installed MIDI Yoke instead of MapleTools, and so far no more freezing of huskervu ATM **knockin' on wood**.
I'll be playin' around with huskervu on Cubase SX this afternoon, reporting back how it goes.
Merci beaucoup mon ami
Raphael
Posted: Mon Oct 03, 2005 11:32 am
by djsubject
v1.0.1 - 3 October 2005 - bug fix 1, handles bad sysex without crashing (thanks go to djsubject for debug info)
preset for Cubase sx by DJ Subject (Thanks!)
No, Thank you!!!
Subz
Posted: Mon Oct 03, 2005 12:51 pm
by James Togher
Cheers mate,
let's hope there's a Mackie Control C4 emulation on it's way aswell.
Then you could have one BCR for Mackie Control Unit emulation and one BCR for Mackie Control C4 emulation!
Nice...
James.
Posted: Tue Oct 04, 2005 11:28 am
by funkster1
James Togher wrote:
Cheers mate,
let's hope there's a Mackie Control C4 emulation on it's way aswell.
Then you could have one BCR for Mackie Control Unit emulation and one BCR for Mackie Control C4 emulation!
Nice...
James.
That implies that Mackie opens the specs to the public and that your application supports the C4 protocol.
It would be great addition to the MCU.
A Behringer support guy phoned me back shortly after I bought the BCR2000,
telling me that the C4 protocol could be a future option for the BCR, but legal stuff had to be cleared first with Mackie.
So maybe there's hope
Raphael
Posted: Wed Oct 05, 2005 3:16 pm
by djsubject
funkster1 wrote:James Togher wrote:
Cheers mate,
let's hope there's a Mackie Control C4 emulation on it's way aswell.
Then you could have one BCR for Mackie Control Unit emulation and one BCR for Mackie Control C4 emulation!
Nice...
James.
That implies that Mackie opens the specs to the public and that your application supports the C4 protocol.
It would be great addition to the MCU.
A Behringer support guy phoned me back shortly after I bought the BCR2000,
telling me that the C4 protocol could be a future option for the BCR, but legal stuff had to be cleared first with Mackie.
So maybe there's hope
Raphael
i think the app supports the Logic Controll XT protocol
seeing as when its loaded it acts as 1 LC & 3 LC XT's all connected to logic at one time
the top row is the LC & the other 3 rows are the 3 XT's
but if thay implement the C4 into the bcr2000 that would be cool!
i wonder if there is a app out there that stands between the bcr2000 & the host software that will make other hosts (like sonar) see it as a MCU?
Subz
Posted: Wed Oct 19, 2005 10:09 pm
by dance
Sorry I am prob being very thick but when I load MCE3LIVE (from
http://www.geocities.jp/mackicrokontrol ... live5.html) in BCedit from the computer to the editor the SAVE button (to save to the BCR20000) is ghosted. How can I save the pre-set to the BCR?
Any help would be appreciated.
PS: A big thanks to the guys who have made this happen.
Oliver
--
Whey Protein
Posted: Wed Oct 19, 2005 10:52 pm
by Namihei
Have you selected your BCR in "Devices" section?
like this
Posted: Wed Oct 19, 2005 11:09 pm
by dance
Werid I rebooted and it worked - thanks!
...but now I'm getting an error message which says:
Code: Select all
TIMEOUT ERROR
WHILE SENDING:
$rev R1
This is when I'm trying too save.