TK.

Everybody who attend the first bulk order got a money request mail via Paypal or PM. Details are listed in the mail (number of ordered GM5/PCBs/Shipping Costs/Paypal fee/Total) - please doublecheck. Some words to the shipping costs: I had some additional expenses (e.g. shipping costs from Ploytec to me, shipping costs for 100 padded envelopes, etc...) so that I increased it by +0.50 EUR for everybody excluding the guys who get their order via Wilba. Tracking/Insurance: Insurance is only possible in conjunction with tracking. And tracking already includes an insurance for up to 35 EUR. I changed it the following way: everybody who requested insurance got also the tracking option. If insurance was requested, and the component costs were higher than ca. 50 EUR, I added the insurance option, otherwise I removed it. Best Regards, Thorsten.

What a surprise - thank you!!! :) I already considered to celebrate this anniversary somehow, but you know... I'm too busy... Even the exact "birthday" is not clear to me. Is it the day of creation, or the day I announced the finished project? I remember that I experimented with the PIC after I won a "PICstart Kit" during a Elektor design contest (10th price for a 80C31 based MIDI mapper). For me it was obvious that the uC has to send some MIDI events first, because I already owned the tools to analyse such messages. It was also the time where a friend showed me Rebirth (for those who don't know it: one of the first 303 and 808 emulations for PC) - it totally amazed me, but the mouse handling was so uggly, that I quickly combined my MIDI and PIC knowledge with the possibilities given by this software synthesizer (MIDI remote capabilities) - after one day the first MIDIbox was finished, and this was probably in June 1998. The controller was only capable of sending predefined CCs, and the pots were jittering due to the poor conversion routines, but we already had a lot of fun. I just noticed: my first song made with a MIDIbox is still available here: http://mp3.de/musik/genre/band/030303/12253/3 (Download "Do It") It seems that I haven't changed my style so much in the last 10 years ;) First announcement in the internet: an email to another friend at 1998-08-16 (sorry, german quote, use babelfish) The interesting point: 16 DM = 8 EUR for a MIDIbox, wasn't this attractive? ;) He encouraged me to announce the controller in a newsgroup - so, this was the first announcement: http://groups.google.com/group/de.rec.music.elektronisch/browse_thread/thread/dc5a7a8ef504ced8/1239b2e00294f6be After this posting another guy suggested to announce the controller at Synth-DIY, a revised version was published in another Elektor magazine, etc... ...and the rest was out of my control ;) I must say that I'm very happy to get in touch with so many people who already have, or who are starting with the same hobby. Some years ago it seemed that do-it-yourself in MIDI Controller and Synth area will die off because prices of ready-made units get cheaper and cheaper. I'm working hard to prove, that there is still more benefit to DIY a device instead of buying a ready-made one :) Best Regards, Thorsten.

Basically I'm using the same circuit like Ulrich Radig, but for the 3.3V supply I'm using the LM317 based VR circuit of MBHP_USB Depending on the weather I will find some time this WE to draw the circuit (hope for a bad weather! ;)) Best Regards, Thorsten.

I got the order today: And stuffed one module - it worked immediately; no PCB errors anymore! :) I will send the invoices via Paypal or PM during this weekend. Best Regards, Thorsten.

A new driver is available for DOG displays A precompiled test application is available in the MIOS Download section, and a schematic here They are looking sexy, no? :) And these are btw. the fastest LCDs I ever tested! (benchmark result: 1.61 mS!) And the power consumption of the backlight is extremely low, so that the 7805 of a core module doesn't get hot. Backlight colour and display variant can be freely combined - just select the colours you like. (I'm using a "EA DOGM163S-A" with black background, combined with the white backlight "EA LED55X31-W" There is enough space under the LCD to stuff some additional components, like a "DINX1": Sideview: Only Drawback I've noticed so far: currently no displays with 20 characters per line are available - it would be the ideal solution for MBSID V2. And two displays could be combined to a 40 column display. For applications which don't rely on special sizes, like MB64, MB64E, MBCV, etc... these displays are recommented from my side to everybody, who wants to give his MIDIbox frontpanel a special touch :) Best Regards, Thorsten.

Status: I haven't received the package yet Please continue to wait silently! ;) yes, thats the easiest way for all of us Best Regards, Thorsten.

Yes, I could provide some more Remote Key functions to control step recording mode. Which functions could be useful: step left/right/clear/repeat last entry?) Oops again! :-/ Was related to the last "quick" changes - also the beat LED was not working properly. It's fixed in v3_3b Should be possible (nice idea to control the tempo with a bassdrum ;)) - I've to think about a good place for the configuration. I guess that you want to define the MIDI channel as well? The metronome configuration page has some free room, maybe I will add it there. Best Regards, Thorsten.

:) I checked this and found an initialisation error in the J5_IO module (IO pins were in high-impedance state). Therefore I released a new MBSEQ version (v3_3a) and a new mios_base package (for programmers). Sidenote: MBSID V2 is probably affected as well, although I haven't noticed a problem with the gates during the last jam session - I've to doublecheck this, it's very strange (maybe PIC18F4685 has a different reset value for TRISA/TRISE) Btw.: I found out, that with a trick it's possible to record polyphonic notes stepwise, and improved this a bit in v3_3a. The normal step recording function doesn't work so well with chords, as each note of the chord will move the position pointer one step forward. But if realtime recording is selected, and the sequencer is stopped, the step pointer won't be moved, and can be directly controlled with GP encoder #6 below the "step" item. Update: polyphonic step recording supported in v3.3c Means in other words: you can select the step where you want to enter a chord without "realtime stress" ;) With v3_3a, the previous chord of a newly selected step will be cleared properly even when the sequencer is stopped. For future releases I'm planning to provide a third recording mode which allows step recording without auto-increment I came to this idea when I had to find a solution to determine the time between the taps accurately enough before starting the sequencer. :) Best Regards, Thorsten.

Algorithmic MIDI sequencing is nothing new, but this guy is a good (and funny) salesman. Btw.: 28:55 - sasha with his "selfmade" MIDI controller ;) Best Regards, Thorsten.

Ploytec has shipped the stuff today. I also got the invoice. No surprise: GM5 3.50 EUR + 19% VAT, PCB 2.50 EUR + 19% VAT Those who get the order via Swiss have to pay less VAT (details from Roger soon) If nothing unexpected happens, I will start to request money & send the first payed orders from end of this week. Deadline for paying: August 25th 20:00 PM CET - at this date, everybody in the list will be asked to buy the remaining parts (first come first serve - a bit EBay feeling ;)) Best Regards, Thorsten.

You can use the common MIOS mechanisms to upload code (or EEPROM) data. It doesn't matter, if data is located in code memory, EEPROM or a BankStick, it's only important that the tables are located at an absolute address (so that pointers compiled into the code never change) Method 1 (quick&dirty): recompile the application, and modify the .hex file, so that it only contains the data section which should be updated. Upload the .hex via MIOS Studio Method 2 (modification of #1): you could use the "mksyx.pl" script to convert the modified .hex file into .syx if you don't want to use MIOS Studio (not recommented, as MIOS Studio provides the much faster (and secure) "smart" mode) Method 3: create a Makefile which only compiles the .asm file to .hex Example: http://svnmios.midibox.org/listing.php?repname=svn.mios&path=%2Ftrunk%2Fapps%2Fexamples%2Fasm%2Fbs_xfer%2F Disadvantage of these methods: the core will be reset after upload. But this might be acceptable Alternatively you would have to program an own SysEx handler like I did in most of my "main" applications (mostly located in *_sysex.inc) - but it's some work and requires more knowledge about side effects, like collecting data into a buffer before storing into EEPROM, since the CPU won't be able to handle MIDI data during programming Program data into EEPROM from your application: just use MIOS_EEPROM_Write Best Regards, Thorsten.

Great that this issue has been clarified :) Best Regards, Thorsten.

Thank you! Nice to see that you find the new features useful :) Yes, this is already possible with the mixer. 32 CCs per page are free assignable, + Volume/Panorama/Program Change for each channel strip, and there are 128 mixer pages stored in a separate BankStick. I think that I know how to program a 8x8 matrix and integrate it perfectly into MBSEQ ;) (basically I will re-use the same routines and concepts like for MBSID V2) In difference to your version, it will be possible to use a 8x8 button matrix + the 16x4 BLM in parallel. I will do the implementation once I got a prototype board from Wilba - just in time :) Best Regards, Thorsten.

...is now available for download: http://www.ucapps.de/mios_download.html Most of the requested features of the last months (but also my private wishes) have been implemented (hope that the guys are still reading this forum ;)) -> http://www.ucapps.de/midibox_seq_changelog.html The remaining feature requests can be found at the bottom of CHANGELOG.txt Best Regards, Thorsten.

MB808 v1.0 has been released "by accident" last sunday (during the re-release of all MIOS applications). However, it works very stable since weeks, all planned features are implemented - have fun! :) Best Regards, Thorsten.

The clock signal change won't solve it (this is required to avoid doubletriggered gates) Yes, please measure the voltage between ground and pin #28? A 7812 doesn't guarantee that the SID will be supplied with 12V if the input voltage of the SID module (J1) is too low Best Regards, Thorsten.

Note that Rudger did all the work, not me! :) You will be asked by the editor if no MIDI interface is connected Maybe no interface is found at all? And which OS and Java version are you using? Best Regards, Thorsten.

Ok, there are three other possibilities for this effect: - either the filter caps are not connected correctly (bad soldering joints) - or you are using the wrong filter caps for your SID (6581: 470 pF, 8580: 4.7nF .. 22nF should lead to a good filter characteristic, 22 nF are recommented), - or the SID is powered with the wrong voltage (6581: 12V, 8580: 9V) You can measure the voltage between Ground and Pin #28 of the SID Best Regards, Thorsten.

The filter type has to selected as well, otherwise you won't hear the sound (CC#45 selects LP filter) Best Regards, Thorsten.

Some more words to the procedure: once I got the PCBs/GM5 chips from Ploytec this week, I will build one or two boards to doublecheck, that the PCB is fine now, and that the chips are programmed correctly and working under Windows/Linux/Mac. This is to avoid any trouble at your side (e.g. in worst case you would have to send back the PCBs or GM5 chips to Munich if there are unsolvable errors/failures) Thereafter I will send out the invoices/money requests, GM5/PCBs will be shipped whenever I receive the money of individual people (please allow a delay of 1..2 days) I will wait for up to two weeks, if there are still unpaid orders, all people in the list will get the chance to buy the remaining parts (first come, first serve). They will be asked via PM Best Regards, Thorsten.

No news yet, but I'm still in contact with Ploytec (due to other reasons) - don't worry, we will get our stuff Update: Response from Ploytec which I got on a sunday afternoon 5 minutes after I asked via email: they will get the programmed chips tomorrow. Order quantities: as mentioned in a change log comment, we should re-calculate the totals once the people of the first batch have been removed from the table. My own spreadsheet is already more up-to-date than the Wiki due to all the unplanned special wishes of various people :/ Best Regards, Thorsten.

Rutger implemented a Java based patch editor and bank librarian for MIDIbox SID V2, which allows you to manage/modify/create new patches under Windows/Mac/Linux remotely without the control surface Even users who built a complete MIDIbox SID might find it very useful, as this software gives a good insight into hundreds of parameters for all 4 sound engines! :) Note that the editor is still under development. Your feedback is very appreciated! Download Best Regards, Thorsten.

Maybe the oscillators are not routed through the filter? CC#44 should be set to 7, CC#45 to 1 Best Regards, Thorsten.

This is an intended default configuration. You will notice, that most of my bassline patches are using the right-channel bassline with saw waveform in upper range. Best Regards, Thorsten.

You have to install gputils and SDCC on your Mac: http://sourceforge.net/project/showfiles.php?group_id=41924 http://sourceforge.net/project/showfiles.php?group_id=599 There are also some forum articles about this topic (installation on Mac) - just use the search function to get informations about what can be made wrong ;) You don't need to do any modifications on the base package (or on any other release package) to get the compiler running. If you already changed anything, remove it (copy over the original release) to avoid side effects (e.g., you don't need to customize GPASM_INCLUDE or SDCC_INCLUDE, since the pathes to default include files are already set correctly when gpasm/sdcc is executed) Best Regards, Thorsten.