Gossiper - Plugin to say what is happening when you are looking it

[plutek]

wow… beautiful!

i’ve gotta study this board, and look at Gossiper some more - this seems to imply that it serves more than just a notification or visual feedback function?

[Rom]

I’ll make a post on this tread when I can :

Show your advanced pedalboard techniques

Hi all, I would like to start a new thread focused on where Mod Devices (and Desktop version too) shine. I am talking about pedalboards. But specifically here, it is not supposed to talk about sound, but routing, CV, MIDI, plugins, etc. The ideia is to share here our gig problems, the creative solutions applied, and problems that we still have. So we can inspire ourself learning different techniques for different problems that sometimes weself created. This post is inspired by the @zwabo pedal…

(Not sure I’ll be as precise and clear as @SrMouraSilva !!!)

[jon]

hey @SrMouraSilva I just tried the Gossiper and it seems quite handy indeed.
It would be indeed super cool if you could edit the text of the popup as @fxsimone suggested (and this may be the first time that I interact in this forum 100% as a MOD user only ). It would be awesome instead of reading there the number of the footswitch (for example), if we could write the text. My goal here would be to write the name of the effect that I’m turning on/off so more than knowing the state of the MIDI footswitch I would know also what I assigned it.

[SrMouraSilva]

Hello, @Rom.

Thanks for your feedback

@Rom

if you find a way to change the popup message, would it be possible to assign a midi expression pedal to the Pot 1 and then showing the value of this pot changing in a popup ?
(as I asked here Expression pedal : showing percentage on the screen)

I am sorry, I am quite confusing because there is more than a year that I implemented it, but if you assign the midi expression for Pot 1, the behavior isn’t that you are expecting?

There is the source line of code that is responsible for defining the text value for Pot’s

SrMouraSilva/plugins-lv2/blob/master/plugins/src/lv2/gossiper/lv2-hmi-gossiper.c#L124

@Rom

could a footswitch trigger be triggered by a physical footswitch AND by another trigger inside the plugin ? (and this other internal trigger footswitch 1 could be assigned with midi)
So, in this case, the physical footswith would

You say there would be more than one parameter assignable for the same CV? So I suppose yes if I duplicate the “Footswitch” parameter.

Now if you are requesting to receive a specific Midi message from an Midi input, this would be great, but I don’t know how to develop using midi.

@Rom

I’ll make a post on this tread when I can :

Wow! This is a pedalboard with a lot of advanced techniques. I’ll waiting for the description!

@jon

My goal here would be to write the name of the effect that I’m turning on/off so more than knowing the state of the MIDI footswitch I would know also what I assigned it.

I have the same goal! I just don’t know yet how to do it . A help for looperative or someone else from community would be great

[falkTX]

@SrMouraSilva

I have the same goal! I just don’t know yet how to do it . A help for looperative or someone else from community would be great

you need to have atom ports with patch:Message type, then declare a few patch:writable properties of type atom:String.
basically the same way plugins deal with files, but instead of path type it is string type.

see LV2 Parameters as Strings - #3 by falkTX for a few links