stryd_one

Hi jeb, The pointers would be even slower than the switch statement :( For realtime stuff like clock ticks, I suggest taking a leaf out of TK's book... You have a counter which is incremented when the clock ticks, and then in the user_tick, you test that counter, and if it is not zero, you call your function. Your switch statement is bang-on though. I'll leave the double-switch thingy to one of the C gurus :)

Maybe it's my LCD but all I can see is a hand, a guitar shape, and some blue lights....

Needs labels ;D hehehe just a running joke, ignore me. I like the internal LCD!

You sure you need all that? Why not have some kind of banking system so you can see for example 12 tracks at a time? Once every few manths someone comes along with an idea like yours but so far I don't believe that anyone has done it - and with good reason. It might pay to reconsider your design so that it is a bit more practical.... You only have two hands, and one pair of eyes which will only be able to tell one LED from another within a 50cm radius... It's just as quick to hit a button as it is to turn your head.

RIP. Sorry for the loss of your friend :'(

Wow how did I miss this thread? Forum must've gone weird... Anyway this is a great idea thomas! Tell us more about it... does it store each 'take' separately so that you can add and remove recorded loops? Or does it merge or overwrite to a single loop? How many entries are allowed per loop? how accurate (what ppqn) are the note entries? does it quantise? Do I ask too many questions? hehehe

There's one major flaw with your concept - the BPM is determined by the record, not the turntable, so this would not have any advantage over just using a few buttons... Seems a lot of trouble to go to for no real benefit...but maybe I missed something :) Even still, you could retrofit the turntable so that you could get the setting of the RPM and pitch adjust directly - no need to do crazy things with LEDs ;) If you must use the optical encoder method you described, you would do better with two sets of holes around the outside like this: x__x__x__x__x__x__x__ _x__x__x__x__x__x__x__ The asymmetrically staggered rows mean that the encoder can really see where it's going, otherwise you can get some strange patterns happening. Another thing you might want to consider is the relationship between the size and number of holes, and the circumference of the disk, to the rate at which you would need to sample the encoder. Anyway, as for midi clock, it works just like a metronome or a ticking watch... It just goes tick, tick, tick, tick, tick..... So there is no 'beginning' or 'end' or step, just a pulse. You are correct that it just starts counting from the tick at the 'beginning', but the ticks are all the same, so how does it know when to start? MIDI Start message (FA). When you hit play on your seq, it sends a message to say "The song starts on the next clock tick", and then the drum machine starts to wait for a tick (F8). Next, your seq sends clock ticks as it plays. When the drum machine gets the first tick, it starts to play it's own sequence, and counts each tick as it arrives. It knows that there are 24 F8 ticks per quarter note, and so when it gets to the 24th tick, it knows that a 1/4 note has passed and it should play the next step. If you don't start from the beginning of the song, it will use SPP to set the location within the song, and then continue from there. I HIGHLY recommend that you read this entire site, but as a minimum, this article is a MUST : Syncing Sequence Playback Hope that helps :)

I've read something about sdcc wanting brackets around every entry, maybe try this: test = {{{1},{2}},{{2},{2}}}; Wow that's ugly!

Well, the hex and syx files essentially are the same data, just delivered differently - the syx file is generated from the hex file. MIOS Studio is definitely the best tool at the moment, and it uses hex files, so that's the way to go. When you download the .jar file, it is often renamed to .zip (due to an extremely common misconfiguration of IE/FF/WinZip). Just rename the .zip file to .jar, double-click it and and you're set :)

Let's put it like this... it's a lot easier to find 1/4" knobs than 1/8" encoders....

Yeh but he's the original version with the buggy firmware ;)

It sounds like the application isn't uploading correctly... Are you using the hex file uploader in 'smart mode'?

Thats so darn cool it's crazy :D

Good stuff :) As I suspect would be the case with many others, my level of interest would be largely dependent upon price though... Is there any indication?

Close.... The way it works is that you have a master, and that sends a midi message of one single byte, 0xF8, which it sends 24 times per beat... Everything else will 'slave' to that master, by receiving those clock ticks, and counting them in a way that allows them to calculate the BPM. What are you trying to do?

OK so: No pots = Everything is OK Add one pot, leave all other AINs grounded. Turn on the box. Test that there is still no jitter, and that the pot works as expected Repeat until it doesn't work Tell us when that is :)

Heh nah they won't quite make the grade :) I need panel mount, sealed to mil spec or at least IP65, with PCB pins, subminiature, but with an actuator that will allow the small switch to have a larger button, button must be matte black or non glossy bare metal, action should be positive, but actuation should not cause too loud a click, I need at least 300 max 500, target price $2 each. Now you know why I've been looking so long... I found some with all that except they have solder lugs not PCB pins.... The search continues :( Edit: Tilted, watch out, someone else got those encoders lately and had trouble...

Uhmmm 16 pin DIP?

Yeh, that was it ;D I've been searching for my switches for almost a year now...... ::)

Yeh :( Finding the right parts can really be a b*tch!

Oh, mine are usually the MC box with their logo on it :) Oh yeh... AD, not MC. *slap* derrrr!

Just so that I can answer in a more precise way... what are you building?

Yeh, with all the LED's lit and motorfaders moving.... And a fire extinguisher on standby ;)

Hi kap, In short: log pots won't work. Sorry!

16 PPR encoders are not supported, use them at your own risk. (IE dude, don't do it :) )