TK.

For the records (I already answered this post in the german forum) the intensity of the noise depends on the sound patch you are using, if you are playing exactly the same sound on the HardSID card, you should notice exactly the same background noise Best Regards, Thorsten.

Yes, the SysEx messages are ok - these are the patches for the slave modules. Just to be sure (because people oversaw this many times in the past): did you take the new wiring between core and SID module into account? It is different since V1.7 (which was released one year ago), all schematics are updated, but there are still people who are building the project based on the expired schematics. The required change is easy - see http://www.ucapps.de/mios_v1_7_hardware_mods.html Best Regards, Thorsten.

Hallo, die Intensitaet haengt von den Soundeinstellungen ab, wenn Du exakt den gleichen Klang einstellst, muesstest Du auch den gleichen Backgroundnoise hoeren spaetestens wenn Du den TB303 Modus ausprobieren moechtest, fuehrt kein Weg am 8580 vorbei - die Filtercharakteristik ist einfach viel besser :) Gruss, Thorsten.

ich habe mir sicherheitshalber nochmal die aktuellste Release (vom 30.7.) runtergeladen (die gleich wie zuvor), und es mit Hermann Seibs VST Host ausprobiert - leider ohne Erfolg. Wie bei den anderen Hosts ist nur ein leerer Rahmen zu sehen: Kann es vielleicht sein, dass das VST auf Resourcen zugreift, die bei mir nicht verfuegbar, oder anders organisiert sind? Ich habe bspw. gelesen, dass eine direkte Verbindung zum MIDI Interface aufgebaut wird - das ist sehr loeblich, denn ansonsten waere es bspw. mit Logic nicht moeglich, CC Events zur MBSID zu uebertragen. Doch koennte sich hier doch evtl. ein Fehler befinden? Ich habe immerhin > 16 MIDI Ports ;-) Kann man irgendwo die aelteren Versionen runterladen? Gruss, Thorsten.

For the SID driver it doesn't matter if a SID module is connected or not, because the communication between the core and SID is unidirectional. So, there must be anything else - maybe a solder blob between two tracks of the core module (around the LCD data lines?) Don't connect the audio input of your stereo/mixer directly to the SID, this could destroy the chip! Best Regards, Thorsten.

I've currently no time to answer all your questions (try again if nobody else answers), but maybe this list helps: http://www.ucapps.de/mios/mios_din_dout_pin_numbers.txt I know, it's a very abstract describtion, but no volunteer has been found yet, who wants to write application specific docs Best Regards, Thorsten.

Hi Nikolai, with error message I ment the SysEx replies which are sent during the upload... however, if you never saw a "...0E ?? F7" message during upload, then it should be ok (MIOS Studio decodes the message and shows it in a readable form) The LCD message you saw notifies about the activation of the BOR flag, see documentation in the ChangeLog: http://www.ucapps.de/mios_changelog.html - this is no error message, but just a hint, that this (required!) change has been done. So, what could happen: your PSU is too weak, or there is a short circuit somewhere, which drops the core voltage to below 4.5V. At this voltage some external components (like LCDs or BankSticks) don't work reliable anymore, therefore the PIC is forced into reset state, so that nothing "dangerous" happens (e.g. so that the bankstick format routine won't be started). Propably for your application the BOR reset is not really relevant, but in general it makes sense to activate it. So - my tip - remove all 74HC595 chips and check if the reset still happens. The successively put them into the sockets again (switch-off the power when doing this!) in order to find out, which part of the DOUT chain is defective If this doesn't help, disconnect the whole DOUT chain from the core module in order to find out, if the short-circuit is there, or anywhere else Best Regards, Thorsten.

Hallo, der (etwas kleingeradene) Snapshot sieht ja schon sehr verheissungsvoll aus, doch ich kriege das VSTi nicht zum Laufen. Zuerst wollte ich es mit Logic Platinum 5.5 ausprobieren - dazu habe ich die .dll Datei in den VstPlugIns Ordner geschoben, und Logic gestartet. Das VSTi befand sich nicht in der Auswahlleiste, doch wie ich spaeter merkte, wurde der Ordner SID-Control angelegt, in dem sich eine neue .dll Datei befand. Also Logic erneut gestartet - nun konnte ich SID-Control/SCTRL anwaehlen, doch es wurde lediglich ein leeres VST-Fenster geoeffnet Anschliessend habe ich versucht, SCTRL mit EnergyXT zu laden (ein reiner VST-Host) - doch ebenfalls ohne Erfolg. Kann es sein, dass in der Beta Release etwas wichtiges fehlt? Gruss, Thorsten. P.S.: Es gibt uebrigens mehrere HW-SIDs auf der Welt, aber ich vermute mal, dass das VSTi nur die MIDIbox SID ansteuern kann? (wuerde mir ausreichen ;-)

M-Audio offered a MIDI<->Bluetooth bridge some time ago, but it's not available anymore, propably because of the bottleneck problem. MIDI provides no handshake protocol - means: if a data package cannot be sent on time, it will be lost - for a musican thats a fatal scenario (think about hanging notes, incomplete sysex, etc).

Hi Axel, the mp3 is not accessible... however, is this a silent sound in background? Then your MBSID is possibly stuffed with a 6581 - the background noise is a design weakness of this chip. Best Regards, Thorsten.

Hi, the BOR feature is a brown-out reset, which resets the core if Vdd is too low. Which value do you read at the Vdd pins? It should be >4.5V Best Regards, Thorsten.

Hi Nikolai, what does happen when you upload MIOS V1.8 again? Maybe one code block was not uploaded correctly, but you oversaw the error message? Best Regards, Thorsten. P.S.: you can verify the completeness of a MIOS installation with the CRC application - with MIOS V1.8 it should display the CRC: BB15

Hi, within the MIDIO128 application the Sensitivity is part of the data dump, this means that you don't need to add additional code, you can select the value in your midio128.ini file (see mk_midio128_syx.zip package), or you can predefine it in main.asm (search for DEFAULT_TS_SENSITIVITY) The default value is 3, and this is a very good value which normaly works perfectly. But - of course - you need to modify your DINX4 module like shown in this schematic: http://www.ucapps.de/mbhp/mbhp_din_touchsensors.pdf otherwise it cannot work Greetings from the rainy Munich (however, more time for tinkering ;-) Best Regards, Thorsten.

The envelope looks very proplery on the scope, so long the gate is release, it outputs 0V, with the gate rises to the max. voltage, before it goes down to the selected sustain level. So long the gate is active, this sustain level will be hold. This means, when you are changing the sustain level, the voltage will track this setting (like in the analog world). Yes, pot 0-3 are used by default, but this is only an example setup (which doesn't really make sense, since these pots also control other AOUTs!) - you should assign the envelope parameters to unused pots Suggestion: remove all the code in map.c, and start to create your own setup. The fun begins, once analog input values and digitally generated waveforms are modulated together. This should result into very interesting effects! :) Example: write: aout_value[0] = CONV_16BIT_TO_12BIT(lfo0_value); lfo0_rate = CONV_16BIT_TO_8BIT(eg0_value); // for direct pot Control eg0_attack = CONV_10BIT_TO_8BIT(MIOS_AIN_PinGet(0)); eg0_decay = CONV_10BIT_TO_8BIT(MIOS_AIN_PinGet(1)); eg0_sustain = CONV_10BIT_TO_8BIT(MIOS_AIN_PinGet(2)); eg0_release = CONV_10BIT_TO_8BIT(MIOS_AIN_PinGet(3)); eg0.GATE = midi_note[0].GATE; // EG triggered with MIDI note at Channel #1 [/code] this will output the LFO0 value at AOUT0, and it will modulate the LFO frequency with the envelope Then you could modulate the eg0_decay with another LFO: [code] eg0_decay = CONV_16BIT_TO_8BIT(lfo1_value); And the LFO1 frequency with an analog input: lfo1_rate = CONV_10BIT_TO_8BIT(MIOS_AIN_PinGet(1)); // modulated with second AIN [/code] Hope to hear more samples soon :) Best Regards, Thorsten.

Seems to be a KS0107/0108 compatible display - very good, should work! :) Just let the CS3/CS4 outputs of the core open, the driver will regognize automatically that the appr. segments are not available Alternatively you could connect a second GLCD in parallel to the first one, with the only exception that the chip select lines are connected to CS3/CS4, which results into an effective resolution of 256x64 (good for MIDIbox LC) Best Regards, Thorsten.

You should be able to do this with special functions (which are working like meta events, but already preprogrammed, see mb64_sfb.inc) -> http://www.ucapps.de/midibox/midibox64_sfb_table.txt Best Regards, Thorsten.

There is a SM_NotifyToggle function which works like USER_DIN_NotifyToggle, this means that up to this point you can generate MIDI events like shown in the examples and big applications (e.g. table method, calculated events, programmed events or whatever) Best Regards, Thorsten.

Hi George, the display offsets are handled by MIOS in a way which allows to use the same cursor positions on any kind of LCD. With MIOS_LCD_YAddressSet the LCD specific cursor offsets are mapped to the MIOS specific cursor offsets. 64 characters (0x40) are reserved for each line, up to 4 lines are (natively) supported: 1st line begins at 0x00 2nd line begins at 0x40 3rd line begins at 0x80 4th line begins at 0xc0 And these lines have to be mapped to the real address offsets of your LCD - this can normaly be found in the datasheet, the most common cases are documented in the functional description of MIOS_LCD_YAddressSet: http://www.ucapps.de/mios_fun.html#MIOS_LCD_YAddressSet For a 2x40 following settings are working: Y0: 0x00 Y1: 0x40 Y2: doesn't matter (*) Y3: doesn't matter (*) (*) note: if a value between 0x80...0xff is specified here, it is assumed that the 3rd and 4th line is mapped to a second LCD Centering the screen just means to add additional offsets to these addresses, e.g. let's say you've a 2x40 display, but only 16 columns are used, this means that you need to add 12 to each offset: Y0: 0x00 + (40-16)/2 Y1: 0x40 + (40-16)/2 Y2: doesn't matter (*) Y3: doesn't matter (*) Thats how MIOS supports LCDs. The MB64 application now simplifies the configuration for people without programming skills by providing 4 predefined display types with premade (and tested) setups. They can be selected with DEFAULT_LCD_SIZE This setting selects the Yx values and the cs_m_display_*.inc file You can see this when you are searching in main.asm for "DEFAULT_LCD_SIZE" Unfortunately nobody sent me the required definitions and .inc file for a 2x40 display yet. This either means, that nobody found it useful yet, or that the guys who did such a customization haven't thought about a public release yet (they are always welcome to bring their code into the mb64 package) So - if you are not able to re-use existing code, it means that you have to program it by yourself. And this requires to understand the code in the cs_m_display_*.inc files --- they are partly different, depending on the guy who programmed the extension, and depending on the available screen size of course (than larger the size, than more features for the display layout can be found). Very tricky is the implementation of the CSMD page (provided by Duggle), because it uses alternative display offsets, which are not the same like on all other display pages (just select the last page within the display menu, and you should notice this). The MB64_LCD_SetDefaultOffsets and MB64_LCD_SetCSMDOffsets (in mb64_lcd.inc) routines are switching between the two parameter sets (the ones which are defined in main.asm), so you don't need to change anything there. Instead you only need to define a new display type (let's say: number 4), you need to define new Yx settings (in main.asm), and you need to create a new cs_m_display_2x40.inc file (hint: just copy cs_m_display_2x20.inc to cs_m_display_2x40.inc and change it for your needs). Simplest way to do this: search in main.asm for DEFAULT_LCD_SIZE == 3, copy the lines from "#if ..." to "#endif", change "DEFAULT_LCD_SIZE == 3" to "DEFAULT_LCD_SIZE == 4", and adapt the code in between the copied conditional statement. (there are only two!) Your (personal) requirements can mainly be realized by changing the CSMD routine in the newly created cs_m_display_2x40.inc file. This isn't easy for somebody who never programmed the simple stuff, so maybe it's better when you are beginning with easier changes in order to get a feeling about the way how assembly language works. Sooner or later you should be able to customize the whole display handler exactly for your needs :) Best Regards, Thorsten.

The MBSID should show the patch name at the second line, this name should be updated whenever you send a new patch with JSynthLib. But the "wrong character" problem is very new to me - it also seems that characters are missing (but this could be a sideeffect) - not sure if this effect can happen if datalines are swapped Best Regards, Thorsten.

(ich kann diese grosse Latenzzeit irgendwie nachvollziehen ;-) Gut zu wissen, dass man sich wieder Hoffnung machen darf! Gruss, Thorstem.

Hallo Pearl, die C version von MBLC wird kein Grafikdisplay unterstuetzen - fuer mich war es damals ziemlich viel Aufwand, diese spezielle Option (die nur von extrem wenig Leuten verwendet wird) einzubauen, und ich moechte die ganze Arbeit nicht nochmal tun. Gruss, Thorsten.

[x] please publish some samples :) Best Regards, Thorsten.

I'm confused, did you read the FAQ? I enhanced the answer there especially for you! Best Regards, Thorsten.

alright, I've received the source code, but cannot see any dependency between BankStick and the VFD driver - the implementation of the driver is very good and shouldn't cause problems. So, I've no idea what could go wrong here Are BankStick accesses the only problem, or is anything else also not working? Best Regards, Thorsten.

This MIDIbox SID was made by pwx The big question: which case did he use for his design? :-) (here a link to the large view: http://69.56.171.55/~midibox/midibox_gallery/pwx1_large.jpg