TK.

Hi, for 36 encoders, you probably have to set the DEFAULT_ENCODER_GROUP_WIDTH setting to 64, as this is the next 2^n value after 32 Best Regards, Thorsten.

Are you able to send the patches with MIDI-Ox? Note, that the "delay after F7" has to be set to about 750 mS Does MBFM return an acknowledge message whenever a patch has been received? Best Regards, Thorsten.

Hi, currently only notes can be recorded, recording CCs is planned for one of the next releases. I guess that not more than 10..20 people have built a MBSEQ yet Best Regards, Thorsten.

Hi, remapping has to be done in main.asm and mios_tables.inc Thereafter recompile the code as described here: http://www.ucapps.de/howto_tools_mpasm.html Best Regards, Thorsten.

Great! :) Best Regards, Thorsten.

No, a bootloader was not used for PIC16F, since the flash size was already very limited. Best Regards, Thorsten.

"Bankstick A not ready" will be displayed, if TL's patchmanager doesn't receive the acknowledge message from the core after a patch has been sent. Are you able to overwrite the first patch? This would indicate, that the PC MIDI Out->MBFM MIDI In connection is ok, and MBFM MIDI Out->PC MIDI In is not working Best Regards, Thorsten.

Which USB interface are you using? (just for the records) Best Regards, Thorsten.

Yes, I used MIDIbox FM, and in the second half MIDIbox SID. Best Regards, Thorsten.

RC14 is available now, it contains some bugfixes. I hope that I haven't broken anything with these changes (normaly the small changes cause the unexpected effects... ;-)) o BankStick write via SysEx now gracefully aborted if only 32k BankStick is addressed and patch number >= 065 SysEx error number 0x11 ("BankStick too small") will be returned in this case o the "send dump" function of the "shift menu" now sends the edit buffer of the selected SID, which also includes the corresponding device ID. BankStick content won't be overwritten if such a dump is sent back. o menu page automatically changed to the previous selection if SID master or slave selected which is running with a different engine [/code] Best Regards, Thorsten.

Yes, the 5 "soft functions" which correlate with the displayed parameters are already there. It is sufficient if the LCD only displays the 5 items, the two unusued LCD lines could be filled with additional informations later (although nobody has good ideas for what to display there...) - most of the MB6582s are stuffed with a 4x20 display. However, my proposal is still the usage of a 2x20 (or alternatively 2x40) display. 2x20, because I'm using the same, accordingly it can be considered that the display screens are layouted perfectly for this size. 2x40, because this is the only straightforward solution for displaying 10 parameters - on a 4x20 it really looks ugly. Best Regards, Thorsten.

There is a nice inbuilt bassline and drum editor in the MIDIbox SID (control surface required). Of course, an external GUI, running on a computer, would be a good alternative solution. The basics are there (full access to sequences via SysEx), but an external editor software is not available yet... A step sequencer is not a common MIDI sequencer - especially because of the quantisation. Best Regards, Thorsten.

thats a good idea, because it also matches with the sequencer concept. If both LEDs lit (green and red), one of the instruments would be played accented. I already built a 4x16 duo-LED/button matrix, but I must say that I would never do the same wiring effort again. A PCB based solution is a strong requirement. Yes, ENC28J60 - Seppoman made some good experiences with this chip. Best Regards, Thorsten.

Are the OP amps directly supplied by the batteries - so, isn't there a voltage regulation? In such a case it's very unlikely to get stable results. Best Regards, Thorsten.

Hallo Paya, willkommen im Forum! :) Die falsche Spannung am Tx Pin deutet darauf hin, dass der Bootloader nicht gestartet wurde. Andererseits: wenn der PIC nicht im Sockel steckt, sollte eigentlich gar keine Spannung anliegen. Ich kann mir das nur so erklaeren, dass evtl. der MIDI Out Port noch mit einem MIDI Interface verbunden war? Zurueck zum Bootloader: hat den jemand in den PIC gebrannt? Ansonsten wuerde ich auch nochmal die Reset Leitung (MRST#, Pin 1) ueberpruefen, hier sollten 5V anliegen. Auch die Oszillator-Pins sind heisse Kanditaten, doch die kann man leider nur mit einem Oszi ueberpruefen - oder zumindest nochmal visuell auf evtl. Kurzschluesse untersuchen. Gruss, Thorsten.

The setup/hold timings are ok, and based on your new experiments, I would say that it really looks like a crosstalk issue between a single data and conrol line, especially because most of the failures are reproducible, but some are sporadic. Maybe it's caused inside the connector that you are using for the ribbon cable? You tested the LCD with "Smartie" - did you connect the LCD with the same cable to the PC? Would it be possible to check this? Best Regards, Thorsten.

Some of you might remember following entry in the wishlist: ----------------------------------------------------------- MBSID Control Extension: as discussed in http://www.midibox.org/forum/index.php?topic=5680.0, but I think that I will overwork the concept so that it is also useful for the other subsystems. This control extension is something like a "breakout box", which is dedicated for easy editing of bass- and drumline sequences. For the MBSID-Lead and MBSID-Multi subsystem it could be used as simple keyboard, for mutes/solo or for quick patch changes. We will see. I propably won't start with this extension before next year - first I want to see MBSID V2 completely working. ----------------------------------------------------------- My statements are still valid, but I'm still not sure about the best solution which fits for all needs. E.g., what I don't like on your proposal is, that a 4x16 LED matrix is not sufficient. Just think about all the possible setups. There is a 8 track drum sequencer, which controls 16 instruments. Accordingly, the LED matrix should consist of 16x16 LEDs - but are the increased frontpanel costs really reasonable? And what about the remaining 3 SIDs which can run the same, or any other engine? How should they be handled? Thats really difficult to decide. E.g., the for basslines and drum engines which are running in parallel it would be important that sequences can be switched back and forth without using an "instrument" button - means: all sequences directly accessible. Like demonstrated in bassline demo #3 where I'm using a common MIDI keyboard for this. In addition, it's possible to control sound parameters with key velocity, which might be a strong requirement for a control extension - if it should replace the already working MIDI keyboard solution (?) - as well. Another idea: if an additional PIC is used to control the extension, it could be connected to MBSID via CAN interface and act as additional bus master. This would not only allow to access MBSID, but also other MIDIboxes, like for example MB-808? And to give you more insight into my secret plans ( ;-) ): one of the next things I want to evaluate is MIDI-over-IP, since it's natively supported by MacOSX, and not only useful for sending MIDI control data, but also to handle the OSC protocol (useful for windows users as well, e.g. Reaktor supports OSC). So, the control extension could provide an ethernet option as well. And this would make it to a real universal solution, which is worth the DIY effort. Best Regards, Thorsten.

Yes, I know what you mean - I'm still thinking about a good solution. A simple workaround could be, that the CS jumps to the root page whenever a SID core is selected, which is running with a different sound engine. But the perfect solution would "remember" the menu pages of the different SIDs. Note that the MBSID V2 already provides all controls for such a special MIDIbox. For example, it is possible to add analog faders/pots to the analog port for controlling the knob functions as an alternative way to the "OSC Assign" layer (-> rotary encoder), which provides the typical CutOff/Resonance/EnvMod/Depth/Accent knob as well. It's even possible to select the sequences from control surface by using the matrix selection buttons. I prefer the usage of a MIDI keyboard, not only because there are more keys and the selection is somehow faster, but also because it allows me to control sound parameters via velocity. They keyword is NRPN, and the usage is explained in mbsidv2_parameter_chart.txt with some examples. If it isn't clear enough, I would propose to open a new topic and ask there for more specific infos. Best Regards, Thorsten.

yes, I used the slightly modified "Drum Kit 2" preset + the sequences, which are part of the patch. Best Regards, Thorsten.

In lc_leds.inc, you have to search for the keywords "CATHODES" and "ANODES". Below these lines, add " comf MIOS_PARAMETER1, F" to invert the pattern. Note that there must be a whitespace (space or tab) between the first column and the "comf" instruction, otherwise the assembler will interpret the instruction as a label, and fail. Best Regards, Thorsten.

I think that the common gatelength function is exactly what you need. E.g., at 120 BPM a single 16th note can control the length from 5 mS to 125 mS in steps of 5 mS By using the global clock divider in the BPM menu, or a local clock divider in the track div menu, you can scale the length by a certain factor. If you are using 4 (as an example), the resulting gate length would be 20 mS .. 500 mS in steps of 20 mS. So, this approach is sufficient for gate lengths > 1 mS, only disadvantage: the length depends on the BPM rate. But I guess that it won't be a big problem for you to re-adjust the gatelength in layer C whenever the BPM rate is changed dramatically. Best Regards, Thorsten.

Why do you want to use triggers instead of the normal gatelength (which depends on the BPM rate, and which is fineadjustable in 24 steps for each 16th note) Best Regards, Thorsten.

Moment, you mean the length of the 1 ms triggers, right? This length cannot be modified, because it directly depends on the SRIO chain sample rate. As described in my first answer of this topic, the current implementation doesn't allow to vary the length. And a solution is really not so easy, otherwise I would spend an hour and hack it into the firmware for you... Best Regards, Thorsten.

Thanks for the compliments! :) I put the drum and bassline patch into a package and wrote a README.txt which describes the setup requirements + workflow. Have fun -> http://www.ucapps.de/midibox_sid/mbsidv2_bassline_demo3_patches.zip Best Regards, Thorsten. P.S.: meanwhile I modified the firmware, so that patch dumps, which are sent from the control surface (-> Shift menu), contain the edit buffer of the selected SID (previously only the dump of SID1 was sent, and it contained a bankstick write request) - so you can upload these patches without the danger of overwriting a BankStick location. This change will be available with RC14 Best Regards, Thorsten.

It's normaly in Layer C Best Regards, Thorsten.