Roland Cloud

[WatchTheGuitar]

I’m living in Brexit Britain after a pandemic with threats of nuclear war, instead of trying to open that portal could we try closing it?

[vurt]

I’m living in Brexit Britain after a pandemic with threats of nuclear war, instead of trying to open that portal could we try closing it?

you know im here too?
i was gonna use the portal to escape to somewhere better...

[ChamomileShark]

unfortunately the portal opens in an alternative version of Basingstoke. One that's even worse.

[vurt]

noooooooo....

[vurt]

arrrrgggghhhhh!!!
just went to check if i need to buy electric...
.

Screenshot_2023-08-08-18-37-47-562~2.jpg

.
im being targeted!!!

[Atlatnesiti]

Sort of Apple Silicon. VST3 for JV and XV is working but the CPU overloads make it unusable. Audio unit is exactly the same, completely unusable.
D50 works well

Roland has updated another 6 plugins to meet AS native compatibility
Thanks heaps, only 10 to go...
BTW; 0 (zero) CPU spikes on my Mac mini Pro 2, works as intended

[Mogular]

Which host? And what format?

[Aloysius]

We only care about Windows 10. Spill the beans.

[Mogular]

To be clear, I'm not seeing any evidence of the CPU overloading, but I'm getting lots of clicks and pops. I've tried it in a number of hosts and I get exactly the same behaviour. This is ONLY with the JV and XV plugins. Everything else that has been released recently works very well. You can see the CPU going up and down in a nutty way as well. For example, on Ableton Live it's constantly oscillating up and down by four or five percent. Any of the other instruments, the CPU usage is very stable.

[Atlatnesiti]

Which host? And what format?

Cubase Pro, Ableton Live Suite, Reason and Logic Pro - all latest versions
PS; Both Vst 3 and Au behave ok

[Mogular]

And you are definitely running in native silicon mode? No Rosetta?

[Mogular]

I did some more tests. The problems are only happening for me when I am playing an instrument in real time. In Logic, for example, if I record a track and then switch to an audio track and then run playback it works very well. Extremely low CPU usage and no crackles.
The moment I go onto an instrument and try and play it live however the logic CPU meter immediately pegs to maximum and anything i play is accompanied by unexpected crackles.
Just to be really sure, I fully uninstalled both plugins and did a restart, but even after that the problem persists.

[Jon at Roland]

Not sure which others have been updated, but my D-50 and XV-5080 say they have updates.

Sadly the XV 5080 Name glitch is still there.

rsp

Hey there Zvenx. I'll be sure to bring it up with the team again and hopefully it'll be in the next round of updates. I would like to see this resolved as well. I think I might have posted about this here before so I apologize if I'm being redundant, but one workaround is to edit the patch file name to something shorter. The whole reason this is occurring is because the patch file name is too long. The patch names are stored in C:\ProgramData\Roland Cloud\XV-5080 and you'll see the factory patch banks labeled "PR-A.bin, PR-B. bin" etc.. if you abbreviate the patch names that appear distorted this should solve the problem. Thanks!

[zvenx]

Hi Jon, yes I had seen the workaround and did it this time after this update when I realised it wasn't fixed as yet.
thanks
rsp

[Atlatnesiti]

And you are definitely running in native silicon mode? No Rosetta?

Yep, AS native