TK.

Hi Kris, thanks for this notification - I found your mail in my "spam folder", propably because of the yahoo email address :-/ Pictures will be published soon! :) Best Regards, Thorsten.

Hi Julio, it's possible without problems. But for such a primitive application, you don't really need the LCD and menu buttons, or are you planning to change the MIDI Note mapping every day? It's better to use the MIDIO128 instead, it provides up to 128 digital outputs (= gate triggers) and can be configured via SysEx Best Regards, Thorsten.

Hi Alex, it isn't so difficult to use some pins of J5 as digital input instead of output, the driver can be disabled by setting the appr. flag in the TRISA (port A pins of J5) and TRISE (port E pins of J5). Of course, once you did this, you have to enhance the application. I guess it's enough to include j5_din.inc and j5_dout.inc into one application, and to add all the hooks to the main.asm (search for the hooks in the main.asm files of both applications) Mixed digital pin/analog pin configuration: this is also possible, but not that flexible then choosing input/output behaviour. Search in the PIC18F452 datasheet for "ADCON1" (in the datasheet you will also find the informations about the TRISx registers) Best Regards, Thorsten.

Hi Carsten, for "dry" SID sounds, check the live session MP3 of Julian: http://www.monome.de/ (58 MB...) The MBFM can do very nice synthetic drums with extremely deep bases (so deep, that I have to reduce the frequency range below 63 Hz), also the modulation possibilities are very excotic (the big advantage of a synthesizer compared to a sampler). MBSID can just do the typical SID drum sounds - all geeks will notice this immediately ;-) But if you are looking for a TRxxx or natural drum replacement, both synths are not sufficient for your needs (I guess that this is what Kokoon wanted to say?) Best Regards, Thorsten.

great! even simple applications are welcome (at least as inspiration) Best Regards, Thorsten.

Hi George, just add a pull-up to the "middle pin", and a switch which activates the ground connection. So long the "middle pin" is not connected to ground, the output level of the encoders will never change (I assume, that the output pins are also connected to pull-ups) Best Regards, Thorsten.

Discussion has been continued in the german forum: http://www.midibox.org/forum/index.php?topic=5890.0

Hallo Lemonhorse, ich schaue mir das heute Abend mal an (habe gerade keinen Zugriff auf den Source Code) Gruss, Thorsten.

Hallo Klaus, ich kann es irgendwie nicht glauben, dass die beiden PICs defekt sind, nach wie vor vermute ich einen Wackelkontakt oder einen Kurzschluss auf der Core oder DIN Platine. Koenntest Du mir die PICs zuschicken, so dass ich mir die Signale mal genauer auf dem Oszilloskop anschauen kann? (Meine Adresse steht im ucapps.de Impressum) - wenns keine Umstaende macht, koenntest Du mir auch gleich die Platinen zuschicken, dann aber bitte an meine Packstation Adresse (gibts via PM) Gruss, Thorsten.

Die Antwort steht im Source Code - oeffne mal main.asm, im Header findest Du eine Auflistung der Files, die man fuer eine eigene Hardwarebeschaltung anpassen muss. Dies alles ist nicht Newbie-gerecht aufbereitet (der Aufwand fuer eine GUI basierende Konfiguration waere imens hoch), man muss sich halt durch die Kommentare durcharbeiten. Doch ich moechte Dich ausdruecklich davor warnen, dass Du mit dem von Dir geplanten User Interface nicht gluecklich sein wirst! Es gibt nicht nur "ein Attack" und "ein Decay", sondern gleich 5 - 3 Attack/Decays fuer die Oszillator-Huellkurven, und zwei zusaetzliche fuer die Huellkurven in der Modulationsmatrix, welche auf Pitch/Pulsweite und Filter geroutet werden koennen. Diese Zusammenhaenge sind Dir vielleicht momentan noch nicht so bewusst, deshalb (nochmals) der Tip, erstmal ganz langsam anzufangen: baue ein einziges SID/Core Paerchen, und editiere die Sounds erstmal mit JSynthLib vom PC (oder Mac) aus. Schnell wirst Du merken, auf welche Parameter es Dir persoenlich ankommt, und spaeter kannst Du Dir dann das User Interface ueberlegen. Wenn Du die Firmware nicht editieren moechtest, dann musst Du Dich jedoch sehr eng an das vorhandene User Interface halten, jemand anderes wird die modifikationen nicht fuer Dich vornehmen! Gruss, Thorsten.

George layouted his own boards, such problematic issues wouldn't exist if he would use the proven MBHP boards ;-) Best Regards, Thorsten.

Just use MIOS Studio to upload the MIOS .hex file, and thereafter the .hex file of the application. If you have an idea, how to improve the documentation, then please create a new page in the Wiki (wiki.midibox.org) and describe the upload procedure in your own words, in order to help other people who are also missing such explicit hints. Hundreds of people have successfully used the bootstrap loader before, but it seems that only a small number of people take care to support newbies who are not permanently reading this forum - in long term this will be a big problem... therefore: please use the wiki! Best Regards, Thorsten.

If this happens with the MB64 application, it must be a hardware issue Best Regards, Thorsten.

First upload MIOS (the operating system) Check if MIDI data is transfered correctly (a message should pop up on the LCD once it was successfull) - if not, do some troubleshooting http://www.ucapps.de/howto_debug_midi.html Tie all unused analog inputs (at J5 and AIN module) to ground in order to avoid random MIDI events Thereafter upload an application like MIDIbox64 and have fun! :) The packages can be found under http://www.ucapps.de/mios_download.html Best Regards, Thorsten.

If you want to customize the layout, you can do it in cs_menu.inc, most important functions: CS_MENU_PrintILine CS_MENU_PrintPLine Best Regards, Thorsten.

they only flicker if the LEDs are multiplexed, and interrupts are disabled for a short time (e.g. during a Flash or EEPROM write), or if the RCLK line is not connected properly So: normaly they should not flicker Best Regards, Thorsten.

Waldorf got them from www.albs.de, the knobs are still available :) Best Regards, Thorsten.

Hi, I really don't know why you guys are trying to use displays which are definitely not properly supported by the application... :-/ George talks about MIDIbox64, and not about MIDIbox SID. In MBSID, the menu interface is implemented on a very different way. There is no simple solution to change the layout for a "more-than-2-line" display. I never considered this, therefore you won't find such a switch in the code. So far the general statement in order to avoid that anybody else comes to the same idea! Inofficial statement (maybe I should delete this after one week ;-)): so long you only want to center the screen (menu items displayed in second and third line), following code in USER_Init (-> main.asm) should do the trick: USER_Init movlw 0x40 ; first line -> 2nd line of 4x20 LCD movwf MIOS_PARAMETER1 movlw 0x14 ; second line -> 3rd line of 4x20 LCD movwf MIOS_PARAMETER2 movlw 0x00 ; third line not supported by MBSID, mapped to 1st line of 4x20 LCD movwf MIOS_PARAMETER3 movlw 0x54 ; fourth line not supported by MBSID, mapped to 4th line of 4x20 LCD call MIOS_LCD_YAddressSet [/code] CS_MENU_DISPLAYED_ITEMS should be set to 5! Best Regards, Thorsten.

Lesen ist auch nicht Deine Staerke? ;-) Lies Dir bitte auch nochmal Hallucinogen's Kommentar durch - in meinem Beispiel ist naemlich ein Fehler Gruss, Thorsten.

Reason: http://www.midibox.org/forum/index.php?topic=5812.0

Hi, in main.asm, set the "USED_AS_KEYBOARD" switch to 1 This allows you to assign different MIDI events to the buttons - it has to be made in buttons.inc Best Regards, Thorsten.

I'm not a layout expert, maybe bypass caps at the power rails help? ;-) Best Regards, Thorsten.

Hi, from the technical point of view this is possible, you could already try to preload a small flash range with the MIOS_BANKSTICK_PageRead and and MIOS_FLASH_Write functions. Once this is working, you could take the required source codes in order to create the bootloader. This isn't trivial if you've never worked with assembly language before... Best Regards, Thorsten.

Hi, if the track is in "controller mode", you will have 16 MIDI controllers for each track. No, it doesn't multiply with the layers Best Regards, Thorsten.

General hint: if the MBSID audio out is routed through a sequencer, then just insert a VST based evelope follower at the beginning of the Fx line - it helps you to eliminate the background noise completely so long no sound is played. And if it supports a lookahead function, the dynamic behaviour of the sounds won't be affected. Best Regards, Thorsten.