TK.

Would also be interesting to me. I'm sure that I could help you, but I'm not sure for what you are planning to use a font, and which format would be adequate Best Regards, Thorsten.

Thanks for asking before! Ok from my side, just offer the components in the fleamarket section Best Regards, Thorsten.

Yes, you can use the same functions for a 64k EEPROM, and no - MIOS doesn't format a BankStick, this has to be done by your application. Just define a "magic number" (e.g. 0x47, 0x11 written to 0x0000 and 0x0001), and check for this value. If you get a different value, you know that your BankStick hasn't been formatted yet. Initialize it with some useful values, write 0x47 0x11 to the specific address - done Best Regards, Thorsten.

There are more relative modes provided, not only Inc/Dec, e.g. 40 +/- Speed, which is supported by software of Native Instruments Best Regards, Thorsten.

...this is what I'm currently try to find out with your help... Propably you misunderstood me. With connecting to ground I meant to connect the Vs (0V) pin with Pin 27 of the SID socket with a cable when the SID is removed. Thats a very easy, but interesting check, as this would tell me if the problem is more located in the pre-amp stage, or of it is an issue with the SID itself. Another test which would be interesting: stuff everything, make sure that the testtone application outputs a proper sound, upload the MBSID V1 application again and send CC#7 to the SID in order to vary the volume. Do you hear differences at low/high volume? Best Regards, Thorsten.

So, you see the message "Test LCD X-Cons.", and on the second line "Pin: D0" on the LCD? Fully written this means "LCD Crossconnection Test. Pin D0" On the other hand: if you see this message, your LCD works ok and you don't need to do any checks with the lcd_interconnection_test application anymore. Just upload another application and have fun! :) Best Regards, Thorsten.

(I'm a Logic Audio User, and I never tried out a XT by myself...) Best Regards, Thorsten.

Hi Sven, just try the C based version, which allows an easier adaption: http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip When you search in the forum for this version, you will find some additional infos, and some guys who already did experiments. 2 core solution: I don't know which host software you are planning to use, but propably it will handle the second one as a Logic Control XT - such a unit doesn't provide a control section Best Regards, Thorsten.

I cannot give you an adquate answer The X/Y ratio of the first one is 1.4, of the second one 1.8 Unfortunately I don't know the exact ratio of my own GLCD, but I would say: yes, on both displays you won't see a 100% perfect circle (like on my own display), but I guess that the impact isn't so high on the second display, as it is close to 2.0 ratio (128/64) Best Regards, Thorsten.

Super, mal wieder ein Happy End! :) Das mit den Bugmeldungen reisst immer sehr schnell ein - kaum findet jemand einen Fehler (was bei der immensen Menge an Code nicht ausgeschlossen ist), schon vermuten andere hinter jeder Anomalie einen weiteren Bug in der Software... es kostet immer eine Menge Ueberzeugungsarbeit, erstmal die Hardware unter die Lupe zu nehmen. Es ist in Ordnung, wenn das RI# Signal niemals den Wert 0V erreicht, wenn es am Core angeschlossen ist, in diesem Fall holt sich der Master die Datenpackete ja so schnell ab, dass sich mit einem Multimeter eigentlich kein stabiles Signal mehr messen laesst. Die Folgen dieser "Signalstoerung" sind in der Tat etwas seltsam, doch ich vermute, dass aufgrund fehlerhafter Datenpackete der IIC Bus so sehr gestoert wird, dass auch die Verbindung zu den BankSticks nicht mehr stabil funktioniert, und deshalb die Firmware zeitweise annimmt, dass der BankStick ausgewechselt wurde - in diesem Fall wird der Inhalt des BankSticks neu eingeladen, und das deckt sich mit Deiner Beschreibung. Hier werde ich irgendwann einmal Ursachenforschung betreiben (ist aber bei einem sauberen Aufbau kein wirkliches Problem) :-) Gruss, Thorsten.

It's sometimes better to use shifted ones for creating a pattern, e.g. (1 << 0) is the same like 0b00000001 or (1 << 2) is the same like 0b00000100 advantage: everybody who knows this coding style can find out the bit which is set immediately (first example: bit 0, second example; bit 2) Combinations are possible as well: (1 << 0) | (1 << 7) is 0b10000001 And if you are looking for the inverted result, write: ~((1 << 0) | (1 << 7)) is: 0b01111110 Also bitfields can be set this way. E.g., if 3 2-bit fields are stored in a byte, you could write: (1 << 4) | (2 << 2) | (3 << 0) is: 0b00011011 Best Regards, Thorsten.

Yes, there is a global MIDI channel which can optionally overrule the channel settings of the bank setup. And this channel could be modified via buttons, which are assigned to Meta events. For a meta event some extra code is required, but I would say: just ask for the code once the box is ready, so that you can immediately try it out. Best Regards, Thorsten.

Rio: lies mal den ChangeLog Gruss, Thorsten.

werde Deine Mail in ca. 1-2 Wochen durcharbeiten Oktaven: verschiedene Programme/Keyboards verwenden verschiedene Schreibweisen - ist das wirklich ein Problem? MBSEQ richtet sich nach der Schreibweise, die auch in Logic Audio verwendet wird. Zum Select Button: das fuehrt zu Inkonsistenzen in der Benutzerfuehrung. Ich bin mir sicher, dass der naechste Benutzer glatt einen Bug melden wuerde, weil er sich den ChangeLog nicht durchliest ;-) Ich habe zu diesem Thema auch irgendwo im Source Code mal ein paar Kommentare hinterlassen - ich habe mir darueber einige Gedanken gemacht, und bin selbst noch zu keinem Schluss gekommen, wie die Select Taste behandelt werden soll, so dass man auch ohne Handbuchlesen damit zurecht kommt. Ich selbst haette Probleme damit, mich auch nach 1-2 Monaten noch daran zu erinnern, dass die Taste im Record Menue eine spezielle Funktion hat... Gruss, Thorsten.

Buying a PIC18F4685 from doc is the most simple and cheapest solution for people in europe to get the PIC with pre-burned bootloader, so that no PIC programmer is required Best Regards, Thorsten.

btw.: in the v1.7 firmware, you will find such controls within the 303 menu page. yes, this is possible. Just upload the most recent release for the PIC18F4685 (v1.74685) Not really - knobs allow you to customize some controls. This feature will also be available for the bassline engine, but I think that they are mostly interesting for automation via MIDI, or for some prepared "special effects" (e.g. changing cutoff and glide rate with a single knob) In general with the bassline engine the menu pages will change, so that only relevant (and some special) sound parameters are displayed for best live usage. The intention is to have nice sounding bassline (+ special sequencer) without much configuration, and with an ergonomic user interface (therefore the encoder functions will change as well in this mode) - it will "feel" like if a different firmware is running, but in background it's still MBSID V2 :) the MOD matrix of MBSID V1 only provides 7 fixed targets for OSC 123 pitch, OSC123 Pulsewidth and filter cutoff, so this wouldn't be a solution. Best Regards, Thorsten.

I'm sure that you will find a lot of source code, just click on MIOS download or MIOS C Interface (which lists some programming examples in C) The Wiki gives also some interesting informations - yes, also about the MIDI protocol Best Regards, Thorsten.

Hi Matrigs, unfortunately there is no straightforward solution to change the purpose of the encoders. It's not only the cs_menu_enc.inc file which needs to be changed, multiple files are affected, and some additional code needs to be implemented to get a special encoder behaviour exactly like you want. If you could give me the encoder functions you are planning to control, I could do the changes for you... (sidenote: the new code wouldn't be compatible with MBSID V2, as the encoder implementation has been changed) Sidenote: you should consider the use of a PIC18F4685, so that MBSID V2 can run. In MBSID V1 the 303 extension was only an add-on which hasn't been considered from the beginning, and therefore is a little bit complicated to use. In MBSID V2 the overall concept has been prepared for such special "engines". For example, in difference to MBSID V1 bassline sequences can be edited on a more comfortable way, and multiple sequences can be embedded within a single patch, so that you can easily switch between them. There will be additional sound parameters especially for those funky C64 like bassline sequences. Also the encoder functions will be changed automatically when the bassline engine is selected, so that the MBSID V2 CS will propably already provide the look&feel for which you are asking. Only problem is, that these are only ideas, and I cannot give you more details before I've implemented the bassline engine (propably it will be much more powerful than I can imagine for now ;) --- see the progress of the Lead engine! :)) You propably need to wait one or two months before the engine is ready for use. Best Regards, Thorsten.

The MIDImerger project uses a software implemented UART which requires so much CPU time, that nothing else can run in parallel. So, it is not possible to use the same approach for any MIOS application - it just needs a second core which scans the second MIDI In. A MBHP_IIC_MIDI extension would require some changes in the MB64 firmware. So, in theory this would be possible, but there is no ready made solution available yet Best Regards, Thorsten.

What happens when all ICs are removed, and pin 27 of the SID socket is connected to ground? Best Regards, Thorsten.

Ueber die RI->SI Verbindung erfaehrt die Firmware, ob ueber den MIDI Input etwas empfangen wurde. In diesem Fall geht das Signal solange auf 0V, bis sich der Master die Daten abholt. Ansonsten steht es auf 5V Das koenntest Du mal ueberpruefen: trenne die RI# Verbindung zum Core (so dass sich die Firmware keine Daten abholt). Nach dem Einschalten sollte RI# auf 5V stehen. Schliesse (erst dann!) ein Keyboard an und spiele eine Note. RI# sollte auf 0V gehen. Schliesse RI# an den Core, das Signal sollte wieder auf 5V gehen Gruss, Thorsten.

Thank you! :) So, you don't need any additional components, right? Just Pin 1 via 220 Ohm resistor the digital output of the 74HC595, Pin 2 to ground, and pin 6/4 to the keyboard. What happens with pin 5? Best Regards, Thorsten.

Hm, then I don't have any ideal for the reason... ICProg has a readout function, right? What has been written between 0x400 and 0x5ff? Best Regards, Thorsten.

Yes, the required adaption of the resistor value is strange. My assumption is, that the MIDI output of the keyboard somehow doesn't comply with the MIDI spec (5mA current loop), so that depending on which kind of optocouplers (or circuitry around the optocoupler) is used, the MIDI signal can be received properly or not. I would start with some current/voltage level measurements, but without a scope this is too difficult... however, as you found a solution, it's fine :) Best Regards, Thorsten.

Sounds more like a problem with the YAC512, since the YMF sends the DAC signal. First I would start to doublecheck the schematic vs. new layout, and the new layout against the old layout, just to ensure that this is no general problem with the interconnections. Check especially that the ICs are stuffed the right way (not mirrored), as this confuses most people Best Regards, Thorsten.