TK.

The software as well as the hardware is "bended" ;-) The software got some small modifications, especially in the envelope behaviour (for proper accent handling) and in the filter characteristic. Oh, and in the meantime also the WT sequencer is modified - it's now a TB303 style sequencer with note/accent/slide/gate and an optional CC, up to 32 steps can be stored in each pattern, live editing and fast switch between different sequences is possible (and this all with a small number of additional assembler instructions at the right places) The hardware: I added a moog filter which is controlled from the MBSID via the AOUT module. I think for the final release it makes sense to support also the "Low-Cost DAC" which consists of a single 74HC595, a resistor ladder and a TL074 The new option makes also fun with the original SID filter (so that no hardware mods are required) Here a new example, the sequence is played by the MBSID itself, and it is synchronized via MIDI clock: http://www.ucapps.de/tmp/tb303_test4.mp3 Is anybody interested in beta-testing the new firmware? :-) Best Regards, Thorsten.

How about a "circuit bending" option in the MIDIbox SID which allows to change the characteristic of the engine? How it could sound? See this example: :-) http://www.ucapps.de/tmp/tb303_test3.mp3 Best Regards, Thorsten.

Hi, thats interesting - Snapper reported the same problem in the German forum. On the other hand, I got some mails in the last weeks from people who had no problems. Please let me some days to think about possible reasons. Best Regards, Thorsten.

Hi Steve, is your laptop stuffed with an IRDA sensor? Then it could be that it allocates one serial port. This can lead to inconsistencies between the COM number and the COM address, and "poor" drivers cannot handle with this properly, regardless if they allow to change the address or not (I had a similar problem some time ago). Solution: disable IRDA in the BIOS. Or, if the BIOS provides an option to select the COM address, try a different one Best Regards, Thorsten.

Hallo, eigentlich ist es nur beim letzten Chip notwendig, den "SER" Eingang auf einen definierten Level zu klemmen, um einen erhoehten Stromverbrauch (jeder Eingang der "wackelt", verbrauch Strom) oder gar einen Latch-Up Effekt zu verhindern. Doch dazu wuerde auch eine Verbindung nach 5V oder 0V ausreichen. Mit den Pull-Ups erreicht man so etwas wie Plug & Play. Man kann also ein DINX4 Modul betreiben, ohne es voll zu bestuecken, oder etwas an der Software aendern zu muessen (MIOS scannt in der Regel 128 Register), egal wieviele 74HC165 nun wirklich angeschlossen sind. Gruss, Thorsten.

Hallo, ich bezweifle, dass eine Aenderung der Widerstandswerte hier wirklich weiterhilft. Eigentlich sollte der LM317T eine sehr stabile Spannung liefern, und wenn er das nicht tut, ist er entweder falsch angeschlossen, oder defekt? Mittlerweile haben mir vier Leute bestaetigt, dass die Schaltung bei ihnen funktioniert - einen Schaltplanfehler kann man eigentlich ausschliessen. Es kann also nur noch an Deinem LM317T liegen Gruss, Thorsten.

Hallo, wie man die Revision am trace code erkennt, weiss ich leider nicht. Der Microchip support hat mir die nummer mitgeteilt, nachdem ich ihnen die ID zugeschickt hatte. Speicherverbrauch der Firmware: eins vorweg, ich habe ja schonmal im englischsprachigen Design Board darauf hingewiesen, dass MIOS auf diesem PIC nicht laeuft, da er bspw. noch weitere Bugs hat, die ihn inkompatibel machen (movff xx, WREG bspw.), und da der USB Speicherbereich den MIOS Bereich ueberlappt. Es waere fuer mich mit einem riesigen Aufwand verbunden, MIOS und die dazugehoerigen Applikationen mit diesem Chip (der vor drei Jahren waehrend der MIOS Planungsphase noch nicht existierte) in Einklang zu bringen. Fuer mich selbst waere es uninteressant, deshalb ist von mir auch keine Hilfe zu erwarten. Generell sind aber beliebige Basteleien denkbar, solange man Programmierkenntnisse hat, und sich zu helfen weiss (bspw. die Teile von MIOS portieren, die man benoetigt). Speicherplatz ist hier kein problem, der MIDI-USB Treiber + der USB Bootstrap Loader belegen ca. 8k, bleiben noch 24k fuer eigene Basteleien uebrig Gruss, Thorsten.

Hi Jeff, "normal" displays don't need special parameter specs, therefore no comfortable solution is available. But it shouldn't be a big problem for you to add some waitcycles (NOP) to the MIOS_CLCD_Strobe_Set and MIOS_CLCD_Strobe_Clr routines in mios_clcd.inc (begin with 5 NOPs after these labels) If 5 NOPs don't help, then the most clever solution is to have a look into the datasheets, mostly they include some timing diagrams which help to find out how a read/write transfer must look like General hint for people who found this article with the search function: this answer is related to VFD displays which are mostly much slower than LCDs, this information is not relevant for LCD displays, all known HD44780 based types are driven properly with the MIOS_CLCD driver. If you display is not working, then it's a "physical" problem (broken wires, shorts, wrong connections), and not a software problem Best Regards, Thorsten.

Very good hint! Could you please add this to the Wiki? http://www.avishowtech.com/midibox/wiki/index.php/WhereToOrder Seems that they also re-sell goods from Reichelt Best Regards, Thorsten.

This display has only a column and row driver, there is no display controller. It's like a monitor without graphic card... Best Regards, Thorsten.

SmashTV sells Bourns encoders with inbuilt switch (better to say: button) for US $1.25 Alternativelely you can use common buttons like me, they don't must be located near by the encoders, but it's just an ergonomical thing. Each host application can handle these buttons in a different manner, therefore it definitely makes sense to plan this into the design. Best Regards, Thorsten.

I had to disable the attachment feature since I'm not able to watch always for illegal stuff (especially when I'm in holidays...) Best Regards, Thorsten.

MIDIbox SEQ V2.2d can now be downloaded from http://www.ucapps.de/mios_download.html Fixed bugs: the "multiple trigger" feature should now work in all cases (I've overworked the appr. code) SysEx upload failed sometimes Best Regards, Thorsten.

This is the MIDIbox SEQ made by Ludo aka. Tatapoum - very well done! :) More pictures can be found at his website: http://www.tatapoum.net/photos/seq/?f=23

This bug is fixed in v1.7a Best Regards, Thorsten.

This bug is fixed in v1.7a Best Regards, Thorsten.

Addendum: the new LFO analog source option is maybe a better solution to utilize a joystick. But if you want to control not only the LFO targets, but also other parameters with the joystick, then the AIN extension which I developed for d2k's box is the better way (however, the LFO possibilities are more powerfull since it also allows you to control the depth and update rate) Best Regards, Thorsten.

MIDIbox SID V1.7a can now be downloaded from http://www.ucapps.de/mios_download.html Fixed bugs: patch name editor bugfix for 2x16 displays avoid crash on maximum WT rate Proper handling of SusKey (automatic portamento) when Legato is active at the same time New feature: o there is now a 6th LFO waveform which forwards analog conversion results from the first 6 analog inputs (J5 port of the core module) to the LFOs. This allows you to control the SID with analog signals The LFO Depth controls the impact on the modulation target The LFO Rate controls the update cycle - a lower rates result to very stuttering effects, the highest rate (127 -> 812 uS sample period) to a very accurate control of Frequencies/Pulsewidths/Filter Thinkable analog sources are pots, joysticks, CV outs, ... [/code] Have some analog fun! :) Best Regards, Thorsten.

MIDIbox SEQ V2.2c can now be downloaded from http://www.ucapps.de/mios_download.html Fixed bugs: the slide function is working again when the gatelength is >24 and a note is followed by another note the sequencer doesn't switch to the song menu anymore when an MIDI Clock Start event is received from external. Best Regards, Thorsten.

Hallo, die Firmware war nach einer Stunde fertig programmiert (basierend auf dem CDC Framework von Microchip), doch dann bin ich leider auf einen Silicon Bug gestossen, der den EUSART betrifft. Im Endeffekt bedeutet es, dass mit dem PIC18Fxx5x keine zuverlaessigen Transfers ueber die serielle Schnittstelle moeglich sind (hin und wieder werden nullen in den Stream eingefuegt) Naehere details: http://forum.microchip.com/tm.asp?m=85120 Nun stehe ich also vor dem Problem, dass es zwar einen Driver gibt, jedoch keine funktionierende Hardware. Und es kann wohl auch noch ein paar Wochen dauern, bis Microchip reagiert, eine neue Revision erstellt und es diese dann auch zu kaufen gibt (ich vermute mal, dass bspw. Reichelt noch Jahre die Rev3 fuehren wird) RS232 Treiberprogrammierung: da gibt es eigentlich nichts zu entwickeln, das CDC Framework, welches man von der Microchip Homepage downloaden kann, bietet bereits eine USB->COM Schnittstelle. Sie verwendet das Legacy-COM Protokoll, das von allen gaengigen Betriebsystemen unterstuetzt wird. Gruss, Thorsten.

Hi Jeff, first of all: this won't be a trivial job because the MBFM firmware is not written in a trivial way. Main focus on the cs_menu handler is not a newbie friendly programming interface, but a powerful UI which consumes so less as memory as possible. Therefore the parameter handling is not easy to understand, and it is spreaded over several files (they all begin with cs_*) I can only say: read the comments in these files, start to draw diagrams about the program flow (starting point: USER_DISPLAY_Tick in main.asm), take especially a look into cs_menu_tables.inc --- this should help. Another note: the user memory of the MBFM has nearly reached its limit (there are about 128 bytes free), you will propably not be able to integrate the VFD driver into the application itself. Instead you have to hack this directly into MIOS (you could write the code directly into mios_clcd.inc, this means: just remove the common LCD driver) Best Regards, Thorsten.

Hi Robin, yes, thats exactly the right way. Best Regards, Thorsten.

oh great, people are buying stuff an begging me for a solution regardless of the effort from my side... do I really have to answer to each posting, or wouldn't it be better to give me my time to complete unfinished plans (wouldn't this even more benefit for the community?) Joystick driver: beside of the link given by TL you should take a look into this posting http://69.56.171.55/~midibox/forum/index.php?topic=1783.0 And a general statement: if the community is not able to create a proper documentation of such "quick hacks", my motivation to publish even more solutions will go down more and more. Because I've the impression that each time I'm doing this I'll have more effort in advance than I really want. The situation could be much better if you wouldn't only "consume" such contributions, but would also give something back. We have a Wiki, we have a lot of webspace at the midibox server (e.g. for diagrams and pictures), nothing prevents you from writing docs. Best Regards, Thorsten.

Hi Ludo, I don't think that this is a bug in the sequencer. Could it be that you've selected a mono voice in your synth? Best Regards, Thorsten.

Hallo, 1.1k passt schon Gruss, Thorsten.