Zam

Hi Using map and toggle mode should work, as fwd to sender and meta should work for led at NGC MAP1 2 20 38 ....120 EVENT_BUTTON .........fwd_id=sender:1 ...... range=MAP1 button_mode=toggle EVENT_SENDER......type=meta meta=runsection:1 at NGR section1 if button == 2 set led:(up):127 set led:(down):0 set led:(random):0 set led:(played):0 set led:(chord):0 endif if button == 20 set led:(up):0 set led:(down):127 set led:(random):0 set led:(played):0 set led:(chord):0 endif if button == 38 set led:(up):127 set led:(down):127 set led:(random):0 set led:(played):0 set led:(chord):0 endif etc..... Best Zam

Hello again ! Demo of the day... how to use moving fader as sequencer Best Zam

Hi all here it is IO board 4 layers, smd for all ic (pitch 1.27 still diy friendly...) Remote board for 6but 6 led, no major change here... and Motor board, with improvement/correction since first manufactured proto PCB Best Zam

Hi all In addition to my moving fader system (soon released), I write some alternative NGC/NGR for various stand alone calibration process like PID tuning and Touch sensitivities. For the "touch calibration" NGC/NGR I write a loop section with incremental value activated by a button that automatically move the fader (CV output) up and down, in order to see when the touch calibration pot bypass the motor driver (or not) here is the section for fader 1 (CV3 due to HW layout): if ^section == 1 if BUTTON:6 == 127 set CV:3 [CV:3+10] if CV:3 >= 16200 set BUTTON:6 126 endif delay_ms 1 exec_meta RunSection:1 endif if BUTTON:6 == 126 set CV:3 [CV:3-10] if CV:3 <= 200 set BUTTON:6 127 endif delay_ms 1 exec_meta RunSection:1 endif if BUTTON:6 == 0 set CV:3 0 endif exit endif It work fine, but I have a strange behaviour between various fader (8 in total) More I go up in fader activation, from 1 to 8, more the fader is slow !!! despite the exact same incremental/decremental math and delay, which is theoretically around 1.6sec full travel here (14 bit / 16383 steps with 10steps each ms -->1600ms), 3.2sec for the full up and down wave. It's not a big problem for me in this use case, I just need to see if fader move or not, speed is not so important but I like to understand why Is there some priority or something with .NGR and section call? Best Zam

Hello Novski Ok, you are on the list ;) I will update in 2 or 3 week with price and technical info/notes Best Zam

Hi all First batch on the way Around 10 pcb set will be available soon (I order 15 but I need some and 1 is reserved for TK) Best Zam

Ho sorry you talk about the pcb with 4DIN or 4DOUT , so yes two pcb for led and 2 pcb for button is ok :) The only SMD part is the SDcard holder, footprint is large, no special skill to solder this with standard iron. Best Zam

Hi Leon Welcome here Your project is absolutely possible with midibox. Few notes: You need 8 DIN/DOUT for 60 button (8x8=64) or a DIO_MATRIX which can handle 64 led and button I suggest you go for the STM32F4 core, which is the more recent core available for MIOS Best Zam

Yes we have a difference here, I don't mention it but I use MB_NG (1.036) at both core. Let's wait advise from TK. Best Zam

This is what I meant ;-) mmm...ok :) maybe this is transfer speed, without buffer consideration and MIOS data analysis ? Your test is interesting, I think I run a way more heavy stream than you, 8 PB constantly changing, bidirectional, 4 port used, acting button and led, with sysex stream etc... and I can use trice the speed ? What is your cable length between cores ? Here midi In (master core) come with 1k to 3V3 pull up, and midi out (master core) is after a line buffer(74HC244) and 220R (series), ribbon about 30 cm Best Zam

are you sure ??? I read 2 ms :) I think it's only UART port... Best Zam

Hi I'm back on this... I think what I want to achieve request 4 session with 4 endpoint at kissbok dialling with 4 SPI midi at midibox side... Best Zam

Hi TK Ok, I work some hours to build an HW config to emulate 4 MCU controler test condition: One "master" core (Benoit RTPM core pcb) as midi router only. IN1->USB1....IN4-->USB4 same with the other way One core (SmashTV) emulating 4 MCU instance, one MCU at midi1, and 3 MCU XT at midi 2 3 and 4 As I have only 8 fader for now, physical 1 and 2 go to midi 1, 3 and 4 to midi 2 etc... same for all button and led with midi event. Midi connection between core are quite direct, I remove optocoupler at input master core but use the buffer at output, for slave core it's direct at J11. I compile different app: -suggested 10x speed, 312.5k - buffer 64, look to work fine -20x speed, 625k - buffer 64, look to work fine... -aprox 30x, 1000k - buffer 64, strange things happen, like button mixed up with midi data and fader send wrong data, CC in place of PB etc, for sure there is massive lost in the data transfer... -same 1000k with buffer at 128, don't seem to help I don't go further for now with buffer at 255 for high speed, because for now 20x work... 1ms ? Voilà ! System is wired and up for running, so let me know if you need more experimentation at my side. Best Zam

Ho sorry my bad... Any router configuration? If it's an alternative .NGC don't forget to add a reset_hw command at start Best Zam

Hi Duggle How is you hardware connected to your host computer ? it look like USB and I suspect the channel 1 you actually see at MiosStudio is USB1. Your port definition send to USB1 en MIDI2 To monitor MIDI2 you have to connect the respective DIN5 MIDI connector (via a midi interface) and select the appropriate midi in port at MiosStudio (or any other midi host software) If you want to use USB1 and USB2 the ports configuration is ports=1100000000000000 Best Zam

Hi Load command work fine :) I just have a question regarding ^section == 0 When this script is read ? only after startup or reset ? before or after .NGC load ? I'm able to automaticity load another setup without conditional with load setupA at section 0 if ^section == 0 load setupA exit endif But I'm not able to chose a setup (with conditional) The use case is to have "default" acting like configuration router setupA (user config) automatically loaded at startup, but if I press some button at startup it will load other setup, like setupB for dedicated calibration, or setupC etc.. if ^section == 0 delay_ms 2000 if button:1 == 127 load setupB else load setupA endif exit endif I have the event_button definition at NGC but if I press it, noting happen, setupA nor setupB are loaded and system is locked at default setup. Best Zam

Impressive ! Best Zam

Great ! I go to test it right now :) Best Zam

Hi all Yesterday, after two years designing and "playing" with hardware for midibox NG, I just finally compil my first app... the default midibox_ng_v1 A new world is opened to me and I hope I can "custom" the ng for my fader system, maybe a dedicated app ! Today I try things like reducing SRIO scan and AOUT number, as deactivated unused hw in my design like encoder OSC etc... Now I have a question regarding the default.ngc file generated by the app when not present at the SDcard, where can I modify this to have my dedicated .ngc automaticaly generated ? Best Zam

Hi Chris Maybe you can try to define an event receiver forwarded to the banked event id ? Best Zam

It happen to me too. I suspect it's when you have hardware I/O in the SR chain that don't have any event definition in the NGC. I don't go further with this for the moment so it's just speculative. since just add: EVENT_BUTTON hw_id= to my 8 unused DIN pin, I don't remember having this issue again. Another suspect is one of my SDcard, which is prone to corrupt file, and after powerON or reset it end sometime in a big mess when you look at the .NGC Best Zam

You've to try out if the higher MIDI rate improves the overall performance, and you've to find the sweet spot. With higher speeds also the performance of your computer, operating system and DAW become relevant. I'm very interested on reports before providing this as a general configuration option for "common users". Best Regards, Thorsten. Hi TK I only have 8 fader and one core running for the moment, hope I can build the second pack soon (need to order the revised PCB) So unfortunately I'm not able to give any feedback now, I also need to go deeper at soft side knowledge, compiling etc ..., I still not so good at this... Best Zam

mmm... not quite sure yet for the +5, but for sure SMPS (vero trivolt) will be in the same enclosure sharing same 0V ref at chassis earth/grounding As sense detection is at annoter PCB (the one with all Din/Dout, 3m from core 19' rack) there is voltage change at Core PCB which can be different if different +5V rail are used depending of LED activity. But that's another topic :) Best Zam

Hi Thorsten Also interested with this to chain two or more core ! Side question, can we interconnect two core directly without optocoupler ? I mean for example MO1 (PA2) from one core to MI1 (PA3) from second core ? My use case (moving fader) will be to have up to 4 core connected to a master which can handle routing from MIDI to USB (or RTPM) to have a single USB (or ethernet) cable to run 4 MCU/HUI instance (like 4 MF_NG hooked to one core). All core running NG. Master will certainly have dedicated event send/receive to manage slave core global data, like my conditional mute and "solo in place" function (actuating analog FET audio mute via optocoupler at DOUT) Do you think there will be enough "power" and bandwidth to send/receive 32xPB data constantly changing ? (worst case with 32 fader always moving) Best Zam

HI Juho Welcome here. At least I know two midiboxer that have designed pcb for the core, maybe they have some avaiable. -BEBdigitalaudio -ksir Best Zam