TK.

You must hear the SID through the "Grainstates FX", recorded and granulated in realtime, parameter controlled by a MB64seq - it rocks! :) Best Regards, Thorsten.

You must hear the SID through the "Grainstates FX", recorded and granulated in realtime, parameter controlled by a MB64seq - it rocks! :) Best Regards, Thorsten.

Hm, in this case I'm very unsure what is causing the trouble. Maybe the LCD needs some additional time until it is ready for receiving a command. Maybe you should try a second initialization in the init hook (e.g lc_init.inc): USER_Init movlw 200 ; wait for 200 ms call MIOS_Delay movlw 0x3e + 1 ; Display On command call MIOS_LCD_Cmd Best Regards, Thorsten.

...Reaktor 4 has been released! :)

...Reaktor 4 has been released! :)

yep Best Regards, Thorsten.

Hi, In the meantime I tried it with different browsers and operating systems, but I cannot reproduce these problems. Ok - you are not able to jump to an URL directly (e.g http://www.ucapps.de/mbhp.html), this URL will be redirected to the main page if the page will be entered from external. But once you are in the main page, the links to the other pages should work. I realized it on this way for the reason that it gives me the freedom to rename pages like I want, to move pages to other servers and to have the menu at the left side available every time. Best Regards, Thorsten.

Hi, In the meantime I tried it with different browsers and operating systems, but I cannot reproduce these problems. Ok - you are not able to jump to an URL directly (e.g http://www.ucapps.de/mbhp.html), this URL will be redirected to the main page if the page will be entered from external. But once you are in the main page, the links to the other pages should work. I realized it on this way for the reason that it gives me the freedom to rename pages like I want, to move pages to other servers and to have the menu at the left side available every time. Best Regards, Thorsten.

Hi Olivier, all pot values should be sent out when the pots are not in snap mode and you type on the snapshot button quickly (!). When you press the button for a longer time, the pot&button setup will be saved. Best Regards, Thorsten.

Hi Dan, yes, the second MIDI In is connected to J4 via an optocoupler. The circuit cannot be powered via MIDI - this would require some circuit changes and mostly it will not run successfully (I tried it once, it worked with my AN1x, but didn't work on another users synth, so I gave up) 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.

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.