Roland Cloud

[Septic Underground]

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.

Yeah same here, it is okay on use cpu wise on its own, but going into play and selecting another track (so it is not in live mode) it spikes the whole system like crazy.

Edit:
You guys are talking on the jv1080/xv5080 it seems, but the same behaviour is going on with the v2 updates with for instance the system8 plugin. Thats on my m2ultra AU in Logic / Ventura

[Mogular]

System 8, and all the rest of the v2 plugins are working great for me. Both VST3 and audio unit. Actually, it was System 1, that only recently started working properly for me in the audio unit - prior to the last release it was a clicky poppy mess.
It doesn't make sense, but I wonder whether the different chips are working in different ways. For example, I'm on an M1 Max and Atlatnesiti is on an M2 Pro Mini. I'm using logic on Ventura too.

[J Veronica]

So where's the JX-8P ACB plugout at?

[Examigan]

Is there a list somewhere showing what that was updated and/or fixed? Usually developers will post something either here or on their forum, or their main website.
EDIT: I just found it here: https://www.rolandcloud.com/news/we-ve- ... nstruments

About the file name issue being garbled, can't they just write into the code to abbreviate a preset's name after X amount of characters? That's an easier issue to fix than most others I would think.

[ToddlerTN]

About the file name issue being garbled, can't they just write into the code to abbreviate a preset's name after X amount of characters? That's an easier issue to fix than most others I would think.

What you propose is actually more difficult and still isn’t a proper fix. The real fix is easy – literally just a couple of keystrokes in the code, which I’ll explain momentarily.

If you’re using Roland Cloud to replace a hardware unit you’ve been using for decades, you’ve also probably got lots of bank names memorized already. The workaround of having to rename and abbreviate them all using five characters max and relearn them is counterproductive. Speaking as a software developer myself, this is pure laziness that it hasn’t been fixed already.

To be precise, the bank name display isn’t the problem. The problem is the patch name being written to the wrong location, on top of the bank name. It just needs to be shifted to the right about ten spaces. It’s a simple oversight and could be fixed in mere minutes. The proper alignment is already used in the JV-1080, so just take a look at that and copy it. It’s literally a matter of editing one or two characters in the code. It’s incredibly frustrating that something so simple can go ignored for so long.

Jon at Roland, I know you’ve said several times that this was on the list of things to be fixed. If you have any influence, please tell the developers that this is a super easy one – it’s like scoring a goal on an empty net. There’s no figuring out “how” to resolve this one. It’s a simple alignment issue. Much appreciated if you’re willing to make the case once again.

For reference:

IMG_4701.jpeg

IMG_4702.jpeg

[ToddlerTN]

Double posted – feel free to delete.

[Jon at Roland]

About the file name issue being garbled, can't they just write into the code to abbreviate a preset's name after X amount of characters? That's an easier issue to fix than most others I would think.

What you propose is actually more difficult and still isn’t a proper fix. The real fix is easy – literally just a couple of keystrokes in the code, which I’ll explain momentarily.

If you’re using Roland Cloud to replace a hardware unit you’ve been using for decades, you’ve also probably got lots of bank names memorized already. The workaround of having to rename and abbreviate them all using five characters max and relearn them is counterproductive. Speaking as a software developer myself, this is pure laziness that it hasn’t been fixed already.

To be precise, the bank name display isn’t the problem. The problem is the patch name being written to the wrong location, on top of the bank name. It just needs to be shifted to the right about ten spaces. It’s a simple oversight and could be fixed in mere minutes. The proper alignment is already used in the JV-1080, so just take a look at that and copy it. It’s literally a matter of editing one or two characters in the code. It’s incredibly frustrating that something so simple can go ignored for so long.

Jon at Roland, I know you’ve said several times that this was on the list of things to be fixed. If you have any influence, please tell the developers that this is a super easy one – it’s like scoring a goal on an empty net. There’s no figuring out “how” to resolve this one. It’s a simple alignment issue. Much appreciated if you’re willing to make the case once again.

For reference:
IMG_4701.jpeg
IMG_4702.jpeg

Hey ToddlerTN! I understand your frustration. It has nothing to do with the competence or integrity of the team. Hopefully it will make it into the next round of updates now that compatibility issues have been mostly resolved! I'll continue advocating for it. Understandably, these issues took up the bulk of time for improvements. As always, appreciate the feedback. This won't be the last round of updates for these plugins.

[Mogular]

@Jon at Roland, Just checking that you have noted the fact that the new updates for the JV and XV plugins are not working smoothly on some silicon macs. In my case, trying to play either of the plugins live results in lots of clicks and pops. However, once I've recorded a part, I can easily play it back without any issues.
This differs from all the other plugins that have been uplifted to Apple Silicon support. I am able to play all of them live as well as recorded without issues.
I am on an M1 Max 64gb with the latest version of Ventura and on the latest version of Logic. I am running in native mode.
I've also tested the plug-ins in Ableton Live as well as Komplete Kontrol and I have the same issues.

[vulpes777]

Hi Jon,

a few weeks ago I happened to see a series of posts complaining that the arpeggiator speed knob had been removed in Jupiter 8 version 2 - I think they are somewhere buried in this thread. I did some tests before updating the plugin, because I didn't want to lose such a vital feature, and found out that while indeed the knob in question had been removed from the GUI, the same knob in version 1 of J8 and in Juno60 did not seem to have any actual effect on the arpeggiator speed at all, See my post:

viewtopic.php?p=8715972#p8715972

So my question is: can you confirm that the knob that was supposed to control the arpeggiator speed was non-functional and has been removed?

If so, can I turn this into a (reasonably) urgent feature request to have a fully working control for the arpeggiator speed back into Jupiter 8 and Juno60? The original hardware obviously had it, the Jupiter/Juno-inspired plugins by the competition all have it, it's kind of baffling that in the official recreation of these two legendary synths, the arpeggiators are stuck at master tempo.

Regards,

--
Marco

[WatchTheGuitar]

It’s quite amusing if Roland has a team of devs who can produce remarkably accurate emulations of analog circuitry but can’t change a label’s x position on the XV 5080 or work out how to change the speed of an arp. Makes me wonder if they even have a dedicated team because if they did then surely we’d see continuous improvement on simple to fix features like that. Maybe all their dev work is bought in.

[Aloysius]

[fmr]

Makes me wonder if they even have a dedicated team because if they did then surely we’d see continuous improvement on simple to fix features like that. Maybe all their dev work is bought in.

I don't think they have.

[ChamomileShark]

I'm wondering why the JP4, JP8 and Juno 106 all went to version 2 which included the circuit mod thing, but the Juno 60 didn't. I don't suppose Jon can comment but that seems odd.

[ChamomileShark]

Does anyone remember whether last December's P4L extended into the new year? I probably won't have the funds this year but on 1st Jan 2024 it's a new financial year for me.

[Funkybot's Evil Twin]

I'm wondering why the JP4, JP8 and Juno 106 all went to version 2 which included the circuit mod thing, but the Juno 60 didn't. I don't suppose Jon can comment but that seems odd.

I gotta think they just haven't gotten around to that one yet and it's coming soon.