Yahoo Groups archive

Casio CZ/ VZ/ FZ - Pro Series

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

Thread

Speed of sysex transfer

Speed of sysex transfer

2013-08-22 by fulfil_objective

Hi Steve,

I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).

High speed sysex transfer is both desired and encouraged, for example, in the case of sending sound data to a sampler. If you wanted to send 128 megabytes of sounds to your sampler, and if you were restricted to 31250 bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable higher speeds, and that speed is encouraged.

31250 bps is the speed of an old dialup modem (actual throughput) on a good day. If you tested at 115200 bps, that is merely 3.7 times faster than 31250 bps. Still very slow by today's standards.

USB 2.0 has a max throughput of something like 35 MB/s. But lets be generous and say that in the real world, you can only get your USB 2.0 to 20 MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120 times faster than 31250 bps.

So yes, I think a capable modern computer with a good USB system can send sysex out faster than the CZ can deal with it. And it's not necessarily tied to CPU speed of the computer either, more like the speed of the whole computer-USB system.

You will probably find it enlightening to read the "Universal Serial Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which you cand download here:

http://www.usb.org/developers/devclass_docs/midi10.pdf

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Gordon JC Pearce

On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
> Hi Steve,
> 
> I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).

Bullshit.

MIDI transfers data at 31250bps.  It doesn't matter how the interface is connected to the host or device, MIDI data is by definition 31250bps.  The interface may be able to talk to the PC faster than that, but you cannot send it to the target device at anything other than 31250bps.

-- 
Gordonjcp MM0YEQ

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Loscha

Thanks, Gordon.
I was in the car when this turd got emailed earlier.

MIDI is, as you state, fixed at a baud rate of 31250 bps. That's the very
definition of MIDI.
And, truth be told, if you look at the system architecture of earlier
synths, they could not take this rate in any sustained manner. You can send
note ones and off pretty fast, most modern synths can take fills speed more
on and off.
If you take an older synth - they cannot even take full back to back note
on note off. They'll start dropping notes or losing note offs.

Also. Latency. A cz-101 takes 8 ms to turn a note on aster receiving the
completed note on message.
I'd imagine the rest of the cz range is the same.
You've got phase accumulators And envelopes to reset. Fortunately, these
are achieved in hardware via the 93x series of chips. If these were done in
software, it'd be an even longer delay.

On Thursday, August 22, 2013, Gordon JC Pearce wrote:

> **
>
>
> On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
> > Hi Steve,
> >
> > I think you are too focused on these vintage numbers like 31250 bps and
> 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
> numbers. USB enables speeds that are hundreds or thousands of times faster
> than these numbers. In fact, greatly higher speeds are touted as one of the
> benefits of a USB MIDI device (along with multiple streams).
>
> Bullshit.
>
> MIDI transfers data at 31250bps. It doesn't matter how the interface is
> connected to the host or device, MIDI data is by definition 31250bps. The
> interface may be able to talk to the PC faster than that, but you cannot
> send it to the target device at anything other than 31250bps.
>
> --
> Gordonjcp MM0YEQ
>
>  
>


[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Daniel Forró

Definitely yes. Standard is standard.

There were only few exceptions - some SCI instruments could use higher  
speed for MIDI.

Daniel Forro
Show quoted textHide quoted text
On 22 Aug, 2013, at 4:45 PM, Gordon JC Pearce wrote:

> On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
>> Hi Steve,
>>
>> I think you are too focused on these vintage numbers like 31250 bps  
>> and 115200 bps. Transferring sysex by USB and MIDI are not limited  
>> to these old numbers. USB enables speeds that are hundreds or  
>> thousands of times faster than these numbers. In fact, greatly  
>> higher speeds are touted as one of the benefits of a USB MIDI  
>> device (along with multiple streams).
>
> Bullshit.
>
> MIDI transfers data at 31250bps.  It doesn't matter how the  
> interface is connected to the host or device, MIDI data is by  
> definition 31250bps.  The interface may be able to talk to the PC  
> faster than that, but you cannot send it to the target device at  
> anything other than 31250bps.
>
> -- 
> Gordonjcp MM0YEQ

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Daniel Forró

On 22 Aug, 2013, at 3:21 PM, fulfil_objective wrote:

> High speed sysex transfer is both desired and encouraged, for  
> example, in the case of sending sound data to a sampler. If you  
> wanted to send 128 megabytes of sounds to your sampler, and if you  
> were restricted to 31250 bps, it would take 9.5 hours to send the  
> sounds. USB MIDI devices enable higher speeds, and that speed is  
> encouraged.

Yes, in the times when nobody used USB for MIDI, SCI used higher MIDI  
speed for the purpose of SDS in some of their instruments, but very  
soon this idea was abandoned and manufacturers started to use SCSI  
SMDI standard for sample transfers.

>
> 31250 bps is the speed of an old dialup modem (actual throughput) on  
> a good day. If you tested at 115200 bps, that is merely 3.7 times  
> faster than 31250 bps. Still very slow by today's standards.

Yes, today's standard are today's standard. Nobody knew anything about  
them 30 years ago. Try to see it this way. It's easy to be a general  
after the battle.

> So yes, I think a capable modern computer with a good USB system can  
> send sysex out faster than the CZ can deal with it. And it's not  
> necessarily tied to CPU speed of the computer either, more like the  
> speed of the whole computer-USB system.
>
> You will probably find it enlightening to read the "Universal Serial  
> Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1,  
> 1999, which you cand download here:
>
> http://www.usb.org/developers/devclass_docs/midi10.pdf

Yes, but transfer between the interface and the target MIDI device  
must follow MIDI standard, which is 31250 bps. Dot.

Daniel Forro

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Jason Adkins

He he,

I liked the phrase "It's easy to be a general after the battle" if it  
wasn't for Sequential Circuits we wouldn't have midi period,we would  
be stuck with DCB or 16 CV-Gate leads for an 8-voice polysynth...

J
Show quoted textHide quoted text
On 22 Aug 2013, at 09:28, Daniel Forró wrote:

>
> On 22 Aug, 2013, at 3:21 PM, fulfil_objective wrote:
>
>> High speed sysex transfer is both desired and encouraged, for
>> example, in the case of sending sound data to a sampler. If you
>> wanted to send 128 megabytes of sounds to your sampler, and if you
>> were restricted to 31250 bps, it would take 9.5 hours to send the
>> sounds. USB MIDI devices enable higher speeds, and that speed is
>> encouraged.
>
> Yes, in the times when nobody used USB for MIDI, SCI used higher MIDI
> speed for the purpose of SDS in some of their instruments, but very
> soon this idea was abandoned and manufacturers started to use SCSI
> SMDI standard for sample transfers.
>
>>
>> 31250 bps is the speed of an old dialup modem (actual throughput) on
>> a good day. If you tested at 115200 bps, that is merely 3.7 times
>> faster than 31250 bps. Still very slow by today's standards.
>
> Yes, today's standard are today's standard. Nobody knew anything about
> them 30 years ago. Try to see it this way. It's easy to be a general
> after the battle.
>
>> So yes, I think a capable modern computer with a good USB system can
>> send sysex out faster than the CZ can deal with it. And it's not
>> necessarily tied to CPU speed of the computer either, more like the
>> speed of the whole computer-USB system.
>>
>> You will probably find it enlightening to read the "Universal Serial
>> Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1,
>> 1999, which you cand download here:
>>
>> http://www.usb.org/developers/devclass_docs/midi10.pdf
>
> Yes, but transfer between the interface and the target MIDI device
> must follow MIDI standard, which is 31250 bps. Dot.
>
> Daniel Forro
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Loscha

A friend of mine, Paul Perry (frostwave) had an interesting issue
along this line, vaguely.

They'd assembled a bunch of Alienator boards. Worked fine. Sound came
in an out. menus working fine, all the lights flashed, but it wouldn't
respond to MIDI.

They'd used (say) 10 Mhz crystals instead of 8Mhz. So, it wasn't
looking for smack on 31250 on the input!!!
Show quoted textHide quoted text
On 8/22/13, Daniel Forró <dan.for@...> wrote:
>
> On 22 Aug, 2013, at 3:21 PM, fulfil_objective wrote:
>
>> High speed sysex transfer is both desired and encouraged, for
>> example, in the case of sending sound data to a sampler. If you
>> wanted to send 128 megabytes of sounds to your sampler, and if you
>> were restricted to 31250 bps, it would take 9.5 hours to send the
>> sounds. USB MIDI devices enable higher speeds, and that speed is
>> encouraged.
>
> Yes, in the times when nobody used USB for MIDI, SCI used higher MIDI
> speed for the purpose of SDS in some of their instruments, but very
> soon this idea was abandoned and manufacturers started to use SCSI
> SMDI standard for sample transfers.
>
>>
>> 31250 bps is the speed of an old dialup modem (actual throughput) on
>> a good day. If you tested at 115200 bps, that is merely 3.7 times
>> faster than 31250 bps. Still very slow by today's standards.
>
> Yes, today's standard are today's standard. Nobody knew anything about
> them 30 years ago. Try to see it this way. It's easy to be a general
> after the battle.
>
>> So yes, I think a capable modern computer with a good USB system can
>> send sysex out faster than the CZ can deal with it. And it's not
>> necessarily tied to CPU speed of the computer either, more like the
>> speed of the whole computer-USB system.
>>
>> You will probably find it enlightening to read the "Universal Serial
>> Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1,
>> 1999, which you cand download here:
>>
>> http://www.usb.org/developers/devclass_docs/midi10.pdf
>
> Yes, but transfer between the interface and the target MIDI device
> must follow MIDI standard, which is 31250 bps. Dot.
>
> Daniel Forro
>
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Lee Borrell

Gordon is correct - the MIDI standard is 31.25 Kb - if there was any other speed,the MIDI equipment would not be able to read the signal- the baud rate is part of what is defined in a PROTOCOL - I should know - I teach IT!


________________________________
Show quoted textHide quoted text
 From: Gordon JC Pearce <gordon@...>
To: CZsynth@yahoogroups.com 
Sent: Thursday, 22 August 2013, 8:45
Subject: Re: [CZsynth] Speed of sysex transfer
 


  
On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
> Hi Steve,
> 
> I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).

Bullshit.

MIDI transfers data at 31250bps.  It doesn't matter how the interface is connected to the host or device, MIDI data is by definition 31250bps.  The interface may be able to talk to the PC faster than that, but you cannot send it to the target device at anything other than 31250bps.

-- 
Gordonjcp MM0YEQ


 

[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Lee Borrell

I think if you talking about USB to USB transfer - or Firewire then you may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN plugs on it is going to do better than that baud rate,or face the equipment not getting the signal. In the case of pre-USB vintage machines,there is no way to go faster than 31.25kB.




________________________________
Show quoted textHide quoted text
 From: fulfil_objective <robot@...>
To: CZsynth@yahoogroups.com 
Sent: Thursday, 22 August 2013, 7:21
Subject: [CZsynth] Speed of sysex transfer
 


  
Hi Steve,

I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).

High speed sysex transfer is both desired and encouraged, for example, in the case of sending sound data to a sampler. If you wanted to send 128 megabytes of sounds to your sampler, and if you were restricted to 31250 bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable higher speeds, and that speed is encouraged.

31250 bps is the speed of an old dialup modem (actual throughput) on a good day. If you tested at 115200 bps, that is merely 3.7 times faster than 31250 bps. Still very slow by today's standards.

USB 2.0 has a max throughput of something like 35 MB/s. But lets be generous and say that in the real world, you can only get your USB 2.0 to 20 MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120 times faster than 31250 bps.

So yes, I think a capable modern computer with a good USB system can send sysex out faster than the CZ can deal with it. And it's not necessarily tied to CPU speed of the computer either, more like the speed of the whole computer-USB system.

You will probably find it enlightening to read the "Universal Serial Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which you cand download here:

http://www.usb.org/developers/devclass_docs/midi10.pdf


 

[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by jammie

you could fit a lan midi port on the cz this is attached to the pre opto isolaters of the uart

then you can use midi over lan

but the midi protocol is still 31.25kb period thats the standard set

but the problem lies with the usb and windows changing it from win98 

and since then midi timing has been sloppy

now a parallel interface is much better and timing is much better 

so a opcode x64 which i still use and has xp 32 and 64bit drivers 

and i have never had any problems with sysex 

but i still use sound diver and changeit which is a great sysex sender and has a section for slowing down packets 
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Lee Borrell 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 12:47 PM
  Subject: Re: [CZsynth] Speed of sysex transfer


    
  I think if you talking about USB to USB transfer - or Firewire then you may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN plugs on it is going to do better than that baud rate,or face the equipment not getting the signal. In the case of pre-USB vintage machines,there is no way to go faster than 31.25kB.

  ________________________________
  From: fulfil_objective <robot@kasploosh.com>
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, 22 August 2013, 7:21
  Subject: [CZsynth] Speed of sysex transfer


    
  Hi Steve,

  I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).

  High speed sysex transfer is both desired and encouraged, for example, in the case of sending sound data to a sampler. If you wanted to send 128 megabytes of sounds to your sampler, and if you were restricted to 31250 bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable higher speeds, and that speed is encouraged.

  31250 bps is the speed of an old dialup modem (actual throughput) on a good day. If you tested at 115200 bps, that is merely 3.7 times faster than 31250 bps. Still very slow by today's standards.

  USB 2.0 has a max throughput of something like 35 MB/s. But lets be generous and say that in the real world, you can only get your USB 2.0 to 20 MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120 times faster than 31250 bps.

  So yes, I think a capable modern computer with a good USB system can send sysex out faster than the CZ can deal with it. And it's not necessarily tied to CPU speed of the computer either, more like the speed of the whole computer-USB system.

  You will probably find it enlightening to read the "Universal Serial Bus Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which you cand download here:

  http://www.usb.org/developers/devclass_docs/midi10.pdf

  [Non-text portions of this message have been removed]



  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13


[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Loscha

You assert that MIDI over USB is sloppy.

This is the same as a schoolgirl saying toads gice you warts!!!

If you look at a MIDI USB over an oscilloscope, as I have, you'll see
it is just fine. I do not have any pictures to document this, sadly --
and my scope is not currently set up.

I defy you to produce factual evidence to the contrary, however!

MiDI is not ideal for tight timing.
If you look at, say, laying a 4 down kick drum on a track, unless that
tempo you are using is an integer divisor of 31250, it's going to flop
around and not be in time.
Period.
Show quoted textHide quoted text
On 8/22/13, jammie <jammie.emma@...> wrote:
> you could fit a lan midi port on the cz this is attached to the pre opto
> isolaters of the uart
>
> then you can use midi over lan
>
> but the midi protocol is still 31.25kb period thats the standard set
>
> but the problem lies with the usb and windows changing it from win98
>
> and since then midi timing has been sloppy
>
> now a parallel interface is much better and timing is much better
>
> so a opcode x64 which i still use and has xp 32 and 64bit drivers
>
> and i have never had any problems with sysex
>
> but i still use sound diver and changeit which is a great sysex sender and
> has a section for slowing down packets
>   ----- Original Message -----
>   From: Lee Borrell
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, August 22, 2013 12:47 PM
>   Subject: Re: [CZsynth] Speed of sysex transfer
>
>
>
>   I think if you talking about USB to USB transfer - or Firewire then you
> may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS
> to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN
> plugs on it is going to do better than that baud rate,or face the equipment
> not getting the signal. In the case of pre-USB vintage machines,there is no
> way to go faster than 31.25kB.
>
>   ________________________________
>   From: fulfil_objective <robot@...>
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, 22 August 2013, 7:21
>   Subject: [CZsynth] Speed of sysex transfer
>
>
>
>   Hi Steve,
>
>   I think you are too focused on these vintage numbers like 31250 bps and
> 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
> numbers. USB enables speeds that are hundreds or thousands of times faster
> than these numbers. In fact, greatly higher speeds are touted as one of the
> benefits of a USB MIDI device (along with multiple streams).
>
>   High speed sysex transfer is both desired and encouraged, for example, in
> the case of sending sound data to a sampler. If you wanted to send 128
> megabytes of sounds to your sampler, and if you were restricted to 31250
> bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
> higher speeds, and that speed is encouraged.
>
>   31250 bps is the speed of an old dialup modem (actual throughput) on a
> good day. If you tested at 115200 bps, that is merely 3.7 times faster than
> 31250 bps. Still very slow by today's standards.
>
>   USB 2.0 has a max throughput of something like 35 MB/s. But lets be
> generous and say that in the real world, you can only get your USB 2.0 to 20
> MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
> times faster than 31250 bps.
>
>   So yes, I think a capable modern computer with a good USB system can send
> sysex out faster than the CZ can deal with it. And it's not necessarily tied
> to CPU speed of the computer either, more like the speed of the whole
> computer-USB system.
>
>   You will probably find it enlightening to read the "Universal Serial Bus
> Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which
> you cand download here:
>
>   http://www.usb.org/developers/devclass_docs/midi10.pdf
>
>   [Non-text portions of this message have been removed]
>
>
>
>
>   No virus found in this message.
>   Checked by AVG - www.avg.com
>   Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
>
>
> [Non-text portions of this message have been removed]
>
>

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

You make some valid points. However, I have seen people in this chat make erroneous, false, and reckless comments before. When someone is trying to solve a problem, in my opinion giving poor advice is not helpful. In communication, there is something called "self-interest pleading." For example, someone who loves a Commodore 64 and every chance they get in a non-Commodore 64 forum they tell people about what they have done with their Commodore 64 and how they should get one to solve their problem is engaging in a version of what I would call self-interest pleading. (Yes, I know no one has talked about a C-64 here to this extent; this is just an extreme example.)

I think if you take a look at what I have done you might find that I try to diagnose issues and ask diagnostic question and propose tests to try to try to hone down the source of the problem.

I usually am polite, but sometimes it is very difficult when people say false things and offer erroneous opinions and on occasion give misguided advice.

Granted some people here sincerely try to be helpful.

However, telling people "One option is to use two instances of midi-ox to get it to solve your problem" and telling people "You need to use two instances of midi-ox, one to send and one to receive . . . " are two different things. (Again, this is just an example.)

Several years ago with the proliferation of computer audio, many people in some forums declared that "Midi is Dead!" Their opinion was that it was inferior to audio, it was designed in the dark ages (or at least an age preceding the age of technological enlightenment), it was slow and useless.

So, I did some research and found that the midi is not tied to 31.25 kbp/s according to the MMA. Of course, with the 5-pin din connector and optoisolator current-loop system older gear will never be able to use higher speeds. That doesn't mean future gear couldn't.

The point is that the death of midi as a communication vehicle was premature. Also, saying you need old computers to work with old gear because the old gear can't handle modern systems is not true. 

On the other hand, offering possible work-arounds is a good thing (in my opinion). 

But please let's not lose sight of the original problem that was posed. Toward that end, last night after posting the results of the tests I proposed, I googled usb midi interface problems with sysex. Here are a few links that (in my opinion) relate to (1) the original problem and (2) the uses of midi-ox to delay the transmission speed of midi data.

http://www.korgforums.com/forum/phpBB2/viewtopic.php?p=396436&sid=6e36daace30aba952586dc60a3424eb6
http://forum.highlyliquid.com/showthread.php?t=738
http://www.kvraudio.com/forum/printview.php?t=372683&start=0

Steve 
 

--- In CZsynth@yahoogroups.com, "fulfil_objective" <robot@...> wrote:

[snip]

> I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. 

[snip]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Francis Cote

If the machine has an issue with sysex speed, it's related to the number of
MIDI messages it can process in a certain amount of time.
If the synth can't process more than, say, 5 messages per second (not real
number, I don't know the real one it's just an example) and you throw 100,
it obviously choke on it.
If the synth makers implemented some kind of buffer able to take all the
data coming from the MIDI port, then the synth's CPU will have all the time
it wants to process at the speed it can process and it won't choke.

A chain is always going at the speed of the slowest node, that's it.
Software that gives you the option of slowing down packets are just adding
some delay between each packets.

Francis



On Thu, Aug 22, 2013 at 8:22 AM, jammie <jammie.emma@...>wrote:

> **
>
>
> you could fit a lan midi port on the cz this is attached to the pre opto
> isolaters of the uart
>
> then you can use midi over lan
>
> but the midi protocol is still 31.25kb period thats the standard set
>
> but the problem lies with the usb and windows changing it from win98
>
> and since then midi timing has been sloppy
>
> now a parallel interface is much better and timing is much better
>
> so a opcode x64 which i still use and has xp 32 and 64bit drivers
>
> and i have never had any problems with sysex
>
> but i still use sound diver and changeit which is a great sysex sender and
> has a section for slowing down packets
> ----- Original Message -----
> From: Lee Borrell
> To: CZsynth@yahoogroups.com
> Sent: Thursday, August 22, 2013 12:47 PM
> Subject: Re: [CZsynth] Speed of sysex transfer
>
> I think if you talking about USB to USB transfer - or Firewire then you
> may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS
> to be 31.25 Kb - this is the MIDI standard. No commercial interface with
> DIN plugs on it is going to do better than that baud rate,or face the
> equipment not getting the signal. In the case of pre-USB vintage
> machines,there is no way to go faster than 31.25kB.
>
> ________________________________
> From: fulfil_objective <robot@...>
> To: CZsynth@yahoogroups.com
> Sent: Thursday, 22 August 2013, 7:21
> Subject: [CZsynth] Speed of sysex transfer
>
> Hi Steve,
>
> I think you are too focused on these vintage numbers like 31250 bps and
> 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
> numbers. USB enables speeds that are hundreds or thousands of times faster
> than these numbers. In fact, greatly higher speeds are touted as one of the
> benefits of a USB MIDI device (along with multiple streams).
>
> High speed sysex transfer is both desired and encouraged, for example, in
> the case of sending sound data to a sampler. If you wanted to send 128
> megabytes of sounds to your sampler, and if you were restricted to 31250
> bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
> higher speeds, and that speed is encouraged.
>
> 31250 bps is the speed of an old dialup modem (actual throughput) on a
> good day. If you tested at 115200 bps, that is merely 3.7 times faster than
> 31250 bps. Still very slow by today's standards.
>
> USB 2.0 has a max throughput of something like 35 MB/s. But lets be
> generous and say that in the real world, you can only get your USB 2.0 to
> 20 MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
> times faster than 31250 bps.
>
> So yes, I think a capable modern computer with a good USB system can send
> sysex out faster than the CZ can deal with it. And it's not necessarily
> tied to CPU speed of the computer either, more like the speed of the whole
> computer-USB system.
>
> You will probably find it enlightening to read the "Universal Serial Bus
> Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which
> you cand download here:
>
> http://www.usb.org/developers/devclass_docs/midi10.pdf
>
> [Non-text portions of this message have been removed]
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
>
>
> [Non-text portions of this message have been removed]
>
>  
>


[Non-text portions of this message have been removed]

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

Gee.  Maybe I have been too polite. ;) 
Steve

--- In CZsynth@yahoogroups.com, Gordon JC Pearce <gordon@...> wrote:
Show quoted textHide quoted text
>
> On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
> > Hi Steve,
> > 
> > I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).
> 
> Bullshit.
> 
> MIDI transfers data at 31250bps.  It doesn't matter how the interface is connected to the host or device, MIDI data is by definition 31250bps.  The interface may be able to talk to the PC faster than that, but you cannot send it to the target device at anything other than 31250bps.
> 
> -- 
> Gordonjcp MM0YEQ
>

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

As I commented, with the 5-pin din, current-loop optoisolator system used by gear manufacturers and hackers for the past several decades, we agree. To borrow a metaphor used a few replies back, I do not try to be a general of past battles with 20-20 hindsight. I try to look at future possibilities.

Steve

--- In CZsynth@yahoogroups.com, Lee Borrell <templarser@...> wrote:
>
> I think if you talking about USB to USB transfer - or Firewire then you may have a point, but as soon as any interface hits a MIDI DIN plug it HAS to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN plugs on it is going to do better than that baud rate,or face the equipment not getting the signal. In the case of pre-USB vintage machines,there is no way to go faster than 31.25kB.

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

Then maybe better forget about MIDI at all. It's a 30 years old  
standard, difficult if not impossible to improve.

Even now some instruments (and numbers go up quickly) use USB for MIDI  
communication with computer.

Then there is Yamaha LAN...

And maybe other new standards will come.

Daniel Forro
Show quoted textHide quoted text
On 22 Aug, 2013, at 10:01 PM, steve_the_composer wrote:

> I try to look at future possibilities.
>
> Steve

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

I am not sure I saved or bookmarked the MMA document that says that midi as a vehicle of communication is not limited to 31.25 kbps. I will look for it.

In case its not clear, I am not saying "Bullshit." Rather, I am agreeing that >>in the past<< gear makers (and hackers) used the 31.25 kbps as a convenience so that 5-pin din midi gear could communicate with all other 5-pin din midi gear.

However, this is not to say that future midi gear couldn't be designed and implemented with different connectors, perhaps faster opto-isolators (if they exist)--or even micro-processors with built-in serial devices, and considerably faster speeds. Rates could even be selectable. 

And there could be step-down devices so that older gear works with a newer system and is thereby not made obsolete.

With the arduino --> serial usb-midi bridge --> midi-ox --> e-mu 2x2 usb interface test I did, clearly something performed the step down. I am guessing it might well be the e-mu 2x2 (and its drivers), but I cannot think of a way to test that.

I suppose I could buy 1x1 usb-midi interface "cable" and run the same tests. If I find that sysex doesn't work properly but note and other data does, then it might not be the interface doing the stepping down. However, if the 1x1 fails, that would lead me to conclude its in the interface.

Anyone want to subsidize the research? How about try to replicate it?

Steve

 

--- In CZsynth@yahoogroups.com, Lee Borrell <templarser@...> wrote:
Show quoted textHide quoted text
>
> 
> 
> Gordon is correct - the MIDI standard is 31.25 Kb - if there was any other speed,the MIDI equipment would not be able to read the signal- the baud rate is part of what is defined in a PROTOCOL - I should know - I teach IT!
> 
> 
> ________________________________
>  From: Gordon JC Pearce <gordon@...>
> To: CZsynth@yahoogroups.com 
> Sent: Thursday, 22 August 2013, 8:45
> Subject: Re: [CZsynth] Speed of sysex transfer
>  
> 
> 
> Â  
> On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
> > Hi Steve,
> > 
> > I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).
> 
> Bullshit.
> 
> MIDI transfers data at 31250bps.  It doesn't matter how the interface is connected to the host or device, MIDI data is by definition 31250bps.  The interface may be able to talk to the PC faster than that, but you cannot send it to the target device at anything other than 31250bps.
> 
> -- 
> Gordonjcp MM0YEQ
> 
> 
>  
> 
> [Non-text portions of this message have been removed]
>

Re: Speed of sysex transfer

2013-08-22 by bernard.escaillas

Hello,

I am just a reader most of the time. But now this is a subject I have dealt with on many synth and many programmable custom devices (Arduino, mbed, Panda,...etc). So it may be a good time to step in ;)

The midi protocol is just a subset of the serial protocol from "the gold old days".
The speed has been defined once for all @ 31250 bauds.
( The Midi association has been working on new "fast Midi" for two decades without beeing able to decide "what next"...So this won't change anytime soon :( )

You can always tweak this speed by a few percents in hardware because receiving device tend to sync to signal. So you may be fine using 32000 bauds for exemple if it is more convenient.

Now concerning the loss of long messages between a modern computer and a synth from the 80's, the problem lies in the CPU speed of the synth and its input buffer:
when the synth receive data on its midi port it has to read and analyse data present in the input buffer. For sysex, the analysis can take some time before the synth has consumed the data and freed the input buffer. If during this analysis the PC keeps pushing data (even at 31250 bauds) into the synth's input buffer, the later can become full and the serial chip refuses (or ignores) incomming data...
Then the sysex is incomplete.

To give the synth enough time to digest the new sysex information, the sending PC should do some pauses. This "pause" setting is available in a tool like MidiOx. There you can set the size of "packets" and the pause to do between packets.
It may take some testing to find the correct values for a given synth...

Old synth don't have more than 64, 128 or 256 bytes at best of input buffer ! Flash memory was very expensive at that time.
I don't know the CZ5000 specs...
Try to send packets of 128 bytes with 50ms in between.
If messages are still lost, either decrease packet size of increase pause duration.
If communication is fine you can try to increase packet and reduce pauses.

Bernard

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

LOL.  I would hate to see all currently existing midi gear made useless, though I can certainly see that as a possibility. In fact, with softsynths it has already happened!!!!!! Of course, there are still some people that prefer hardware synths. Of course, I have seen people in different forums go from softsynths TO hardware a well.

So, I agree; it may be a moot point.

However, I recommend separating midi as a vehicle of communication (all it a language, if you like) from the connection apparatus--the 5-pin din, current loop apparatus.

My usb-midi keyboard can communicate with vsts and other software via the usb connection. It does so using the "language" of midi (note on/off, CC, aftertouch, program change, etc.) Of course, it is based on 8 bits (e.g., 0x90 0x40 0x7F, 0xB0 0x0A 0x7F, etc.).

I suppose someone could come up with a 16-bit, 32-bit, 64-bit, or even higher version which might make the 8-bit system severely outdated. If they do, I would hope the make it reverse compatible if at all possible.

I love my dinosaurs!!!!

For what its worth, in my testing, I still used 8N1. In fact, until now it didn't occur to me to see if I could change that.

As for midi-over-lan and midi-over-internet, I have dabbled a little bit, but not much.  It seems to me that with internet latencies, to be effective, a system of time stamping and compensation is needed.  I haven't delved into that at all.

In any case, its nice to know that my arduino program works with both vsts and CZs. Perhaps I will hook up a midi connector directly so I can test different gear and different interfaces.  So far, I have only used 31.25 kpbs (8N1), but it might be interesting to have a device that tests 5-pin din, current loops at different speeds. My guess is that the range of tolerances for midi out (microprocessor dev board to hardware) would be different for midi in (hardware to microprocessor dev board). However, I would expect that anything other than 8N1 would fail totally.

Steve

--- In CZsynth@yahoogroups.com, Daniel Forró <dan.for@...> wrote:
Show quoted textHide quoted text
>
> Then maybe better forget about MIDI at all. It's a 30 years old  
> standard, difficult if not impossible to improve.
> 
> Even now some instruments (and numbers go up quickly) use USB for MIDI  
> communication with computer.
> 
> Then there is Yamaha LAN...
> 
> And maybe other new standards will come.
> 
> Daniel Forro
> 
> On 22 Aug, 2013, at 10:01 PM, steve_the_composer wrote:
> 
> > I try to look at future possibilities.
> >
> > Steve
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

On 22 Aug, 2013, at 10:30 PM, steve_the_composer wrote:

> I am not sure I saved or bookmarked the MMA document that says that  
> midi as a vehicle of communication is not limited to 31.25 kbps. I  
> will look for it.

You are right. As I have mentioned, it was SCI who used in some of  
their machines faster MIDI.
>
> In case its not clear, I am not saying "Bullshit."

Nobody said it was you :-)

> Rather, I am agreeing that >>in the past<< gear makers (and hackers)  
> used the 31.25 kbps as a convenience so that 5-pin din midi gear  
> could communicate with all other 5-pin din midi gear.

This is how MIDI was designed.
>
> However, this is not to say that future midi gear couldn't be  
> designed and implemented with different connectors, perhaps faster  
> opto-isolators (if they exist)--or even micro-processors with built- 
> in serial devices, and considerably faster speeds. Rates could even  
> be selectable.
>
> And there could be step-down devices so that older gear works with a  
> newer system and is thereby not made obsolete.

While still years ago this idea was offered I don't think anybody  
today will lose time with thinking about this. There's no reason to  
try to improve MIDI. There's nothing to improve, because if we improve  
it, lot of old devices will become incompatible and obsolete. There  
are only some small addition to MIDI standard from time to time, but  
basic idea is the same as 30 years ago. And even older because MIDI  
was based on older standards.

So if really there's a need for improvement, then some new standard  
should be invented. But I don't see any reason for it. With modern  
multiple output MIDI interfaces and powerful computers there's hardly  
any problem with controlling huge MIDI system. Recently I have 672  
MIDI channels connected to 10 years old Mac G4 PPC with OS 9 Classic,  
and can use maximally 512 MIDI channels at once due limitation in soft  
sequencer (Opcode Studio Vision Pro). Until now I have used maximally  
about 100 channels for orchestra emulation...

There can be some latency, but when we are aware of it, we can live  
with it and compensate it by clever programming.

  And of course some bridge between modern standard and MIDI - this  
will be necessary. But it exists - USB/MIDI interface is good example.

> With the arduino --> serial usb-midi bridge --> midi-ox --> e-mu 2x2  
> usb interface test I did, clearly something performed the step down.  
> I am guessing it might well be the e-mu 2x2 (and its drivers), but I  
> cannot think of a way to test that.

Definitely it's USB/MIDI device. It must convert fast USB protocol to  
slow MIDI protocol, and change data format.
>
> I suppose I could buy 1x1 usb-midi interface "cable" and run the  
> same tests. If I find that sysex doesn't work properly but note and  
> other data does, then it might not be the interface doing the  
> stepping down. However, if the 1x1 fails, that would lead me to  
> conclude its in the interface.

Of course it's in interface.
>
> Anyone want to subsidize the research? How about try to replicate it?
>
> Steve

Daniel Forro

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

On 22 Aug, 2013, at 10:44 PM, bernard.escaillas wrote:

> The midi protocol is just a subset of the serial protocol from "the  
> gold old days".
> The speed has been defined once for all @ 31250 bauds.
> ( The Midi association has been working on new "fast Midi" for two  
> decades without beeing able to decide "what next"...So this won't  
> change anytime soon :( )

SCI used faster MIDI in some of their machines.
>
> You can always tweak this speed by a few percents in hardware  
> because receiving device tend to sync to signal. So you may be fine  
> using 32000 bauds for exemple if it is more convenient.

Yamaha, Korg and maybe other firms have used also MIDI transfer  
through common Serial cable (with Mini DIN connector), and for Mac  
there's a speed 38400 bps.

> Now concerning the loss of long messages between a modern computer  
> and a synth from the 80's, the problem lies in the CPU speed of the  
> synth and its input buffer:
> when the synth receive data on its midi port it has to read and  
> analyse data present in the input buffer. For sysex, the analysis  
> can take some time before the synth has consumed the data and freed  
> the input buffer. If during this analysis the PC keeps pushing data  
> (even at 31250 bauds) into the synth's input buffer, the later can  
> become full and the serial chip refuses (or ignores) incomming data...
> Then the sysex is incomplete.
>
> To give the synth enough time to digest the new sysex information,  
> the sending PC should do some pauses. This "pause" setting is  
> available in a tool like MidiOx. There you can set the size of  
> "packets" and the pause to do between packets.
> It may take some testing to find the correct values for a given  
> synth...

Exactly so, this is the same what I have written. Thanks for  
confirmation.
>
> Old synth don't have more than 64, 128 or 256 bytes at best of input  
> buffer ! Flash memory was very expensive at that time.
> I don't know the CZ5000 specs...
> Try to send packets of 128 bytes with 50ms in between.
> If messages are still lost, either decrease packet size of increase  
> pause duration.
> If communication is fine you can try to increase packet and reduce  
> pauses.


Daniel Forro



[Non-text portions of this message have been removed]

Re: Speed of sysex transfer

2013-08-22 by k9k9dog

lol. MIDI sample dump cannot even be envisaged. dot. 
i hope nobody's going to start sl*gging MIDI (again). 
quite simply one of the best human inventions ever.
what about wordclocking? (i'm only kidding, send it 
via your old ADAT...). word.

i'm serious about caged artist: it works beautifully.
everyone should have an atari kicking around for all 
it can do. i just got one *nicked* during a housemove, 
of all things they could have taken...consider: editors, 
old sequencers, the cubase Interactive Phrase Synth as 
arpeggiator, etc.(slow workflow, crashes in hot weather)

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

Agreement.

Three ATARI still at my side, one Mega ST on my table with two HD and  
Ultrasatan. I've been using them since 1988 :-) I was more Notator  
user but Cubase had some good features...

Daniel Forro
Show quoted textHide quoted text
On 22 Aug, 2013, at 11:16 PM, k9k9dog wrote:

> lol. MIDI sample dump cannot even be envisaged. dot.
> i hope nobody's going to start sl*gging MIDI (again).
> quite simply one of the best human inventions ever.
> what about wordclocking? (i'm only kidding, send it
> via your old ADAT...). word.
>
> i'm serious about caged artist: it works beautifully.
> everyone should have an atari kicking around for all
> it can do. i just got one *nicked* during a housemove,
> of all things they could have taken...consider: editors,
> old sequencers, the cubase Interactive Phrase Synth as
> arpeggiator, etc.(slow workflow, crashes in hot weather)

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

Footnotes:
(1) I googled Yamaha LAN and found some forum stuff with people having issues with it.
(2) About 3 or 4 years ago, I ran a test of midi-over-internet where I payed a softsynth of a chat buddy in NL (IIRC). He echoed the midi data back to me which I recorded and determined the round trip latency. I think it was about 600ms.
(3) What prompted the experiment (where's the Youtube clip?) were some very successful tests (no noticeable latency) I had done controlling gear hooked up to one computer from a controller hooked up to another computer across the room but via a router. (Of course, I was using 8-bit midi.)

So, thanks for the offer to forget midi, but I am a dinosaur myself and I like dinosaur gear.

Oh, yeah, even as a dinosaur, I stick by my claim of looking towards future possibilities. Always did; always will. I did that when I was in my teens, too--when I envisioned controlling a synth (Moog modular) with a computer. It was unheard of back then. In fact, one of my professors told me, "What a waste of a computer!" Needless to say, I should have told him "Bullshit," and tried to find a professor or a program that had the ability to envision future possibilities.

Again, I try my best to help people with issues they have. Those efforts are future-solution oriented. I envision possibilities. But I do so mindful of the past. 

I am not sure who said, "the past informs the present to ideally improve the future," but I think there is merit in that approach--whether it be on a small-scale, near-term problem-solution or a large-scale, long-term one.

I see no problem with integrating the old with the new with an eye towards the future. 

Steve

PS: When I first read and responded to your reply to my comment about the future, I did not see any arrogance, agism, or sarcasm whatsoever. I usually don't pick up on stuff like that even when it is there. In fact, it didn't even occur to me you might be doing that until sometime after I had innocently started penning the footnotes by way of simple clarification. However, in retrospect, your tone seems clear--everything you wrote was a reply to my comment that "I try to look at future possibilities."

It seems that your lead in, "Then maybe better forget about MIDI after all," was a retort, a challenge.

Of course, it is hard to tell attitude in printed text messages posted on a forum. So, if you weren't being sarcastic and arrogant, I happily withdraw the suggestion that it might have been.

steve_the_visionary_dinosaur  ;)
  

--- In CZsynth@yahoogroups.com, Daniel Forró <dan.for@...> wrote:
Show quoted textHide quoted text
>
> Then maybe better forget about MIDI at all. It's a 30 years old  
> standard, difficult if not impossible to improve.
> 
> Even now some instruments (and numbers go up quickly) use USB for MIDI  
> communication with computer.
> 
> Then there is Yamaha LAN...
> 
> And maybe other new standards will come.
> 
> Daniel Forro
> 
> On 22 Aug, 2013, at 10:01 PM, steve_the_composer wrote:
> 
> > I try to look at future possibilities.
> >
> > Steve
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by jammie

like i said its already possible to make your equipment into midi over lan compatible the modules cost £45 and they are connected before the opto isolators on the uart tx and rx channels 

you can have 100meter run cat5 cables and still get rock solid timing 

its already here along the way in some older synths there was 14bit cc

synths and samplers like emu and roland all the lsb msb 7bit data which gives a much smoother real time control

this is the next step but when the lan signals get to the lan connection the fpga sorts the data to the standard midi baud rate

also midi -ox has always been flaky for me

and why i use changeit instead as it seems to be a better midi sender  and sounddiver3

and my trustie st
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: steve_the_composer 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 2:30 PM
  Subject: [CZsynth] Re: Speed of sysex transfer


    
  I am not sure I saved or bookmarked the MMA document that says that midi as a vehicle of communication is not limited to 31.25 kbps. I will look for it.

  In case its not clear, I am not saying "Bullshit." Rather, I am agreeing that >>in the past<< gear makers (and hackers) used the 31.25 kbps as a convenience so that 5-pin din midi gear could communicate with all other 5-pin din midi gear.

  However, this is not to say that future midi gear couldn't be designed and implemented with different connectors, perhaps faster opto-isolators (if they exist)--or even micro-processors with built-in serial devices, and considerably faster speeds. Rates could even be selectable. 

  And there could be step-down devices so that older gear works with a newer system and is thereby not made obsolete.

  With the arduino --> serial usb-midi bridge --> midi-ox --> e-mu 2x2 usb interface test I did, clearly something performed the step down. I am guessing it might well be the e-mu 2x2 (and its drivers), but I cannot think of a way to test that.

  I suppose I could buy 1x1 usb-midi interface "cable" and run the same tests. If I find that sysex doesn't work properly but note and other data does, then it might not be the interface doing the stepping down. However, if the 1x1 fails, that would lead me to conclude its in the interface.

  Anyone want to subsidize the research? How about try to replicate it?

  Steve

  --- In CZsynth@yahoogroups.com, Lee Borrell <templarser@...> wrote:
  >
  > 
  > 
  > Gordon is correct - the MIDI standard is 31.25 Kb - if there was any other speed,the MIDI equipment would not be able to read the signal- the baud rate is part of what is defined in a PROTOCOL - I should know - I teach IT!
  > 
  > 
  > ________________________________
  > From: Gordon JC Pearce <gordon@...>
  > To: CZsynth@yahoogroups.com 
  > Sent: Thursday, 22 August 2013, 8:45
  > Subject: Re: [CZsynth] Speed of sysex transfer
  > 
  > 
  > 
  > Â  
  > On Thu, Aug 22, 2013 at 06:21:26AM -0000, fulfil_objective wrote:
  > > Hi Steve,
  > > 
  > > I think you are too focused on these vintage numbers like 31250 bps and 115200 bps. Transferring sysex by USB and MIDI are not limited to these old numbers. USB enables speeds that are hundreds or thousands of times faster than these numbers. In fact, greatly higher speeds are touted as one of the benefits of a USB MIDI device (along with multiple streams).
  > 
  > Bullshit.
  > 
  > MIDI transfers data at 31250bps. It doesn't matter how the interface is connected to the host or device, MIDI data is by definition 31250bps. The interface may be able to talk to the PC faster than that, but you cannot send it to the target device at anything other than 31250bps.
  > 
  > -- 
  > Gordonjcp MM0YEQ
  > 
  > 
  > 
  > 
  > [Non-text portions of this message have been removed]
  >



  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13


[Non-text portions of this message have been removed]

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

LOL. It looks like we were "talking" at the same time in that we were replying to messages we each posted previously at the same time.

Your posts written simultaneously with mine have led me to conclude I was right in the first place--that you did not intend to be sarcastic and arrogant. (I guess it was a sincere attempt to point me in the direction of things you felt I was not aware of--e.g., midi-over-lan/internet.)

So, I hereby withdraw the suggestion that it might have been.

steve_the_verbose


--- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:

[snip]
Show quoted textHide quoted text
> Of course, it is hard to tell attitude in printed text messages posted on a forum. So, if you weren't being sarcastic and arrogant, I happily withdraw the suggestion that it might have been.
> 
> steve_the_visionary_dinosaur  ;)

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

Steve,

thanks for your message. I can assure you there's no arrogance or  
sarcasm in my messages, I'm not that type. If you could feel something  
alike, then it's only due my poor knowledge of Shakespeare tongue, I'm  
not able to use well some nuances and finesses.

In any case I like your messages and attitude.

Daniel Forro
another dinosaur liking prehistoric gear (I had even a Museum of  
Electronic Instruments, the only of its kind in my former country)
Show quoted textHide quoted text
On 22 Aug, 2013, at 11:58 PM, steve_the_composer wrote:

> Footnotes:
> (1) I googled Yamaha LAN and found some forum stuff with people  
> having issues with it.
> (2) About 3 or 4 years ago, I ran a test of midi-over-internet where  
> I payed a softsynth of a chat buddy in NL (IIRC). He echoed the midi  
> data back to me which I recorded and determined the round trip  
> latency. I think it was about 600ms.
> (3) What prompted the experiment (where's the Youtube clip?) were  
> some very successful tests (no noticeable latency) I had done  
> controlling gear hooked up to one computer from a controller hooked  
> up to another computer across the room but via a router. (Of course,  
> I was using 8-bit midi.)
>
> So, thanks for the offer to forget midi, but I am a dinosaur myself  
> and I like dinosaur gear.
>
> Oh, yeah, even as a dinosaur, I stick by my claim of looking towards  
> future possibilities. Always did; always will. I did that when I was  
> in my teens, too--when I envisioned controlling a synth (Moog  
> modular) with a computer. It was unheard of back then. In fact, one  
> of my professors told me, "What a waste of a computer!" Needless to  
> say, I should have told him "Bullshit," and tried to find a  
> professor or a program that had the ability to envision future  
> possibilities.
>
> Again, I try my best to help people with issues they have. Those  
> efforts are future-solution oriented. I envision possibilities. But  
> I do so mindful of the past.
>
> I am not sure who said, "the past informs the present to ideally  
> improve the future," but I think there is merit in that approach-- 
> whether it be on a small-scale, near-term problem-solution or a  
> large-scale, long-term one.
>
> I see no problem with integrating the old with the new with an eye  
> towards the future.
>
> Steve
>
> PS: When I first read and responded to your reply to my comment  
> about the future, I did not see any arrogance, agism, or sarcasm  
> whatsoever. I usually don't pick up on stuff like that even when it  
> is there. In fact, it didn't even occur to me you might be doing  
> that until sometime after I had innocently started penning the  
> footnotes by way of simple clarification. However, in retrospect,  
> your tone seems clear--everything you wrote was a reply to my  
> comment that "I try to look at future possibilities."
>
> It seems that your lead in, "Then maybe better forget about MIDI  
> after all," was a retort, a challenge.
>
> Of course, it is hard to tell attitude in printed text messages  
> posted on a forum. So, if you weren't being sarcastic and arrogant,  
> I happily withdraw the suggestion that it might have been.
>
> steve_the_visionary_dinosaur  ;)
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Jason Adkins

Not my thing Notator, Cubase has always been my sequencer of choice  
although I did mess about with Breakthru 2+ at one point.
I have 4 ST's but only using one,the Mega STE with internal HD.
Sorry Daniel I was playing games on them in 1987 ;)
I have a Mega as well,coolest looking ST.

J
Show quoted textHide quoted text
On 22 Aug 2013, at 15:37, Daniel Forró wrote:

> Agreement.
>
> Three ATARI still at my side, one Mega ST on my table with two HD and
> Ultrasatan. I've been using them since 1988 :-) I was more Notator
> user but Cubase had some good features...
>
> Daniel Forro
>
> On 22 Aug, 2013, at 11:16 PM, k9k9dog wrote:
>
>> lol. MIDI sample dump cannot even be envisaged. dot.
>> i hope nobody's going to start sl*gging MIDI (again).
>> quite simply one of the best human inventions ever.
>> what about wordclocking? (i'm only kidding, send it
>> via your old ADAT...). word.
>>
>> i'm serious about caged artist: it works beautifully.
>> everyone should have an atari kicking around for all
>> it can do. i just got one *nicked* during a housemove,
>> of all things they could have taken...consider: editors,
>> old sequencers, the cubase Interactive Phrase Synth as
>> arpeggiator, etc.(slow workflow, crashes in hot weather)
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Daniel Forró

On 23 Aug, 2013, at 12:45 AM, Jason Adkins wrote:

> Not my thing Notator, Cubase has always been my sequencer of choice
> although I did mess about with Breakthru 2+ at one point.

I didn't like linear type of sequencer, pattern oriented Notator  
seemed to me more flexible and could be also used in linear way when  
necessary. And it offered better notation than early Cubase.

> I have 4 ST's but only using one,the Mega STE with internal HD.
> Sorry Daniel I was playing games on them in 1987 ;)

For this (and of course for music) I had Commodore 64 and Yamaha CX5M  
since 1985 :-)

Daniel Forro

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Jason Adkins

For patterned based sequencing I'd use an MC50 or Alesis MMT8,even  
thought it has an AC psu with iffy style connector 3,5inch jack I  
think? and crappy rubber buttons but a great sequencer nonetheless.
The CX5M was nice actually,looked cool too,Iike said before I  
programed a crude looking naked woman controlled by the cursor keys on  
the  msx,my first ever bit of programming,,,

The C64 was a nightmare to program in comparison,It's only saving  
grace was it's popularity and the SID chip...... However Steinberg  
ever managed to program Pro16 on that thing I'll never know.
Show quoted textHide quoted text
>
> For this (and of course for music) I had Commodore 64 and Yamaha CX5M
> since 1985 :-)
>
> Daniel Forro
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Lee Borrell

I have to admit the CX5m looks like something the aliens left on earth in 2001,Space Odyssey...but it suffers from a basic written by MS,which once I started looking into it started spotting all the old annoying habits that cause Windows to be so crap. I would take a Commodore before a CX. The OS in that has never failed me and is intuitive and easy to use. 
The only drawback was not having MIDI on tap - which I corrected by making my own interface,which was thankfully given by MAPLIN in their magazine. The Interface once made is dead easy to use,and easier to communicate with than either the Atari ST or the CX5m.

http://templarseries.atspace.com/maplin.html




________________________________
Show quoted textHide quoted text
 From: Jason Adkins <jason_ralf808@....uk>
To: CZsynth@yahoogroups.com 
Sent: Thursday, 22 August 2013, 19:30
Subject: Re: [CZsynth] Re: Speed of sysex transfer
 


  
For patterned based sequencing I'd use an MC50 or Alesis MMT8,even 
thought it has an AC psu with iffy style connector 3,5inch jack I 
think? and crappy rubber buttons but a great sequencer nonetheless.
The CX5M was nice actually,looked cool too,Iike said before I 
programed a crude looking naked woman controlled by the cursor keys on 
the  msx,my first ever bit of programming,,,

The C64 was a nightmare to program in comparison,It's only saving 
grace was it's popularity and the SID chip...... However Steinberg 
ever managed to program Pro16 on that thing I'll never know.

>
> For this (and of course for music) I had Commodore 64 and Yamaha CX5M
> since 1985 :-)
>
> Daniel Forro
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>


 

[Non-text portions of this message have been removed]

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-22 by Jason Adkins

lol,I don't agree with you the MSX basic was way better than the C64  
crap basic,I agree the SID chip was way better than any other sound  
chip put into a computer of that era or probably of any era,hence that  
little synth and virtual,weirdly enough the Atari ST can do a great  
SID emulation.I agree with you about Maplin they certainly are not  
what they used to be,f""king expensive to...
Have you got an Amiga by any chance?
Show quoted textHide quoted text
On 22 Aug 2013, at 19:48, Lee Borrell wrote:

> I have to admit the CX5m looks like something the aliens left on  
> earth in 2001,Space Odyssey...but it suffers from a basic written by  
> MS,which once I started looking into it started spotting all the old  
> annoying habits that cause Windows to be so crap. I would take a  
> Commodore before a CX. The OS in that has never failed me and is  
> intuitive and easy to use.
> The only drawback was not having MIDI on tap - which I corrected by  
> making my own interface,which was thankfully given by MAPLIN in  
> their magazine. The Interface once made is dead easy to use,and  
> easier to communicate with than either the Atari ST or the CX5m.
>
> http://templarseries.atspace.com/maplin.html
>
>
>
>
> ________________________________
> From: Jason Adkins <jason_ralf808@...>
> To: CZsynth@yahoogroups.com
> Sent: Thursday, 22 August 2013, 19:30
> Subject: Re: [CZsynth] Re: Speed of sysex transfer
>
>
>
>
> For patterned based sequencing I'd use an MC50 or Alesis MMT8,even
> thought it has an AC psu with iffy style connector 3,5inch jack I
> think? and crappy rubber buttons but a great sequencer nonetheless.
> The CX5M was nice actually,looked cool too,Iike said before I
> programed a crude looking naked woman controlled by the cursor keys on
> the  msx,my first ever bit of programming,,,
>
> The C64 was a nightmare to program in comparison,It's only saving
> grace was it's popularity and the SID chip...... However Steinberg
> ever managed to program Pro16 on that thing I'll never know.
>
>>
>> For this (and of course for music) I had Commodore 64 and Yamaha CX5M
>> since 1985 :-)
>>
>> Daniel Forro
>>
>>
>> ------------------------------------
>>
>> Yahoo! Groups Links
>>
>>
>>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by jammie

actually we have proven usb midi does drop notes out of time using an oscilloscope 

and expersleepers software and usb timing is not rock solid as midi from the st

or expert sleepers audio to midi which is just great 

 http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php

heres a video showing you 

defy away but thats just one example of many 
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Loscha 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 1:37 PM
  Subject: Re: [CZsynth] Speed of sysex transfer


    
  You assert that MIDI over USB is sloppy.

  This is the same as a schoolgirl saying toads gice you warts!!!

  If you look at a MIDI USB over an oscilloscope, as I have, you'll see
  it is just fine. I do not have any pictures to document this, sadly --
  and my scope is not currently set up.

  I defy you to produce factual evidence to the contrary, however!

  MiDI is not ideal for tight timing.
  If you look at, say, laying a 4 down kick drum on a track, unless that
  tempo you are using is an integer divisor of 31250, it's going to flop
  around and not be in time.
  Period.

  On 8/22/13, jammie <jammie.emma@...> wrote:
  > you could fit a lan midi port on the cz this is attached to the pre opto
  > isolaters of the uart
  >
  > then you can use midi over lan
  >
  > but the midi protocol is still 31.25kb period thats the standard set
  >
  > but the problem lies with the usb and windows changing it from win98
  >
  > and since then midi timing has been sloppy
  >
  > now a parallel interface is much better and timing is much better
  >
  > so a opcode x64 which i still use and has xp 32 and 64bit drivers
  >
  > and i have never had any problems with sysex
  >
  > but i still use sound diver and changeit which is a great sysex sender and
  > has a section for slowing down packets
  > ----- Original Message -----
  > From: Lee Borrell
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, August 22, 2013 12:47 PM
  > Subject: Re: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > I think if you talking about USB to USB transfer - or Firewire then you
  > may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS
  > to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN
  > plugs on it is going to do better than that baud rate,or face the equipment
  > not getting the signal. In the case of pre-USB vintage machines,there is no
  > way to go faster than 31.25kB.
  >
  > ________________________________
  > From: fulfil_objective <robot@...>
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, 22 August 2013, 7:21
  > Subject: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > Hi Steve,
  >
  > I think you are too focused on these vintage numbers like 31250 bps and
  > 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
  > numbers. USB enables speeds that are hundreds or thousands of times faster
  > than these numbers. In fact, greatly higher speeds are touted as one of the
  > benefits of a USB MIDI device (along with multiple streams).
  >
  > High speed sysex transfer is both desired and encouraged, for example, in
  > the case of sending sound data to a sampler. If you wanted to send 128
  > megabytes of sounds to your sampler, and if you were restricted to 31250
  > bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
  > higher speeds, and that speed is encouraged.
  >
  > 31250 bps is the speed of an old dialup modem (actual throughput) on a
  > good day. If you tested at 115200 bps, that is merely 3.7 times faster than
  > 31250 bps. Still very slow by today's standards.
  >
  > USB 2.0 has a max throughput of something like 35 MB/s. But lets be
  > generous and say that in the real world, you can only get your USB 2.0 to 20
  > MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
  > times faster than 31250 bps.
  >
  > So yes, I think a capable modern computer with a good USB system can send
  > sysex out faster than the CZ can deal with it. And it's not necessarily tied
  > to CPU speed of the computer either, more like the speed of the whole
  > computer-USB system.
  >
  > You will probably find it enlightening to read the "Universal Serial Bus
  > Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which
  > you cand download here:
  >
  > http://www.usb.org/developers/devclass_docs/midi10.pdf
  >
  > [Non-text portions of this message have been removed]
  >
  >
  >
  >
  > No virus found in this message.
  > Checked by AVG - www.avg.com
  > Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
  >
  >
  > [Non-text portions of this message have been removed]
  >
  >


  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13


[Non-text portions of this message have been removed]

Re: Speed of sysex transfer

2013-08-22 by fulfil_objective

Wow! Quite a lot of traffic in the old yahoo group today! :c)

It looks like a made some highly erroneous statements, and I thank all of you for frankly calling bullshit on those things. May the five pins always receive data at 31250 bps.

"Turd", "LOL", no problem with those either. Thanks guys!

I agree with Steve that misinformation on the web can be a strong and bad influence. The responses to my original message are clear, and overall I think it's a good discussion. Thanks to Bernard and Richard for the good and concise summaries of the real issue.

Man do you remember that guy who thought sysex could go faster than 31250 bps. What a doofus!

Thanks again guys!

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Lee Borrell

I am not quite clear on the mis-timing issue.

MIDI is asynchronous - each item has it's own master clock used to transfer the bits across the communicating line at 31.25 Kb - the timing of the MIDI clock is different than the clock used to clock the signals across the line,which is usually derived from a 1-4Mhz master clock.

The synchronization of any timing MIDI signal is thence due to the arrival of the timing message comprising the 8 bits of the System clock messages.
 The MIDI system is capable of sending 31250 bits per second and the timing message is 8 bits - even if it was an entire midi message of 3x8bits (24 bits) this is still some 1300 messages during that time. Normal tempos of 120 or so BPM are hardly going to drift significantly are they?

I am open to "Bullshit calls" as I am just querying just how much any timing is likely to be out using 31.25 Kb?




________________________________
Show quoted textHide quoted text
 From: jammie <jammie.emma@...>
To: CZsynth@yahoogroups.com 
Sent: Thursday, 22 August 2013, 21:40
Subject: Re: [CZsynth] Speed of sysex transfer
 


  
actually we have proven usb midi does drop notes out of time using an oscilloscope 

and expersleepers software and usb timing is not rock solid as midi from the st

or expert sleepers audio to midi which is just great 

http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php

heres a video showing you 

defy away but thats just one example of many 

----- Original Message ----- 
From: Loscha 
To: CZsynth@yahoogroups.com 
Sent: Thursday, August 22, 2013 1:37 PM
Subject: Re: [CZsynth] Speed of sysex transfer

You assert that MIDI over USB is sloppy.

This is the same as a schoolgirl saying toads gice you warts!!!

If you look at a MIDI USB over an oscilloscope, as I have, you'll see
it is just fine. I do not have any pictures to document this, sadly --
and my scope is not currently set up.

I defy you to produce factual evidence to the contrary, however!

MiDI is not ideal for tight timing.
If you look at, say, laying a 4 down kick drum on a track, unless that
tempo you are using is an integer divisor of 31250, it's going to flop
around and not be in time.
Period.

On 8/22/13, jammie <jammie.emma@...> wrote:
> you could fit a lan midi port on the cz this is attached to the pre opto
> isolaters of the uart
>
> then you can use midi over lan
>
> but the midi protocol is still 31.25kb period thats the standard set
>
> but the problem lies with the usb and windows changing it from win98
>
> and since then midi timing has been sloppy
>
> now a parallel interface is much better and timing is much better
>
> so a opcode x64 which i still use and has xp 32 and 64bit drivers
>
> and i have never had any problems with sysex
>
> but i still use sound diver and changeit which is a great sysex sender and
> has a section for slowing down packets
> ----- Original Message -----
> From: Lee Borrell
> To: CZsynth@yahoogroups.com
> Sent: Thursday, August 22, 2013 12:47 PM
> Subject: Re: [CZsynth] Speed of sysex transfer
>
>
>
> I think if you talking about USB to USB transfer - or Firewire then you
> may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS
> to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN
> plugs on it is going to do better than that baud rate,or face the equipment
> not getting the signal. In the case of pre-USB vintage machines,there is no
> way to go faster than 31.25kB.
>
> ________________________________
> From: fulfil_objective <robot@...>
> To: CZsynth@...m
> Sent: Thursday, 22 August 2013, 7:21
> Subject: [CZsynth] Speed of sysex transfer
>
>
>
> Hi Steve,
>
> I think you are too focused on these vintage numbers like 31250 bps and
> 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
> numbers. USB enables speeds that are hundreds or thousands of times faster
> than these numbers. In fact, greatly higher speeds are touted as one of the
> benefits of a USB MIDI device (along with multiple streams).
>
> High speed sysex transfer is both desired and encouraged, for example, in
> the case of sending sound data to a sampler. If you wanted to send 128
> megabytes of sounds to your sampler, and if you were restricted to 31250
> bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
> higher speeds, and that speed is encouraged.
>
> 31250 bps is the speed of an old dialup modem (actual throughput) on a
> good day. If you tested at 115200 bps, that is merely 3.7 times faster than
> 31250 bps. Still very slow by today's standards.
>
> USB 2.0 has a max throughput of something like 35 MB/s. But lets be
> generous and say that in the real world, you can only get your USB 2.0 to 20
> MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
> times faster than 31250 bps.
>
> So yes, I think a capable modern computer with a good USB system can send
> sysex out faster than the CZ can deal with it. And it's not necessarily tied
> to CPU speed of the computer either, more like the speed of the whole
> computer-USB system.
>
> You will probably find it enlightening to read the "Universal Serial Bus
> Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which
> you cand download here:
>
> http://www.usb.org/developers/devclass_docs/midi10.pdf
>
> [Non-text portions of this message have been removed]
>
>
>
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
>
>
> [Non-text portions of this message have been removed]
>
>

No virus found in this message.
Checked by AVG - www.avg.com
Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13

[Non-text portions of this message have been removed]


 

[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Loscha

This video does NOT prove USB MIDI interfaces do not have rock solid
timing. This is corporate BS trying to pain their product (which
multiplexes variate CV destinations through SPDIF - a pretty clever
trick) and how that has nice tight timing.

The video displays, however exactly what I described -- unless the
tempo of you song is an INTEGER DIVISOR (THAT'S A WHOLE NUMBER), you
will not get a MIDI stream that wil exactly describe your 'groove' as
a stream of MIDI notes.

It's like GIF. GIF is a beautiful and often the most elegant file
format, to use after all these years, but some people say it's a lossy
format. This displays an incomplete knowledge of the format. You MUST
reduce the color palette to 255 or less colors to be encoded into a
GIF.

MIDI is like your basic Nexus 6. It was built as good as they could be
made, but in 1982 - when they started -- there were electronic
tradeoffs that had to be made. Sadly, MIDI didn't have a 5 year life
span.

Still no evidence that USB MIDI interfaces produce 'flubby' timing.
Just furster evidence that MIDI is not your best friend for a 4 down
drum beat.

DIN Synch 24 is a a much better choice for tight repeditive rhythmic timing.

For all it's flaws, however -- MIDI is so much better than what almost
happened -- every manufacturer with their own Bus design, which would
probably be modified and kept in service for a few years only anyway
-- Look at DCB fer cryin out loud. That Could have been MIDI!!! Or the
other way around!
Show quoted textHide quoted text
On 8/23/13, jammie <jammie.emma@...> wrote:
> actually we have proven usb midi does drop notes out of time using an
> oscilloscope
>
> and expersleepers software and usb timing is not rock solid as midi from the
> st
>
> or expert sleepers audio to midi which is just great
>
> http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php
>
> heres a video showing you
>
> defy away but thats just one example of many
>
>   ----- Original Message -----
>   From: Loscha
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, August 22, 2013 1:37 PM
>   Subject: Re: [CZsynth] Speed of sysex transfer
>
>
>
>   You assert that MIDI over USB is sloppy.
>
>   This is the same as a schoolgirl saying toads gice you warts!!!
>
>   If you look at a MIDI USB over an oscilloscope, as I have, you'll see
>   it is just fine. I do not have any pictures to document this, sadly --
>   and my scope is not currently set up.
>
>   I defy you to produce factual evidence to the contrary, however!
>
>   MiDI is not ideal for tight timing.
>   If you look at, say, laying a 4 down kick drum on a track, unless that
>   tempo you are using is an integer divisor of 31250, it's going to flop
>   around and not be in time.
>   Period.
>
>   On 8/22/13, jammie <jammie.emma@...> wrote:
>   > you could fit a lan midi port on the cz this is attached to the pre
> opto
>   > isolaters of the uart
>   >
>   > then you can use midi over lan
>   >
>   > but the midi protocol is still 31.25kb period thats the standard set
>   >
>   > but the problem lies with the usb and windows changing it from win98
>   >
>   > and since then midi timing has been sloppy
>   >
>   > now a parallel interface is much better and timing is much better
>   >
>   > so a opcode x64 which i still use and has xp 32 and 64bit drivers
>   >
>   > and i have never had any problems with sysex
>   >
>   > but i still use sound diver and changeit which is a great sysex sender
> and
>   > has a section for slowing down packets
>   > ----- Original Message -----
>   > From: Lee Borrell
>   > To: CZsynth@yahoogroups.com
>   > Sent: Thursday, August 22, 2013 12:47 PM
>   > Subject: Re: [CZsynth] Speed of sysex transfer
>   >
>   >
>   >
>   > I think if you talking about USB to USB transfer - or Firewire then you
>   > may have a point ,but as soon as any interface hits a MIDI DIN plug it
> HAS
>   > to be 31.25 Kb - this is the MIDI standard. No commercial interface with
> DIN
>   > plugs on it is going to do better than that baud rate,or face the
> equipment
>   > not getting the signal. In the case of pre-USB vintage machines,there is
> no
>   > way to go faster than 31.25kB.
>   >
>   > ________________________________
>   > From: fulfil_objective <robot@...>
>   > To: CZsynth@yahoogroups.com
>   > Sent: Thursday, 22 August 2013, 7:21
>   > Subject: [CZsynth] Speed of sysex transfer
>   >
>   >
>   >
>   > Hi Steve,
>   >
>   > I think you are too focused on these vintage numbers like 31250 bps and
>   > 115200 bps. Transferring sysex by USB and MIDI are not limited to these
> old
>   > numbers. USB enables speeds that are hundreds or thousands of times
> faster
>   > than these numbers. In fact, greatly higher speeds are touted as one of
> the
>   > benefits of a USB MIDI device (along with multiple streams).
>   >
>   > High speed sysex transfer is both desired and encouraged, for example,
> in
>   > the case of sending sound data to a sampler. If you wanted to send 128
>   > megabytes of sounds to your sampler, and if you were restricted to
> 31250
>   > bps, it would take 9.5 hours to send the sounds. USB MIDI devices
> enable
>   > higher speeds, and that speed is encouraged.
>   >
>   > 31250 bps is the speed of an old dialup modem (actual throughput) on a
>   > good day. If you tested at 115200 bps, that is merely 3.7 times faster
> than
>   > 31250 bps. Still very slow by today's standards.
>   >
>   > USB 2.0 has a max throughput of something like 35 MB/s. But lets be
>   > generous and say that in the real world, you can only get your USB 2.0
> to 20
>   > MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
>   > times faster than 31250 bps.
>   >
>   > So yes, I think a capable modern computer with a good USB system can
> send
>   > sysex out faster than the CZ can deal with it. And it's not necessarily
> tied
>   > to CPU speed of the computer either, more like the speed of the whole
>   > computer-USB system.
>   >
>   > You will probably find it enlightening to read the "Universal Serial
> Bus
>   > Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999,
> which
>   > you cand download here:
>   >
>   > http://www.usb.org/developers/devclass_docs/midi10.pdf
>   >
>   > [Non-text portions of this message have been removed]
>   >
>   >
>   >
>   >
>   > No virus found in this message.
>   > Checked by AVG - www.avg.com
>   > Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date:
> 08/21/13
>   >
>   >
>   > [Non-text portions of this message have been removed]
>   >
>   >
>
>
>
>   No virus found in this message.
>   Checked by AVG - www.avg.com
>   Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13
>
>
> [Non-text portions of this message have been removed]
>
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by jammie

its the usb thats the problem not the midi 

usb to midi interfaces are the ones that mess up midi timing

my hardware sequencers mpc60 and the quasimidi cyber6 dont suffer like certain usb to midi devices

and its also proven that not all usb to midi devices are equal as proven by some not sending sysex properly
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Lee Borrell 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 10:58 PM
  Subject: Re: [CZsynth] Speed of sysex transfer


    
  I am not quite clear on the mis-timing issue.

  MIDI is asynchronous - each item has it's own master clock used to transfer the bits across the communicating line at 31.25 Kb - the timing of the MIDI clock is different than the clock used to clock the signals across the line,which is usually derived from a 1-4Mhz master clock.

  The synchronization of any timing MIDI signal is thence due to the arrival of the timing message comprising the 8 bits of the System clock messages.
   The MIDI system is capable of sending 31250 bits per second and the timing message is 8 bits - even if it was an entire midi message of 3x8bits (24 bits) this is still some 1300 messages during that time. Normal tempos of 120 or so BPM are hardly going to drift significantly are they?

  I am open to "Bullshit calls" as I am just querying just how much any timing is likely to be out using 31.25 Kb?

  ________________________________
  From: jammie <jammie.emma@...>
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, 22 August 2013, 21:40
  Subject: Re: [CZsynth] Speed of sysex transfer


    
  actually we have proven usb midi does drop notes out of time using an oscilloscope 

  and expersleepers software and usb timing is not rock solid as midi from the st

  or expert sleepers audio to midi which is just great 

  http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php

  heres a video showing you 

  defy away but thats just one example of many 

  ----- Original Message ----- 
  From: Loscha 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 1:37 PM
  Subject: Re: [CZsynth] Speed of sysex transfer

  You assert that MIDI over USB is sloppy.

  This is the same as a schoolgirl saying toads gice you warts!!!

  If you look at a MIDI USB over an oscilloscope, as I have, you'll see
  it is just fine. I do not have any pictures to document this, sadly --
  and my scope is not currently set up.

  I defy you to produce factual evidence to the contrary, however!

  MiDI is not ideal for tight timing.
  If you look at, say, laying a 4 down kick drum on a track, unless that
  tempo you are using is an integer divisor of 31250, it's going to flop
  around and not be in time.
  Period.

  On 8/22/13, jammie <jammie.emma@...> wrote:
  > you could fit a lan midi port on the cz this is attached to the pre opto
  > isolaters of the uart
  >
  > then you can use midi over lan
  >
  > but the midi protocol is still 31.25kb period thats the standard set
  >
  > but the problem lies with the usb and windows changing it from win98
  >
  > and since then midi timing has been sloppy
  >
  > now a parallel interface is much better and timing is much better
  >
  > so a opcode x64 which i still use and has xp 32 and 64bit drivers
  >
  > and i have never had any problems with sysex
  >
  > but i still use sound diver and changeit which is a great sysex sender and
  > has a section for slowing down packets
  > ----- Original Message -----
  > From: Lee Borrell
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, August 22, 2013 12:47 PM
  > Subject: Re: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > I think if you talking about USB to USB transfer - or Firewire then you
  > may have a point ,but as soon as any interface hits a MIDI DIN plug it HAS
  > to be 31.25 Kb - this is the MIDI standard. No commercial interface with DIN
  > plugs on it is going to do better than that baud rate,or face the equipment
  > not getting the signal. In the case of pre-USB vintage machines,there is no
  > way to go faster than 31.25kB.
  >
  > ________________________________
  > From: fulfil_objective <robot@...>
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, 22 August 2013, 7:21
  > Subject: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > Hi Steve,
  >
  > I think you are too focused on these vintage numbers like 31250 bps and
  > 115200 bps. Transferring sysex by USB and MIDI are not limited to these old
  > numbers. USB enables speeds that are hundreds or thousands of times faster
  > than these numbers. In fact, greatly higher speeds are touted as one of the
  > benefits of a USB MIDI device (along with multiple streams).
  >
  > High speed sysex transfer is both desired and encouraged, for example, in
  > the case of sending sound data to a sampler. If you wanted to send 128
  > megabytes of sounds to your sampler, and if you were restricted to 31250
  > bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
  > higher speeds, and that speed is encouraged.
  >
  > 31250 bps is the speed of an old dialup modem (actual throughput) on a
  > good day. If you tested at 115200 bps, that is merely 3.7 times faster than
  > 31250 bps. Still very slow by today's standards.
  >
  > USB 2.0 has a max throughput of something like 35 MB/s. But lets be
  > generous and say that in the real world, you can only get your USB 2.0 to 20
  > MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
  > times faster than 31250 bps.
  >
  > So yes, I think a capable modern computer with a good USB system can send
  > sysex out faster than the CZ can deal with it. And it's not necessarily tied
  > to CPU speed of the computer either, more like the speed of the whole
  > computer-USB system.
  >
  > You will probably find it enlightening to read the "Universal Serial Bus
  > Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, which
  > you cand download here:
  >
  > http://www.usb.org/developers/devclass_docs/midi10.pdf
  >
  > [Non-text portions of this message have been removed]
  >
  >
  >
  >
  > No virus found in this message.
  > Checked by AVG - www.avg.com
  > Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
  >
  >
  > [Non-text portions of this message have been removed]
  >
  >

  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13

  [Non-text portions of this message have been removed]

  [Non-text portions of this message have been removed]



  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13


[Non-text portions of this message have been removed]

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by Loscha

If you make a video of audio on on trace of your scope, and MIDI on
the other for any device, ANY device, you will get the exact same
video.

Shift the tempo around in it's smallest increment (most things 1 BPM,
I've got a Dr-202 which happily changes at 1/10th a BPM) and the
difference in timing, amount of note leading/lagging slightly will
change.

The drum machine triggers notes to it's own internal CPU update. Could
be something like 1Mhz or at least several hundred Kb.

Many MIDI devices I've got have trouble keeping time if you change
settings around, but - hey, I've got a Quasimidi Raveolution, the
notoriously worst thing in the world for disappearing beats when using
some menufunctions.
Show quoted textHide quoted text
On 8/23/13, jammie <jammie.emma@...> wrote:
> its the usb thats the problem not the midi
>
> usb to midi interfaces are the ones that mess up midi timing
>
> my hardware sequencers mpc60 and the quasimidi cyber6 dont suffer like
> certain usb to midi devices
>
> and its also proven that not all usb to midi devices are equal as proven by
> some not sending sysex properly
>
>
>   ----- Original Message -----
>   From: Lee Borrell
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, August 22, 2013 10:58 PM
>   Subject: Re: [CZsynth] Speed of sysex transfer
>
>
>
>   I am not quite clear on the mis-timing issue.
>
>   MIDI is asynchronous - each item has it's own master clock used to
> transfer the bits across the communicating line at 31.25 Kb - the timing of
> the MIDI clock is different than the clock used to clock the signals across
> the line,which is usually derived from a 1-4Mhz master clock.
>
>   The synchronization of any timing MIDI signal is thence due to the arrival
> of the timing message comprising the 8 bits of the System clock messages.
>    The MIDI system is capable of sending 31250 bits per second and the
> timing message is 8 bits - even if it was an entire midi message of 3x8bits
> (24 bits) this is still some 1300 messages during that time. Normal tempos
> of 120 or so BPM are hardly going to drift significantly are they?
>
>   I am open to "Bullshit calls" as I am just querying just how much any
> timing is likely to be out using 31.25 Kb?
>
>   ________________________________
>   From: jammie <jammie.emma@...>
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, 22 August 2013, 21:40
>   Subject: Re: [CZsynth] Speed of sysex transfer
>
>
>
>   actually we have proven usb midi does drop notes out of time using an
> oscilloscope
>
>   and expersleepers software and usb timing is not rock solid as midi from
> the st
>
>   or expert sleepers audio to midi which is just great
>
>
> http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php
>
>   heres a video showing you
>
>   defy away but thats just one example of many
>
>   ----- Original Message -----
>   From: Loscha
>   To: CZsynth@yahoogroups.com
>   Sent: Thursday, August 22, 2013 1:37 PM
>   Subject: Re: [CZsynth] Speed of sysex transfer
>
>   You assert that MIDI over USB is sloppy.
>
>   This is the same as a schoolgirl saying toads gice you warts!!!
>
>   If you look at a MIDI USB over an oscilloscope, as I have, you'll see
>   it is just fine. I do not have any pictures to document this, sadly --
>   and my scope is not currently set up.
>
>   I defy you to produce factual evidence to the contrary, however!
>
>   MiDI is not ideal for tight timing.
>   If you look at, say, laying a 4 down kick drum on a track, unless that
>   tempo you are using is an integer divisor of 31250, it's going to flop
>   around and not be in time.
>   Period.
>
>   On 8/22/13, jammie <jammie.emma@...> wrote:
>   > you could fit a lan midi port on the cz this is attached to the pre
> opto
>   > isolaters of the uart
>   >
>   > then you can use midi over lan
>   >
>   > but the midi protocol is still 31.25kb period thats the standard set
>   >
>   > but the problem lies with the usb and windows changing it from win98
>   >
>   > and since then midi timing has been sloppy
>   >
>   > now a parallel interface is much better and timing is much better
>   >
>   > so a opcode x64 which i still use and has xp 32 and 64bit drivers
>   >
>   > and i have never had any problems with sysex
>   >
>   > but i still use sound diver and changeit which is a great sysex sender
> and
>   > has a section for slowing down packets
>   > ----- Original Message -----
>   > From: Lee Borrell
>   > To: CZsynth@yahoogroups.com
>   > Sent: Thursday, August 22, 2013 12:47 PM
>   > Subject: Re: [CZsynth] Speed of sysex transfer
>   >
>   >
>   >
>   > I think if you talking about USB to USB transfer - or Firewire then you
>   > may have a point ,but as soon as any interface hits a MIDI DIN plug it
> HAS
>   > to be 31.25 Kb - this is the MIDI standard. No commercial interface with
> DIN
>   > plugs on it is going to do better than that baud rate,or face the
> equipment
>   > not getting the signal. In the case of pre-USB vintage machines,there is
> no
>   > way to go faster than 31.25kB.
>   >
>   > ________________________________
>   > From: fulfil_objective <robot@...>
>   > To: CZsynth@yahoogroups.com
>   > Sent: Thursday, 22 August 2013, 7:21
>   > Subject: [CZsynth] Speed of sysex transfer
>   >
>   >
>   >
>   > Hi Steve,
>   >
>   > I think you are too focused on these vintage numbers like 31250 bps and
>   > 115200 bps. Transferring sysex by USB and MIDI are not limited to these
> old
>   > numbers. USB enables speeds that are hundreds or thousands of times
> faster
>   > than these numbers. In fact, greatly higher speeds are touted as one of
> the
>   > benefits of a USB MIDI device (along with multiple streams).
>   >
>   > High speed sysex transfer is both desired and encouraged, for example,
> in
>   > the case of sending sound data to a sampler. If you wanted to send 128
>   > megabytes of sounds to your sampler, and if you were restricted to
> 31250
>   > bps, it would take 9.5 hours to send the sounds. USB MIDI devices
> enable
>   > higher speeds, and that speed is encouraged.
>   >
>   > 31250 bps is the speed of an old dialup modem (actual throughput) on a
>   > good day. If you tested at 115200 bps, that is merely 3.7 times faster
> than
>   > 31250 bps. Still very slow by today's standards.
>   >
>   > USB 2.0 has a max throughput of something like 35 MB/s. But lets be
>   > generous and say that in the real world, you can only get your USB 2.0
> to 20
>   > MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
>   > times faster than 31250 bps.
>   >
>   > So yes, I think a capable modern computer with a good USB system can
> send
>   > sysex out faster than the CZ can deal with it. And it's not necessarily
> tied
>   > to CPU speed of the computer either, more like the speed of the whole
>   > computer-USB system.
>   >
>   > You will probably find it enlightening to read the "Universal Serial
> Bus
>   > Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999,
> which
>   > you cand download here:
>   >
>   > http://www.usb.org/developers/devclass_docs/midi10.pdf
>   >
>   > [Non-text portions of this message have been removed]
>   >
>   >
>   >
>   >
>   > No virus found in this message.
>   > Checked by AVG - www.avg.com
>   > Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date:
> 08/21/13
>   >
>   >
>   > [Non-text portions of this message have been removed]
>   >
>   >
>
>   No virus found in this message.
>   Checked by AVG - www.avg.com
>   Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13
>
>   [Non-text portions of this message have been removed]
>
>   [Non-text portions of this message have been removed]
>
>
>
>
>   No virus found in this message.
>   Checked by AVG - www.avg.com
>   Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13
>
>
> [Non-text portions of this message have been removed]
>
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by jammie

i always found the sequencer crap on the ravolution and why i sold mine

but the cyber6 has a nice 8 track sequencer and is much better to program and to string sequences to make songs

i still use my st for a lot of sequencing and i use the daws for audio via my dsp cards

each to there own 
Show quoted textHide quoted text
  ----- Original Message ----- 
  From: Loscha 
  To: CZsynth@yahoogroups.com 
  Sent: Thursday, August 22, 2013 11:38 PM
  Subject: Re: [CZsynth] Speed of sysex transfer


    
  If you make a video of audio on on trace of your scope, and MIDI on
  the other for any device, ANY device, you will get the exact same
  video.

  Shift the tempo around in it's smallest increment (most things 1 BPM,
  I've got a Dr-202 which happily changes at 1/10th a BPM) and the
  difference in timing, amount of note leading/lagging slightly will
  change.

  The drum machine triggers notes to it's own internal CPU update. Could
  be something like 1Mhz or at least several hundred Kb.

  Many MIDI devices I've got have trouble keeping time if you change
  settings around, but - hey, I've got a Quasimidi Raveolution, the
  notoriously worst thing in the world for disappearing beats when using
  some menufunctions.

  On 8/23/13, jammie <jammie.emma@...> wrote:
  > its the usb thats the problem not the midi
  >
  > usb to midi interfaces are the ones that mess up midi timing
  >
  > my hardware sequencers mpc60 and the quasimidi cyber6 dont suffer like
  > certain usb to midi devices
  >
  > and its also proven that not all usb to midi devices are equal as proven by
  > some not sending sysex properly
  >
  >
  > ----- Original Message -----
  > From: Lee Borrell
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, August 22, 2013 10:58 PM
  > Subject: Re: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > I am not quite clear on the mis-timing issue.
  >
  > MIDI is asynchronous - each item has it's own master clock used to
  > transfer the bits across the communicating line at 31.25 Kb - the timing of
  > the MIDI clock is different than the clock used to clock the signals across
  > the line,which is usually derived from a 1-4Mhz master clock.
  >
  > The synchronization of any timing MIDI signal is thence due to the arrival
  > of the timing message comprising the 8 bits of the System clock messages.
  > The MIDI system is capable of sending 31250 bits per second and the
  > timing message is 8 bits - even if it was an entire midi message of 3x8bits
  > (24 bits) this is still some 1300 messages during that time. Normal tempos
  > of 120 or so BPM are hardly going to drift significantly are they?
  >
  > I am open to "Bullshit calls" as I am just querying just how much any
  > timing is likely to be out using 31.25 Kb?
  >
  > ________________________________
  > From: jammie <jammie.emma@...>
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, 22 August 2013, 21:40
  > Subject: Re: [CZsynth] Speed of sysex transfer
  >
  >
  >
  > actually we have proven usb midi does drop notes out of time using an
  > oscilloscope
  >
  > and expersleepers software and usb timing is not rock solid as midi from
  > the st
  >
  > or expert sleepers audio to midi which is just great
  >
  >
  > http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php
  >
  > heres a video showing you
  >
  > defy away but thats just one example of many
  >
  > ----- Original Message -----
  > From: Loscha
  > To: CZsynth@yahoogroups.com
  > Sent: Thursday, August 22, 2013 1:37 PM
  > Subject: Re: [CZsynth] Speed of sysex transfer
  >
  > You assert that MIDI over USB is sloppy.
  >
  > This is the same as a schoolgirl saying toads gice you warts!!!
  >
  > If you look at a MIDI USB over an oscilloscope, as I have, you'll see
  > it is just fine. I do not have any pictures to document this, sadly --
  > and my scope is not currently set up.
  >
  > I defy you to produce factual evidence to the contrary, however!
  >
  > MiDI is not ideal for tight timing.
  > If you look at, say, laying a 4 down kick drum on a track, unless that
  > tempo you are using is an integer divisor of 31250, it's going to flop
  > around and not be in time.
  > Period.
  >
  > On 8/22/13, jammie <jammie.emma@...> wrote:
  > > you could fit a lan midi port on the cz this is attached to the pre
  > opto
  > > isolaters of the uart
  > >
  > > then you can use midi over lan
  > >
  > > but the midi protocol is still 31.25kb period thats the standard set
  > >
  > > but the problem lies with the usb and windows changing it from win98
  > >
  > > and since then midi timing has been sloppy
  > >
  > > now a parallel interface is much better and timing is much better
  > >
  > > so a opcode x64 which i still use and has xp 32 and 64bit drivers
  > >
  > > and i have never had any problems with sysex
  > >
  > > but i still use sound diver and changeit which is a great sysex sender
  > and
  > > has a section for slowing down packets
  > > ----- Original Message -----
  > > From: Lee Borrell
  > > To: CZsynth@yahoogroups.com
  > > Sent: Thursday, August 22, 2013 12:47 PM
  > > Subject: Re: [CZsynth] Speed of sysex transfer
  > >
  > >
  > >
  > > I think if you talking about USB to USB transfer - or Firewire then you
  > > may have a point ,but as soon as any interface hits a MIDI DIN plug it
  > HAS
  > > to be 31.25 Kb - this is the MIDI standard. No commercial interface with
  > DIN
  > > plugs on it is going to do better than that baud rate,or face the
  > equipment
  > > not getting the signal. In the case of pre-USB vintage machines,there is
  > no
  > > way to go faster than 31.25kB.
  > >
  > > ________________________________
  > > From: fulfil_objective <robot@...>
  > > To: CZsynth@yahoogroups.com
  > > Sent: Thursday, 22 August 2013, 7:21
  > > Subject: [CZsynth] Speed of sysex transfer
  > >
  > >
  > >
  > > Hi Steve,
  > >
  > > I think you are too focused on these vintage numbers like 31250 bps and
  > > 115200 bps. Transferring sysex by USB and MIDI are not limited to these
  > old
  > > numbers. USB enables speeds that are hundreds or thousands of times
  > faster
  > > than these numbers. In fact, greatly higher speeds are touted as one of
  > the
  > > benefits of a USB MIDI device (along with multiple streams).
  > >
  > > High speed sysex transfer is both desired and encouraged, for example,
  > in
  > > the case of sending sound data to a sampler. If you wanted to send 128
  > > megabytes of sounds to your sampler, and if you were restricted to
  > 31250
  > > bps, it would take 9.5 hours to send the sounds. USB MIDI devices
  > enable
  > > higher speeds, and that speed is encouraged.
  > >
  > > 31250 bps is the speed of an old dialup modem (actual throughput) on a
  > > good day. If you tested at 115200 bps, that is merely 3.7 times faster
  > than
  > > 31250 bps. Still very slow by today's standards.
  > >
  > > USB 2.0 has a max throughput of something like 35 MB/s. But lets be
  > > generous and say that in the real world, you can only get your USB 2.0
  > to 20
  > > MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 5,120
  > > times faster than 31250 bps.
  > >
  > > So yes, I think a capable modern computer with a good USB system can
  > send
  > > sysex out faster than the CZ can deal with it. And it's not necessarily
  > tied
  > > to CPU speed of the computer either, more like the speed of the whole
  > > computer-USB system.
  > >
  > > You will probably find it enlightening to read the "Universal Serial
  > Bus
  > > Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999,
  > which
  > > you cand download here:
  > >
  > > http://www.usb.org/developers/devclass_docs/midi10.pdf
  > >
  > > [Non-text portions of this message have been removed]
  > >
  > >
  > >
  > >
  > > No virus found in this message.
  > > Checked by AVG - www.avg.com
  > > Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date:
  > 08/21/13
  > >
  > >
  > > [Non-text portions of this message have been removed]
  > >
  > >
  >
  > No virus found in this message.
  > Checked by AVG - www.avg.com
  > Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13
  >
  > [Non-text portions of this message have been removed]
  >
  > [Non-text portions of this message have been removed]
  >
  >
  >
  >
  > No virus found in this message.
  > Checked by AVG - www.avg.com
  > Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13
  >
  >
  > [Non-text portions of this message have been removed]
  >
  >


  
  No virus found in this message.
  Checked by AVG - www.avg.com
  Version: 2013.0.3392 / Virus Database: 3211/6599 - Release Date: 08/22/13


[Non-text portions of this message have been removed]

Re: Speed of sysex transfer

2013-08-22 by steve_the_composer

Thanks for the link to the video. I am not sure that 1-2 millisecond variation in midi pulses is worth of being called a "horror." I am sure that my playing is far more than 1-2 milliseconds off.

The video is interesting and tends to confirm my suspicion that usb timing is not 100.00000% constant.

If it were available, I would be interested a comparison of more interfaces (not just the motu fastlane). I wonder, for example, how my parallel port interfaces would fare.

Steve


--- In CZsynth@yahoogroups.com, "jammie" <jammie.emma@...> wrote:
Show quoted textHide quoted text
>
> actually we have proven usb midi does drop notes out of time using an oscilloscope 
> 
> and expersleepers software and usb timing is not rock solid as midi from the st
> 
> or expert sleepers audio to midi which is just great 
> 
>  http://www.expert-sleepers.co.uk/index_files/the-horrors-of-usb-midi-timing.php
> 
> heres a video showing you 
> 
> defy away but thats just one example of many 
>

Re: [CZsynth] Speed of sysex transfer

2013-08-22 by charlie midi gfa

im really thinking i should bring up buffer
buffer is in these devices
 so chunks of data can be transfered at a time

this is likeily to have an overall effect on the message reception

if a dump  stuffs too much into the buffer before the next rt1 or circular 
buffer read
theres a good chance its going to become foul and error the  midi devices

slow the sender of the message to  31250 bits per second  please
especially when dealing with a cz


hope to stand correct
charlie




----- Original Message ----- 
Show quoted textHide quoted text
From: "Francis Cote" <francis.cote@...>
To: <CZsynth@yahoogroups.com>
Sent: Thursday, August 22, 2013 8:42 AM
Subject: Re: [CZsynth] Speed of sysex transfer


> If the machine has an issue with sysex speed, it's related to the number 
> of
> MIDI messages it can process in a certain amount of time.
> If the synth can't process more than, say, 5 messages per second (not real
> number, I don't know the real one it's just an example) and you throw 100,
> it obviously choke on it.
> If the synth makers implemented some kind of buffer able to take all the
> data coming from the MIDI port, then the synth's CPU will have all the 
> time
> it wants to process at the speed it can process and it won't choke.
>
> A chain is always going at the speed of the slowest node, that's it.
> Software that gives you the option of slowing down packets are just adding
> some delay between each packets.
>
> Francis
>
>
>
> On Thu, Aug 22, 2013 at 8:22 AM, jammie 
> <jammie.emma@...>wrote:
>
>> **
>>
>>
>> you could fit a lan midi port on the cz this is attached to the pre opto
>> isolaters of the uart
>>
>> then you can use midi over lan
>>
>> but the midi protocol is still 31.25kb period thats the standard set
>>
>> but the problem lies with the usb and windows changing it from win98
>>
>> and since then midi timing has been sloppy
>>
>> now a parallel interface is much better and timing is much better
>>
>> so a opcode x64 which i still use and has xp 32 and 64bit drivers
>>
>> and i have never had any problems with sysex
>>
>> but i still use sound diver and changeit which is a great sysex sender 
>> and
>> has a section for slowing down packets
>> ----- Original Message -----
>> From: Lee Borrell
>> To: CZsynth@yahoogroups.com
>> Sent: Thursday, August 22, 2013 12:47 PM
>> Subject: Re: [CZsynth] Speed of sysex transfer
>>
>> I think if you talking about USB to USB transfer - or Firewire then you
>> may have a point ,but as soon as any interface hits a MIDI DIN plug it 
>> HAS
>> to be 31.25 Kb - this is the MIDI standard. No commercial interface with
>> DIN plugs on it is going to do better than that baud rate,or face the
>> equipment not getting the signal. In the case of pre-USB vintage
>> machines,there is no way to go faster than 31.25kB.
>>
>> ________________________________
>> From: fulfil_objective <robot@...>
>> To: CZsynth@yahoogroups.com
>> Sent: Thursday, 22 August 2013, 7:21
>> Subject: [CZsynth] Speed of sysex transfer
>>
>> Hi Steve,
>>
>> I think you are too focused on these vintage numbers like 31250 bps and
>> 115200 bps. Transferring sysex by USB and MIDI are not limited to these 
>> old
>> numbers. USB enables speeds that are hundreds or thousands of times 
>> faster
>> than these numbers. In fact, greatly higher speeds are touted as one of 
>> the
>> benefits of a USB MIDI device (along with multiple streams).
>>
>> High speed sysex transfer is both desired and encouraged, for example, in
>> the case of sending sound data to a sampler. If you wanted to send 128
>> megabytes of sounds to your sampler, and if you were restricted to 31250
>> bps, it would take 9.5 hours to send the sounds. USB MIDI devices enable
>> higher speeds, and that speed is encouraged.
>>
>> 31250 bps is the speed of an old dialup modem (actual throughput) on a
>> good day. If you tested at 115200 bps, that is merely 3.7 times faster 
>> than
>> 31250 bps. Still very slow by today's standards.
>>
>> USB 2.0 has a max throughput of something like 35 MB/s. But lets be
>> generous and say that in the real world, you can only get your USB 2.0 to
>> 20 MB/s. That speed, 20 MB/s, works out to 160,000,000 bps, which is 
>> 5,120
>> times faster than 31250 bps.
>>
>> So yes, I think a capable modern computer with a good USB system can send
>> sysex out faster than the CZ can deal with it. And it's not necessarily
>> tied to CPU speed of the computer either, more like the speed of the 
>> whole
>> computer-USB system.
>>
>> You will probably find it enlightening to read the "Universal Serial Bus
>> Device Class Definition for MIDI Devices", Release 1.0, Nov 1, 1999, 
>> which
>> you cand download here:
>>
>> http://www.usb.org/developers/devclass_docs/midi10.pdf
>>
>> [Non-text portions of this message have been removed]
>>
>> No virus found in this message.
>> Checked by AVG - www.avg.com
>> Version: 2013.0.3392 / Virus Database: 3211/6597 - Release Date: 08/21/13
>>
>>
>> [Non-text portions of this message have been removed]
>>
>>
>>
>
>
> [Non-text portions of this message have been removed]
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
>

Re: Speed of sysex transfer

2013-08-23 by steve_the_composer

As people have pointed out, this group has been extremely active over the last day or two.  I did not see any replies about your "integer divisor" statement; so if someone replied already, please accept my apology (but only if I am repeating what someone else has said).

In the thread so far people have talked about primarily two types of timing--(1) rate of serial port data transfer and (2) tempo.

Sort of related to tempo, there's something I call resolution. Sequencers (and the midi files they create) sometimes refer to ppq--pulses per quarter (http://en.wikipedia.org/wiki/Pulses_Per_Quarter). 

I suspect that the precision with which someone lays down a track so it is 100% on the beat (or any other precise place) is more a matter of the resolution of the sequencer than the divisibility of the tempo into the rate of serial data transmission.

I could be wrong (and if so, my guess is that someone will let me know).

Steve



--- In CZsynth@yahoogroups.com, Loscha <loscha@...> wrote:
Show quoted textHide quoted text
>

> MiDI is not ideal for tight timing.
> If you look at, say, laying a 4 down kick drum on a track, unless that
> tempo you are using is an integer divisor of 31250, it's going to flop
> around and not be in time.
> Period.
>

Re: [CZsynth] Re: Speed of sysex transfer

2013-08-23 by Daniel Forró

No, no, no - sequencer resolution or tempo of music has nothing to do  
with MIDI data transfer, and high resolution can't improve MIDI  
timing, delay, latency or similar problems.

Two main problems of MIDI from the point of view of timing are:
- Serial protocol - all data which are seemingly in one moment, are in  
fact "arpeggiated" and sent one note by another one. MIDI doesn't know  
anything like a chord. Even when the chord is recorded exactly on the  
beat, in reality it is sent to MIDI arpeggiated. Everything is sent as  
one voice - monophonic - melody. And maximal throughput of MIDI is  
3125 bytes/sec, which is about 1000 messages in the second when we  
count the longest three byte messages... That's a resolution about 1  
msec. That would be about 62 notes on each MIDI channel, in theory. It  
can be more thanks to running status (and sending <Note Off> as <Note  
On Velocity Zero>), which seems to be enough good. But: not only notes  
are sent, but also MIDI controllers, pitch bend, aftertouch, MIDI  
clock and SysEx blocks... All this leave less space for notes itself  
which are the most important for the music.

Some software sequencers have solution that they analyzed recorded  
data which should be sent and change their order to be sent in the  
most efficient way without delay, with using of running status. I  
remember also that Emagic Notator sent MIDI data in order how tracks  
were in the pattern - from up to down, from track 1 to track 16. So it  
was recommended to place time critical tracks (like drum part track)  
up, and less important tracks down.

But there's another issue: we must add another delay caused at the  
side of receiving device which has to decode MIDI data, and send them  
to tone generator. Also these data are based on sequential processing...

Another delay can be caused by long MIDI cable, or chaining more MIDI  
instruments by MIDI Through connector.

- Fixed transfer speed - music has not fixed density of the  
information, quite opposite - typical for music is cumulative behavior  
with bursts in information density. But MIDI transfer speed is  
constant. When there's too much musical information on MIDI cable,  
it's not sent simultaneously, but one by one, and there's a delay.

Daniel Forro
Show quoted textHide quoted text
On 23 Aug, 2013, at 9:46 AM, steve_the_composer wrote:

> As people have pointed out, this group has been extremely active  
> over the last day or two.  I did not see any replies about your  
> "integer divisor" statement; so if someone replied already, please  
> accept my apology (but only if I am repeating what someone else has  
> said).
>
> In the thread so far people have talked about primarily two types of  
> timing--(1) rate of serial port data transfer and (2) tempo.
>
> Sort of related to tempo, there's something I call resolution.  
> Sequencers (and the midi files they create) sometimes refer to ppq-- 
> pulses per quarter (http://en.wikipedia.org/wiki/Pulses_Per_Quarter).
>
> I suspect that the precision with which someone lays down a track so  
> it is 100% on the beat (or any other precise place) is more a matter  
> of the resolution of the sequencer than the divisibility of the  
> tempo into the rate of serial data transmission.
>
> I could be wrong (and if so, my guess is that someone will let me  
> know).
>
> Steve

Re: [CZsynth] Speed of sysex transfer

2013-08-23 by Gordon JC Pearce

On Thu, Aug 22, 2013 at 10:37:00PM +1000, Loscha wrote:
> MiDI is not ideal for tight timing.
> If you look at, say, laying a 4 down kick drum on a track, unless that
> tempo you are using is an integer divisor of 31250, it's going to flop
> around and not be in time.
> Period.

That's not quite true.  For 31250 to be correct you'd need to be able to time the notes right down to individual bits, and you can't.  For a full 3-byte Note On message, you need three bytes - 24 bits, plus six start and stop bits, plus  whatever gap between bytes the transmitter inserts - so you've got roughly 1ms per message.

Now 1ms is pretty quick but in busy passages where you throw a lot of Note On messages at once you could easily end up with an appreciable gap between the first and last note on the beat.  At worst if you fired a Note On message as a full three-byte status on all 16 channels you'd end up with around 15ms of latency between the first and last note fired, which (and you can confirm this with a simple delay effect set for 50/50 wet/dry and no feedback) is enough to cause an appreciable flam.  If you bang out a lot of notes on one channel, like a complex drum part, then the problem only gets worse.

It's *still* not that bad though, unless you're doing ridiculously busy semi-semi-quaver passages at 160bpm with masses of notes on every channel.  If you're up in that territory you want to look at having multiple interfaces.  For the rest of us, with our four-part multi and monotimbral JX8Ps with slow-ass envelopes, it won't bother us in the least.

-- 
Gordonjcp MM0YEQ

Re: [CZsynth] Speed of sysex transfer

2013-08-23 by Daniel Forró

Exactly what I have written few hours ago...

On 23 Aug, 2013, at 4:09 PM, Gordon JC Pearce wrote:

>  For 31250 to be correct you'd need to be able to time the notes  
> right down to individual bits, and you can't.  For a full 3-byte  
> Note On message, you need three bytes - 24 bits, plus six start and  
> stop bits, plus  whatever gap between bytes the transmitter inserts  
> - so you've got roughly 1ms per message.
>
> Now 1ms is pretty quick but in busy passages where you throw a lot  
> of Note On messages at once you could easily end up with an  
> appreciable gap between the first and last note on the beat.  At  
> worst if you fired a Note On message as a full three-byte status on  
> all 16 channels you'd end up with around 15ms of latency between the  
> first and last note fired, which (and you can confirm this with a  
> simple delay effect set for 50/50 wet/dry and no feedback) is enough  
> to cause an appreciable flam.  If you bang out a lot of notes on one  
> channel, like a complex drum part, then the problem only gets worse.
>
> It's *still* not that bad though, unless you're doing ridiculously  
> busy semi-semi-quaver passages at 160bpm with masses of notes on  
> every channel.

Plus some controllers, pitch bend, and sometimes some short sysex in  
between... and better to filter aftertouch and not use MIDI clock...

>  If you're up in that territory you want to look at having multiple  
> interfaces.

Yes, for example I use this system:
- Opcode Studio 5lx with 240 MIDI channels (serial cable to computer)

- Yamaha UX256 with 256 MIDI channels (USB cable to computer), 96  
channels go out through MIDI, 160 channels go out through two serial  
cables - each of them transfer 80 channels (one cable controls 64  
channels in Yamaha MU128 plus another 16 channels in chained  
instrument, another one controls 32 channels in Yamaha PSR9000 Pro  
plus another 16 channels in chained instrument)

- MOTU MIDI Express 128 with 128 MIDI channels (USB cable to computer)

- Roland Sound Canvas SC8820 - 32 channels for it's own control + 16  
channels for chained instrument (USB cable to computer)

As additional I have connected three Yamaha MIDI Patchbays MJC8, used  
just as simple thru-boxes.

> For the rest of us, with our four-part multi and monotimbral JX8Ps  
> with slow-ass envelopes, it won't bother us in the least.
>
> -- 
> Gordonjcp MM0YEQ

Nice times when I have started in 1985 with DX7, CZ101 and Drumtraks  
only... Now little bit more instruments :-)

Daniel Forro

Re: Speed of sysex transfer

2013-08-23 by steve_the_composer

Excellent explanation covering both theory and practical reality.
Steve

--- In CZsynth@yahoogroups.com, Gordon JC Pearce <gordon@...> wrote:
Show quoted textHide quoted text
>
> On Thu, Aug 22, 2013 at 10:37:00PM +1000, Loscha wrote:
> > MiDI is not ideal for tight timing.
> > If you look at, say, laying a 4 down kick drum on a track, unless that
> > tempo you are using is an integer divisor of 31250, it's going to flop
> > around and not be in time.
> > Period.
> 
> That's not quite true.  For 31250 to be correct you'd need to be able to time the notes right down to individual bits, and you can't.  For a full 3-byte Note On message, you need three bytes - 24 bits, plus six start and stop bits, plus  whatever gap between bytes the transmitter inserts - so you've got roughly 1ms per message.
> 
> Now 1ms is pretty quick but in busy passages where you throw a lot of Note On messages at once you could easily end up with an appreciable gap between the first and last note on the beat.  At worst if you fired a Note On message as a full three-byte status on all 16 channels you'd end up with around 15ms of latency between the first and last note fired, which (and you can confirm this with a simple delay effect set for 50/50 wet/dry and no feedback) is enough to cause an appreciable flam.  If you bang out a lot of notes on one channel, like a complex drum part, then the problem only gets worse.
> 
> It's *still* not that bad though, unless you're doing ridiculously busy semi-semi-quaver passages at 160bpm with masses of notes on every channel.  If you're up in that territory you want to look at having multiple interfaces.  For the rest of us, with our four-part multi and monotimbral JX8Ps with slow-ass envelopes, it won't bother us in the least.
> 
> -- 
> Gordonjcp MM0YEQ
>

Re: Speed of sysex transfer

2013-08-23 by steve_the_composer

Now imagine doing a live performance with a sequencer playing 1 sound module having notes 10 notes on each of 16 midi channels (all on the down beat!) AND doing a patch dump of 127 patches of 1605 bytes each on top of controllers and pitch bend. 

Its a good thing Casio CZ and VZ users don't have to worry about much data (at least not with their Casios).

Steve


--- In CZsynth@yahoogroups.com, Daniel Forró <dan.for@...> wrote:

[snip]

> Plus some controllers, pitch bend, and sometimes some short sysex   
> in between... and better to filter aftertouch and not use MIDI
> clock...
 
[snip]

Re: Speed of sysex transfer

2013-08-23 by k9k9dog

remember people 'printing to tape' with ADAT to run off 
their compositions and tighten everything up? :)

--- In CZsynth@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
Show quoted textHide quoted text
>
> Excellent explanation covering both theory and practical reality.
> Steve
> 
> --- In CZsynth@yahoogroups.com, Gordon JC Pearce <gordon@> wrote:
> >
> > On Thu, Aug 22, 2013 at 10:37:00PM +1000, Loscha wrote:
> > > MiDI is not ideal for tight timing.
> > > If you look at, say, laying a 4 down kick drum on a track, unless that
> > > tempo you are using is an integer divisor of 31250, it's going to flop
> > > around and not be in time.
> > > Period.
> > 
> > That's not quite true.  For 31250 to be correct you'd need to be able to time the notes right down to individual bits, and you can't.  For a full 3-byte Note On message, you need three bytes - 24 bits, plus six start and stop bits, plus  whatever gap between bytes the transmitter inserts - so you've got roughly 1ms per message.
> > 
> > Now 1ms is pretty quick but in busy passages where you throw a lot of Note On messages at once you could easily end up with an appreciable gap between the first and last note on the beat.  At worst if you fired a Note On message as a full three-byte status on all 16 channels you'd end up with around 15ms of latency between the first and last note fired, which (and you can confirm this with a simple delay effect set for 50/50 wet/dry and no feedback) is enough to cause an appreciable flam.  If you bang out a lot of notes on one channel, like a complex drum part, then the problem only gets worse.
> > 
> > It's *still* not that bad though, unless you're doing ridiculously busy semi-semi-quaver passages at 160bpm with masses of notes on every channel.  If you're up in that territory you want to look at having multiple interfaces.  For the rest of us, with our four-part multi and monotimbral JX8Ps with slow-ass envelopes, it won't bother us in the least.
> > 
> > -- 
> > Gordonjcp MM0YEQ
> >
>

Re: Speed of sysex transfer

2013-08-24 by steve_the_composer

I never got into that.  However, I did get into visually examining the midi event list and manually tweaking the start (and sometimes the duration) of notes, correcting or deleting accidental notes, etc. (Batch quantizing was never good enough!)

Steve

--- In CZsynth@yahoogroups.com, "k9k9dog" <domgoold@...> wrote:
Show quoted textHide quoted text
>
> remember people 'printing to tape' with ADAT to run off 
> their compositions and tighten everything up? :)
>

Re: [CZsynth] Speed of sysex transfer

2013-08-25 by Summa

Hi,

I haven't watched all the communication about that topic yet, been a 
bit busy lately, so the approval of new members messages tend to be a 
bit slower than usual...

On 22 Aug 2013 at 6:21, fulfil_objective wrote:

> I think you are too focused on these vintage numbers like 31250 bps and
> 115200 bps. Transferring sysex by USB and MIDI are not limited to these
> old numbers. 

It's a "clocked" interface with a _fixed_speed_, that way MIDI 
communication can't be faster than this, even so some manufacturers 
establised a faster MIDI communication between their own devices and 
MIDI over USB and Ethernet might be faster too. Still older synths 
can't keep up in case computers using the full midi bandwith 
especially without pausing between the blocks.

Other than that, some interfaces tend to have problems with sysex, 
especially the noname USB class compliant ones. Here's a link to a 
MIDI Interface Sysex black-/whitelist (link at the top)...

http://www.midibox.org/dokuwiki/doku.php?id=midi_interface_blacklist

Sysex wise I tend to use my Roland (Edirol/Cakewalk) UM3EX/UM2G 
(Vista/Windows7) MIDI Interfaces, 4x Unitor/AMT8 (98/XP) and a 
MIDIsport 4x4 (98/XP)...
Other than that I avoid class compliant interfaces especially within 
Windows...

I hope this helps!
                  Summa

-- 

CZ/VZ 		mailing list	: http://groups.yahoo.com/group/CZsynth
FMHeaven	mailing list	: http://groups.yahoo.com/group/fmheaven/
FS1R		mailing list	: http://groups.yahoo.com/group/fs1r/	
Vokator		mailing list	: http://groups.yahoo.com/group/vokator
FM-Synthesis	mailing list	: 
http://groups.yahoo.com/group/fm-synthesis/

http://www.summasounds.de/

Re: Speed of sysex transfer

2013-08-25 by steve_the_composer

Thanks for chiming in, Summa.  I was initially pleased to see the white list/black list of midi interfaces, but I was shocked to see it lists problems my E-Mu Xmidi 2x2 allegedly has with sysex. 

I would gladly run tests on mine, but I didn't see any tests listed. It seems to be a list that anyone can add to with no consistent standards. (There is a link of the list for "more details" on my interface, but that doesn't contain any details.)

As for older synths not being able to keep up with full midi bandwidth, considering I tested the CZ-500 using Win7 64-bit and an interface on the blacklist (as far as sysex goes), I don't know what to say. Hmmmmmmmmm. (Steve scratches his head and wonders aloud what could explain the discrepancies.)

Maybe its the luck of the draw, that my particular CZ-5000 that can handle sysex transfers without delays and my particular blacklisted midi interface that works with sysex. It could just be random variation. Hmmmmmmm. Could be fluctuation in household power, I suppose.

There are other possibilities: when I first got my 64-bit Win7 laptop, I learned quickly with midi gear not to let Windows find device drivers, but to cancel the search for drivers and to use manufacturer's drivers. Some automatically discovered drivers just did not work!! Unfortunately, with the blacklist/whitelist we have no idea what drivers were used. My Xmidi 2x2 uses the manufacturer's latest driver. That might explain why mine works with sysex.

As for the CZ-5000, there is also another possibility. Back in the late '80s I zapped my CZ with static (dry winter condition, and static prone carpet). I sent my Casio to be repaired at the place Casio USA used and they tuned it up to factory specs.  That was over 20 years ago, but perhaps they did such a good job that my circuits still work like new. That might explain why mine works with midi-ox without delays. 

So perhaps its not that older gear can't handle modern computer speeds, but that over time, components and circuit boards deteriorate, timings get off, memory wears out, etc. That might explain what's going on here. 

If I had more time, I'd write an arduino program to send out midi data at different rates to try to measure the max and min serial speeds gear can handle. Maybe over time, with deteriorating circuits, some gear cannot keep pace with 31250 bps.  Maybe the leds in optoisolators dim over time. I guess there are a lot of variables that could explain differences. So maybe it would be nice to have a way to measure something like this.

Nevertheless, I still think that saying older midi gear cannot handle the speeds of today's modern computers is way too broad of a statement to be accurate and even useful. Maybe some specific gear can and some can't. 

Anyhow, this has been an interesting thread. Lots of interesting factors to consider together with workarounds, paths to pursue, etc.

By the way, does anyone know of any published standards for assessing sysex capability of midi interfaces? 

Steve

Steve





--- In CZsynth@yahoogroups.com, "Summa" <flotorian@...> wrote:

[snip]

> Still older synths 
> can't keep up in case computers using the full midi bandwith 
> especially without pausing between the blocks.
> 
> Other than that, some interfaces tend to have problems with sysex, 
> especially the noname USB class compliant ones. Here's a link to a 
> MIDI Interface Sysex black-/whitelist (link at the top)...

[snip]

Re: Speed of sysex transfer

2013-08-25 by steve_the_composer

Update: I went over to the MIDIBox chat site.  It seems that the blacklist/whitelist is just from MIDIBox people. Also, it seems to reflect experiences with really long sysex commands. The size of the CZ dumps is really small compared to dumps from 1990s gear, so that blacklist/whitelist might not be useful for CZers.

Still, I wouldn't rely on a $3.99 - $9.99 usb-midi interface cable.  You might get one that works, but I have seen a lot of complaints on the internet. (You pay your money and you take your chances.)

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.