|
|
|
|
|
|
|
|
|
|
| Re: Disk Clone: aftermath [message #73434 is a reply to message #73432] |
Sun, 01 October 2006 19:18  |
JCampbell
 Messages: 18 Registered: September 2006
|
Junior Member |
|
|
and then set the SX tracks on mono
output
> > busses to stream the tracks back over lightpipe to Paris for further
> > processing, panning and summing, then the system is very stable. It
takes 30
> > minutes to an hour per song (24 tracks average) to get this going. It's
> > almost second nature to me now actually, but I'd like to avoid having to
> > jump through the initial hoops of rendering, batch conversion in WL and
> > importing into Cubase. With my Paris tracking template set up with the
EDS
> > external inserts and the Sampleslide native insert ready to go and
bypassed
> > until mix time, I could just enable the inserts, highlight all Paris
tracks
> > and nudge them 10 + 1, click on my mix patchbay setup in Paris, open
Forte
> > to the default rack processor template and I'm mixing a 40 track project
in
> > 5 minutes with delay compensated UAD-1 plugins and external hardware on
> > inserts and auxes in Paris.
> >
> > Deej
> >
> >
> > "Don Nafe" <dnafe@magma.ca> wrote in message news:453152c8$1@linux...
> >> hence the need for such a large I/O interface?
> >>
> >> Don
> >>
> >> "DJ" <notachance@net.net> wrote in message news:45314e37@linux...
> >>> Dave,
> >>>
> >>> All tracks are being played back through Paris. The point of this is
to
> >>> have
> >>> all tracks crossing the editor timeline simultaneously whether they
are
> >>> being processed by a plugin, or not. In order to achieve this, each
> > track
> >>> has to be sent to a Forte bus, processed by the UAD-1 Delaycomp (and
> >>> whatever else) then returned to Paris. the "nudge" and then the
> >>> Sampleslide
> >>> instance in Paris is in order to cover the latency between the two
> >>> computers
> >>> caused by the 512k buffer settings of the audio interface on the
native
> >>> platforn. without this, there will be flamming of all tracks (I have
> >>> tested
> >>> it). Another solution would be to process only certain tracks through
> >>> Forte
> >>> and leave others to play back in Paris. this is possible to do, but
then
> >>> you
> >>> get into nudging "all" tracks in Paris that are *not* being processed
in
> >>> Forte by a measured increment which would be the total latency of 5 x
> >>> UAD-1
> >>> plugins plus the 512K sample buffer. I haven't yet measured it, but
I'm
> >>> going to do so today. I'm thinking this may be well over the latency
> >>> threshold that would allow a visual reference to the Paris timeline
> > while
> >>> mixing, plus, those tracks that are being processed in Forte would be
> >>> nudged
> >>> a different number of samples from the ones that weren't. This creates
|
|
|
|