• Content count

  • Joined

  • Last visited

Everything posted by Zam

  1. dipCoreF4 and dipBoardF4, a compact Core.

    Unfortunately not enough interest for my "highend", costly, and complex automation to justify another hundreds hours of "R&D", despite I still have in mind a "simplified" version...but still in standby for the moment. Best Zam
  2. dipCoreF4 and dipBoardF4, a compact Core.

    Hello Bruno Look great ! If only I got this 4 years ago, my midibox design would have the core directly on the main board... Bravo Zam  
  3. Push & Hold - function?

    Hello   You can reduce the time for the short push to only wait the processing when long time press   if ^section == 1 delay_ms 50 if BUTTON:1 == 0 SEND CC USB1 1 2 0 exit endif delay_ms 500 if BUTTON:1 == 127 SEND CC USB1 1 1 127 exit endif endif By this you can handle both situation time in any time respond configuration you want Note that first condition will in fact be the time you manually release the button (if shorter than second delay) + the first delay as the script will re-trig when button is off ( due to button_mode=onoff) Best Zam  
  4. is it strange??

    brilliant edit Best Zam
  5. understanding the .ngc code

    Hello   Don't know if you can do this without a script (NGR) to handle the 8 possible two CC toggle (equivalent to Y axis in a 2x8 pattern) You can maybe simply with toggle scan X(16,17...23,24, 31,16....) and Y (16,24,17,25....31,16...) with 2 MAP But in a strict "user friendly" interface I personally won't use two encoder to select data in a 2x8 matrix display (for a 8x8 OK...) A single continuous scan will be as fast for only 16 slot (assuming you can go both direction, most distant data is only at 8 encoder tick) , OR you can use the encoder button to switch X/Y scan axis Only two encoder, data and value Best Zam
  6. DAW integration of LED rings

    Hello Assuming you set your led type and value according to MCU chart (CC for Vpot/encoder IIRC) it should work... side note: MCU Vpot have flip function, you'll have feedback according to selected layer (pan, aux etc...) Best Zam
  7. understanding the .ngc code

    Hello The purpose is to have on up and one down button cycle trigging 0 21 41 61 81 with dedicated led for each steps right ? Maybe a script(runsection + .NGR) will be better strategy, especially to retrigg/update the "opposit" button value to match actual CC value Otherwise you push button 1 few time (let say 2, CC val=61) but button 2 stay at 0, and if you push it once you send 21... Best Zam
  8. Sender and if_equal

    Hello All your sender have same id... Define hw_id=1 for all event AND id=100..101..102... (or whatever numbering strategy you choose) Don't know if it's the reason of your issue (but it might, same events with different conditional may behave strange and conflict...), you better make a correct config first Best Zam
  9. MIDI over Bluetooth with ESP32

    Great work Thorsten !! Side question, is it possible to hook ESP32 and STM32F4 cores with direct midi/UART connection (high speed without opto like I do between 3 STM core here) And use it as a RTPM wifi bridge ? Best Zam
  10. Joyeux Noel et Bonne Année à tous!!!

    Happy new year to all ! Cheers Zam
  11. More AINSER Problems

    plz wait until OP say something...can be dumb too Still (no offense) I find pples around so focused on digital and code that they usually miss the first things to check in the chain Best Zam
  12. More AINSER Problems

    Hello Did you check the analog side ? I mean the pots to multiplexer path ? If you make the 8 pot wiper like a single bus... Best Zam
  13. Hi all This is the MIOS based 89MotioN system release and support tread The first PCB batch is now available. It consist of 17 pcb to build a 8 fader pack automated motor fader system as follow: -1x 89InouT, 4 layer 80*260mm pcb, which handle 64 D i/o and 8 A i/o, connection to 8 89MotoR board, connection to core(or line receiver), and optional D i/o chain connector, and power supply distribution. -8x 89MotoR, 2 layer 34*116mm pcb, which handle analog PID motor driver, touch detection, one optional isolated digital output (optocoupler), one optional digital input (button), 6 D i/o through connector from 89InouT to 89 RemotE -8x 89RemotE, 2 layer 14*148mm pcb, which support up to 6 omron B3W-9 series illuminated tact switch. -all pcb HASL lead free Price is (out of stock) (+shipping/packing, +fees if applicable). 12 pcb set available from this first manufacturing what you get: -the 17 PCB described above -BOM -schematic -PCB mechanical drawing -Basic notes for build and calibration What you need for basic build: -all component at the BOM (most ref already fitted for RS and reichelt) 300/400euros -one STM32F4 core running latest MB_NG, configured to emulate Mackie Control. There is universal MCU template available, as my NG/NR config for DigitalPerformer i’ll be happy to share. (request 1 core for each 8 fader pack) -decent PSU, 3 rail total, +5V, +/-15(+/-12 work too). at least 2A per rail, be careful most low cost bipolar supply have poor negative amperage capabilities, sense input is recommended for the +5 rail (I use industrial euro rack Vero trivolt PK120, 500€) -8 motor fader (tested ALPS RSA0N 8V and TKD MF914 10V my current choices) 15 to 100€/pce -A console, a box or a front panel that fit the system (I can provide basic template .fpd file for fader and button cutout) 0€ if it’s a retrofit installation that need no metalwork to 1000€+ in a custom modular setup like mine… -For integration in analog chain you need a +10dB post fader buffer (for unity gain @ fader -10dB attenuation position), to my knowledge all descent console have it so you are fine, in situation of outboard analog mixing/summing you have to think about it. -line transmiter/receiver in case you need/want the core, PSU, SCS and or LCD in a separate/dedicated case or 19inch rack Important notes: This is a 2+ years R&D at hardware side for me, not to mention what TK have done since lot of years, as improvement and new options recently done at NG code which this system won’t work so well without. The goal since beginning is to build a high end automated fader system, dedicated to analog chain/mixing desk requiring low noise and low EMI environment, which is a challenge with digital data lines and motor close to low level analog audio signal. Saying all this I consider this build an « advanced » one, it involves 20 SMD ic at the main I/O board, I won’t do a step by step build tread, so ppl have to know how to read a schematic/BOM and understand what’s going on with all those component. It’s a long built we are close to 1000 component to solder in total… mistake can be exponential with so many part, no special skill, but methods and organization at all stages. My expectations for this first run is to have few fader pack builded around, in a reasonable time range, to have useful feedback and various experience to share. Also, it’s not a cheep build, consider 2-3k depending of hardware integration, motor fader choices, frontpanel + optional 19in or case if you want/need psu and core far from faders (like me, it request optional line driver) I have great result in my use case, 8 fader(for now) loaded in a discret 32 channel Studer 289 from 1977, however, I can’t guaranty the same result (in term of audio integrity) in another desk, if trouble occurs with digital data line or motor radiation, it could be dependent of specific console design/layout at both mechanical and electronic side. So I can’t say « I will solve your problem » but of course I will try to help. For ppl that just want a DAW controller (no analog audio path in the fader) there is possible cost saving, cheaper fader (like ALPS RSA0N11), lowering fader speed and increase current limiter at motor to use cheaper PSU. For ppl that want motor fader to automated a VCA based system, there is different option to handle this with the system, let’s have a talk if you are interested WARNING ! there is some limitation: -at the moment the system don’t support HUI protocol for fader data, It won’t work as is in Protools !!! Be sure your DAW allow MCU protocol, or have a look at some midi translator software, I made a quick test, and was able to convert pitch bend fader data to HUI raw midi data on the fly, I don’t and won’t push further at this topic for the moment, so I have no measurement or data to share regarding hypothetic extra latency. -Work in progress regarding HUI protocol, now the system handle it natively for all data type, I have a working midibox_ng 1.036 build, it involve a special handling of NRPN data at mbng_event.c (standard NRPN won't work but none are involved in HUI), as some trick at .NGC configuration file. I don't have a Protools licence but will perform test soon with someone that have one. -Another point is about MCU protocole, be aware that some functions are not bidirectional, and some are not « real time » bidirectional. Automation mode don’t return note or CC but only sysex text to print the mode at LCD, it’s still a challenge for now to update automation status LED from DAW All data except fader pitch bend are updates/returned to the system only once per sec, which mean the visual feedback (LED) is not ultra fast. Also as audio is picked-up pre fader at DAW, solo and mute can be complicated to handle depending of your DAW, here those functions are 100% handled onboard with optocoupled remote analog mute and special mute/solo conditional script. Mute automation is done via a separated midi track What I won’t do: -publicly release the schematic, at least for this firs run, and certainly for the few next. -release the layout/ pcb fabrication files. -organize any component and part bulk order /group buy for this first batch. What I hope to do next: -Be able to test TKD LMH5 series (I’m sure it will work fine with the driver, it’s the same 8V mabushi motor as ALPS), it’s an alternative quality between the MF914 and the ALPS RSA0N, which have an interesting mechanical build, to say it quick, motor driver PCB should be directly soldered to the fader terminal, vertical mount, which can be a nice option for future and mechanical integration option. So if someone plane to use those, just drop me a message to discuss about one or two spare fader for test at my side. -Test (me or someone else) a fader with coreless motor -Design a 89TransporT unit for the system, which should be a D i/o extension with button and led, maybe one rotary encoder, to have extended function and DAW transport interface in the same design. -Build a vst/AU plug-in if I can… or if someone have the skill and motivation for this, to have direct connection with the fader, without third party MCU driver. -Go further with RTPmidi, high speed, which combined with plugin should allow the system to have way more than 32 fader in a single channel. -all other things that will com up in mind by the time… Quick technical data: -2000 steps, which equal to 0.05mm for 100mm fader. Theoretically 2048 (11bit), but some dead band are involved depending of calibration and fader curve mapping -100ms for full travel -Repositioning accuracy better than 0.01dB (at static event) -fader tracking is 0.1dB for 2/3 of the fader (upper side) if dedicated interpolation map is used for each fader (it’s some time to measure and write in the config file…) otherwise one global interpolation map for all fader give you at worst the fader attenuation accuracy given by the manufacturer. In short, the system is more precise than any manufacturer taper print you will find. I hope future builder will have fun with this great tool, which to my knowledge is the first analog fader automation available for DIYer If interested just PM me Best Zam   the development thread
  14. MIDI over Bluetooth with ESP32

      KiCAD is great ! Glad you switch Best Zam  
  15. Power Protection circuit for SID 8580

    Hello Why not just use a resistor/fuse (or resetable fuse) and a zener ? Best Zam
  16. MIDI over Bluetooth with ESP32

    Hello Thorsten I have something like "MF_HD" in head since time but don't start because of no more real need for me (I have my motor driver) It's hybrid, between MF_NG and My 89MotioN, in all aspect probably (cost, quality and performance)   Your two AD scan from fader servo seem to show improved noise at 200kHz.   Best Zam  
  17. MIDI over Bluetooth with ESP32

    Ok ! don't know what is the agenda or if any major MFNG update is on the road (which I can help on by the way...) I suggest to factor at least 10 the clock in case of hybrid system (analog close to or in the fader...) let say 312.5kHz , which correspond to 256 speed level (you have room over 64...) also a value over 192kHz (HD audio) I mean If it's easy don't hesitate to change this... Best Zam
  18. MIDI over Bluetooth with ESP32

    Hello Thorsten That's interesting, what is the max possible clock speed ? Best Zam
  19. MIDI over Bluetooth with ESP32

    Hi all Look promising Especially if RTPM via wifi is implemented Best Zam
  20. fader info

    Hello Fader are just pot, 3 pin, you should find the pinout within 30 sec with a ohm meter... The pin that have variable resistance (across any two other) when moving the fader is the wiper The two pin that have fixed resistance when moving the fader are 0 and Vref The pin across the wiper which indicate low resistance when moving the fader down is the 0v The pin across the wiper which indicate low resistance when moving the fader up is the Vref Best Zam
  21. understanding the .ngc code

    Hey TK   of bad Best Zam  
  22. understanding the .ngc code

    Hello If you need more toggle steps use a map for value MAP 1 2 3 4 in event button range=map1 the button value will toggle 1,2,3,4,1,2,3...... and 4 sender with contitional if_equal=1.... if_equal=4   i think i made a mistake you have to separate the fwd_id led (otherwise led will get the sysex and not the button value)   event_button id=1 fwd_id=sender:1 range=0:127 button_mode=toggle event_sender hw_id=1 id=1000 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x10 0xf7" if_equal=0 event_sender hw_id=1 id=1001 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7" if_equal=127 event_sender hw_id=1 id=1002 fwd_id=led:1:0 if_equal=0 event_sender hw_id=1 id=1003 fwd_id=led:1:1 if_equal=127 Best Zam
  23. understanding the .ngc code

    Hello You can do it this way: event_button id=1 fwd_id=sender:1 range=0:127 button_mode=toggle event_sender hw_id=1 id=1000 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x10 0xf7" if_equal=0 event_sender hw_id=1 id=1001 fwd_id=led:1 type=SysEx stream="0xf0 0x00 0x01 0x16 0xE0 0x18 0x01 0xf7" if_equal=127 Best Zam
  24. Hello Don't know if it's related but I remember having app issue (MB_NG) when in debug mode combined with large "regular" data transfer or config file update from/to computer. So maybe as a start just be sure debug mod is off as soon as you don't need it and send lot of data. Best Zam