EsotericLabs Posted October 1, 2013 Report Share Posted October 1, 2013 Hello dear community, if I might ask about the following: My project is a Seq V4 and a midio128 in one enclosure. The SEQ V4 does, well, midi sequencing, the midio 128 drives a DB50xg sound card (code see ) plus some interfacing with guitar foot switches, volume / expression pedals etc and has a SCS. The two cores need to talk back to one another. The sequencer will have the soundboard as its default output, and the midio needs to send back switch and expression pedal signals to the seq v4 core. I cross-wired J5B.A6 and J5B.A7 for midi in/out 3, but this creates midi feedback: the cores lock up in sending each other the same messages over and over again. The routers are not yet set up at all, so i guess it is not in there. I read up on mbnet, but i don't understand it and it will require extra programming in the seq v4 code, which maxed out the capacities of the core already. I'd really appreciate your debugging tips and suggestions. And by the way, if anyone could recommend a good audio signal quality DPDT 5V relay that latches on pulses, i'd really appreciate that as well. The midio128 will become a guitar fx looper/ switcher then with an extra DOUT. Thanks for your ideas! Quote Link to comment Share on other sites More sharing options...
TK. Posted October 1, 2013 Report Share Posted October 1, 2013 Hi, you did it right - the most simple way to link two cores is a common MIDI IO crosslink, and MIDI3 was a good choice. But I'm surprised that you get a feedback. Could you please enter the "router" command in both applications, and copy&paste the terminal output into this posting? Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted October 1, 2013 Author Report Share Posted October 1, 2013 Thank you TK, you're very supportive this is the router output from the SEQ V4 application [13234.128] MIDI Router Nodes (change with 'set router <node> <in-port> <channel> <out-port> <channel>) [13234.129] Example: set router 1 IN1 all USB1 all [13234.129] 1 SRC:Def. off DST:OUT1 off [13234.129] 2 SRC:Def. off DST:OUT1 off [13234.129] 3 SRC:Def. off DST:OUT1 off [13234.129] 4 SRC:Def. off DST:OUT1 off [13234.129] 5 SRC:Def. off DST:OUT1 off [13234.129] 6 SRC:Def. off DST:OUT1 off [13234.129] 7 SRC:Def. off DST:OUT1 off [13234.129] 8 SRC:Def. off DST:OUT1 off [13234.130] 9 SRC:Def. off DST:OUT1 off [13234.130] 10 SRC:Def. off DST:OUT1 off [13234.130] 11 SRC:Def. off DST:OUT1 off [13234.130] 12 SRC:Def. off DST:OUT1 off [13234.130] 13 SRC:Def. off DST:OUT1 off [13234.130] 14 SRC:Def. off DST:OUT1 off [13234.131] 15 SRC:Def. off DST:OUT1 off [13234.131] 16 SRC:Def. off DST:OUT1 off [13234.131] [13234.131] MIDI Clock (change with 'set mclk_in <in-port> <on|off>' resp. 'set mclk_out <out-port> <on|off>') [13234.131] USB1 IN:on OUT:on [13234.131] USB2 IN:off OUT:on [13234.131] USB3 IN:off OUT:on [13234.131] USB4 IN:off OUT:on [13234.131] MID1 IN:on OUT:on [13234.131] MID2 IN:on OUT:on [13234.131] MID3 IN:on OUT:on [13234.132] MID4 IN:on OUT:on [13234.132] IIC1 IN:--- OUT:--- [13234.132] IIC2 IN:--- OUT:--- [13234.132] IIC3 IN:--- OUT:--- [13234.132] IIC4 IN:--- OUT:--- [13234.132] OSC1 IN:on OUT:on [13234.132] OSC2 IN:off OUT:on [13234.132] OSC3 IN:off OUT:on [13234.133] OSC4 IN:off OUT:on and here it is from the midio128. [ 13234.128] MIDI Router Nodes (change with 'set router <node> <in-port> <channel> <out-port> <channel>) [13234.129] Example: set router 1 IN1 all USB1 all [13234.129] 1 SRC:Def. off DST:OUT1 off [13234.129] 2 SRC:Def. off DST:OUT1 off [13234.129] 3 SRC:Def. off DST:OUT1 off [13234.129] 4 SRC:Def. off DST:OUT1 off [13234.129] 5 SRC:Def. off DST:OUT1 off [13234.129] 6 SRC:Def. off DST:OUT1 off [13234.129] 7 SRC:Def. off DST:OUT1 off [13234.129] 8 SRC:Def. off DST:OUT1 off [13234.130] 9 SRC:Def. off DST:OUT1 off [13234.130] 10 SRC:Def. off DST:OUT1 off [13234.130] 11 SRC:Def. off DST:OUT1 off [13234.130] 12 SRC:Def. off DST:OUT1 off [13234.130] 13 SRC:Def. off DST:OUT1 off [13234.130] 14 SRC:Def. off DST:OUT1 off [13234.131] 15 SRC:Def. off DST:OUT1 off [13234.131] 16 SRC:Def. off DST:OUT1 off [13234.131] [13234.131] MIDI Clock (change with 'set mclk_in <in-port> <on|off>' resp. 'set mclk_out <out-port> <on|off>') [13234.131] USB1 IN:on OUT:on [13234.131] USB2 IN:off OUT:on [13234.131] USB3 IN:off OUT:on [13234.131] USB4 IN:off OUT:on [13234.131] MID1 IN:on OUT:on [13234.131] MID2 IN:on OUT:on [13234.131] MID3 IN:on OUT:on [13234.132] MID4 IN:on OUT:on [13234.132] IIC1 IN:--- OUT:--- [13234.132] IIC2 IN:--- OUT:--- [13234.132] IIC3 IN:--- OUT:--- [13234.132] IIC4 IN:--- OUT:--- [13234.132] OSC1 IN:on OUT:on [13234.132] OSC2 IN:off OUT:on [13234.132] OSC3 IN:off OUT:on [13234.133] OSC4 IN:off OUT:on The SEQ v4 keeps sending midi FC bytes when paused or stopped and FA bytes when playing. The midio128 is in a loop always mentioning song position and won't give the router info when the seq is connected. I'm still with midio 3.13, need to download the repository and recompile my MB50XG project. the seq is v4.078. Maybe the problem is in my db50xg code.. Hope you see something! Quote Link to comment Share on other sites More sharing options...
TK. Posted October 1, 2013 Report Share Posted October 1, 2013 It's the BPM generator which generates the FC events, the router commands shows that IN and OUT are enabled at both sides. So, try: set mclk_in IN3 off set mclk_out OUT3 off at both cores to avoid the feedback. Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted October 1, 2013 Author Report Share Posted October 1, 2013 (edited) Oh thank you! I will test that. I took out one wire, so I'll have to solder it back on again. But basicly, both cores are drowning one another in clock signals, right? I uploaded the prebuilt midio128 v3.16. it has clock filtering in the menu right; and the seq v4.078 does not. Edited October 1, 2013 by EsotericLabs Quote Link to comment Share on other sites More sharing options...
TK. Posted October 1, 2013 Report Share Posted October 1, 2013 But basicly, both cores are drowning one another in clock signals, right? yes I uploaded the prebuilt midio128 v3.16. it has clock filtering in the menu right; and the seq v4.078 does not. MBSEQ has it in the BPM page Best Regards, Thorsten. Quote Link to comment Share on other sites More sharing options...
EsotericLabs Posted October 2, 2013 Author Report Share Posted October 2, 2013 TK you're like a heat seeking missile. Works like a charm! Thanks a million! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.