Patches and discussion for Ensoniq VFX family group photo

Yahoo Groups archive

Patches and discussion for Ensoniq VFX family

Index last updated: 2026-04-29 00:03 UTC

Thread

Re: [Ensoniq-VFX-SD] Beware cheap chinese USB MID I cables on ebay...

Re: [Ensoniq-VFX-SD] Beware cheap chinese USB MID I cables on ebay...

2008-06-21 by Claus

Hi Steve :)


I´ve been using a Winman 1x1 (ISA back then!) with no problems. Midiman BiPort 2x4s (COM port) on Win98se with NO problems. For the last year or so, a MidiSport 8x8 (USB on 98se(!!) is running. No problem either. I've also tried the MIDI I/O on the Evolution UC33e controller and the MIDI I/O on a Terratec Phase 22. All working.


So I'm really wondering what Your problem might be. Maybe I'm wrong, but to my knowledge, VFXs don't use running status. Roland does, as one of the only ones getting to my mind from back then.


To me it really sounds like a 'bad' USB port or something along that line. Which might include bad drivers. The BiPort 2x4s as an example runs way better with v1.02 than the newest avaiable drivers (1.05 I think, allthough discontinued). Have You tried that? It MIGHT help. Else I really would suggest the 8x8s (or similar), since it: Brings LOTS of I/O, works as a MIDI-patchbay. AND can be used without the computer :)) (OK, pricey, but really nice!)


One last (SIMPLE!) suggestion, as I had this problem once: Have You tried spraying the MIDI I/Os on the VFX with elctronic-cleaner? That MIGHT help too. You're on XP?


Regards,

- Claus, DK





----Original Message-----

From: steve@...

Sent: Friday, June 20, 2008 7:47 PM -07:00

To: Ensoniq-VFX-SD@yahoogroups.com

Subject: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables on ebay...


This is a heads up to all of you. If you know of a better forum I

should be posting this in, let me know.


Having recently put some softsynth software on my mac laptop, I wanted

a usb - midi interface that I could just put in my laptop bag and have

with me. There are a bunch of cheap, 1x1 usb midi adapters available

on ebay for around $20 after shipping. I could not find much

information on whether these worked well or not, using google. So I

thought I'd try one.


I hooked it up to my VFX-SD and things were NOT working well. I tried

it with my Macbook laptop and with my windows XP desktop machine. In

both cases, the symptoms were the same. A single note would play

fine, but chords would not, no matter how much time between pressing

each note. And there were stuck notes, etc.


So the short story is: you may get even less than you pay for if you

try to use one of these with a VFX.


I looked at the output with Midi-Ox, and I think I may have a clue to

the problem. The rest of this message is pretty much pure speculation.


It looks like this device does not handle running status correctly.

And at least my VFX-SD seems to send running status whenever it can.


Running status is a midi feature that's been around from the

begining of midi. Status bytes have the high bit set (decimal

value is greater than 127), other bytes don't. For example, a

note on message looks like A0 45 40 (in hexadecimal). A0 is a

status byte that says "this message is a NOTE ON message for

midi channel 1." 45 is the note number, and 40 is the

velocity. If more note on messages need to be sent for

channel 1, the sender is allowed to send just more note

number, velocity byte pairs, without sending the initial byte,

so: A0 45 40 47 42 would be two note on messages on midi

channel 1, one for note 45 velocity of 40, one for note 47

velocity of 42.


This midi interface doesn't seem to react to anything unless there's a

status byte. So, Note-On, Note-off, Note-On, Note-off works, but

Note-On, Note-On, Note-off, Note-off doesn't.


I've heard that these interfaces are rip-offs of the M-Audio midisport

uno; I found this info in the linux alpha drivers section:


- usb-audio: work around broken M-Audio MidiSport Uno firmware

The firmware of the M-Audio USB Uno MIDI Interface has, at least in

hardware revision 1.25, a bug that garbles its USB output. When it

receives a Note On MIDI message that uses running status, the resulting

USB MIDI packet has a wrong CIN (4 instead of 9) and a wrong length

(2 bytes, the status byte is still missing).

This patch adds a workaround to track the CINs and the MIDI messages of

received USB MIDI packets to detect whether a packet with CIN 4 is a

correct SysEx packet or a buggy running status packet.


That suggests that this is probably a bug-for-bug-compatible clone,

and that a workaround is proably already in the other platforms'

USB-MIDI drivers, if only they could be convinced to see this device

as a midisport uno. :-(


Anyway, buyer beware!


--> Steve


--

Steve Wahl steve@...


One day, the light bulb in the fridge burnt out, and I thought to myself,

"At least now I know it's off when the door's closed... Or do I?"

Re: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables on ebay...

2008-06-21 by Steve Wahl

On Sat, Jun 21, 2008 at 03:11:23AM +0000, Claus wrote:
> Hi Steve :)
> 
> I\ufffdve been using a Winman 1x1 (ISA back then!) with no
> problems. Midiman BiPort 2x4s (COM port) on Win98se with NO
> problems. For the last year or so, a MidiSport 8x8 (USB on 98se(!!)
> is running. No problem either. I've also tried the MIDI I/O on the
> Evolution UC33e controller and the MIDI I/O on a Terratec Phase
> 22. All working.

I've used a few working interfaces over the years, too.  You mention
all brand name stuff, many that shipped with their own drivers.

I should be clear: I'm not talking about brand name midi interfaces
that just happen to be made in China.  They're likely as good as the
name on them and the company standing behind them.

I'm talking about a no-name, generic USB-MIDI cable from ebay, that in
fact I realize I'm only assuming was made in China.  

Speaking as a driver writer (but, so far, not a MIDI driver writer),
sometimes hardware has bugs in it that must be worked around.  My
theory is that this cheap, no-name cable "stole" the circuitry /
silicon from a slightly buggy version of the UNO, and changed the USB
ID for the device which means the driver that works OK with a real UNO
can't recognize that it has to compensate for a hardware bug.

(If you don't think they can easily steal things like circuit board
artwork and silicon, read up on counterfiet Cisco hardware someday!)

> So I'm really wondering what Your problem might be. Maybe I'm wrong,
> but to my knowledge, VFXs don't use running status. Roland does, as
> one of the only ones getting to my mind from back then.

If it's true that the VFX doesn't use running status, that throws a
big wrench into my theory.  I looked at a different interface with my
VFX and Midi-Ox, and I don't see running status.  BUT I have a feeling
that the windows midi driver API has the driver hide received running
status from the applications, so midi-ox wouldn't know if running
status came in or not.

If I get time, I'll hook up the oscilloscope and find out for certain!
:-)

(You're not by any chance confusing running status with active
sensing, are you?  I know nearly nobody used active sensing.)

> To me it really sounds like a 'bad' USB port or something along that
> line. Which might include bad drivers. The BiPort 2x4s as an example
> runs way better with v1.02 than the newest avaiable drivers (1.05 I
> think, allthough discontinued). Have You tried that? It MIGHT
> help.

This is one of those devices that doesn't come with drivers, instead
uses the "class" drivers that ship with your OS.  So far I've used Mac
OS X Leopard, and Windows XP (SP2 I think, but I haven't paid too much
attention to detail there); both machines using USB ports that have no
problem with other things like thumb drives.  I also used a MidiMan
Oxygen 8 on the mac a little while back.  I can't say for sure it was
the same port, because I have two USB ports.

> Else I really would suggest the 8x8s (or similar), since it:
> Brings LOTS of I/O, works as a MIDI-patchbay. AND can be used
> without the computer :)) (OK, pricey, but really nice!)

I have quite a few examples of midi interfaces around here; I think I
even still have one to connect to my amiga around somewhere!  While
I've had one in particular be a bit flakey (MOTU PC midi flyer,
parallel port connection, I think it was interrupt conflicts or
something that caused flakeyness), all the others I've tried have
basically worked.  Never had a problem like this before.

The object of this purchase was a simple, inexpensive midi interface I
can toss in the laptop bag.  $20 seemed like a "what have I got to
lose" price -- the answer was I've got $20 to lose, of course.  $40 +
tax / shipping / etc. for a brand name interface seemed a little high
at the time.  Not now, though!

> One last (SIMPLE!) suggestion, as I had this problem once: Have You
> tried spraying the MIDI I/Os on the VFX with elctronic-cleaner? That
> MIGHT help too. 

I use the VFX-SD midi out all the time to control a Roland JV-1080.
And I hooked it up to the midi in on my Emu-1212 just to check for
certain (same win XP system I tested the USB interface on).  NO
dropped notes with that.  So, I think the electrical connection is
fine.

> You're on XP?

As well as OS X Leopard and various Linux systems; haven't done MIDI
on any of them for a while.  I mostly use MIDI only for live playing
and VFX-SD sequencing; I just record audio when I use a computer.

But, anyway, thanks for your input on this, Claus!  

--> Steve

-- 
Steve Wahl    steve@...

"'No Child Left Behind' -- Think about those words for a second. How
else do you not leave a child behind unless you hold everyone else
back with him?"
   -- Someone named "Geoffrey" on Slashdot

AW: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables onebay...

2008-06-21 by Hans Artmann

Just to add to the device list:
I'm using an Emagic AMT-8 and a Tascam U428 without any problems, both connected via USB.
It's a pity that Emagic has been aquired by Apple - same sad story like with Ensoniq and Emu. Good products
are been taken out of the competition while there's nothing better to offer.
Hans
Show quoted textHide quoted text
-----Ursprüngliche Nachricht-----
Von: Ensoniq-VFX-SD@yahoogroups.com [mailto:Ensoniq-VFX-SD@yahoogroups.com] Im Auftrag von Steve Wahl
Gesendet: Samstag, 21. Juni 2008 07:28
An: Ensoniq-VFX-SD@yahoogroups.com
Betreff: Re: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables onebay...

On Sat, Jun 21, 2008 at 03:11:23AM +0000, Claus wrote:
> Hi Steve :)
>
> I´ve been using a Winman 1x1 (ISA back then!) with no
> problems. Midiman BiPort 2x4s (COM port) on Win98se with NO
> problems. For the last year or so, a MidiSport 8x8 (USB on 98se(!!)
> is running. No problem either. I've also tried the MIDI I/O on the
> Evolution UC33e controller and the MIDI I/O on a Terratec Phase
> 22. All working.

I've used a few working interfaces over the years, too. You mention
all brand name stuff, many that shipped with their own drivers.

I should be clear: I'm not talking about brand name midi interfaces
that just happen to be made in China. They're likely as good as the
name on them and the company standing behind them.

I'm talking about a no-name, generic USB-MIDI cable from ebay, that in
fact I realize I'm only assuming was made in China.

Speaking as a driver writer (but, so far, not a MIDI driver writer),
sometimes hardware has bugs in it that must be worked around. My
theory is that this cheap, no-name cable "stole" the circuitry /
silicon from a slightly buggy version of the UNO, and changed the USB
ID for the device which means the driver that works OK with a real UNO
can't recognize that it has to compensate for a hardware bug.

(If you don't think they can easily steal things like circuit board
artwork and silicon, read up on counterfiet Cisco hardware someday!)

> So I'm really wondering what Your problem might be. Maybe I'm wrong,
> but to my knowledge, VFXs don't use running status. Roland does, as
> one of the only ones getting to my mind from back then.

If it's true that the VFX doesn't use running status, that throws a
big wrench into my theory. I looked at a different interface with my
VFX and Midi-Ox, and I don't see running status. BUT I have a feeling
that the windows midi driver API has the driver hide received running
status from the applications, so midi-ox wouldn't know if running
status came in or not.

If I get time, I'll hook up the oscilloscope and find out for certain!
:-)

(You're not by any chance confusing running status with active
sensing, are you? I know nearly nobody used active sensing.)

> To me it really sounds like a 'bad' USB port or something along that
> line. Which might include bad drivers. The BiPort 2x4s as an example
> runs way better with v1.02 than the newest avaiable drivers (1.05 I
> think, allthough discontinued). Have You tried that? It MIGHT
> help.

This is one of those devices that doesn't come with drivers, instead
uses the "class" drivers that ship with your OS. So far I've used Mac
OS X Leopard, and Windows XP (SP2 I think, but I haven't paid too much
attention to detail there); both machines using USB ports that have no
problem with other things like thumb drives. I also used a MidiMan
Oxygen 8 on the mac a little while back. I can't say for sure it was
the same port, because I have two USB ports.

> Else I really would suggest the 8x8s (or similar), since it:
> Brings LOTS of I/O, works as a MIDI-patchbay. AND can be used
> without the computer :)) (OK, pricey, but really nice!)

I have quite a few examples of midi interfaces around here; I think I
even still have one to connect to my amiga around somewhere! While
I've had one in particular be a bit flakey (MOTU PC midi flyer,
parallel port connection, I think it was interrupt conflicts or
something that caused flakeyness), all the others I've tried have
basically worked. Never had a problem like this before.

The object of this purchase was a simple, inexpensive midi interface I
can toss in the laptop bag. $20 seemed like a "what have I got to
lose" price -- the answer was I've got $20 to lose, of course. $40 +
tax / shipping / etc. for a brand name interface seemed a little high
at the time. Not now, though!

> One last (SIMPLE!) suggestion, as I had this problem once: Have You
> tried spraying the MIDI I/Os on the VFX with elctronic-cleaner? That
> MIGHT help too.

I use the VFX-SD midi out all the time to control a Roland JV-1080.
And I hooked it up to the midi in on my Emu-1212 just to check for
certain (same win XP system I tested the USB interface on). NO
dropped notes with that. So, I think the electrical connection is
fine.

> You're on XP?

As well as OS X Leopard and various Linux systems; haven't done MIDI
on any of them for a while. I mostly use MIDI only for live playing
and VFX-SD sequencing; I just record audio when I use a computer.

But, anyway, thanks for your input on this, Claus!

--> Steve

--
Steve Wahl steve@pro-ns.net

"'No Child Left Behind' -- Think about those words for a second. How
else do you not leave a child behind unless you hold everyone else
back with him?"
-- Someone named "Geoffrey" on Slashdot

Re: AW: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables onebay...

2008-06-21 by Mark Wiens

I'm curious, has anyone tried the Emu 1x1 USB-MIDI? It has the least 
expensive list price of any of that I've seen ($29.95)... 
notwithstanding those EBay Chinese knock-offs.

- Mark

Hans Artmann wrote:
Show quoted textHide quoted text
> Just to add to the device list:
> I'm using an Emagic AMT-8 and a Tascam U428 without any problems, both 
> connected via USB.
> It's a pity that Emagic has been aquired by Apple - same sad story like 
> with Ensoniq and Emu. Good products
> are been taken out of the competition while there's nothing better to offer.
>  
> Hans
>  
>  
> 
>     -----Ursprüngliche Nachricht-----
>     Von: Ensoniq-VFX-SD@yahoogroups.com
>     [mailto:Ensoniq-VFX-SD@yahoogroups.com] Im Auftrag von Steve Wahl
>     Gesendet: Samstag, 21. Juni 2008 07:28
>     An: Ensoniq-VFX-SD@yahoogroups.com
>     Betreff: Re: [Ensoniq-VFX-SD] Beware cheap chinese USB MIDI cables
>     onebay...
> 
>     On Sat, Jun 21, 2008 at 03:11:23AM +0000, Claus wrote:
>      > Hi Steve :)
>      >
>      > I´ve been using a Winman 1x1 (ISA back then!) with no
>      > problems. Midiman BiPort 2x4s (COM port) on Win98se with NO
>      > problems. For the last year or so, a MidiSport 8x8 (USB on 98se(!!)
>      > is running. No problem either. I've also tried the MIDI I/O on the
>      > Evolution UC33e controller and the MIDI I/O on a Terratec Phase
>      > 22. All working.
> 
>     I've used a few working interfaces over the years, too. You mention
>     all brand name stuff, many that shipped with their own drivers.
> 
>     I should be clear: I'm not talking about brand name midi interfaces
>     that just happen to be made in China. They're likely as good as the
>     name on them and the company standing behind them.
> 
>     I'm talking about a no-name, generic USB-MIDI cable from ebay, that in
>     fact I realize I'm only assuming was made in China.
> 
>     Speaking as a driver writer (but, so far, not a MIDI driver writer),
>     sometimes hardware has bugs in it that must be worked around. My
>     theory is that this cheap, no-name cable "stole" the circuitry /
>     silicon from a slightly buggy version of the UNO, and changed the USB
>     ID for the device which means the driver that works OK with a real UNO
>     can't recognize that it has to compensate for a hardware bug.
> 
>     (If you don't think they can easily steal things like circuit board
>     artwork and silicon, read up on counterfiet Cisco hardware someday!)
> 
>      > So I'm really wondering what Your problem might be. Maybe I'm wrong,
>      > but to my knowledge, VFXs don't use running status. Roland does, as
>      > one of the only ones getting to my mind from back then.
> 
>     If it's true that the VFX doesn't use running status, that throws a
>     big wrench into my theory. I looked at a different interface with my
>     VFX and Midi-Ox, and I don't see running status. BUT I have a feeling
>     that the windows midi driver API has the driver hide received running
>     status from the applications, so midi-ox wouldn't know if running
>     status came in or not.
> 
>     If I get time, I'll hook up the oscilloscope and find out for certain!
>     :-)
> 
>     (You're not by any chance confusing running status with active
>     sensing, are you? I know nearly nobody used active sensing.)
> 
>      > To me it really sounds like a 'bad' USB port or something along that
>      > line. Which might include bad drivers. The BiPort 2x4s as an example
>      > runs way better with v1.02 than the newest avaiable drivers (1.05 I
>      > think, allthough discontinued). Have You tried that? It MIGHT
>      > help.
> 
>     This is one of those devices that doesn't come with drivers, instead
>     uses the "class" drivers that ship with your OS. So far I've used Mac
>     OS X Leopard, and Windows XP (SP2 I think, but I haven't paid too much
>     attention to detail there); both machines using USB ports that have no
>     problem with other things like thumb drives. I also used a MidiMan
>     Oxygen 8 on the mac a little while back. I can't say for sure it was
>     the same port, because I have two USB ports.
> 
>      > Else I really would suggest the 8x8s (or similar), since it:
>      > Brings LOTS of I/O, works as a MIDI-patchbay. AND can be used
>      > without the computer :)) (OK, pricey, but really nice!)
> 
>     I have quite a few examples of midi interfaces around here; I think I
>     even still have one to connect to my amiga around somewhere! While
>     I've had one in particular be a bit flakey (MOTU PC midi flyer,
>     parallel port connection, I think it was interrupt conflicts or
>     something that caused flakeyness), all the others I've tried have
>     basically worked. Never had a problem like this before.
> 
>     The object of this purchase was a simple, inexpensive midi interface I
>     can toss in the laptop bag. $20 seemed like a "what have I got to
>     lose" price -- the answer was I've got $20 to lose, of course. $40 +
>     tax / shipping / etc. for a brand name interface seemed a little high
>     at the time. Not now, though!
> 
>      > One last (SIMPLE!) suggestion, as I had this problem once: Have You
>      > tried spraying the MIDI I/Os on the VFX with elctronic-cleaner? That
>      > MIGHT help too.
> 
>     I use the VFX-SD midi out all the time to control a Roland JV-1080.
>     And I hooked it up to the midi in on my Emu-1212 just to check for
>     certain (same win XP system I tested the USB interface on). NO
>     dropped notes with that. So, I think the electrical connection is
>     fine.
> 
>      > You're on XP?
> 
>     As well as OS X Leopard and various Linux systems; haven't done MIDI
>     on any of them for a while. I mostly use MIDI only for live playing
>     and VFX-SD sequencing; I just record audio when I use a computer.
> 
>     But, anyway, thanks for your input on this, Claus!
> 
>     --> Steve
> 
>     -- 
>     Steve Wahl steve@... <mailto:steve%40pro-ns.net>
> 
>     "'No Child Left Behind' -- Think about those words for a second. How
>     else do you not leave a child behind unless you hold everyone else
>     back with him?"
>     -- Someone named "Geoffrey" on Slashdot

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.