Hawkeye

Hola, is it a STM32F1 or F4? Which SEQ firmware version? There have been some versions which may run (too) low on memory on the F1, which might cause the crash. Accordingly, and to my knowledge, in the latest versions for F1, TK. has removed some functionality to avoid that. So, if you are running on a F1 and have not upgraded yet... :-D Edit: I just read your text "dual midi modules", which allows to deduct, that you are running on a F4... Sorry, i missed that... anything you did before the crash? E.g. SD-card access? Can you reproduce the crash? Many greets, Peter

Nice chip! If it is good enough for video signal switching, it should be easily able to cope with audio signals... :-) Please keep us posted on that project... An affordable, standalone MIDI-controlled audio switcher surely is a nice thing - I know, there have been similar mixer projects before, but this looks like a fairly simple and affordable solution... Everybody, who does not have enough mixer ports and hates switching with good old patchbay cables or needs a kind of "total recall" for patchbay wiring would benefit. Many greets! Peter

Great job! Regarding the background noise - which kind of power supply are you currently using? If you are using a low-quality switcher, then it could be upgraded... but, if you are already using a linear voltage regulator, than that should be always more noise free than any switcher. On the other hand, modern switchers have a very high switching frequency, so that they are inaudible in the audio domain, and the latest consensus is, that they are just as good as linear voltage regulators... I therefore also suspect it is either chip noise (if you are using 6581s, these are quite noisy) or indeed a ground loop inducing hum (as you suspected)... A good idea is to star-wire and avoid multiple ground "backflows" to the power supply. Other sources of noise in other MIDIboxes include cooling fans, but I have not seen any in your build. You'll fix the noise problem, the unit is looking great! Many greets and have a nice weekend! Peter

Hola, While - without feedback on that matter from either nILS or Wilba for about half a year - nobody really knows, if or when it will take place, it is safe to say, that building an original MIDIbox FM as documented on ucapps.de surely is still an option to get a MIDIbox FM :). Big efforts were made by @Sauraen in the last time to build a STM32F4-powered new variant, and @Psykhaze is planning for a different version with a bit bigger CS than the SammichFM, but a smaller CS than Sauraens leviathan (not in a bad way, but probably too expensive and time-intense to build for the standard user) CS. Methinks, there would be a big future for a new version of MIDIbox FM, if there is enough interest and an affordable CS can be designed. Fortunately, imho Volca FM (also PreenFM) are totally different from the OPL3 "signature" sound that just brings back good old DOS-game memories (Dune II, anyone? :-)) Many greets, Peter

+1, imho just get a cheap second-hand akai mpd and wire via MIDI, just as Andy suggests... I have one (MPD32) as well and it works great, as long as you only use the pads and don't expect MIDI magic from the rest of the thing :-). They also managed to get pressure sensitivity right and you can adjust to your own preferences using pressure curve configuration... You should be able to score one for less than 80€ second hand... and you can always rip it apart and put it in your own enclosure :-) In the end, this is one thing less to build, that is covered by an established manufacturer and you probably can't beat the purchase price (no way when calculating the build hours) when DIYing, so it makes no real sense - best to concentrate more on the fun stuff to build, that nobody has built before :) Many greets, Peter

Sauraen: thanks for the video - outstanding work! It will probably help a lot of people to understand the OPL3 synthesis features a lot better. And you created a really awesome control surface, this is very difficult for FM synths! Many greets, Peter

Hi Jérôme, awesome! Regarding the quartzes, best ask Sauraen - he definitely has most experience around here driving an OPL3 module from a 32-bit core! :-) Many greets and enjoy! Peter

Looking good and great choice with the STM32F4 core! :) For the UI, it probably makes sense to really test out in the Ctrlr editor, which settings are altered most often - and put these on the CS. With jojjelitos help, I am (still in the ongoing looooong process of) writing a MBNG/Programma template for the Yamaha FS1r. And I find it incredibly difficult on a FM synth to isolate the most important parameters for patch programming, even if you have lots of (encoder/knob) real estate on the CS. In that respect, I'd say: rethink the dual waveform switchers (they are kind of redundant) - but try to bring on most parameters for a single edited operator (vol, attack, sustain, decay, release, keyscale, waveform, multiplier, sustain/vib/tremolo, lfo1->vol, lfo2->vol, eg5->vol) on to the encoders/switches without any further switching. Then you can easily cycle through the four operators and adjust settings -> this should work out... If you are going for that graphical display, some things can also be nicely configured there (e.g. the algorithm selector). But prepare for a lot of work, even if it is C-based... it is not a trivial project, but you surely know that by now! :-). I haven't seen other displays than the blue ones, but haven't looked thoroughly. Also, it is more of a green-blue, it is really nice... There are also awesome 4x20 character OLEDs out there, I have one (also in blue) on an old E-MU sampler (as a replacement), but these are also available in different colors. So if you want to go for the (easier-to-code-for) character-based display route, take a look at these 4x20 character OLED offerings (also other manufactorers than newhaven offer these, but I'd somehow stick with them. It is a hate-love by now ;-)) Many greets and enjoy the weekend! Peter

Hi there, regarding the shift registers: best to look at examples of matrix/time multiplexing code, used in projects like MIDIbox NG, SEQ, ... Of course, this more easily understandable C code can be converted to MIOS8 assembly and it would be a good first skilltest to do that and build a prototype on veroboard :-). You will find corresponding code in the MB6582 sources to drive e.g. the 8x8 LED mod matrix. Using that matrix approach, you will require far less shift registers, and that's how it was done by Wilba on the MB6582 and the MBSEQ... As a general rule of thumb, you can realize an 8x8 matrix with two shift registers (8x8 pins). There are other configurations possible, of course, but at least for LED output matrices, this is recommended, as using bigger matrices, the relative "on cycle time" (load cycle) will be very short and would require certain types of LEDs or drivers... If you don't want to go the matrix route, your calculation is correct, you need one shift register input/output pin per led or switch. And two input pins per encoder. So that's quite a few of shift register ICs... Many greets, Peter

Awesome and thanks for reporting back! Many greets, Peter

Just write a forum message to SmashTV or Shuriken. They should be able to create an account, i dunno my way around the wiki ;-) Many greets and keep up the spirit. In the end, everything is possible with MIDIbox, you just need a bit of preseverance, if you are doing something special... :-) Peter

Regarding graphical displays: If you want to go totally nerdy, take the below-linked 256x64px OLED from Newhaven with 16 grey (blue) levels. It totally rocks and we now have a driver for the 32 bit MIOS :). It also fits perfectly into a 4x20 conventional LCD cutout, so this is a great candidate for a MB6582-case-clone. Be aware though, that for all kinds of funny display effects (like in the video linked), CPU is eaten for breakfast :-). Highly recommended therefore: go for the new core! You will just have more horsepower available and are futureproof. But these are only my 5 cents, if your mind is set, just follow your path! :-) https://youtu.be/gK0AkkID3hA Many greets and enjoy! Peter

Yeah, I like the idea of a MBFM in a MB6582 form factor a lot! (but it would probably need quite some modifications to the firmware (two cores, different display and ui). But then, nothing is impossible! You might find it easier to work with the "heavyweight" platform instead, if you are no PIC ASM guru :-D) Many greets! Peter

As jojjelito wrote, there *might* be a T6963C controller on the RS 7000 displays, but to confirm, someone would have to open it up and take a look. Methinks, there is a good chance, that there is, but I might be wrong. Artronic is a great place to buy modern T6963C variants with LED backlights (without EL foil)... With jojjelitos help, I managed to replace two T6963C 240x64px displays in a Kawai K5000 and an E-MU E6400 ultra for cheap (~ 30€ each) in the last years, and it is a not very difficult process. But you might need to do some hardware hacking, e.g. a) disable the EL high-voltage generator to avoid humming b) build a small pot-trimmable manual contrast control (there is a schematic on artronic how to do this) c) select the proper character height (small or large font) on the display, just solder a jumper/pad. d) find and connect a power source for the LED backlight Good luck! Peter

Yeah, das passt dann, perfektes Debugging! :-) Ich glaube, Du kannst die Noten sehen, wenn Du einen MIDI Router konfigurierst, der die IN-Ports auf einen USB-Out-Port ausgibt (der, den Du auch für MIOS Terminal verwendest). Ciao und viele Grüße, Peter

As written in the german thread, you could debug via MIOS Terminal (connect the Core via USB, start MIOS Terminal, send MIDI notes to all INs) and see, if there is inbound MIDI note data... and don't worry too much! :-) MIDI IN/OUT blinking may be some MIDI routing, or you are sending a clock signal, that is also echoed to multiple ports. Many greets, Peter

Hi, Meine fünf Cents: erstmal fertigbauen und nicht zuviel Angst! :-) Hab in den letzten Jahren auch schon so einiges verpolt - ausser ziemlich aufgeheizte Chips (insbesondere Shiftregister, aber die können das wohl ab), ist nicht viel passiert... Solange die MIDI-IN LEDs blinken, wenn MIDI-Noten reinkommen, würde ich sagen, es ist kein Kurzschluß, auch wenn das Startup-Geblinker nicht mehr gegeben ist... Ansonsten debugged es sich auch leichter mit Displays und Schaltern... Was Du auch machen kannst, ist das Ganze mal im MIOS-Terminal zu betreiben, dort solltest Du eingehende MIDI-Noten auch ohne Frontpanel sehen. Viele Grüße und ein schönes Wochenende! Ciao, Peter

Hi there, had a quick look into the datasheet, and they should work after some hacking... If you are using a new 32 bit MIDIbox core, this corresponds to some C coding and is doable, if you have some patience. On an old 8-bit core, you need to revert to PIC assembly, which results in more grey hair, but also works after some grumbling :-). You are aiming for a 6800 parallel 4-bit mode in general (so some jumper/pads need to be soldered). Newhaven also has (slightly larger) character modules that are HD44780 compatible and should init without problems, so I would recommend one of these, if it fits... otherwise you might really waste some hours for a few saved centimeters :-): http://www.mouser.de/ProductDetail/Newhaven-Display/NHD-0220DZW-AY5/?qs=sGAEpiMZZMt82OzCyDsLFJpT9hslWrFHVkGqpl0m5Z4%3d I did a fair bit of Newhaven OLED display hacking in the last years, and sometimes it works out of the box, sometimes it is a mess because of messy documentation :-) : Many greets and enjoy! Peter

You need to take care of the orientation of the LEDs. They will light up (and also be very bright), if anode/cathode are reversed. Also, make sure to control "L31" - as this one is inserted reversed to the others. Many greets & good luck! Peter

Great work! Having these boards available would really encourage people to bring their MIDIbox NGs (Programma is only a name for a given defined hardware subset) to a new level of functionality and bling :-). Andys approach already is very modular. A set of boards that were proposed above for use in a NG/Programma context might look like: [TOP] [E][E] [E][E] [L][R] Where [TOP] is one or two of Andys first listed boards with four displays. These are optional in the Programma context and would only display additional (but not vital) status information, e.g. a graphical representation of envelopes, LFOs, OSC mixer settings... [E] is one of the awesome new 4x4 encoder + 4 OLED boards. Each OLED is mounted in a 45° degree angle to allow maximum packing density. The OLEDs are really close to the encoders, partly overlapping with the encoder base (but mounted above the encoder base). The setup with 4x4x4 boards would be equivalent of the first version Programma prototype lingering around here, with 64 encoders and 16 encoder displays. It is a nice size also to control complex synths. More encoders would be possible, but it gets really confusing already to find the correct parameter with 64 encoders, even if labels are there. It is just a lot of knobs and I would personally prefer banking after having 64 encoders available for use. [L] and [R] is the bottom menu and bank selector section. The six pushbuttons are equivalent to a SCS, the encoder is the bank selector, or when in menu mode, the menu item switcher (like MIDIbox NG right now). The two displays each left and right are intended to be used for a) Menu display and encoder-current/original value display (two displays used) b) Keyboard layout of the six (circular) keys. These can be remapped to different functions when in different modes and labelled accordingly. E.g. a different 6-key layout in normal use mode and in menu mode. c) Current bank info. Big synths require multiple banks. E.g. you could have a bank for the oscillators, a bank for the filtering action, a bank for fx, ... (each bank is a set of 64 encoders). This would display a graphical label of the bank, the encoders are currently in. Turn the main encoder to quickly switch banks. Of course, these boards can also be used for other/different projects, and is not necessarily only for the NG (with Programma code extensions). It would be nice to have a quad-OLED module available in many projects, for example for MBCV.... Many greets, Peter

Thanks a lot, J! A lot of the sound is due to your great gear recommendations, especially that Polivoks is such a winner :-) Many greets! Peter

Hi there, experienced a lot of slowness with older cards, it is normal/no problem from the hardware viewpoint, They are slow, when creating "randomly" written blocks, so the speed information on the card itself (e.g. 15MB/s or 30MB/s) is never reached, that is read speed in the best case. I can recommend Sandisk Ultra in low capacities (SD, or SDHC) somewhere from 2-8GB, these are also cheap (5-8 $/EUR), just make sure you get an original, not a clone :-). I have been using a Sandisk Ultra 2GB (then a SD, not SDHC "class 4", which says nothing much, as that random write speed counts) in the main sequencer since many years - it is very reliable, easily large enough for lots of SEQ sessions and is a lot faster than others. So, I'd recommend to get an Ultra up to 16GB, please report back, if you experience a speed increase (which I think you should). Also, just as Phatline said, a reliable recommendation is this (cheapest) SD-card from Reichelt: http://www.reichelt.de/INTENSO-SDHC4G/3/index.html?&ACTION=3&LA=446&ARTICLE=83725&artnr=INTENSO+SDHC4G&SEARCH=sd+4gb It is sufficiently fast (SEQv4 create session not near 2 minutes, at max 20-30 seconds on a STM32F4) and I am using it in all other MIDIboxes (1x SEQ, 1x SEQ lite,1 x MBNG, 1x "Loopa") with no problems at all. I have not tested (or would recommended) SDXC (32GB+) cards, as the offered capacity is almost never needed. Many greets and enjoy! Peter

Hi Marc and welcome! just search the forums to look for ideas! Lots of people have built lots of MIDIboxes, the best inspiration you can get is by browsing around! Also, google helps! And when you've found something interesting, e.g. this project: http://midibox.org/dokuwiki/doku.php?id=fadercore_-_fadermodule_for_audio_daw you could always write a forum private message to the project author, to ask for the project status, if there were build problems, etc... Many greets and enjoy! Peter

Thanks, Andy! :-)

Congrats! Very cool, that you've got it up and running! :-) Many greets, Peter