TK.

Yes, JSynthLib works with SysEx... the SID chip shouldn't cause such a problem, because there is no feedback to the core. Means: regardless if a SID is connected or not, the application should never freeze. I've really no idea what should cause such a scenario, just let me some days, maybe I will be able to reproduce this sooner or later... if anybody else but kokoon and pwx is able to stimulate the hang-up, please let me know. Best Regards, Thorsten.

fixed. Gruss, Thorsten.

I wasn't able to reproduce the error yet, maybe it only happens at certain patches? Which patch are you using exactly? Best Regards, Thorsten.

Cool! I haven't expected such an error, I will improve the schematic Best Regards, Thorsten.

Hi Davo, the schematics are free for non-commercial use Best Regards, Thorsten.

Hi Corey, these are interesting questions for a FAQ (FARMARKER) Detuning: OPL3 only supports predefined multiply factors, thats the only way to "detune" the oscillators... I understand under detuning those slight frequency differences between the OPs which could make the results even more interesting (especially for Fx sounds) The drum channel has its own voices, they are handled independently from the instruments Multitimbral: there are 4 instruments and 6 voices, the voices are allocated dynamically. This means, if all 4 instruments are in mono mode, only 4 voices are allocated, 2 are unusued. If one or more instruments in poly mode, they will share the voices (the longest played voice will be dropped first) CC: yes, absolutely live with immediate update on LCD - this feature was one of my main focus Parameters: yes, all are editable via CC. Only difference to SysEx is, that CC listens on a specific MIDI channel. This can cause a problem once two instruments are assigned to the same MIDI channel, you won't be able to edit them seperately. Have fun :) Best Regards, Thorsten.

12.3V is within the allowed voltage range I just got the idea that something else could cause such a problem: the oscillator. The SID won't generate any sound so long no clock is running. Is your module stuffed with an integrated oscillator? Then check the connections around there (it's impossible to measure the frequency without a scope). You could also try to clock the SID from the PIC like described at the MBHP_SID page --- note that the oscillator has to be removed in this case Best Regards, Thorsten.

The different cap value cannot cause a problem. very good! This increases the chances to get the module running :) It depends on the type of error. A solder clump between two tracks of the SID module could cause such a problem. In principle such errors can be found visually, but is very time consuming. There is a radical, but very effective method which saves some time, but which requires a good oversight over the schematic and the PCB: cut the power rails (e.g. with a screwdriver) at some places where you think that they could be critical, and measure the voltage after each cut. This helps you to find the area which is affected. Try to find the error without too much cuts... after you've located the error, you can repair these cuts with solder... Best Regards, Thorsten.

How about MIOS Studio for Mac? http://www.midibox.org/forum/index.php?topic=5230.0 Best Regards, Thorsten.

I don't know any reason, why some, but not all CCs of a slave shouldn't be accessible. It's important, that a filter type (LP/HP/BP) is selected (CC#45), and that the oscillators are assigned to the filter path (CC#44) - did you take this into account? JSynthLib: thats a know issue, JSynthLib can only control a single module properly, it isn't in my hands to improve the handling of multiple synths :-/ Best Regards, Thorsten.

Since you are using MIDI-Ox, you have to create a .syx file which addresses ID #1, you can do this by calling the hex2syx.pl script from a DOS shell: perl hex2syx.pl main.hex -device_id 0x01 It's simpler with MIOS Studio: just select device ID 01 (no new conversion required) Best Regards, Thorsten.

Yes, relaxing the timings is a good idea. If you are using the sm_example1, you only need to increase the "MIOS_SRIO_UpdateFrqSet" setting in main.src - currently it is set to 1 mS, just try 10 or 100 mS Best Regards, Thorsten.

Since everything seems to be fine at the digital side, it could be a problem at the output amplifier stage around T1 - check the soldering joints, check that the transistor is mounted correctly (the direction does matter) Best Regards, Thorsten.

The difference between MIOS V1.8 and V1.7 isn't so big, so this is not the reason. There was a problem with MIOS V1.6, which is fixed in both versions. Testing the updated MBSID application makes more sense. I always take care that such MIDI overruns never happen, if you've found a way to hang up the MIDI engine, then please send me the appr. patch (but please: try it out with the most recent firmware first) Best Regards, Thorsten.

Ja, das ist koscher :) Es gibt kein eigenes Board fuer solche Verkaeufe, aber Du koenntest den Topic in "Verkaufe Bauteile/Module" umwandeln, und ich wuerde den Thread "sticky" machen, bis alles verkauft ist Gruss, Thorsten.

Hallo, schau mal in diesen Code rein http://www.ucapps.de/mios/midibox_lc_v2_0_alpha1.zip, in lc_vpots.c findest Du Tabellen mit den LED Patterns. Daraus wird ersichtlich, dass man bis zu 16 LEDs pro "Meter" (bzw. hier: LED-Ring) ansteuern kann. Die Center-LED wird in LC_VPOT_LEDRing_CheckUpdates() nachtraeglich angesteuert, aber den entsprechenden Code kann man ja entfernen ;-) Im Wesentlichen laesst sich ein "Reglereinstellungsanzeigemodus?" aehnlich realisieren, nur nimmt man nicht die Werte aus vpot_abs_value[8], sondern aus fader_position[8] (-> lc_mf.c) Gruss, Thorsten.

First of all it would be interesting, from which chip this failure is comming from. This should help to locate the error. So, just put out the ICs from the sockets (each time only one), and check which one does lower the voltage. Please do the measurements quickly, because depending on the type of error the ICs could be damaged when they are powered too long (hopefully all ICs are still ok) Best Regards, Thorsten.

Hi Seppoman, like Pay_c I suppose that this is a shielding problem. The button matrix sends very short pulses over the select lines, than longer the cables, than higher the propability for crosstalk effects. Shielded cables help to eliminate crosstalk Best Regards, Thorsten.

I don't know this effect, maybe because I'm working with a much more advanced firmware since some months? Are you using the most recent version of MIOS and MBSID? -> http://www.ucapps.de/mios/mios_v1_8.zip -> http://www.ucapps.de/mios/midibox_sid_v1_7_303beta9.zip Best Regards, Thorsten.

MIOS can handle this, but you will have to re-write the application at many places. Due to performance reasons, it has to be made in assembly code. Best Regards, Thorsten.

Hi, yes... but it's maybe better to say: the oldest note is assigned to CV 1/gate1 Each note has it's seperate CV and gate output MIDIbox CV uses the same Poly algorithm like MIDIbox SID: each new note will pushed into a stack, each released note will be removed from the stack. So long the stack is full (SID: 3 notes, CV: 8 notes), additional notes won't be accepted Sidenote: MIDIbox FM provides an optimized stack handling: once the stack is full, the "oldest" note will be dropped, resp. replaced by the new note Best Regards, Thorsten.

or use MBHP_BURNER (broccoli18 doesn't work with all PCs) FAQMARKER Best Regards, Thorsten.

A link to the current beta version (beta9) can be found here: http://69.56.171.55/~midibox/forum/index.php?topic=4956.0 I'm still waiting for the curtis chips in order to finalize the low-cost AOUT controlled filter circuit, then I will start with the documentation. Best Regards, Thorsten.

Zum Testen der DOUTs koenntest Du eine Dummy-Applikation einladen, die garantiert nichts macht (bspw. das Skeleton), MIOS Studio oeffnen, das Debug Fenster oeffnen, die Funktion "MIOS_DOUT_SRSet" anwaehlen, WREG auf 0 (selektiert das Shift Register), und MIOS_PARAMETER1 auf 1 (alle 8 LEDs an) Doch wenn Du sowohl DIN als auch DOUT Module nicht funktionieren, ist die Wahrscheinlichkeit sehr hoch, dass es an der SCLK oder RCLK Leitung liegt (wie bereits weiter oben beschrieben). Auch der beschriebene Effekt mit der Rew-Taste deutet darauf hin, dass die Werte nicht durch die Register geschoben werden. Hast Du ein Ohmmeter oder einen Durchgangspruefer? Dann propiere mal folgendes aus: nimm alle 74HC165/74HC595 und den PIC aus den Sockeln, und ueberpruefe, ob zwischen Pin #22 und den SC pins an den Shift Registern eine Verbindung besteht (Details findest Du in den Schaltplaenen) Das gleiche mit Pin #21 und den RC Pins wiederholen Anschliessend noch ueberpruefen, ob keine verbindung zwischen SC und RC besteht Gruss, Thorsten.

Ok, ich werde beide Features (Soft-Takeover und Volume-Meter) bei der naechsten Version beruecksichtigen. Falls es nicht auf Anhieb funktioniert, kannst Du dann ja mal selbst debuggen (die neue Meter Funktion kann ich ohne die entspr. Hardware nicht vollstaendig testen) Gruss, Thorsten.