stryd_one

That's not quite what I meant :) For a normal interface like that, with buttons with very different functions and physical layout, I agree that makes sense, and I do the same thing....but in a keyboard situation the functions are linear (key 0 is note 0...key 64 is note 64), so it makes sense to me to reflect that in code. Having the switch statement is one way of making an exclusion to the linearity, but I prefer to make such exclusions with an if statement. I guess it also should be considered what the purpose of the thing is... because if it doesn't increase speed, or the speed increase is not noticable, or you don't plan on having any other code on the chip (like putting a synth in the keyboard) ... there's no point optimising at all! And the switch statement certainly makes it a lot easier for people to modify if they're new to C But that's the beauty of it... coding is like music, It's an artform :) Each to their own :)

Warning - while you were reading 2 new replies have been posted. You may wish to review your post. Damnit, beaten!!

Do like what it says in my sig... Hint: you want the first link ;) You might find a lot of learning can be had from reading the files too. There are comments in there that explain stuff. Is there something in particular that's tripping you up?

Groovy...or should I say, Le Groovee. Hehehehe

Nice one rasteri! Why the comparators I wonder? I take it that the levels coming from the sensors didn't always hit 0? that's an interesting concept! My split-second was reaction was "of course!" because its seems more ergonomic; it will leave your arm/wrist/hand in a more natural position (straight line), and allow you to move some of the rotation into your shoulder joints (and therefore away from your wrist). Then I tried it (on my air-mixer. it's very light.) and realised - that's good for a long set and all, but no good for fast movement. This is because the fastest movement you could use for the fader is a radial rotation of the hand, which uses the two bones in your forearm as an axis, and then your hand would be at a 90 degree angle, converting the rotation into lateral motion... yaknow, same way you always see DJ's hold their hand when scratching fast...it's natural for a reason :) To allaw the forearm to rotate fast, yu want to have your elbow right in next to your ribs, which means your forearm will point straight out away from you. When you do it that way, the 90degree angle that is standard(xfade at the front) makes the most sense. That said, the upfaders would benefit from being at a 45degree angle in both situations, so that they are closer to perpendicular (like the xfader is)... if you rock the upfaders with both hands that could be tricky though...... Woops back to topic ;)

I don't think there's room in the case for headers...

I used the quickzoom addon to get around that but yeh it could be smaller :) (damn you and your nice camera!) That's a bit strange mate, it doesn't look like software cause it's really random, like, it clears some parts of the line and not others. Don't suppose you've tried switching screens?

Sorry I meant the bypass switching, just for the effect in/outs... The mode switches etc would want to be with the filters for sure. Don't worry I will be 99% spectator on this one, at least for the time being.

Hey Aussies, put your order on the wiki page please :) Pricing may vary slightly or whatever, it'll probably go down if anything.

Yeh USD$52 plus shipping etc means it'll be closer to $70 but that's still al ot less than the $300 they used to go for... So, is the idea to hack it and make it a standalone midi device, or just to use software to send midi?

Heh, I thought I didn't have any of these chips, turns out I have 12 :D I wouldn't want the switching circuit on-board though... IMO that is a separate job and would be better on a separate board. Otherwise I'm interested :)

RS have the xtal too, and I have to place an order from them anyway (for SD sockets and numerous parts for another project). I've put that order on hold until I find out how many xtals we need. They also have the eeprom if anyone wants it. Which one of these is it exactly? I'l start a bulk order page tonight when I get home, so we can add our names and quantities to the page... I am in a rush to order though, due to the aforementioned RS order being on hold. Sideline note: I think the existing parts list has machine pin IC sockets which are nice but costly...

50 bucks? Where?

OK 1) That's a -damn- nice controller 2) Shame about the price omg. 3) "Synesthesia Corporation" oh please. 4) "patented Mandala" oh, really, that's just wrong! :D For the non-buddhist-initiated among you, that's like saying "Copyrighted Prayer". Some words just don't belong next to each other ;D

4620 and 452 are fully compatible so no worries there. As for the 4685, it kinda depends. You may have to work a little bit with the makefile and more specifically the udata pragma marker. I've done some preparations that might help a little...but, I'd just use the 4620.

I just can't read this thread any more!! LOL!

Thanks for the input dude!! It's switches are buffered up (well, latched) so only the ones that change are flipped (IE, if you tell it to be closed, and it's already closed, it won't change) and they all change near-simultaneously. The total load time is in the 4-8ns region (typical to max, so should be 4ns mostly) so that's not too bad. I think I was talking earlier about how we could implement an 'insert' effect, it would be great to have a saved source and destination for the insert which you could punch in and out like that, nice idea! and easy to integrate with this :) Thanks! Last I spoke with him they weren't quite finished, I think he wants to finish them off before anyone sees them, understandably... I'll go prod him. ;D

Levon the timesaver! Any other aussies up for a group buy? We can save a bit by crossing pricebreaks...

x2

Hey cool! Looks like you need suction or somethin though, look at all that dust..... That's great to watch man, thanks :)

http://www.youtube.com/watch?v=kl0guIkizVQ Try the youtube button... now I better watch it :)

Sweet!! 8) "Oops, TK did it again" ;D Last call for SD connectors, if you want one, PM me NOW! They'll be USD$5 plus postage from Australia to wherever you are. Here's the link with datasheet: http://australia.rs-online.com/web/search/searchBrowseAction.html?method=getProduct&R=5025010 For 30c more you can get the top-side-up version: http://australia.rs-online.com/web/search/searchBrowseAction.html?method=getProduct&R=5025004 If you're stateside then you might like to look to sparkfun, but it seems that you euro guys have no cheap source, so here it is :) Last chance from me for a while!

Well MIOS should prevent writing anything there, but the BSL is definitely cooked after foona used it, so go figure... Whatever it is, it definitely does not work ;D FYI: In recent times, the bootloader was in a different location - there's nothing wrong with serge's editor, it works as designed and as it should.

Hate to do this to you, bet you need to read this whole thread (again if you already have)... This has been covered... DIP is preferable, and that's your source (futurlec, or ebay will do fine) The docmatrix! It was revealed in this thread but kinda pre-dates this project Well, they are really, it's a tradeoff. You've compared different specs there, they're measured differently by each manufacturer, you've been misled ;) I went into more detail earlier in this thread, but the nutshell is: AD = better THD, MT = better crosstalk... Being an acoustic instrument, the THD would be of lesser concern than crosstalk to me. That said, you're more than welcome to use the AD... but it's a while away, and if time invested is your concern then using one of the existing designs is the way to go. I just don't want to see you stressing out a couple months from now if it's not ready :)

No they aren't already defined, that's part of the other project. I've got a pretty good idea of what functions will be available but it's nothing final yet. The tricky part is handling that some chips update one crosspoint at a time, while others must reload the entire matrix, and others can do both, so there needs to be optional support for all three methods of loading any one type of chip. I discussed the way this will be handled in the other thread.