I've been using the Roland v1.0.4 VSTs (R2R) since 2023 but today they all started making loud random noises when playing MIDI, like they are in demo mode. Going into options on the modules it states "authorized". I tried uninstalling and reinstalling. Same problem. I've not changed my settings or added any new software. I am using Cubase with Windows 11. Any ideas on how to fix?

 

Interesting, I tried playing with the 909 a couple days ago when i needed to jot an idea and I couldn't get it to produce sound at all, didn't have much time so I switched to a diff plug instead (D16), haven't investigated if I thought it was a timebomb or user error but i didn't think i was doing anything wrong. Perhaps they have timebombed.

 

Did you look at the original posts of them on the sister site? Sometimes people go back to original place where they downloaded something from and leave comments if something has time bombed. I looked on another site, and there are no complaints left by others with the issue on there. The only Windows releases I see are from August of 2023, and were all released separately. Same ones? That's quite a delay if they really have time bombed. Until a more recent update, the Mac versions I was using were even older.

Did you change any settings in your firewall, or somehow allow outbound traffic to escape? You'd expect more posts about this...

 

Just tested my Jupiter 4, all clear. What product are you using? If it happens to be this one, have you checked the ensemble blue button and the condition knob? Roland Cloud's emulations emulate even the noise of old devices, including their famous Juno chorus. This can be further complicated by signal processing down the chain.

 

I tested my D-50, JD-800, JUNO-106, JUPITER-4, JUPITER-8, XV-5080, all works. WIN 11, Studio One 7, Cubase 14, Reaper latest release.

 

I have a problem of different nature with all Roland 2023 R2R releases - all sound banks get renamed to .bak and instruments don't recognise them, so every plugin ends up without any sounds. You can trick them into loading those sounds by renaming them back to .bin, but every time you restart the plugins they rename sound banks to .bak again and you have to rename them again and again and again (like that Cure song... "A Forest" lol). I have tried a lot of things to make them work, but had to call it quits and gave up. Only Zenology by VR works for me, and that's the best one so I'm not complaining. Maybe old Roland R2R releases that used different protection would work.

However, I'm using WINE 9 stable with Yabridge 5.1.1 in Linux Debian 12.10, so that doesn't help probably. Some heavily protected plugins just don't work with Wine, like most PSP and D16 plugins.

I've just tried XV-5080 v104 again and yes - sound banks get renamed as soon as you start the plugin and you get no sounds to play. Maybe if you make some yourself.. it could work?

The point of why I posted this is that it seems these Roland 2023 R2R's releases are not so reliable and probably very hard to crack properly. They even mention in the .nfo this same problem happening to other team's releases. Well, it happens to theirs, too, in some cases.

I FOUND THE SOLUTION! Thank you for bringing this up, so I tried to make it work again and found the solution. I prevented the plugin from changing a certain file by not giving it permissions to change it and now it can't selfdestruct its sounds. :mid-finger-to-roland:

 

Last edited: Mar 30, 2025 at 1:15 PM

Nice one pal.
THE POWER OF READ-ONLY PERMISSION... soon in your best theaters

 

The problem is just copying bin files into the folder without the plugin knowing about it - it will reject them in the way you describe. Instead, if you load the bank via it's preset browser, it will place it properly there and it will stick, as the plugin knows about the files that way.

 

I use the Roland SRX Strings, Jupiter 8, SRX Brass, SRX Electric Pianoi, SRX Keyboards, SRX orchestra. SRX Piano 1 & 2, STRX STudio, and XV 5080. I use a legit version of 9.5 Cubase on Windows 11. Yes, these are from 2023 and I've used them a lot. I've changed nothing in my settings. All of a sudden they all started making random loud noises like an old Simmons synth drum hit when playing MIDI. I tried recording into audio and the sounds are there in the audio. I uninstalled all modules and reinstalled and same. I've an older version of Sound Canvas and it works okay. (I've rarely used it) The Roland modules are the only ones doing this. Everything in the modules works great exept for all the loud random noises blurting out. I tried every Roland Cloud module I use and they all do it. All my other VSTs work well. I've only tried the R2R versions from 2023 and not V.R., and have been using these since they were posted. I looked on the sister site and there are no comments on most of the posts from 2023 on the Roland Cloud stuff. Thank-you for your answers.

 

The noises sound like hits from an old Simmons drum kit, and the noises are loud. It is on every Roland module I have except an old version of Sound Canvas which I rarely use. I used all of them a lot, since 2023 when posted. I do not use many plugins and have not changed any setting or added VSTs in a long time. My old Cubase 9.5 is legit and I'm using Windows 11. The modules make the sounds even as the only plugins in a project with no other VSTs. They simply started all doing this yesterday. No other sound modules make these noise at all, only the Roland. Thank-you for the reply.

 

As I am on Linux too, I have the exact same problem! Reading you have solved it, would you mind to elaborate on your solution because I don't understand what you mean with: "I prevented the plugin from changing a certain file by not giving it permissions to change it and now it can't selfdestruct it's sounds." ???

 

might be cloud farts, caused by solar discharge in the upper atmosphere. Consider wrapping your computer in aluminum foil or a faraday cage if you have one laying around. Make sure you have ground strap connected to a copper rod driven into the soil at least 19 inches. or it could be a windows glitch, sometimes its hard to tell.

if it continues, send all your gear to me (prepaid) and I'll test it and send it back to you (prepaid) - usually takes about 6 months of testing to really suss things out. Let me know before shipping and I'll give you my P.O. box# to drop ship it to..

 

Not so much. ;)

However, R2R I believe prefer to leave the plugins unmodified and write client software to emulate the live server, so authorisation calls are being made, just they are getting answered locally to authorise the plugins.

Personally, I don't prefer that approach because it means you have to run all kinds of licensing emulation processes running all the time...

 

I had to remove *all* permissions, even read ones. If you leave read permissions the plugin changes its permissions to "write" and there go your sounds again. cunning. I can't remember if you can do that in Windows - remove all permissions and still be able to have and change the file as a "root" (admin). It's a text file in ProgramData/Roland Cloud/name_of_the_plugin folder that gets created when you start the plugin. I wonder if it works the same in real Windows. Probably not as nobody posted any problems of this kind that I know of.

Anyway, I made XV-5080, JV-1080, System-8, JD-800 and D-50 work this way. I'm not too fond of Roland plugins... The graphics are very glitchy. but they sound great.

 

Last edited: Mar 30, 2025 at 1:53 PM

Plugins create a file called "InstalledBankNames.dat" in ProgramData/Roland Cloud/name_of_the_plugin folder which lists all the installed sound banks and then the plugin won't load them. What I did is delete all the text from this file and made it have no permissions at all, so the plugin cannot change it, but it's there, empty. If you remove it a plugin will create another one and there we go again with the problem. It just has to be there so plugins cannot create it again. I also moved all the .bin banks from there to Program Files/Roland Cloud/name_of_the_plugin/Patch so all the .bin sound banks are in one place.

 

Thanks SIneWave, but I still do not quite understand what you are doing.
I withdraw all permissions of "InstalledBankNames.dat". I also withdraw all permissions of "PR-A.bin" and then place that file "PR-A.bin" in "wine/drive_c/ProgramData/Roland Cloud/XV-5080/", then the XV5080 cannot "see" that file. When I try to load it, the program says it cannot be read. So the .bin file has to be readable. If I make the "PR-A.bin" readable, then the program sees the file when starting XV5080, but after closing reaper it is renamed to .bak again. The only thing that works is what you did: put the files somewhere else and then load them. But then you have to load the .bin files each time you want to use the plugin. Is that correct? So being able to access all the .bin files from the start is not possible?

 

No. As posted above, once you load the file through the plugin browser, the plugin "knows" about the file, and it won't be disabled, and always available.

 

Does this remain true when the plugin is being loaded via Wine? Every time the emulated plugin is closed, it will lose the location "remembered" by the plugin this way.

 

No idea, I'm on Mac, and don't know anything useful about non-typical uses, or what filesystem plugins running in emulation have access to...
Why are you running them in Wine?