Roland Cloud

[D-Fusion]

Is this on Mac or PC?

This project is on a PC running Cubase. After hours of faffing around we managed to downgrade to an earlier version of Zenology from another computer and everything works as it should again, so that's a small victory.

Ok.
I haven't tested the new Zenology with older projects on my PC but i will do that now to see if the same happens to on my system with Bitwig.

[samlletas]

PSA: Think twice before updating Zenology Pro if you're having older projects with drums from Zenology Pro. We didn't, and after updating Zenology Pro our project now crashes the DAW when we try to open it. So that's not great, and there's no way to downgrade to the previous version either what I can see. Thankfully I think we can salvage this by importing the other tracks in a new project and redo the drum track from Zenology, but yeah this isn't great Roland

Edit: actually this seems true for not only drum tracks, so if you're in the middle of a project using Zenology I wouldn't update at all.

I'm noticing much longer load times on this new Zenology version. Could the crash be related to that? For example, I'm on Reaper on PC and old projects take a while to load, but they eventually end up loading, perhaps some DAWs timeout before Zenology loads.

Some tests I did:

• Zenology v2.02 = 1st instance loads in about 10 seconds, 2nd instance loads faster in about 2 seconds.

• Zenology v2.03 = 1st instance loads in about 15-20 seconds, 2nd instance also loads in about 15-20 seconds.

So not only did the initial load time increased, but now also adding additional Zenology instances seems to be no longer optimized (e.g. reusing data from the 1st load) like the previous Zenology version.

[victoria]

Your guess is as good as mine, but we couldn't even import a single track running Zenology from old projects. Cubase would just freeze or crash, and when we re-started we'd get the "Cubase crashed because of this file: (zenology vst3)" window and the option to unload the plugin. It did seem to work just fine if we added Zenology to a new project, so I'm guessing there is just something not quite 100% backwards compatible with how Cubase has saved the state of the plugin.

[D-Fusion]

Your guess is as good as mine, but we couldn't even import a single track running Zenology from old projects. Cubase would just freeze or crash, and when we re-started we'd get the "Cubase crashed because of this file: (zenology vst3)" window and the option to unload the plugin. It did seem to work just fine if we added Zenology to a new project, so I'm guessing there is just something not quite 100% backwards compatible with how Cubase has saved the state of the plugin.

I Just tested some older projects that used Older versions of Zen Pro and they loaded up just fine in Bitwig so i guess it might be some Cubase Issue.

I had a hard time finding one of them since most of My Zen Pro Songs has been replaced with my Roland HW's But i found a few of them and they worked fine.

I usually use my HW first because of the long loading time of Zen Pro and most of the time I don't need Zen Pro since i already have 3 HW Zen core boxes that gives me 14 Instrument Tracks ready to go as soon as i open Bitwig.

But i do hope that your issue gets solved quickly since i know how it feels when something won't work as it should

[IvyBirds]

Your guess is as good as mine, but we couldn't even import a single track running Zenology from old projects. Cubase would just freeze or crash, and when we re-started we'd get the "Cubase crashed because of this file: (zenology vst3)" window and the option to unload the plugin. It did seem to work just fine if we added Zenology to a new project, so I'm guessing there is just something not quite 100% backwards compatible with how Cubase has saved the state of the plugin.

Are you using the Cubase Inspector on any of the tracks to modulate or control anything in Zenology that is visible to the DAW?

I am wondering if something changed with the way Zenology VST3 is communicating with Cubase in that regard so that now the inspector on old patches is trying to talk to something that is not there and is causing a crash, while the new version when freshly loaded is pointing at the proper location

[victoria]

At first I was thinking along those lines as well; we thought it was only caused by drum tracks, as that was part of the Zenology update and one of us had done some minor tweaks to a drum sample in Zenology. But then we realized it didn't matter, loading any track from an old project - even if it was just a stock preset with zero changes - would crash the DAW.

We did manage to downgrade to a previous version and it's all working fine for now, but if anyone here is running Cubase I'd advise you to make a safe copy of the previous version of Zenology before updating. Stay safe and don't waste hours on this like I did.

[JerGoertz]

Does Roland Cloud still report usage data, etc. back to Roland? ("spyware")

[Aloysius]

Are these people using mac computers to compile their plugins? On the JC-120 (Windows) they have this giant speaker grid that does nothing. All the important controls are tiny.

Aha. There's a control panel view that can be resized. Phew!

[Hyperbole]

The JV-1080, XV-5080, and all SRX instruments are still unusable for me on my M1 Max MacBook Pro with 64GB of RAM in Cubase Pro 13 running under macOS Sequoia. The CPU spikes almost continuously.

I really don't want to pay for Zenology Pro when all I need is the XV-5080, and I can use one of my LifeTime Keys for it. But since I can access the same XV-5080 presets in Zenology Pro (including the Wave Expansions that correspond to the various SRX instruments,) I suppose I will have to pony up for Zenology. Because Roland seems either incapable or unwilling to fix this CPU issue with the XV-type instruments. Oh well, at least I will get the nicer Visual Edit screen in Zenology and the new
VA oscillators and additional filter types.

[WatchTheGuitar]

Apparently I get three months Ultimate subscription ‘free’ after buying the Jazz Chorus amp plugin for $50.
May interest some here as it works out cheaper than the sub alone currently.
But, Roland you keep sending me the same email notifying me of this… for some reason every few minutes! I’m up to 10 so have tried unsubscribing from Roland emails to stop the flow. Sort your shit out please.

Edit: ffs I am still getting the emails after unsubscribing from emails!

IMG_1070.jpeg

[beely]

The JV-1080, XV-5080, and all SRX instruments are still unusable for me on my M1 Max MacBook Pro with 64GB of RAM in Cubase Pro 13 running under macOS Sequoia. The CPU spikes almost continuously.

That sounds like you are still running the old versions (as the poster above with the exact same issue was). What version number is displayed in the About box for the XV and JV plugins?

[WatchTheGuitar]

The flood of Roland Cloud emails finally finished. Yay!

[samlletas]

The performance of the new Zenology version (v2.03) is very bad:

1. Load times are worse, and each additional plugin instance takes longer to load for some reason.
2. My DAW slows down after adding 5 instances or more, I can't click on stuff and the Zenology UI doesn't even open.

I'm on Windows 10, my DAW is Reaper.

Reported the problem via the Roland contact form. Hopefully they don't take months/years to fix the performance

[Hyperbole]

The JV-1080, XV-5080, and all SRX instruments are still unusable for me on my M1 Max MacBook Pro with 64GB of RAM in Cubase Pro 13 running under macOS Sequoia. The CPU spikes almost continuously.

That sounds like you are still running the old versions (as the poster above with the exact same issue was). What version number is displayed in the About box for the XV and JV plugins?

Ah, you're right. I am still using version 1.0.4. I just assumed that I had already been updated to version 1.0.5. How do I get version 1.0.5 of the XV-5080 plugin? There is no update for it in the Roland Cloud app. Is v1.0.5 a beta version or something like that? If so, can I download the beta from the Roland site?

[JamminFool]

reload RCM repeatedly until it decides to show it to you.