Casio CZ/ VZ/ FZ - Pro Series

I believe you that you don't see the reason. Intuitively it makes sense to me--midi-ox still needs a roundtrip midi flow for some readon. In any case, I explained the testing procedures I used and reported the results.

I remain convinced from my systematic testing that (1) there is no need to use more than one instance of midi-ox to send sysex data dumps to the CZ and (2) there is no need to use more than one instance of midi-ox to receive sysex data dumps from the CZ.

Based on your experience, I assume you can also do it with two instances of midi-ox. However, I think it should be clear that a person does not need to use two instances.

If you (or anyone else) decides to try to replicate my procedures, I'd be interested to know what the results are. There is always the possibility that no matter how detailed I was, I may have left a step or two out (or assumed too much background knowledge or experience on the part of others).

Steve

PS:

Just in case it isn't clear, what you are calling a PROMPT, is what I call a sysex command, namely, what Casio calls Send Request 1. (See page 19 of Casio's original "Guidebook for Midi (Nov. 1985).")

The very same instance of the version of midi-ox I used has a send/receive command. So it sends what you are calling the PROMPT and also listens for the reply.

In fact, you (or anyone else) can put 16 PROMPTS in the send area to request 16 CZ patches and the very same instance of midi-ox will receive 16 replies from the CZ, one for each of the requests.

If it worked for me, I cannot see why it wouldn't work for others.


--- In CZsynth@yahoogroups.com, Lee Borrell <templarser@...> wrote:
>
> I see no reason why MIDI-ox should hang waiting for an ACK when sending SYSx out to the MIDI out port:
> The reason to use 2 instances is when you are trying to get the CZ to give up a patch into the PC - not vice versa. Therefore the first instance is required to send a PROMPT to send the patch - the patch data is then picked up by the RX instance.
> 
> --- On Thu, 29/9/11, steve_the_composer <smw-mail@...> wrote:
> 
> From: steve_the_composer <smw-mail@...>
> Subject: [CZsynth] Re: Sysx patches and CZ101
> To: CZsynth@yahoogroups.com
> Date: Thursday, 29 September, 2011, 23:02
> 
>       
>       Using a 1990s era parallel port MOTU 8x8 midi router (port 8 in and port 8 out) connected to my CZ-3000, one and only one instance of midi-ox, and an XP SP3 PC (approc 6-7 years old), I successfully transmitted your first sysex bank (A) to the CZ and simultaneously received the acknowledgements from the CZ (F0 44 00 00 70 30 F7) on the first try. 
> 
> This is both good and bad.
> 
> GOOD:
> 
> --The patches work.
> --This confirms that midi-ox can be used to send previously stored CZ banks in sysex form to the CZ. 
> 
> BAD:
> 
> My test doesn't help diagnose your problem.
> 
> Test number 2:
> 
> I disconnected the midi out cable from the CZ so that midi-ox would not receive the ack. I transmitted your second bank (B).
> 
> Result:
> 
> Midi-ox hung, waiting for an acknowledgement.
> 
> 
> 
> I then reconnected the midi out and retransmitted the second set of patches. It was as successful as the first test.
> 
> 
> 
> This is useful information. It tells us midi-ox needs the roundtrip midi connection.
> 
> 
> 
> Again, this was done with one instance of midi-ox. When I read the post that someone said you needed two, it struck me as odd and didn't square with my admittedly limited understanding of midi-ox. I reserved judgement and consciously chose not to comment until I had a chance to do an actual test. (I generally like to run tests if I have the time to confirm that I am not giving erroneous advice. Also, I usually learn stuff that I can use by running the tests.)
> 
> 
> 
> I am at a loss, though, as to how to pose further diagnostic questions so that you can be successful.  Maybe after dinner I will write up the steps I took. I fully expect that you already tried what I did, but as long as I have the CZ hooked up I might as well document the steps. 
> 
> 
> 
> Steve
> 
> 
> 
> 
> 
>     
>      
> 
>     
>     
> 
> 
>  
> 
> 
> 
>   
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> [Non-text portions of this message have been removed]
>