TK.

I will ship already paid GM5 orders probably this Thursday. Next shipping day would be friday next week. The ordering procedure is described in the Wiki: http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder Best Regards, Thorsten.

Gridracer: your idea isn't lost - I like it and will see what I can do. Echopraxia: the recommended method is to store the complete track from which the drum map should be exported into a preset (MENU->EVENT->PRESET->SAVE AS NEW PRESET) Now you can import the drum map into another track with the PRESET function as well. Note that you will be asked for several import options, e.g. you can exclude the pattern import (Steps: no), etc. This function not only works for importing/exporting drum maps, but for anything related to a track. It's the most powerful copy function (especially since you are able to edit preset files with a text editor) - you will like it! :) Best Regards, Thorsten.

Thanks for joining the order! :) PMs with order details are sent. Attention Ankage: I can't determine your forum name Attention JuliaDee: I can't determine your forum name Attention Kabbi: I can't determine your forum name Attention Chrisbob12: your email address (...@lineone.net) is invalid, therefore the PM wasn't forwarded to your email account. Attention Bastard3b: your email address (...@freenet.de) is invalid, therefore the PM wasn't forwarded to your email account. Attention Zenguru: your email address (...@evtek.fi) is invalid, therefore the PM wasn't forwarded to your email account. Best Regards, Thorsten.

Hi Martin, ok from my side, especially if you sell the sammichSID to a forum member. :) Best Regards, Thorsten.

habe ihn via PM verpetzt ;) Best Regards, Thorsten.

svn is working again :) Best Regards, Thorsten.

Thats really a FAQ and I can only say: don't trust on "max allowed" values... Connections between the BLM_SCALAR modules (especially SCLK and RCLK) should be as short as possible! Try your best! Optimize it to the minimum cable length! Too long clock lines will result into flickering LEDs and unstable button states. The prototype will show the robustness in reality. Take the cable lengths of my prototype as example - it still works very stable. The cable/track length between BLM_SCALAR and LEDs/Buttons doesn't really matter. Best Regards, Thorsten.

In some modes MBSEQ rotates the screen by 90°, e.g. when velocity/length/probability/... or mixer parameters are edited. Therefore 16x16 (+ the extra buttons of course) is a must, supporting reduced BLM16x16+X layouts would result into a nightmare at my side! Best Regards, Thorsten.

wow! Best Regards, Thorsten.

This can be decided layout-driven (there are multiple possibilities) - for extra buttons it's only important that each button/LED combination is individually accessible in the matrix. (I will check your layout once it's finished) Best Regards, Thorsten.

Looks good so far! The 8x8 based variant would look similar, but currently I don't have the time to draw the schematic. You would create a schematic anyhow, so let's save this effort - I will explain it instead. If LEDs/Buttons are numbered this way: EC1 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A11 A12 A13 A14 A15 A16 EC2 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 B12 B13 B14 B15 B16 EC3 C1 C2 C3 C4 C5 C6 C7 C8 C9 C10 C11 C12 C13 C14 C15 C16 EC4 D1 D2 D3 D4 D5 D6 D7 D8 D9 D10 D11 D12 D13 D14 D15 D16 EC5 E1 E2 E3 E4 E5 E6 E7 E8 E9 E10 E11 E12 E13 E14 E15 E16 EC6 F1 F2 F3 F4 F5 F6 F7 F8 F9 F10 F11 F12 F13 F14 F15 F16 EC7 G1 G2 G3 G4 G5 G6 G7 G8 G9 G10 G11 G12 G13 G14 G15 G16 EC8 H1 H2 H3 H4 H5 H6 H7 H8 H9 H10 H11 H12 H13 H14 H15 H16 EC9 I1 I2 I3 I4 I5 I6 I7 I8 I9 I10 I11 I12 I13 I14 I15 I16 EC10 J1 J2 J3 J4 J5 J6 J7 J8 J9 J10 J11 J12 J13 J14 J15 J16 EK11 K1 K2 K3 K4 K5 K6 K7 K8 K9 K10 K11 K12 K13 K14 K15 K16 EC12 L1 L2 L3 L4 L5 L6 L7 L8 L9 L10 L11 L12 L13 L14 L15 L16 EC13 M1 M2 M3 M4 M5 M6 M7 M8 M9 M10 M11 M12 M13 M14 M15 M16 EC14 N1 N2 N3 N4 N5 N6 N7 N8 N9 N10 N11 N12 N13 N14 N15 N16 EC15 O1 O2 O3 O4 O5 O6 O7 O8 O9 O10 O11 O12 O13 O14 O15 O16 EC16 P1 P2 P3 P4 P5 P6 P7 P8 P9 P10 P11 P12 P13 P14 P15 P16 EC17 X1 X2 X3 X4 X5 X6 X7 X8 X9 X10 X11 X12 X13 X14 X15 X16 we would: connect BLM_SCALAR::J3_1:C0..C7 with the cathodes of EC1+A1..A8, EC2+B1..B8, ... EC8+H1..H8 connect BLM_SCALAR::J3_1:G0..G7 with the green anodes of A1..H1, A2..H2, ... A8..H8 connect BLM_SCALAR::J4_1:R0..R7 with the red anodes of A1..H1, A2..H2, ... A8..H8 connect BLM_SCALAR::J4_1:I0..I7 with the buttons of A1..H1, A2..H2, ... A8..H8 connect the green anodes of EC1..EC8 with BLM_SCALAR::J3_5:G0 connect the red anodes of EC1..EC8 with BLM_SCALAR::J4_5:R0 connect the buttons of EC1..EC8 with BLM_SCALAR::J4_5:I0 Do you see the logic behind this matrix routing, or do you need additional explanations? Best Regards, Thorsten.

Good news: I will get a batch of 250 GM5 chips from Ploytec very soon! If you are interested, please add your name and the quantity to this list: -> http://www.midibox.org/dokuwiki/doku.php?id=tk_gm5_bulkorder Best Regards, Thorsten.

Hi, thats easy, as encoder pinnings are defined in a table: From http://www.ucapps.de/mios_c_send_enc_abs7.html MIOS_ENC_TABLE { // sr pin mode MIOS_ENC_ENTRY( 1, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 1 MIOS_ENC_ENTRY( 1, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 2 MIOS_ENC_ENTRY( 1, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 3 MIOS_ENC_ENTRY( 1, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 4 MIOS_ENC_ENTRY( 2, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 5 MIOS_ENC_ENTRY( 2, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 6 MIOS_ENC_ENTRY( 2, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 7 MIOS_ENC_ENTRY( 2, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 8 MIOS_ENC_EOT }; [/code] your table (that you unfortunately forgot to post here - it would simplify things) has probably following entries: [code] MIOS_ENC_TABLE { // sr pin mode MIOS_ENC_ENTRY( 5, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 1 MIOS_ENC_ENTRY( 5, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 2 MIOS_ENC_ENTRY( 5, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 3 MIOS_ENC_ENTRY( 5, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 4 MIOS_ENC_ENTRY( 6, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 5 MIOS_ENC_ENTRY( 6, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 6 MIOS_ENC_ENTRY( 6, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 7 MIOS_ENC_ENTRY( 6, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 8 MIOS_ENC_ENTRY( 7, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 9 MIOS_ENC_ENTRY( 7, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 10 MIOS_ENC_ENTRY( 7, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 11 MIOS_ENC_ENTRY( 7, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 12 MIOS_ENC_EOT }; You want to map 1->1 2->2 5->3 6->4 9->5 10->6 3->7 4->8 7->9 8->10 11->11 12->12 Accordingly you have to swap some table entries: MIOS_ENC_TABLE { // sr pin mode MIOS_ENC_ENTRY( 5, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 1 MIOS_ENC_ENTRY( 5, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 2 MIOS_ENC_ENTRY( 6, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 5 -> now 3 MIOS_ENC_ENTRY( 6, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 6 -> now 4 MIOS_ENC_ENTRY( 7, 0, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 9 -> now 5 MIOS_ENC_ENTRY( 7, 2, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 10 -> now 6 MIOS_ENC_ENTRY( 5, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 3 -> now 7 MIOS_ENC_ENTRY( 5, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 4 -> now 8 MIOS_ENC_ENTRY( 6, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 7 -> now 9 MIOS_ENC_ENTRY( 6, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 8 -> now 10 MIOS_ENC_ENTRY( 7, 4, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 11 MIOS_ENC_ENTRY( 7, 6, MIOS_ENC_MODE_NON_DETENTED), // V-Pot 12 MIOS_ENC_EOT }; [/code] hope this makes sense Best Regards, Thorsten.

No his isn't possible, and as mentioned earlier, it's easier and faster (performance wise) to change this on your hardware. Best Regards, Thorsten.

Hallo, das ist eine relativ einfache Programmieraufgabe. Hier die Funktion, mit der Du 9 frei konfigurierbare CCs versenden kannst: #define NUM_CC 9 unsigned char ccNumber[NUM_CC]; unsigned short ccStates; void sendCCs(unsigned short flags) { unsigned char i; for(i=0; i<NUM_CC; ++i) { unsigned onOff = ccStates & (1 << i); // send CCs MIOS_MIDI_TxBufferPut(0xb0); // CC at MIDI Channel #1 MIOS_MIDI_TxBufferPut(ccNumber[i]); MIOS_MIDI_TxBufferPut(onOff ? 127 : 0); // set LED as well MIOS_DOUT_PinSet(i, onOff ? 1 : 0); } } [/code] ccNumber ist ein Array, in dem Du die entspr. Werte ablegst. Entweder statisch gesetzt (in Init()...), oder aus einem EEPROM geladen (-> MIOS_EEPROM_* funktionen) ccStates ist ein 16 bit Wert, der den Toggle-Status der 9 Taster enthaelt. Die Bits lassen sich mit (1 << i) addressieren. Wenn Du nun (bspw. aus dem DIN_NotifyToggle Hook) ein bit setzen willst, schreibst Du "ccStates |= (1 << pin)", und zum Loeschen schreibst Du "ccStates &= ~(1 << pin);" Mehr Programmierdetails unter: http://www.ucapps.de/mios8_c.html Gruss, Thorsten.

It's easier and faster (performance wise) to change this on your hardware. Best Regards, Thorsten.

Ich habe gerade auf Deine Mail von heute Nachmittag geantwortet, und einen Link zum Source Code geschickt. Er ist eine nette Abschreckung auf das, was auf Dich zukommen wuerde und erfordert hoffentlich keine weiteren Kommentare meinerseits. Nicht ohne Grund habe ich den Source Code (von 2001) niemals offiziell veroeffentlicht - der Supportaufwand waere einfach zu gross. Die meisten Firmwares, die Du ausprobiert hast, erfordern uebrigens einen PIC16F877, der PIC16F874 hat nur halb soviel Speicher. Das Programm wird also ziemlich schnell abstuerzen, oder sich "seltsam" verhalten... Gruss, Thorsten.

A possible reason why the upload is not working properly is, that the application that you downloaded before crashes the PIC, and that your computer is not fast enough to handle the upload request when the PIC is restarted. Therefore I added a new mechanism to MIOS Studio 2.1 which can handle this situation properly. 1) download MIOS Studio 2.1 (-> http://www.ucapps.de/mios_studio.html) 2) select MIDI ports and device ID as before 3) power-off your MB6582 4) press the start button. MIOS Studio won't find the MIDIbox, but it will go into a new mode which waits for an upload request 5) once you see the appr. message ("Waiting for upload request..."), power-on your MB6582 6) the download should start now - if not, it would be interesting to know if a SysEx message is received by the MIDI IN monitor (if yes: which one?) Best Regards, Thorsten.

Wrong - you read the MBSID V1 FAQ, and you are mixing MBSID V1 features that have been developed 6 years ago with MBSID V2 features that are the current state. Meanwhile I spent a lot of sparetime to improve *a lot of* things. However, you are free to read the MBSID V2 manual on my webpage and to write a new Wiki page based on what you learnt, because it seems that nobody felt triggered to do this so far (probably because most people are aware about the V2 users manual) [text macro]Thats poor community effort btw. - if you don't like this, go away and search for another project! If you see the problem and want to help, feel welcomed to improve the wiki![text macro] Best Regards, Thorsten.

No, as Seppoman already mentioned, you can control each voice separately in Multi and Drum mode. Did you already read the user manual where such details are described? interesting pages that answer your questions: -> http://www.ucapps.de/midibox_sid_manual_hw.html -> http://www.ucapps.de/midibox_sid_manual_m.html -> http://www.ucapps.de/midibox_sid_manual_d.html E.g. with the multi engine you could assign each instrument to a different voice. Best Regards, Thorsten.

Can you confirm that one LCD works at J15A and J15B, and that it outputs different screens? (left/right side of the MBSEQ screen) In this case the hardware (core) is working correctly, and the application is properly installed as well. Initialisation is done here: http://svnmios.midibox.org/filedetails.php?repname=svn.mios32&path=%2Ftrunk%2Fmodules%2Fapp_lcd%2Fclcd%2Fapp_lcd.c Only the MBSEQ application will initialize mios32_lcd_device == 1 (all others only mios32_lcd_device == 0). As you can see in the source code, each device has a dedicated timeout flag - if MIOS32 doesn't get a response from a display after 2500 (!) tries, it won't be accessed anymore. The same mechanism have been used by the PIC based MBSEQ V2 and V3 firmwares since years, this is well tested code. Best Regards, Thorsten.

Thanks for the input! :) I just came back home and won't have the time today to check firmware changes by myself. However, I think that I know from where the delay is coming from: MIDI clock start was sent directly after the MIDI clock event, but it should be sent before. Could you please try following temporary release if it works at your side? If it still doesn't work, I will test this with various sequencers at my side... later. Track transpose page now always starts with semitone selection. Due to conceptional reasons it isn't possible to store the last setting, nor to make it configurable in a config file. The issues reported by Gridracer are not fixed yet. -> http://www.ucapps.de/mios32/midibox_seq_v4_0beta23_pre1.zip There are some preparations for OSC which hopefully won't conflict with existing functions. They are currently only working on an iPad, MBHP_ETH support will be added this weekend. Best Regards, Thorsten.

For the case that an incomplete app upload prevents further uploads (e.g. since the application crashes during runtime): could you please try to upload the application via 1st level bootloader? Just start the upload within 3 seconds after power-on. Best Regards, Thorsten.