TK.

Du verwechselst IIC mit USB. Ausserdem gibt es fuer solche Experimente keine Firmware... Am besten kaufst Du Dir ein fertiges USB MIDI Interface fuer 20 Euronen oder so... das kommt guenstiger. Gruss, Thorsten.

Die gibts bei Conrad, siehe http://www.midibox.org/forum/index.php?topic=7354.msg50585#msg50585 Gruss, Thorsten.

You have to upload the main.hex file of the MIDIO128 package - with MIOS Studio Best Regards, Thorsten.

A feature wish by myself: 10) it should be possible to use the ALL button on the mixer map :) Best Regards, Thorsten.

Hi Dietmar, I'm not completely sure, but it could be that you forgot to change the emulation mode to "Mackie Control XT" for the second and third core (LC_EMULATION_ID should be set to 0x15) - if Nuendo can only handle one master unit, this would be the solution If this isn't the solution, I have no other idea... Best Regards, Thorsten.

Alright, the mixer map is implemented now after a rapid prototyping session :) The concept has been slightly changed, as always during the implementation phase... Some comments to John's posting: no, it works independent. It's like a MIDI controller extension. I understand this wish, but as mentioned before, this is unfortunately not possible. Ok, I will get rid of the idea to share the Song BankStick, and only provide an option to use an additional BankStick for Mixer Maps. The implementation will be simpler, and I don't need to take so many corner cases into account (e.g. somebody doesn't read the documentation, and uses a 32k BankStick instead of 64k) The "---" is for the case that you won't send a controller, e.g. MIDIbox SID doesn't understand the pan controller, instead it will trigger "Voice 3 Play Note" - this is not what somebody wants, therefore all controllers are disabled by default. Ok, I got rid of this idea - disadvantage is now, that only two freely assignable CC's are available anymore, but the argument for a cleaner work flow is stronger. As mentioned above: I understand, but this is not possible (see also FAQMARKER) "Note CC CC" is available since a long time (see changelog) I could add an option which ensures that only notes are changed As mentioned in a previous posting, drum mode is prepared, but not completely working yet. Just follow the notes in the ChangeLog, sooner or later it will either be available, or it will be removed. The mode which is prepared is "Vel Vel Vel" (notes are fixed). The problem is, that currently the LEDs don't reflect the gate, and that the trigger buttons don't clear/set the gate. You only can control if a drum is played or not by changing the velocity. My plan is to enhance the editor, so that the velocity (accordingly the gates for all three layers) can be controlled in a special way when the "Vel Vel Vel" mode is selected so that it behaves like a TRx0x, each track can play 3 drum lines... Best Regards, Thorsten.

Most of the mixer map is implemented now (this is a 4-hour hack, not sure if the rest is still working) SAVE/LOAD/Change Map not functional yet! From the ChangeLog: o a mixer map has been implemented It can be accessed by pressing MENU+VIEW, or by going into the UTILITY menu and pressing the button below "Mix." NOTE: if you are planning a new frontpanel, the "View" label below GP button #1 could be renamed to "Mixer" There are 7 pages, which can be selected with the datawheel, or alternatively with the Rew/Fwd buttons when no song is playing: MIDI Port, MIDI Channel, Prog.Change, Volume, Panorama, CC1-2 Values can be changed with the GP encoders The ALL and FAST button taking effect as well. The ALL button provides two functions: - when LED active, only values which are not enabled will be changed - when button pressed, all values will be changed to the same value They are sent directly over the selected MIDI port - all ports are selectable, even Loopback and AOUT! When the SELECT button is pressed, a utility page will be displayed which allows to - change and load a mixer map (one of 127) - to Copy/Paste the map - to clear the map - to reload the map from BankStick - to save the map into BankStick - to dump the complete map via the MIDI/AOUT/Loopback ports - to change the assignments for CC1 - to change the assignments for CC2 Since the ports and channels are freely assignable and working totally independent from the running patterns, the mixer map function behaves like a MIDI controller - you can define up to 127 maps which can be stored, restore, dumped and controlled in realtime! [/code] Mixer page #4 (Volume): Mixer Utility Page:

So etwas kann man doch immer mal gebrauchen - ich nehme 3 Platinen :) Gruss, Thorsten.

Also mit der MIDIbox SID Step C hast Du ja eigentlich schon ein ziemlich aufwaendiges Projekt auf die Beine gebracht, der Aufbau einer MBSEQ ist nicht wesentlich schwieriger, und Du kannst natuerlich jederzeit hier im Forum nachfragen, wenn Du irgendwo haengenbleibst. Im Notfall kannst Du mich auch telefonisch erreichen (so lassen sich manche Sachen schneller bereden). Nochmal zum Thema Button/Duo-LED Matrix: hier habe ich ein paar Bilder abgelegt - natuerlich laesst sich das auf Lochraster aufbauen, doch das Faedeln der ganzen Verbindungen ist wirklich nicht ohne: http://www.midibox.org/midibox_seq_blm_ext Zur Frage mit den Program und Bank Changes: in der V3 wird es demnaechst eine Mixer Map geben, in der man u.A auch die Program Changes festlegen kann :) Die Diskussion laeuft gerade im englischen Teil des Forums. Gruss, Thorsten.

The C examples provide some additional infos, how to configure encoders: http://www.ucapps.de/mios_c.html Best Regards, Thorsten.

I'm using Displaytech Displays in nearly all of my MIDIboxes The minimum cycle time of the enable line is 500 nS, so the timings used by MIOS are not the real issue here. Adding a delay of 1 mS will have the unacceptable side effect, that the whole system will run so slow that data loss at the MIDI input can happen (as you already noticed). I cannot add more than already written by SmashTV and AC Best Regards, Thorsten.

I think that it shouldn't be a big problem to select and "dump" a mixer map also in pattern mode. Yes, I know that there are advantages and disadvantages of an independent system. The main advantage is, that I don't need to touch the SysEx structure of patterns, this is important because there or only a few bytes free anymore. To say it more dramatically (because I think that I cannot mention it often enough): currently we can store 128 patterns in a 64k BankStick. The data is already compressed. If more informations should be stored in a pattern, I would have to limit the number of storable patterns per BankStick again, and this is what most of you wouldn't like to see, and what I want to prevent. FAQMARKER Seperate BankStick: not required, when you imagine how difficult it will be to maintain a huge set of parameters. I don't know where to find the manuals of Kurzweil synths, but I think that you have to make a difference between internally controlled parameters of a synthesizer, which can be changed very fast, and external MIDI parameters, where the transfer speed is limited by the MIDI bandwidth. Example: let's say you want to control 7 CC's plus Program Change of 16 channels. A dump would cause a delay of ca. 8*16*1 mS = 128 mS over a single MIDI out (it's more relaxed when multiple MIDI outs are used), and this would be definitely too much, the realtime capabilities would be affected. I also don't really want to spend too much time in implementing a complex mixer function which propably would consume more code memory than it's really worth. So, let's reduce it to the real needs, and then let's continue with the next feature... What I can extract from your postings, and what I can say from my experience, is the following: 1) at least Port, MIDI channel, Program Change, Volume, Pan, 4 free definable CCs 2) the 4 CCs should be assignable for each track seperately, e.g. to 16, 17, 18, 19 (general purpose CC's) or for example to Bank/Reverb/Chorus/Fx2 3) it must be possible to select, if a parameter should be sent or not to save MIDI bandwidth. Therefore a parameter won't be sent by default (---), and has to be enabled by setting the value: 0-127, 7bit 4) Using the upper half of the Song BankStick means 32k are available. Considered that for each mixer map 256 bytes are reserved, we would get 128 mixer maps 5) parameters will be stored automatically into the appr. BankStick slot whenever the page is changed (no special save button) 6) it should be possible to copy a mixer map to another slot (copy/paste) 7) it should be possible to clear a mixer map (clr) 8 ) it should be possible to "dump" a mixer map whenever you want 9) it should be possible to "dump" a mixer map as song list entry I think that this is all I can offer ;-) Dave: I can understand the need for such a performance controller page, but I fear that I could not offer the full flexibility, especially for controlling the note length of different tracks at the same time, this is really hard to edit (I guess you would also like to see the parameter names and not only numbers) and therefore very memory consuming. It would be much easier to create a seperate control box for such a functionality On the other hand: you could use one or two... or all 4 CC's of a mixer map and assign them to CC's you want. In addition, I could provide the "loopback" port as additional interface, which allows to control sequencer parameters from the mixer map. Best Regards, Thorsten.

I finally got an idea, how to realize program changes (and more) without modifications in the existing SysEx structures (which is nearly impossible): by providing mixer maps. A mixer map could contain the MIDI channel and port, program change, the two bank change CCs + volume + 3 additional CC's for each track. It would be stored in a seperate location (e.g. upper half of the Song BankStick, accordingly you would need a 64k BankStick instead of 32k), and it would be referenced in the song list. The advantage of this approach is, that you can prepare several mixer maps for your instruments, and reference them multiple times within the song menu w/o the need for an additional copy&paste mechanism for the case that you want to make small adjustments. Any other ideas, what could be part of such a mixer map? Best Regards, Thorsten.

Hi Robin, yes, you have to take care, that no recursion happens. If this is the case, the clrwdt won't help, instead the application will freeze, so that you have to trigger a reset manually (power-off/on). In fact, one of the purposes of the watchdog timer is to terminate such programming errors gracefully with a reset, so that somebody is able to upload the corrected code w/o reseting the core manually. Back to the topic: recursion means, that the DIN_NotifyToggle calls itself several times. If there is no condition which terminates this process, then the stack will overflow sooner or later, the whole application will crash. So, all what you have to do is to ensure, that the button numbers which are forwarded to the DIN_NotifyToggle function will not execute the part of the code, which will call DIN_NotifyToggle again Best Regards, Thorsten.

Wow! Great case! Can I put this into the gallery? :) The second slave won't play so long the Link is disabled. You either have to add a DIN module in order to get access to the Link function, or you have to enable the Link by default in the *.asm file you are using Best Regards, Thorsten.

After his first MIDIbox SID Step-A (http://www.midibox.org/forum/index.php?topic=6264.0), Jack (aka. jackan) built this black-green beast! A really beautiful one! :)

MIOS ist nicht kompatibel zum PIC18F4550, weil sich die Speicherbereiche ueberlappen, internes USB ist somit nicht machbar, es sei denn, jemand schreibt sowohl MIOS, als auch die gewuenschte Applikation um. Ja, der PIC18F4620 hat im wesentlichen mehr Speicher, aber auch leider (genauso wie der PIC18F4550) mehr Bugs :-( Gruss, Thorsten.

Hallo Christian, die Button/Duo-LED Matrix ist ein rein optionales Feature, und auch nicht so ohne weiteres nachzubauen - ich habe drei Tage lang LEDs verklebt und "gefaedelt", bis die Matrix endlich komplett war. Eigentlich sollte man ein PCB hierfuer bereitstellen, doch das wird 1) nicht billig, und 2) kann ich das aus Zeitgruenden nicht selbst supporten. Somit bleibt dieses Feature etwas fuer Freaks, die schon alles gebaut haben, und nach neuen Herausforderungen suchen ;-) Die MBSEQ laesst sich auch prima ohne diese Matrix bedienen, darauf habe ich grossen Wert gelegt. Und wie doc bereits erwaehnte, benoetigt man hierfuer nur die MBSEQ V2 Hardware + PIC18F4620 + mindestens ein MBHP_IIC_MIDI Modul Gruss, Thorsten.

Hi Robin, the upload request (or reset) is caused by the watchdog timer. If a function takes more than 1 second, you have to insert __asm clrwdt __endasm; [/code] within the "big loop" (which sends a dump, or writes something into EEPROM) in order to ensure, that the watchdog timer won't overrun and accordingly trigger the reset Best Regards, Thorsten.

Hi Chris, this is a measuring error - some current drain should be caused by the 7805, if you measure 5V at J2, then the current should be >0mA Do you see the upload request from the PIC in the meantime? Best Regards, Thorsten.

Thank you both! :) Today I migrated a MIDIbox SEQ of a friend, he was speakless when I demonstrated all the new features, and the whole time I saw a big smile on his face! :) You mean for MBSEQ or in general? However, for both I can say, it's only a software, not a hardware problem. Even the limitation of 16 DIN/16 DOUT chain can be solved by adding a second chain to other free pins. But for MBSEQ I cannot recomment this, because this will affect the realtime capabilities. For a standalone matrix, I would assume that there is enough CPU free for 3 additional 16 DIN/16 DOUT chains when the guy who programs this has good assembly skills (you have to optimize the handlers like I did in the SRIO driver - unrolled code) Best Regards, Thorsten.

Hi, I cannot help you that much on the first three questions... maybe the "Parts Questions" section would be a better location for this. To 4) you need 3 DINX4 modules, and if you want to use MBSEQ V3 (you definitely want!), you will need a PIC18F4620 and a MBHP_IIC_MIDI module in addition. To 5) thanks! :) Best Regards, Thorsten.

Hi John, the logfile looks ok. It could be a problem with the MIDI clock (which is not listed in the logfile) There is a bug in the current build, the MIDI clock settings are overwritten once you leave the MIDI menu, accordingly the sequencer won't send MIDI clock to your K2000, and the synth will propably lock to the wrong clock. Here the bugfix: open seq_dump.inc, search for function "SEQ_DUMP_StoreGlobal", go to line 401, and replace: ;; ---[ store MIDI router settings ]--- call MIOS_EEPROM_Read movff WREG, SEQ_ROUTER_MCLK_ENABLED [/code] by: [code] ;; ---[ store MIDI router settings ]--- movff SEQ_ROUTER_MCLK_ENABLED, WREG call MIOS_EEPROM_Write does this help? Best Regards, Thorsten.

Hi John, there shouldn't be a problem with the LTC, you only have to take care that the MAX232 is *not* stuffed. But so far I remember, you had an issue with this module on your MBSEQ as well, so I don't know how to help you here, but to answer your other question: yep, it's documented in the main.asm (and setup_*.asm) file Keyword: LED Best Regards, Thorsten.

Message on the webpage: Sorry, there are currently no free download slots available on this server. Please try again later, or you can upgrade to FileFactory Premium for instant access. :-( Best Regards, Thorsten.