8O

Cheers for the nice comments! The midi runs from the midibox to arkaos VJ (and there my responsibility ends). Maybe I'll have some videos to show when it's all up and running... will keep you posted... :)

Hi, hope I'm posting in the right forum here... Just wanted to share my latest finished midibox design. It's a simple DIN + Core to be used in a theatre. Each ethernet socket supports 4 DIN and they'll be wired to an arrangement of light switches as input. And gratuitous use of wood-effect vinyl, of course... The casing is an old D-Link ethernet router, cannibalised for its ports. Hacksawing straight through the original PCB was fun... :) Many thanks to the useful advice here on this forum - what a fantastic community! And to Mike's Midishop's great service when the core boards were in short supply.

Ah yes, now I notice that the routing between IC3 and IC4 is done as I imagine between IC2 and IC3 should be... Something for V3, maybe... ;)

Sometimes the obvious answer is the right one! :) :)

Hi again, Hope I'm in the right forum again - did a quick search for this, but didn't find anything... Am currently assembling a DINx4 module and noticed that a bridge jumper is included to go from IC2 pin 10 to IC3 pin 9. But if I look on the underside of my pcb there's nothing in the way to prevent just a track being laid directly. So I'm just wondering why this bridge is necessary? Cheers!

Not sure if I'm in the right forum page here, and a search didn't show that this has been posted before, so... I just upgraded Eagle to the latest version 5.4.0 and while the brd files for the PIC and STM core boards open fine, I get an error when trying to open the brd files for ain, din and dout. Error from Eagle is: Anyone else seeing the same problem?

LOL :) :) Cheers - that's the info I wanted. Will be placing my order for new core and dinx4 kits this afternoon! Thanks again!

Hi all, I had a search on the forum and read: http://www.midibox.org/forum/index.php/topic,13095.0.html http://www.midibox.org/forum/index.php/topic,13094.0.html http://www.midibox.org/forum/index.php/topic,6570.0.html ...but I'm still unsure. Basically, I'm making a quick little project with just Core and a DINx4. The Core and DINx4 box will be right next to each other. But the switches used as input for the DINx4 will be 10m away from the DINx4 PCB. I'm planning to use CAT 5 cable with 4 signal/earth pairs per cable between the switches and the DINx4. What's the maximum length I can get away with reliably? Is there a calculation I can do or is it too dependent on cable quality, etc? Thanks in advance for any advice...

Hi, I just wrote something similar in another Waldorf controller thread. This looks like another interesting project! But as in the other thread, my devil's advocate question is: do you really want to reduce the number of encoders? Playing round with my Waldorf synth mapped to a commercial midi controller, and also thinking about building a dedicated midibox control for it, I would be thinking about giving as many of the parameters as possible their own dedicated knob/button. It means more knobs = more cost, but I recommend thinking about the extra usability it will bring. Just an idea! Feel free to ignore completely! ;D

Scorchio!

Hi Alexander - in another thread I had the same question regarding the skeleton code. Yes, it's been moved to the mios base package.

Just to close this thread: all the new info is in http://www.midibox.org/forum/index.php/topic,11882.0.html and it works beautifully!

Absolutely brilliant - many thanks!

Upgraded to gpasm 013.6 beta and just now managed to successfully compile my first asm application. Lovely. I owe you all a beer each for your great help! Cheers!

Cheers guys. I'm running gpasm-0.13.3 beta, so I guess I should upgrade. I'm also checking everything in the link you posted Thorsten - thanks for the pointer. That'll keep me quiet for a while... :)

I agree with the others that it would make more sense to use them in an analogue circuit, but I came across an old article describing how to change the characteristics of log & linear pots which may be of interest if you're determined to try to use the faders. http://www.elby-designs.com/documents/tailoringpotentionometers.pdf - but, as the article mentions, you're only going to get a rough approximation of a linear characteristics, even if your faders turn out to have ideal log characteristics. Might be worth investigating anyway...

Ok, that's my homework - will get busy getting logs to post. Will get back to you... Since posting that other thread, I've been regularly checking here: http://www.midibox.org/dokuwiki/application_development http://www.midibox.org/dokuwiki/how_to_use_xcode2_as_ide_on_a_mac http://www.midibox.org/dokuwiki/installing_gputils_and_sdcc_on_osx ...but haven't seen any changes for a new structure. Am I looking in the right place? I've also lost the links for the skeleton codes (e.g. http://ucapps.de/mios/sdcc_skeleton_v1_9a.zip - is a 404)... am I going crazy, or have they moved somewhere outside the realms of the ucapps search...?

Cheers for the fast reply folks. Stryd_one, here's my earlier thread on trying to get assembly stuff to compile on OSX: http://www.midibox.org/forum/index.php/topic,11858.0.html The goal is an Ableton Live controller with 24 DIN, 2 AIN (pots), 24 DOUT - that's my first attempt which is more of a test run. After that, trying some encs in AIN too... Pretty basic stuff ;D Edit: the goal of the code modifications I want to do is to change the info that's displayed on the LCD. I am using a 2x8 LCD (don't ask why ;D) and would like to modify the code a little so that the useful information gets displayed in the first 8 characters... Edit2: oh, and also modifying the code to add DOUT control of a serial input latched driver...

I'm making steady (read: slow ;)) progress on my midibox project, and have now reached the point where I really have to dive into the software side a little. The problem is that I'm still having loads of issues getting asm compiling on Mac OSX (C compiling works fine). I currently have the midibox64 code (latest version) running nicely on my PIC, but now that I want to start changing the code it looks like I need to change to a C-based application. So, I'm thinking ain64_din128_dout128_v2b is the closest thing in C, compared to midibox64 code. Is this a correct assumption? Anyone else been in this same situation? I am guessing there is no C version of the midibox64 application itself, is there...? Thanks in advance for any advice!

Timelapse? What timelapse? ;D Ahem, a Canon IXUS 75 on a Hama micro tripod.

Shhhh.... ;) ;)

Ah, you beauty, I finally got the DINx4 to work! It had me scratching my head for ages until my trusty multimeter spotted that the lower right-hand corner of the PIC wasn't pressed into the socket tightly. So while the pins were all behaving correctly, the PIC wasn't getting any of my delicious DIN signals. Now all is beautiful and tonight I even sent my first midi note to Ableton Live. Never has a single piano note sounded so nice! :) Keep up the good work folks! :)

Cool - maybe see you here! It's a great city!

( )Enjoy! Again! PS: I did rush it a bit - those caps on the underside are a right palaver - so it only kinda works at the moment... :-\

Thanks Narwhal - so maybe I'll build some other example apps and see if they give me some hints. Sounds like it should work in theory... Thanks Thorsten - looking forward to the new info... :)