TK.

PIC18F4620... hm, I haven't tried the MBSID application on this derivative for a long time - which MIOS release are you using, and which firmware version? Best Regards, Thorsten.

Did you change the relative positions in LC_HLP_MTCPositionGet_SMPTE (lc_hlp.inc)? Please compare it with the original code - this function should not be touched to ensure, that all digits are print on screen Best Regards, Thorsten.

It's maybe a short, by sending different characters the affected data line can be found out. MIOS Studio provides a special debug window which allows you to send characters to the LCD. They will be visible for 2 seconds, before the MBSID application switches to the previous screen again. Could you please write down which characters you see when following strings are sent to MBSID: (these are 8 spaces) 00000000 11111111 22222222 44444444 88888888 @@@@@@@@ PPPPPPPP aaaaaaaa pppppppp Are you using a PIC18F452, or already a PIC18F4685? Best Regards, Thorsten.

It's explained here: http://www.ucapps.de/midibox_seq_v2.html Keyword: "vintage" Note that MBSEQ V3 doesn't support pots/faders anymore, therefore the reference to MBSEQ V2 Best Regards, Thorsten.

Most of your requests are already implemented! :-) See the user manual and listen to the sound examples: http://www.ucapps.de/midibox_sid_manual.html Unisono: search for detune. Offset: search for phase offset and delay Independent control of oscillators is possible with the multi engine. The voices are dynamically allocated, but especially for ring/sync effects I've added an optional static allocation. So: yes you can do this, but the gate of the third oscillator needs to be controlled from a seperate MIDI channel. By enabling GSA, the gate will stay active once it has been triggered the first time. Best Regards, Thorsten.

Hi Razmo, yes, super-poly isn't a big deal, but there are about 1000 other features I want to add to the first final release which are also cool, and also easy to implement. Step by step w/o hurry - I'm young, I've the time... ;-) Full SysEx Implementation is already available for the lead and multi engine. There is no user-friendly documentation, but as you are a programmer: The SysEx strings are listed in midibox_sid_sysex_implementation.txt The SysEx structure in app_defines.inc, search for "Patch Record Structure" Most important for Sound Diver handling is the capability to divide a 8bit value into two 4bit values, because the sysex data part consists of 1024 nibbles for a 512 byte patch Best Regards, Thorsten.

With MBSEQ V2 (vintage option for analog controllers) you can do this Best Regards, Thorsten.

Maybe it's possible to narrow down the issue: which kind of characters do you see on screen? Are they changing from time to time, or are these always the same characters? Do you see some text (e.g. Chn.) which doesn't change? Best Regards, Thorsten.

Status: got the parts, haven't found the time yet to build the circuit Best Regards, Thorsten.

Soviel ich weiss, hat dieses Remote-Display Konzept noch niemand umgesetzt. Und die Programmierung ist auch leider nicht ganz so trivial, da man das Menuhandling komplett ueberarbeiten muesste, um den MIDI Traffic zu minimieren. Die MB64 Applikation ist hierfuer nicht geeignet. Am besten faengt man ein neues Projekt an, in dem man von Anfang an darauf Ruecksicht nimmt. Dieses koennte auch in C programmiert sein... Gruss, Thorsten. P.S.: auch von meiner Seite Respekt dafuer, dass Du eine funktionsfaehige Box bereits im ersten Forumposting vorzeigen kannst! Was dagegen, wenn ich sie in der MIDIbox of the Week Section veroeffentliche? :)

For the MIDI router project, I warmed up a waldorf knob in a hot-water boiler, so that it was elastic enough to stick it over a burns encoder. It can be easily removed without a knife Best Regards, Thorsten.

Hi Tom, my first statement to this issue won't help you, but I must highlight this: thats a very interesting observation! I will add the reset trick to the troubleshooting guide as an important experiment to check, if the core module is booting thereafter. But before, the reason for this failures has to be found out of course. It's propably a power issue - maybe your PSU doesn't deliver enough current during power-on, so that parts of the PIC is not properly reseted? I guess your LCD has a backlight? Did you already try to boot the MIDIbox without the LCD backlight connection? Best Regards, Thorsten.

I'm surprised that you already took care for a heatsink and ventilation slots - your MIDIbox seems to be constructed better than many other ones. Also the operating temperature range of the LCD seems to be normal. If random characters appear again, please measure the supply voltage. This could give a hint (but propably it doesn't... just a hope ;-)) Best Regards, Thorsten.

Thats very hard to say, and I'm sure that if anybody would start to write down a list, it would be partly wrong, or some ground connections would be missing. The easiest approach is to compare the board with the schematic. I would propose to print out the schematic, search the parts on the board in the schematic, check if it is connected to ground, and wire the appr. connection if it is missing. Mark off each part you've checked that way to ensure that none is missing at the end. This should be a process of ca. 15 minutes - and it will be complete :) Best Regards, Thorsten.

I used some spare parts and haven't taken care for certain trimpot values or capacitor types. The circuit matches with the schematic in the datasheet. No tricks, no black magic. For best circurity please ask an analog expert, and not me - I'm a novice in this area and the wrong person who could give you the right tips. I'm happy enough that I haven't fried the CEM3378 during the experiments, and I don't want to take over the responsibility that you destroy your own CEM3378s Best Regards, Thorsten.

Great, thank you very much! :) It listened to the session four times today in the car (direction Italy - nostalgic feelings - perfect match ;-)) Best Regards, Thorsten.

Hi Matteo, in my eyes this is the expected behaviour. All parameter layers are controlled by the trigger layers. There is only a single gate for all layers, and this one will trigger all Notes/CC of the step. There is no solution available which allows to trigger the notes/CCs independent from each other (only exception: the event modes which have been prepared for drums) Best Regards, Thorsten. P.S.: thanks for the postcard! :)

Hi, yes, higher temperatures can cause such effects. Do you have a datasheet of your LCD? What is the specified temperature range? Is your MIDIbox built into a closed plastic case without "ventilation slots"? Maybe it makes also sense to measure the voltage at J2 when this happens. If it is much below 5V (I mean, 4.8V or less) due to increased heat, such random effects could happen as well. In this case, a heatsink for the 7805 could help - or if your MIDIbox is built into a metal case: just screw the 7805 on the bottom or sidepanel of your case. Best Regards, Thorsten.

ALBS is located in germany - it could make sense that somebody in Europe is doing the group order for ALBS knobs to save shipping costs and tax fees. ...how about a new "group order" board? ;-) Best Regards, Thorsten.

yes, it also works with other engines, just only the hold function is missing (yet) The same mechanism will be provided by the drum engine. Btw.: thanks to the ensemble it is possible to control all SIDs from the same MIDI channel, and to define split points in order to select sequences from different keyboard zones, or to layer them (e.g. selecting a bassline and drum sequence with a single key) You can also use the modulation matrix of MBSID, it selects and displays sequences in bassline/drum mode. :) However, something "Monome" like works also fine, but note that there is no feedback for LEDs, to display which sequence is currently selected. Best Regards, Thorsten.

Tables can be added anywhere. You don't need to specify a specific start address. Only exception are tables in setup_*.asm, but I guess that there is not enough free memory anymore between 3080 and 3300 Just include the file which contains the table at the end of main.inc, before "seq_presets.inc" is included 2: yes, it's a mistake in the .pdf file Best Regards, Thorsten.

Here a short impression - this demo is played with a single core and two SIDs. It basically consists of two sequences, which have been copied&pasted 4 times and slightly modified within the SEQ editor: There are different modes to play a bassline... In this demo I used a mode which allows to select sequences with a MIDI keyboard, so that I was able to switch back and forth between different parts with one hand, while tweaking sound parameters with the other hand. http://www.ucapps.de/mp3/midibox_sid/mbsidv2_bassline_demo1.mp3 Btw.: all 8 sequences are allocated, and I don't use the parameter track... Best Regards, Thorsten.

Of course, like the Lead and Multi engine, also the Bassline (and Drum) engine will get some randomize functions - it is possible to generate a completely random patch, or to randomize specific sections (e.g. only OSC settings, only Env, only LFO, only notes, only accent, only slide, etc...) from a special menu page --- so long, until it sounds cool. Again ;) Of course. There is a special edit screen (which differs from the normal WT editor for most ergonomic note entry). And you can add analog pots in order to control the typical 303 parameters. You can also control them from the Knobs layer with rotary encoders, or from a special menu page if you don't want to use the minimal control surface only. And in far future there will also be a Control Extension (breakout box) as described in the wishlist. But note that this extension is a low priority feature for me - first I want to see the complete firmware before deciting the final layout of this extension. It should fit perfectly for all engines, not only for basslines Best Regards, Thorsten.

I don't want to say that this isn't a nice idea, and I also don't want to say that it wouldn't be easy to add such a feature - but I'm sure that I won't have the time for a firmware update in the next months. However, I've started a list of feature requests here: http://www.midibox.org/dokuwiki/doku.php?id=midibox_cv Just add your ideas No guarantee that I will implement this - but if something else wants to contribute, just step forward - it's open source and one of the easier understandable applications! Best Regards, Thorsten.

Yes, it's actually the row index. The name seems to be an artefact from another code. However, it's important that the counter variable is located at a different address than SEQ_BLM_ROW_CTR, since ROW_CTR is incremented from an interrupt routine, and COL_CTR (which should mabye be renamed to ROW_CTR2) is incremented from the main thread (conflicts have to be avoided) Best Regards, Thorsten.