stryd_one

No need to host elsewhere ... You can attach images to your post, or if it is something which may need to be kept for documentation, I will be happy to upload it to the wiki for you :)

Yep that's right. If you have 126 buttons you would probably just send the same midi note number as your button number, so button 1 would be note 1, button 2 note 2, etc. Of course you can make any button send any message that you want, including whatever data you need in order to use microtonal tunings. Check out the C Interface page, especially the Sending MIDI events on button movements example and also the Functions Reference. It's a little different when using a scanning matrix, but as the developer of the app, how exactly it is done, is up to you :)

Hi jidh, Welcome aboard :) It sounds like maybe there is a problem with the cable between your DIN modules, or maybe a short on one of the PCBs Which application is this? What happens with the buttons 3-16, are they all OK like 1 and 2? Are you using momentary switches (switches off when you release it)? Where did you get your PCBs from? You may like to try some of the testing apps on the download page. I noticed you have also posted on the French forum: problème DIN So maybe you will get better help in your native tongue :)

Yeh PC's will do that... I'm assuming you don't have this problem with other devices? Is it a drift or a wide jitter? (as in, does it correct itself and swing either side of where you want it, or does it permanently slow down more and more, getting farther and farther behind where it should be)?

Heya THZ. I definitely think that you could do this for less than $300, but it will take some time, as you will need to learn to program in C. Remember, time is money: If your main aim is to save money, maybe you could invest some extra hours at work and use the overtime pay to buy a commercial offering - it will probably be cheaper when you count your hourly wage into how long it will take. Of course you will have a lot of advantages in doing it DIY - it will be fully customized to your requirements and you can always add new features later if you want to, and you will have actually, like, learned cool stuff :) What are the sound sources you will use? How do they implement playing notes in a microtonal scale? Remember that a midi note is just a message with a number attached to it - what the synth does with that number, is up to the synth. When I send a middle A, that's note number 69, my synth will play 440Hz. You will still be sending note 69 when you hit A4. What your synth does with that, is up to the synth. Some modern synths allow you to send frequency information as a sysex command (http://www.midi.org/about-midi/tuning.shtml) but most do not - in those cases you have to do something else, like sending PB data with the note - and even then, your synths must all be configured to adjust pitch in a predetermined fashion. So what I'm trying to say is... forget about this midibox for a minute, think about your synths and what they need to receive in order to play these scales.

Depends on the system. For example on mine they are editable, so it'll be stored in some kind of easily rewritable location (flash or sram or something) on yours they may be stored in the firmware as they are not editable. Could be pretty much anywhere, but in your case changing them would probably mean reburning the firmware for the system.

Well if you want to do a mod of mb64(e) to send notes microtonally, you need to have a table/array/whatever, for each scale, which contains the note data (pitchbend change, some sysex, whatever you need to send to your synth). Then you would need to mod the function for sending the notes, to use that data. I doubt that such a full-featured app as mb64 will leave sufficient free memory for such a task... Maybe you could import scales from bankstick to reduce it rather than storing every scale in ram.... But MB64 is a gutsy app and not so much room for improvement on the current PICs. You could cut other features out to make room, or you could port the app to a more capable PIC (4685/4620/etc), but either would require fairly solid knowledge of the app, and even if these things were unnecessary, certainly PIC ASM. Hope that was more constructive :D Hey THZ when you tell me what you're planning to do maybe you could mention if you have some programming experience?

I'm not the right guy to give advice on this project at this point, I'll leave it to the pipes experts... But I have to say... WOW!

True... Channel aftertouch (from an analog source) can be applied to a digital input though. Not necessarily... Some microtonal controllers send a calculated pitch bend right before each midi note out. Of course if you want to do that, then May not be true.... So tell us more THZ! I'm very curious :)

Glad it works! Thank you for documenting your solution :)

;D I'm still learning C... What can I say: There is an easier and much safer way. Declare your variable using the 'register' keyword: register unsigned char Foo; This uses the Access RAM as intended, and allocates the address as required, allowing for the MIOS parameters. I guess you could say that this is the right way to do it. A reminder that the Access Bank is small and for special variables, it's not a free pass to faster code ;)

Controller: Easy. Making the software interact with it in a useful manner: The reason I don't use PC's ;D

Ideas... well I'm guessing either a dead com.pnent, a short, software misconfiguration or a power issue (too much current through LEDs), in no order of likelihood ;) Sorry Jymm but I have to ask lots of questions and make lots of suggestions. Because this is obviously not an easy one to fix i will get straight to the point with matters. Don't take it personally, remember I just want to get your Midibox working :) Here goes: Well it's a fairly safe assumption, but you do not "Know" that at all. You "know" that switching them does not cause the thing to catch fire. But I'm yet to see where you've tested it properly to confirm that they do in fact work as designed. Maybe you have :) but I haven't seen it... I can only advise as I know ;) Using this one as an example, you can switch the PCB's, or the IC's, or the cables, or any combination... Then you've got each button connected to them as well, and maybe more cables or a CS PCB. I am not suggesting that you should test all that, but at least be aware that you have not tested them and so you are assuming it's OK, and you don't really know for sure. It's an educated guess ;) It's important, not to confuse assumptions for facts, or you may end up putting lots of effort in for no reason, and that sucks! Your troubleshooting process seems pretty darn good IMO, with the one exception being that you are very quick to kind-of-test something and state that you "know" it's good. And for goodness' sake stop bloody plugging things in and out when it's powered on! It's not an enterprise server with hotplug PCI-x ;) You may need to reconfigure the software if you want it to work the same way with different hardware. You can find out how, in the main files of the app in comments. (open main.c in notepad) What happens when you try this without the LCD? Don't forget to turn it off before reconfiguring the hardware! How did you test it to make sure it "works fine"? Just a sidenote, it may pay to be precise with the terminology to avoid confusion. a DIN is one single pin, which you would connect to a switch. A DINx4 is a module with 4 Shift registers on it, each one having 8 DIN's. That might be a good starting point for testing :D At this point you can forget the MB64 app. We'll get to that later. Right now, the test apps are the ones you want. One app you should try which wasn't mentioned here is the SRIO test app. What is the max current draw of your design? (include LEDs and LCD) Are you using standard parts? (vreg/rectifier/caps/etc) does the vreg get hot? Have you tested the 9v to make sure it really is 9V? When it's plugged into the midibox and when it's not? Have you tested the voltages on the circuit at run time? Have you checked for noise (Set to AC voltage) Have you tried another PSU? What about the cables between them? Are you connecting everything as per the schematics? Mike's kit's are good, but sometimes we make mistakes when soldering ;) This one's a strange one. I'm inclined to think that you've done a pretty good job of testing it and your assumptions are accurate and at the moment I'm suspicious of the LED's drawing too much... Dunno..... Test it out using the tips above and see if you find something suss.... Good luck man!!

I was thinking the chassis could be handy for a MB64 or LC something... The knobs I would just get from you, rather than fight a bunch of ebay dudes to a high price.

http://offer.ebay.com.au/ws/eBayISAPI.dll?ViewBids&item=140157305940 Last line is interesting if you like to recycle....

Hmm it's still doing it.. sometimes when I refresh the icons are inline (like the IE screenshot I posted before) and sometimes they are not) like the FF shot) It may have always been doing this, I never sat there refreshing the same page over and over before... I just opened it in IE and there are still no transparent gifs... Darn I got excited :(

CHEER!!!! Thanks man It's lookin good. Hangon... the icons in the boxes seem to be misaligned :( I swear they were in line like they should be just a minute ago... Yeh, like that...wait now it's broken again... hahahahah what are you doing :)

Yes thats the one you want. dimensions are on the wiki :)

What's that urban myth mangled Einstein quote about the definition of insanity? Now you're a mad scientist... welcome to the fray.

"I try only plugging a connector on the J2 port of the 2nd DIN, and the led goes out" You are powering off the whole thing when you plug and unplug cables right? :-\

Whao man that's a bit extreme! I don't think there was any kind of animosity intended, certainly not to that degree! It's all friendly here :) Unless you really p*ss me off. ;D Ahhhh! The 'K-word'!

If we rub your belly like Buddha, will some of that amazing luck be passed onto us? :)

Ahh I dig that pawful stuff... SSM was a major influence for my seq...

No it means the ASM version is the one to use. Leave the alpha for now....

Check the wiring ... again ;)