I have to agree with David guys. I don't have the Roland JV2080, but I do have the XP60, which is essentially the same thing.

I've never had any problems with the timing of my XP60 period. Never. I never had problems even when I triggered it from programs like Cakewalk or Cubase. And like David, my X also fully loaded.

The 3FX story is a likely one, but I've come accross people who comaplain about this, and people who deny this all the way. I'm one of tghe deny-ers. Sorry all, check the rest of your systems.

The Infamous EPU.

David,
Is there some settings I'm missing on the 2080 to disable or filter these settings? I'm sending MTC through Cakewalk to the VS-880 for synchronization. But on 2080, I've disable Rx of Sysex msgs and pretty much everything else except pan, bend, and volume.
Incidentally, I sent my USB Midman back and am exchanging it for a Portman serial model.

No disrespect taken. However I will disagree with anyone who says there isnt a problem with midi timing on the 2080. Whilst I accept that cc data, sysex etc can clog up midi timing on anything. On the 2080 that just makes it worse. When I had one I tried it on numerous systems and setups and the result was the same, sloppy/sluggish response to midi data. I also realise that midi is a serial protocol so that midi events happen sequentially (there will always be some delay with lots of stacked notes). However, what i noticed was that it depends on how you program it. At the time I was using the 2080 as a "do it all synth" ie 16 channels of heavy usage, but within the supposed 64 voice limit. Timing became more erratic with the rhythm channel being used, and use of lfos and tight envelopes. I even spoke to Roland at the time, who after listening to a midi file i sent them, had to admit that the timing wasnt as good as the rest of the JV/XP series. (The XP60 isnt't the same, it only has 1 EFX).

Also, one of the ways i found out there was a problem was when I set a reasonably complex sequence up, with one sound having a delay effect added. Then if i dropped in the drum channel the delay would hiccup, due to the voices being triggered slightly later

In my opinion, it is really down to how you use it. I'm sure no one is going to notice if you've got lots of slow evolving sounds coming out, but if, like me, you were trying to get near enough a whole tune out of the thing, with tight parts, you will notice it.

Oh, and mine had a shocking buzz/distortion in the outputs as well!

I'm just trying to let people know the truth, which is that Roland ripped everyone off by saying that the 2080 can do 64 voices and 3efx properly. They just cashed in on an existing processor design, and wrote a bit of extra software.

I look forward to being flamed!!!

Hi all,

Reports of MIDI timing problems with the JV-2080 have reached legendary status, regardless of whether it is pure urban legend or has some basis in fact.

I agree with the others who say to analyze the data stream to make sure controller info. isn't clogging the works, check for MIDI loops, etc.

Interesting bit about 'phase lock': what I'm wondering is, what about using other modules along side the XV-5080? They aren't 'phase locked'.

Regardless, one could make an argument that the XV-5080 contains 2 MIDI IN's for a good reason: Roland learned a lesson about the importance of parallel MIDI processing with the 2080.

Chris

The 2080 midi problem is well documented. However, some sources are actually now saying that it in fact ISN'T a midi problem, but a polyphony problem!

Seems Roland may have not been exactly honest about the polyphony.