TK.

no, it's not provided by MIOS, since a much better concept is planned for the future. Duggle works on an IIC driver which will allow to add multiple additional MIDI IOs to a single core (not only this, but also PS/2 keyboards, mouse, etc... ;-)) Best Regards, Thorsten.

The global channel can also be changed within the SysEx dump, but vmidibox64 doesn't support to edit the value yet (since it has been written for the PIC16F version). So, you need to wait for the PIC18F specific editor --- or you need to change the channel manually in mb64_presets.inc (search for GLOBAL_CHANNEL) of course, since the channel is saved in the dump, changes are permanent BankStick: not required if you only use the internal bank link between buttons->LED: everything configurable... (try to find more docs at my Website...) Best Regards, Thorsten.

Hi, it's prepared, but not fully implemented yet. Release date for this feature: unknown (very low priority for myself) Best Regards, Thorsten.

Du koenntest in sid_init.inc folgendes einbauen: um den zweiten BankStick zu selektieren. Irgendwann kann man den BankStick dann auch mal bequem vom Menu aus und via CC selektieren, so dass keine Code Aenderung notwendig ist. Gruss, Thorsten.

MB64. MB64E and MBMF provide a global MIDI channel, which can be changed in the menu and which overwrites the predefined channels of the sysex data. Thats the simplest way to change the channel - but of course, there are also other ways ;-) Best Regards, Thorsten.

Hi Frank, nice to hear that MIOS motivates you to learn PIC programming :) Is it enough info for you when I just describe how it works in principle? You have to enlarge the AIN_ACTIVE_VALUES array to more than 64 entries. Currently it's located to 0xc0-0xff, but for more entries it's better to shift the base address to 0x100, so that up to 256 entries (0x100-0x1ff) can be accessed without much more programming effort. Now you need to add something like a group offset to the pointer which addresses this array within USER_AIN_NotifyChange). The offset is 0x40 (64) for 4 groups (when 256 entries are available). Example: replace ;; prepare pointer 1 for active value entry lfsr FSR1, AIN_ACTIVE_VALUES_BEGIN movf AIN_POT_NUMBER, W addwf FSR1L, F ;; now we can access the active value indirectly via INDF1 by ;; prepare pointer 1 for active value entry lfsr FSR1, AIN_ACTIVE_VALUES_BEGIN movf AIN_POT_NUMBER, W addwf GROUP_OFFSET, W addwf FSR1L, F ;; now we can access the active value indirectly via INDF1 The offset can be: 0x00, 0x40, 0x80, 0xc0 (if 64 pots are connected) Example for 16 pots: 0x00, 0x10, 0x20, 0x30, ... Second change: the USER_MPROC_NotifyFoundEvent has to go through 256 entries instead of only 64 Third change: you need to one or more buttons for changing the group offset Thats all Best Regards, Thorsten.

Hi, How do you access this variable? Did you take the special addressing for registers above 0x7f into account? See http://www.ucapps.de/mios/mios_ram_handling.txt It's very important that you are working with the BSR and with the BANKED flag in this cased, otherwise it isn't much surprising that anything else (like the display) crashes, shows random numbers or is doing something totally unexpected. Additional question: do you see the random characters only after your modification, or do you already see it with the original release? Best Regards, Thorsten.

New contribution by Ofir: http://logo.midibox.org

does the same happen when you replace ;; print rec/solo/mute status at 0/0 SET_CLCD_RSM_MSG 1, 0, 0 ;; print select status at 0/1 SET_CLCD_SEL_MSG 1, 0, 1 by ;; don't print rec/solo/mute status SET_CLCD_RSM_MSG 0, 0, 0 ;; don't print select status SET_CLCD_SEL_MSG 0, 0, 0 in the LC_CLCD_Init_Page0 function? (-> lc_clcd.inc) If it doesn't happen again, then a possible reason could be that Cubase updates the Mute/Solo/Select/Record status LEDs more often than Logic and this could stress the application too much. A solution: use of the same update algorithm like for MIDIbox SID and MIDIbox SEQ - but this is something which has to be integrated by myself (too complicated for programming beginners - even to explain how it works ;-)) But please ensure that this is really the reason before I have to do all this effort. Best Regards, Thorsten.

...just to ensure that you won't miss these great designs: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1079994721 http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1079994325 http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1079993159

PayC is the first guy who finished his MIDIbox SEQ V2 just one week after the official release. What a great design!!! Are you sequenced? :-)

Ooops - He did it again! Based on experiences with his sensational 2 x MIDIbox LC design (http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=gallery;action=display;num=1050012551), Axel redesigned his MIDIbox completely to a 24 motorfader device (1 master LC, 2 slave LCs). Hope that he will find the time to answer all your questions! :-)

ToFiC sent me these pictures some weeks ago, but I haven't found the time to integrate it into the MIDIbox gallery yet. On the other hand I don't want to wait any longer to introduce his great design! Well done! :) (more pictures can be found under http://perso.wanadoo.fr/kasper.korrils)

I've no idea, since you never mentioned which application your are using. With MB64E you've up to 128 encoder entries, they have to be referenced with the functions under mb64e_fsr.inc Best Regards, Thorsten.

Hi Thomas, could it be that you haven't found the MIOS bootstrap loader page yet? It describes the required steps for the code upload: http://www.ucapps.de/mios_bootstrap.html It's simpler and less error-prone than using the JDM - and especially: it's much faster! Therefore this is the only way I'm suggesting on my website - everything else would lead to an immense amount of additional support effort. Once you've learned how to program a single MIOS core via MIDI, you will be able to program the other cores within 5 minutes - believe me ;-) Therefore I don't understand why parallel programming would be required (btw.: it works, but only with expert knowledge) For the SID application you want to assign unique MIOS device IDs as well as unique SID device IDs to the 4 cores. See also http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=troubleshooting;action=display;num=1075154388;start=4#4 And if the MIDI connection shoudln't work, here another useful page: http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

Hi, I haven't noticed such a problem with my display, which is 4 times slower then a CLCD, therefore I still assume it isn't a software problem (buffer overrun or whatever), but an electrical problem. The host software only updates small pieces of the display view when it has been changed. This explains, why random characters are still visible. You could check, if this was a problem with the MIDI In line or with the display lines by changing the display page. This refreshes the display. If random characters are still visible, you know that the connections to the LCDs are not affected. Thereafter you could check if the same problem appears when Motorfaders are disabled (I guess that you already know the MF_ENABLED switch in main.asm) -- if no random characters appear anymore, you know that the MF module influences the core voltage (and especially the core supply voltage) Best Regards, Thorsten.

Hi, you've connected the encoder to the pins which are normaly used for the menu navigation. I guess that you haven't adapted the MB64E setup to your hardware, no? The problem is that I currently haven't time to explain the setup detailed enough, so maybe somebody else can help? It would especially be helpful if somebody could write down some step-by-step instructions for the MIDIbox configuration, because it seems that the comments in the source files are too confusing for non-programmers. Jimminy: in the meantime you should try the MIDIO128 application. If this application sends multiple MIDI events with a single push on a button, you've definitely a hardware problem. If it sends a single event, you've a configuration problem. Best Regards, Thorsten.

Hallo, die Probleme mit dem Filter kann ich bestaetigen - einige 6502 klingen nach 15-20 Jahren nicht mehr so toll. Aber der 8580 ist sowieso der bessere SID. :) Das Oszillator-Problem ist mir neu. > nachdem ich meine midibox sid noch immernicht zum laufen gebracht ich habe Dir bereits vor zwei Wochen angeboten, dass Du mir das Core/SID Modul einfach mal zuschicken kannst... nachdem ich soviel Zeit investiert habe, um Dir beim Debuggen zu helfen, moechte ich unbedingt mehr ueber die eigentliche Ursache wissen. Nich zuletzt, um anderen Leuten mit aehnlichen Problemen passende Ratschlaege geben zu koennen, ohne die ganze Prozedur noch einmal durchziehen zu muessen. Gruss, Thorsten.

Hallo, ist das Patch Format denn irgendwo dokumentiert? Dann wuerde ein simples (Perl) Script ausreichen, um die Sounds in das MIDIbox SID Format zu konvertieren. Das gleiche gilt uebrigens auch fuer die SIDstation (die Beschreibung der SysEx-Struktur kann man von der Elektron Homepage downloaden) - doch leider hat sich bisher noch keiner gefunden, der die Arbeit uebernehmen moechte. Gruss, Thorsten.

Hallo, das Protokoll ist im englischen User Manual beschrieben, und das kann man irgendwo auf der Emagic Seite downloaded (weiss leider auch nicht mehr, wo genau - ist schon etwas her...) Gruss, Thorsten.

Chriss' hint is very important - in my own MBHP_AOUT layout I will take care about multiturn trimmers, because it's too difficult to calibrate the output voltage with a common pot. Balanced outs: thats a new feature especially for synths with -4V/4V inputs (like Kobol). I will add some more words about this extension once I find the time! (currently I'm very busy@work, so - not before end of next week...) This extension isn't required for common analogue synths, so just ignore it if you haven't heart about balanced CVs before. Best Regards, Thorsten.

Hi, there is a special meta event which is prepared for this, the answer is somewhere in mb64_meta.inc, mb64e_meta.inc or mbmf_meta.inc, depending on the MIDIbox you are planning to build Best Regards, Thorsten.

And who checks the AOUT schematic??? Just yesterday I found another bug (Ry/R_p have to be connected to E-!) New version can be found here: http://www.ucapps.de/mbhp/mbhp_aout.pdf And there is now also a small extension for a balanced CV output (e.g. -5..5V) http://www.ucapps.de/mbhp/mbhp_aout_balanced_cv.pdf Best Regards, Thorsten.

Hi Thomas, I hope that this picture shows exactly, where the MIOS ID has to be specified: "142" is just an example!! Your IDs: 00 01 02 03 Best Regards, Thorsten.

Spacing between tracks means the clearance between those funny copper lines. It makes sense to visually check if they are too near together (high risk for shorts). RCLK and SCLK are the clock signals between J1:SC -> J2:SC and J1:RC -> J2:RC of the DINX4 module. See also the schematic http://www.ucapps.de/mbhp/mbhp_dinx4.pdf Sometimes people reported exactly the same problem, and the reason was mostly a short circuit between these tracks. So maybe this is something which could be improved in the PCB layout to reduce the failure rate... Best Regards, Thorsten.