(11-21-2025, 11:03 AM)XORadmin Wrote: I see the issue and for now I am only passing SC.CV with the merge command (most probably having in mind back then that one would have a faderbox as master which should be used in the nerdseq but also completely passed further). The command also is merged with the fixed 0x31 address which would be used for a first ER-301.
..
So there is no benefit currently using the teletype mode. One basic idea was to make the NerdSEQ varibles available in the Teletype (it could poll them) but since there was never any deeper discussion rather than 'we should do it at some point' this is left open until then.
I could implement the merge of all commands coming from the I2C port (in fact I got this commented out/disabled in my code), but keep in mind here that you would need to take care of the addresses (by definition...thats I2C, a follower acknowledges if it sees it's own address). A follower port can receive it's data only on one port (eg 0x31) and if you would for example receive 0x32 it would be ignored and so also not passed to a ER301 which is set to 0x32. Only 0x31 would be passed to 0x31.
Even though they are theoretical workarounds for it (just listen and acknowledge to every address or to more than one address or just listen but no acknowledge etc..) it would not work out well. It would introduce much more 'why doesn't it work' situations than they are already.
So the way it works with Teletype > ER-301 is that you have to use ports 101-200 when the ER-301 is set to listen to 0x32 instead of 0x31. If the NS is set to 0x31, would it be possible to forward those later ports? Or maybe forwarding all data would be the most "true" implementation of "Out Merge", leaving it up to each module to decide what to do with the data?
See also think link on the ER-301 spec for mapping ports and destinations: https://docs.orthogonaldevices.com/er-30...setup.html
Eg. right now my TT messages directed at the ER-301 did not get properly merged. I believe (not near modular right not to re-confirm) that sending SC.CV on port 101 did not get merged by NS, whereas SC.CV messages on port 1 did get merged (but for some reason only the first pulse was properly merged?).
(11-21-2025, 11:03 AM)XORadmin Wrote: Wiring the teletype/crow to both NerdSEQ and ER-301 while also acting as a leader to the ER-301 (double leader system) can work but it goes wrong once the signals collide = Teletype/Crow and NerdSEQ trying to send something to the ER301 at he same time.
Do you know if collisions occur if the NS and TT are sending messages on separate ports? E.g. I want to use NS to send triggers and CV to trigger and modulate pitch on drum patterns, but I want to use the TT to modulate the mixer for various channels, various effects, etc. So while it's entirely possible (and likely) that two messages will be sent at the same time (especially because TT and NS will be using the same clock) it is impossible for them to be affecting the same port.