hi Victor!
agreed! @infinitedigits had been cooking up a method to “batch add” initializations for library files like Passthrough to all scripts in a code
folder. seems like it’d help with this situation, where a specific utility is globally useful to a subset of users. Zack, any leads / thoughts?
but also, just to confirm we’re following the same procedure, if you have Passthrough already installed through maiden then you only need to copy/paste these two lines right under the script’s header:
local passthru = include 'passthrough/lib/passthrough'
passthru.init()
but if you’re using a ton of scripts that get updated a lot, i get that it’s a non-ideal. it might also be good to bump threads for your favorite scripts and ask the authors to include this in theirs:
if util.file_exists(_path.code.."passthrough") then
local passthru = include 'passthrough/lib/passthrough'
passthru.init()
end
that code will check to see if Passthrough’s installed and if so, initialize it.
i agree that robust MIDI traffic management would be awesome, i think it just opens up a lot of design considerations, which might be nice to gather some feedback on:
- i don’t use a lot of interconnected MIDI devices, but is a standard use case having a MIDI keyboard connected to norns that you’d also like to route to a non-computer device?
- what other devices or programs come to mind when you think of this functionality? eg. is the way that Ableton Live handles MIDI routing the standard we’re discussing? or the MIDI thru of a Digitakt?
- since the
DEVICES > MIDI
menu can manage many devices (currently 4, soon 16), would ideal functionality include:
- the ability to direct MIDI traffic from one device to many?
- the ability to assign each connected device a passthrough destination?
since the code itself is already done, technically not difficult. @nattog might want to take a PR on as the library’s author. it sounds like @ngwese also has something brewing that might fit the bill, as well 