Author |
Topic: sysex and voiceworks (Read 2052 times) |
|
oldmidiman
New Member
MIDI-OX Rules!
Posts: 1
|
 |
sysex and voiceworks
« on: Dec 29th, 2003, 7:05pm » |
 Quote  Modify
|
I have been trying to upgrade my TC Helicon voiceworks softrware. I am using my laptop with roland um-1 interface cable. When I try to send file I see activity on the output midi port (sys) but nothing happens to the voiceworks unit. I followed the directions from tc helicon about powering up the unit with the song mode and arrow up key depressed and scrolling until download dsp code appears, I then tell midiox to send sysx file. It appears that something is going on but the voiceworks unit doesn't seem to receive anything. Any help would be greatly appreciated. This my first with midiox, seems like a great program, I just need to figure what all I can do with it.
Thanks
|
|
 IP Logged |
|
|
|
ray_costello
New Member
MIDI-OX Rules!
Posts: 6
|
|
Re: sysex and voiceworks
« Reply #1 on: Nov 22nd, 2004, 5:54pm » |
Quote Modify
|
I have exactly the same problem.
The only difference is that I am using a Desktop PC with Yamaha USB/Midi box.
I know I have connection to the Voiceworks because I can set the input port to PC keyvoard or my Roland RD600 and the midi light flashes on the Voiceworks front Panel.
As 'oldmidiman' says, Midiox seems to be sending the Sysex file but nothing happens on the Voiceworks.
Any ideas would be much appreciated.
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
 
Gender: 
Posts: 2027
|
|
Re: sysex and voiceworks
« Reply #2 on: Nov 22nd, 2004, 6:03pm » |
Quote Modify
|
Several users report trouble with Yamaha MIDI USB devices sending and receiving SysEx, and I had so much trouble with a UX256, I stoped using it. Check for updated drivers. To test the Yamaha MIDI device, set up a hardware loop back by running a cable from MIDI Out N to MIDI In N, and then dump from one MIDI-OX instance to another. Then compare the dumps: if they're not identical there is a problem.
|
|
IP Logged |
--Jamie
Music is its own reward.
|
|
|
ray_costello
New Member
MIDI-OX Rules!
Posts: 6
|
|
Re: sysex and voiceworks
« Reply #3 on: Nov 23rd, 2004, 4:03pm » |
Quote Modify
|
Hi Jamie, 
Many thanks for the advice.
I have received a mail from Voiceworks support today and they have also indicated the Yamaha USB/Midi may well be the problem.
I will perform the tests that you suggest, though I feel a new interface is required.
BTW - Midi-OX is an excellent product and so easy to use.
I will post an update when I have more information.
Thanks again for the help.
Ray
|
|
IP Logged |
|
|
|
ray_costello
New Member
MIDI-OX Rules!
Posts: 6
|
|
Re: sysex and voiceworks
« Reply #4 on: Nov 23rd, 2004, 5:24pm » |
Quote Modify
|
Hi Jamie,
An update as promised.
It looks like it's thumbs down for the Yamaha UX256.
I installed a loopback on Port 1 IN to Port 1 Out. I then loaded the SYSEX file and could see it going to the OUT on the Midi Port Activity (SX red light flashing) nothing on the IN (SX red light no activity)
With the result above I did not dump across two instances as it looks like the Yamaha is not passing SX data anyway.
I think this is conclusive, what do you think?
Thanks again
Ray
|
|
IP Logged |
|
|
|
Jamie OConnell
Administrator
Gender:
Posts: 2027
|
|
Re: sysex and voiceworks
« Reply #5 on: Nov 28th, 2004, 1:41pm » |
Quote Modify
|
You should really do the 2 instance dump, as SOME data definitely does go across. It's just that I've seen the UX256 drop bytes. I was hoping they had improved the driver since I last checked.
|
| « Last Edit: Nov 28th, 2004, 1:42pm by Jamie OConnell » |
IP Logged |
--Jamie
Music is its own reward.
|
|
|
|
User Forum ::
Powered by YaBB
Home 
Help 
Search 
Members 
Login 
Register
Reply
Notify of replies
Send Topic
Print