Search the Community

Showing results for tags 'matrix'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 17 results

  1. Stop knobs board

    Hello, My English is not very good. I am trying to build an electronic stop knobs board. If I press a knob I want a signal to my grandorgue program. Later on I want to connect leds to indicate the state of the button. I made board, soldiered the button switch and connected them to a dio_matirix. The lpc17 had an old bootloader with midio128. I succeeded in installing midibox NG. The file "default.mio" was still on the SD card so I deleted it. The stop knobs (buttons) are not working out of the box. All the column buttons send the same note. I read a lot of manuals, but I do not get clear where to start. Probably edit the "default.ngc"....   Any help is appreciated. Robert    
  2. Harmonic Table Matrix

    I am working on a harmonic table midi keyboard inspired by This will be a grid of 21x12 keys with two switches per key. Two sets of matrix switches, one upper PCB and one Lower PCB to.determine velocity. I was concerned about scanning two large matrices, but the keys repeat along its length, By duplicating the lines in, the 21x12 matrix can be reduced to 7x12. This should hopefully reduce the total matrix scanning time with only sacrificing the option to designate keyboard sections to different channels.   Are there any problems to this approach? Regarding resistors, do I need any on the lines in/out and if so should they be before the line split or after? Thank you for the help.
  3. Hi everybody, Sit down ... Take a deep breath ... Close your eyes ... Now your mind is free ... Start dreaming about your perfect MIDI Router ... Imagine its IO count, features, shape / case, its behaviour and menu / screen functions... Leave aside any technical limitations, just imagine it ... Could you take a few minutes to describe it, please? Best regards Bruno  
  4. Hey MIDIbox community, first of all I want to thanks everybody participating in this project, since utilizing from the MIDIbox project really saved me a lot of time. In 2014 I started working on my DIY MIDI controller LambdaControl and can now proudly say that it is finished. I designed and build LambdaControl to support me during my upcoming live performances. Therefore, the controller consists of 10 channel that are fully integrated into Ableton Live. Each channel consists of a volume fader, six buttons for clip selection, four rotary potentiometers for effects, and an encoder with switch button functionality (could be used to control a looping mechanism). The normal components like the potentiometers or encoders are simply scanned by using the AINSER64 and DIN modules with a custom MIOS32 firmware. However, the special part of LambdaControl is the custom 10x6 RGB button matrix (based on button pads from Sparkfun), which is completely integrated into Ableton Live like a Novation Launchpad. For this purpose I connected a separate micro controller unit (MCU) via I2C to the MIDIbox core, which drives the RGB leds and reads the button inputs. The matrix MCU (16MHz Arduino Nano) can produce up to 4096 different colors by driving the matrix with a combination of multiplexing and Bit Angle Modulation (BAM). The matrix MCU still uses the shift registers of the DIN and DOUT modules to connect to the matrix rows and columns. This works really stable in the given scenario, but my implementation has some drawbacks like a low refresh rate or a relatively high input lag for the buttons (more in the documentation). This problems can be easily solved by using a MCU with more power or using a specialized IC like a TLC5958. However, it was a nice challenge to do everything in software on a limited hardware. Moreover, the parts used for the matrix MCU were with around 4€ really cheap. Additionally, I written a so called MIDI Remote Script, which integrates the by MIDI messages controllable RGB button matrix into Ableton Live. The MIDI Remote Scripts are python scripts that Live internally uses to integrate the different commercial MIDI controllers. The following picture shows that LambdaControl can be selected as every other control surface inside Live's preferences. The other screenshot shows the red rectangle that Live is rendering to visualize the position of LambdaControl's clip launcher that can be moved up and down by using the encoder on the master channel. I decided to release all files under open source licenses, such that other people can make us of my work. First of all you can find a complete documentation with more information and pictures on my website. Then I created four repositories on github for the different parts: Repository for the hardware related files like the faceplate or the 3D printable case MIOS32 firmware for the MIDIbox core Matrix MCU Firmware for the separate micro controller that drives the RGB matrix MIDI Remote Script for Ableton Live that integrates LambdaControl into the DAW I hope this information can help other people with their projects.
  5. Hi, in the pdf on the Wilba frontpanel button/LED matrix, the dual-color GPx LEDs are said to be hardcoded into the firmware. But in the said pdf the information on how to wire them is confusing. In the schematic the dual-color LEDs are wired to pins D4-D7, but in the chart next to the schematic they are wired to pins D3-D0. The question is: which version in the linked pdf – schematic or chart – is the one that I should use if I want to make a DIY frontpanel with DIO matrix?
  6. Encoders in matrix designs

    Need some technical advice about a question: May encoders be managed in a switch matrix design? see it may allow to manage large encoders numbers by having less DIN/DOUTs inputs outputs Bests, JK
  7. YEAH! Weihnachten ist gerettet!! Muss jetzt nur noch jemanden finden, der sich um meine Kinder und Arbeit kümmert. Ich habe zu tun...
  8. DIO Matrix glitching

    Hi, as part of my organ conversion I'm reading in the manuals with a DIO matrix module. Because of the weird pin layout of the keyboards and there also otherwise being no reason to use the keyboard drivers, I am using a simple DIN matrix (NGC file is attached). There are actually two DIN matrices. One for the pedalboard which is a 2*16 matrix and the two manuals which is a 8*16 matrix for both. All are inverted due to "wrong" diode directions. There is also loads of other stuff further down in the config file like buttons as well as switches and solenoids + some logic connecting the two. The problem that I'm having is that on the second DIO Matrix I occasionally get a glitch that on the first multiplexer all 16 keys fire a NoteOn event but never a NoteOff event (the lowest 16 keys on the first manual: IDs: 1033 - 1048). The glitch happens irregularly, at the moment maybe once every 4-5 hours (about every 15 million iterations of the midibox). Earlier in the year it was something like every few minutes though I was running a different firmware back then. I first suspected an electrical problem as I employed a different technique at the beginning of my project (crimping) which I later found to be unreliable and changed it (using ribbon cable + IDC connectors and soldering the wires with heat shrink over the solder joints. I re-did all the connections with IDC connectors. That didn't change the problem. I then remembered that the first time I powered up that DIO matrix module I had the DIs and the DOs swapped and thought I might have damaged the chips, so I exchanged the whole board: No change. I have now basically run out of ideas and wondered if any of you had any ideas: electrical/configuration/operating system/could it be software? What is surprising me is that even if the SRs return xFF for a tick and cause 16 NoteOn messages to get fired, wouldn't a reading of x00 the following tick cause NoteOff events to get fired? It seems weird that the NoteOff events simply never seem to get sent. I'd be very grateful for any suggestions as the only thing I can now think of is to go on a wild goose chase and trying to figure out if the special case of my configuration with inverted DIN matrix and the number of shift registers being limited can very rarely cause some kind of exception in the software.   Best Regards   Mathis ORGAN.NGC
  9. TekkStar formerly "Tama Techstar 306" once in the 80ś this was a brainless Drumexpander for Electronic Drum Kits... 30years later it gets a brain, no sequencing @ all, but note processing, and with note processing you can do a lot by doing less... wile a korg electribe rythm is sequencing, you can takt that and Kill, invert, roll, reroute, Offsets the notes and make trigger out of it... this drumexpander is velocity sensitive that meens, i could use a AOUT Board for this.... BUT i think that is a little bit overkill --- i decidet to take a DINX4, change the Resistors and make a 4Stage Veloctiy Trigger. I know that is enough because, i have already programmed a groovebox in max msp, that uses 3 Velocitys (3 Colours in the button matrix) - so 4 of it- enough... A AOUT board is still a plan - but not for trigger, - more for a VCA and VCF @ the Master > from my livesetup with other drumachines, i saw that it is very "doing less sounding much" if you can change the Release time of the Master --- by trigger a VCA (the trigger is selectable)... and VCF -without words! As you see this Case holds: 4 Analog Tom - Board 1 Analog Synth -Board 1 Analog Clap -Board -a Mixboard, which i dont use anymore, i need place for 2xDoutX4 and a DinX4! From Behind, already installed: The Core, and a modified DOUTX4 Board, A Core-Powerswitch (to reboot), and a PowerConnect where before was a Cable. Finding the best Resistor Values for the DoutX4 Board, by using 5K Trimpots As you see I used 4 Off it, so one Trigger has 4 Velocity-Stages. After finding the correct Values, and then testing fixed resistors in the near of the Pot Values (by ear), its time to solder a bit... well 2h 40min Later found a place for it, and wired the trigger outputs to the Drumvoices The 7th Board - the "Mix Board" a useless device that do not very much, ok, it makes headphone output a symmetric audio and so on, but how cares, I NEED PLACE for the UI and for the Midibox Boards (DOUTX4 DINX4 and so on), but bevore I had to solder a Adapter, because the Connecter pins are swapping on this board before it goes to the powersupply The Powersupply, supply me with +6VDC, and the coolest: -15 +15VDC!!!! yes I have planes... but The CORE wants 5V, so find a place for a 7805 found it! The core fits well behind the Trafo, but the Powercord sucks! Away with that ugly grey chord - a real Power Connector a "Kaltgerätebuchse" - hell yeah! But hey Core should be shieldet against the trafo, i searched my metal cases, and i found a very soft flexible Metall which is great for such ferromagnetic shielding stuff... Programming and testing Functions on Prototype Connector Boards "PressFitPCB" Because the TOM4 Board was Broken "Haarriss" the PCB-was broken, i had to solder something by the way i made my own first mods for this (by looking @ the shematic, which is very good to understand)
  10. Hello, my vision is to create a 32x32 digitally controllable audio matrix. I already created a very basic functional concept based on the AD75019. But the IC in fact doesn't matter for now as it's still exchangable in my plans. Because I already own 4 AD75019 i've choosen them to create my first basic schematic. As I am only a software engineer with some basic knowledge in electronics I wanted you to have a look over this and tell me if its complete bullshit or perhaps ( I hope so ) a good base to start. As I read at I think the biggest problems which can occur is the mighty crosstalk problem (where the MT8816 should fit better than the AD75019) and possible gain problems when routing 1:n or n:1 . I read that even n:1 would make bigger problems than 1:n . If I understood it right, when making 1:n, it would solve the problems if I just add some buffer opamps after the matrix outputs. When I wanted n:1 I need something like a mixer style schematic running through the matrix IC. This would mean I have to add some resistors before the input of the matrix ic. In common to the 1:n option I also have to add an buffer opamp at the outputs of the matrix IC. To be able to chain multiple matrix ICs I also added some buffers before the inputs to be able to distribute the incoming signals to multiple ICs. Additional to that I added resistors and a final output buffer stage to merge the outputs of multiple matrix ICs. I don't know what would happen when making n:m connections. Should this be prohibited or is it possible without side effects ? Is this a reasonable idea or isn't it good to chain opamps ? Simplyfied it's nothng more than 2 opamp mixer units chained through the matrix ics. Will the audio quality suffer from this ? To keep it scalable I'd split boards into 3 types (without the controlling board and other stuff around).... 'input (distribution) stage', 'chainable matrix boards', 'output stage'. I hope you were able to understand my idea in this :)   Best regards, Andreas 32x32 audio matrix 01.pdf
  11. Has anybody built a BLM with bidirectional two lead duocolor LEDs, where the two colors can be adressed by reversing the polarity?     How would the scan circuit have to be designed in order to work with the standard midibox solutions? Of course, compared with the scalar board, the resistor-transistor arrangement of IC2 could be placed next to IC3 and another 74HC595 next to IC2. But then the scan algorythm would also have to scan each color sequentially.     Why am I looking for such a solution? I evaluated the  the switch of choice for my Synth project:     For my needs, I only have single color buttons (yellow). But this button could also be interesting for BLM applications where duocolor would be needed (RGB is available as well).   I am working on a versatile matrix PCB solution for my synth project, where single rows of a matrix can be cut to the desired length and the LEDs can be adressed individually via solder jumpers. These smaller boards can be bought much cheaper in small quantities than the propriatary matrix boards and in my case serve different needs.
  12. TekkStar Make 057 UI Matrix working

    From the album TekkStar (Tama Techstar Midification)

    YES the matrix work!
  13. TekkStar Make 056 UI Matrix Testtool

    From the album TekkStar (Tama Techstar Midification)

    Test the matrix with simple LEDs bevore connecting the matrix... elsewhere you get very confused by programming and testing...
  14. The RGB LED matrix described here can be used to signal feedback to the user, as for example in my MIDI Matrix with 56 Inputs and 56 Outputs. But, it can also be used for fancy stuff, Vegas mode, bling, impressing your neighbours,…     The PCB is as wide as the RGB LED modules themselves, with enough space above and below for mounting holes. This means that the modules can easily be chained horizontally in order to create type crawls. If you cut off the top and bottom mounting holes along the line that is printed on the PCB then you can also create larger screens extending in two dimensions.   It consists of 4 DOUT shift registers (74HC595) that feed the RGB LED display module in a matrix style. It is connected to J8/J9 of the core board. In order to access the RGB LEDs, use the BLM-X module which makes it straightforward to access single colors / single LEDs in the matrix.   A fully detailed description of the project can be found in the Wiki.
  15. I recently received a few requests for TPD kits, as some of the parts seem to be difficult to obtain in some areas of the world - surprisingly, the 7 segment LED displays were among them. Unfortunately, I cannot do complete kits now, but I have purchased enough parts for 5 "semi" kits that should help with the most difficult parts. The semi kits consist of:   1x TPD PCB 7x 7segment LED display green 2x duo LED matrix module 1x rotary encoder with switch 4x three-legged common cathode duo LED, clear or diffuse, you decide   These are thought for people who are really having difficulties finding these - as I had to pay import duties to Norway you will most probably be cheaper if you can order them elsewhere. I am asking 24€ plus shipping per semi kit as above. For more information about the TPD have a look in the Wiki: http://www.midibox.o....php?id=tpd_pcb   PM me or post interest here, I can ship immediately.   Best, ilmenator    
  16. Sale: Monome 128 Panel

    Hello Folks,   Due to oveproduction I am offering 2 of the following panels:   Monome 128 Panel Aluminium, 6mm thick Raw finish, pleas brush or paint yourself (if you don't want to do it yourself I may brush it and throw some transparent coating on it I got laying around for a bit extra) No holes or drillings Original measurements from Monome plans Lasermanufactured   Please note these are kind of heavy, so shipping to outter Germany might be costy.   Please PM if you are interested.   Here's a picture. I didn't have acces to a better camera sadly.  
  17. LED Matrix around 8 Encoders

    I have problems with my LED Matrix. I built it upon the Schematic of Fairlightiii's pcb but with just 8 Encoders and LED Rings.   By turning one of the Encoders all LEDs around the other Encoders go on, but the LEDs around the Encoder i turn don't.  And the brightness of the LEDs increase by Turning all the Encoders to 127.   Don't know where to start searching.  The PCB is correct, i checked that.    this ist my config .ngc for testing:   RESET_HW LCD "%C" LCD "@(1:1:8)OLED1" LCD "@(2:1:8)OLED2" LCD "@(3:1:8)OLED3" LCD "@(4:1:8)OLED4" LCD "@(5:1:8)OLED5" LCD "@(6:1:8)OLED6" LCD "@(7:1:8)OLED7" LCD "@(8:1:8)OLED8" # Buttons configuration EVENT_BUTTON id=1 fwd_id=LED:1 type=NoteOn key=24 lcd_pos=1:1:1 label="^std_btn" EVENT_BUTTON id=2 fwd_id=LED:2 type=NoteOn key=37 lcd_pos=2:1:1 label="^std_btn" EVENT_BUTTON id=3 fwd_id=LED:3 type=NoteOn key=38 lcd_pos=3:1:1 label="^std_btn" EVENT_BUTTON id=4 fwd_id=LED:4 type=NoteOn key=39 lcd_pos=4:1:1 label="^std_btn" EVENT_BUTTON id=5 fwd_id=LED:5 type=NoteOn key=40 lcd_pos=5:1:1 label="^std_btn" EVENT_BUTTON id=6 fwd_id=LED:6 type=NoteOn key=41 lcd_pos=6:1:1 label="^std_btn" EVENT_BUTTON id=7 fwd_id=LED:7 type=NoteOn key=42 lcd_pos=7:1:1 label="^std_btn" EVENT_BUTTON id=8 fwd_id=LED:8 type=NoteOn key=43 lcd_pos=8:1:1 label="^std_btn" EVENT_BUTTON id=9 fwd_id=LED:9 type=NoteOn key=36 lcd_pos=1:1:1 label="^std_btn" EVENT_BUTTON id=10 fwd_id=LED:10 type=NoteOn key=37 lcd_pos=2:1:1 label="^std_btn" EVENT_BUTTON id=11 fwd_id=LED:11 type=NoteOn key=38 lcd_pos=3:1:1 label="^std_btn" EVENT_BUTTON id=12 fwd_id=LED:12 type=NoteOn key=39 lcd_pos=4:1:1 label="^std_btn" EVENT_BUTTON id=13 fwd_id=LED:13 type=NoteOn key=40 lcd_pos=5:1:1 label="^std_btn" EVENT_BUTTON id=14 fwd_id=LED:14 type=NoteOn key=41 lcd_pos=6:1:1 label="^std_btn" EVENT_BUTTON id=15 fwd_id=LED:15 type=NoteOn key=42 lcd_pos=7:1:1 label="^std_btn" EVENT_BUTTON id=16 fwd_id=LED:16 type=NoteOn key=43 lcd_pos=8:1:1 label="^std_btn" EVENT_BUTTON id=17 fwd_id=LED:17 type=NoteOn key=36 lcd_pos=1:1:1 label="^std_btn" EVENT_BUTTON id=18 fwd_id=LED:18 type=NoteOn key=37 lcd_pos=2:1:1 label="^std_btn" EVENT_BUTTON id=19 fwd_id=LED:19 type=NoteOn key=38 lcd_pos=3:1:1 label="^std_btn" EVENT_BUTTON id=20 fwd_id=LED:20 type=NoteOn key=39 lcd_pos=4:1:1 label="^std_btn" EVENT_BUTTON id=21 fwd_id=LED:21 type=NoteOn key=40 lcd_pos=5:1:1 label="^std_btn" EVENT_BUTTON id=22 fwd_id=LED:22 type=NoteOn key=41 lcd_pos=6:1:1 label="^std_btn" EVENT_BUTTON id=23 fwd_id=LED:23 type=NoteOn key=42 lcd_pos=7:1:1 label="^std_btn" EVENT_BUTTON id=24 fwd_id=LED:24 type=NoteOn key=42 lcd_pos=8:1:1 label="^std_btn" EVENT_BUTTON id=41 fwd_id=LED:41 type=NoteOn key=43 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id=41 fwd_id=LED:25 type=NoteOn key=43 lcd_pos=1:1:2 label="^std_btn" EVENT_BUTTON id=42 fwd_id=LED:42 type=NoteOn key=36 lcd_pos=2:1:2 label="^std_btn" EVENT_BUTTON id=43 fwd_id=LED:43 type=NoteOn key=37 lcd_pos=3:1:2 label="^std_btn" EVENT_BUTTON id=44 fwd_id=LED:44 type=NoteOn key=38 lcd_pos=4:1:2 label="^std_btn" EVENT_BUTTON id=45 fwd_id=LED:45 type=NoteOn key=39 lcd_pos=5:1:2 label="^std_btn" EVENT_BUTTON id=46 fwd_id=LED:46 type=NoteOn key=40 lcd_pos=6:1:2 label="^std_btn" EVENT_BUTTON id=47 fwd_id=LED:47 type=NoteOn key=41 lcd_pos=7:1:2 label="^std_btn" EVENT_BUTTON id=48 fwd_id=LED:48 type=NoteOn key=42 lcd_pos=8:1:2 label="^std_btn" # Encoder configuration ENC n= 1 sr=4 pins=0:1 type=detented2 ENC n= 2 sr=4 pins=2:3 type=detented2 ENC n= 3 sr=4 pins=4:5 type=detented2 ENC n= 4 sr=4 pins=6:7 type=detented2 ENC n= 5 sr=5 pins=0:1 type=detented2 ENC n= 6 sr=5 pins=2:3 type=detented2 ENC n= 7 sr=5 pins=4:5 type=detented2 ENC n= 8 sr=5 pins=6:7 type=detented2 # LEDring configuration DOUT_MATRIX n= 1 rows=8 sr_dout_sel1= 7 sr_dout_sel2= 0 sr_dout_r1= 8 sr_dout_r2= 9 # Encoder events EVENT_ENC id= 1 fwd_id=LED_MATRIX:1 type=CC chn= 1 cc= 24 lcd_pos=1:1:4 label="^std_enc" EVENT_ENC id= 2 fwd_id=LED_MATRIX:2 type=CC chn= 1 cc= 25 lcd_pos=2:1:4 label="^std_enc" EVENT_ENC id= 3 fwd_id=LED_MATRIX:3 type=CC chn= 1 cc= 26 lcd_pos=3:1:4 label="^std_enc" EVENT_ENC id= 4 fwd_id=LED_MATRIX:4 type=CC chn= 1 cc= 27 lcd_pos=4:1:4 label="^std_enc" EVENT_ENC id= 5 fwd_id=LED_MATRIX:5 type=CC chn= 1 cc= 28 lcd_pos=5:1:4 label="^std_enc" EVENT_ENC id= 6 fwd_id=LED_MATRIX:6 type=CC chn= 1 cc= 29 lcd_pos=6:1:4 label="^std_enc" EVENT_ENC id= 7 fwd_id=LED_MATRIX:7 type=CC chn= 1 cc= 30 lcd_pos=7:1:4 label="^std_enc" EVENT_ENC id= 8 fwd_id=LED_MATRIX:8 type=CC chn= 1 cc= 31 lcd_pos=8:1:4 label="^std_enc" # we've a single MBHP_MF_NG module with 8 motorfaders # It has to be configured for Motormix protocol! MF n=1 enabled=1 midi_in_port=IN2 midi_out_port=OUT2 chn=1 ts_first_button_id=2001 config_port=USB3 ################################################################################ # on motorfader movements EVENT_MF id= 1 fwd_id=ENC:33 type=CC chn= 1 cc=32 range=0:127 lcd_pos=1:1:5 label="^std_mf" EVENT_MF id= 2 fwd_id=ENC:34 type=CC chn= 1 cc=33 range=0:127 lcd_pos=2:1:5 label="^std_mf" EVENT_MF id= 3 fwd_id=ENC:35 type=CC chn= 1 cc=34 range=0:127 lcd_pos=3:1:5 label="^std_mf" EVENT_MF id= 4 fwd_id=ENC:36 type=CC chn= 1 cc=35 range=0:127 lcd_pos=4:1:5 label="^std_mf" EVENT_MF id= 5 fwd_id=ENC:37 type=CC chn= 1 cc=36 range=0:127 lcd_pos=5:1:5 label="^std_mf" EVENT_MF id= 6 fwd_id=ENC:38 type=CC chn= 1 cc=37 range=0:127 lcd_pos=6:1:5 label="^std_mf" EVENT_MF id= 7 fwd_id=ENC:39 type=CC chn= 1 cc=38 range=0:127 lcd_pos=7:1:5 label="^std_mf" EVENT_MF id= 8 fwd_id=ENC:40 type=CC chn= 1 cc=39 range=0:127 lcd_pos=8:1:5 label="^std_mf" # on touchsensor event (first id has been specified in the MF configuration above) EVENT_BUTTON id= 2001 type=NoteOn chn= 1 key=0x68 range=0:127 lcd_pos=1:1:6 label="^std_btn" EVENT_BUTTON id= 2002 type=NoteOn chn= 1 key=0x69 range=0:127 lcd_pos=2:1:6 label="^std_btn" EVENT_BUTTON id= 2003 type=NoteOn chn= 1 key=0x70 range=0:127 lcd_pos=3:1:6 label="^std_btn" EVENT_BUTTON id= 2004 type=NoteOn chn= 1 key=0x71 range=0:127 lcd_pos=4:1:6 label="^std_btn" EVENT_BUTTON id= 2005 type=NoteOn chn= 1 key=0x72 range=0:127 lcd_pos=5:1:6 label="^std_btn" EVENT_BUTTON id= 2006 type=NoteOn chn= 1 key=0x73 range=0:127 lcd_pos=6:1:6 label="^std_btn" EVENT_BUTTON id= 2007 type=NoteOn chn= 1 key=0x74 range=0:127 lcd_pos=7:1:6 label="^std_btn" EVENT_BUTTON id= 2008 type=NoteOn chn= 1 key=0x75 range=0:127 lcd_pos=8:1:6 label="^std_btn"   Any Ideas?   Thanks novski