findbuddha

http://meeblip.noisepages.com/

Encoders are only wired to DIN. There's a PDF on ucapps.de -> DIN module that shows how encoders are connected, it's the same idea in Wilba's PCB.

http://www.ucapps.de/ Read about the Core modules, and the DIN/DOUT/AIN/MF modules. :)

All the buttons and LEDs on Wilba's PCB are connected to a matrix, to save on shift registers.

These lines: # number of first and second DOUT shift register used for GP LEDs GP_DOUT_L_SR 3 GP_DOUT_R_SR 4 # DOUTs for Dual Color option: GP_DOUT_L2_SR 0 GP_DOUT_R2_SR 0 are enough for 1x16 dual color LEDs or 2x16 single color LEDs. As for de-illuminating of 1st color of dual LED, I don't know how it's handled. In the BLM section there is an option for this....

Read here:

Can't help with the power supply stuff sorry. As for MB LC: For 16 channels you'll need 2x Core8 (PIC). A Core32 (STM32) implementation isn't doable, unless you can roll your own solution for touch sensors. (I've just ordered a Core32 and 2x Core8 for this purpose - expensive and I'll have to do a bit of coding). As for all your buttons and encoders: - You'll need to check what's actually supported by the Mackie/Logic Control protocol - Each core module can handle up to 16x8 digital inputs and 16x8 digital outputs. Have a look at TK's interconnection diagrams on ucapps.de for an idea of how the LC is usually connected up.

If you want to use Core32 you'll need to do some programming yourself - check http://svnmios.midibox.org/ for code/tutorials etc. to make sure you're comfortable with this. Each DINx4/DOUTx4 module has 32 pins - you'll need 1 pin for each LED/button, unless you want to work out a matrix.

You want to be using the BLM_SCALAR app as a base for your own software. DIN_BLM_NotifyToggle is in app.c, and is called whenever a pin changes on the BLM. TK's code is very well commented! (I'm seeing all this in the MIOS32 section, it's a little different in the MIOS8 section but you should be able to work it out) :)

From the readme in SVN for BLM_SCALAR: Looks like you might have to do a little coding to get it to work how you want. (DIN_BLM_NotifyToggle looks like a good starting point) :)

TK, is there any update to this situation? If I were to be ordering from SmashTV shortly, would it be safe to get a Core8 for this purpose? I assume this would be overkill, but a safe option. Thanks :)

Real buttons! And bigger too!..................... NO ITUNES!!!!!! :frantics:

Quick drawing: Top is 4.5mm translucent, to protrude slightly above 3mm front panel. Bottom is 8mm extension of the buttons actuator, with a space to fit the LED, and allow room for button to go up and down without pushing on LED. Larger than top part to prevent the assembly falling out. May need to be taller, depending on height of LED and length of button travel.

I'm going to attempt something with laser cut acrylic from ponoko.

Seller says they won't ship outside EU.... would any of you kind Germans consider purchasing on behalf of other midiboxers? Ta :)

Here's what Wilba mentioned about LEDs in the BLM forum (this was for shining through the sparkfun button pads):

I've mailed the seller to see if they ship to Aus..... Hawkeye, did you have any particular SMD LEDs in mind? Do you intend to attach LED to button actuator, or locate next to button? The 3mm through hole LEDs I had intended to use are too tall to mount next to these buttons. :)

How nice are the buttons? Are they totally silent? Wonder if the seller ships outside of EU.....

Thanks, I was tossing up between Ableton Live with a tightly integrated midi interface (must have step sequencer) or using Reaper + MBSeq. I looked briefly into Live's API and Max4Live situation, and decided to stay well away - especially given Ableton's poor delivery of promised hardware integration features with M4L.

I might be interested in OSC too, apparently Reaper is going to get OSC support in the nearish future.

Careful, there's a time limit for filing a complaint.

Are you able to access data inside clips? Ie. use control surface as hardware step sequencer? :)

There are some spam links in the wiki - 2 I could see on front page, not sure about elsewhere