I just have a problem with an LV2 output control port. Output + Trigger is not working as i expect. I can set the value, but the host never reset it, at least i do not receive the reset value in the JavaScript side. Anybody knows if it is supposed to work, or if it is a bug?
output triggers are to be reset on plugin’s side, not host side
Oh i see. Thanks.
But in this case i should receive 2 times the change event in the JavaScript side if 2 consecutive run have to output the same value. I have to check but feel like i have to cheat around.
I did some tests. I feel like the Mod do not manage well the triggered output. It is difficult to check, i don’t know hosts supporting that. But i think, as there is, i guess a filter to reduce the amount of events in the JavaScript world, it is mostly impossible to receive the right output trigger. It is mostly always zero.
For triggered output, the JavaScript change event callback should not receive the last value of the port, but at least, the last value during the integration period which is not the default value (else the default value). It is still not perfect, but can be much better.
Do you know the way it behave? or where is the code?
I still can change the way i manage this thing in the plugin, from event based, to state based. What do you think?
This looks great for some debugging and figuring out which messages are being received!
When can we expect it in Beta? 
Btw managed to build and install using mod-plugin-builder and seems to be working great.
One feature request though: add a mode that allows for actually seeing what musical notes or GM-drums are being sent. This could be useful when one is playing with the sequencers.
1 Like
Hey @dreamer, I just confirmed with the team and the MIDI display may be pushed to the Beta plugins really soon (probably today).
2 Likes
Its work on MOD DUO?
Correct. You can use this plugin on the DUO as well.
See the Beta section if you want to try it.
1 Like
I use that plugin a lot, so I guess it’s time to say “thanks” now.
2 Likes
Same here !
It may be time to put get it out of the beta section too ?
4 Likes
I was able to use it on DUO, it helped me to know that I was getting the right message to my other devices, however I still have a problem. I was going to answer here reporting and explaining everything, but I decided to open a topic just for this because they address other details. if you can check there:
2 Likes
Thanks, why it’s still in beta? MIDI channels are numbered from 0 to 15, and from 1 to 16 in others MIDI plugins, now that I have understood this, it’s very helpfull for a beginner like me to understand how MIDI is working.
2 Likes
good question, for me I dont see a special reason why to keep it in beta.
it was made using and older style of delivering messages, but still works.
the midi channel numbering I agree can be confusing and should be adapted. on the user-facing level, channels should begin at 1. code-wise if it uses 1 or 0 as starting point doesnt really matter as long as it works.
@val did you try the trigger behaviour under the latest release? I recall doing some fixing related to this a while ago.
4 Likes
Me too. Thanks.
This plugin is a must have when we use midi : MIDI display - MOD Audio
But it is still in Beta since many years, though everything works fine. Shouldn’t it move to the normal store ?
2 Likes
yes. indeed. 
Please don’t create duplicate topics. Lets keep things centralized 
I think it comes down to the questions that @falkTX asked above. Other than that it seems good to me too.
2 Likes
Of course ! Sorry, I didnt found this one back…
1 Like
I built @val’s midi-display for MOD Desktop (Windows) using @falkTX’s PawPaw.
I tried contacting @val to ask if I could share the file, but I haven’t received a response.
If anyone believes I shouldn’t share it, please let me know and I will remove the file.
https://github.com/Inqb8tr-jp/midi-display.lv2/releases/download/v0.8/midi-display-windows.zip
2 Likes