TK.

Thanks, I've added the link to http://www.ucapps.de/wheretoorder.html Best Regards, Thorsten.

You could add some lines of code into the application which switches between the baudrates. I can tell you more details once I know which application you are planning to build exactly ;-) Best Regards, Thorsten.

Kein Problem, schicke mir die PICs zu, Adresse liegt in Deiner Mailbox. Serge's SysEx loader eignet sich leider nur fuer den Upload von MIDIbox64/MIDIbox64E/MIDIO128 Baenken (Konfigurationsdaten). Aber keine Panik - alles wird einfacher! Die verschiedenen Tools werden demnaechst durch das "MIOS Studio" abgeloest. Gruss, Thorsten.

...should be ok please read again what I've wrote before about the MBHP_USB module in your last postings. The upload of a MIDIbox bank doesn't work with MIDI-Ox, but with Serges SysEx loader, required upload rate: 100 bytes/s The upload of MIOS code doesn't work with Serges SysEx loader, but with MIDI-Ox. The required settings can be found here: http://www.ucapps.de/mios_bootstrap.html Best Regards, Thorsten. FAQMARKER (so that I don't have to repeat myself every week... ;-) )

I've changed the panel design of MIDIbox SEQ - it's still not final, but much more changes are not planned. http://www.ucapps.de/midibox_seq.html Best Regards, Thorsten.

In theory you could add some code to the applications in order to send CC values with the pots, but this solution won't never be so comfortable like the MIDIbox64 application. So - in consideration of your missing programming skills - it's easier for you to use a seperate core module. There is no need for an external Merger, just enable MIDIbox Link (see also http://www.ucapps.de/midibox_link.html). You can select the merger options in the menus (or from external) - connect the MIDIbox64 before the MIDIbox SEQ, select "MBLink Forwarding Point" in the MIDIbox64 menu, and "MBLink Endpoint" in the MBSEQ menu - voila! Best Regards, Thorsten.

Hi Dan, I never tried this out, so I cannot give you more detailed tips. Try some existing options. Hope that you publish your experiences some day at the Portal :) To the code in main.asm: yes, this has to be added to USER_Init... Best Regards, Thorsten.

Hallo Noskule, na, das erklaert eigentlich alles. Fuer die DIN Register kann man zwar eine Samplerate einstellen, doch leider nur in 1 mS Schritten. Fuer normale Encoder ist das auch voellig ausreichend. Schneller geht es nicht, weil die Routine dafuer nicht ausgelegt wurde. Doch bei Deinem Trackball kommen die Signale in so kurzen ABstaenden, dass sie wesentlich oefter abgetastet werden muessen. Evtl. alle 100 uS, damit auch kein 1->0/0->1 Uebergang verloren geht. Prinzipiell ist das kein Problem, doch hier musst Du wohl selbst Hand anlegen. Sprich: den Trackball am besten an zwei freie IO Pins anschliessen (ersparrt Dir den Treiber fuer das DIN Shiftregister) und in MIOS_Timer eine selbstgeschriebene Capturing Routine reinhaengen, die dann die Increments/Decrements ermittelt und an das Hauptprogramm uebergibt. Gruss, Thorsten.

Hi Pilo, the problem is, that you didn't mention which problems you are observing, therefore I cannot really give you an useful answer... However, the lcd_benchmark application demonstrates how to use TMR3 w/o interrupts. Best Regards, Thorsten.

Follow also the instructions under: http://www.ucapps.de/howto_debug_midi.html Best Regards, Thorsten.

Hi Dan, sure, you can. But note: if you are planning to build two MIDIbox LC, then every core module needs it dedicated IO pair (this is a limitation of the Logic Control protocol) or: if it is not required that the second core sends MIDI data to the host application, then there isn't a need for a MIDI chain. In this case you can just connect the MIDI Input of the second core (J11:MI) in parallel to the MIDI Input of the first core (J11:MI) Best Regards, Thorsten.

Of course, this is an important detail! Does it work, when the unused D0-D3 pins are connected to ground? Best Regards, Thorsten.

Hi, Scuzzle: of course, you've to take care that the correct baudrate is selected (it's a special menu entry in MB64/MB64E/MBMF). But there isn't a problem so long as the cables are not connected to the port which runs with the wrong baudrate. Pull-Up: two solutions: 1) cut the track between the Rx pin and R6. Use a resistor value which is much greater than R6, let's say 100k. Then it won't affect the optocoupler output signal or: 2) Don't cut the track directly at the Rx pin, but between IC2/Pin 6 and R6, so that you don't need an additional pull-up resistor. Since I would prefer method 2, here more details: Rx Pin: connected with R6 and the switch output IC2, Pin 6: connected with one switch input J11:MI: connected with the other switch input Once you get this running, please draw a schematic, add some comments and publish it at the MIDIbox Portal, since it could also be interesting for other people. Best Regards, Thorsten.

Ok, werde ich mir dann irgendwann mal anschauen und in der naechsten alpha fixen Gruss, Thorsten.

Hi Pilo, MIOS_Timer uses TMR3, thats already a 16 bit timer, and by using the MIOS_Timer_Init function you're able to control "allowed" parameters. Take care that USER_Timer is an interrupt service routine (Use FSR2, use IRQ_TMP*, etc...) Best Regards, Thorsten.

For the records: the problems are solved, he used an incompatible MIOS version (V1.4) with the MIDIbox64 firmware, which has been released after V1.4 It always makes sense to use the most recent releases, regardless if the new features are useful for you or not. Best Regards, Thorsten.

For the records: the problems are solved, he used an incompatible MIOS version (V1.4) with the MIDIbox64 firmware, which has been released after V1.4 It always makes sense to use the most recent releases, regardless if the new features are useful for you or not. Best Regards, Thorsten.

Hi Dan, Exactly. It will work once the "MIDI Merger" or "MBLink FP" option has been enabled. This can also be done from external by sending F0 00 00 7E 40 00 0D 01 00 58 28 00 01 00 00 00 00 00 00 F7 to the master core. With F0 00 00 7E 40 00 0D 01 00 58 28 00 00 00 00 00 00 00 00 F7 you can switch off the merger function again. Best Regards, Thorsten. FAQMARKER

Hi, did you also check that the 1k Pull-Up at Port J4 of the core module is connected proplery? Without this resistor the MIDIbox could switch to BankStick mode and would read random display/MIDI data Best Regards, Thorsten.

Hi, this should work - also during the PIC is running - but you have to add an additional pull-up resistor between the Rx pin and +5V in order to avoid random MIDI events during the switch phase. Best Regards, Thorsten. P.S.: the switch is only required for the Rx pin to change between the optocoupler and RS232 signal

Hi Wilba, I suggest 2.5mm aluminium, otherwise there is a high chance that this beautiful panel will bend during drilling. To the modulation matrix: since you arranged it at the left border, it makes sense to place the target selection buttons at the right side - for ergonomical reasons. You have to push two buttons to make a mod connection. E.g., to make a connection between E2 and the filter, you've to hold the filter button (with your forefinger) and to push the E2 button (with your thumb) For the envelope alternate mode I would suggest to use depth/attack/decay/curve/release parameter - in this order. Sustain is not affected by the curve, and you possibly don't want to switch back and forth between every curve adjustment (when changing the curve parameter, you have to adjust the assigned parts of the envelope anyhow - example: the decay will be much short with higher curve values, this has to be readjusted) Another hint: seppoman wrote a working VFD display driver for MIOS. His VFD runs much slower than a common LCD (ca. 4 times), but with the menu optimizations in alpha2 this issue has been solved (more intelligent display output routine) Best Regards, Thorsten.

In MBSEQ this has been realized by chaining the patterns. You can also set loop points, if you don't want to waste the pattern memory with equal patterns Best Regards, Thorsten.

You could also connect both SID modules to the core at the same time. They will play exactly the same sound, but this doesn't matter here. Just switch between the two Audio Outs. :) Best Regards, Thorsten.

Hallo, fein - somit sehe ich die Performance Probleme als geloest :) Zur "ARPSEQ Three": nein, das ist kein Performance, sondern ein SID Problem. Der Huellkurvengenerator verhaelt sich manchmal etwas seltsam. Du kannst das ueberpruefen, indem Du die Release Time bei allen drei Oszillatoren mal auf 0 zurueckdrehst. Hoerst Du den Unterschied? Den zweiten Punkt kann ich gerade nicht so ohne weiteres reproduzieren - meinst Du, dass bspw. im OSC Menue das S von "OPS" fehlen wuerde? Gruss, Thorsten.

Hi Dan, no reason for beeing confused. This is a feature for a guy who wants to switch between 6581 and 8580 w/o uploading a reconfigured application. The note about the core module is for people who design their own layout. If they also want to switch between the filter algorithms, they should not forget this pull-up resistor. Best Regards, Thorsten.