TK.

:)

I would also like to have an upload area so that users can distribute their creations without my help and without an own homepage. But I neither have the experience how to realize such a web based system, nor a free server, nor I want to account for the risk that somebody uploads illegal stuff. It's difficult, but if somebody wants to take care about such a server, please step forward! :) Best Regards, Thorsten.

I would also like to have an upload area so that users can distribute their creations without my help and without an own homepage. But I neither have the experience how to realize such a web based system, nor a free server, nor I want to account for the risk that somebody uploads illegal stuff. It's difficult, but if somebody wants to take care about such a server, please step forward! :) Best Regards, Thorsten.

Btw.: the panel for the SID control surface I made some weeks ago has to be overworked, as the LCD/6-buttons/rotary encoder section at the upper left corner doesn't fit with the components I plan to use. The LCD is bigger than expected so that the buttons have to be placed farther apart from the display. Thats a principle problem - if you don't use the same components like me, you need a different panel layout. However, if you plan to make only a minimal control surface, I would recomment a 40x2 LCD with 11 buttons and rotary encoder. If this is too expensive for you, just take the 20x2 LCD Best Regards, Thorsten.

I cannot recomment 100k pots because of the high impedance, the current drain will be so low that external noise can influence the measuring results too much. The result: jittering pot values. So, best values are around 1k and 10k. Best Regards, Thorsten.

Yes, with a relay this should make fun - an additional driver is absolutely required. Either a transistor, or a ULN2803 like shown here: http://www.ucapps.de/midio128/relay_example.pdf (this example has been made for MIDIO128, but works also great with every MIOS based application) Best Regards, Thorsten.

Hi Steve, great to hear that you finally made it! :) The touch sensors are controlled by the application like common buttons. You just only have to assign the ID_FADER_TOUCH_CHNx events to the appr. input pins in lc_io_table.inc Best Regards, Thorsten.

Hi, you could control the CC parameters directly via pots in the following way: in sid_ain.inc you can insert a routine which branches to several routines depending on the moved pot. The routines have to forward the pot value to the CC handler by calling the SID_CCIN_Set routine. A simple example for one pot only: USER_AIN_NotifyChange ;; get 7-bit value of pot #0 movlw 0x00 call MIOS_AIN_Pin7bitGet ;; forward value to the CC handler ;; it expects: CC parameter number in WREG ;; CC parameter value in MIOS_PARAMETER1, so: movwf MIOS_PARAMETER1 ; save 7-bit value in MIOS_PARAMETER1 movlw 0x10 ; control CC #10h == Transpose V1/V2/V3 call SID_CCIN_Set ; call function return ; and exit AIN handler there are three examples in the download section which describe how more pots can be handled. And maybe one of the next SID firmware release will provide another example... Best Regards, Thorsten.

Hi Dan, yes, the A/K pins are not necessary to control the LCD. Hm.... you wrote: does this mean that the core is running with the same LCD type for both displays? This will not work, you have either to change the type setting in the ID field during burning the first-level bootstrap loader, or you have to add a MIOS_LCD_TypeSet function call to the LC_Init hook of the application. Best Regards, Thorsten.

Hi, currently I'm porting the MB64seq step by step to MIOS. It's not very difficult and it doesn't consume that much effort, but currently I haven't so much time for MIOS, therefore the final sequencer release can take some weeks. The menu interface is already running - the look&feel is 100% compatible to the PIC16F version, but the implementation is totally different - a more modular way which allows to add submenues (also hierachically) very easily. The menu can now optionally controlled by a data wheel (==rotary encoder) and via MIDI for a remote link. And it will be reused for the MIOS based MIDIbox64 and MIDIbox16E. The button handler now also supports control via MIDI, so that all functions are also controllable from another MIDIbox or from a computer based sequencer. The next step will be the sequencer engine, it will also redesigned on a modular way, so that multiple instances can run in parallel. Only the memory and the user interface will limit the number of tracks. Triggering patterns via buttons or program change messages is already possible with the PIC16F application, sure it will also work with the reimplementation. Programming MIOS applications: the example applications in the download section describe how to handle with the MIOS hooks. You will get a better understanding once you modified and tried it with a real existing box. Programming teams: maybe we should try this once all PIC16F applications have been ported, because they should provide a good fundament for improvements and customizations. Sampler or soundfonts: requires a lot of memory and a large data store device. I would prefer an old PC or homecomputer for this job, a PIC based (multichip) solution would be more expensive Best Regards, Thorsten.

Hi Dan, ok, with a PIC16F core you have to connect the LED rings to port J7, it should work w/o problems Best Regards, Thorsten.

It is similar to the display I got from Christian some time ago (DMF6104). I haven't found the time to write a driver yet, but it will be supported. I'm unsure about the performance, maybe it will be slower than the KS0108 type GLCD Best Regards, Thorsten.

Just a note: in a few days Tim aka SmashTV will offer premade PCBs, Kits and a PIC burning service in the US - more infos soon :) Best Regards, Thorsten.

Hi Gilles, MIDIbox16E only supports undetented encoders, MIOS supports detented and undetented types. Just show me a datasheet and the exact part number before you make the order Best Regards, Thorsten.

Hi, all DIN and DOUT connections are free configurable. In this way you can decide by yourself, if you want to have a full setup or a downstripped version with less buttons & LEDs. The configuration has to be done in main.asm (general settings), mios_tables.inc (encoder settings) and lc_io_table.inc (button & LED settings) Best Regards, Thorsten.

Hi Dan, the initialization is exactly the same - the display will be turned on with the "0x3f" command, thereafter you should see the pixels. Also the bus interface is exactly the same. Are you able to control the contrast? Do you see gray pixels? If not, the Vee->V0 connection via the pot has not been setuped correctly. You could also measure Vee against ground, should be ca. -10V. The level at V0 should be between -8V and -10V Another possible reason could be the reset line (remember the HD64240 problem?). The reset input should be tied to +5V. If this doesn't work, try ground (the datasheet doesn't make clear if the reset is inverted or not) Best Regards, Thorsten.

yes, the application registers all incoming LED status messages so that they are also saved during the alternative layer is active :) Best Regards, Thorsten.

Hi Dan, in this case the best solution is to set the BPM to "MIDI slave", so that the box synchronizes to the MIDI clock and starts/stops with the appr. controll messages which are sent by Logic. If the box doesn't receive the clock, you possibly have to enable this under Options->Settings->Synchronisation Settings Best Regards, Thorsten.

Hallo Johannes, ja, Du bist kurz davor :) Nun hilft es nur noch, die 5V Versorgungsleitung nachzuverfolgen. Irgendwo ist die Verbindung zum 7805 unterbrochen. Gruss, Thorsten.

Yes, the power supply doesn't deliver enough current. If possible just fade down the backlight Best Regards, Thorsten.

Hi Dan, not this isn't correct. The shift registers have to be defined in the main.asm file: ;; used by lc_ledrings.inc LEDRINGS_SR_CATHODES EQU 8 ; shift register with cathodes of the 8 LED rings LEDRINGS_SR_ANODES_1 EQU 10 ; first shift register with anodes of the 8 LED rings LEDRINGS_SR_ANODES_2 EQU 11 ; second shift register with anodes of the 8 LED rings note that here the shift registers are counted from 0. This means: number 8 is the 9th shift register in the chain Best Regards, Thorsten.

I didn't create my schematics with eagle, so they will not help :-/ However, the modules are so compact that you can just join them together - it will save a lot of effort! Best Regards, Thorsten.

In some menues the snapshot button is also used for other functions. But it's ok, you can use the "snapshot" function for restore and another for store, or you can hold the snapshot button 3 seconds in order to store the bank - the function itself is defined via "Special Function Button" event (some kind of meta event, see the appr. list for available functions) Best Regards, Thorsten.

I would prefer the EC24E, it costs the same but sends 24 pulses/rotation. In the catalouge it isn't clear if this is really a detented or non-detent type - however, if it is detented it will only work with MIOS Best Regards, Thorsten.

It will also work well with PIC16F877 :) Best Regards, Thorsten.