TK.

sweet! :) I will add a change into the next MBSID release, so that the edit LEDs goes automatically into "flash" mode once a CC is received via MIDI, so that it won't be required anymore to change a parameter manually before enjoying the animations (and the game) Best Regards, Thorsten.

We all remember the legendary "Der Brat 1000" (-> http://69.56.171.55/~midibox/forum/index.php?topic=3651.0) This is the small version "Der Brat. 50" - the ideal mobile solution for jamming together with friends ;-) Seppoman wrote:

This is the MIDIbox SID of Fabian - he built it into an old case of an "electrical thermometer". He wrote (in german - use http://babelfish.altavista.com for translation)

Hallo Frank, bei graphischen LCDs muessen die Y-Offsets anders eingestellt werden. Am besten machst Du die Aenderungen wieder rueckgaengig, und aenderst die Offsets in main.asm wie folgt: #if DEFAULT_LCD_SIZE == 3 ; 4x20 #define DEFAULT_YOFFSET_LINE0 0x02 #define DEFAULT_YOFFSET_LINE1 0x42 #define DEFAULT_YOFFSET_LINE2 0x82 #define DEFAULT_YOFFSET_LINE3 0xc2 #define CSMD_YOFFSET_LINE0 0x00 #define CSMD_YOFFSET_LINE1 0x40 #define CSMD_YOFFSET_LINE2 0x80 #define CSMD_YOFFSET_LINE3 0xc0 #endif [/code] danach werden die Menueseiten nach wie vor nur zentriert dargestellt. Lediglich innerhalb des Display-Menues wird der Bildbereich komplett ausgenutzt (vor allem auf Seite 3) Gruss, Thorsten.

all I can provide is this code: void ENC_NotifyChange(unsigned char encoder, char incrementer) __wparam { unsigned int value; // encoder number 0, 2, 4, 6, 8, 10, 12, 14: VPOT // encoder number 1, 3, 5, 7, 9, 11, 13, 15: Fader replacement if( encoder < 16 ) { if( !(encoder & 1) ) MM_VPOT_SendENCEvent(encoder >> 1, incrementer); else { // add incrementer to absolute value value = MM_MF_FaderPosGet(encoder >> 1); if( MIOS_HLP_16bitAddSaturate(incrementer, &value, 0x3ff) ) { // send fader event MM_MF_FaderEvent(encoder >> 1, value); } } } // encoder number 16: datawheel else if( encoder == 16 ) MM_VPOT_SendJogWheelEvent(incrementer); else { // here you could handle additional encoders } } [/code] Best Regards, Thorsten.

Hi Julian, how did you check if the CC are received by the MBSID? If you want to check the displayed value on the LCD, you have to enable edit mode, otherwise the control surface doesn't take these changes (this is for a non-destructive automation from a MIDI host) Best Regards, Thorsten.

with the SDCC based version it is possible, yes maybe this could work, but the additional ledring (or better: ledbar) handler has to be implemented by yourself. However, with the C version it isn't so difficult Best Regards, Thorsten.

Hi, vmidibox only uploads the configuration data, this has nothing to do with .hex files Did you upload the MIDIbox V2.4 application before? Best Regards, Thorsten.

Here some quick snapshots, how the MBLC emulation looks on the MIDIbox SEQ hardware. 8 encoders are used as "V-Pots", the remaining 8 encoders as Motorfader-replacement (mostly controls volume). The Jogwheel function is available (17th encoder), and there are 3 button layers to which the LC commands are assigned (of course, it is possible to add even more buttons (up to 128-2*17 = 94 button functions) and LEDs (up to 128), and to customize the button/LED in order to assign LC commands like desired - the MIDIbox LC application is really flexible :) And it provides a "general purpose" mode with 128 additional MIDI parameters Common view (the tracks are selected with the Bank +/- buttons) View of a VST plugIn: Editing VST parameters: The screens look a little bit scrambled. The reason is, that it has to be stretched from 2x55 to 2x80, so that the displayed parameter labels and values are exactly above the appr. V-Pots. There are 4 different display modes with alternative views, e.g. one where the 2x55 display is centered (no scrambling) Best Regards, Thorsten.

yes Best Regards, Thorsten.

For sound engine hacks the SE option already exists (it provides 7 flags, one is allocated for the TB303 option, the others are free yet) - see http://69.56.171.55/~midibox/forum/index.php?topic=4447.0 The MIDI Clock Out option uses an existing register which already stores the three sync flags for LFO/ENV/WT, 5 flags are free. As mentioned above, the option itself consumes 4 assembly instructions, thats ok for a general option. Best Regards, Thorsten.

Hi Julian, It's disabled when you are trying to "get" a bank within a bank window, because this is the context which only allows to request patches. Banks can only be requested from a library window. Great! I'm planning to publish a new library with a second preset bank once the TB303 option has been released :) Best Regards, Thorsten.

Ok, MIDI clock output can be enabled with Parameter #125 ("MIDI Sync"), bit 3 in the next release Best Regards, Thorsten.

Hi Rowan, thank you, I will check it this weekend :) Best Regards, Thorsten. P.S.: have a nice flight - if you are flying via Singapore, don't waste your time with the microKontrol, but enjoy the city instead! ;-)

Hi Luke, MB64E can "only" receive the parameters of the currently selected bank. Means: 128 encoder values and 64 button (LED) values. Each bank is divided into groups. With 32 rotaries you have four groups, which can be selected with "Special Function Buttons" (see sfb table) There are several "workarounds" which could be used: if your host application provides a function which sends the status of all control elements (faders/pots/buttons...) via MIDI, then just trigger this function and the Encoder positions/LEDs will be updated. This is how my MB64E interacts with Logic Audio, it has the big advantage that LEDs/Encoder positions will be updated even after I loaded a new song - for myself this is very important, therefore I never thought about the capability to store even more parameters in RAM, since this wouldn't really be a perfect solution you could enable the auto-snapshot function which stores and restores the whole "scene" when you are switching between different banks in the last time it very often turned out that people don't really need the high flexibility of MB64E, but just want to use their MIDIbox to interact with a host application. This means that normaly encoders only have to send 7-bit or 14-bit events, the buttons should send Note events. If the appr. CC#s and Notes are statically defined (e.g. Encoders always send/receive CC or NRPN, Buttons always send Note On/Off), an alternative application could be realized which only supports predefined events, but can handle with up to 640 encoder parameters and 1024 LED values at the same time! Whats the oppinion of the community, is there a need for such a "generic" controller (in my eyes it's a primitive application, but it seems that this is exactly the need for most of you?) Best Regards, Thorsten.

This doesn't answer the question: why do you need a MIDI clock output, what do you want to do with this clock exactly? Why do you think that a master clock, sent by the SID, is better than clocking the SID as slave? Best Regards, Thorsten.

You are writing this in a form where it could be assumed that you are an expert in this area - the YAC is not a common linear DAC, it's provides a 10-bit mantissa and 7-step exponent (best for high dynamics), the analog output range is 16-bit. Can you please determine the exact benefit with this type of DACs? what are the experimental results? Did you notice any disturbing parameters during your experiments which haven't been mentioned at the website from where you copied this text? Best Regards, Thorsten.

Hi Julian, please send me your patches, once they are well sorted :) this dummy device always exists due to conceptional reasons in JSynthLib - it doesn't affect the SID to the first SID, device ID 0, because only this SID has a BankStick You could also use device ID 1, but in this case it would only to possible to write into the EEPROM (single patch), and not to transfer a whole bank Another problem is, that JSynthLib doesn't really support the access to multiple devices from a single editor (yet), the current solution is a dirty workaround, and the use is complicated (conceptional problem, no way to improve this without changes in the core library) If you want to send a patch to the first SID slave (device ID 1): of course Open a new Library, then click on Patch->Get In this menu you are able to select the Bank. Very important: this is not supported in JSynthLib versions < 0.20 because at this time the multiple BankStick option was not supported by MIDIbox SID ;-) So, please use this version: http://69.56.171.55/~midibox/jsynthlib/JSynthLib-0.20.0_midibox_mod1.jar.zip Another tip: if you only want to rearrange the patches, it makes sense to use TL's Patch Manager instead - the handling is much more comfortable: http://www.automatic-brain.de/midibox/ Best Regards, Thorsten.

Hallo, ich wuerde vier Stueck mitbestellen :) Gruss, Thorsten.

Hi Rowan, just a quick question: I noticed that the Reason3 demo supports the KMK, do you know if all features of the protocol are supported, or if anything is missing? Is any other demo software available in the net which supports the Korg protocol, so that I can double-check the implementation? Best Regards, Thorsten.

Yes, they are always used. The reason is, that this allows to switch very fast between different views. E.g, with a single encoder you are still able to access (receive and send) up to 128 parameters, isn't this a great possibility? :) This was a request by some users, it was hard work to realize this, and now its unfortunately very difficult to remove this feature (due to heavy code optimizations) If you only need such primitive controller features, I would suggest to program something based on the C wrapper instead. Just wait some weeks/months until all examples are available, it will be much easier to combine the C modules to the controller of your dreams than trying to modify such a complex application like MB64E Best Regards, Thorsten.

You can't, because you haven't built a MIDIbox SID yet, and therefore don't know about the possibilities ;-) Be honest: are you writing these postings as a provocation? Thats my impression, because your ideas are mostly far from real requirements, and on queries about your crude statements you never give an answer (this happend several times in the past) Hint: add "movlw 0xf8" and "call MIOS_MIDI_TxBufferPut" after the SID_WT_Branch_Play_TB303 label and you will get a MIDI clock... Most people prefer MIDI slave capabilities, since this simplifes the synchronization with PC based sequencers, where the MIDI In has mostly an higher jitter than the MIDI Out (especially when USB based interfaces are used), and where the automatic latency compansation with the Audio record function only works correctly when the host sends the clock If any MIDIbox user would give me the request, that he needs a MIDI clock output for a certain application, and if he would really use it, I would build this into the firmware. But I don't do this for boys who think that they have found a virtually important function which must be implemented before he starts to get his own experiences with the endless features which are already available (and which are for 33% not used by anybody but myself...) Best Regards, Thorsten.

This is really a multi-purpose box! :-) Matteo wrote:

Have you already built your MIDIbox FM? Mix all 4 outputs together, play the same sound, do you hear the difference? ;-) Best Regards, Thorsten.

Yes, in this case you are allowed to left out the SID select buttons Best Regards, Thorsten.