TK.

Hi Trent, it's already possible to connect a FT232 without changing bootloader and firmware, just select the MIDIbox-to-COM interface (baudrate: 38400) in the PIC ID header (bit 8 ), the FT232 can handle this. Much higher baudrates than 38400 are not recommented from my side, because this could lead to unexpected side effects in MIOS applications - a MIDI In buffer overflow could happen if data is received much faster than with normal baudrate. However, if you just want to try faster baudrates regardless of this warning, then just use the search function of your operating system (Windows: search button within the explorer), and search for "baudrate" Best Regards, Thorsten.

Kopie von http://www.ucapps.de/midibox_sid_csB.html This function activates the CC mode. If enabled, manual parameter changes from the control unit will be sent out as CC MIDI events over the MIDI Out port. If this port is connected to your computer, you are able to record these events with your recording software in order to automate parameter changes (e.g filter sweeps or portamento slides)[/code] Du koenntest erstmal Step A aufbauen, also Control Surface mit 2x20 LCD, 6 Tastern und einem Encoder. Wenn Du dann in das FIL Menu wechselst, kannst Du den CutOff mit dem gleichen Feeling ansteuern wie mit einem dedizierten Encoder fuer diesen Parameter Gruss, Thorsten.

Ja, wenn Du die CC Taste drueckst... Wenn die MBSID nur einen SID im Master Betrieb ansteuert, dann ist das ohne grosse Aenderungen in der Firmware moeglich. In MIOS_AIN_NotifyChange muss lediglich der Poti-Wert an die SID_CCIN_Set Funktion weitergeleitet werden. Eine entsprechende Anleitung findest Du hier irgendwo im Forum Fuer den Master/Slave Betrieb gab es ebenfalls mal eine Loesung, doch die ist mittlerweile nicht mehr kompatibel zur aktuellen Firmware. Doch ich vermute mal, dass Du die MBSID sowieso nur mit einem SID betreiben moechtest... Gruss, Thorsten.

You are the copyright owner of the logo, it's your decision! :) Best Regards, Thorsten.

ja - allerdings hast Du in diesem Fall ja keine Rueckantwort -> Parameterspruenge. So kannst Du auch gleich ein Poti an J5 anschliessen, das kostet dich nur 1 EUR, bietet aber echtes "analoges" Feeling weiss ich nicht, ich bezweifle es aber. Probiere erstmal den internen encoder handler aus - evtl. gefaellt er Dir besser, als Du momentan annimmst (fuer meine Beduerfnisse ist er voellig ausreichend). Gruss, Thorsten.

IIC is a synchronous protocol, which means: the master controls the baudrate. In general I don't know why you want to decrease the baudrate, maybe this is the wrong solution for your intentions...? Best Regards, Thorsten.

wenn sie eine niedrige aufloesung haben: ja. MBSID verhaelt sich eher wie ein Waldorf, eine hoehere Encoder-Aufloesung wuerde einen weiteren Mikrocontroller (und etwas zusaetzliche Programmierarbeit) erfordern. Die meisten bevorzugen den 8580 wegen des besseren Filters - dieser SID ist im C64-II (helles Gehaeuse - nicht den Brotkasten) eingebaut Gruss, Thorsten.

Hallo Marc, ich habe einen Walkthrough geschrieben, hast Du den schon gefunden? -> http://www.ucapps.de/midibox_sid_walkthrough.html Gruss, Thorsten.

mios_iic.inc - you need to insert some additional NOPs into the MIOS_IIC_Delay_600ns_Stretch and MIOS_IIC_Delay_600ns function Best Regards, Thorsten.

Hi, the PIC doesn't provide special mechanisms for measuring the load (e.g. like performance counters), but you could just count the number of Tick() calls over a certain period (e.g. one second) - than higher the counter value, than less the load Best Regards, Thorsten.

This request is: DENIED Please don't see this as a personal attack, it is my error, that I haven't spent enough thoughts on the general approach for sale requests like yours. I haven't considered the consequences good enough - e.g., the consequence, that it won't be so easy anymore to make small but incompatible changes in the circuits, module interconnections or firmware if they improve the project with an acceptable documentation effort. At the end, I would loose the motivation to do any useful changes in future (partly this is already the case). But even more I haven't considered that SmashTV and Mike, who have already spent a lot of money and effort to provide PCBs for best prices to the community, will hang on their preinvestions if other people are trying to do sell PCBs and kits as well. The only right way is to work together with these guys, to distribute new PCBs over the already existing channels, and not to go into competition with people who have already helped the community so much in the last years! And even if they are not interested in the PCB (maybe because it's too much customized to your own needs, and not flexible enough for others), you can still contribute by releasing the layout and the documentation for free - midibox.org has a lot of filespace. The board could be a nice inspiration for others to improve your work, maybe the results will inspirate you as well, and at the end we will maybe find the perfect solution, which is really worth for a PCB batch order, and where I also would be willing to support the variant in future. I've now written an addendum to the rules to make my intentions more clear: http://www.midibox.org/forum/index.php?topic=5758.msg45977#msg45977 Best Regards, Thorsten.

I planned to reply your posting once I have enough time to give you an adequate answer. But if you want to have some quick thoughts, here they are: Great to read that somebody customized the MBSEQ firmware for drums! I'm really happy about it! My intentions for sale requests were not formulated clear enough, I've now written an addendum: http://www.midibox.org/forum/index.php?topic=5758.msg45977#msg45977 Of course, it's no problem for myself when you are selling kits/PCBs for the analog circuits And for the MBHP based modules you could mention in your documentation, that they can be purchased from SmashTV and Mike if the user doesn't want to built them on a breadboard, or etch himself If a special DIN/DOUT module combination with the possibility to mount the buttons/encoders/LEDs directly is required, I guess that the best way would be to discuss this with potentional users first (how should the case look like), and thereafter maybe to ask SmashTV/Mike, if they could distribute the PCB over their shop Best Regards, Thorsten.

Addendum: In the meantime I realized, that there is no advantage for the community and for myself, when somebody unknown intends to sale MIDIbox/MIOS based projects in any form (PCBs only, kits or completely prebuilt products), when he never distributed his creations to the public for free before, when he hasn't proved over a long time, that he is willing to support MIDIbox users, and not at least: when I don't really know him personally. Some of us have spent a lot of time and money to contribute, so that they really have deserved a (mostly very small) profit for their effort. For these noble guys it is very demotivating, when greenhorns are trying to make quick money with their work. It's like a sellout. If you are now thinking, that I'm blocking interesting projects, or that I don't want to encourage user distribitions, then you're just at the wrong website, keep searching for a similar project which fits your attitudes. To say it clearly: everybody is very welcome to make contributions to the projects, so long it is for free. But if he wants to sell anything, he has to gain my trust first - this is a long term process. Best Regards, Thorsten.

It's still difficult for me to make the final decision, there are many pros and cons, some of them will be propably mentioned later once I'm very sure... However, I've an important question: are you using a legal copy of Eagle? Because the freeware version is limited to 100x80 mm size and only allowed for non-profit projects. The commercial version is very expensive. Best Regards, Thorsten.

I started the wrapper at a time where this documentation was not available... so the approach was very easy: I compiled a dummy function with the same parameter list, and had a look into the resulting .asm file. I copied the generated code 1:1 to ensure that I don't oversee any side effects. I think that the compiler uses FSR2 as a temporary pointer to ensure, that a function never returns with an unbalanced stack pointer in FSR0. However, for the C wrapper we have some potential for optimizations here - with the disadvantage, that there will also be a lot of additional debugging effort ;-) Best Regards, Thorsten.

Hi Shum, could it be that you forgot the first modification I mentioned (setting the display type) The information on LCD setting are in the main.asm file (the comments...). I know that some can be really confused, but nobody took the time for writing a user documentation into the Wiki yet... Best Regards, Thorsten.

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.