TK.

MIDIbox controllers are going to get attractive for artists :) Sasa wrote:

Das Gehaeuse ist nach einer Woche bei mir angekommen, es macht einen stabilen Eindruck, und was fuer mich wichtig ist: an der Front ist nach oben/unten hin genuegend Platz fuer ein LCD Ob sich die Rueckseite gut bohren laesst, wird sich dann demnaechst zeigen. Mir persoenlich ist die U-Form ganz recht, ich habe naemlich auch keine Werkstatt, vor allem keinen Schraubstock, kann das Gehaeuse nun aber (im zusammengebauten Zustand) beim Bohren mit den Knien festhalten ;-) Gruss, Thorsten.

Please upload the code again with the latest MIOS Studio version tomorrow, just to ensure that it is complete - would be bad, if you miss one of the new features :) Best Regards, Thorsten.

Hi, I would propose to play a little with the JSynthLib based editor, it gives you a good impression about all the parameters, and you can already control your MBFM w/o any control surface in order to play with the parameters. I think that I don't need to answer here, since my workflow is described in the user manual :) Best Regards, Thorsten.

Hi Matteo, just use the latest MIOS Studio release, it got an update especially for PIC18F4620 which is required when uploading code beyond 0x8000 Best Regards, Thorsten.

Thanks! I changed this in seq_scale.inc, a new build will be available soon Best Regards, Thorsten.

With the current snapshot it's already possible to assign 8 BankSticks to different functions. 64k EEPROMs (24LC512) are stongly recommented, but 32k types are also working. One is used for Song Mode, another for Mixer maps, the others can be used as pattern storage. The configuration has to be done in setup_mbseq_v3.asm, here the default mapping: ; BankStick Mode & Allocation Map ; Each BankStick (CS0..CS7) has an own entry ; Set the value to: ; 0: ignore BankStick which could be (or is) connected to the CS address ; 1: if a 32k BankStick (24LC256) is connected and should be used as Pattern Storage (64 patterns) ; 2: if a 64k BankStick (24LC512) is connected and should be used as Pattern Storage (128 patterns) ; 3: if a 32k or 64k BankStick is connected and should be used as Song Storage ; only the first 32k are used, so there is no advantage on using a 24LC512 here. ; 5: if a 32k or 64k BankStick is connected and should be used as Mixer Map Storage ; only the first 32k are used, so there is no advantage on using a 24LC512 here. ; NOTE: only one BankStick can be used as Song Storage, only one for Mixer Maps ; If no entry with "mode 3" is defined, Song mode will be disabled. ; If no entry with "mode 5" is defined, there will only be one Mixer Map which cannot be stored ; If a BankStick is not connected to the MBSEQ, the appr. entry will have no effect #define DEFAULT_BANKSTICK_MODE_CS0 1 ; 32k #define DEFAULT_BANKSTICK_MODE_CS1 1 ; 32k #define DEFAULT_BANKSTICK_MODE_CS2 5 ; Mixer Map (using CS2 to ensure compatibility with Atmel EEPROMs which only provide 4 CS addresses) #define DEFAULT_BANKSTICK_MODE_CS3 3 ; Song mode (using CS3 to ensure compatibility with Atmel EEPROMs which only provide 4 CS addresses) #define DEFAULT_BANKSTICK_MODE_CS4 1 ; 32k #define DEFAULT_BANKSTICK_MODE_CS5 1 ; 32k #define DEFAULT_BANKSTICK_MODE_CS6 1 ; 32k #define DEFAULT_BANKSTICK_MODE_CS7 1 ; 32k [/code] Best Regards, Thorsten.

It's very strange, that the state of the backlight changes. It should work totally independent. It's just a LED, so when you swap B+/B-, the LED won't turn on - but thats all. It should not dimm It's hard to analyse, if the LCD has been destroyed. With some LCDs this can happen very quickly when the plug is inserted the wrong direction, but as you've already mentioned, this wasn't the case... so, I cannot really help here :-/ Best Regards, Thorsten.

Yes, thats correct. By doing so, IIC1 will also be the default port, and you will be able to upload code through this MIDI Out Best Regards, Thorsten.

Hi Robin, wow, this special behaviour of MIDI-Ox on SysEx buffer overruns was new to me! Good to know! Best Regards, Thorsten.

Hi, there are 6 different modes, they can be assigned individually to the encoders, and each mode can send Notes. So, just select "Absolute Mode" for one of the encoders, and assign a note event. Best Regards, Thorsten.

Hi Sebastian, I've planned to implement a small user interface once I found a good 19" case which allows me to add a 2x40 LCD, because I want to add a MIDI status display as well. But it will be a very propritary solution for myself, the mapping still has to be programmed, only constants of this mapping will be changable via (maybe) 8 button/LED combinations (e.g. CC Filter for MBSEQ->PC Path On/Off, or forcing MIDI channel of keyboard input to Chn.#16 On/Off, or mapping CC's from the MIDI keyboard to other CC numbers On/Off) So, just go for your own user interface and publish it in the Wiki! I really like it, when people document their modifications, this could be inspirative for others to do more changes. Best Regards, Thorsten.

When you read the posting, you will notice that the box has been renamed to MIDIbox UC The Wiki page has been changed accordingly Best Regards, Thorsten.

Es wurde nicht direkt eingestampft, die 5x2 USB Firmware schlummert noch undokumentiert auf meiner Festplatte. Ich verwende sie jedoch nicht, da der Windows Treiber nicht Multiclient-Faehig ist, stattdessen verwende ich die Hardware nun als MIDI Router ohne USB, und dieses Projekt schlummert undokumentiert auf der MIOS Download Seite, wird von mir jedoch auch wirklich verwendet und ist im Vergleich zu USB sowieso die bessere Loesung wegen der niedrigeren Latenzzeiten. Jemand aus dem Forum wollte eigentlich einen alternativen Windows Treiber schreiben, da hat sich jedoch lange nichts mehr getan - scheint also nicht trivial zu sein. Und mit Windows Vista wird sowieso alles anders - der Supportaufwand waere einfach immens, deshalb empfehle ich, MIDI Interfaces von Leuten zu kaufen, die dafuer bezahlt werden - das spart mir ne Menge Stress... Gruss, Thorsten.

The mixer map is fully implemented now. And I finally found a tricky solution how to improve the editing in event mode 5 (Vel/Vel/Vel) - it works like on a TRx0x style sequencer now, up to three drum lines are stored per track o Drum Mode is completely implemented now. It gets active with Event Mode 5 (Vel/Vel/Vel) or 8 (Vel/CC/CC) In Mode 5 three different drums can be played per track In Mode 8 one drum can be played + 2 CCs for sound modulation Notes are constant values and defined in the event menu as well. In Drum mode the trigger layers have a special behaviour: when a trigger layer is not assigned to any function (especially not to gate!), then the trigger button will modify the velocity instead. The GP LEDs will lit when velocity of a step is != 0 Sounds complicated, but the result is just a TRx0x like handling! Proposal for a quick try: change to EVENT menu, select Mode 5 (Vel/Vel/Vel), and press the button below "COPY PRESET" Now you can control three different drums with Note Layer A/B/C And you can control the gate with the non-assigned trigger layer A, Accent with trigger layer B, Roll with trigger layer C Limitation: the trigger layers (excepting gates) are applied on all three notes - e.g., if accent is activated for a particular step, all three notes of this step will be accented. Another hint: save your favourite setups in special patterns (e.g. into a seperate BankStick) to get a quick access to such personal presets. [/code]

Hi Andrew, it sounds ok Best Regards, Thorsten.

Hi SounDuke, I cannot say so much about this topic without discussing this with a lawyer ;-) Just mention, that you built the controller by yourself based on on plans from midibox.org You don't need to highlight this in each second sentence, but at least a reference to the sources one time would be a respectable way. And of course: I would be happy if you could send me article scans, CDs, videos, etc... where my projects are mentioned :) Best Regards, Thorsten.

Hi Robin, when invalid or incomplete MIDI events are sent, MIDI-Ox displays more bytes than really received. It could be, that the code sends only the MIDI status (0xb4, 0xb5, 0xb6, ...), but not the remaining two bytes (CC number and value) Best Regards, Thorsten.

Yes, I just use a MBHP_AOUT module (MBHP_AOUT_LC works as well in the meantime) in order to control the analog filter. Beside of the CEM filter, I've a DIY moog style filter as well. In MBSID V1, the CV output just follows the CutOff/Resonance, accordingly the internal filter of the SID should be switched off. In MBSID V2, a free CV output mapping will be possible Best Regards, Thorsten.

In MBSID V1 you have to use the split keyboard function in order to assign the oscillators to different keyboard zones. This allows you to play them over a single MIDI channel seperately. In MBSID V2, there will be a special poly mode (-> see Wishlist where the details are explained) Best Regards, Thorsten.

the mixer works totally independent from the sequencer, you can assign any ports/channels/... you want. You can even control synths or analog outputs which are not played by the sequencer, or you can use two, three or more maps to prepare the whole setup. Of course, they are free assignable for all mixer tracks seperately. E.g., instead of Reverb and Chorus for all tracks, you could create a mixer map with the most favourite CC's of your synths. In order to improve the handling, I've moved these two special pages to the mixer utility menu (press SELECT button). Assignment settings are not directly selectable anymore with the datawheel, I think that this is better for live usage. For me it was just a 4 hour hack, but it was planned since months, and finally I found a good way how to program this without wasting too much resources. I don't think that this is a problem in the sequencer, Program Change uses the same code as all other parameters to select the output port. Could you please post a RAM dump from 0x300, size 0x80? (such a RAM dump can be made with MIOS Studio, just open the debug window and select the RAM read function) This could help me to understand, which configuration you are using exactly. In general the mixer map should be fully functional now. And drum mode (TRx0x style editing of Vel/Vel/Vel tracks) as well :) Best Regards, Thorsten.

I don't think so, my own MBSID is connected via the MIDI router to the sequencer. The MIDI router itself uses MBHP_IIC_MIDI modules as well, so the hardware is similar. The device ID is not related to MIDI channels Best Regards, Thorsten.

Hallo, du weisst gar nicht, wie passend dieser Tip gerade kommt, denn ich aergere mich momentan ueber das verzogene Gehaeuse meiner Button/Duo-LED Matrix. Ausserdem bin ich auch mit dem 1 HE Gehaeuse von Pollin nicht zufrieden (das war eigentlich fuer meinem MIDI Router vorgesehen), da die Laschen hinter der Frontplatte so breit sind, dass kein LCD mehr durchpasst. Habe mir gerade ein 1 HE Gehaeuse mit 170 mm Tiefe bei Benkler bestellt, um es mal anzutesten. Werde berichten, und gegebenfalls den Link auf meine Homepage setzen. Gruss, Thorsten.

Keine Ahnung, ich habe noch nie einen Doepfer Controller in den Haenden gehalten. Ich kann mich erinnern, dass der Pocket Control zu der Zeit rauskam, als ich die erste MIDIbox in der Zeitschrift Elektor veroeffentlicht habe, das war im Jahr 2000. Schon damals hatte die MIDIbox mehr Features (bspw. den Snap Modus). Mich wundert es nicht, das die Dinger nicht mehr verkauft werden... who cares? Gruss, Thorsten.

You will find some tips here: http://www.midibox.org/forum/index.php?topic=7853.0 and in various other articles within the troubleshooting section. All errors and analysis tips which ever have been made are collected there (and some in the MIDIbox SID section, initiated by people who started the topic in the wrong section - sorry for that, don't know how to handle this w/o the help of an additional moderator) Best Regards, Thorsten.