TK.

No - for me the existing randomization possibilities are sufficient Best Regards, Thorsten.

Ja, sieht nach einem Designfehler aus. 100 nF werden fuer 3.3V chips hergenommen, ich haette das Datasheet sorgfaeltiger lesen sollen :-/ Danke fuer den Hinweis! Werde den Schaltplan demnaechst updaten Gruss, Thorsten.

Miss mal die Spannungen direkt am Druckerport. Im Schaltplan habe ich die Signalleitungen mit "Clock", "Data In", "Data Out", "Vdd enable" und "Vpp enable" bezeichnet. Diese Signale muessten sich mit P18 zwischen 5V und 0V hin- und herschalten lassen. Kannst Du das bestaetigen? Gruss, Thorsten.

Hi, do you see a gray/black line when the LCD is powered and not initialized? This would indicate, that the contrast voltage is ok. If not, this Wiki page helps: http://www.midibox.org/dokuwiki/doku.php?id=troubleshooting_lcd_displays Best Regards, Thorsten.

The difference between 120 BPM and 119 BPM is 136 uS (@24ppqn) It's a systematic problem, that such a jitter cannot be compensated with MIDI, as sending one byte takes 320 uS In addition, your MIDI interface (USB?) will add some additional delay and jitter, and this is normaly much higher than the accuracy of a MIDIbox. See also the MIDI benchmark: http://www.midibox.org/forum/index.php?topic=2342.0 So, the only solution is to use Logic as MIDI clock master Best Regards, Thorsten.

Hi RM, This is already possible in the Length menu. :) You can even control the loop and end point via CC, and it can be controlled from another track (internal loopback) for very organic sequences. Yes, this was already possible with MBSID V2, a step can trigger an event up to 4 times with a delay of 1..31 microticks between each trigger. This can be defined for each step seperately in the length layer Best Regards, Thorsten.

Thank you very much for the research! I've updated the OPL3 PSU schematic, so that it only uses a single bridge rectifier. I think that I never found this issue by myself, since I'm using transformers with seperate secondaries - and I'm not sure, if I connected the two middle AC lines together. I will check this once I open the case of my MBFM again. The PSU of JD Sleep looks like a good alternative solution for people, who have a single secondary transformer lying around which they want to re-use for the AOUT or OPL3 module. A wiki page about this topic would be great! I would add a link to this page from ucapps.de, so that everybody can read more about different variations. Freeware schematic drawing tool: I'm using xcircuit since more than 10 years now. I don't know if there are better tools in the meantime, but this one works under different operating systems, which is a big advantage. Best Regards, Thorsten.

Yes, it was about 300 bytes for one pattern. A complete pattern backup is not provided by MBSEQ itself, this would require a SysEx tool like TL's patch manager, but nobody has implemented it for MBSEQ. Songs cannot be dumped. If you just want to create a backup of the BankStick, then you could use the MIOS functions for this - see http://www.ucapps.de/mios/mios_backup.txt It's the fastest way... Best Regards, Thorsten.

Please note that the assign layer of the OSC section is a *must* for MBSID V2, as it contains the free assignable "knob" functions - each patch will have its own assignments which allow interactive sound control of specific parameters which are relevant for "cool sweeps" Without this layer, you can only control these "knobs" from an external MIDI controller, or with your PC Best Regards, Thorsten.

Hi, in MBSEQ V3, the size is 651 bytes. Just press the GP buttons below ">>SEND<<" within the SysEx menu Best Regards, Thorsten.

A hold function is not available for MBSID V1 (as it requires some extra memory), but will be available in MBSID V2 Best Regards, Thorsten.

Episode #1: the reincarnation of a DIY synth :) -> mbsidv2_demo1.mp3 Best Regards, Thorsten.

Hi Reiner, unfortunately the repeat rate is hardcoded into MIOS (it's 32 mS). I will make it configurable with the next release Best Regards, Thorsten.

Rio: I will check this and release a new version if required Stryd: ok, I'm a young guy, I can wait ;) Best Regards, Thorsten.

Schoen, dass ihr die Sache unter Euch ausgemacht habt! dj3nk: ich werde nun erstmal von einem Bann aus dem Forum absehen. Es ist verstaendlich, dass Du momentan im Stress bist, aber die Umgangsform gegenueber anderen sollte darunter nicht leiden, egal ob Du sie persoenlich kennst, oder ob sie am anderen Ende der Welt sitzen. Gerade im anonymen Internet kann das sehr schnell in eine ungewollte Richtung eskalieren, wie man in diesem Thread nachlesen kann, und davon hat niemand was. Gruss, Thorsten.

20mS - this sounds like the ADSR bug, see also: http://www.ucapps.de/howto_sid_wavetables_1.html at the end of the page Best Regards, Thorsten.

So, if the RC and SC signal is available, the only possibility I could imagine is that the 74HC165s are not powered (bad soldering at pin 8, 15 or 16). Could you please check this with removed chips? Because otherwise it could happen that you measure an "output voltage" caused by internal nets instead of the "input voltage" from the power supply. Best Regards, Thorsten.

And here the next monster MIDIbox :) Dietmar has added MIDIbox LC based LCDs, LED digits and LED meters to his Tascam US2400 controllers in order to get a visualisation of parameters and values. There are some buttons in addition which allow to trigger functions, which are not accessible from the Tascam Controller.

There is a new MIOS Studio Version available, which supports uploads to code memory range >64k http://www.midibox.org/mios_studio/MIOSStudio_beta7_5.jar.zip Best Regards, Thorsten.

Now, this is interesting! I should consider to overwork the schematic Best Regards, Thorsten.

In the meantime USB interfaces are so cheap, that it doesn't make a difference if you are using a DIY unit or not. Some commercial interfaces have the advantage, that they are not using the legacy MIDI USB driver of M$ - accordingly they are mostly multi client capable, thats a big plus I'm not planning to try other chips... the PIC18F4550 desaster was already frustrating enough, and answering requests like "could you please make it available", "why not trying another chip" do frustrate me even more, because I don't need this interface for myself, I don't want to spend the time for additional support effort if the interface doesn't work with the exotic windows version somebody is using, and I've a lot of other interesting projects in the queue. Best Regards, Thorsten.

Hi, I remember, that somebody else had similar problems with a switching power supply. What kind of PSU are you using, and does the v_mf voltage change when a fader is moved? Best Regards, Thorsten.

bit #0 should set the leftmost LED (D7) on a common DOUTX4 board - this mirroring has historical reasons Best Regards, Thorsten.

Great!!! :) (because I was really out of ideas ;-) Best Regards, Thorsten.

Hi Simone, sounds, like there is a problem with the shift register. See this troubleshooting page for debugging instructions: http://www.midibox.org/dokuwiki/doku.php?id=din_module no, the 1st level bootloader will always send this request at startup - no problem. thats not correct, "00" is an invalid SysEx command and not sent under normal circumstances. Where did you read this? Maybe a typo Best Regards, Thorsten.