TK.

Clockbox

83 posts in this topic

Mike, my mistake. I thought you joined play/pause. It is not problem to add dedicated pause button. Stryd, thanks for an offer, If I find out one more button don`t fits the arrangement on my design I`ll ask for you help. ;)

Mike, did I left something else?

Share this post


Link to post
Share on other sites

No, nothing else missed. Perhaps the one thing I missed, too: Space for stickers on the front to name the channels. It can be confusing with many connected slaves.

Share this post


Link to post
Share on other sites

I also didn`t left the place for stickers. Remembering which is where is not good idea after few beers on a gig. Doesn`t it? I`ll left more space at the bottom for the labels. Thanks for the tip.

Share this post


Link to post
Share on other sites

Here is the clockbox EPS layout for 8 x MIDI out if somebody needs it. The layout is tested and it it works OK. It could probably be better done but I`m new to Eagle. :P

clockbox-io.zip

4090_clockbox-io_gifb4069ae14d0990e2bb2d

clockbox-io.zip

4090_clockbox-io_gifb4069ae14d0990e2bb2d

Share this post


Link to post
Share on other sites

my design, i build it in a broken behringer device, i only had a patch of 2x40 characta display @ home so...

DSC00001.JPG

DSC00001.JPG

Share this post


Link to post
Share on other sites

Nice 1. How'd you get the silkscreen off the panel?

Share this post


Link to post
Share on other sites

with sandpaper  ;)

Share this post


Link to post
Share on other sites

I thought that'd kill the finish, but it looks like it was blank. Nice one :)

Share this post


Link to post
Share on other sites

no the finis is alright...just take 1000er paper

Share this post


Link to post
Share on other sites

Thanks man... Wet or dry?

Share this post


Link to post
Share on other sites

"easyCut plus, Waterproof, electro coated, Latex cwt Aloxyde P1000" sounds like WET but i made it Dry  :D, but it was not easy...but ok, what is easy?  8)

Share this post


Link to post
Share on other sites

Heheh thanks for the info man.

Share this post


Link to post
Share on other sites

hmm ... since Sasha built his cb i'm thinking about one for myself. But with a addition like this:SyncShifter

Share this post


Link to post
Share on other sites

hmm ... since Sasha built his cb i'm thinking about one for myself. But with a addition like this:SyncShifter

funny, i was just going to post this

Share this post


Link to post
Share on other sites

Has anyone done any testing with the clock generated for accuracy?  I'm considering building this project as I need a rock solid midi clock but I want to be sure this will be stable enough for what I am doing.

If no one has, would someone mind posting a dump from midi-ox of the generated clock timing (or similar data)?

Share this post


Link to post
Share on other sites
The strengths of a PIC microcontroller are microsecond accurate IO interactions and realtime processing.

it should be more than accurate enough to make music and deliver a most reliable and steady pace, esp. if the core is just running the small clock app... though I admit, it might get critical if you're working at the CERN staff restaurant and need atomic time accuracy for the afternoon dance over coffee & cake =)

Regards,

Michael

Share this post


Link to post
Share on other sites

Has anyone done any testing with the clock generated for accuracy? I'm considering building this project as I need a rock solid midi clock but I want to be sure this will be stable enough for what I am doing.

If no one has, would someone mind posting a dump from midi-ox of the generated clock timing (or similar data)?

Welcome aboard :)

You won't find a better MIDI clock anywhere. Tests in MIDI-Ox would be irrelevant, as the timing is at least several hundred times more accurate than the timers your PC has to offer - an oscilloscope would be required, and I know that TK used his when testing this software :)

Share this post


Link to post
Share on other sites

Thanks for the replies.

For those of you who have built this before, how long does SmashTv usually take to ship?  I have a gig coming up on May 16th that I need to use this for and I'm curious how long it will take to receive it and if I can build it fast enough (I'm fairly experienced with an iron and have all the equipment) to actually use at the show.

Tom

ps. Now what would be ideal, is combining this project with the midi merge project.  I'm using a MOTU 4x6 merge matrix (which does MTC but not midi clock...which I could never understand that choice) for that purpose but ideally the less hardware I have to tote around the better.

Share this post


Link to post
Share on other sites

I would say it's a bit late to order PCBs for this... If you are a fast worker and experienced, perhaps you could make a core module on vero board or similar?

Share this post


Link to post
Share on other sites

I *could* do it on vero (I just hate working with the stuff) but I would still need a programmed mc as I do not have a programmer so I would still have to order *something* at the very least.

Share this post


Link to post
Share on other sites

in 11 days (less some for building/testing) you will only be able to get common stuff... maybe you can get a JDM off ebay or a set of components to vero one up...

You're really cutting it fine though :( I'd get to ordering as per the ucapps.de partslist if I were you... actually if I were you, I'd work on an alternate software solution first, as a fallback in case you get time to start a clockbox but not finish it.

Share this post


Link to post
Share on other sites

Hi everybody!

Now we are nearly done with our clockcox. since we change nearly all the connections on the din my question is, where to change the assignment between the hardwarepin and the software. thx for your help.

braintu

Share this post


Link to post
Share on other sites

main.c

Share this post


Link to post
Share on other sites

I'm looking at the code and trying to determine where the best place to implement a delay in order to add drift compensation to the midi clock.  The use case is when using this clock with the PC, the PC will have lag before the audio hits the sound card but my synth will not.  So the clock should have some sort of compensation for this in order for all the sound sources to be in time correct?

The most obvious place I found was in Tick(void) just after MCLOCK_Tick();

Thoughts? 

As a side note: looking through the source code, if this clock method is the same method used by the MidiBox SEQ projects, there is no clock prioritization scheme I could see.  So if a clock and a note on event where to occur at the same time, would the clock have to wait for the note on and therefore introduce clock drift?

Share this post


Link to post
Share on other sites

I'd guess you'd wanna do that in MCLOCK_Tick().

I don't have the time to look over the code in depth, but you are aware that the note on event won't take a lot of time, right? It's not a matter of milliseconds but should be well in µs range, so I really doubt you'll need any compensation for that case ;)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now