TK.

Hi Dan, fine that it works! :) No, this release doesn't provide the control surface handling, this has to be done when my own hardware is ready (could take 2-3 weeks). You could modify sid_ain.inc. SID CC's can be controlled with the SID_CCIN_Set function. However, in the meantime I had the idea for a very flexible minimal control unit which is similar to MIDIbox TC, but much faster in the handling (it's a mix between the VST parameter handling of Logic Control and the F-key handling of a HP48 calculator ;-)) and it will provide several hardware options: 2x16, 2x20 or 2x40 LCD, 8 buttons, 6 buttons/1 encoder, 8 buttons/1 pot, etc. So, if you want to control your SID(s) directly without a computer, it could be a good idea to continue with the MIDIbox TC example. I will release the interim solution possibly tomorrow :) Best Regards, Thorsten.

Really great price! :) Best Regards, Thorsten.

Hi Matteo, now you will find some more informations about MIOS under Concepts->MIOS->Introduction which should explain the reasons, why the MIOS concept is more useful than the PIC16F solutions :) Best Regards, Thorsten.

Yes, I've ordered 3x24LC256, 3xPIC16F877 and 3xPIC18F452 I/P, the package was delivered via FedEx directly from Taiwan and I haven't payed any cent! :) Best Regards, Thorsten.

Hi Kyo, yes, you have to use two core modules for this setup, but it will work :) I would use one single core, 4xDINX4, 4xDOUTX4 as "MIDIbox Link Forwarding Point" (at the begining of the MIDI chain) only for the encoders and LED rings, and a second core as "MIDIbox Link Endpoint" for the rest. An AIN module is not required, since MIOS supports also unmuxed (non-multiplexed) access to the ADC. The appr. configuration has to be made in the initialization routine: ;; initialize the AIN driver ;; use 8 faders movlw 8 call MIOS_AIN_NumberSet ;; don't use the AIN 4051 multiplexers call MIOS_AIN_UnMuxed I will provide a test application for 64 encoders and LED rings in the next days. Best Regards, Thorsten.

Hi Dan, I've just added a MIOS introduction to my homepage which should make the concept clear. ;-) 4x40 LCD: sure - will work. But you have to enhance the application by yourself, so that it prints more or less usefull messages on the additional space. Thereafter you can send me your modifications so that I can release it with the official version. Best Regards, Thorsten.

Hi Matteo, you should follow the other postings, because I don't want to repeat myself every time... ;-) PIC16F: funny, but a lot of limitations. All of my PIC16F firmwares get the best out of this controller, but it is very hard to add even more features PIC18F: more memory, faster CPU, less limitations, same price. Order some free PIC18F452-I/P at Microchip, exchange the 20 MHz crystal by a 10 MHz crystal and you are ready for the next generation! :) Best Regards, Thorsten.

Hi again, SID slaves: no LCD required SID master: no LCD required SID control surface: 2x20 LCD required Best Regards, Thorsten.

Hi T-z-Z, sure ;-) the system architecture of MIOS is quite stable, everything has been pepared for more complex applications... See: mios_tables.inc, where you can configure 64 rotary encoders :) As I wrote in another article, a port of MIDIbox64seq to MIOS is planned, and the sequencer engine will be reusable for other types of sequencers. Rotary encoders and graphical LCD: no problem! But you have to enhance the application code by yourself or you have to hope that somebody else publishes his modifcations! Best Regards, Thorsten.

Hi Matteo, yes, you could send a "ping" command to the core: f0 00 00 7E 46 00 0F F7 The same string should be returned. Yes, because the power consumption is very low. In this case P1 and P2 are not required yep :) yes, perfect. You could also use a PSU with 200 mA Best Regards, Thorsten.

Thanks a lot for the input! :) Best Regards, Thorsten.

Hi Nenad, sorry, this was a typing error. Yes, PIC18F452 I/P or I/PT are working fine. Some instructions can be found under Concepts->MIOS->Bootstrap loader. The short form: use your JDM to burn the bootstrap loader into the PIC. Thereafter you don't need the JDM anymore! Load MIOS via MIDI, thereafter load an application via MIDI. The currently provided applications can be found under Concepts->MIOS->Download. And thats only the beginning ;-) Best Regards, Thorsten.

Hi Matteo, 470pF caps are the right ones for the 6581 (I have to update the PCB snapshot) Best Regards, Thorsten.

Hi Matteo, this isn't possible with the PIC16F version, due to memory and latency reasons. But with a PIC18F452 you just only have to enhance the sid_ain.inc file Best Regards, Thorsten.

Hi Dan, yes, this would be the perfect PSU for a MIDIbox LC!!! :) Best Regards, Thorsten.

Hi, yes, you are mostly right. MIDIbox NG is nothing else than a MIDIbox which is fully based on the MBHP, which works under MIOS as operating system and which can be used for different functions by exchanging applications via MIDI (one time a sequencer, another time a Logic Control emulator...) Hardware changes are not planned... Best Regards, Thorsten.

Hi Nenad, yes, you can reuse all the modules, just only replace the chip and the crystal. The "AIN DIN DOUT" test already works fine as Reason controller :) Best Regards, Thorsten. P.S.: you could order free samples (3 x PIC16F877, 3 x 24LC256, 3 x PIC18F452 ) at the Microchip site.

Hi, I purchased the 2x40 LCDs for 5 Euro per piece at EBay. ;-) 8 encoders or 16, if you replace the motorfaders by encoders. However, this mode is provided by the host application, it just swaps (alternates) the function of V-pots and motorfaders with one push of a button. So - 16 rotary encoders make only sense if you plan to use your box also with other MIOS applications. If you want to save money, use 8 encoders. If you find some nice faders (without motors), you can use them too. See mios_tables.inc in the source archive. But you can also assign the functions to other DIN pins if you want. Best Regards, Thorsten.

Hi *, some imperfections in the SRIO and MF handler have been fixed in this release. Additionally V1.1 provides following new functions: MIOS_HLP_16bitAddSaturate: 16 bit addition with saturation. Usefull in conjunction with rotary encoders. Will be used by upcoming applications (MIDIbox HN already uses this function in hn_enc.inc) support for detented encoders (see mios_tables.inc) MIOS_DIN_PinAutoRepeatEnable, MIOS_DIN_PinAutoRepeatDisable, MIOS_DIN_PinAutoRepeatGet: an assignable autorepeat function for every button. Excellent for data entry. Used by Magic MIDI Delay and Motorfader Calibration App. MIOS_CLCD_SpecialCharInit, MIOS_CLCD_SpecialCharsInit: allows to initialize the 8 special characters of a LCD. MIOS_LCD_YAddressSet: allows to enable a second character LCD The last function is now used by the MIDIbox LC application in order to drive two LCDs. This is a nice alternative solution compared to a graphical LCD - the characters are bigger and therefore the faders and V-pots can be arranged better on the panel (more space between the faders) The inputs of the second LCD have to be connected 1:1 with the control lines of the first LCD. Just only the E (enable) input requires a seperate interconnection to the core module: J10:RC (pin RC.4 of the PIC) It's very hard to make photos from the LCDs due to unwanted mirroring effects. Here are the only tries which adumbrate how it looks like: For comparison only the screen of a graphical LCD (sorry again for the bad quality...) Hopefully I will find some time to documentate all the new stuff (instead of programming new functions ;-)) Best Regards, Thorsten. P.S.: thanks to Axel/Frank/Rasmus (in alphabetical order) for beta-testing!

How about a low-budget MIDI controller with just one rotary encoder, one 2x20 LCD and 6 buttons to control your whole equipment? ;-) This application is just a demonstrator and far from perfection, but it's already usefull as MIDI remote device for Cubase/Logic/Whatever or softsynths like Reaktor. Up to 255 MIDI parameters can be controlled, organized in 51 banks. All parameters and banks can be labled for a better oversight. Incoming events will be registered, means: the internal values will be updated automatically - presumed that the MIDI host application sends the parameters through MIDI Out when you load a new song, a new patch, or move a virtual fader/knob. Handling: Main screen, first bank is active, 5 parameters are shown. When a parameter is selected with one of the 5 select-buttons, you can control it with the rotary encoder. So long as you turn the encoder, the parameter label will be print in long form, also a nice bar is displayed (-> bar could look better, feel free to enhance it!). Here parameter 2 (Pan) is modified. By pressing the menu button, the bank can be selected. Instead of numbers, every bank can be named. Here a connection diagram for the application: http://www.ucapps.de/mios/midibox_tc.pdf The code is available under Concepts->MIOS->Download Configuration has to be done in two seperate files: the MIDI events are defined in mios_tables.inc::MIOS_MPROC_EVENT_TABLE tc_labels.inc contains the labels for 51 banks and 255 parameters Alternative switch: in app_defines.h, you can change the VALUES_PER_PAGE setting if you would like to control only 4 parameters per page. In this case, 64 banks and 256 parameters are available. It's intended as fallback solution for 2x16 displays. Have fun! :) Best Regards, Thorsten.

Hi all, I'm not sure, maybe after the minimal control surface has been finished, but this step could be delayed, since I also want to finalize my MIDIbox64seq (PIC16F and PIC18F version) before continuing - however, it will be possible sooner or later! :) Best Regards, Thorsten.

Here a snapshot from the current design state of d2k's MIDIboxes - neat! :)

Hi *, I just have finished the port of MIDIbox SID to the MIOS platform. It behaves 1:1 like a PIC16F SID box, but the performance is much better. The software engine takes about 200 uS instead of 600 uS for one update cycle on the PIC18F, this gives us enough freedom for additional features (primary the Control surface). However, since both versions have been implemented like a realtime system, you will hear no difference. ;-) Even if a long envelope or a slow LFO is played, the timing is absolutely cycle accurate. The code can be found under Concepts->MIOS->Download I will release a first version for a minimal Control Interface with 6 buttons, one rotary encoder and a 2x20 LCD in the next days. :) Best Regards, Thorsten.

Super! :) Gruss, Thorsten.

Die Soundkarte selbst hat keinen Optokoppler integriert, davon haben sich die Hersteller schon seit Ewigkeiten erfolgreich gedrueckt. Deshalb muesste er im Gameport-Kabel eingebaut sein. Und hier koennte das Problem liegen: es gibt naemlich auch billige MIDI-Kabel ohne Optokoppler, die mit manchen Geraeten zusammenspielen, mit manchen nicht... suche mal unter http://www.deja.com nach "+gameport +midi +problem" und Du wirst merken, dass Kabel ohne Optokoppler wirklich nicht zu empfehlen sind. However, auch hierfuer gibt es eine Loesung: einen MIDIbox kann man naemlich auch ohne Adapter an den Gameport anschliessen. ;-) Gruss, Thorsten.