Roland Cloud

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

Post

i already have 8 instruments from cloud, so I canceled my subscription to get 2 new instruments like sh-5 and jupiter 6 anytime

Post

I have all the lifetime keys i need and some can be consider duplicates even if they are a little different like ACB/ABM because there wasn't enough on offer for me choose what i wanted since Zenology and it's products are not included in the P4Life rewards.

I Also choose 3 SRX as lifetime keys that i already have lifetimes keys for in Zenology Pro because there was nothing else for me to choose from in their lifetime reward list.

I was thinking of using those 3 slots when something new came out that isn't a duplicate of what i already have but their new policy that came without no warning stopped that and changing lifetime key products In the Roland Cloud page is not possible anymore.

If they had given me a warning about this beforehand I would have Changed them to The Drum Machines instead of having the double Srx banks in 2 different formats.

Post

vulpes777 wrote: Thu Nov 16, 2023 10:45 am
I think the [JV/XV] display bug is still there, as someone at Roland sneakily updated the library names to make them shorter, so that they don't overlap with the patch name in the GUIs.
I cancelled my Ultimate last December. I have a few legendary keys, some I bought and some from P4L. I can’t believe the same bugs have persisted for years and continue to get reported and ignored. But in this case, it’s worse than ignored. Someone actually took the time to “fix” this in the laziest possible way – which just hides the bug and doesn’t fix the real issue that users experience trying to import their legacy banks (kind of the whole reason I packed up my hardware version).

I’ve got money to give you, Roland. I spend thousands each year on gear and software. I’m back here a year after unsubscribing because I’m willing to come back, and interested in what Roland has been up to, and I find the same old nonsense. Stuff that still doesn’t work as it should. Why are you unwilling to fix something so simple? I promise if I had the source code, I could fix this display bug the right way in literally minutes.

IMG_6742.jpeg
You do not have the required permissions to view the files attached to this post.

Post

SLiC wrote: Tue Nov 28, 2023 12:08 pm I suspect more people would be excited by this over anything else :hyper:

Image
Throw in a JD990 alongside that JP8080 and V-Synth and I'll be set for life on any and everything Roland related :phones:

Post

ToddlerTN wrote: Wed Nov 29, 2023 2:05 am Why are you unwilling to fix something so simple? I promise if I had the source code, I could fix this display bug the right way in literally minutes.
They DGAF obviously.

Post

ToddlerTN wrote: Wed Nov 29, 2023 2:05 am
vulpes777 wrote: Thu Nov 16, 2023 10:45 am
I think the [JV/XV] display bug is still there, as someone at Roland sneakily updated the library names to make them shorter, so that they don't overlap with the patch name in the GUIs.
I cancelled my Ultimate last December. I have a few legendary keys, some I bought and some from P4L. I can’t believe the same bugs have persisted for years and continue to get reported and ignored. But in this case, it’s worse than ignored. Someone actually took the time to “fix” this in the laziest possible way – which just hides the bug and doesn’t fix the real issue that users experience trying to import their legacy banks (kind of the whole reason I packed up my hardware version).

I’ve got money to give you, Roland. I spend thousands each year on gear and software. I’m back here a year after unsubscribing because I’m willing to come back, and interested in what Roland has been up to, and I find the same old nonsense. Stuff that still doesn’t work as it should. Why are you unwilling to fix something so simple? I promise if I had the source code, I could fix this display bug the right way in literally minutes.


IMG_6742.jpeg
D-Fusion wrote: Thu Dec 16, 2021 1:30 pm I have been waiting for Months on a Fix for a serious bug in the SRX Dance Trax where it doesn't save the preset properly.
When using PCM from SRX B Waves and save it as a Preset it points to SRX A Wavebank on Reload and the workaround they gave me is to Select SRX A and then SRX B to get to the correct PCM Sample in your preset.

Hope this will be fixed soon.
Wonder if this has been fixed yet since i never got any reply from them saying that the bug is fixed and i removed the SRX Dance trax because of this bug and bought the Zenology version instead because of it + It is much better having all the SRX banks in one plugin instead of having them in separate products.

If the bug is still there than it has been going on since the Dance trax was released and i noticed it when i started to make my own presets with it.

Post

How about this great feature...hide keyboard. TAL is again much better in this.

Screenshot 2023-11-29 at 10.34.24.jpg
Screenshot 2023-11-29 at 10.34.38.jpg
Screenshot 2023-11-29 at 10.39.26.png
Screenshot 2023-11-29 at 10.39.40.png
You do not have the required permissions to view the files attached to this post.

Post

ToddlerTN wrote: Wed Nov 29, 2023 2:05 am
vulpes777 wrote: Thu Nov 16, 2023 10:45 am
I think the [JV/XV] display bug is still there, as someone at Roland sneakily updated the library names to make them shorter, so that they don't overlap with the patch name in the GUIs.
Stuff that still doesn’t work as it should. Why are you unwilling to fix something so simple? I promise if I had the source code, I could fix this display bug the right way in literally minutes.
Hey ToddlerTN and vulpes777. As I've mentioned before Roland Cloud is a small and international team of people working on software maintenence, product design, managing online sales, the website and so much more. That being said, smaller cosmetic issues are sometimes unintentionally moved aside for the purpose of fixing bigger issues. Sometimes things will simply get miscommunicated via translation between different teams. No one is unwilling to fix these things. We aren't intentionally avoiding them. For this particular issue, it has been noted and a ticket has been made for it. Next time I get a chance I'll bring it up again with the team and try and get it pushed ahead and get it included in the next update. But know that we get tons and tons of tickets a day that all require attention and we appreciate your patience while we work through these things.

In the meantime, the issue is simply that the patch name is too long. By renaming the patch to something smaller or abbreviated, this is a good work around for this issue. It looks goofy to have the name overlap like this and I would also like to see it fixed. We really appreciate your support! And thank you for the feedback. :)

Post

Jon at Roland wrote: Thu Nov 30, 2023 12:16 am
smaller cosmetic issues are sometimes unintentionally moved aside for the purpose of fixing bigger issues

-snip-

For this particular issue, it has been noted and a ticket has been made for it. Next time I get a chance I'll bring it up again with the team and try and get it pushed ahead and get it included in the next update. But know that we get tons and tons of tickets a day that all require attention and we appreciate your patience while we work through these things.

In the meantime, the issue is simply that the patch name is too long. By renaming the patch to something smaller or abbreviated, this is a good work around for this issue. It looks goofy to have the name overlap like this and I would also like to see it fixed. We really appreciate your support! And thank you for the feedback. :)
I appreciate you taking it seriously, Jon.

I would argue that this is not simply a cosmetic issue. It directly affects usability. Let me try to explain.

I’ve been using custom JV/XV patch banks since the 1990s, and having renamed them now to employ the workaround throws me every time I go looking for a patch I committed to memory long ago. I’ve got a little cheat sheet, but it’s really frustrating. It takes me out of my creative flow.

For anyone whose first experience with the JV-1080 is via Roland Cloud, I’m sure this bank name bug seems like no big deal. But for someone like me intending to replace a piece of gear that I’ve used for almost 30 years with the faithful reproduction that is the Legendary Roland Cloud version, this bug is jarring, and it impedes my workflow.

Post

ToddlerTN wrote: Thu Nov 30, 2023 4:01 am
Jon at Roland wrote: Thu Nov 30, 2023 12:16 am
smaller cosmetic issues are sometimes unintentionally moved aside for the purpose of fixing bigger issues

-snip-

For this particular issue, it has been noted and a ticket has been made for it. Next time I get a chance I'll bring it up again with the team and try and get it pushed ahead and get it included in the next update. But know that we get tons and tons of tickets a day that all require attention and we appreciate your patience while we work through these things.

In the meantime, the issue is simply that the patch name is too long. By renaming the patch to something smaller or abbreviated, this is a good work around for this issue. It looks goofy to have the name overlap like this and I would also like to see it fixed. We really appreciate your support! And thank you for the feedback. :)
I appreciate you taking it seriously, Jon.

I would argue that this is not simply a cosmetic issue. It directly affects usability. Let me try to explain.

I’ve been using custom JV/XV patch banks since the 1990s, and having renamed them now to employ the workaround throws me every time I go looking for a patch I committed to memory long ago. I’ve got a little cheat sheet, but it’s really frustrating. It takes me out of my creative flow.

For anyone whose first experience with the JV-1080 is via Roland Cloud, I’m sure this bank name bug seems like no big deal. But for someone like me intending to replace a piece of gear that I’ve used for almost 30 years with the faithful reproduction that is the Legendary Roland Cloud version, this bug is jarring, and it impedes my workflow.
I totally understand ToddlerTN, and I will include that in my feedback around this issue as well. I hope I didn't seem like I was trivializing it. We see all these issues as important.

Post

Nope, didn’t think you were trivializing it! Whoever prioritizes the tickets, however… (kidding).

Post

Does anyone know when you can claim your lifetime key with P4L?

I started the P4L Pro subscription last December and at some point made my choice which meant that I could play 3 instruments without having to do the activate/ deactivate hokey cokey.

I've just renewed and I have my claimed instrument shown but it seems I'm unable to claim another key yet?
Pastoral, Kosmiche, Ambient Music https://markgriffiths.bandcamp.com/
Experimental Music https://markdaltongriffiths.bandcamp.com/

Post

Just managed to re-create ReBirth 338 inside Galaxias :-)
Shame can not to use it in my DAW… :-(

Post

Atlatnesiti wrote: Tue Dec 05, 2023 3:57 am Just managed to re-create ReBirth 338 inside Galaxias :-)
Shame can not to use it in my DAW… :-(
I’ve got lifetime keys for the 303, 808 and 909, but have way more fun with the D16 versions, the new Nepheton 2 808 Clone just dropped and comes with a load of great kits and patterns out the gate. If you do want authenticity you can pipe the MIDI through to the Roland versions eventually anyway.

Are you safe?
"For now… a bit like a fish on the floor"
https://tidal.com/artist/33798849

Post

I would have bought Zenology if it was on sale but it never is. I just bought 28 Arturia plugins for $49. :)

Post Reply

Return to “Instruments”