Hi, I did to try to install your gossiper.lv2 and tetr4-switch.lv2 folders in my Dwarf, unfortunately I get the message “Error adding effect” when I drag them on the PB…
The compiled version that is present on the GitHub actually isn’t the version that I am using over my Dwarf. I don’t know, maybe the docker build image that I used to compile changed something .
My Dwarf has some problem that I can’t connect it with my laptop over USB and the Bluetooth is also quite unstable too, so I can’t check the compiled version. But, I made a backup of the plugins and I will share with you tomorrow.
Just a question, is your dwarf using a version 1.13? The popup API needs it.
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 change state as usual AND with midi ?
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 don’t know any plugin doing this but the Looperlative LP3s. If not giving the source code for this maybe @looperlative could help with this ?
(changing the text of a popup message)
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?
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.
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
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.
Wow! This is a pedalboard with a lot of advanced techniques. I’ll waiting for the description!
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.
Oh !!! Sorry, this is exactly what I was expecting ! It’s perfect ! Thanks !
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 ?
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…
I understood. On the Chocolate forum topic, I remember that someone wrote a workaround to do this using other plugins. Check this part:
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
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
So my hope reports to the solution proposed here… one day :