totoRaymond

Hi, Actually no, the command should be something like: LCD "@(1:1:1)LFO Freq %3d" but i think it would then display the value sent when script session is called, there might be a way to display another value, but i dont' know how. Alternatively you could use the TRIGGER EVENT function. It should update the display according to your EVENT label settings but also send the associated MIDI message. Bests, Thomas

Hi ssp, I don't remember if labels can be called from a map, but i don't think so. However, i think it is possible to change the display using a .ngr script. Bests Thomas

Hi Therezin, I mounted the monitor upside-down because of the viewing angle. This specific monitor has been designed to be looked at from above. It's actually pretty good from around 10° to 90°, but from 95° to 180°, the visibility is very bad. Therefore i had to reverse it so when i seat behind my desk, i'm in the good range. Let me know if this explanation is not clear enough, it's pretty hard to describe in a foreign language. Thomas

Hi ssp, I can't really help you with these problems, I might probably tinker with the code someday, but I don't have time to dig into this right now.

Hi ssp! Yes, this means that if you want more than 2 AINSER, you need to modify the code. and that you might use some unused IO pins on the J5A and J5B connectors. Cheers, Thomas

So 16 banks in total, right? I'll will try something... After a bit of head scratching and a few glasses of rhums, here you go: first the .ngc : EVENT_BUTTON id= 1 type= Meta meta= DecBank meta= RunSection:1 button_mode= OnOnly #Bank decrease EVENT_BUTTON id= 2 type= Meta meta= IncBank meta= RunSection:1 button_mode= OnOnly #Bank increase EVENT_LED id= 1 range= 1:1 radio_group= 1 #bank1 EVENT_LED id= 2 range= 2:2 radio_group= 1 #bank2 EVENT_LED id= 3 range= 3:3 radio_group= 1 #bank3 EVENT_LED id= 4 range= 4:4 radio_group= 4 #bank4 now for the .ngr : ####### Section 0 ####### if ^section == 0 log "running section0" #initialize all banks to 1 log "call bank 1 for all parameters" set ^bank 1 exit endif ######################### ########## Section 1 ########### #tests for the current bank and lights the corresponding LED if ^section == 1 if ^bank == 1 log "bank 1 selected" set LED:1 1 elseif ^bank == 2 log "bank 2 selected" set LED:2 2 elseif ^bank == 3 log "bank 3 selected" set LED:3 3 elseif ^bank == 4 log "bank 4 selected" set LED:4 4 endif exit endif ################################ I hope it works for you, at least, it behaves as wanted here.

yes, as many as you need, until you reach the 1000 maximum character for a single line. then you can use .ngr script, EVENT_SENDER or EVENT_anything really to trigger even more things.

Hi ssp, Two things: First, you need to change the id of the second controller: # Bank 1 EVENT_AINSER id=1 hw_id =1 bank=1 fwd_to_lcd=1 type=CC chn=1 cc=16 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR1 #%3i %3d@(2:1:2)%B" #Bank 2 EVENT_AINSER id=1001 hw_id =1 bank=2 fwd_to_lcd=1 type=CC chn=1 cc=17 range=0:127 offset=0 lcd_pos=2:1:1 label="FDR2 #%3i %3d@(2:1:2)%B" Otherwise, Midibox might get confused, all EVENT_xxx must have a unique id. Unless they are of different types. for example you can have EVENT_LED id=1 and EVENT_AINSER id=1 Second: To light an led for each bank you need the button that sets the bank to forward info to the respective LED. for example: # select Bank1 directly EVENT_BUTTON id=1 fwd_id= LED:1 type=Meta meta=SetBank button_mode=OnOnly range=1:1 # select Bank2 directly EVENT_BUTTON id=2 fwd_id= LED:2 type=Meta meta=SetBank button_mode=OnOnly range=2:2 #LEDS EVENTS EVENT_LED id= 1 range= 1:1 radio_group= 1 EVENT_LED id= 2 range= 2:2 radio_group=1 The radio group makes sure only one LED turns on I also put the switches in the same radio_group on my config, but i'm not certain it's mandatory. now, i didn't use cycle_bank, inc_bank or dec_bank but you can take a look at those examples config to see if you find something interesting: https://github.com/midibox/mios32/tree/master/apps/controllers/midibox_ng_v1/cfg/tests And also, i found usefull to add #initialize all banks to 1 log "call bank 1 for all parameters" set ^bank 1 to the section 0 of my .ngr script. this ensure that all parameters are set to bank 1 at startup.

Hi everyone! Quick update here. I finally finished my controller and installed it in my small control-room. Here it is. I really like the way it turned out, i'm working with it since 2 weeks now, and it's a real bonus to the ergonomics. It still have room for improvements but that was expected and i will continue to work on it in the next future. I'd like to thank everyone on this forum who helped me build this and a BIG thanks to TK and all the midibox team. Without this place I would have never been able to even start this project. Cheers, Thomas

Lemur does listen to port 8000 and only port 8000. 8001 is used for Lemur to communicate with offline editor. Making network connections work reliably can sometimes be quite quircky. My instance of Lemur is hosted on a Odroid XU4 running Lineage OS, therefore no wifi but ethernet. The ethernet driver must have problems since whenever i try to configure a static Ip address, my odroid lose its network connection after a couple reboots. I ended up setting a permanent DHCP, but i need to remember that every time my ISP annoys me enough for me to change. Well, glad you got your config back together and working. Cheers, Thomas

Hi, I'm currently adding some OSC to my custom DAW remote, which is a Midibox and a lemur instance and it works. Have you checked your network connections? With OSC, it's preferable to set everything to static IP address. Thomas

Well it seems to work as expected so far. You might be able to lower the jitter by using shielded cable (microphone cable should be fine). Thomas

I feel what you say. Documentation on the midibox NG is sometimes wonky (some description are wrong case wise, I've lost nights chasing case sensitive statements) but the software is so good.... I'd like to be able to correct things on the documentation sometimes.... or just add comments so people after resolve same problems faster. still, MidiBox is an awesome project. It deserves to be supported by a lot more people. I'd like to become part of the team though i don't feel worthy of it. Cheers, Thomas

Hi, I got the same issue yesterday too. Seem to work right now... Thomas

Hi again, If you're thinking about 2 buttons, then there is the "meta= IncBank" and "meta= DecBank" options. having the effect of increasing bank and decreasing bank respectively. AND (i just checked the manual), you can also specify the hw_id on which you want to change bank with "meta= IncBankOfHwId" and "meta= DecBankOfHwId" options. advantage being: i doesn't change ALL parameters banks but only the specified ones (you can specify any number of hw_id) Hope this helps. Thomas

HI Everyone, Just a quick update, it's been a while since last one but Covid plus a child got in the way . I also had to rebuild my CNC router from scratch last winter in order to make the front panels. So, the front panels are slowly getting done, and i can finally add thing to the mock-up chassis i made a year ago. (Pictures attached) I hope all the front panels will be finished next week so i'll be able to start debugging the config files. I also still need to find a way to properly label my buttons caps. Cheers, Thomas

Hi Zener, well i don't use any virtual instruments so the short answer is : no. But, i don't see why it couldn't be used for that too if needed. Thomas

HI! It's time for a quick update! I'm in the process of building the console frame right now. Mostly because 90% of the pcb assemblies are done and because i need a way to wire everything together without becoming too messy (I fried 2 stm32 Discovery so far due to bad wiring). So I assembled a model today and it came out great! I'm really pleased with the dimensions and the sloping of the frame right now, but some dimensions are too tight to fit everything together, so i'll have to redo everything (thankfully it's made out of scrap wood). To give an idea of the finished console, the bottom will hold 24 faders on the left plus a master section (transport, jog, switches, surround panner) on the right. the middle will be 24 encoders plus Oleds, and a few switches. and the top will be a 19" 4U Rack on the left, a 15" Touchscreen on the centre, and 12 Encoders plus monitoring controls on the right. Cheers, Thomas

Well, there's nothing in the doc about using ASCII code with MidiBox NG, so i'm not sure you can do that. Unfortunately my STM32F4 board fried last time i plugged it (messy wiring) so i can't try anything right now. Sorry I couldn't help, Thomas

Hi, I don't think the built in fonts have special characters available. I remember reading a thread about creating you're own custom fonts, but it involved recompiling the MB_NG firmware. Search the forum, you light be lucky Thomas Edit: I found it! it was in the wiki page: http://wiki.midibox.org/doku.php?id=how_to_create_custom_glcd_fonts_icons_bars_for_midibox_ng

Hi, Yes, you can chain up to 4 of these boards together. You need to change the #id of at least one of the controllers to be able to use them with MIOS studio. I've not done it myself everything is ecplained in this thread: You should read the whole thread, it's full of good info on how to setup the board properly. Are you using a core module to interface with the MF_NG? Or do you want to connect them directly to the computer? Cheers, Thomas

HI Zeke and thanks for the advice! I'm building a DAW controller, basically i'll emulate 3 Mackie Control Units plus a "generic remote" to control Nuendo. In the end, i hope to get 25 faders plus a bunch of stuff (including a touch screen with a lemur patch). I reported my progress in this thread (not updated very often though) : Right now i have only fader attached to the board. The wiring with this board is a bit of a mess so i'm currently making a new pcb with one connector for each fader to keep things tidy. I'll definitely try with 8 faders connected, but in the near future i have to build a prototype enclosure (made of MDF i have lying around) so i can start to assemble everything properly (and stop killing board with shorted wires). All the fine tuning will be done once I gathered all the parts. Cheers, Thomas

No worrys, as I said, i think i will settle for this solution for now. I'd like to have a working build before end of the year and improve from there. If I remember well, you're problem with PWM was related to EMI leaking into the analog circuitry, not the actual physical noise of the fader. Am I right? You're right, the PIC used on MF_NG won't go higher in frequency, But if need be, i'm not afraid to port the code to a more capable micro... (as long as i have a working controller, i have all the time in the world to make it better... ) I never looked inside a D-command, but if i get a chance, i'll check the Ic's used (might even look inside an Avid S6, who knows, those faders are great). I'm going to start looking into some other controllers too. Thanks! Thomas

You need to download an old version of MPLAB to use a pickit 2. A quick search in google tells me MPLAB IDE v8.92 is the latest version with pickit2 support. all older versions of mplab are available on microchip webpage: https://www.microchip.com/development-tools/pic-and-dspic-downloads-archive Or you can buy pickit3 or 4 and use MPLAB X Cheers, Thomas

Hi Zam, After reading ths whole topic again last week-end, I tried to lower the voltage. With Vm down to about 4V, i was able to get rid of most of the mechanical noise, but now the faders are a bit sluggish (actually, there's only one fader wired to the board right now). The PWM might be the problem, I know you went another route for your analog automation system (I followed the story since the beginning on gdyi). Do you think we could get rid of that noise using a higher PWM frequency? Or is it necessary to drive faders with DACs instead? There must be a way to drive faders in silence, I work all day on digidesign D-Command, they use the same ALPS K-faders I have and they're very quiet (and fast). I think i could live with slow faders for a time, but I might try to move to another solution once my controller is finally assembled. Cheers, Thomas