TK.

:-) Best Regards, Thorsten.

Hi Xavier, yes, it doesn't allow you to route analog input signals to the LFOs - but thats all. I'm missing the CC and Edit button - in MBSID V2 they could get a special alternative purpose (not sure, if the link button will get an alternative purpose as well) You could assign the keytracking parameter to the encoder between Resonance and Rate There won't be much memory space in the PIC18F452 for such features (but you will notice this sooner or later...) However, in MBSID V2, the matrix handling will be overworked (more flexible assignments), and I will propably consider more informative LCD messages if there is enough space within the PIC18F4620 flash after all the features have been implenented Best Regards, Thorsten.

What is the output voltage of the 7805? Best Regards, Thorsten.

Ausser dem Code gibt es auch noch eine Dokumentation auf meiner Website ;-) -> http://www.ucapps.de/midibox_sid_csB.html (siehe Beschreibung der Buttons am Ende der Seite) Link ist nicht unbedingt notwendig, mit CC lassen sich Parameteraenderungen mit einem externen Sequenzer aufnehmen und somit automatisieren, bei aktiviertem Edit Button werden Patchaenderungen automatisch abgespeichert, wenn Du zu einem neuen Patch wechselst. Bei MBSID V2 koennte es passieren, dass die Buttons weitere Funktionen erhalten, ich wuerde sie nicht auslassen Gruss, Thorsten.

Which software are you using? Sometimes it sounds like you have recorded the chords live, activated a quantisation and the sequencer shifted the notes to the next step Best Regards, Thorsten.

Could you please upload the MIDImon application and check, which MIDI events are received when this happens? It sounds, like one of your MIDI devices sends an invalid or incomplete MIDI event Thats really strange, I never heard of such a effect. Maybe - alternatively to the assumption above (wrong MIDI events received): could it be, that one of your MIDI devices has no optocoupler at the MIDI In? And if this device shares the ground with the core & AOUT module, then some really unexpected things can happen - this is the reason, why according to the MIDI spec each MIDI device should have an optocoupler I just tried to reproduce this, but without success. I don't want to except that this is a bug, but it could also be related to your MIDI Timeout issues. Once they have been solved, could you please try this again? And if it still happens, could you then send me a SysEx dump of your configuration? (It can be sent from the last menu page, and it can be received with MIDI-Ox) Best Regards, Thorsten.

Hrmpf, this was an error in my step-by-step instructions - the battery must be connected to J1, otherwise the 7505 won't be supplied, and the logic chips would get their voltage indirectly from the LPT port, which cannot work properly. So, I've changed my list above, could you please check this again? I haven't written such a detailed documentation where the purpose of each single component is described, I know that this could be useful, but I don't find the time for such stuff. I also don't know, where you could find more hints about such digital designs... Best Regards, Thorsten.

Hi Digi, this could be a bad soldering on the power connections, you should especially check them - note: once the LCD got no power, it needs to be initialized again by MIOS (easiest method: power off/on the core), otherwise it will show the black bars like during the bootloader phase. Best Regards, Thorsten.

I haven't spent any additional thoughts on this yet, as you propably know, I'm currently working on MBSEQ V3 and this requires my full concentration. Any statement I give now could be obsolete 2 months later, when I get ideas for even more powerfull MBSID V2 features - when you follow the progress of MBSEQ V3, then you know what I mean. It wouldn't be a big problem to add a feature which allows to send MIDI Notes out, this even could already be integrated into MBSID V1 by adding some lines of code into the sid_wt.inc functions... For the control surface I don't think that it will exactly look like the one of TB303, because I don't find it erconomic. If you are searching for a 1:1 TB303 sequencer clone, then I cannot help here, because I'm not interested in such a project. You could have a look into this forum: http://19642.forendienst.de/index.php, where such a DIY sequencer is documented. Best Regards, Thorsten.

In german it is called "Fädeldraht" Buttons are connected to a 4x8 matrix, and LEDs to a 4x16 matrix. I've written a special driver which allows to control the red and green LED seperately. No problem here, it takes some time to melt the insulation with a soldering iron Together with a second board it will be an extension for MIDIbox SEQ. So, I will see some animated colour LEDs soon :) Best Regards, Thorsten.

Fine :) I think that the synth sounds are a too dominant, I would add a delay fx which is synchronized to the tempo (but I must say that I'm a delay fetishist ;-)) The beats should be stronger, EQs and a compressor help to make them louder And I'm missing the bassline, also a second synth hook overlayed to the pads would be nice Best Regards, Thorsten.

Why do you want to build a MBSEQ, when MBSID V2 will provide a dedicated control surface extension for TB303 mode? See also the bottom of this page: http://www.ucapps.de/midibox_sid_v2_wishlist.html Best Regards, Thorsten.

Here my experiences: by using verowire the LED connections can be made flexible enough so that there is no danger that the legs get broken over lifetime. Verowire is expensive, but allows to wrap the connections between buttons, LEDs and shift registers quickly - compared to ribbon cable I used in previous projects, it only took 1/3 of the time to wire a complete board, since it was not required to deisolate the cables with a cutter - just heat up the isolation :) Creating the whole module took about 5 hours. Here some pictures: Bottom of the board with all the button connections to the shift registers - you can also see the "Verowire pen" I'm using Glueing the LEDs on the buttons - they are sitting very solid; later they will be held by the frontpanel in addition ...after I soldered the LED connections - it looks a little bit like tinsel over a christmas tree ;-) The module was working immediately :) I'm using Red/Green Duo-LEDs. When both LEDs are lit together, the resulting colour is yellow. So, I've three colours now :) Disadvantage of this technique: I will have to consider a certain tolerance for all button holes, since it is difficult to adjust the distance between the buttons; the LEDs are not sitting 100% aligned! However, I guess (or hope) that with the frontpanel these cannot be noticed anymore Best Regards, Thorsten.

HC works with CMOS levels on the inputs, and HCT with TTL levels, so HC is normaly the better choice It's strange that your dealer doesn't purchase them anymore, because HC is normaly the prefered choice - maybe it's just sold out, and he wants to get rid of the other chips before buying new ones... However, not sure if this is the problem, because 3.3V is still within the TTL range (>2.4V for high level) But I (and most of us) are using HC chips - so, it's a difference which could matter for any reason. Best Regards, Thorsten.

in MBSID, this mode is called "SusKey", the functionality in other words: slide will be activated when two notes are overlapping. In MBSEQ, slides are activated in the same way. But this doesn't give you all possibilities, because when you are using this technique, you cannot indepedently control if on a slided note the gate should be retriggered (or not), or that the note should be accented. Best Regards, Thorsten.

Lassen wir ihn mal als Reminder fuer alle, die noch nicht wissen, dass es Preset Patches gibt ;-) Gruss, Thorsten.

Whenever you are pressing a button which is assigned to a Fx event (Exception: FF), or when you are turning a pot which is assigned to a Fx event, the application will branch to the meta handler in mb64e_meta.inc - so, if you do see other MIDI events as expected, the problem must be inside the meta handler, and nowhere else. No, a midibox64e.syx file only overwrites the configuration data, it doesn't overwrite any code Best Regards, Thorsten.

Emulating TB303 sequences completely via MIDI is mostly not possible, because synths normaly don't provide a way to change the pitch to a new note and to activate the slide without triggering the gate. See also http://www.ucapps.de/howto_sid_bassline.html, example for the Code "26" Such a function can be partly simulated by dynamically switching between mono and legato mode via CC, but the implementation depends heavily on the capabilities of the target synth. Best Regards, Thorsten.

Sounds similar (not equal) to how I've implemented chord mode 2 (see last sneak preview #3) A big difference is, that you can use any track (of 16) to control the transpose (of you don't want to use an external keyboard). The advantage is, that you can quickly switch between different parts of the song (e.g. chorus, break, etc...) just by changing the track group from where the transposing is done. This track group cannot only contain the transpose line, but also additional drums (for filling the beats), additional licks, or whatever. Transpose can also be done from multiple tracks which are running at different speeds, with random gates and/or random steps for very experimental results. :) Best Regards, Thorsten.

Hi, you can do this by mapping the group number to the LEDs: ################################################################################ # LED Map: assignes the LED shift registers to the Button Shift # registers or special values # Currently following values are supported: # 0 Default Setting (see Map below) # 1 Button Shift Register 1 (Button ID #1-#8) # 2 Button Shift Register 2 (Button ID #9-#16) # 3 Button Shift Register 3 (F1-F4 and Navigation Buttons: ID #17-#24) # 4 Button Shift Register 4 (Button ID #25-#32) # 5 Button Shift Register 5 (Button ID #33-#40) # 6 Button Shift Register 6 (Button ID #41-#48) # 7 Button Shift Register 7 (Button ID #49-#56) # 8 Button Shift Register 8 (Button ID #57-#64) # 9 Selected Group (1 of 8) # 10 Selected Bank (1 of 8) # 11-15 reserved # 16 MIDI Status received for Button ID #1-#8 # 17 MIDI Status received for Button ID #9-#16 # 18 MIDI Status received for Button ID #17-#24 # 19 MIDI Status received for Button ID #25-#32 # 20 MIDI Status received for Button ID #33-#40 # 21 MIDI Status received for Button ID #41-#48 # 22 MIDI Status received for Button ID #49-#56 # 23 MIDI Status received for Button ID #57-#64 # 24-31 reserved ################################################################################ [/code] So, assignment option #9 is for what you are searching for Best Regards, Thorsten.

Hi Matthias, no problem reg. the song name ;-) It seems that it is not allowed to access the mp3, the error message is "Das Aufrufen dieser Daten von extern Quellen ist nicht erlaubt" Best Regards, Thorsten.

It refers to my solution within the assembly code, you can export a label (= address which will be determined during the link stage) with "global <label-name>". Within the C program, you can import the label with "extern" no, this is not required general examples how to import/export labels between assembly and C code can be found in sm_c_example1_v1, sm_c_example2_v1, midi_router_v1_0b It doesn't make much sense to bring this into MIOS, it would blow up the code size and wouldn't have any advantage for people who don't use a GLCD (more than 99%) You can just add the additional fonts to the application When you are including the fonts like I have described in my first article, you won't run into problems - and when you replace the "org" by a global, you don't need to calculate an address Best Regards, Thorsten.

If only a small set of brightness levels are required, you could do this via PWM - no additional hardware is required in this case, only a special PWM routine which can be included into the application. I read an article about a clever PWM method for an optimized LED dimming some time ago, unfortunately I forgot the link... :-/ The idea was, not just to change the duty cycle in order to dimm the LED, but to run special sequences of pulses to avoid the typical "flickering" effect. Best Regards, Thorsten.

yes, the V1 firmware runs also on a PIC18F4620, only MIOS and the bootloader are different In other words: the core module is the same, microcontroller and MIOS are different, the application is binary compatible I guess you mean firmware: no, neither the most current V1 nor the future V2 will run on a PIC16F877, this uC is obsolete Best Regards, Thorsten.

Hi Christian, both solutations have their advantages and disadvantages, therefore it would be nice if you could document both in the Wiki (yes, everybody is allowed to change existing pages) Your method has the advantage, that it isn't required to upload the font again and again with each program update. My method has the advantage, that new fonts can be inserted into the project in a similar way. The only thing I would change is the way how the base address of the font is specified. With relocatable code, it makes sense to let the linker decide at which location the font should be stored, by exporting/importing the label of the base address, you can use for example 'MIOS_GLCD_FontInit(font_big);', 'MIOS_GLCD_FontInit(font_small);', 'MIOS_GLCD_FontInit(icons_knobs);' without knowing the absolute address Best Regards, Thorsten.