TK.

Hi Chriss, yes, the slaves are also able to control a AOUT or AOUT_LC module independent from the master - I guess that the stereo effects will be great. Once I find the time, I will try such a configuration with my 4xCEM3378 filters :) Best Regards, Thorsten.

Here another preview from the MBSEQ V3 display layout - the track direction page: In comparison to the old 2x16 display layout: the new one allows to select the track direction mode directly with the general purpose buttons, which is much better when you want to select a different direction during live playing. The drawback is of course, that I had to change the menu code in a way, which makes it incompatible to smaller displays... however, no problem for all MBSEQ V2 builders I know so far, because all of them have used two 2x40 LCDs Best Regards, Thorsten.

I think that the way how MIOS_LCD_PrintBCD5 passes the parameters should work. I remember that I tested it with the LCD functions, so I forgot to do the same change with MIOS_HLP_Dec2BCD The changes were required after a change in the parameter passing between 2.4 snapshot xxx and 2.5.0 Due to such facts, I recomment the usage of 2.5.0 only, I cannot guarantee that it will work with the current snapshot builds Best Regards, Thorsten.

Hi Thomas, 1) yes, the MIDImon http://www.ucapps.de/midimon.html ;-) everything else depends too much on Windows, the MIDI API, etc... 2) this is very strange! Does this also happen when you are using one of the premade applications, like MIDIbox LC (sends/receives 14bit Pitch Bender), or MIDIbox MF (sends/receives 7bit CC) Best Regards, Thorsten.

Hi Shum, in main.asm, set: #define DEFAULT_LCD_SIZE 1 for 2x20 display mode, and replace #if DEFAULT_LCD_SIZE == 1 ; 2x20 #define DEFAULT_YOFFSET_LINE0 0x02 #define DEFAULT_YOFFSET_LINE1 0x42 #define DEFAULT_YOFFSET_LINE2 0x16 #define DEFAULT_YOFFSET_LINE3 0x56 #define CSMD_YOFFSET_LINE0 0x00 #define CSMD_YOFFSET_LINE1 0x40 #define CSMD_YOFFSET_LINE2 0x14 #define CSMD_YOFFSET_LINE3 0x54 #endif [/code] by: [code]#if DEFAULT_LCD_SIZE == 1 ; 2x24 #define DEFAULT_YOFFSET_LINE0 0x04 #define DEFAULT_YOFFSET_LINE1 0x44 #define DEFAULT_YOFFSET_LINE2 0x18 #define DEFAULT_YOFFSET_LINE3 0x58 #define CSMD_YOFFSET_LINE0 0x02 #define CSMD_YOFFSET_LINE1 0x42 #define CSMD_YOFFSET_LINE2 0x16 #define CSMD_YOFFSET_LINE3 0x56 #endif Best Regards, Thorsten.

You only need to create a new app_lcd.inc (custom LCD driver) file, and you need to select this display type from USER_Init. Other changes are not required, and the app_lcd.inc will be compatible to all MIOS based applications (even to C based applications) The statement, that it is difficult to adapt an existing software, is not true for applications which already provide exactly the number of characters and lines (e.g. for MBSEQ: 2 * 80 characters) you are trying to partitionate over multiple displays (e.g. 2 * 2x40 or 4 * 2x20 LCDs) It's difficult for applications which only provide a specific display layout (e.g. 2x16 or like MBSEQ V3: 2x80), since you have to plan new display pages, you have to understand how and where to modify the display routines, you need to know where the firmware stores the informations, etc... don't mix these requirements... Hope that it's now clear enough. Best Regards, Thorsten.

Hallo, diesen Effekt kenne ich noch nicht - wenn sowohl das Core Modul, wie auch der MIDI-Adapter mit einem Optokoppler ausgestattet sind, kann die Spannung eigentlich nicht darunter leiden. Doch vielleicht ist es ein Masseproblem? Trenne mal die Masse am MIDI Out des Core Moduls, so dass keine Masse Verbindung zwischen Core und PC besteht. Zum Testen den Audio Out des SID Moduls ebenfalls abstecken! Ausserdem koenntest Du mal die beiden Pins am MIDI In vertauschen (nur probehalber) - bei einer Verpolung wird der MIDI Out der Soundkarte naemlich kurzgeschlossen, und wenn hier die 220 Ohm Widerstaende fehlen (glaube ich nicht, aber heutzutage wird ja an allem gespart), wuerde die Spannung einbrechen Gruss, Thorsten.

Logic - weil ich Cubase unlogisch finde Gruss, Thorsten.

fixed Best Regards, Thorsten.

Under normal circumstances you don't need to create a special .h or .c file for the SFR definitions, the addresses are compatible. Just only the EEADRH register might be important if EEPROM locations >= 0x100 should be accessed, but so long you are not doing this, the pic18f452* files will work fine Yes, 0x600-0xf7f are available as additional RAM locations. And 0x3000-0xffff is the application code space Best Regards, Thorsten.

I will give you the final answer next thursday (Currently I don't find much time to answer all postings and emails...) Best Regards, Thorsten.

You can select the PIC18F452 without danger, you only need to adapt the project.lkr file (enhanced RAM/code memory) Best Regards, Thorsten.

See this answer http://www.midibox.org/forum/index.php?topic=7006.msg45321#msg45321 For somebody with programming experiences, it should be very easy to setup a compatible custom driver for 4 2x20 LCDs within 1 hour... but it can only be programmed by somebody who has build the appr. hardware... Best Regards, Thorsten.

For the 2x40 LCD option, you will read "only 8 steps are visible on screen (visible beats selected by last changed value)." This means: you will either see step 1-8, or 9-16. The application will switch to the right page when you turn an encoder or press one of the 16 general purpose buttons. Please note, that the 1 * 2x40 LCD option won't work with MBSEQ V3, only 2 * 2x40 will be supported! Best Regards, Thorsten.

I've to disagree my own answer: since MIOS SysEx responses are not tunnled (this is not possible), the endpoint will filter them out. But: you can easily change the merger mode of the last core to "forwarding point" from the debug window of MIOS Studio - just call the MIOS_MIDI_MergerSet function to the ID of the last core with WREG=0x03 Best Regards, Thorsten.

US $100 is a high price when you consider, that the core and SID kit are available in SmashTV's shop for ca. US $40, thats less than the half, and I think that even a MBHP_IIC_MIDI module, a PIC18F4620 and a wall wart won't raise the costs to more than US $50..$60. Therefore I'm currently not sure if I can recomment your venture with a good feeling, because people could assume that this is the best price for a "low-cost MIDIbox SID", which is just not correct... :-/ I've to sleep some nights of this... Best Regards, Thorsten.

this is because another thread has propably overwritten the MIOS_PARAMETER* locations in the meantime... which MIDI message is returned by the core? Btw.: in mios_lcd.inc you can find some usage example for the MIOS_HLP_Dec2BCD() function. As mentioned before: if there is a problem, I expect it in the wrapper code (still don't have time to debug this...) Best Regards, Thorsten.

It works so long the MIDI merger is enabled, regardless if it is a "normal merger", a forwarding or endpoint. Since the SysEx response is not tunnled, it is even forwarded by the endpoint. Thomas: what exactly doesn't work? Best Regards, Thorsten.

Hi, 2x24 LCDs are not enough, because the message transmitted by the host are 2x56 But: if you only need a display, then the graphical LCD solution might be interesting for you. Even a T6963C based display, which is normaly too slow for the whole application (if e.g. motorfaders have to be moved in parallel), is fast enough for your purposes. And in addition, you will get a nice MTC/Beat display, and graphical animated knobs and meters :) I suggest a T6963C based display only for your use case (display only) - they are cheap ($10...) and therefore less expensive than two CLCDs Power: yes, you can propably use the +5V from your BCF, it's worth a try Best Regards, Thorsten.

(I've currently not so much time to test this...) MIOS uses this function internally within MIOS_LCD_BCD4 and MIOS_LCD_BCD5, therefore I'm sure that it delivers the right results. But there could be a problem in the C wrapper (maybe the integer value is passed in the wrong way - this can happen depending on the SDCC version you are using) Best Regards, Thorsten.

Watchdog timer: it's configured in a way which doesn't allow to enable/disable it via software. It's always enabled, and it is serviced by MIOS within the mainloop (after USER_Tick has been called) If USER_Tick stalls longer than 2 seconds, the PIC will be reset. If your routine needs longer (this is critical, >20 mS will cause a MIDI In buffer overrun if a bulk of data is received at the same time), than you have to issue a "clrwdt" instruction in order to service the watchdog, and to avoid a reset. Best Regards, Thorsten.

Hi Jaicen, as mentioned in the last paragraph of the wishlist (http://www.ucapps.de/midibox_sid_v2_wishlist.html), I won't start to continue with planning the extension before V2 is finished. Mainly because, from my experience, I will implement much more features than written down in the list (this is for example the case for MBSEQ V3, on which I'm currently working - you will notice a lot of surprises at the end :)) Best Regards, Thorsten.

Just to say it short: keep on testing! :) Best Regards, Thorsten.

Momentan togglest Du die Variable, wenn der Taster sowohl gedrueckt, als auch losgelassen wurde. Du moechtest aber wahrscheinlich nur dann toggeln, wenn der Taster gedrueckt wurde... dies geht am einfachsten mit einem if( pin_value != 0 ) return; // exit if button has not been pressed [/code] am Anfang der Funktion Gruss, Thorsten.

Compare it with: http://www.ucapps.de/mbhp/mbhp_sid_c64_psu.pdf, a connection is not required, but it doesn't hurt However, I'm missing the 5V/ground connections, without them the logic chips won't be supplied... Best Regards, Thorsten.