Hi Skyrise,
not having an AIN-module doesn’t mean I can’t have analog inputs right?
right. Because there’s heavy scaling and interpolation done and quite a bunch of variables are used per sensor/AIN Line, I restricted it to the 8 AIN lines available directly on the Core module (unmuxed mode).
I think 32 AINs (in muxed mode by connecting an AIN module to the 8 “unmuxed” pins) would be too much for the current PIC…
Let’s say I have 3 digital inputs (on/off) and 4 analog “sliders” (0V-5V) it would fit on your Sensorizer Box?
Well, the thing is:
No DINs here, because the DIN is already used to control the Hardware User Interface.
I’ve built the sensorizer to be able to simply plug any sensor into my box and use it immediately. As my setup changes quite often (distance-, touch-, skinresistance-, capacity-sensors…), I just need the appropriate cable+connector and I’m ready to go. I also have another controller (microKONTROL) with sliders and encoders to fine-tune some settings…
The specialized target functionality and the field of expertise is quite clear (talking of Sensorizer vs. MB64). I think that’s good - and I don’t want to get in “feature-conflict” with the default Midibox(es).
It wouldn’t be that hard to adapt the sensorizer if you were a programmer, but as you are not that good in that field, I’d recommend, you simply build both of them. As mentioned, the Sensorizer Basic consists of just a few hardware pieces, it should be easily integrateable. And remember, you can always reuse a core module for anything else if you’re not confident.
I can help you with enabling the MIDI-Merger in the sensorizer software, that means you could connect both boxes in row…
The sensors I am going to use for my Audiovisual Liveset will be an infrared slider (AI), a plastic cowboy-gun (DI), some cushion-buttons for a breakdancer (DI) and maybe more.
Because there’s just one sensor with analogue output listed – another idea:
there’s also the possibility to use a MB64/e and work on a circuit that improves the voltage of the sensor. For example, you could use a rail-to-rail opAmp to amplify signals to gain a maximum of 5Vs. If you can make the sensor send out 0-5Vs in the end and if we’re talking of a maximum of one or two sensors, I’d think this would probably be the easiest method.
hope this helps! 
Best regards,
Michael
ps: maybe some additional infos for future sensorizer developments:
The Core functionality will definitely remain (just sensors send MIDI), because I’d like to use remaining PIC resources to increase and strengthen the basic functionality. Ideas are: sending quantized Note Ons (and not only CCs), maybe in conjunction with harmonization…