TK.

Hi Frank, if the application has been written on a proper way, so that it doesn't rely on previous initializations which are made by the bootstrap loader, you could bypass the bootloader by overwriting address 0x0000-0x0002 with "NOP" instructions. Do you have access to the source code? If not, you could also patch the hex file Best Regards, Thorsten.

Hi Frank, if the application has been written on a proper way, so that it doesn't rely on previous initializations which are made by the bootstrap loader, you could bypass the bootloader by overwriting address 0x0000-0x0002 with "NOP" instructions. Do you have access to the source code? If not, you could also patch the hex file Best Regards, Thorsten.

Hi Amando, PIC18F and PIC16F are not binary compatible, there is now chance to run an old firmware on the PIC18F452 The most current version of IC-Prog also provides the PIC18F452 Best Regards, Thorsten.

Hi Dendy, I've no answer to 1) because it must be a strange electrical problem, but to number 2) it could be the reason that you are using an old bootstrap loader version? Versions below V1.1b didn't start when they received any MIDI message during the startup phase. This has been fixed in V1.1b - this version only waits for SysEx messages which begin with F0 00 00 7E 40, all other events will be ignored. Best Regards, Thorsten.

Hi Richard, the firmware changes the "encoder speed" depending on the value range (max value). Some values with a short range require more detents than others, in order to allow a precise control. So, this effect is ok. There are also some parameters like the oscillator ADSR or the filter cutoff/resonance, which are only 4 bit wide (limited by the SID chip itself). Thats the reason why these values can only be incremented/decremented by 8 But regarding the Rectangle waveform I'm unsure ("Pul" for Pulse should be displayed). If some inc/dec pulses from the encoder are missing (see also http://www.ucapps.de/mios/mios_encoder_modes.gif), you either have to change the connections (see the schematics under Concepts->MBHP->DIN) or the encoder mode in the application setup (-> mios_tables.inc) Hope this helps - have fun with the SID! :) Best Regards, Thorsten.

Hi Richard, the firmware changes the "encoder speed" depending on the value range (max value). Some values with a short range require more detents than others, in order to allow a precise control. So, this effect is ok. There are also some parameters like the oscillator ADSR or the filter cutoff/resonance, which are only 4 bit wide (limited by the SID chip itself). Thats the reason why these values can only be incremented/decremented by 8 But regarding the Rectangle waveform I'm unsure ("Pul" for Pulse should be displayed). If some inc/dec pulses from the encoder are missing (see also http://www.ucapps.de/mios/mios_encoder_modes.gif), you either have to change the connections (see the schematics under Concepts->MBHP->DIN) or the encoder mode in the application setup (-> mios_tables.inc) Hope this helps - have fun with the SID! :) Best Regards, Thorsten.

Hi Dan, in theory: yes in practice: I don't want to touch the MB64 firmware anymore, it's very hard to add even more features without relocating code (which mostly causes trouble and new bugs) Looking forward for the MIOS implementation :) Best Regards, Thorsten.

Hi Dan, in theory: yes in practice: I don't want to touch the MB64 firmware anymore, it's very hard to add even more features without relocating code (which mostly causes trouble and new bugs) Looking forward for the MIOS implementation :) Best Regards, Thorsten.

Hi, I just've got a very interesting mail from josemym@wanadoo.es - he wrote, that he was able to get the JDM running under Windows XP after he set the baudrate of the COM port to 2400 in the system setup window. Maybe this has also to be done under Win2k. Under Win ME I noticed no difference Best Regards, Thorsten.

Hi, I just've got a very interesting mail from josemym@wanadoo.es - he wrote, that he was able to get the JDM running under Windows XP after he set the baudrate of the COM port to 2400 in the system setup window. Maybe this has also to be done under Win2k. Under Win ME I noticed no difference Best Regards, Thorsten.

Hi, only the PIC18F versions will provide the possibility to change the display layout on a similar way like it has been realized for the MBLC, so that larger LCDs make sense. The PIC16F variants are unfortunately "out of memory" :-( Best Regards, Thorsten.

Hi Trenton, this is really a fair price! :) Dan re-used a mousewheel with success, here some infos: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1041441259 Best Regards, Thorsten.

Hi Trenton, this is really a fair price! :) Dan re-used a mousewheel with success, here some infos: http://www.midibox.org/cgi-bin/yabb/YaBB.cgi?board=concepts;action=display;num=1041441259 Best Regards, Thorsten.

Hi Helge, I just have changed the orderlist: "rad 10/16" changed to "rad 10/35", "rad 1/16" changed to "rad 1/63" just to avoid confusion :) Best Regards, Thorsten.

Hi Helge, I just have changed the orderlist: "rad 10/16" changed to "rad 10/35", "rad 1/16" changed to "rad 1/63" just to avoid confusion :) Best Regards, Thorsten.

Hi Flownezz, currently I've much less time for the MIDIbox stuff than expected, therefore most of my running projects are stalled, and the ISA bridge is something for the time after these projects have been completed ;-) Best Regards, Thorsten.

Hi Simolch, you are right, it makes sense to add 4 LEDs for the track mute function. The firmware already drives 32 LEDs (-> 4 shift registers), but only the first 16 are currently used. It wouldn't be a problem for me to add even more functions to the spare DOUTs - any suggestions before I change the firmware? Best Regards, Thorsten. P.S.: 32 LEDs are maximum, the PIC16F based sequencer will not support 64 LEDs due to memory limitations.

Hi Xcen, the new layout should be prefered, because it should work without any additional modifications - some months ago I made some minor changes in the circuit to improve the quality, but the PCBs of Dave, Martin and Shum are older and don't come with all these changes (you have to read the documentation to see the differences and required mods...) Also the partlist is only for the new board design http://www.ucapps.de/midibox/midibox_plus_orderlist.txt However, as I wrote: you should prefer the new one ;-) Best Regards, Thorsten.

Hi Xcen, the new layout should be prefered, because it should work without any additional modifications - some months ago I made some minor changes in the circuit to improve the quality, but the PCBs of Dave, Martin and Shum are older and don't come with all these changes (you have to read the documentation to see the differences and required mods...) Also the partlist is only for the new board design http://www.ucapps.de/midibox/midibox_plus_orderlist.txt However, as I wrote: you should prefer the new one ;-) Best Regards, Thorsten.

Hi Pay, Since these postings are also a nice documentation about MIDIbox variations, it makes sense to integrate them into the menu structure at the left side. I could add a page under "Miscellaneous->Forum Digest" which could contain some direct links to these forum articles. All what I need is a list of your favourite articles (just list the links below) Best Regards, Thorsten.

Hi Pay, Since these postings are also a nice documentation about MIDIbox variations, it makes sense to integrate them into the menu structure at the left side. I could add a page under "Miscellaneous->Forum Digest" which could contain some direct links to these forum articles. All what I need is a list of your favourite articles (just list the links below) Best Regards, Thorsten.

Darren, if it wasn't your intention to bring "just another MIDI controller" to the market in form of a DIY kit, I want to apologize for my strong words. On the other hand take this as advice that you've touched a very sensible subject. I neither want to go into competition with other companies, nor I plan to build clones of other controllers. What you are starting here, could be the first step into the wrong direction. In my eyes a uniformed controller design makes no sense, most people have their very own idea about the perfect interface for their personal workflow. If not, they will also be satisfied with commercial solutions (want to save money? Than purchase a second-hand controller at EBay...). You could help the community, if you would initiate collective orders for special components (maybe together with SmashTV), and if you could start to create parts lists especially for people in the UK. Also additional walkthroughs, written by beginners who never made a MIDI controller before, are very welcome. Tor Arne wrote a nice HowTo, but in the meantime the MBHP is so flexible, that it makes sense to add even more variations with special part lists, module diagrams, panel templates and a lot of pictures! Best Regards, Thorsten.

Darren, if it wasn't your intention to bring "just another MIDI controller" to the market in form of a DIY kit, I want to apologize for my strong words. On the other hand take this as advice that you've touched a very sensible subject. I neither want to go into competition with other companies, nor I plan to build clones of other controllers. What you are starting here, could be the first step into the wrong direction. In my eyes a uniformed controller design makes no sense, most people have their very own idea about the perfect interface for their personal workflow. If not, they will also be satisfied with commercial solutions (want to save money? Than purchase a second-hand controller at EBay...). You could help the community, if you would initiate collective orders for special components (maybe together with SmashTV), and if you could start to create parts lists especially for people in the UK. Also additional walkthroughs, written by beginners who never made a MIDI controller before, are very welcome. Tor Arne wrote a nice HowTo, but in the meantime the MBHP is so flexible, that it makes sense to add even more variations with special part lists, module diagrams, panel templates and a lot of pictures! Best Regards, Thorsten.

Hi Steve, it's strange, it just have noticed the same. Only the rotary encoders get the function of the motorfaders, but not vice versa. But I can remember that it was working a while ago. Either this has been changed in one of the latest Logic versions, or a special option has to be enabled to get this working :-/ Best Regards, Thorsten.

Hi Steve, it's strange, it just have noticed the same. Only the rotary encoders get the function of the motorfaders, but not vice versa. But I can remember that it was working a while ago. Either this has been changed in one of the latest Logic versions, or a special option has to be enabled to get this working :-/ Best Regards, Thorsten.