Search the Community

Showing results for tags 'midi'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Found 62 results

  1. Midibox en cascada

    que tal amigos, estoy a punto de comenzar con uno o varios midibox, mi pregunta es, es posible conectarlos en cascada? es decir, usar multiples midibox64 conectados entre si via midi in a midi out y el ultimo dispositivo conectado al PC?   espero sus comentarios
  2. Hi everybody, After have build SEQ v4 with STM32F1 with options (ethernet / 4x IIC midi / AOUT/ BLM port) no wilba CS/ homemade frontpanel (lots of DIN DOUT) some years ago... (and working very well) I'm building a new SEQ V4 with STM32F4 and Wilba CS/schaeffer frontpanel with: Line Driver transmetter 2x MIDI IO IIC Midi ethernet card from the fist seq BLM port a separate rack with Line Driver receiver ,AOUT and DOUTx4 for gates/triggers Questions: I don't find informations for the BLM port with STM32F4! someone say on a forum that the second MIDI IO will be for this purpose: what is the best way to have BLM port with STM32F4? how to wire? Is MIDI IO with STM32F4 provide 3V or 5V midi ? (does the MIDI IO stuffed with 220 ohms or 47 ohms resistors R3 R5 R8 R10?) Is the config of LineDriver is Plug n' Play? you could use the seq without Line Driver receiver or have to plug parallel port permanently? Thanks  
  3. Hi, my plug-on board dreamblaster X1 is finished now. Same pinout as the smaller S1 some use in their midibox, but much more features and larger soundbank. I sent one to Phil in Australia (3 weeks underway in post !), and now he finally made I nice review. Even though it is not a midibox, and closed source (requires NDA to buy their dev kit), I proudly want to show it to you here.  I will be starting my next project for 2016, with a dream chip, ideas welcome !! Greetings, Serge  
  4. MIDI note out from Sequencer?

    Good (late) evening, I'd like to use my sammichSID to compliment my growing Eurorack setup and I was wondering if the MIDIBOX Sid V2 was capable of sending MIDI note data out of the MIDI Out port. The Eurorack MIDI interface I'm using (the Hex Inverter 'MIDI2CV') requires a Note-on to 'wake up' (including to begin outputting Clock) and while I seem to have the Sammich set to Clock Out, I can't seem to get the MIDI2CV to recognize any note data (thus, it will not 'wake up' and output  clock pulses). I'm wondering if it is possible for the Drum sequencers to output note data, or any of the sequencers - really. Thanks, Erik
  5. (Modular?) MIDI Controller

    Hi there! I've got this idea spinning around in my head... It all started out with a bunch of Behringer's BCR-/BCF2000 which I considered to be the best controllers I could get (for the money) to control Propellerheads' Reason with. The only problem was that I just couldn't get all 4 of them running together, controlling what I wanted them to and giving me the feedback I was craving for... Then someone crossed my way and helped me build a codec (a file that tells Reason all it needs to know about the controller) which handles every 2 of them as one device, which got me the control I wanted, but still lacked proper feedback, since I wans't yet able to get access to the BCs' original functionality... Then I came up with the idea to create my very own MIDI controller, based of an improved BC-like design, and built on top of the MIDIbox platform! :D My latest spin on this idea is this: I think it would be a lot more affordable for me to build some smaller controller units one by one, than doing the whole big thing all at once! So... would it be possible to, let's say, make a controller that's just a MIDI brain with some basic/general controls, and then make some additional "modules" (e.g. one with lots of encoders, one with a bunch of faders, perhaps an additional one covered with buttons, etc...) and then connect them all to the one basic controller, which in turn provides data and power connections? I've already done some research, but although there are already some more or less modular controller platforms out there, there doesn't seem to be something like this... yet! :) I'll appreciate any kind of response, and, maybe some time, a little (more) help in development of such a system -- if only to see it it would be feasible... Thanks!
  6. Newbie help midi from daw to multi LCD

    Hi. Im new to the midibox, i got the link from a  friend. Im about to build me a new home-studio.   I got cubase and 2 behringer bcf2000 and one Presonos Masterfader.   All is working fine. But now i want to intergrade 8 to 16 lcd displays in to my desk.  I want to display vu-meters, trackname/number and any outher usefull info i can get out from the mackie-midi-out.   Iv seen some youtube-projects with the adurion and one lcd-display. but nothing with 8 or 16. If its not possible i can go with 4 lcd´s displaying sevreal tracks on the same lcd.   What should i buy. My friend said that i should get a MidiBox NG. I have 4 4x20 hdd44780 lcds at home, but with the china-prices a can buy new models if the hd44780 is a bad lcd.     So first of all i need to now what to buy. So i start in the right end.
  7. [sOLD]   Looking to sell one spare gm5x5x5 board for reasonable price (not trying to make money on it, but also not hysteric about loosing on, you know)  :smile:   It is working and once soldered back in 201?, was stored in my DIY box. I ordered many of those and used only one. Please PM with offers.        
  8. Midi Clock to DOUT

    Hey everybody   I searched in the forum as well as the NG documentation but couldn't find anything about this topic. Is there a possibility to forward the midi clock pulse or a division of it to a DOUT pin (comming either from the internal generator or an external clock through midi in)? I would like to sync an LFO to the clock.   Cheers Andy
  9. Hi all,   Please go easy on me, I am new to MIDI and Sammich!   I have built a Sammich a few months ago now, and was having problems flashing it, Rowan kindly had a look at it and between him and TK it was fixed (bad optocoupler)   Rowan flashed the MIOS and patches for me and I replaced the opto coupler, and bought 2 new SID's as the existing ones were both slightly faulty, now its up and running and the Sammich sounds great triggering the patches from the buttons on it's front panel.   Now, here comes the problem:   I have wanted to hook it up via MIDI so I can play the patches with a keyboard, which i think should be fairly straight forward based on other MIDI devices I have used.   When I hook up the Sammich to my controller keyboard I set it to send on channel 1, I also make sure in the patch on the sammich, in the menu that it is set to also use channel 1, I play the keyboard and nothing happens, I cycle through patches and make sure they are on channel 1 also, but still nothing?   I have also hooked the sammich up to fruityloops via a Umidi USB cable (as suggested by the whitelist) and set fruity to output on channel 1, now this does strange things, sometimes the patch will trigger or play randomly or sometimes it causes the sammich to cycle through patches randomly?   I have midi out on the keyboard and or fruityloops to midi in on the sammich.   I have taken it to a friend who is a bit more knowledgeable with MIDI than me, and he has had a play and thinks there may be an issue with the sammich not properly responding to the midi information, and possibly miss translating what it is receiving.   Could this be me just not knowing enough about MIDI, or is there potentially another issue with the sammich that needs correcting, like with the faulty optocoupler?   Any help appreciated, and if someone could confirm the best way to make sure it is receiving MIDI and translating it properly that would be great.   Thanks,   Kai.
  10. Hello,   I have finished building and hardware testing a sammich, but unfortunately I seem unable to flash it with any of my MIDI interfaces.   Is there anyone in the UK that is able to help me by either lending me a known working MIDI interface, or doing the flash for me if I send them the sammich?   I am unfortunately unable to source a nuesonic cable, and all 4 interfaces i've tried won't seem to do it.   Please contact me and let me know if you can help.   Many Thanks,   Kai.
  11. Issue found with Apple RTP-MIDI driver

    Hello all,   I wanted to inform the MB fourm members using the RTP-MIDI OEM that a small issue has been found with the RTP-MIDI driver in 10.8, 10.9 and partly 10.10. This issue is not critical at all but it can give you a lot of stress to try to find the root cause :hyper: The symptom is simple : under some circumstances, the MIDI communication starts only after 10 to 30 seconds after the session has been opened. The Apple driver indicates that everything is fine, but you see the first MIDI data some time after the session is opened (the MIDI data are not delayed, the MIDI communication really starts after this period, so no MIDI data being received or exchanged meanwhile)   Here is a decription of the problem: The RTP-MIDI OEM board can be a session initiator and a session listener. In other terms, it can be invited by the Mac and it can also invite the Mac. When the Mac is the session initiator (meaning that you use the "MIDI Network Control Panel"), everything is fine: when you click on Connect button, you are able to exchange MIDI data with the KissBox OEM in the next second.   When the OEM module becomes session intiator (meaning you have entered the Mac address in the KissBox Editor as a destination for the session), you will see that the Mac is being invited and accepts the invitation just after the OEM module is powered, but you are unable to exchange any MIDI data for a period around 10 seconds (I have even seen some exceptionnal cases where it was taking 30 seconds). The Apple Control Panel also becomes quite unresponsive during this time, giving you the feeling that the driver is crashed.   We have found the origin of the problem and we have a solution for it :sweat:   The root cause is a different behaviour in the clock synchronization period when the Mac is session initiator or when it is invited. When the Mac is initiator, it starts a synchronization sequence immediately after the session is opened, and the KissBox OEM is able to synchronize with this first message.   When the Mac is invited, it gets the same synchronization sequence, but from the OEM module this time. For a strange reason, the Apple driver waits until it gets something like 15 or 20 messages from the OEM until it starts accepting MIDI data. During this period, on 10.8 and 10.9 machines, the Control Panel seems stuck (in fact, it works again as soon as there are enough CK messages received) Do not ask me why the Apple driver acts like this...   This problem does not happen with the Windows rtpMIDI driver.   I have modified the synchronization sequence of the OEM, to make sure it sends enough CK messages in a short time to "unlock" the driver. This change is implemented in V2.2 of the OEM firmware. I will release it on the KissBox website probably today or tomorrow   Benoit    
  12. Hi everyone,   I have a strange problem with my STM32F4 Discovery not being able to communicate with MIOS studio.   I flash the STM32F4 with the mios32 bootloader no issues via ST link, but then if I reboot the core and connect through the left Micro-USB, the USB MIDI driver doesn't come up on either windows or macOS (so I can't connect it to MIOS studio). If I boot the core in boot hold mode, the USB-MIDI driver comes up on both Mavericks or Win7 (MIOS bootloader) the core gets recognised and can upload an application (ID=0), but when I then upload midibox_seq_v4_086 and reboot, even though it works on the displays of my MbSeq4, no USB Midi drivers again in either Win7 or Mavericks.   To test further, through boot hold mode I uploaded midio128_v3_019, reboot, and the drivers do come up and I can use the terminal, but I get 'No response from MIOS8 or MIOS32 core' (I've checked with all Device ID values, none works). If I now try to upload midibox_seq_v4_086 I get the 'Warning: no reponse from the core' message half way through and the core doesn't seem to send an upload request after booting.   I have done this when the STM32f4 Discovery board is not connected with the MBHP_CORE_STM32F4 module and it exhibits the same behaviour.   Is this midibox_seq_v4_086 messing up the USB midi drivers somehow?  Or perhaps some residual code somewhere if it connects under boot hold?   Any help is much appreciated!
  13. Hey everyone,   I bought a Kross synth from Korg a few months ago, and now use it as a live inbstrument with my own Korg EMX-1.   The Kross synth is very nice, but is too unconvenient to use live. All settings are mastered by the software, and you have to access menus, and under menus to modify anything, kind of boring... I now use the Korg Kross Editor, that allows me to controll Kross faster and easier.   I have never built a MIDI controller myself, I just started getting informed on the topic, and it seems accessible.   So here's my question, I'd like to know what you guys can tell me about building a MIDI controller that would be directly made for my Korg Kross ? Is that doable ? And how ?   Cheers everyone !
  14. Hi TK,   I have a lot of GrooveBoxes (Roland MCs, Electribes, Seq4L, MidiREX) and on most devices there is the same problem in connecting with a master clock device while receiving notes from other devices.   So i need mergers. But i want to merge all signals EXCEPT clock signals (#FA, #FB, #FC, #F8). And sometimes I like to split MIDI IN into a MIDI OUT(1) containing all data except clock signal  and a second MIDI OUT(2) which only takes the clock signals. I could do it with a big machine, but i prefer little boxes (more useful if only taking a few devices to a session).   So i struggled over your very easy to build MIDI Merger based on 16F88. I'm going to build that on stripboard anyway after my coming vaccation, but few questiones occure now:   How does it handle incomming clock signals from both inputs? (I have no plan on programming PICs - so i can't follow the code by now - this might change in future :rolleyes:   ) Are Clock signals only taken from IN 1 or first sending clock is the one who can send?   Is it easy to add a second MIDI-Out to the merger which carries only incomming clock signals?   If so i think it will be an interesting "swiss knife" for a lot of GrooveBox owners.   Thanks anyway for all your efforts to DIY community! Best regards Paul
  15. DSC00362 small

    From the album RTPMIDI_CORE_STM32

    The RTPMIDI_CORE_STM32F4 board being powered by the KissBox OEM board using the PoE (Power Over Ethernet) option.

    From the album RTPMIDI_CORE_STM32

    Picture of the first assembled RTP-MIDI CORE STM32F4 board, equipped with the RTP-MIDI OEM module, and doing the first test run.

    © BEB

  17. The NG and the DSP...

    Hello all, as I told in the thread dedicated to the RTP-MIDI compatible NG board I made, I added some expansion ports to the board, not only for the KissBox but also for something else on which I am working since a long time... It's time now to reveal what I am working on :smile:   Since a very long time, I work on the idea to ressucitate the Soundart Chameleon, and since the beginning, I am convinced that the MIDIBox NG CPU is the right base for it. For those who do not know what the Chameleon was: the Soundart Chameleon was an hardware synthesizer, built around a DSP56300 and a Coldfire microcontroller. The whole software base was completely opened, and it was possible to write your own synthesizer application. The bad thing is that Soundard went bankrupt, and Chameleon disappeared, which is a pity, considering that the idea was brilliant, and the price was affordable for such a machine. The MIDI part of the Chameleon was running under MIDIShare (a open concept, similar in many ways to MIOS), and it was responsible of loading the DSP code.   Then come the DSP problem... I program and design DSP boards since a long, long time for pro audio and music applications, and I know quite well that DSP may seem out of reach for DIY community. We are facing two problems : price and tooling. Almost all DSP uses BGA and other SMD industrial packages, making the idea of DIY board really out of reach for most of MIDIBox members. Making the PCB is not really a problem anymore, but soldering these chips by hand is most of the time impossible. Even "low end" DSP like the VLSI and the Spin FV-1 are SMD.   So I looked to two other solutions : recycling ASX/i-CON/Plugiator boards or use Analog Devices EZ-Kit boards For both of them, the cost is roughly the same (around 350 euros for a board - ouch!), but there is nothing to do at hardware level. If you think it's expensive, just take a look to the Monome Aleph.... 1400 dollars!!!! The Aleph is partially open source (hardware is closed source), and the software is still quite limited today (as far as I know, the Aleph only have one synth project for now). Even with a 500 dollars DSP board, a MIDIBox project would cost half this price (and would be compleetly open)   From a personal point of view, the EZKit are much better (more audio I/O, more interfacing possibilities, complete documentation available, software toolchain delivered with the kit), but they are bigger and you must write your own software (but that's where I come into the game, since I will provide the code and support for the community)   The ASX/iCON boards are delivered with three excellent software synths (the VST interface for them being simply awful however :sad: ), and they can be driven directly from MIDI I/O from the MIDIBox for simple projects. There is no technical documentation for these boards (I had to draw the schematics by myself, after hours and hours of investigation), and getting access to the DSP requires some modification (to inhibit the local processor and replace it with the MIDIBox board), but it's feasible   I have included in the RTPMIDI_CORE board the connector needed to access the EZKit and ASX boards, so the link will be very easy to make between the two boards (see "MIDIBox goes RTP-MIDI" topic for details about this board), and I am currently coding and testing the library for the STM32 to load firmware in DSP board (take care, Analog Device calls it a bootloader too, but it has nothing to see with MIOS bootloader :shifty: )   I just expect now that this project will get some interest from the MIDIBox community   I did not want to go into much details in this already quite long post, but of course, if you have any question... just ask (I am preparing some pictures of the first prototypes I made)   Benoit
  18. Because my Waldorf Midibay became too small for connecting all of my MIDI equipment, I went ahead and designed my own MIDI matrix / programmable patchbay. The modular MIDIbox Matrix has up to 56 input and 56 output ports and provides a smart solution for the fact that not all MIDI equipment is usually located in the same rack or corner of the studio space.   MIDIbox Matrix features break-out boxes (BOBs) that give access to 4 MIDI in and 4 MIDI out ports at a time. These are connected via 9-pin serial cables to the main unit and are designed to be conveniently placed in the back of your rack, e.g. attached to the inner sidewall of a rack enclosure with screws or velcro tape. This means that instead of running 8 MIDI cables to the MIDIbox Matrix in order to connect four synths, you only need a single, cheap serial cable from your side rack to the center point of your matrix.   Two BOBs each connect to a single I/O board, which does all the level shifting and signal refreshing. Up to seven I/O boards can be attached to the heart of the MIDIbox Matrix, an FPGA-based switching and routing logic that is controlled via a core board such as the STM32 or the LPC17.   As the system is highly modular, it is possible to start with a low port count (4) and then increase the number of available ports by simply adding I/O boards and BOBs as needed. Fully loaded, i.e. offering 56 input and 56 output MIDI ports, the MIDIbox Matrix consists of 1x FPGA board 7x I/O boards 14x BOBs plus a core board and the PCB holding the user interface.   This is how a BOB looks like in my setup:   Software-wise, this is almost ready - everything works as expected, just the PANIC button has to be implemented in the next weeks, and some code cleanup will be necessary. You can find more documentation in the Wiki if you are interested.   Kind regards, ilmenator
  19. IIC MIDI Module

    From the album Simple-MIDI-Router

    IIC MIDI Module

    © Elektrophantasten

  20. MIDI IOX4

    From the album Simple-MIDI-Router

    4/4 MIDI-IO-Modul for my Simple-MIDI-Router

    © Elektrophantasten

  21. MIDI Player

    From the album Tutorial

    low cost STM32F4 MIDI Player Erster Erfolg mit dem Tutorial #019: A MIDI Player plays from SD Card

    © Elektrophantasten

  22. MIDIbox goes RTP-MIDI...

    Hello to all MIDIBox forum members,   I am proud to announce that, thanks to Thorsten work, the last version of MIOS is now RTP-MIDI ready :rolleyes: If you do not know what is RTP-MIDI, you can take a look there :   (In two words, RTP-MIDI is transporting MIDI over IP networks, to take benefit from high speed from Ethernet, plus other new functionnalities like automatic merging/splitting). RTP-MIDI is completely license free, natively supported by Apple in OS-X and iOS, and there is a free driver for Windows too. It's also Plug&Play thanks to the use of Bonjour.   The concept is based on the use of the KissBox RTP-MIDI OEM board (, which translates the RTP-MIDI protocol into an high speed SPI based protocol (the protocol being simply the one used for USB transfers)   Of course, final users will not need to write their own RTP-MIDI application in the KissBox CPU board, I have written this part (Thorsten included the host part and tested it for the MIDIBox applications) The first version is in beta state, we are now looking to optimize it, especially the SPI speed.   We will demonstrate the board at NAMM in Anaheim in two weeks, if you want to see it operating (we are located at booth 1088 in Hall E, for those who want to visit us)   If you have any comment or question, they are of course welcome   Benoit (PS : yes, I am from KissBox, in case you are asking yourself :shifty: )  
  23.   "A simple plug-in module that converts your electronic keyboard to a "lefthand" arrangement. The Keyboard Mirror changes all the note values so that the highest notes are at the left of the keyboard, and the lowest notes to the right."   I would certainly almost kill to get this. I get the impression from the man who first made these that he does not plan to make them available ever again.   I want one. How much will it take?      
  24. Midification Johannus OPUS 230

    Bonjour à tous,   Tout nouveau sur le Forum, je viens ici dans un but précis : Je possède un orgue analogique Johannus Opus 230. L'instrument est vieillissant, et j'aimerais beaucoup le midifier afin de le faire fonctionner avec un logiciel d'orgue virtuel. Dans l'état actuel des choses, je souhaites midifier les 2 claviers, le pédalier, et la pédale expressive. Les registres seront supprimés afin de permettre plus de flexibilité quant aux différents fichiers possible d'échantillons. Peut-être seront-ils remplacés un jour par un 3° clavier.   J'ai besoin de toutes les informations possibles et qu'en l'état actuel des choses, je ne sais vraiment pas par quoi commencer pour éviter les bêtises. Vous remerciant d'avance pour votre aide.   Samuel
  25. Hilfe für Projekt

    Hallo zusammen, Ich wollte mich erstmal kurz vorstellen: Mein Name ist Jason bin 18 Jahre alt und habe ein Fachabi als Elektrotechnischer Assistent mit Schwerpunkt Datentechnik. Im Moment bin ich Auszubildende Fachkraft für Veranstaltungstechnik und bin der Mann, der das Licht schön machen soll. Ich habe schon viele Freeware Lösungen als Lichtsteuerungen ausprobiert, jedoch war keine so gute wie die GrandMA onPC von MA lighting. Die Firma stellt auch große Pulte her die Weltweit auf Konzerten und TV Shows unterwegs sind. Die Billigste Version ist eine 2Port Node, sprich ein Ethernet > DMX Konverter. Jetzt habe ich mitbekommen, dass man diese Software in Verbindung mit der Node auch per Shortcuts und Midi bedienen kann. Habe nun einige Wochen rumgesurft und und bin drauf gestoßen das man das Behringer BCF2000 mit der Software per Midi verbinden kann und auch die Rückspielwege auf die Motorfader auch funktionieren, jedoch fehlen mir noch eine Menge an Tasten zur Optimalen Bedienung. Jetzt bin ich durch google und Youtube auf Midibox gestoßen. Da ich keinen Plan von Midi habe, wollte ich hier nun mal nachfragen, ob mir jemand mal die Philosophie von dem ganzen Midibox Projekt erklären kann und mich eventuell auch etwas beraten kann zu meinem Vorhaben. Vielleicht hat sich jemand schon mal genau mit dem Konzept auseinander gesetzt der mir ebenfalls weiterhelfen kann und will. Gruß Neuling Jason