TK.

Hi, no, the matrix is enabled by default. Have you already tried the mbsid_led_matrix_test? Best Regards, Thorsten.

While I've worked on the bassline tutorial, I noticed that the WT sequencer was somehow broken in 303 mode. Slided notes retriggered the gate, and this was not intended. So, here the new beta: http://www.ucapps.de/mios/midibox_sid_v1_7_303beta16.zip old 303 sequences are not compatible and will sound different... let's say: better ;-) Best Regards, Thorsten.

Nein, die PWM Einstellungen sind nicht egal - nur wenn die Spannung einbricht, dann schon ;-) Meine Aussagen basieren nach wie vor auf Vermutungen, wenn Du zumindest den Fader Typ angeben wuerdest, koennte man sich ein genaueres Bild ueber das Problem machen. Vielleicht koenntest Du auch mal die Spannung am Fader messen, wenn eine neue Position angefahren wird. Und wie aendert sich die Versorgungsspannung des MF Moduls, wenn ein oder mehrere Fader bewegt werden? Gruss, Thorsten.

Yes, in this case it's very likely that the display is broken Best Regards, Thorsten.

Hallo Jan, der L293D kann nur bis zu 0.6A liefern, das ist zu wenig, denn gerade der Anlaufstrom kann je nach Fadertyp (hier hast Du keine Details genannt) ziemlich hoch sein... auch das Netzteil muss fuer hoehere Stroeme geeignet sein. Gruss, Thorsten.

Hi Reiner, such an effect could happen if the external application continuously updates the screen. A LCD isn't a TV screen, it doesn't need to be refreshed - just send the SysEx only if something has changed on the text output, and not permanently. Alternatively you could use LCD command 01 instead of 00, because 00 always clears the screen before characters are written, and this causes a flickering effect. This is just an assumption (you haven't mentioned, how your application is working) Best Regards, Thorsten.

MBSID already features this. In addition, you can jump directly into the LFO/env menu and select the appr. modulator when you push the E1/E2/L1..6 button of the modulation matrix. Best Regards, Thorsten.

Hi Lorin, this sounds great! I'm very interested on your project and would like to use it :) I could help you with the MIDI integration (should be easy with MBHP_IIC_SpeakJet) Best Regards, Thorsten.

It's a 2x20 LCD, and momentary close buttons Best Regards, Thorsten.

Hallo Jack, die Configuration Bits habe ich nirgendwo gespeichert, und bevor ich etwas zurechtbastle, was ich selbst nicht getestet habe (und somit fehlerhaft sein koennte), rate ich lieber, die Einstellungen mit denen des PIC18F4520 zu vergleichen. Wenn die Programmierung fehlschlaegt, liegt es jedoch eher an der Software oder am JDM - die neueren PICs wollen 12.5V an MCLR sehen, der JDM reguliert die Spannung nicht sauber. Mit dem MBHP_BURNER und P18 wird es wohl eher klappen Gruss, Thorsten.

sm_c_example1 and sm_c_example2 are now available under http://www.ucapps.de/mios_download.html This was just a quick transfer from the completely assembly based examples - I don't plan further enhancements, and I cannot support these projects that much. Feel free to publish your changes. Best Regards, Thorsten.

if you want to use the features of MBSID V2 in future (see http://www.ucapps.de/midibox_sid_v2_wishlist.html), then a PIC18F4620 should be prefered, if you are planning your own firmware, I guess that you will be happy with the PIC18F452 for the first 1-2 years - and who knows, which pin compatible chips are available until then (the EUSART bug will be fixed sooner or later) Best Regards, Thorsten.

for a single SID: yes for a four SID solution you need at least CS Step B, the usage without is too difficult (there are some postings about this topic in the forum...) yes, but it's difficult to handle, since switching between different device IDs isn't so easy with JSynthLib Best Regards, Thorsten.

there isn't that much documentation available about this, but the lower line shows the production date which gives a hint Best Regards, Thorsten.

Yes, especially the newer (shrinked) 6581 versions which were produced 1984 and later have bad filters - if good filter sound and low noisefloor is desired, consider the use of a 8580 Best Regards, Thorsten.

You have to use the hex2syx.pl script which is part of the mios_v1_9_src package, the commands are ok. Best Regards, Thorsten.

I just have released a preliminary schematic + firmware -> http://www.ucapps.de/mbhp_iic_speakjet.html Best Regards, Thorsten.

I don't think that this is a bad SID, it seems to be a feature of the software (e.g. an envelope on the pitch?) If you hear any sound, you can be sure, that the SID is ok Best Regards, Thorsten.

Just upload MIDIO128, it will send a MIDI event when a DIN changes. It's the most powerful debugging help, because in combination with a MIDI monitor you can follow the pin toggles in a logfile/window PSU: not my area of competence ;-) Best Regards, Thorsten.

if you want to have a cheap synth with less features than today, a combination could be possible. But if you want a really powerful synth, not only the firmware should focus on a single soundchip, but also the user interface (-> front panel) I don't think so, it would result into a synth with a lot of compromisses, not only because of the additional code memory consumption. Ok, the PIC18F4620 provides twice the memory, but I want to fill it with new MBSID features, and not with hardware options which most people would never use I've read the microwave manual and can confirm, that the modulation possibilities are much more flexible. A short summary: there are a lot of modulation sources, not only LFOs and envelopes, but also different MIDI events and especially the 4 modifiers. The 4 modifiers allow to combine two modulation sources with a mathematical operation. E.g., "LFO1 / LFO2" or "MIDI Note * Modwheel" - and even complex operations like "LFO1 S&H LFO2" or "Modwheel filter" (applies a low-pass filter). The modulation matrix allows 16 connections between any modulation source to any modulation target with individual depths - and there are much more targets than on MBSID (e.g. also ENV and LFO parameters, Depths of modulation assignments, etc...) Of course, the possibilities are great, but I also see some drawbacks, and I guess that I've to think very long about a concept which matches with my own requirements. a) Microwave provides only 16 modmatrix connections instead of 128 (MBSID V1) resp. 384 (MBSID V2) - so, some MBSID sounds won't be possible anymore b) the usage is more complicated - creating a modmatrix routing takes more time than just enabling the "prepared" matrix connection on MBSID c) all modulation targets require some special code, I fear that this will slow down the engine so much, that the current update frequency of 1.22kHz cannot be ensured anymore, instead I assume an update frequency of 500 Hz or slower. This will also affect the current MBSID sound d) the RAM consumption for buffering the target values will be so high, that some other features might be cancled e) the front panel doesn't match with the different matrix concept anymore, but using my existing front panel is one of the strongest requirements The performance drawback for "16 modmatrix routing paths" provided by microwave instead of 384 "modmatrix nodes" provided by MBSID V2 might sound confusing, but this is related to the implementation (the modmatrix nodes are using prepared waveforms, they are just added to the destination) But I don't want to say that I'm not impressed about the possibilities, especially the modifier concept is interesting. Maybe MBSID V2 could provide similar possibilities by enhancing the LFOs - so that they can be alternatively used as generic modulator with two source inputs and an operator. I will think about this... Best Regards, Thorsten.

Hallo Jack, der Bootloader laeuft auch auf dem PIC18F4550, wenn man bspw. PIC_DERIVATIVE 2 waehlt, und die Configs fuer PIC18F4550 anpasst - doch ich selbst verwende lieber den USB Bootloader von Microchip. Code Upload via USB macht einfach mehr Spass, die GUI ist supereinfach zu bedienen, und selbst fuer Linux gibt es mittlerweile eine Kommandozeilen-Version, die problemlos funktioniert. Ich habe kein Interesse an PCBs (habe noch zuviele eigene Projekte am Laufen ;-) Gruss, Thorsten.

Sidenote: with the new mkmk.pl script (part of the most recent C wrapper release), it's possible to integrate assembly modules (.asm files) into a C project. The assembly code must be relocatable (means: it requires a data and code section, absolute addresses should not be specified). An example can be found in the midi router package, see MAKEFILE.SPEC how to add .asm files, and see int_midi.asm/int_midi.h, how a relocatable module looks like Best Regards, Thorsten.

If somebody shoots new pictures or writes better documentation -> please add this to wiki Best Regards, Thorsten.

I also think that this is a problem with the DIN module - just use MIDIO128 and srio_interconnection_test for debugging Best Regards, Thorsten.

Hi, I'm not a Mac user, but somebody reported that the "Syx Librarian" works fine: Just increase the pause between messages until no new message is sent before the reply has been received from the MBSID Best Regards, Thorsten.