TK.

Hi Radek, it's already finished, but not available for public. Best Regards, Thorsten.

No, a special configuration is not required to get the buttons working. The random behaviour on stop button changes indicate, that there is a problem with the shift register connections. A troubleshooting guide for the DIN registers can be found here: http://www.midibox.org/dokuwiki/doku.php?id=din_module Hope it helps - if not, just write about your observations during the tests. Best Regards, Thorsten.

This "bug" has been declared as a feature ;-) You will find these addresses in the specification, and MBFM uses translation tables based on this spec in order to address the operators correctly. But note also, that MBFM uses the OPL3 in 4 operator mode only, 2 operator mode (which would result into more voices, but also with less quality) is not supported! Best Regards, Thorsten.

The resistances are ok, the intention of this test was, if you get 0 ohm (-> short) or a high resistance (-> ok) I don't know the typical resistance, I never take care for such details, and it differs with the used parts anyhow (as you already noticed) The transformer connections you made are still unclear to me, but the problem is, that so many transformers look so different. I cannot really help you here, only motivate to continue with experiments. E.g., you could doublecheck if the center cable is really the center cable by measuring the voltages between the 3 transformer outputs. The voltage difference between this cable and the outer should be 12V, the voltage difference between the outer cables should be 24V Best Regards, Thorsten.

I don't see an error on your PCB. Does the trouble start once the PSU is connected to the MBHP_OPL3 module, or did you measure the voltages before doing this? The +/-12/Ground tracks on the MBHP_OPL3 module can be checked very easily against shorts if you have a multimeter or similar. Just check the resistance between the tracks, or use it as a logic tester (if this mode is available), and check for unexpected "beeps" (=short) Best Regards, Thorsten.

In general please note, that live record mode currently only supports monophonic notes - so in fact only Event Mode #1 (Note/Vel/Len). Recording polyphonic notes or CC is planned for future versions (as it will require a lot of work). The usecase you are mentioning here is working like expected (I just have checked this again). You have to consider, that a) like mentioned above, only a single note is recorded, and this is the base node passed to the arpeggiator b) a loopback track should have a higher priority, so that on a step change a new note is played, before the next track plays a note based on this input. Example: transposed track#1, loopback track#2 [tt] 1: C-3 C-3 C-3 C-4 C-3 C-3 C-3 C-4 2: C-3 --- G-3 --- C-3 --- F-3 --- [/tt] The sequencer will play: [tt] C-3 C-3 C-3 G-4 G-3 C-3 C-3 F-4 [/tt] which is wrong, because the transponation is one step too late When the loopback track is located at Track 1, it will work like intended: [tt] 1: C-3 --- G-3 --- C-3 --- F-3 --- 2: C-3 C-3 C-3 C-4 C-3 C-3 C-3 C-4 [/tt] Output: [tt] C-3 C-3 G-3 G-4 C-3 C-3 F-3 F-4 [/tt] For an arpeggiator loopback, event mode #4 (Note/Note/Note) with a high clock divider value (e.g. 96ppqn/64 = 1 measure per step) is the better choice. In this event mode live recording is not working! I would say it's an imperfection, and not a bug. It's related to the way, how the LCD screen handler overlays the current menu page when the track view is temporary displayed. I'm aware that this sometimes doesn't work without artefacts in the screen, but a solution is not so easy to realize here (clearing the whole LCD screen on page changes costs a lot of time - this is a LCD hardware issue, it inserts busy cycles), and I think that the impact on the usability is low. Best Regards, Thorsten.

Any PSU which delivers a bidirectional voltage will work. You could even supply the OPs with +/- 9V or +/- 15V. Have a look into your 1U racks, maybe there is already a suitable PSU which you could canibalize? Nobody else reported an error in this schematic in the past. I don't know, what should be wrong there. Did you cross-check your circuit with the PCB of Talion? It is a nice reference! I hope that I haven't clicked on the delete button by fault. I remember that I did this some months ago in another posting when I moved my mouse under unstable conditions (on my sofa ;-) too quickly. But I noticed this immediately. What I want to say: if I removed your posting unintentionally, please don't take this personally! When did you write your posting? If it was before 2007-02-11, ca. 18:00, I'm sure that it wasn't my error... Best Regards, Thorsten.

I remember that I enjoyed your two live recordings months ago. Do you offer new ones for free download in the meantime? :) Best Regards, Thorsten.

Unfortunately yes - MIDI data forwarding is the easiest way to reproduce the EUSART bug. :-/ But the MBHP_IIC_MIDI module could be advantageous for your sequencer anyhow, as it allows you to add independent MIDI ports for different MIDI devices (no MIDI channel assignment trouble). Also the bandwidth is higher, because MIDI events can be sent to different devices in parallel. However, so long only your small PC sampler is connected, this doesn't really matter - just an idea Best Regards, Thorsten.

Please don't add the fuse to the high-voltage lines, this is too dangerous (especially when the sockets are not isolated). Only add them to the 12V lines Best Regards, Thorsten.

I think it doesn't matter, which ~ pins you select. I made a quick diagram just to ensure: By exchaning the ~ pins (difference between left and right circuit), from the electrical point of view nothing will change. It's like if you would flip the diodes at the vertical axis. Since the bridge is symmetrical, you would see "the same picture" I highly recomment to add fuses to the AC lines. A short circuit at the DC side could not only blow up the bridges, but also other components! Best Regards, Thorsten.

Look at these beautiful cases - if you haven't already found them in Artesia's Blogs: http://www.midibox.org/forum/index.php?topic=7854.0 http://www.midibox.org/forum/index.php?topic=5818.0 Combined MIDIbox SID/FM MIDIbox SEQ Beautiful! :)

And it looks extremely solid! Great! :) Best Regards, Thorsten.

Hi Matthias, yes, this was the reason. The transformer has to be connected to the AC inputs Best Regards, Thorsten.

Fast alle Befehle sind in 16bit codiert, manche auch in 32bit. Es gibt Prozessoren, die mehr daraus machen... ;-) Gruss, Thorsten.

Na das ist doch mal wirklich ein brauchbares Feature! Sobald alle Listen eingegeben sind, werde ich die Links in meine Homepage einbauen :) Gibt es dafuer auch Bonusmeilen? ;-) Gruss, Thorsten.

An dj3nk: was soll das? Dein Verhalten ist fuer mich absolut unverstaendlich! Ich bin ich kurz davor, Deinen Account zu verbannen, denn Leute wie Du haben hier im Forum nichts zu suchen! Gruss, Thorsten.

A single OPL3 already provides so many voices, that there are 4 independent instruments + 1 drum channel available. This saves you from building 4 core modules, and I don't think that you really need much more than one OPL3 in your setup. The number of knobs was my design decition, the firmware isn't prepared for more. But you can add a MB64E before MBFM if you want, the available CC parameters are documented on the website. This adds a latency of 1 mS Best Regards, Thorsten.

I like the idea, but I would vote for small prices for each category, instead of giving me money. The fact, that this will result into an interesting contest with innovative and fancy ideas, improved documentation, happy community gives me enough. :) As one of the prices I would contribute 4 CORE and 4 SID modules as can be seen in this picture: http://www.midibox.org/midibox_sid_blm_photos/05.jpg They are second-hand, but well tested over a long "burn in" period of 4 years. They were housed in a non-dusty C64 case during this time. Soldered with leaded tin, best quality components, prepared for optimized PSU circuit and MBSID V2. Mounted on a pizza box (doesn't smell anymore). And the best: they are blotted with original fingerprints of TK! ;-) SIDs and PICs, DIN/DOUT, IIC modules are not included! As it doesn't make much sense to give this stuff to somebody who already owns a MBSID, I would like to see it as a price for the best user application. The nominations could be done in a seperate forum section. Best Regards, Thorsten.

Maybe it makes sense to use a special low-drop regulator for such a project. There should be good schematics available in the web, just google for "low-drop 5v schematic" Best Regards, Thorsten.

Ok, I've added the two last features - now it's design freeze, next feature request won't be taken into account for v3.0 Exactly - your old patterns should still run like before, but it also makes sense to tweak on the parameters during live playing and to check, if the sequencer behaves like expected. All the event modes are not tested good enough, especially drum mode. I mostly use Note/Vel/Len, Chord2/Vel/Len and CC/CC/CC by myself. All event modes have to be tested with different track modes (Normal, Transpose, Arpeggiator), Scales, Directions, Progression Parameters, Trigger assignments, MIDI output ports and channels, Track Lengths, Loop points, Track chains, Groove modes, Random (Humanize) modes, Morphings, Clock divider settings, and all what I forgot to mention here (which is normaly the stuff which won't work, maybe I overlooked a certain dependency ;-)) I'm also not sure if the Song mode changes are really working reliable, and all the new stuff which has been quickly built into the firmware on John's requests... Best Regards, Thorsten.

A common design technique is to use 100 nF and elcaps ( electrolytic capacitor, directional caps) in parallel. It doesn't matter if these are 10uF, 15uF, 22uF, ... Yes, the requirements for RGB LEDs is too high, this would require additional source and sink drivers, and a software variation which inverts the outputs. You need the additional DIN/DOUT modules which are listed under http://www.ucapps.de/midibox_seq_v2.html (the hardware requirements for MBSEQ V2 are also valid for MBSEQ V3) Best Regards, Thorsten.

Ok, build #71 contains two last features for v3.0: o there is now a BankStick format menu accessible from the main menu. It allows you to re-initialise a BankStick, and to check the selected Type/Size and availability (n/a print when BankStick not connected) There is no quick-access option for this menu, so that this menu isn't easily accessible during a live session. Just change to the main menu and search for "Format BankSt." [/code] [code] o The Copy/Paste/Clr function now also works on the track configuration Just only the MIDI channel and Port will never be overwritten for your own comfort! o The Copy/Paste/Clr function now also works on the track configuration Just only the MIDI channel and Port will never be overwritten for your own comfort!

Yes, MB64E is the "better" MIDIbox controller. Especially because it can handle 128 pot/encoder events and 64 buttons within one bank. :) My website doesn't make this very clear, I would like to see a discussion about the MIDIbox variations in the Wiki. Best Regards, Thorsten.

Hi JD, where did you read the info about J6? I would like to remove it from my website, with the MIOS variant this solution is obsolete. Best Regards, Thorsten.