TK.

You are right, I should slowly do the next step of the "old project phase out" - removing the page from the navigation bar ;) Best Regards, Thorsten.

Thank you! But: you missed that I've changed the format a little in the meantime - the name of the scale (20 characters) is part of the table as well. Do you want to change this, or should I do the required modifications? Best Regards, Thorsten.

If you think, that all the big shiny MIDI controllers with blue LEDs, silver knobs, high-speed Alps faders, 128 PPR rotary encoders, alu frontpanel, multicolour engravings and wooden side frames could impress a lady, then you are propably on the wrong track! Jaybee demonstrates with her MIDI doll (original name "MIDItrulla"), how an attractive MIDI controller should look like:

Hi John, I've created a new Wiki page which discusses this topic, and gives two examples: http://www.midibox.org/dokuwiki/doku.php?id=button_overlay Please inform me if anything is missing, so that the page can be improved. Best Regards, Thorsten.

The "ensemble" (which contains MIDI channel, Splits, Transpose, Patch/Bank, etc... informations) will have some additional custom parameters free for such static settings. It's on you to program a driver which controls additional AOUT modules. I cannot support such special variants from my side, as it would increase my own support effort significantly. But the basics have been considered. Best Regards, Thorsten.

I've released an updated version (midibox_fm_v1_1a) where this issue is fixed Best Regards, Thorsten.

No, Windows should just find the drivers in the ez-usb/driver directory. There are alternative drivers available, maybe it's worth a try. Just google for "ezusb driver" Best Regards, Thorsten.

As answered in another article, in MBSID V2 controlling AOUT modules has been completely integrated into the patch structure, and into the modulation matrix It's already integrated into the existing MBFM patch structure (but with much less modulation possibilities compared to MBSID V2 - which is a modulation monster! ;-)) Best Regards, Thorsten.

Hi Diex, the easiest way is to use following register settings: volume register: 0x0f --- you should hear additional background noise now! frequency register (low/high) of voice 1 = 16777 (for 1kHz) Sustain/Release = 0xf0 Attack/Decay = 0x00 Waveform = 0x11 (Triangle, Gate on) You haven't listed the reset signal of the SID - how is it controlled? Maybe it's permanently active? Best Regards, Thorsten.

Hi, this has been prepared in the patch structure of MBSID V2: SID_Ix_CUSTOM_SW EQU 0x014 ; custom switch flags #1-8 SID_Ix_CUSTOM_PAR1_L EQU 0x040 ; custom parameter #1 (e.g. for AOUT) SID_Ix_CUSTOM_PAR1_H EQU 0x041 SID_Ix_CUSTOM_PAR2_L EQU 0x042 ; custom parameter #2 SID_Ix_CUSTOM_PAR2_H EQU 0x043 SID_Ix_CUSTOM_PAR3_L EQU 0x044 ; custom parameter #3 SID_Ix_CUSTOM_PAR3_H EQU 0x045 SID_Ix_CUSTOM_PAR4_L EQU 0x046 ; custom parameter #4 SID_Ix_CUSTOM_PAR4_H EQU 0x047 SID_Ix_CUSTOM_PAR5_L EQU 0x048 ; custom parameter #5 SID_Ix_CUSTOM_PAR5_H EQU 0x049 SID_Ix_CUSTOM_PAR6_L EQU 0x04a ; custom parameter #6 SID_Ix_CUSTOM_PAR6_H EQU 0x04b SID_Ix_CUSTOM_PAR7_L EQU 0x04c ; custom parameter #7 SID_Ix_CUSTOM_PAR7_H EQU 0x04d SID_Ix_CUSTOM_PAR8_L EQU 0x04e ; custom parameter #8 SID_Ix_CUSTOM_PAR8_H EQU 0x04f [/code] In addition, up to 8 AOUTs will be available as modulation matrix targets Best Regards, Thorsten.

Hi Max, this could be a configuration problem. For the 8 gates at J5, you have to set ENABLE_J5 switch in main.asm to 1 Also the AOUT_LC modules need to be configured in main.asm, for 8*8 bit you have to set: #define DEFAULT_AOUT_LC_1_RESOLUTION 2 ; 1st AOUT_LC module #define DEFAULT_AOUT_LC_2_RESOLUTION 2 ; 2nd AOUT_LC module #define DEFAULT_AOUT_LC_3_RESOLUTION 2 ; 3rd AOUT_LC module #define DEFAULT_AOUT_LC_4_RESOLUTION 2 ; 4th AOUT_LC module Thereafter build a new .hex file like described here: http://www.ucapps.de/howto_tools_mpasm.html it's normal that the 7805 gets very hot, especially when a backlit LCD with full brightness is connected. So long the core doesn't reset randomly, this is acceptable. Alternatively you can reduce the backlight brightness, or add a headsink to the 7805 Reboot when pins are shortened - I would propose to add small resistors to the gates and CV outputs, e.g. 100 Ohm, in order to prevent a short circuit. Please let me know if it helps Best Regards, Thorsten.

No, the 4051s shouldn't be so sensitive - many geeks never use sockets for these chips. Do you see the same random CC events when no AIN module is connected, and all analog inputs at J5 are clamped to ground? What happens, when only one multipexed channel for 8 pots is connected to the first analog input of J5, and the others are connected to ground? (for this test, the 4051s have to be supplied with Vss/Vdd, and the 3 select lines have to be connected to J6 of the core module) Best Regards, Thorsten.

Programming works fine under WinXP. Once the module is connected w/o EEPROM, Windows should ask for the drivers. If this message doesn't pop up, than it's very likely an issue with the USB connection, or with the module itself (bad solderings?) A 24LC512 EEPROM cannot be used, as it has a 16bit address register, but only EEPROMs with 8bit address register are supported However, once your module is detected by Windows, and once the Cypress driver is installed, you can temporary upload the mbhp_usb_midi*.hex file through the EzMr Control Panel - you have to do this after each restart manually. With the EEPROM, the firmware will be available permanently. Best Regards, Thorsten.

I think that using a single core is the easier solution in this particular case. Hopefully this evening I will find some time to program and test the small routine for you! Best Regards, Thorsten.

Thanks for reporting this, it seems to be a programming error. Open mbfm_se.inc, search for MBFM_SE_Note, and remove this block: ;; transpose it movlw MBFM_Ix_TRANSPOSE movf PLUSW0, W sublw 0x40 xorlw 0xff IFSET WREG, 7, movlw 0x00 addwf IRQ_TMP5, F [/code] you will find a similar code below these lines - this is the right one Best Regards, Thorsten.

Maybe the pins of the MIDI In socket are swapped, or the LED is connected the wrong way (cathode = short leg has to be connected via a 220 Ohm resistor to ground) Best Regards, Thorsten.

very inspirational! :) How are your plans for mounting the LEDs? Getting them aligned with the holes in the frontpanel is very difficult when they are mounted on the PCB. Thats the reason, why I either use smaller boards, or glue the LEDs into the panel Best Regards, Thorsten.

Hi John, MB64E (which is better than MB64) has a fixed data structure for 64 buttons, 64 LEDs, 128 7bit events for rotary encoders or pots, and 64 LED rings. If the remaining 32 buttons should only be used to send statically assigned MIDI events (e.g. Note On events), I could give you a small routine which has to be inserted into USER_DIN_NotifyToggle Note that the encoders require 16 digital inputs - you need 4 DINX4 modules Best Regards, Thorsten.

Yes, I'm using my V2 control surface as well. I've added a second 19" box for a button/LED matrix and 4 group select buttons, but this is only a freaky "nice-to-have" extension and not required to access all available functions. I used my sequencer 6 months without it, before I built it just for fun, and not because it's a "must-have". No, they will be formatted during the first startup with v3 - the data structure has been changed for 32 step tracks and more control informations. A v2 pattern compatibility is not provided by the firmware itself, but in theory patterns could be converted with a special program So, in fact you only need to replace the PIC18F452 by a PIC18F4620, and you will already be able to use the new firmware. Hint: some PIC18F4620 have been recently offered for cheap money in the Fleamarket section by people, who bought it for their MBSID V2 (but which will need a PIC18F4685 in future) In addition to the new PIC, at least one MBHP_IIC_MIDI module is useful. Details are listed here: http://www.midibox.org/dokuwiki/doku.php?id=mios_pic18f4620&s=pic18f4620 Just consider, that MBSEQ V2 has been programmed 4 years ago... since this time I collected ideas of users and myself, which couldn't be integrated into the small PIC18F452 anymore, but which would be nice to have once bigger PICs are available. I also worked on solutions how to overcome known problems and limitations. To say it short: the MBSEQ V3 firmware is a work of 10 months. It's not just a small upgrade, you will experience a completely different machine! :) Best Regards, Thorsten.

It is a known problem with MBSEQ V2, and in fact there are much more inconsistencies. The whole engine has been overworked in MBSEQ V3 based on the experiences I made with V2, so it's really worth a try! Best Regards, Thorsten.

Ueberpruefe mal die Versorgungsspannungen an den 74HC14 (siehe Schaltplan), evtl. ist Vss oder Vdd irgendwo nicht angeschlossen (Loetstellen ueberpruefen), und die Chips/LEDs werden ueber den Druckerport versorgt - das wuerde fuer ein schwaches aufleuchten der LEDs ausreichen, nicht aber zum Brennen eines PICs Gruss, Thorsten.

MBSEQ V3 provides four different approaches. 1) static randomisation within the utility menu: Just press the button below "Rand" and a new random pattern with random notes/velocity/length/gates will be generated Press and hold the random button and turn one of the rotary encoders to increase/descrease the randomness (+/- x) 2) "humanisation": Adds non-static randomness to Note/Velocity/Length, the intensity (+/- x) can be selected as well 3 and 4): random Gate and Value for specific steps: Part of the trigger layers - allows you to trigger the gate and/or to play the Note/Velocity/Length value randomly on steps where this function is activated Min/Max values are nothing else than defining the "mid" value within the layer, and adding the selected "intensity" (+/- x) to this value Different Note Scales are provided for "harmonic randomness" When I'm speaking about Notes, I mean MIDI events - it could also be a CC or it could be a chord of up to 4 notes. And don't forget: there is a loopback port which allows you to control any sequencer parameter randomly - so, not only the step events, but every parameter which is listed in the CC implementation table Just think about random morphs between two patterns, random progression parameters (jump back and forth), random clock dividers... So, of course, there is always something which somebody has seen in another sequencer, and what he would like to see in MBSEQ V3 as well, as requesting features - and especially asking "is it possible..." is so easy. But from my oppinion, nobody should do this before he has tested the already existing features - there are a lot of things to explore :) Best Regards, Thorsten.

I read your thread again, just to be sure, but I haven't found anything, which isn't already possible with MBSEQ V3, or did I miss something? ;) Best Regards, Thorsten.

Hi Rio, it took some time to find out, how to reproduce this, because you missed to mention, that this only happens when the paste target position is not the first step (or in other words: when a part of the pattern is copied to another position) Next bug, please! Gruss, Thorsten.

There is a new build #72 which got a bugfix in the paste function (triggers were overwritten when paste target was not the first step) Best Regards, Thorsten.