Roland Cloud

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic

Post

Introspective wrote: Thu Jun 06, 2024 3:31 pm
Jermusic wrote: Thu Jun 06, 2024 2:40 pm This is essentially my issue right now, Roland Cloud plugins take forever to load in REAPER and then if they load at all, they are highly unstable and make REAPER crash. This is a serious issue.
Sounds familiar (though I use BitWig, not Reaper: you are brave!) ...

I actually contacted support (at the same time as posting my last message) and they JUST got back to me. After a quick follow-up question, they replied immediately and suggested I roll back (UNINSTALLING the RCM first, of course) to an older version of the RCM: 3.1.3 and that actually worked like a charm, everything is loading again, and quickly.

Phew!

...Still feeling pretty wary, but I am heartened that they responded so quickly and that their first suggestion actually worked...
Thank you very much! I followed your instructions and rolled back to RC 3.1.3 and it works like a charm on my PC as well. Again, thank you!
Last edited by Jermusic on Thu Jun 06, 2024 4:32 pm, edited 1 time in total.

Post

Jermusic wrote: Thu Jun 06, 2024 4:25 pm
Introspective wrote: Thu Jun 06, 2024 3:31 pm
Jermusic wrote: Thu Jun 06, 2024 2:40 pm This is essentially my issue right now, Roland Cloud plugins take forever to load in REAPER and then if they load at all, they are highly unstable and make REAPER crash. This is a serious issue.
Sounds familiar (though I use BitWig, not Reaper: you are brave!) ...

I actually contacted support (at the same time as posting my last message) and they JUST got back to me. After a quick follow-up question, they replied immediately and suggested I roll back (UNINSTALLING the RCM first, of course) to an older version of the RCM: 3.1.3 and that actually worked like a charm, everything is loading again, and quickly.

Phew!

...Still feeling pretty wary, but I am heartened that they responded so quickly and that their first suggestion actually worked...
Thank you very much! I followed your instructions and rolled back to RC 3.1.3 and it works like a charm on my PC as well. Again, thank you!

Post

PAK wrote: Thu Jun 06, 2024 4:04 pm
ozinga wrote: Wed Jun 05, 2024 7:51 pmAround October I had 5080 and 1080 cpu spike issues. Support told me that an update soon will fix.
After so many years I finally quit my sub around Jan when it seemed that no fix is coming. I see that as of know there is still not a single update for those plugins.
Regarding the 5080 and 1080 plugins (and all SRX plugins) and the CPU spiking issues - They are known to impact higher end Apple M1 chips at this point. Roland support uses iMac’s, which aren’t impacted, and thus they won’t confirm the issue - even though everyone knows it’s an issue at this point.

Last I’d heard RC support had asked Roland to supply them with a Mac Studio they could use to verify the issue, but I don’t know if this request was ever granted. If it wasn't that would be an incredibly worrying thing..
The very fact they even had to ask is a very worrying thing

Post

D-Fusion wrote: Thu Jun 06, 2024 3:55 pm
I think it is time for them to make a new cloud app and get away from this bloated crap we are offered now and offer 1 time activation for lifetime keys.
I have suggested this before elsewhere but I will suggest it again here

They should drop the entirety of RCM, just trash it and get rid of it forever, once that happens they should move onto step 2

At the core of every Roland Cloud Software title is an emulator for their custom bespoke chips that run the hardware. They do that so they can just port the ACB or Zencore code from the hardware to the software. This allows allows GALAXIAS to work as it's just one giant emulator

Anyway make two simple plugins one for Lifetime Keys, and one for Subscriptions

These plugins will just be a shell that contains the emulator. So you would launch the Roland Cloud Plugin then select the instrument you want to use say "Jupiter 8" and it loads the code for the Jupiter 8 and bam it's a Jupiter 8. If it's the Lifetime Key version you have already unlocked it and it will just load forever. If you try to load an instrument that you don't own it will prompt you for the serial number or allow you to buy it

If it's the subscription model it will work the same way only everything in your plan is unlocked and you could choose to manually connect to unlock your next subscription period or have the plugin do it automatically at launch

Doing this would be so simple to use and make it so simple to say be working on a pad sound for your track on say a D50 and easily just switch it to XV5080 without doing anything in your DAW

Post

IvyBirds wrote: Thu Jun 06, 2024 4:54 pm
D-Fusion wrote: Thu Jun 06, 2024 3:55 pm
I think it is time for them to make a new cloud app and get away from this bloated crap we are offered now and offer 1 time activation for lifetime keys.
I have suggested this before elsewhere but I will suggest it again here

They should drop the entirety of RCM, just trash it and get rid of it forever, once that happens they should move onto step 2

At the core of every Roland Cloud Software title is an emulator for their custom bespoke chips that run the hardware. They do that so they can just port the ACB or Zencore code from the hardware to the software. This allows allows GALAXIAS to work as it's just one giant emulator

Anyway make two simple plugins one for Lifetime Keys, and one for Subscriptions

These plugins will just be a shell that contains the emulator. So you would launch the Roland Cloud Plugin then select the instrument you want to use say "Jupiter 8" and it loads the code for the Jupiter 8 and bam it's a Jupiter 8. If it's the Lifetime Key version you have already unlocked it and it will just load forever. If you try to load an instrument that you don't own it will prompt you for the serial number or allow you to buy it

If it's the subscription model it will work the same way only everything in your plan is unlocked and you could choose to manually connect to unlock your next subscription period or have the plugin do it automatically at launch

Doing this would be so simple to use and make it so simple to say be working on a pad sound for your track on say a D50 and easily just switch it to XV5080 without doing anything in your DAW
i assume you are just speculating, or have you actually seen the code?

Post

JamminFool wrote: Thu Jun 06, 2024 5:05 pm
IvyBirds wrote: Thu Jun 06, 2024 4:54 pm
D-Fusion wrote: Thu Jun 06, 2024 3:55 pm
I think it is time for them to make a new cloud app and get away from this bloated crap we are offered now and offer 1 time activation for lifetime keys.
I have suggested this before elsewhere but I will suggest it again here

They should drop the entirety of RCM, just trash it and get rid of it forever, once that happens they should move onto step 2

At the core of every Roland Cloud Software title is an emulator for their custom bespoke chips that run the hardware. They do that so they can just port the ACB or Zencore code from the hardware to the software. This allows allows GALAXIAS to work as it's just one giant emulator

Anyway make two simple plugins one for Lifetime Keys, and one for Subscriptions

These plugins will just be a shell that contains the emulator. So you would launch the Roland Cloud Plugin then select the instrument you want to use say "Jupiter 8" and it loads the code for the Jupiter 8 and bam it's a Jupiter 8. If it's the Lifetime Key version you have already unlocked it and it will just load forever. If you try to load an instrument that you don't own it will prompt you for the serial number or allow you to buy it

If it's the subscription model it will work the same way only everything in your plan is unlocked and you could choose to manually connect to unlock your next subscription period or have the plugin do it automatically at launch

Doing this would be so simple to use and make it so simple to say be working on a pad sound for your track on say a D50 and easily just switch it to XV5080 without doing anything in your DAW
i assume you are just speculating, or have you actually seen the code?
Let's just say I am not speculating, the bulk of the heavy lifting and what causes the slow load times is the emulator, the code for the actual instruments is only a handful of MBs, sample based instruments have sample libraries as well, but those are kept small and use the small files used in 1990s XV series

Roland calls their custom bespoke chips "BMC" In this article the CEO of Roland talks about them

https://www.roland.com/uk/promos/jupiter-x_story/

Roland Cloud Instruments are all built on a BMC emulator, they should just embrace that and ditch the RCM

Separate the code from individual instruments from the emulator that makes them work

Post

IvyBirds wrote: Thu Jun 06, 2024 5:44 pm
JamminFool wrote: Thu Jun 06, 2024 5:05 pm
IvyBirds wrote: Thu Jun 06, 2024 4:54 pm
D-Fusion wrote: Thu Jun 06, 2024 3:55 pm
I think it is time for them to make a new cloud app and get away from this bloated crap we are offered now and offer 1 time activation for lifetime keys.
At the core of every Roland Cloud Software title is an emulator for their custom bespoke chips that run the hardware. They do that so they can just port the ACB or Zencore code from the hardware to the software. This allows allows GALAXIAS to work as it's just one giant emulator

Anyway make two simple plugins one for Lifetime Keys, and one for Subscriptions

These plugins will just be a shell that contains the emulator. So you would launch the Roland Cloud Plugin then select the instrument you want to use say "Jupiter 8" and it loads the code for the Jupiter 8 and bam it's a Jupiter 8. If it's the Lifetime Key version you have already unlocked it and it will just load forever. If you try to load an instrument that you don't own it will prompt you for the serial number or allow you to buy it

If it's the subscription model it will work the same way only everything in your plan is unlocked and you could choose to manually connect to unlock your next subscription period or have the plugin do it automatically at launch

Doing this would be so simple to use and make it so simple to say be working on a pad sound for your track on say a D50 and easily just switch it to XV5080 without doing anything in your DAW
i assume you are just speculating, or have you actually seen the code?
Let's just say I am not speculating, the bulk of the heavy lifting and what causes the slow load times is the emulator, the code for the actual instruments is only a handful of MBs, sample based instruments have sample libraries as well, but those are kept small and use the small files used in 1990s XV series

Roland calls their custom bespoke chips "BMC" In this article the CEO of Roland talks about them

https://www.roland.com/uk/promos/jupiter-x_story/

Roland Cloud Instruments are all built on a BMC emulator, they should just embrace that and ditch the RCM

Separate the code from individual instruments from the emulator that makes them work
the Legendary instruments are built using ACB, while the ZEN-Core instruments are built on the BCM technology. The only ZEN-Core instruments in the Roland Cloud are Zenology and the Zenology Expansions. ACB does not use BCM. It pre-dates BCM. So, no, I don't think all Roland Cloud Instruments are built on a BMC emulator.

I don't know, since I also have not seen the code, but as a result I don't think that what you proposed would cover both technologies. :shrug:

Post

JamminFool wrote: Thu Jun 06, 2024 6:16 pm the Legendary instruments are built using ACB, while the ZEN-Core instruments are built on the BCM technology.
Which is the better code base though for accurate sounds ?

Post

IvyBirds wrote: Thu Jun 06, 2024 5:44 pm Let's just say I am not speculating, the bulk of the heavy lifting and what causes the slow load times is the emulator, the code for the actual instruments is only a handful of MBs, sample based instruments have sample libraries as well, but those are kept small and use the small files used in 1990s XV series
remember all those presets packs for the legendaries and zenology.
Each and every one needs to be validated DRM wise with Roland when you load em in.
So 150 presetpacks for zeno means 150 checks before loading the thing on your screen.

It is just a shitty framework and Roland has painted itself in the corner with their arrogant way of conducting their sub business.

Post

Is it me? I cannot believe how long it's taking to load these synths in Studio one 6. They don't seem to take that long if I make them part of the template but the wait time loading them on an individuual instrument track is pretty bad.I take that back. It REALLY bad.

Post

Digivolt wrote: Thu Jun 06, 2024 7:05 pm
JamminFool wrote: Thu Jun 06, 2024 6:16 pm the Legendary instruments are built using ACB, while the ZEN-Core instruments are built on the BCM technology.
Which is the better code base though for accurate sounds ?
ACB :tu:

Post

JamminFool wrote: Thu Jun 06, 2024 6:16 pm Roland Cloud Instruments are all
the Legendary instruments are built using ACB, while the ZEN-Core instruments are built on the BCM technology. The only ZEN-Core instruments in the Roland Cloud are Zenology and the Zenology Expansions. ACB does not use BCM. It pre-dates BCM.
BCM are Roland's proprietary CPU chips that run both the ACB hardware like the System 8 which is all ACB all the time and the Zen Core instruments that came out later

All of the Roland Cloud instruments use the BCM emulator for both ACB and Zenology instruments

ACB is just code that runs inside of BCM chips, Zencore is also just code running inside of a BCM chip

You can see the BCM Chips inside of the System 8 in this video at around 2:18



BCM chips replaced the Roland/Boss ESC2 chips that were used in things like the Integra 7 and the Jupiter 80 for Supernatural which is why we don't have the SNS engine as a plugin and probably never will despite how awesome that will be

We do however have some Supernatural Samples inside of Zenology
Last edited by IvyBirds on Thu Jun 06, 2024 9:43 pm, edited 2 times in total.

Post

dblock wrote: Thu Jun 06, 2024 8:54 pm Is it me? I cannot believe how long it's taking to load these synths in Studio one 6. They don't seem to take that long if I make them part of the template but the wait time loading them on an individuual instrument track is pretty bad.I take that back. It REALLY bad.
Read my previous comment, about 10 comments back in the thread.

Post

Septic Underground wrote: Thu Jun 06, 2024 7:22 pm
IvyBirds wrote: Thu Jun 06, 2024 5:44 pm Let's just say I am not speculating, the bulk of the heavy lifting and what causes the slow load times is the emulator, the code for the actual instruments is only a handful of MBs, sample based instruments have sample libraries as well, but those are kept small and use the small files used in 1990s XV series
remember all those presets packs for the legendaries and zenology.
Each and every one needs to be validated DRM wise with Roland when you load em in.
So 150 presetpacks for zeno means 150 checks before loading the thing on your screen.

It is just a shitty framework and Roland has painted itself in the corner with their arrogant way of conducting their sub business.
Totally agree it's all shitty, takes way to long and uses way more CPU than it needs to

Post

Where is Jon from Roland?
Collector of VSTs

Post Reply

Return to “Instruments”