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

[Rom]

@SrMouraSilva

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?

Oh !!! Sorry, this is exactly what I was expecting ! It’s perfect ! Thanks !

@SrMouraSilva

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

Yes, I think that’s what I would like.
For example a midi controller footswitch sends multiple triggers :

• crunch OFF
• tremolo ON
• delay send ON

But I want to have a footswitch on my Dwarf to do the Delay send ON, that reflect the state of the actual state of the effect, when it is triggered with the midi controller or with the Dwarf’s footswitch.

---

Actually the Assign to notfy1 doesn’t do anything when pressed ON or OFF, could it trigger the Footswitch 1 ?

[SrMouraSilva]

@Rom

Actually the Assign to notfy1 doesn’t do anything when pressed ON or OFF, could it trigger the Footswitch 1 ?

It is necessary to have a parameter visible into the screen for raising notification/showing modal alert. If there isn’t any visible, Gossiper can’t gossip you. It is a limitation of Mod Dwarf. So it’s why I implemented the Assign to notify parameters, they appears to be dumb parameters (because bottle them on or off doesn’t change anything) but without them, isn’t possible to see the messages…

@Rom

But I want to have a footswitch on my Dwarf to do the Delay send ON, that reflect the state of the actual state of the effect, when it is triggered with the midi controller or with the Dwarf’s footswitch.

I understood. On the Chocolate forum topic, I remember that someone wrote a workaround to do this using other plugins. Check this part:

@SrMouraSilva

Control an effect with the MIDI and the Mod Dwarf footswitch

[Rom]

@SrMouraSilva

It is necessary to have a parameter visible into the screen for raising notification/showing modal alert. If there isn’t any visible, Gossiper can’t gossip you. It is a limitation of Mod Dwarf. So it’s why I implemented the Assign to notify parameters, they appears to be dumb parameters (because bottle them on or off doesn’t change anything) but without them, isn’t possible to see the messages…

Yep, I get that, but does it mean this parameter should be useless ? I was hoping it can do both :

• being there so you can have the messages
• being a useful swith

@SrMouraSilva

I understood. On the Chocolate forum topic, I remember that someone wrote a workaround to do this using other plugins. Check this part:

I don’t find it… I found this workaround to have both controls on the Dwarf and the midi controller, but I think with a mindi + feedback loop it’s a lot easier

MIDI "Chocolate" controller with the Mod Dwarf, an introduction

Just got myself a Chocolate, too. Nice little toy and quite nice for that ridicoulously low price. I have an addition to the great instructions by @SrMouraSilva : A little change in the section “Control an effect with the MIDI and the Mod Dwarf Footswitch” makes it possible to use both controls independently: Set the CV logic Operator to “XOR” instead of “OR”. (This means output is “on” only when exactly one of the two “Control to CV” is on and the other is off, and output is “off” when bot…

So my hope reports to the solution proposed here… one day :

Midi mapping parameters: Bi Directional?

Hi @jon, I have a proof of concept running on linux. It only requires changes to mod-host, all changes are in effects.c. Basically: Adds jack midi output port to mod-host Add int8_t midiOutValue to `MIDI_CC_T’. This will hold the 7 bit normalised param value or -1 for no change. Change effects_init() to set all g_midi_cc_list[].midiOutValue to -1 (no value) Change effects_set_parameter() to check g_midi_cc_list[] and if MIDI_CC_T matches parameter set midiOutValue to correct CC value. Chan…

Thanks again, and a lot !!!