I don't think, that the guys will improve anything. Be happy for every workaround you know... and use it and be happy! There are still a lot of bugs in the vetta software, which never will be fixed and even the last Line6Edit update won't fix all functional bugs (for example mic settings for the Flextone).
On the other side the MIDI protocol was created in the 80's just to transfer tiny messages like "which key" was pressed "how fast" and "how long". That's all and this will work with your MIDI interface. But in our case, Line6Edit and the Firmware update transfers a big amount of data, which - maybe - is not matching the standard MIDI protocol. Be happy that it works fine with M-Audio Uno. All guys who are able to afford a Vetta, should have the bucks for this blue box.
Currently Being ModeratedAug 4, 2009 12:23 AM (in response to candreasffm)Re: Line 6 Vetta II and Midi
I was able to afford a ROM I/O device so money is not the problem really. It's just a pity line6 doesn't officially state what devices to use (in the pilot's handbook). I would have saved some money
This information is correct. The M-Audio series devices seem to be the most robust of the MIDI-USB devices, which is why Line 6 recommends them. It is also a good idea to make sure you are plugging directly into the motherboard rather than the front of the computer or a hub. See the following links for more MIDI and USB information:
MIDI: Functionality, Control, and Connectivity with Line 6 devices
USB Connectivity with Line 6 Devices
Line 6 Edit FAQ
Line 6 Edit: Transferring Patches (Downloaded or Created)
Please be sure to award Helpful and/or Correct points to community members who respond with helpful or correct answers!
The whole MIDI/USB thing is about buffering.
The MIDI protocol is designed to play an instrument in real time with correct timing for the MIDI sequence. So, it won't deal with buffering where the data flow stops and starts as a memory buffer fills.
Most (nearly all) MIDI/USB interfaces mess up the flow of MIDI data by allowing the USB buffering to start and stop the flow of data. If there is only a small amount of data involved then the buffering won't come into play. Like when Monkey just checks what device is connected.
Only a handful of MIDI/USB interfaces will work correctly without interrupting the data flow with buffering. The M-Audio UNO is one of the least expensive of the proper MIDI/USB interfaces.
Vetta users before you have experienced the same problems and have remedied the problem by getting a reliable MIDI/USB interface.
Of course, the manufacturer of the interface is not going to want to admit any limitation of their hardware, but ask them for a technical breakdown of how MIDI data is buffered compared to a native MIDI interface (one that doesn't route via USB) like what comes out of a MIDI sound module or keyboard.
Anyway, you can either persist with using the interface you have and not transfer data to and from the Vetta or you could get a reliable MIDI/USB interface and be up and running in no time at all.
Another suggestion is to get yourself a sound card for your computer that comes with a MIDI interface. That way you never have to worry about MIDI/USB. I have kept my trusty Sound Blaster Live Drive because it has MIDI ports on the front panel, I have never had any problems with MIDI, not ever.
Currently Being ModeratedAug 4, 2009 12:19 AM (in response to Crusty_Old_Rocker)Re: Line 6 Vetta II and Midi
Thank you for explaining! I have never worked with midi so I had no idea of what to look for when I bought my usb device. It's just a pity line6 doesn't officially state what devices to use (in the pilot's handbook). I would have saved some money
I'll go and by a m-audio or maybe even a soundcard with midi.
Well, I just tried my new M-Audio MIDISport Uno and it worked right away
So all I have to do now is to get rid of the ROMi/o thing
I hope this thread will help others like me who just start exploring their Vetta and encounter the same problems...
I did the same with M-audio uno cable but my Vetta is not detected by Monkey.
I tried to install the drivers of the cable, eliminate the hub and make thousands attempts relying on the tips written above but nothing changes: my vetta doesn't work and its serial number can't be seen through Monkey.
How can I do to update the flash memory succesfully?