a reason not to slave your mpc...

innerclock wrote:For anyone interested in the reasons why:-

http://web.webhost4life.com/innerclock/ ... ge&name=35

Midi Clock or MTC In or Out from your DAW will be a rough ride. Take it as fact. Firewire or USB. Doesn't matter. There are loads of reasons. If it bothers you or you not it still makes a difference to how things sound.

At least if you have your hardware as master - something in your rig will be keeping time. With the DAW running your rig via USB/Midi Firewire the whole show gets the wobbly knee syndrome.

We are a few weeks off production of a solution.

Sample and tempo accurate Midi Clock from any DAW. And it does simultaneous Din Sync and Trigger Outs for your TR-808s/303s and Step Sequencers too.

We've been continually testing MPC-3000s running Mansell Labs Vailixi 3.50OS on our lab prototype and getting maximum 2 samples variation off perfect timing which is the limit of the MPC stability and testing anyway.

Our sync conversion between DAW and Hardware is less than 20 microseconds firm.

Apart from sounding truly amazing - having your external hardware and DAW locked properly means you can record/overdub and have everything line up properly in the grid.

Less editing to make up for tight beats ruined by a rough clock on the way in.

Bliss. Shipping Mid October.

http://web.webhost4life.com/innerclock/ ... ge&name=16

best - David
http://www.innerclocksystems.com

WoW !!!

Helluva post - especially with all the mis-information out there (some in this thread)

Now I know fa sho , wut I always felt in my gut:

MPC Timing > CPU timing

We always publish the the numbers when we release product.

Have a look at the testimonials on our home page - these are for our Sync-Shift MKII mainly but it shows the degree to which customers are happy with our gear.

There is a VST/AU Plug-In supplied with the Sync-Lock.

It runs on any DAW Host and provides sample accurate sync pulses to the Sync-Lock.

The Sync-Lock converts pulses to Midi Clock/Din and Trigs in under 20 microseconds.

From this you get grid/tempo/sample accurate sync from your DAW.

No question.

We're busy putting final touches to packaging and Plug-In graphics this week.

Check with Analogue Haven in the US or Schneiders in Europe for stock availability.

Our predicted RRP at this stage is $395 USD and that gets you:-

Sync-Lock
Universal Power Supply
Y-Adapter for Footswitch/Trigger Output
Sync-Gen Plug-In Software Installer CDRom
Owners Manual

Best - David
http://www.innerclocksystems.com

it also has DIN/Synch -- nice.

I've never had any issues. I sync via MTC with the MPC slaved to PT LE!

MTC stability is no better than Midi Clock - it all depends on the device and driver generating the Midi Data from the Application.

Just because Time Code is meant to be linear - she can still be a rubber band if the source has poor performance and this is indeed the case for many midi sync devices.

All MPCs can follow MTC quite well although in testing all sync input methods on a tricked up Vailixi MPC-3000 a few years back with very reliable sync sources - MTC/Midi Clock/FSK/Pulse 96 and Quarter Notes - in terms of slave stability - Midi Clock came out the clear winner.

That being said - feed an MPC rough Midi anything and she is going to suffer.

If you have time and feel like doing the litmus test - I'd love to hear your results - doesn't take long.

BTW, what Midi Interface are you using?

Best regards - David
www.innerclocksystems.com

Some nice news:-

http://www.youtube.com/watch?v=b3ULMpaBpeo

http://web.webhost4life.com/innerclock/ ... ge&name=16

Best regards - David
www.innerclocksystems.com

+1 for my HD3 and Big Ben

+1 for my LE setup at home within just a few samples no matter my track count
(Granted, I will slip a bit if I record back into a heavily processed session as say 512+ buffer, but this rarely happens, I don't use LE much, it's my toy in the home studio, the setup in my sig)

Internal clocks (Via DAW) are known to fluctuate.... it's obvious..... a dedicated clock is always the best solution.

However, a dproperly configured machine will clock very accurately under some pretty intense load, given the OS and DAW are configured properly.

I have a dualcore machine at home hittin DVERB tests that many peoples Quads are seeing... All in config. Not just software, but hardware as well.

It's like an engine, you can't just slap any old carb and intake, or Cam, on any old heads or valves or bore. You've gotta blue-print things.

A hugely overlooked one is the chipset. People tend to ignore this. That's where I start. North and South / MOBO. Then CPU, then RAM.... and so on. Then minimize the OS install, optimize the OS config, optimize/config the DAW.... off you go.

My newest build is in progress now, I've built two others of the basis of this machine for friends, an Asus P5Q, with Quad Intel, still trying to decide on CPU..... But I am building with SSD's on this one which should show me marked improvements..... I chose the P5Q Based on the VERY SPECIFIC Chipset revisions introduced on this exact P5Q model, and the PCI/PCIe configurations of the slots being able to accept up to a PT HD3 internally, which is what I am currently running in my studio dual, but will have the option of expanding beyond the PCI into PCIe if the time comes that I choose to do so. I am betting that with this machine..... when it's done, I will likely get VERY CLOSE results from clocking internally, or from my Big Ben. Especially running the HD3, but I will likely test it with LE as well to see how it handles the processing load.

Any independent info out there for the internal clock BLACK LION AUDIO puts in their signature series mods?