TK.

Yes, thats an error in MBSID V1, which won't be fixed anymore (as this is an untypical corner case) Best Regards, Thorsten.

it's your personal desition. I'm using 2x8580, 4x6582 and 2x6580 Disadvantage: the filter of 8580 and 6582 sounds equal, whereas the 6580 filters sound different (also between the two chips). Accordingly, I can use the super-polyphony feature only for the 6 8580/6582 SIDs Best Regards, Thorsten.

Ok, a variation for CS_MENU_DISPLAYED_ITEMS == 4 has to be added to cs_menu_enc_table.inc hm! sh* happened - for this I don't know a solution yet /edit: discussion here: http://www.midibox.org/forum/index.php?topic=10039.0 they are pre-defined to 0..fff in setup_6581.asm I guess that you made an error by uploading setup_8580.asm instead of setup_6581.asm? In this case, a "virgin ensemble bankstick" will be completely initialized with the default values for 8580 So, you need to change the correct range manually now just increase the depth of the modulation path - it's 64 by default, max value is 127 Best Regards, Thorsten.

It definitely is strange, as nobody has reported this issue before. There are only 4 lines of additional code I inserted into RC6, and it's only related to voice allocation. Today I checked typical cases which could lead to such effects, e.g. uploading setup_mb6582.hex instead of setup_tk.hex, reviewing the code at the 64k boundary, uploading rc5/rc6 and back to rc5 - but I wasn't able to reproduce this. Please: could anybody who uses a MB6582 please confirm, that cloning is still working, and that the slave cores are running? Narwhal: it could be helpful to know the MBNet and application state - just create a SRAM dump of 0x000 (range 0x80) and 0x600 (range 0x80) with MIOS Studio as shown in this picture: and copy&paste the hex output into your posting. Note that I've selected device ID 1 at the left upper corner. The MIDI output is jumpered accordingly. It would also be interesting to know, why you are waiting for the MIOS boot screen instead of the MBSID version number screen as suggested. This screen follows after the MIOS boot screen. Could it be, that it is not shown on your setup? Best Regards, Thorsten.

Ensure that you are using the latest MIOS Studio version, older versions can only upload code to the 32k flash of a PIC18F452 Best Regards, Thorsten.

Since you've posted this question also in the french forum, I'm not sure if the issue is already solved. I don't know, why TL's patch manager shouldn't be able to access Bank A... maybe some pins of the EEPROM are not connected? Best Regards, Thorsten.

I haven't changed something on the cloning mechanism in any rc* release Could you please try the following: press the MENU button once the MBSID version number is displayed (don't press is during the boot process). This ensures that all cores are ready for receiving the update request. Best Regards, Thorsten.

This topic has been moved to MIDIbox of the Week. [iurl]http://www.midibox.org/forum/index.php?topic=9996.0[/iurl]

Hallo Stuart, danke fuer den Erfahrungsbericht - ich habe den Artikel gleich mal in die MIDIbox of the Week Sektion verschoben. :) English speakers: please use babelfish Das Problem mit den LEDs stimmt mich langsam bedenklich; Du bist wohl nicht der einzige, der davon berichtet, andererseits gibt es MIDIboxen, die mit wesentlich mehr LEDs bestueckt sind, und die trotzdem stabil laufen. Falls Du hier nicht weiterkommst, schreibe mir doch bitte eine PM, damit wir das gemeinsam debuggen koennen. Gruss, Thorsten.

It's normal that there is some crackling noise in background, especially when slow envelopes are used. Best Regards, Thorsten.

Fine! :) I guess you mean a 24LC512 - yes, it's supported, but it doesn't make a difference if you connect a 24LC256 or 24LC512, only 32k will be used. Best Regards, Thorsten.

MBSID V2.0 has already reached its final state; currently the release candidates will be published with the last bugfixes of corner cases (which most people wouldn't notice anyhow). Just today I found an imperfection in the drum voice allocation when Mono mode is activated. It's fixed in rc6 Best Regards, Thorsten.

If the menu button is directly connected to the DIN (no usage of a button matrix), the button has to be pressed while the MBSID version number is displayed. Just press it multiple times to ensure that the event will be notified... Best Regards, Thorsten.

No, you cannot slow down the track with the scrub function. It's better to use the BPM clock divider for this - this one has been made for live usage Best Regards, Thorsten.

The panel looks really good, especially with the flat buttons! :) What are you planning to insert into the lower right corner? LED behaviour: individual assignments are not provided by the firmware, but you can do this for each shift register (group of 8 pins). E.g., if the LEDs connected to the first SR should receive MIDI events which correspond with the first 8 buttons, and the second SR should control the LEDs according to the state of the next 8 buttons, then use following assignments: [tt] LED_SR1 = 16 # (MIDI Status of Button ID #1-#8) LED_SR2 = 2 # (Button ID #9-#16) [/tt] all variations can be found in the midibox64.ini file of the mk_syx.zip package Best Regards, Thorsten.

Yes, I tested it with a 808 some time ago - it works. Best Regards, Thorsten.

It allows you to FFW (fast-forward) the sequencer lines while notes are played. But I must say that I don't really use it - it's only nice when you want to demonstrate some nice features to friends ;-) Best Regards, Thorsten.

ok, then directly try out rc4 this evening (link: see first article of this thread) The number of SRIOs is now configurable in the setup_*.asm file, and it's 10 by default The settings for TK_OPTION and USE_SINKDRIVER has vanished. Now there is only a variation between MB6582 and "normal" approach anymore. Best Regards, Thorsten.

P.S.: could you please check if the LED matrix is working correctly with following setup: #define DEFAULT_SRM_CATHODES 7 #define DEFAULT_SRM_USE_SINKDRIVERS 1 #define DEFAULT_SRM_TK_OPTION 1 #define DEFAULT_SRM_MODMATRIX_DOUT 8 [/code] (no hardware change required, don't be confused about the swapped CATHODES/Anodes definitions) Best Regards, Thorsten.

Ok, I see - this LED matrix variation hasn't been tested for a long time, and when I look into the source code, I see a potential source for a coding error. I will check this and probably release rc4 in ca. 1 hour Best Regards, Thorsten.

You will have to increase the number of SRIO in main.inc (search for MIOS_SRIO_NumberSet) - I will bring this setting into the setup_*.asm file for future releases. To 2: how does it behave when you enable/disable following options (there are 4 combinations, one has already been tested by you): DEFAULT_SRM_USE_SINKDRIVERS DEFAULT_SRM_TK_OPTION Check also the connections of the anodes/cathodes - maybe the shift registers are swapped? DEFAULT_SRM_CATHODES DEFAULT_SRM_LEDS_DOUT how does it behave when you are swapping the SR numbers in your setup_*.asm file? and last question: according to which schematic did you connect the LED matrix? Best Regards, Thorsten.

Schoen zu sehen, wie Du voran kommst. :) Die Assembler Befehle findest Du im Datasheet unter http://www.microchip.com/stellent/idcplg?IdcService=SS_GET_PAGE&nodeId=1335&dDocName=en010296 und die haeufig verwendeten Befehlskombinationen wie IFCLR/IFSET sind im macros.h File gesammelt. Mit: movlw 0x3c IFSET MIOS_PARAMETER2, 7, movlw 0x3d call MIOS_MIDI_TxBufferPut [/code] erreicht man folgendes: zunaechst wird der Wert 0x3c in das Arbeitsregister (W) geschrieben. Wenn in der Variablen MIOS_PARAMETER2 bit #7 gesetzt ist, dann wird der Wert mit 0x3d ueberschrieben. MIOS_MIDI_TxBufferPut sendet dann anschliessend den aktuellen Wert. MIOS_PARAMETER2,7 ist bei einer Linksdrehung gesetzt (der "incrementer" ist in diesem Fall negativ, also bspw. 0xff. Bei einer Rechtdrehung ist er positiv, also bspw. 0x01 - Stichwort "signed values") Das deutet darauf hin, dass mit dem DIN Modul etwas nicht stimmt. Werden die Werte auch dann gesendet, wenn der Encoder nicht angeschlossen ist? Dann ueberpruefe mal die Pull-Up Widerstaende an den digitalen Eingaengen. Gruss, Thorsten.

Unfortunately MIOS cannot be cloned (I hope that v1.9f was the last release with dedicated changes for MBSID V2) So, you need to upload MIOS to each single core, thereafter change the ID if this hasn't been done yet (it's a static change which won't be overwritten by new MIOS releases), thereafter upload the application. For future application updates you can use the cloning function. Best Regards, Thorsten.

such a button function is not available by default, but could be added. Anyhow, I think it's worth to spend the money for the additional buttons, as you wouldn't be able anymore to select multiple tracks at once. This especially saves time when changing configurations like MIDI channel, MIDI port, track modes/directions/etc... on the selected tracks at once. (*) Best Regards, Thorsten. (*) just remember that this is not completely true - it is also possible to select multiple tracks with the GP buttons while MUTE is pressed. However, it's your decition. I can only say: than more dedicated buttons available, than better the workflow.

Thanks! Great to see the first working MB-6582 from this batch run :) It looks like the "OSC Ctrl" button is permanently active (-> permanent connection to ground). When I press it during power-on, I get the same screen. For cloning it's sufficient to press Enter (in the documentation called: MENU) w/o the shift button during startup. All special button combinations are listed at the bottom of this page: http://www.ucapps.de/midibox_sid_manual_fp.html Best Regards, Thorsten.