TK.

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.

Hi Dan, thanks for the additions :) Yes, a LED digit display could be used. A demonstrator is still in the queue ;-) A SysEx message which contains the value could also be possible, but maybe it's better just to send out a CC or NRPN and to visualize the value with Logic? You can use the MIOS_MIDI_TxBufferPut function to send out values. Best Regards, Thorsten.

Hi js, yes, the MIOS_AIN_Muxed function is very important, otherwise the multiplexer control lines at port J6 will not be serviced. Fine that you've found the solution :) Best Regards, Thorsten.

Hi Jason, the PIC should already run with 4.5V. Maybe it's better to check the crystal first, it has to be isolated from the copper tracks with a tape in order to avoid shorts. This picture shows, how it has to be done for MIDIbox Plus, but for the MBHP core module it's the same: Best Regards, Thorsten.

Hi Jason, the PIC should already run with 4.5V. Maybe it's better to check the crystal first, it has to be isolated from the copper tracks with a tape in order to avoid shorts. This picture shows, how it has to be done for MIDIbox Plus, but for the MBHP core module it's the same: Best Regards, Thorsten.

Hi Xcen, for a beginner it makes sense to start with MIDIbox Plus. This is the easiest solution with a single board, and the performance isn't worse than the modularised MBHP designs, just only the number of pots/faders and buttons is limited. Later you can decide by yourself if you still need more controllers, or if MIDIbox Plus is sufficient for your needs. The schematic, PCB, partlist etc. can be found under Old Projects->MIDIbox Plus->Design. Premade PCBs are currently provided by Mike (see link at this page), but later also by SmashTV from the US. He plans also to offer kits and to burn PICs, but you have to be very patient before the rollout. Best Regards, Thorsten.

Hi Xcen, for a beginner it makes sense to start with MIDIbox Plus. This is the easiest solution with a single board, and the performance isn't worse than the modularised MBHP designs, just only the number of pots/faders and buttons is limited. Later you can decide by yourself if you still need more controllers, or if MIDIbox Plus is sufficient for your needs. The schematic, PCB, partlist etc. can be found under Old Projects->MIDIbox Plus->Design. Premade PCBs are currently provided by Mike (see link at this page), but later also by SmashTV from the US. He plans also to offer kits and to burn PICs, but you have to be very patient before the rollout. Best Regards, Thorsten.

The new version comes with some small improvements which will be used by upcoming applications in the next week/month/year. Although you will not notice a big difference compared to MIOS V1.1 so long as the applications don't use these features, just get the new release to be up-to-date MIOS_LCD_TypeSet offers additional parameters the chip select lines of KS0108 or HD61202 based displays can now be inverted additional GLCD driver for T6963c based displays. The performance of this display is very poor, it is not recommented for applications which have to react in realtime like the MIDIbox LC or any other "MIDI receiver" the enable pins of character LCDs can now be changed during runtime. In this way it is possible to connect multiple LCDs to one core module, the maximum number of LCDs which can be handled by a application is now only limited by the number of free pins fast write to BankStick and EEPROM w/o verify page write to BankStick (64 bytes at once) dynamic priority sampling for muxed pots (improved latency, known from MIDIbox Plus and MIDIbox64) Additional sources: Schematic for GLCD type 0 (KS0108 and HD61202 or compatible) http://www.ucapps.de/mbhp/mbhp_glcd0.pdf Schematic for GLCD type 1 (T6963C or compatible --- not recommented) http://www.ucapps.de/mbhp/mbhp_glcd1.pdf The first application which will get use of the new MIOS V1.2 functions is the SID (the BankStick page write will solve the SysEx buffer overrun issue) Best Regards, Thorsten.

The new version comes with some small improvements which will be used by upcoming applications in the next week/month/year. Although you will not notice a big difference compared to MIOS V1.1 so long as the applications don't use these features, just get the new release to be up-to-date MIOS_LCD_TypeSet offers additional parameters the chip select lines of KS0108 or HD61202 based displays can now be inverted additional GLCD driver for T6963c based displays. The performance of this display is very poor, it is not recommented for applications which have to react in realtime like the MIDIbox LC or any other "MIDI receiver" the enable pins of character LCDs can now be changed during runtime. In this way it is possible to connect multiple LCDs to one core module, the maximum number of LCDs which can be handled by a application is now only limited by the number of free pins fast write to BankStick and EEPROM w/o verify page write to BankStick (64 bytes at once) dynamic priority sampling for muxed pots (improved latency, known from MIDIbox Plus and MIDIbox64) Additional sources: Schematic for GLCD type 0 (KS0108 and HD61202 or compatible) http://www.ucapps.de/mbhp/mbhp_glcd0.pdf Schematic for GLCD type 1 (T6963C or compatible --- not recommented) http://www.ucapps.de/mbhp/mbhp_glcd1.pdf The first application which will get use of the new MIOS V1.2 functions is the SID (the BankStick page write will solve the SysEx buffer overrun issue) Best Regards, Thorsten.

zu den Encodern: unter Concepts->MBHP->DINX4 gibt es einen Schaltplan speziell zum Alps STEC16B03 , den es bei Schuricht und RS zu kaufen gibt. Die Anschlussbelegung unterscheidet sich von herkoemmlichen Encodern, wenn man zwei Pins vertauscht, wird in der Tat langsamer inkrementiert. Ansonsten waere es natuerlich auch moeglich, den sog. "progressive mode" auszunutzen, den man mit MIOS_ENC_SpeedSet fuer jeden einzelnen Encoder einstellen kann. In diesem Modus inkrementiert der Encoder in groesseren Schritten, je schneller man ihn dreht. Bei der MB16E kann man zwischen Fast/Normal/Slow Modus via Knopfdruck umschalten, vielleicht sollte ich das bei in die MBLC Applikation auch einbauen. Allerdings wird man mit den Encodern niemals das Pot-Feeling erreichen, deshalb verwende ich bspw. auch weiterhin meine MBPlus oder MB64 wenn ich an Synth-Parameter n herumschraube... Gruss, Thorsten,

zu den Encodern: unter Concepts->MBHP->DINX4 gibt es einen Schaltplan speziell zum Alps STEC16B03 , den es bei Schuricht und RS zu kaufen gibt. Die Anschlussbelegung unterscheidet sich von herkoemmlichen Encodern, wenn man zwei Pins vertauscht, wird in der Tat langsamer inkrementiert. Ansonsten waere es natuerlich auch moeglich, den sog. "progressive mode" auszunutzen, den man mit MIOS_ENC_SpeedSet fuer jeden einzelnen Encoder einstellen kann. In diesem Modus inkrementiert der Encoder in groesseren Schritten, je schneller man ihn dreht. Bei der MB16E kann man zwischen Fast/Normal/Slow Modus via Knopfdruck umschalten, vielleicht sollte ich das bei in die MBLC Applikation auch einbauen. Allerdings wird man mit den Encodern niemals das Pot-Feeling erreichen, deshalb verwende ich bspw. auch weiterhin meine MBPlus oder MB64 wenn ich an Synth-Parameter n herumschraube... Gruss, Thorsten,

You are a fool! --- end of discussion from my side --- Best Regards, Thorsten.

You are a fool! --- end of discussion from my side --- Best Regards, Thorsten.

Viel Spass beim Beta-Testen! :) Ja, die LC-User haben es nicht leicht. Aber mit einem Firmware-Update koennte Mackie eigentlich auch ihre eigenen Controller wesentlich flexibler ausstatten. Warum die das nicht machen, weiss der Geier... yep, zum Beispiel. Aber auch der Parallelbetrieb macht Sinn. Ich kenne Cubase nicht so genau, aber unter Logic koennte man bspw. ein Environment basteln, mit dem man den GPC Modus fuer seine Lieblings-Plugins und externen Synthesizer/Fx's verwenden koennte, und den (wesentlich dynamischeren) LC modus fuer den Reset. Der Vorteil: auf diese Weise kann man sich die Controller so sortieren, wie man sie gerade braucht. Mit der Moeglichkeit, Gruppen und Menues zu erstellen, wird der GPC modus dann sogar richtig ergonomisch bedienbar. :) Gruss, Thorsten. P.S.: die Idee zum GPC Modus stammt uebrigens von Axel!

Viel Spass beim Beta-Testen! :) Ja, die LC-User haben es nicht leicht. Aber mit einem Firmware-Update koennte Mackie eigentlich auch ihre eigenen Controller wesentlich flexibler ausstatten. Warum die das nicht machen, weiss der Geier... yep, zum Beispiel. Aber auch der Parallelbetrieb macht Sinn. Ich kenne Cubase nicht so genau, aber unter Logic koennte man bspw. ein Environment basteln, mit dem man den GPC Modus fuer seine Lieblings-Plugins und externen Synthesizer/Fx's verwenden koennte, und den (wesentlich dynamischeren) LC modus fuer den Reset. Der Vorteil: auf diese Weise kann man sich die Controller so sortieren, wie man sie gerade braucht. Mit der Moeglichkeit, Gruppen und Menues zu erstellen, wird der GPC modus dann sogar richtig ergonomisch bedienbar. :) Gruss, Thorsten. P.S.: die Idee zum GPC Modus stammt uebrigens von Axel!