Unfiltered Audio Lion

[aMUSEd]

I have a Block M, connecting the Roli controller module, just changes the Block M into an XY pad, and that kinda sucks because it wont play notes. Is Lion MPE enabled otherwise without the module in Lion?

Yep! The Block Modulator is only needed if you want to use the Block as a modulation source. To use MPE, just make sure that you have the MIDI mode set to MPE (bottom left). To add MPE modulation, the MIDI Input modulator that is present on every LION patch has MPE outputs.

For me the Lightpad Block support almost never picks up my Block no matter what host I use. Or if it does the connection is erratic and often gets lost between switching patches.

[D Halgren]

Can you please flag it with PA's support. They are saying they can't reproduce it, and acting like they haven't heard of it.

PA support are worse than useless when it comes to fixing anything. I've been having issues with the VST3 versions of several of their plugins not displaying correctly. They confirmed they could reproduce the bug and would sort it. To date they have mailed me 16 times saying the bug was fixed. It's not fixed .. and now they are telling me the issue is my DAW (Live 10) not their plugins.

Man that sux I hope it works out for you. Crossing my fingers that UA doesn't drop the ball on this. PA totally closed my ticket once they said UA knew about the problem, but it ain't fixed

[thecontrolcentre]

Man that sux I hope it works out for you. Crossing my fingers that UA doesn't drop the ball on this. PA totally closed my ticket once they said UA knew about the problem, but it ain't fixed

It's not gonna work out (for me) as PA have said it's not their problem. UA on the other hand are much more on the ball (so far) ... last year they were putting out beta fixes months before PA got around to uploading them. It seems once PA have your cash they're not really interested any more.

[jzero]

I wonder if the filters in the effects row could have Osc 1 Osc 2 checkboxes. It would be great to apply different filters for each oscillator.

[WasteLand]

I have a Block M, connecting the Roli controller module, just changes the Block M into an XY pad, and that kinda sucks because it wont play notes. Is Lion MPE enabled otherwise without the module in Lion?

Yep! The Block Modulator is only needed if you want to use the Block as a modulation source. To use MPE, just make sure that you have the MIDI mode set to MPE (bottom left). To add MPE modulation, the MIDI Input modulator that is present on every LION patch has MPE outputs.

For me the Lightpad Block support almost never picks up my Block no matter what host I use. Or if it does the connection is erratic and often gets lost between switching patches.

still a problem, i believe i only managed to get to work in bitwig studio (now on 3.3.1).

i made a support ticket, you can only do it via PA, but thé Lizard, says that they get those tickets.

so i hope it will be solved. it isn't recorded via midi, but of course you can perform live, record the output. still a great feature, a pity, that it almost never works in cubase, reaper (didn't try live 11 beta yet, have pre-ordered live 11 suite upgrade). sometimes it does work strangely in cubase or reaper...

indeed connection is erratic, only not in bitwig, bút only when it is choosen as a generic controller (i have attached my seabord block seperately from my 2 lightpad M blocks, i have 2 USB 2.0 hubs, fully loaded.. not enough power for 3, via DNA.)

o well still a great synth. LION, also as a MPE synth, or it better it is one of those synths that performs at its best wíth MPE, in my experience. like generate (MPE was a big part of the development, and the overall synth performance soundwise), or yes cypher 2 (but the last one isn't strange...).

[aMUSEd]

I’ve tried it in Bitwig, Logic and Waveform but most times it’s not picked up the Block at all (the VST3 also crashes a lot in Waveform and the VST gui seems to not reopen when closed)

[WasteLand]

I’ve tried it in Bitwig, Logic and Waveform but most times it’s not picked up the Block at all (the VST3 also crashes a lot in Waveform and the VST gui seems to not reopen when closed)

we have discussed this, you are on MAC i believe? o yes, mac, because of logic. i am on windows, perhaps that makes a difference, at least for bitwig.

waveform OEM, i had, or i have, but not installed anymore, there sandboxing is somewhat problematic (or perhaps not that problematic, there is no VST3 plugin that is programmed at the right protocol, since, yes, the SDK is a mess, but also, BESIDE THE POINT!).

waveform has more problems with GUI's, for instance softube modular i thought, o yes, all softube plugins.. and another plugin, can be a settings problem (as in bitwig sometimes, sandboxing settings).

i hope they have read it, my support ticket... about connecting to a block, a lightpad M block.

it is a pity that you can't program the normal XYZ pad/modulator (or is that one only XY, yes only XY), or i am missing something obvious. no i am not.

you can assign CC to macro's?? no. only parameters, via the DAW, i believe, so indirectly to a hardware midi controller.

it is nice to have the roli block module. but in way, the XYZ mode (or app as roli calls it), does the same, yes unfiltered audio gives your more modes within the app the load into the lightpad M block.

i hope thelizard will read this. a small thing, but for effects, and yes LION! a great addition to the expressive capabilities. (and i own all UA stuff, vst, and some for VM.)

[Tj Shredder]

I’ve tried it in Bitwig, Logic and Waveform but most times it’s not picked up the Block at all (the VST3 also crashes a lot in Waveform and the VST gui seems to not reopen when closed)

I recently had a similar problem with a brand new Touché controller (magnitudes more fun than a Roli block...).
The culprit was a usb hub. As soon I connected it directly all was fine. And even just the opposite side of the hub worked (7-port internally cascaded).
Do you run it through a hub???

[aMUSEd]

Yes - although its a thunderbolt to usb hub which i would have thought was ok

[thelizard]

We're compiling new versions of everything using JUCE 6 so that we can roll out Apple Silicon support (and so far we haven't run into any issues regarding that). In the process, a lot of the Blocks library stuff was changed in JUCE 6. I'm hoping that these changes will fix the Blocks experience, but that comes later on my QA checklist.

I'm not really sure how to go about this now that ROLI now longer owns JUCE, and the Blocks API that is built into JUCE is the only real communication method.

At the very least, I'll start by posting the Lightpad sketch that we send to the Block here. That way, you can still use our app, but maybe use it to send MIDI CCs instead of communicating directly with the plugin.

[WasteLand]

We're compiling new versions of everything using JUCE 6 so that we can roll out Apple Silicon support (and so far we haven't run into any issues regarding that). In the process, a lot of the Blocks library stuff was changed in JUCE 6. I'm hoping that these changes will fix the Blocks experience, but that comes later on my QA checklist.

I'm not really sure how to go about this now that ROLI now longer owns JUCE, and the Blocks API that is built into JUCE is the only real communication method.

At the very least, I'll start by posting the Lightpad sketch that we send to the Block here. That way, you can still use our app, but maybe use it to send MIDI CCs instead of communicating directly with the plugin.

this what also thought. it is nice that UA loads the app itself, but why not a seperate app, that you can load yourself (1 block is already connected with a UA plugin..).

this app that we can download now, will it send the proper MIDI CCs to UA plugins???
or how to use it with UA plugins, in the same way as the roli block modulator.

roli has still is own app SDK of course, for JUCE. i am not a developer.

if you can get it to work, to connect it would be great. but for instance: softube modular, an example, the module, the roli module "expects" a roli seaboard rise. but! in the XYZ mode, built in the dashboard, or better the roli rise controller app, mimics the XY pad (plus pressure, o wow difficult, MPE uses als XYZ.. i just mean non MPE, CC messages), and the 3 sliders.
but you can program the sensel morph to do the same (i guess, only have roli stuff..).

no: i am babbling!

1. the blocks experience, i get it, it is not a priority
2. the roli dashboard contains already a XYZ pad.
3. you can indeed make your app available, as of now, to load via dashboard.
4. how will it communicate with UA plugins? no midi learn (as far as i know, i never use it, i do parameter control..).

perhaps the best solution: the app as seperate download, i assume, or is the connection very direct? me thinks. or still a midi layer? o well.. (yes of course EDIT is this: midi CC it sends... always that strange... parameter/midi/values/gggrr. no! no grrr! that is how synths work, a midi domain and a component domain..)

o well.. (2 times)

sorry for my confusing post, o well, you do JUCE, so... this post you can turn in to schematic for a nonlinear almost chaotic oscillator.

o about: usb connection: i first started to use roli seabord block and a lightpad M block on my laptop, with no hub (enough connections..). to start, then it went to my studio, indeed via hubs..

strangest thing, i must recheck it, it works in bitwig, if the lightpad block(s) is connected seperately and it must be a generic controller (switching between them isn't that bad).

[c_voltage]

Master ADSR wrong behavior during Quality at more than 1x mode still not fixed yet (v114), first report about issue was almost year ago, in february.

[simon.a.billington]

Can you please flag it with PA's support. They are saying they can't reproduce it, and acting like they haven't heard of it.

PA support are worse than useless when it comes to fixing anything. I've been having issues with the VST3 versions of several of their plugins not displaying correctly. They confirmed they could reproduce the bug and would sort it. To date they have mailed me 16 times saying the bug was fixed. It's not fixed .. and now they are telling me the issue is my DAW (Live 10) not their plugins.

Well it’s hard to fix a problem you can’t reproduce. That’s also why intermittent problems are hard to get sorted, first they’re there, now they’re not.

Many times it works out to be something unique about the user system, like some kind of file corruption or some other service ruining in the background that messes with it, or even cracks. These are the kind of things every dev finds hard to deal with.

It’s why things can take time. Even if they find a solution that isn’t a simple bug fix they still have to run tests to make sure it’s not going to screw with everyone else creating a “frying pan to fire” type of scenario.

[D Halgren]

Can you please flag it with PA's support. They are saying they can't reproduce it, and acting like they haven't heard of it.

PA support are worse than useless when it comes to fixing anything. I've been having issues with the VST3 versions of several of their plugins not displaying correctly. They confirmed they could reproduce the bug and would sort it. To date they have mailed me 16 times saying the bug was fixed. It's not fixed .. and now they are telling me the issue is my DAW (Live 10) not their plugins.

Well it’s hard to fix a problem you can’t reproduce. That’s also why intermittent problems are hard to get sorted, first they’re there, now they’re not.

Many times it works out to be something unique about the user system, like some kind of file corruption or some other service ruining in the background that messes with it, or even cracks. These are the kind of things every dev finds hard to deal with.

It’s why things can take time. Even if they find a solution that isn’t a simple bug fix they still have to run tests to make sure it’s not going to screw with everyone else creating a “frying pan to fire” type of scenario.

I was told by PA that UA are aware of the problem, and have a fix, but there hasn't been an update as of yet. I sent video of the problem in. They closed my ticket even though the problem is still there.

[simon.a.billington]

Can you please flag it with PA's support. They are saying they can't reproduce it, and acting like they haven't heard of it.

PA support are worse than useless when it comes to fixing anything. I've been having issues with the VST3 versions of several of their plugins not displaying correctly. They confirmed they could reproduce the bug and would sort it. To date they have mailed me 16 times saying the bug was fixed. It's not fixed .. and now they are telling me the issue is my DAW (Live 10) not their plugins.

Well it’s hard to fix a problem you can’t reproduce. That’s also why intermittent problems are hard to get sorted, first they’re there, now they’re not.

Many times it works out to be something unique about the user system, like some kind of file corruption or some other service ruining in the background that messes with it, or even cracks. These are the kind of things every dev finds hard to deal with.

It’s why things can take time. Even if they find a solution that isn’t a simple bug fix they still have to run tests to make sure it’s not going to screw with everyone else creating a “frying pan to fire” type of scenario.

I was told by PA that UA are aware of the problem, and have a fix, but there hasn't been an update as of yet. I sent video of the problem in. They closed my ticket even though the problem is still there.

It just means they have a solution but haven’t published it yet, quite possibly because it’s still in Beta phase and we’ve just had Xmas. COVID could be causing a few delays too. Or maybe they have a few fixes for the same plugin and are waiting on those so they can publish it all together.

There’s plenty of reasons really. What’s important here is the patience thing.