More Adventures in JV-1080 Land

More Adventures in JV-1080 Land

And a formal excuse. This is the “Mea Maxima Culpa” Edition.

So, my last post about the Roland Cloud JV-1080 had a few inaccuracies that I want to iron out here instead of re-writing the former post.

Disclaimer ;)

Okay, so I know there are more models in the series; JV-1010, XV-2020, XV-3080 and XV-5050 but I’ll stick to and will only refer to the XV-5080.

Quoting myself

Mea Maxima Culpa

1. The JV-1080 and the JV-2080 doesn’t have true stereo waveforms per tone. This is a feature found in the XV series, and this is also why the Cloud JV (let’s just call it that from now on) is more of a XV-3080/5080 than the good ol’ JV-1080.

2. The modulation routing section, or Common Controls as they seem to be called on the JV-1080, is different from the Cloud JV too. The Cloud JV has the 4 by 4 matrix as the XV-5080. On the JV-1080 there are three controls to be used where the first source is hard-routed to the modulation wheel. The second and third are freely assignable to any controller you like. These three controllers can modify four parameters per tone. Ok? The Cloud JV, and the XV-5080 has a modulation matrix (see below) made up by four sources and four destinations with no separations of tones more than that you can turn on or off a tone for each destination. Destination 1 for source 1 can control one parameter but for all four tones; or any of them. But just one parameter. This is quite a huge difference and you’ll have to have your tongue in your own cheek when manually editing sounds to clone your JV-1080 catalogue.

Roland Cloud JV-1080, with my Happy Holidays patch

3. I was also wrong about the micro-tuning part. Sorry. Both the JV-1080, JV-2080 and the rest has this.

4. Don’t think I mentioned it, but the JV-1080 and JV-2080 doesn’t have Categories to which a Patch can be assigned; for example “Soft Pad”, “Hard Lead” and so on. But in the Cloud JV? (wait for it Jeremy Clarkson style) You can!


JV-1080Cloud JV-1080XV-5080
Waveforms Per Tone122
EFX Processors115
Expansions4x SR-JV804x SRJV-80
4x SRX
Modulation Matrix3 by 44 by 44 by 4
Sample PlaybackNoNoYes
Comparison Table

The Cloud JV is clearly more of an XV-5080 in JV-1080’s clothing.

Performance Mode, Sort of…

Presonus Studio One lets you create your own “Multi Instruments”. You can also add arpeggiators to any of the instances by adding “Splitter”.

Studio One Multi-Instrument with 16 Roland Cloud JV-1080
Studio One Performance Monitor

Mmm, Tasty Little CPU

But adding 16 Cloud JVs to a project will be hard on your CPU, as you can see to the left. I have a 2.8 GHz Intel Core i7 in my DAW and the CPU load here is without any additional effect plugins.

I’m working on reviving one of my old songs written and recorded using the JV-1080 and simply just bounce a new version using the Cloud JV instead. I’ll post a link to it as soon as I’m done. I’ll also post the original, which has been bounced off a C60 cassette without Dolby for extra noise and wobble… since that’s what I had back then. Oh, and the original was mixed using a Samson Mixpad 9! You don’t see them very often these days.

The CPU usage when loading 16 Cloud JVs is quite high. Makes me think of how well the old RISC processor in the JV-1080 really was, even thought this is quite and unfair comparason. Makes the legacy even stronger, and makes this successor even more amazing.

Further Reading, And Nerding

I recommend you to read Don Solaris’ The Ultimate JV, JD, XV F.A.Q. and don’t let the URL fool you.

Don also has a great post about the JD-990, which the JV-*080 and XV seriers are derived from. Read it!


I’m super excited what Roland Cloud has in their bag of secrets when it comes to further expanding the Cloud JV, and of course what more synths that will come. I, for one, was completely sure that the JX-3P, JX-8P or JX-10 was supposed to be released before the JV-1080. How wrong was I? But I’m glad I was wrong.


Swedish artist, music producer, composer and remixer.

1 comment so far

Roland Cloud JV-1080 – PaleSkinnySwede

[…] and inaccuracies in this article has been revised in this post instead of re-writing this […]