IAC midi input device in Element plugin version

[steveschow]

The graph modules for midi devices, such as being able to route an IAC device directly into the graph via a node...only seems to work in the Standalone version of Kushview...doesn't work in any of the plugin versions that I tried. This would be very helpful. If not, then remove it from the plugin version to avoid confusion.

[mfisher31]

Ahhh yes, good idea. It's not really possible for it to be consistent. The issue (i think) are conflicts between host and Element when both are accessing the same MIDI device.

Off subject but I've been working hard getting a User manual together... including details on how scripting works in Element.
https://element.readthedocs.io/en/latest/scripting/overview.html

The API is still very slim. I really want the foundation of it all solid before really adding tons of examples and expanding it. Good news about that is I'm happy with it now and ready for the next phase.... which is going over suggestions from you and others on what to implement!

[steveschow]

Hey great to hear. I'm in the middle of a big renovation and move so it may be a while before I can really try some Lua in Element, but I'll get to it eventually..but yea...any docs will be helpful.

Regarding the API, I think simple is good to start. There is a lot of potential to get crazy with it so that with LUA we can someday even make UI's that interface with various objects in Element, etc..but I would just suggest at first, at least regarding midi, which is my primary interest...just super simple, but the thing that is the most difficult in scripters such as LuaProtoPlug, PlugNScript and others...is that there is currently no way to schedule midi events in the future with them. LogicPro Scripter is the only one that provides an easy way to do that...and that greatly opens up things to do with it...whereas the other ones are using for doing simple filter, but you run out of interesting things to do with that pretty quickly.

Regarding the IAC...I can't remember why I started this ticket...but I guess from inside the Plugin Version of Element it would be better to have a dedicated module that can connect to outside midi devices directly, including IAC), but most people will not actually do that. I have used that feature in PlogueBidule on occasion though.

[mfisher31]

I'm so behind on everything. I'll have a look at using IAC in the plugin version. I've had people say it works and others say it doesn't.

[mfisher31]

see #1000 (issue number 1000 exactly... neat!)

[RedStoneRanger]

Under windows it looks like its the way the host opens a device. No idea how that works but there are Apps that lock the device and others (Like Bome MT or loopMidi) don't.
My two cents to Bidule if it comes to Midi & OSC management: I use it intensively but the way Bidule manages communication ressources is a nightmare. In BD you can only insert a MIDI device once and then it is no longer available to other instances. OSC receivers often fail to start after plug-in load and have to be activated manually.
This is why I came to Element. In one particular use case I use it as a wrapper for Bidule and let it do the device routing, which is excellent by the way.

[steveschow]

windows is notorious for not having the greatest multi-client support in general. I have used this feature on PlagueBidule numerous times without issue. DDFM MetaPlugin also has this capability. True that it might be easier, cleaner, etc. on MacOS due to CoreMidi while Windows is kind of a crap shoot, I can't comment more about windows.

Its not the kind of thing that is often needed in a plugin, and sometimes DAW's provide this capability, but in some cases the DAW doesn't and then it becomes invaluable to be able to do it from inside a plugin such as Element or the others I mentioned.

[RedStoneRanger]

Got your point. Windows is notorious for not having a lot of things that would make my life easier. I don't want to talk about everything Multimedia here. But again, I think I realy stress these things a bit because in my current project, I need 100+ instances of these gizmos.
MetaPlugin is waiting in my backyard but I somehow trust Element even if it didn't jump the 100+ hurdle :)
BTW: I am working in Davinci Resolve, which is not a typical DAW but an LNE with some kind of inbuilt DAW and it provides zero capabilities. This is why I am doing this project.

[mfisher31]

Alright, I went to go "re-enable" those. They're already on. So I guess check em' out and let me know. The code for the node's themselves has been updated working out kinks in general. So they should be better than the pre 1.0 stuff.