Hi there
We are using internally TWO in this project: Proof Of Performance , it is useful for rehearsals. We record performances data and then play it back in Two streaming to Unreal. Thanks for making this possible.
We are encountering a couple of challenges though.
when creating a new MIDI namespace, it is not prepopulated like the default one. I dont seem to be able to get input into this created namespace. So I create two MIDI addresses, both with the default midi namespace but different input device in different midi channels.
Hi VanTA, welcome to the forum, awesome to see you’re using TWO for this project!
Indeed that’s how I imagined the recording and playback to be used, and how I’ve mainly used it myself. For rehearsing and testing with complex setups where you can’t keep all OSC data going all the time.
I have to confess I’ve not used the MIDI features of TWO nearly as much as the OSC functionality - which is why there may be a few more issues with it.
But I’ve been able to reproduce the bug you describe, and I can confirm TWO is definitely NOT behaving like it should!
I’ll fix it ASAP, and post here as soon as I have.
Oh, with some more testing, I found another workaround, and with it a very good indication of where the bug is:
If you set the devices and ports, save your project, close TWO, start it again, and open the saved project, it will correctly listen to the separate device and port pairs.
Here’s the separate tracks from Ableton working well over loopmidi, with TWO:
Ok Cool!
That seems to be working. Happy that it helped find the bug.
Is it also possible to use two Addresses with the same Namespace and the same device but different Midi channel? we were getting duplicates in that config as well.
Even better would be an address to be able to listen/record different MIDI channels.
Sure, thanks. The file you sent works.
The default midi namespace is already fully populated and that is why we use it. Creating a new one means adding each individual node manually, for notes is not an issue but CC is since theres 127.
Something like this would be nice:
Namespaces tab, click ‘New…’
‘MIDI Namespace’ button in the popup window could open a new pop up window with:
‘Copy nodes from:’ and a list of existing MIDI namespaces to select (including the default one).
That would save a lot of time, which in live environments is crucial.
Probably for OSC namespaces this would be useful too.
Is it also possible to use two Addresses with the same Namespace and the same device but different Midi channel? we were getting duplicates in that config as well.
That SHOULD work, but with the UI bug we found the saving of the changed settings might be broken.
From my testing the bug is just in the GUI - the changed choices are not properly set internally.
I’ve most likely found what it is - it’s a bug in the ChoicePropertyComponent in JUCE which I introduced when updating the JUCE version I used a (good) while back - I should update again, adapt to the new version.
So if I’ve understood it correctly it should work after the above fix - coming up.
Probably for OSC namespaces this would be useful too.
Since in Address you can use an existing Namespace, if I’ve understood it correctly, there’s the functionality already to re-use nodes if what you want is the full namespace.
Also, with the right-click pop-up there’s the full set of Cut/Copy/Paste commands, so you can create a new root node, and then copy-paste any nodes from existing namespaces into it - that should solve the use-case you describe if I understood it correctly, no?
If you have a moment and can test it I’d love to know if this fixes it also for you.
And if you’re on mac let me know, I’ll make a mac build with the fix ASAP tomorrow and link here.
That’s good news then, thanks again for reporting the bug and for checking that it works for you now! I hope you keep finding TWO useful, and look forward to seeing you back on the forum .
