TK.

I added some more details about the arpeggiator to the manual yesterday - also the difference between Up&Down and Down&Up is described, and this evening I will propably add two or three samples. Btw.: the method, how to control the phase offset between the oscillators of a SID (a feature you will propably not find on any other SID synth since it is not natively supported by the hardware), has been invented by Wilba! :) Best Regards, Thorsten.

This topic has been moved to MIDIbox of the Week. [iurl]http://www.midibox.org/forum/index.php?topic=9161.0[/iurl]

This topic has been moved to MIDIbox of the Week. [iurl]http://www.midibox.org/forum/index.php?topic=9159.0[/iurl]

This topic has been moved to MIDIbox of the Week. [iurl]http://www.midibox.org/forum/index.php?topic=9157.0[/iurl]

The ring modulator is a SID internal feature; it works like described in the datasheet, and there is no control over the Fx level Best Regards, Thorsten.

midi_benchmark.zip (-> MIOS upload page) Best Regards, Thorsten.

Thank you! :) Wisefire: as Wilba has already mentioned, notes are played unsorted by default. Sorted order is provided as an option. There is not only an Up&Down, but also a Down&Up. I just have added UD2 and DU2 as alternative modes where the border notes are played twice. However, this is only one of many new features compared to MBSID V1 - and I must say, that programming this firmware really makes fun, as I don't have to take so many compatibility issues into account. :) Best Regards, Thorsten.

FYI :) http://www.ucapps.de/midibox_sid_manual.html Best Regards, Thorsten.

this is already possible - there are 8 16bit values implemented for customized external (or internal) parameters. They can be controlled via modulation matrix, via knobs, via MIDI, via wavetable... Best Regards, Thorsten.

Super, "00" erklaert alles: der CLCD Treiber ist noch aktiviert, wahrscheinlich wurde der PIC mit der ID 0000...00 programmiert Das laesst sich nachtraeglich aendern: nimmt die change_id Applikation, aendere in main.asm "MIOS_LCD_TYPE" auf den Wert 1, baue ein neues .hex und lade es auf - danach sollte sich das Display melden :) Gruss, Thorsten.

<sachlich>danke!</sachlich> :-) Es ist immer wieder schoen zu wissen, dass auch andere Leute mit der MBSEQ ihren Spass haben - das motiviert fuer neue Taten! :) Gruss, Thorsten.

Laut Datenblatt kannst Du V0 an den VI Pin anschliessen (-0.3..VDD - passt) Wenn Du nun am Kontrastpoti drehst, solltest Du selbst bei einem nicht initialisierten Display einen schwarzen Bildschirm sehen (man stellt das Poti dann so ein, dass die schwarzen Pixel gerade so verschwinden) Falls Du die Pixel nicht siehst -> VI checken MIOS: ist der richtige Displaytyp eingestellt? Das kann man wie folgt ueberpruefen: in MIOS Studio das Debugging Fenster oeffnen, den Reiter "Debugging Functions" anklicken, auf den Button "RAM Read" klicken, Startadresse 0x000, No. Bytes auf 0x1 Damit liest Du das "MIOS_BOX_CFG0" register aus. Bit 3:0 (die rechte Ziffer) sollte auf 9 (oder 1) stehen. Welche Ziffer erscheint bei Dir? Gruss, Thorsten.

depends on what are you planning to do with the SID. So long your synth only transfers the sound parameters to the SIDs, 16k is more than enough. Once you are starting to add features like LFOs/Envelopes/modulation, wavetables, arpeggiators, external CVs, you propably need much more. It also depends on your programming skills - if you know how to compress code and optimize the memory usage, 16k will be fine. But if you never completed such a project before, and want to develop under relaxed conditions, use the microcontroller with the biggest memory you can find. My first MBSID started with a 16k PIC16F874, in the meantime I'm using a 96k PIC18F4685 - and the firmware will propably allocate this memory completely. You really need to be more specific when asking such questions. Prophet64 runs on a 1 MHz 6502, and handles the graphical user interface as well as the two SIDs in parallel. Best Regards, Thorsten.

Da bist Du leider nicht der einzige. Deshalb eine Frage in die Runde: wie kann man den Installationsvorgang noch verstaendlicher darstellen? Gruss, Thorsten.

Hallo, je nach Hersteller kann die Anschlussbelegung des Expression-Pedals unterschiedlich sein! Am besten misst Du das vorher mal aus. Zwei Anschluesse sind fuer die aeusseren Enden des Potis. Wenn Du das Pedal bewegst, sollte sich der Widerstandswert zwischen den Anschluessen nicht aendern. Wenn Du diese Anschluesse herausgefunden hast, schliesst Du einen an +5V, und den anderen an Masse. Der dritte liefert dann je nach Stellung des Pedals eine Spannung zwischen 0 und 5V - auch das kann man nachmessen. Und dieser Pin muss nun an J5:A0 angeschlosssen werden, so dass der Core diese Spannung ermitteln, und in ein MIDI Event umsetzen kann. Wenn die Polaritaet nicht stimmt, einfach 0V/5V am Stecker (bzw. in der entsprechenden Buchse) vertauschen. Niemals Masse oder 5V an den "Schieber" des Potis anschliessen - sonst qualmts! Die restlichen analogen Eingaeneg A1-A7 koenntest Du auch direkt mit Masse verloeten (bspw. auf der Unterseite des PCBs) Ohne die 4051er muss der Multiplex-Modus deaktiviert werden (im Source Code nach "mux" suchen) Es gibt auch ein C Beispiel, in dem nur ein einziger AIN Eingang verwendet wird: http://www.ucapps.de/mios_c_send_ain.html Gruss, Thorsten.

Could it be, that one of the (unusued) DOUT pins has a short? Would it be easy for you to disconnect all other LED connections? Best Regards, Thorsten.

What should I say/write... I cannot comment this so long nobody can tell me exactly, how to reproduce this effect (best: send me the pattern and give me step-by-step instructions) Best Regards, Thorsten.

SPP has a 16th note resolution. The problem is, that the internal song pointer of MBSEQ is only prepared for 8bit. It will cost me some effort to change it to 16bit - Whomper, please let me know if it is really required. Best Regards, Thorsten.

In difference to MBSID, MBFM uses 5 characters per menu item. The main page, which displays the instruments, allocates all 2x40 characters, and you definitely want to see them all. So, there is no way to use exactly the same CS like MBSID, mainly because MBFM is a different synth (e.g. 4 FM operators instead of 3 SID oscillators...)! Only the right side of the CS (4 encoders, LED matrix and selection buttons) can be omitted, everything else is not only "nice-to-have", it's a strong requirement. Best Regards, Thorsten.

Nice ones, Buryplo! :) I added a link to this article to the MIDIbox FM page Best Regards, Thorsten.

Not sure if this is really the easier solution, as you need to program the routine which switches between the MIDI INs by yourself. 74157 would propably work, 74HC257 is a nice one, too Best Regards, Thorsten.

This topic has been moved to Miscellaneous. [iurl]http://www.midibox.org/forum/index.php?topic=9000.0[/iurl]

This topic has been moved to Miscellaneous. [iurl]http://www.midibox.org/forum/index.php?topic=9106.0[/iurl]

Are you able to test the gameport with another MIDI device? (e.g. a MIDI keyboard)? And how is your core module powered? From the PC, or with a seperate PSU? Best Regards, Thorsten.

Just for the case you have missed the info: check the 1k pull-up resistors They are required, regardless if a BankStick is connected or not. Without these pull-ups (or with a bad connection) MIOS cannot determine if a BankStick is connected or not, it will get random data. Best Regards, Thorsten.