#82

I picked up an original block and the surface had major issues. I wish ROLI had been a billable client so someone would benefit from my repeated cries for a larger surface, tactile indexing points, softer surfaces, etc. that make the controller nigh unusable.

#83

Glad to see iā€™m not just bitching. I had too much on my plate and was too absorbed in trying to make it work in M4L during the first week that i missed the point regarding the bad sensitivity of the surface. Otherwise i would have send it back.
Btw, any news on the ability to not have to go to the MIDI config to enable bluetooth MIDI each time you boot the computer ?? This makes this thing even less useful. Crappiest piece of gear i ever bought (well, with Push of courseā€¦oh my ! i am bitching again !).

#84

I will admit that I too feel more than a little burned having purchased a first gen block and spent a decent amount of time trying to both work around itā€™s shortcomings on the tactile front and the software front.

I have no intention of purchasing roli products at this point even though I am attracted to what they are producingā€¦

#85

Iā€™m stuck with two of the original lightpad blocks. Iā€™m told the new firmware makes them less awful, but really, I canā€™t see ever plugging them in to confirm that.

Their seaboard line gets better with every iteration, though. Though, I do pine for another octave or two on the Seaboard Block. Or just a 25th key, like the Rise has ā€“ I keep reaching for a high C that isnā€™t there. And Iā€™m not convinced a second unit is the answer, because that creates an unslideable gap in the center of my range, and a point of structural weakness if Iā€™m holding the controller in my lap. But, yeah. Anyone hesitating on the mini layout hasnā€™t considered their intonation on chordsā€¦

Side note: a three octave Seaboard Block would be four and a half lightpad blocks wide. A sideways control block would complete that rectangle, but the arrangement is just awkward enough that I donā€™t think weā€™ll ever see it.

#86

Anyone doing it? I recently acquired a Squarp Hermod module and plugged my Seaboard Block into it. Wonderful things followed, especially with the slide and aftertouch set as separate CV modulations.

#87

Just getting started. Linnstrument + Percussa SSP for me. Need more timeā€¦

#88

Iā€™ve been thinking about trying some of these for a while, specifically for use in my augmented snare setup so I finally bit the bullet and scored a used current gen Lightblock and a ā€œLoopā€ control block.

I donā€™t think Iā€™d use both as itā€™s overkill for the amount of space I have, so I want to prototype some interfaces to see what makes the most sense for mounting on the snare.

They havenā€™t arrived yet, so Iā€™m still just coding-in-the-dark, but thankfully the Max package for it seems pretty robust.

Is anyone using these (with Max) to make some interesting interfaces?

The Lightblock in particular seems to have someā€¦um, pretty gauche implementations, even though it looks like it could be quite powerful.

One thing that does kind of confuse me is the controls blocks (specifically via blocks.multictrl) doesnā€™t expose decoupled LED feedback. You seem to only be able to set on/off/press colors, and set a ā€œtoggle modeā€, where the LEDs are momentary or toggling. That seems mind-blowing that that would be a limitationā€¦

Is there a way around this?

Also, in thinking of a more norns-y future, does anyone know if itā€™s possible to control the LEDs (or other features) via vanilla MIDI and/or sysex? Thereā€™s an SDK for the Blocks, but Iā€™m not great at reading C++.

#89

Hey, I have a couple of the first generation Lightpad Blocks and really liked them. Itā€™s like a touchscreen interface that also allows me tactile feedback of a button (meaning I can rest my finger on a button and push when Iā€™m ready rather than the standard touch screen teacup fingers).

They have a pretty robust JUCE API for it but donā€™t give too much support. Unfortunately they did not expose MIDI feedback last I checked (I had sent them an email about this) BUT the Max integration allows you to do that very easily. In fact, it is quite powerful and customizable if you are a Max person but that means having it connected to a laptop. Iā€™m assuming the Max externals also allow you to get the high resolution that the device puts out whereas the MIDI resolution for CC control can be quite tough to work with on such an expressive interface.

Just watch the battery life on them. They will discharge slowly while not in use so make sure to get them a fresh charge before any shows.

#90

Thanks for the info.

Iā€™m very comfortable with Max, so working in there is ideal for what Iā€™m after (though norns-ing is a different question).

As I said, mine havenā€™t arrived yet so itā€™s possible this is a non-issue and it is possible to control it in a manner like Iā€™m intending (and unlike how the blocks.multictrl UI works), but the Max external doesnā€™t appear to let you set LEDs independently of the output. Again, this is for the control blocks, not the light block. The light blocks appear to have more robust options available.

It also occurred to me that it would be possible to have monome-esque (matrix-based) control over the individual LEDs on a light block by using some serialosc->jitter matrix stuff (the BEAP package has some of that). Donā€™t know if itā€™s possible to ā€œlayerā€ that with input-based controls, but can still be a more reasonable way of working with the feedback programmatically.

#91

If you donā€™t mind a slightly related question,
is it possible in some way that the computer (mac os) remembers the block as a MIDI bluetooth device ?
Having to reset it at every startup is really annoying.

#92

So they finally arrived and I have to say Iā€™m pretty unimpressed.

It feels like a slightly better engineered KMI product in that itā€™s pretty good, but thatā€™s about it. It lacks a clear sense of vision and/or refinement.

Iā€™m baffled by how hard you have to press the buttons on the smaller ā€œcontrolā€ block, as it makes it borderline uselessā€¦ not to mention I was really confused when I discovered that the smaller block has no USB-C port, so it functions only wirelessly (or when ā€œdockedā€ to a Lightblock).

The Lightblock, when connected via a cable, isnā€™t too bad. Itā€™s a large area, the feel isnā€™t terrible, and offers me more room/control than the Dicers Iā€™m presently using. Iā€™ll see if I can come up with a suitably sturdy 3d printed mount so I can mount it on my snare. Iā€™ll have to come up with something a bit sturdier than what I have no as the Lightblock is fairly heavy (for its size) and bigger than the dicer, so Iā€™d want to make sure it doesnā€™t wobble too much on the snare.

Itā€™s a shame no one seems to make a compact controller that isnā€™t dogshitā€¦

6 Likes
#93

Curious, what would you like to see in a compact controller, what features would it have, how much would it cost?

#94

To be honest, pretty low standards here. Something with around 8ish buttons, smaller than a phone (or same size), wired would be great, though I could see bluetooth over midi being good for some people. Price point, in the ā€œcheap controllerā€ category (circa or below $100).

Something like that would be perfect as a simple ā€œremoteā€-type controller for various projects. As often all Iā€™ll need is a couple buttons to do what I want.

#95

Nice, thanks for the context, when you say buttons, do you mean MPE or just simple buttons, arcade style? something more tactile like buttons/piezo under rubber so you could be a little more rough with it?

#96

I was thinking, in a generic sense, silicone-style rubbery ā€œpadsā€, not even velocity sensitive. Not personally a big fan of arcade-style buttons (in controllers), but I guess some people really like them.

Iā€™m aiming to make a DIY thing (based on the Bela TRILL stuff) which will be more complex than that (capacitive/pressure sensitive, with decoupled LED feedback etcā€¦).

2 Likes
#97

Kinda makes me think of the guitar wing (I consider it for myself because itā€™d be tremendously helpful for live use, although I donā€™t find it especially pretty to look at) http://lividinstruments.com/wp-content/uploads/2014/04/guitarWing_features.jpg But I think the form factor is still too big anyway.

#98

Are people here mostly using Max for configuring their Lightpads from patch to patch?

Been rediscovering mine and now they are part of my base live setup again. I actually like the firmness on the Lightpad as they can work like real buttons (so I can rest my hand on them while performing before pushing) which is what I hate about almost all touch controllers. But it sucks that the LEDs arenā€™t addressable and configurable via MIDI or some other means. My solution has been to just stick with a basic 4 fader layout with buttons on top and never change it. But feedback would be so nice so I could recall settings.

I made a Lightpad OSC transmitter/receiver a while back with JUCE that allowed me to address the LEDs via OSC but then one of their firmware upgrades broke it and I didnā€™t bother trying to keep up with the updates. Thinking about diving back into the Blocks SDK to try to figure out a way to address the LEDs from SuperCollider though and maybe just never update the firmware again.

#99

They also make the MINIM, which I was excited about when it wa announced, but when I saw pics and stuff, itā€™s friggin huge!

#100

Yeah, itā€™s down to details but I agree the final form factor is kind of only halfway through in the in end. (Itā€™s still a clever controller though)

#101

I made a simple 5x5 pad decoupled two-way MIDI control script for it, which works standalone (works great with norns!). Iā€™m on holiday at the moment so donā€™t have access to it, but when I get back home in two weeks Iā€™ll tweak it (maybe make it in a few resolutions as well) and upload it.

1 Like