Yahoo Groups archive

Analogue-sequencer

Index last updated: 2026-04-28 23:15 UTC

Message

Re: [analogue-sequencer] Re: syncing with cubase

2009-10-22 by sean zoega

Herman, many thanks for getting in touch...I still have a final few 
tests to do but I am tending towards agreeing with you. I have just made 
sure that everything is running the latest drivers etc. and I am running 
a very simple test set-up but at the moment MIDI clock is just totally 
unstable and unusable. I have been doing some tests and if I have the P3 
and Cubase synced up and just press the "loop" button or turn on a track 
with the P3 the sync. is gone.

This raises an interesting issue;
   do I just abandon DAW's and go the hardware sequencer route
   or find a way to sync. Logic/Cubase to P3

On the hardware route, what are you using Herman...how do you record 
vocals/guitar?
At the moment I really like some of the sequenced synths within Reaktor 
and love the FM8 sequencer and If the problem is with the PC/MAC then 
swapping to Logic isnt going to solve anything.....so how do I do this? 
Does anybody know of a device that I could use as a studio Master Clock 
that outputs wordclock or SMPTE to Cubase/Logic whilst simultaneously 
sending out a solid MIDI clock? This seems to be the only solution if 
you want to actually embrace any of the computer audio developments of 
the last twenty years and still use a P3.

or does anybody make a device that solids up the MIDI clock...this seems 
like a reasonably simple thing to do...it just averages out the tempo of 
last second of MIDI clock and outputs this as nice solid MIDI 
clock...you would lose the ability to change tempo, but this would be a 
small price to pay to actually to be able to sync the devices together 
and actually play in tempo (the number 1 requirement of music)

sean (frustrated of Chorlton)

Herman Dackenberg wrote:
>  
>
> Hi Sean,
> I don't even have a P3 (waiting eagerly for the Cirklon), but 
> unfortunately
> I must say that MIDI in my experience, MIDI from PC's and Mac's are 
> not that
> tight. This also goes for MIDI-clock. I've been incredibly frustrated by
> this for over 10 years, and decided to go with hardware sequencers and
> Atari. Anyway, my experience with MIDI clock from PC's is that it's simply
> not good enough - too much jitter. Of course some hardware configurations
> are better than others, but the problem still persists.
>
> Best regards,
> Herman Dackenberg
>
> On Thu, Oct 22, 2009 at 4:09 PM, sean zoega <sean@zoega.co.uk 
> <mailto:sean%40zoega.co.uk>> wrote:
>
> >
> >
> > Thanks Colin, I now have MIDI-0x on my PC...just ordered a USB>MIDI
> > cable so I can get the MIDI clock into the PC. I'll keep you posted.
> > Thanks for the info on MTC, sounds like everybody is getting on just
> > fine with MIDI clock apart from me...so I'm hoping that I can track down
> > the problem soon..and get back to making noises
> >
> > cheers
> > sean
> >
> > Colin f wrote:
> > >
> > >
> > >
> > > > Thanks Colin...I will investigate. I have lodged a question
> > > > with Steinberg as I cant see any mentions of problems on any
> > > > notice boards.
> > > > Also I'll do the simple stuff like buying a higher quality
> > > > shorter MIDI lead.
> > >
> > > The sure way to see what's going in, if you can beg, borrow or steal
> > > another
> > > laptop, would be to pass the MIDI from Cubase to the P3 through 
> something
> > > like MIDI-Ox, so you can see exactly when MIDI clock bytes are being
> > sent.
> > > That should clear up very quickly whether there are any missing bytes,
> > > clock
> > > bytes bunched tightly together, or a.n.other problem.
> > >
> > > > Can I ask a more general question..you
> > > > mention new modes of working with MIDI clock with Cirklon but
> > > > from my investigations MTC would seem to be the preferred
> > > > method of syncing equipment...is there a reason why you are
> > > > not going this route?
> > >
> > > The new timing mechanism in Cirklon is going to allow support for MTC,
> > > but I
> > > still prefer MIDI clock.
> > > MTC is a linear timecode. It doesn't carry any information about tempo
> > but
> > > rather provides an absolute timing reference, which a slaved device
> > > can then
> > > use to generate a pre-defined tempo clock.
> > > This is primarily aimed at syncing devices where the tempo of a 
> project
> > is
> > > fixed in advance, either at a single value, or at a series of values
> > > defined
> > > in a tempo map - essential if you're composing to a film or video 
> source.
> > > And it doesn't make much difference if you are locking MIDI tracks to
> > > recorded audio tracks where the tempo is essentially fixed anyway.
> > > I prefer to use MIDI clock, as I always set the tempo by feel, and
> > > wouldn't
> > > like to have a track tied to a certain tempo from the outset.
> > >
> > > Best regards,
> > > Colin Fraser
> > > Sequentix Music Systems Ltd
> > > http://www.sequentix.com <http://www.sequentix.com> 
> <http://www.sequentix.com <http://www.sequentix.com>>
> > >
> > >
> >
> >
> >
>
> [Non-text portions of this message have been removed]
>
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.