Request: Msuperlooper feedback Help

[AisD]

Hello, Im trying to control msuperlooper via OSC so feedback for me is necessary.
At the moment im able to select tracks and loops
im trying to create visual feedback of...

ezgif.com-gif-maker (7).gif

to look something like this...

ezgif.com-gif-maker (5).gif

I would really like to have something like moving parameter by the vst settings like this

ezgif.com-gif-maker (6).gif

Maybe there is easier solution to this?
Perhaps there is a way to have feedback for this moment?
I welcome all your suggestions please help me cure this never ending headache...

[ericzang]

I also welcome the implementation of OSC and/or MIDI feedback for the track/looper states. Helpful for control surface integration and reflecting the state when a Multiparameter makes changes to parameters.

[AisD]

I do not understand why these important functions are not implemented yet...

[MeldaProduction]

Well, MSL has been designed for touch screens, so there's no need for any external MIDI device. Where you can certainly control MSL, but feedback to the device hasn't been implemented and sorry to say, there's no dev time left at all. I'll add it in the todo list as low priority.

[ericzang]

MSL has been designed for touch screens, so there's no need for any external MIDI device.

Thanks for making a note of it on the to do list. I certainly understand the lack of dev time situation and its really amazing all the great developments you do!

The approach of using MSL directly on a touch screen is well appreciated when the hands are available. Just highlighting the known situation where instrumentalists typically prefer to use a midi foot controller (such as Softstep for example, which can change its led colors and character display according to received midi). Also, using a customized touch screen application such as Lemur or Open-Stage-Control (not to be confused with OSC the protocol) is a good way to consolidate status display and control of various aspects of one's performing project and plugins. In these uses, midi and/or OSC feedback from MSL could be quite helpful.

I posted these thoughts in an older thread about possible ways to implement feedback messages:

One idea is that MSL would just send a fixed set of CCs (perhaps based on Launchpad for example). Then it would be up to the user to use a method to convert those CCs to the needed ones (could use Bome, Lemur, midi fx utility plugins, Max, etc). Though this is relatively advanced, I would guess anyone who wants to delve in this far would not be deterred to do that. Another idea, though I don't know if this fits within the Melda framework, is to have an external user editable text file that MSL uses to configure what messages it sends out.

For example, just some obvious parameters off the top of my head that would send out midi:
Track State: Recording, Playing, or "Stopped" (actually mute because of the way the MSL "play" button functions), Overdubbing, Cleared.
Which track selected and which subloop selected.

Thanks very much!

[Dirk Diggler]

By the way I would say this is an industry wide issue, not just Melda. The only way I've seen midi feedback work is with proprietary controllers and software.

Have you ever checked out the Akai APC40MKII? The only software that I've found that actually works with it is Ableton and Resolume. Both apps built specific proprietary hooks into their application.

And I will add I don't use the Akai with MSL, I use a SoftStep2.

Bomes is about the only option, and that's a steep learning curve.

[AisD]

Dirk, there is no way for me to make proper feedback without melda actually implementing it, I will not give up, if i have to i will wait for them to make even more skins, maybe one day they will give up and implement this core function for people that dont give a f about skins and want functionality.
There is this really nice multi tool that is free and it's way better than bome, and it's totally free!! Google Chataigne

[Dirk Diggler]

Good luck I certainly understand the desire.

So how does a breadnut help with feedback?

[noizejoy]

If you have a plugin host that can translate bi-directionally between vst automation and midi messages, this might be doable.

I'm not a regular MSL user, but I just ran a little test with Cubase and its Quick Controls feature; I ended up mapping

MSL Track 1: Gain <==> Touch fader 1 on my Machine Jam hardware controller

The communication worked bi-directionally exactly as desired:

• Moving the hardware fader moved the MSL gain

• Moving the MSL gain in the plugin GUI moved the display on the hardware

[R13]

If you have a plugin host that can translate bi-directionally between vst automation and midi messages, this might be doable.

Exactly. It should be the job of the plugin host rather than the plugin. Ones like Gig Performer can also support turning a automation parameter into an OSC message (and support bi-directional communication).

If MSL had automation parameters that provided the loop progress/position, then Gig Performer could easily send that as OSC (as @AisD is seeking).

[AisD]

Hello again...
Is this getting addressed or I'm writing for no reason?

[Mister36]

Something to address this is still needed for MSL in my opinion.