liinnerd

you could use encoders next to the pots if you don't want to use a second core.

soldering the bridges is easier then making a complete new pcb I.M.O. ;) however grouping things on one larger pcb is a good idea!

your english is fine ;) ... I just wanted to show you my threat because its very similar.. doesnt matter if you use 7 or 8 leds ;-) But then again if you only use 16 encoders + rings then I would stay with the standard ledring configuration. just connect your 16x7 leds like the ledring schematic shows you. when everything works, you could configure the ledring pattern to your needs.

oh no reason at all, thought it might be easier, but it aint :-) And when I use 5 SRs how would i configure it then? I suppose it also needs some coding

good idea. But here in Holland farnell charges 5 euro's handling costs for orders below 50 euro's.. don't know if it's the same in the UK. So it could be expensive to order just 2 pots ;-)

Hi Gino, You could connect just 7 leds instead of the 11 shown in the example. I've done it with 8 leds (I'm using ledbars). I'm also trying to reduce the code to 8 leds to drive 32 ledbars from 1 Doutx4. But no luck so far. My problem looks a lot like yours (if i'm correct) take a look at my post: http://www.midibox.org/forum/index.php/topic,13899.0.html Hope i'll figure it out soon. Grtz, Richard

Okay i took a peek at the code. I removed all references to ledring handler (mb64_ledrings.inc) and configured the system (main.inc) to use 1+2 x 3 (SR 1+2 cathodes, SR 3 annodes) for the first 16 ledbars and sr 1+2 x 4 for the second 16 ledbars. Compiled it... uploaded it..... but as I thought it doesnt work ??? Can it be done this way? or am I miles off... ;-)

YES you're right.. maybe I wasn't clear on that ;-) I have the hardware already finished and I could just use 2 DOUTx4, but if it could be done with one DOUTx4 it would be more efficient. My asm coding skills are very limited and I don't know if it's hard to do. Do you think it needs a lot of programming?

Looks like you could use them... there 10K Lineair so shouldn't give any problems. The difference between the two? The price ;-) Looks like one is horizont PCB mount and the other vertical. Grtz, Richard

Tilted> thanks for your input... but if you look at the example pdf (http://www.ucapps.de/mbhp/mbhp_doutx4_ledrings.pdf) the 4the register is use for leds 9,10,11 so it should be possible to drive the next 16 ledrings with this SR and connect the cathodes on SR 1 and 2. Or am I missing something? Maybe I should just try it... but i'm afraid i'll just mess things up ;-) I had already a lot of probs to get thing working :)

Let me refrase the above. If I only use 8 Leds for a Ledring, would it be possbile to use one DOUTX4 for 32 Ledrings? And if so, do I need to change something in the sourcecode or can I just configure the correct SR settings in the main.asm? Richard

It's been a long time since I posted a question on this board but this is one I can't figure out on my own. So I hop someone can point me in the right direction. I'm configuring my MidiBox 64e to use 16 Ledbars as ledrings and connected them as shown in the DOUT example (http://www.ucapps.de/mbhp/mbhp_doutx4_ledrings.pdf) I've configure the setup file and everything works. But since one ledbar only uses 8 leds I thought let's disable the 4th register in the setup #define LEDRINGS_SR_ENC1_16_CATHODES_1 1 ; first shift register 16 LED rings for module 1 cathodes - #define LEDRINGS_SR_ENC1_16_CATHODES_2 2 #define LEDRINGS_SR_ENC1_16_ANODES_1 3 #define LEDRINGS_SR_ENC1_16_ANODES_2 0 ** edit: somehow the whitespace between cathode and register numer was lost in the code display above. FIXED IT! ** But when I upload this configuration the ledbars won't light up. When I change the LEDRINGS_SR_ENC1_16_ANODES_2 to SR 4. everything is okay. Is it possible to disable it somehow? Not that its really necessary but I'm just curious. I will extend my box to 32 ledbars which leads me to my other question.... Is it possible to share the cathodes from the next 16 bars with SR 1+2 and drive them with the 4th register to connect 32 LEDBARS on one DOUTX4? Hope someone can help me thanks!, Richard

I Like using the screen, but only for visual feedback from certain plugins/effects settings. It would be great if you could really customize the ableton layout so you would only need a 10" screen (or smaller). As for the controls; You could insert a max/msp patch by using rewire but I don't know if it's possible to extract clip info etc and send it to your midibox.

Hey! i didn't said it would work ;-) I tried to use the API but it crashes as soon as I try to enable it in Live. Hopefully the collaboration between Ableton and cycling'74 will result in a better solution for this problem soon!!!

To do those things you don't need to do fancy stuff with max/msp. You can simply assign MIDI ctrl to Ableton, e.g: per channel start/stop and scene up and down is also possible. Just use a rotary encoder and assign clockwise turn to up and counterclockw. to down. If you really want to have flashy disco leds than take a look at Live API http://code.google.com/p/liveapi/ Live API can be used as a bridge between Live and Max/Msp and allows you to extract more info out of Live. (as far as I know this is what Monolake also used)

It should work. You'll need to build the 16f88 adapter http://www.ucapps.de/mbhp/mbhp_burner_16f88_adapter.pdf And download the 16F software http://www.sprut.de/electronic/soft/pbrenner/pbrenner2.htm I haqven't tried it yet, but it should work. grtz, Liinnerd

ah ok. I thought it would be something like that, I just needed confirmation ;-) Thnx!

oow oke! I'm glad it works. But why would you use remote scripts? does this give you more flexibilty on outputting certain midi data. For example: is it possible to give each clip it's unique midi ID to remote control?

I also don't understand what the problem is. I used a controller with ableton Live 5 & 6. and it sends back the info to my controller, so when I change something on the screen the button on my controller changes with it. Now to activate this function all you need to do is.... go to prefs --> MIDI /sync then select the MIDI IN port from your controller and activate TRACK [ON] & REMOTE [ON] do exactly the same for the MIDI OUT port that connects your controller to your pc/mac When you close the prefs window, you should be able to map a controller key to ableton by using midi map. And when you click on a button it should feedback to your controller. Hope this helps. grtz, Liinnerd

ah that explains a lot.. ;-) í'm glad you made the layouts for all the midibox modules that way, otherwise i had to hardwire all the ground paths manually :-) grtz, Liinnerd

Here are the images of the pic burner (without ratsnest) as promised. The other modules function perfectly without the ratsnest. grtz, Liinnerd

Okay! I'll try to make doc for the core and picburner. If I remember correctly the other modules work correct without the ratsnest. There's one downside.. You'll have to wait till saturday, because i don't have the modules here with me now. Grtz, Liinnerd

I also forgot to make the ratsnest before exporting the print, so my modules and pic programmer where also missing some connections. But i've manage to solve this buy wiring them by hand. I could take a look at them and discribe it to you , or make some images if you are interested. grtz, Liinnerd

yes david i did my homework.. maybe more people should do that before asking questions. I started building my midibox about a year ago and before I started, I just read all the information on the website and of course the forum (which is a great source of information) FKY> By just reading the docs about the core and modules on the website it should'nt be to difficult to understand how everything works and is interconnected. And if that does'nt help you that you can do a search on the forum. But I understand that somethimes it can be very confusing on which modules to use. So the great flexibility is maybe also it's downside for the mdibox... but hey! i you can't manage that maybe you should go and buy a controller in the shop (maybe cheaper to) But for those who want an true ass kickin' midi machine... MidiBox is the thing for YOU! And the folks here on the forum are glad to help you, just as long as you show a little initiative yourself!. Good Luck with your box! Grtz, Liinnerd

Indeed! first you read.. then you ask... but to give you a hint.. 60 buttons and switches (with some led if it's possible) --> 60 DIN inputs for buttons, 60 DOUT for corresponding led's 10 slider potentiometer --> 10 AIN (analogue inputs) 40 rotary potentiometer --> 40 AIN (I assume you mean oldskool pots and not rotary encoders, because rotary's need DIN's) --> so you need a total of 50 ain's Hope this give you a kickstart... and now... READ.. READ.... there's enough info on the site aswell as the forum and wiki! grtz, Liinnerd