Yahoo Groups archive

Casio CZ/ VZ/ FZ - Pro Series

Index last updated: 2026-04-28 22:42 UTC

Thread

Midi-Ox Sysex works

Midi-Ox Sysex works

2004-09-05 by zog2zog2003

I set the Midi Ox sysex buffer size to 128 and the number of them to 
2.  ( Under "view" get up the sysex window, then under sysex 
it's "options" )

My sysex patch files load to the VZ with those settings.  Apparently 
if you get "buffer full" errors, restarting Midi-Ox clears the buffer 
and you get fewer probs.  I started getting good transfers at 2 
buffers of 32, then tried a few with larger buffers.  Of course some 
other settings may also work.

Somebody already mentioned you should have the VZ's memory-protect 
disabled, and the Menu-3 settings usually = "Load","Midi" 
and "VC+OP", and have activated the "Execute" line before 
transmitting the sysex file from Midi-Ox.


Pete

Re: Midi-Ox Sysex works

2004-09-05 by phonophobie

just tried it out again - no success! maybe it´s something else? i
guess i will check this all on a win98 pc, soon




--- In CZsynth@...m, "zog2zog2003" <sandersp1@j...> wrote:
Show quoted textHide quoted text
> I set the Midi Ox sysex buffer size to 128 and the number of them to 
> 2.  ( Under "view" get up the sysex window, then under sysex 
> it's "options" )
> 
> My sysex patch files load to the VZ with those settings.  Apparently 
> if you get "buffer full" errors, restarting Midi-Ox clears the buffer 
> and you get fewer probs.  I started getting good transfers at 2 
> buffers of 32, then tried a few with larger buffers.  Of course some 
> other settings may also work.
> 
> Somebody already mentioned you should have the VZ's memory-protect 
> disabled, and the Menu-3 settings usually = "Load","Midi" 
> and "VC+OP", and have activated the "Execute" line before 
> transmitting the sysex file from Midi-Ox.
> 
> 
> Pete

Re: Midi-Ox Sysex works

2004-09-05 by zog2zog2003

Phono,
One thing the help mentions, is to have the "Pass Sysex" 
checkmarked.  It's at the bottom of the "Options" menu on the Midi-Ox 
front page.
It seemed like 2 buffers of 32 bytes was the most stable setting, but 
maybe I was just doing something wrong.  2 of 128 bytes is still 
working for me.  Closing Midi-Ox and restarting it after any errors, 
seems to be important, and I sometimes hit the "panic" midi button on 
my synth, as well as the "midi clear" button that's by the headphone 
out of the VZ.   Trying to clear any buffers.  I'm using XP right now.

Good luck.

Pete

--- In CZsynth@yahoogroups.com, "phonophobie" <sidstation@h...> wrote:
> just tried it out again - no success! maybe it´s something else? i
> guess i will check this all on a win98 pc, soon
> 
> 
> 
> 
> --- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> 
wrote:
> > I set the Midi Ox sysex buffer size to 128 and the number of them 
to 
> > 2.  ( Under "view" get up the sysex window, then under sysex 
> > it's "options" )
> > 
> > My sysex patch files load to the VZ with those settings.  
Apparently 
> > if you get "buffer full" errors, restarting Midi-Ox clears the 
buffer 
> > and you get fewer probs.  I started getting good transfers at 2 
> > buffers of 32, then tried a few with larger buffers.  Of course 
some 
> > other settings may also work.
> > 
> > Somebody already mentioned you should have the VZ's memory-
protect 
Show quoted textHide quoted text
> > disabled, and the Menu-3 settings usually = "Load","Midi" 
> > and "VC+OP", and have activated the "Execute" line before 
> > transmitting the sysex file from Midi-Ox.
> > 
> > 
> > Pete

Re: Midi-Ox Sysex works

2004-09-05 by phonophobie

thanks pete, i just checked it. It was checkmarked all the time. What
did you set for DELAY rates in MidiOX ( between buffers ), and do you
know if i can use MidiOx to see the Midichannel of the sysexfile which
i want to transfer? 

phono

--- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> wrote:
Show quoted textHide quoted text
> Phono,
> One thing the help mentions, is to have the "Pass Sysex" 
> checkmarked.  It's at the bottom of the "Options" menu on the Midi-Ox 
> front page.
> It seemed like 2 buffers of 32 bytes was the most stable setting, but 
> maybe I was just doing something wrong.  2 of 128 bytes is still 
> working for me.  Closing Midi-Ox and restarting it after any errors, 
> seems to be important, and I sometimes hit the "panic" midi button on 
> my synth, as well as the "midi clear" button that's by the headphone 
> out of the VZ.   Trying to clear any buffers.  I'm using XP right now.
> 
> Good luck.
> 
> Pete
> 
> --- In CZsynth@yahoogroups.com, "phonophobie" <sidstation@h...> wrote:
> > just tried it out again - no success! maybe it´s something else? i
> > guess i will check this all on a win98 pc, soon
> > 
> > 
> > 
> > 
> > --- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> 
> wrote:
> > > I set the Midi Ox sysex buffer size to 128 and the number of them 
> to 
> > > 2.  ( Under "view" get up the sysex window, then under sysex 
> > > it's "options" )
> > > 
> > > My sysex patch files load to the VZ with those settings.  
> Apparently 
> > > if you get "buffer full" errors, restarting Midi-Ox clears the 
> buffer 
> > > and you get fewer probs.  I started getting good transfers at 2 
> > > buffers of 32, then tried a few with larger buffers.  Of course 
> some 
> > > other settings may also work.
> > > 
> > > Somebody already mentioned you should have the VZ's memory-
> protect 
> > > disabled, and the Menu-3 settings usually = "Load","Midi" 
> > > and "VC+OP", and have activated the "Execute" line before 
> > > transmitting the sysex file from Midi-Ox.
> > > 
> > > 
> > > Pete

Re: Midi-Ox Sysex works

2004-09-05 by steve_the_composer

OK.  I finally got it to work on XP.  I had MidiOX 7.0 receiving, but 
nothing would make it send to the VZ--even though everything looked 
correct. It seems my interface had partially locked up--perhaps 
because I had several midi programs loaded at the same time.

SO, I rebooted the computer and the interface.  This time, I ran ONLY 
MidiOx.  I was able to send the files directly to the VZ via MidiOx.  
Try this.

BTW, what computer/OS and interface are you using?  Is there anything 
else in your set up which might be affecting the data flow?

With MidiOx, under MIDI Devices, the only ports I selected were the 
in and outs for the port connected to the VZ.
For port routings, I have MIDI-OX Event Port going directly to the 
port with the VZ.

I have sent vz.syx files successfully to the VZ with midiox about a 
dozen times.

Hope this helps.
--Steve

--- In CZsynth@yahoogroups.com, "phonophobie" <sidstation@h...> wrote:
> just tried it out again - no success! maybe it´s something else?
i
> guess i will check this all on a win98 pc, soon
> 
> 
> 
> 
> --- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> 
wrote:
> > I set the Midi Ox sysex buffer size to 128 and the number of them 
to 
> > 2.  ( Under "view" get up the sysex window, then under sysex 
> > it's "options" )
> > 
> > My sysex patch files load to the VZ with those settings.  
Apparently 
> > if you get "buffer full" errors, restarting Midi-Ox clears the 
buffer 
> > and you get fewer probs.  I started getting good transfers at 2 
> > buffers of 32, then tried a few with larger buffers.  Of course 
some 
> > other settings may also work.
> > 
> > Somebody already mentioned you should have the VZ's memory-
protect 
Show quoted textHide quoted text
> > disabled, and the Menu-3 settings usually = "Load","Midi" 
> > and "VC+OP", and have activated the "Execute" line before 
> > transmitting the sysex file from Midi-Ox.
> > 
> > 
> > Pete

Re: Midi-Ox Sysex works

2004-09-05 by zog2zog2003

It has 60 milliseconds in the Delay box, also 60 in the Delay after 
F7 box. 

 I get some colored lines of display on the Monitor-Output screen, 
and I believe that's the timestamp and lines of sysex data being 
transmitted.  It looks like it identifies  my midi ports, but not the 
midi channel. It says "buffer: 7 bytes  system exclusive", followed 
by 7 bytes of sysex hex.  I tried to find a screen with the channel, 
but didn't.  I think I get errors when I touch my keyboard, or when a 
cord or headphones rest on it.
I forgot to say you have to have the "EXCLUSIVE=ENA" set on page 4 of 
menu 3.

Pete

--- In CZsynth@yahoogroups.com, "phonophobie" <sidstation@h...> wrote:
> thanks pete, i just checked it. It was checkmarked all the time. 
What
> did you set for DELAY rates in MidiOX ( between buffers ), and do 
you
> know if i can use MidiOx to see the Midichannel of the sysexfile 
which
Show quoted textHide quoted text
> i want to transfer? 
> 
> phono

Re: Midi-Ox Sysex works

2004-09-05 by zog2zog2003

Steve, did your Midi-Ox transfers work without changing any of the 
defaults ? Like so many buffers of 256 bytes ?

I've been thinking maybe that wasn't my prob.

Thanks, 
Pete

Re: Midi-Ox Sysex works

2004-09-06 by phonophobie

@ pete:
thanx for the detailed infos. a bufferdelay of 60ms is the normal
value of midiox ( i also tried 1000 ;) ... i guess you can not help me
out. The Problem must be somewhere else. thanx!

@ steve:
ok, i will this reboot thing - tomorow :)
I am on winXP professional, and my audio/midi Interface is the Yamaha
01X (via mlan). Everything else is disconnected. Cables dirctly from
interface to synth. 
I remember i´ve transfered sysex banks with my older system on win98
and terratec soundcard succesfully. That´s also the reason why i
stored own patchbanks in sysex format.
Another important point is, that VZ patch transfer goes well with
VZeditor. So it´s a little confusing why midiOX does not work for
me.... dunno... well i also became problems with my kawai k5 synth and
sysex transfers. Sound Quest is maybe a solution for me?

@ after all, i would be happy to share some good patches with you
guys. I let you know when i have some available. 

Good Nite ;)
phono

Re: Midi-Ox Sysex works

2004-09-06 by steve_the_composer

I left it at the default for both in and out: 256 bytes, 16 buffers.  
I thought of you when I looked at those settings and wondered if you 
reallly needed to change them. (This is my first experience with 
MidiOx, and I am not sure what is going on behind the scenes.)

--Steve

--- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> wrote:
Show quoted textHide quoted text
> Steve, did your Midi-Ox transfers work without changing any of the 
> defaults ? Like so many buffers of 256 bytes ?
> 
> I've been thinking maybe that wasn't my prob.
> 
> Thanks, 
> Pete

Re: Midi-Ox Sysex works

2004-09-06 by zog2zog2003

Thanks.  I haven't had it work with 256 bytes at all yet.  It still 
works for me at 2 of 128, though.  I tried most of the sounds in the 
forum's files while doing that, so it was good for something!

Pete


--- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@p...> 
wrote:
> I left it at the default for both in and out: 256 bytes, 16 
buffers.

Re: Midi-Ox Sysex works

2004-09-06 by steve_the_composer

--- In CZsynth@yahoogroups.com, "zog2zog2003" <sandersp1@j...> wrote:
> It has 60 milliseconds in the Delay box, also 60 in the Delay after 
> F7 box.
I left this as the default, too.
 
>  I get some colored lines of display on the Monitor-Output screen, 
> and I believe that's the timestamp and lines of sysex data being 
> transmitted.
Somewhere there is a setting to either show all sysex data or just a 
line saying sysex was sent.

> It looks like it identifies  my midi ports, but not the 
> midi channel. It says "buffer: 7 bytes  system exclusive", followed 
> by 7 bytes of sysex hex.  I tried to find a screen with the
> channel, but didn't.

It makes sense that MidiOx would send them out on a port to whoever 
is on that port regardless of channel. Sysex commands themselves are 
not channelized.  However, within the sysex message, data specifies 
manufacturer, product line, etc. and may specify device id, channel, 
etc.  

--Steve

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.