Home » The PARIS Forums » PARIS: Main » More info on using Cubase SX as a standalone FX processor
|
|
| Re: More info on using Cubase SX as a standalone FX processor [message #73562 is a reply to message #73561] |
Wed, 04 October 2006 12:38   |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Further repeated testing has verified that when Paris ADAT sync output is
hooked directly up to the RME audio interface ADAT sync input, if ASIO
positioning protocall is selected as the Cubase sync sounce, even if the RME
transport is set to internal so that the Cubase transport is not chasing the
Paris timeline, Cubase will crash within 5 seconds of the beginning of an
audio track from Submix 2/card B/MEC 2 starting to play.
Setting sync source in Cubase SX to MTC (with no midi interface selected) so
that there is no interfacing between the Paris ADAT module and Cubase SX
works fine......no crashes of cubase SX when processing tracks from multiple
submixes in Paris.
Thanks for you input on this Dave. Hopefully the Datasync II will do the
trick.
Deej
"DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> OK,
>
> Before you guys start getting too exicted about this, it appears that
there
> is one more hoop to jump through if you are using multiple MECs. When
> looping audio from Paris *through* Cubase SX channels while Cubase SX is
> slaved to Paris ADAT sync, Cubase crashes once audio is being looped from
> two different MECs. This is likely due to the latency between EDS cards
> causing a trainwreck with the clocking.
> This will not be an issue to those who are not wanting to have plugin
> automation in SX. As long as SX is not slaving to the Paris timeline, the
> audio passes through the audio interface on Cubase and back to Paris with
no
> problem. If, however, you want to automate plugin parameters, you will
need
> both machines timeline synced so that you can write automation data to
> Cubase SX.
>
> I am hoping to solve this problem by sending Paris ADAT sync to a JL
Cooper
> Datasync II unit which converts ADAT timecode to MTC and then slaving
Cubase
> SX to incoming MTC form the Datasync II.
>
> Thank goodness for yet another kludge. I thought I had finally succeeded
in
> accomplishing everything I started out to do and there was this sudden
> realization that my life would have no further purpose.
>
> ;o)
>
>
|
|
|
|
| UH OH!!......not good! [message #73563 is a reply to message #73562] |
Wed, 04 October 2006 12:47 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
The Cubase rig just crashed while not receiving any sync info at all between
Paris and Cubase. Not good. I've got another trick up my sleeve. Stay tuned.
"DJ" <notachance@net.net> wrote in message news:45240db7@linux...
> Further repeated testing has verified that when Paris ADAT sync output is
> hooked directly up to the RME audio interface ADAT sync input, if ASIO
> positioning protocall is selected as the Cubase sync sounce, even if the
RME
> transport is set to internal so that the Cubase transport is not chasing
the
> Paris timeline, Cubase will crash within 5 seconds of the beginning of an
> audio track from Submix 2/card B/MEC 2 starting to play.
>
> Setting sync source in Cubase SX to MTC (with no midi interface selected)
so
> that there is no interfacing between the Paris ADAT module and Cubase SX
> works fine......no crashes of cubase SX when processing tracks from
multiple
> submixes in Paris.
>
> Thanks for you input on this Dave. Hopefully the Datasync II will do the
> trick.
>
> Deej
>
>
>
> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> > OK,
> >
> > Before you guys start getting too exicted about this, it appears that
> there
> > is one more hoop to jump through if you are using multiple MECs. When
> > looping audio from Paris *through* Cubase SX channels while Cubase SX is
> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
from
> > two different MECs. This is likely due to the latency between EDS cards
> > causing a trainwreck with the clocking.
> > This will not be an issue to those who are not wanting to have plugin
> > automation in SX. As long as SX is not slaving to the Paris timeline,
the
> > audio passes through the audio interface on Cubase and back to Paris
with
> no
> > problem. If, however, you want to automate plugin parameters, you will
> need
> > both machines timeline synced so that you can write automation data to
> > Cubase SX.
> >
> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
> Cooper
> > Datasync II unit which converts ADAT timecode to MTC and then slaving
> Cubase
> > SX to incoming MTC form the Datasync II.
> >
> > Thank goodness for yet another kludge. I thought I had finally succeeded
> in
> > accomplishing everything I started out to do and there was this sudden
> > realization that my life would have no further purpose.
> >
> > ;o)
> >
> >
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73565 is a reply to message #73563] |
Wed, 04 October 2006 13:43 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Hmmm......this just may not be possible to achieve. I've got both systems
clocked to the Lucid....No ADAT sync is interfaced with the RME cards. The
jury is still out on whether or not this is going to fly. The latency
between EDS cards and the audio being streamed from ADAT modules that are
clocked to those cards may be an insurmountable issue here.
Deej
"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
> The Cubase rig just crashed while not receiving any sync info at all
between
> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
tuned.
>
>
> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
> > Further repeated testing has verified that when Paris ADAT sync output
is
> > hooked directly up to the RME audio interface ADAT sync input, if ASIO
> > positioning protocall is selected as the Cubase sync sounce, even if the
> RME
> > transport is set to internal so that the Cubase transport is not chasing
> the
> > Paris timeline, Cubase will crash within 5 seconds of the beginning of
an
> > audio track from Submix 2/card B/MEC 2 starting to play.
> >
> > Setting sync source in Cubase SX to MTC (with no midi interface
selected)
> so
> > that there is no interfacing between the Paris ADAT module and Cubase SX
> > works fine......no crashes of cubase SX when processing tracks from
> multiple
> > submixes in Paris.
> >
> > Thanks for you input on this Dave. Hopefully the Datasync II will do the
> > trick.
> >
> > Deej
> >
> >
> >
> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> > > OK,
> > >
> > > Before you guys start getting too exicted about this, it appears that
> > there
> > > is one more hoop to jump through if you are using multiple MECs. When
> > > looping audio from Paris *through* Cubase SX channels while Cubase SX
is
> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
> from
> > > two different MECs. This is likely due to the latency between EDS
cards
> > > causing a trainwreck with the clocking.
> > > This will not be an issue to those who are not wanting to have plugin
> > > automation in SX. As long as SX is not slaving to the Paris timeline,
> the
> > > audio passes through the audio interface on Cubase and back to Paris
> with
> > no
> > > problem. If, however, you want to automate plugin parameters, you will
> > need
> > > both machines timeline synced so that you can write automation data to
> > > Cubase SX.
> > >
> > > I am hoping to solve this problem by sending Paris ADAT sync to a JL
> > Cooper
> > > Datasync II unit which converts ADAT timecode to MTC and then slaving
> > Cubase
> > > SX to incoming MTC form the Datasync II.
> > >
> > > Thank goodness for yet another kludge. I thought I had finally
succeeded
> > in
> > > accomplishing everything I started out to do and there was this sudden
> > > realization that my life would have no further purpose.
> > >
> > > ;o)
> > >
> > >
> >
> >
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73567 is a reply to message #73565] |
Wed, 04 October 2006 14:44 |
Don Nafe
Messages: 1206
Registered: July 2005
|
Senior Member |
|
|
looks like it's time to set up a third computer with a basic music app..that
can send a start/stop signal to an external clock module which all your
goodies can then sync to
or not
Don
"DJ" <notachance@net.net> wrote in message news:45241cfe$1@linux...
> Hmmm......this just may not be possible to achieve. I've got both systems
> clocked to the Lucid....No ADAT sync is interfaced with the RME cards. The
> jury is still out on whether or not this is going to fly. The latency
> between EDS cards and the audio being streamed from ADAT modules that are
> clocked to those cards may be an insurmountable issue here.
> Deej
>
> "DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>> The Cubase rig just crashed while not receiving any sync info at all
> between
>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
> tuned.
>>
>>
>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>> > Further repeated testing has verified that when Paris ADAT sync output
> is
>> > hooked directly up to the RME audio interface ADAT sync input, if ASIO
>> > positioning protocall is selected as the Cubase sync sounce, even if
>> > the
>> RME
>> > transport is set to internal so that the Cubase transport is not
>> > chasing
>> the
>> > Paris timeline, Cubase will crash within 5 seconds of the beginning of
> an
>> > audio track from Submix 2/card B/MEC 2 starting to play.
>> >
>> > Setting sync source in Cubase SX to MTC (with no midi interface
> selected)
>> so
>> > that there is no interfacing between the Paris ADAT module and Cubase
>> > SX
>> > works fine......no crashes of cubase SX when processing tracks from
>> multiple
>> > submixes in Paris.
>> >
>> > Thanks for you input on this Dave. Hopefully the Datasync II will do
>> > the
>> > trick.
>> >
>> > Deej
>> >
>> >
>> >
>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> > > OK,
>> > >
>> > > Before you guys start getting too exicted about this, it appears that
>> > there
>> > > is one more hoop to jump through if you are using multiple MECs. When
>> > > looping audio from Paris *through* Cubase SX channels while Cubase SX
> is
>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>> from
>> > > two different MECs. This is likely due to the latency between EDS
> cards
>> > > causing a trainwreck with the clocking.
>> > > This will not be an issue to those who are not wanting to have plugin
>> > > automation in SX. As long as SX is not slaving to the Paris timeline,
>> the
>> > > audio passes through the audio interface on Cubase and back to Paris
>> with
>> > no
>> > > problem. If, however, you want to automate plugin parameters, you
>> > > will
>> > need
>> > > both machines timeline synced so that you can write automation data
>> > > to
>> > > Cubase SX.
>> > >
>> > > I am hoping to solve this problem by sending Paris ADAT sync to a JL
>> > Cooper
>> > > Datasync II unit which converts ADAT timecode to MTC and then slaving
>> > Cubase
>> > > SX to incoming MTC form the Datasync II.
>> > >
>> > > Thank goodness for yet another kludge. I thought I had finally
> succeeded
>> > in
>> > > accomplishing everything I started out to do and there was this
>> > > sudden
>> > > realization that my life would have no further purpose.
>> > >
>> > > ;o)
>> > >
>> > >
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73568 is a reply to message #73565] |
Wed, 04 October 2006 14:50 |
Nappy
Messages: 198
Registered: September 2006
|
Senior Member |
|
|
DJ'
I'm starting to think it may be time for you to make the jump to a Dualcore
intel box and
2 UAD PCI-e cards running Cubase 4. I know you have invested alot of time
and
brain power into this,lord knows I'm exhausted just reading it. I think you
would be
better using PARIS as a summing buss. At least thats what I'm coming to believe.
I'm going to use my old B&W G3 for my PARIS system and build a Dualcore Intel
box and run Cubase 4 and be done with it.
respect
Nappy
"DJ" <notachance@net.net> wrote:
>Hmmm......this just may not be possible to achieve. I've got both systems
>clocked to the Lucid....No ADAT sync is interfaced with the RME cards. The
>jury is still out on whether or not this is going to fly. The latency
>between EDS cards and the audio being streamed from ADAT modules that are
>clocked to those cards may be an insurmountable issue here.
>Deej
>
>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>> The Cubase rig just crashed while not receiving any sync info at all
>between
>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>tuned.
>>
>>
>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>> > Further repeated testing has verified that when Paris ADAT sync output
>is
>> > hooked directly up to the RME audio interface ADAT sync input, if ASIO
>> > positioning protocall is selected as the Cubase sync sounce, even if
the
>> RME
>> > transport is set to internal so that the Cubase transport is not chasing
>> the
>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
of
>an
>> > audio track from Submix 2/card B/MEC 2 starting to play.
>> >
>> > Setting sync source in Cubase SX to MTC (with no midi interface
>selected)
>> so
>> > that there is no interfacing between the Paris ADAT module and Cubase
SX
>> > works fine......no crashes of cubase SX when processing tracks from
>> multiple
>> > submixes in Paris.
>> >
>> > Thanks for you input on this Dave. Hopefully the Datasync II will do
the
>> > trick.
>> >
>> > Deej
>> >
>> >
>> >
>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> > > OK,
>> > >
>> > > Before you guys start getting too exicted about this, it appears that
>> > there
>> > > is one more hoop to jump through if you are using multiple MECs. When
>> > > looping audio from Paris *through* Cubase SX channels while Cubase
SX
>is
>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>> from
>> > > two different MECs. This is likely due to the latency between EDS
>cards
>> > > causing a trainwreck with the clocking.
>> > > This will not be an issue to those who are not wanting to have plugin
>> > > automation in SX. As long as SX is not slaving to the Paris timeline,
>> the
>> > > audio passes through the audio interface on Cubase and back to Paris
>> with
>> > no
>> > > problem. If, however, you want to automate plugin parameters, you
will
>> > need
>> > > both machines timeline synced so that you can write automation data
to
>> > > Cubase SX.
>> > >
>> > > I am hoping to solve this problem by sending Paris ADAT sync to a
JL
>> > Cooper
>> > > Datasync II unit which converts ADAT timecode to MTC and then slaving
>> > Cubase
>> > > SX to incoming MTC form the Datasync II.
>> > >
>> > > Thank goodness for yet another kludge. I thought I had finally
>succeeded
>> > in
>> > > accomplishing everything I started out to do and there was this sudden
>> > > realization that my life would have no further purpose.
>> > >
>> > > ;o)
>> > >
>> > >
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73572 is a reply to message #73567] |
Wed, 04 October 2006 18:04 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
I'm still lookng into this. There are some things about it that aren't
adding up. It seems that the problem must be when a digital signal is sent
out the RE ADAT output to be returned to Paris after processing on an
individual channel, though Paris isn't the app that is crashing. If I just
stream audio from Cubase SX to Paris and sum it there with Paris in Live Mix
mode......including send effects, no crashing. It's when the audio is looped
*through* across EDS cards with Paris in *always monitro input mode that
Cubase crashes.......even when both machines are only WC synced with SX
receiving no positioning info and not chasing Paris. I'm going to try the
Datasync solution, but I doubt if it will cure this issue. I may have hit an
insurmountable barrier here.......the sample latency between EDS
cards/submixes seems to be the culprit. I have also tried it without any
external hardware boxes being attached to the RME cards in the SX DAW. Makes
no difference. Oh well, I can live with the scenario I was using before but
it doesn't sound quite as good as what I am trying to do with using SX
solely as an FX processor.
"Don Nafe" <dnafe@magma.ca> wrote in message news:45242948$1@linux...
> looks like it's time to set up a third computer with a basic music
app..that
> can send a start/stop signal to an external clock module which all your
> goodies can then sync to
>
>
> or not
>
> Don
>
>
> "DJ" <notachance@net.net> wrote in message news:45241cfe$1@linux...
> > Hmmm......this just may not be possible to achieve. I've got both
systems
> > clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
The
> > jury is still out on whether or not this is going to fly. The latency
> > between EDS cards and the audio being streamed from ADAT modules that
are
> > clocked to those cards may be an insurmountable issue here.
> > Deej
> >
> > "DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
> >> The Cubase rig just crashed while not receiving any sync info at all
> > between
> >> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
> > tuned.
> >>
> >>
> >> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
> >> > Further repeated testing has verified that when Paris ADAT sync
output
> > is
> >> > hooked directly up to the RME audio interface ADAT sync input, if
ASIO
> >> > positioning protocall is selected as the Cubase sync sounce, even if
> >> > the
> >> RME
> >> > transport is set to internal so that the Cubase transport is not
> >> > chasing
> >> the
> >> > Paris timeline, Cubase will crash within 5 seconds of the beginning
of
> > an
> >> > audio track from Submix 2/card B/MEC 2 starting to play.
> >> >
> >> > Setting sync source in Cubase SX to MTC (with no midi interface
> > selected)
> >> so
> >> > that there is no interfacing between the Paris ADAT module and Cubase
> >> > SX
> >> > works fine......no crashes of cubase SX when processing tracks from
> >> multiple
> >> > submixes in Paris.
> >> >
> >> > Thanks for you input on this Dave. Hopefully the Datasync II will do
> >> > the
> >> > trick.
> >> >
> >> > Deej
> >> >
> >> >
> >> >
> >> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >> > > OK,
> >> > >
> >> > > Before you guys start getting too exicted about this, it appears
that
> >> > there
> >> > > is one more hoop to jump through if you are using multiple MECs.
When
> >> > > looping audio from Paris *through* Cubase SX channels while Cubase
SX
> > is
> >> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
looped
> >> from
> >> > > two different MECs. This is likely due to the latency between EDS
> > cards
> >> > > causing a trainwreck with the clocking.
> >> > > This will not be an issue to those who are not wanting to have
plugin
> >> > > automation in SX. As long as SX is not slaving to the Paris
timeline,
> >> the
> >> > > audio passes through the audio interface on Cubase and back to
Paris
> >> with
> >> > no
> >> > > problem. If, however, you want to automate plugin parameters, you
> >> > > will
> >> > need
> >> > > both machines timeline synced so that you can write automation data
> >> > > to
> >> > > Cubase SX.
> >> > >
> >> > > I am hoping to solve this problem by sending Paris ADAT sync to a
JL
> >> > Cooper
> >> > > Datasync II unit which converts ADAT timecode to MTC and then
slaving
> >> > Cubase
> >> > > SX to incoming MTC form the Datasync II.
> >> > >
> >> > > Thank goodness for yet another kludge. I thought I had finally
> > succeeded
> >> > in
> >> > > accomplishing everything I started out to do and there was this
> >> > > sudden
> >> > > realization that my life would have no further purpose.
> >> > >
> >> > > ;o)
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
> >
>
>
|
|
|
|
|
|
| AHhhh.........HA!!! [message #73583 is a reply to message #73575] |
Wed, 04 October 2006 21:44 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
I wonder if this isn't working because some of the UAD-1 plugins (like the
Neve EQ for instance) are upsampling what is essentially a Paris audio file
being played *through* SX with none of the downsampling possible that would
normally be part of the DSP process in SX to resolve the sample rate of the
plugin to the project sample rate/clock source. If so, that would certainly
explain some things. It might also explain why the UAD-1 card with ADAT I/O
that was on the boards a few years ago went nowhere and why the POCO,
Duende, etc. do not have digital I/O and only work in a plugin format. If
these processors were
upsampling/downsampling in real time, the SR converters/clocking shenanigans
that would be necessary to bring the audio signal back to the project sample
rate would put the pricepoint through the roof.
Well.....it's just a thought........
;O)
Deej
"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
> Well.........I'm baffled by this and I'm just going to let it slide for a
> while. Looping audio *through* SX so that it functions as a standalone FX
> processor has been a total bust so far. OTOH, streaming tracks directly
from
> SX (lots of them) to Paris and summing there does not create the clocking
> trainwreck that looping through the inserts does. I guess it must be the
> loop that is causing it as opposed to the one way trip.
>
> C'est la ****'in vie
>
> ;o)
>
> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> > OK,
> >
> > Before you guys start getting too exicted about this, it appears that
> there
> > is one more hoop to jump through if you are using multiple MECs. When
> > looping audio from Paris *through* Cubase SX channels while Cubase SX is
> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
from
> > two different MECs. This is likely due to the latency between EDS cards
> > causing a trainwreck with the clocking.
> > This will not be an issue to those who are not wanting to have plugin
> > automation in SX. As long as SX is not slaving to the Paris timeline,
the
> > audio passes through the audio interface on Cubase and back to Paris
with
> no
> > problem. If, however, you want to automate plugin parameters, you will
> need
> > both machines timeline synced so that you can write automation data to
> > Cubase SX.
> >
> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
> Cooper
> > Datasync II unit which converts ADAT timecode to MTC and then slaving
> Cubase
> > SX to incoming MTC form the Datasync II.
> >
> > Thank goodness for yet another kludge. I thought I had finally succeeded
> in
> > accomplishing everything I started out to do and there was this sudden
> > realization that my life would have no further purpose.
> >
> > ;o)
> >
> >
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73588 is a reply to message #73572] |
Thu, 05 October 2006 00:26 |
Martin Harrington
Messages: 560
Registered: September 2005
|
Senior Member |
|
|
No wonder you're almost "hairless" Deej...you need to start winding
down...relax a little and stop re-inventing the wheel.
Use Paris as it's meant to be, or use Cubase, (or whatever), and get all the
goodies.
Why not just master in Paris??
How's Amy...you do remember her, don't you?
8>P
many regards
--
Martin Harrington
www.lendanear-sound.com
"DJ" <notachance@net.net> wrote in message news:45245a1a$1@linux...
> I'm still lookng into this. There are some things about it that aren't
> adding up. It seems that the problem must be when a digital signal is sent
> out the RE ADAT output to be returned to Paris after processing on an
> individual channel, though Paris isn't the app that is crashing. If I just
> stream audio from Cubase SX to Paris and sum it there with Paris in Live
> Mix
> mode......including send effects, no crashing. It's when the audio is
> looped
> *through* across EDS cards with Paris in *always monitro input mode that
> Cubase crashes.......even when both machines are only WC synced with SX
> receiving no positioning info and not chasing Paris. I'm going to try the
> Datasync solution, but I doubt if it will cure this issue. I may have hit
> an
> insurmountable barrier here.......the sample latency between EDS
> cards/submixes seems to be the culprit. I have also tried it without any
> external hardware boxes being attached to the RME cards in the SX DAW.
> Makes
> no difference. Oh well, I can live with the scenario I was using before
> but
> it doesn't sound quite as good as what I am trying to do with using SX
> solely as an FX processor.
>
>
> "Don Nafe" <dnafe@magma.ca> wrote in message news:45242948$1@linux...
>> looks like it's time to set up a third computer with a basic music
> app..that
>> can send a start/stop signal to an external clock module which all your
>> goodies can then sync to
>>
>>
>> or not
>>
>> Don
>>
>>
>> "DJ" <notachance@net.net> wrote in message news:45241cfe$1@linux...
>> > Hmmm......this just may not be possible to achieve. I've got both
> systems
>> > clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
> The
>> > jury is still out on whether or not this is going to fly. The latency
>> > between EDS cards and the audio being streamed from ADAT modules that
> are
>> > clocked to those cards may be an insurmountable issue here.
>> > Deej
>> >
>> > "DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>> >> The Cubase rig just crashed while not receiving any sync info at all
>> > between
>> >> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>> > tuned.
>> >>
>> >>
>> >> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>> >> > Further repeated testing has verified that when Paris ADAT sync
> output
>> > is
>> >> > hooked directly up to the RME audio interface ADAT sync input, if
> ASIO
>> >> > positioning protocall is selected as the Cubase sync sounce, even if
>> >> > the
>> >> RME
>> >> > transport is set to internal so that the Cubase transport is not
>> >> > chasing
>> >> the
>> >> > Paris timeline, Cubase will crash within 5 seconds of the beginning
> of
>> > an
>> >> > audio track from Submix 2/card B/MEC 2 starting to play.
>> >> >
>> >> > Setting sync source in Cubase SX to MTC (with no midi interface
>> > selected)
>> >> so
>> >> > that there is no interfacing between the Paris ADAT module and
>> >> > Cubase
>> >> > SX
>> >> > works fine......no crashes of cubase SX when processing tracks from
>> >> multiple
>> >> > submixes in Paris.
>> >> >
>> >> > Thanks for you input on this Dave. Hopefully the Datasync II will do
>> >> > the
>> >> > trick.
>> >> >
>> >> > Deej
>> >> >
>> >> >
>> >> >
>> >> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> >> > > OK,
>> >> > >
>> >> > > Before you guys start getting too exicted about this, it appears
> that
>> >> > there
>> >> > > is one more hoop to jump through if you are using multiple MECs.
> When
>> >> > > looping audio from Paris *through* Cubase SX channels while Cubase
> SX
>> > is
>> >> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
> looped
>> >> from
>> >> > > two different MECs. This is likely due to the latency between EDS
>> > cards
>> >> > > causing a trainwreck with the clocking.
>> >> > > This will not be an issue to those who are not wanting to have
> plugin
>> >> > > automation in SX. As long as SX is not slaving to the Paris
> timeline,
>> >> the
>> >> > > audio passes through the audio interface on Cubase and back to
> Paris
>> >> with
>> >> > no
>> >> > > problem. If, however, you want to automate plugin parameters, you
>> >> > > will
>> >> > need
>> >> > > both machines timeline synced so that you can write automation
>> >> > > data
>> >> > > to
>> >> > > Cubase SX.
>> >> > >
>> >> > > I am hoping to solve this problem by sending Paris ADAT sync to a
> JL
>> >> > Cooper
>> >> > > Datasync II unit which converts ADAT timecode to MTC and then
> slaving
>> >> > Cubase
>> >> > > SX to incoming MTC form the Datasync II.
>> >> > >
>> >> > > Thank goodness for yet another kludge. I thought I had finally
>> > succeeded
>> >> > in
>> >> > > accomplishing everything I started out to do and there was this
>> >> > > sudden
>> >> > > realization that my life would have no further purpose.
>> >> > >
>> >> > > ;o)
>> >> > >
>> >> > >
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73589 is a reply to message #73568] |
Thu, 05 October 2006 00:29 |
Martin Harrington
Messages: 560
Registered: September 2005
|
Senior Member |
|
|
Huh, that's funny, I didn't read Nappy's post until I sent the previous
one...
It's not only me that's looking after you health
--
Martin Harrington
www.lendanear-sound.com
"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>
> DJ'
> I'm starting to think it may be time for you to make the jump to a
> Dualcore
> intel box and
> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of time
> and
> brain power into this,lord knows I'm exhausted just reading it. I think
> you
> would be
> better using PARIS as a summing buss. At least thats what I'm coming to
> believe.
> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
> Intel
> box and run Cubase 4 and be done with it.
>
> respect
> Nappy
> "DJ" <notachance@net.net> wrote:
>>Hmmm......this just may not be possible to achieve. I've got both systems
>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards. The
>>jury is still out on whether or not this is going to fly. The latency
>>between EDS cards and the audio being streamed from ADAT modules that are
>>clocked to those cards may be an insurmountable issue here.
>>Deej
>>
>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>> The Cubase rig just crashed while not receiving any sync info at all
>>between
>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>tuned.
>>>
>>>
>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>> > Further repeated testing has verified that when Paris ADAT sync output
>>is
>>> > hooked directly up to the RME audio interface ADAT sync input, if
>>> > ASIO
>>> > positioning protocall is selected as the Cubase sync sounce, even if
> the
>>> RME
>>> > transport is set to internal so that the Cubase transport is not
>>> > chasing
>>> the
>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
> of
>>an
>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>> >
>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>selected)
>>> so
>>> > that there is no interfacing between the Paris ADAT module and Cubase
> SX
>>> > works fine......no crashes of cubase SX when processing tracks from
>>> multiple
>>> > submixes in Paris.
>>> >
>>> > Thanks for you input on this Dave. Hopefully the Datasync II will do
> the
>>> > trick.
>>> >
>>> > Deej
>>> >
>>> >
>>> >
>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>> > > OK,
>>> > >
>>> > > Before you guys start getting too exicted about this, it appears
>>> > > that
>>> > there
>>> > > is one more hoop to jump through if you are using multiple MECs.
>>> > > When
>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
> SX
>>is
>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>>> from
>>> > > two different MECs. This is likely due to the latency between EDS
>>cards
>>> > > causing a trainwreck with the clocking.
>>> > > This will not be an issue to those who are not wanting to have
>>> > > plugin
>>> > > automation in SX. As long as SX is not slaving to the Paris
>>> > > timeline,
>>> the
>>> > > audio passes through the audio interface on Cubase and back to Paris
>>> with
>>> > no
>>> > > problem. If, however, you want to automate plugin parameters, you
> will
>>> > need
>>> > > both machines timeline synced so that you can write automation data
> to
>>> > > Cubase SX.
>>> > >
>>> > > I am hoping to solve this problem by sending Paris ADAT sync to a
> JL
>>> > Cooper
>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>> > > slaving
>>> > Cubase
>>> > > SX to incoming MTC form the Datasync II.
>>> > >
>>> > > Thank goodness for yet another kludge. I thought I had finally
>>succeeded
>>> > in
>>> > > accomplishing everything I started out to do and there was this
>>> > > sudden
>>> > > realization that my life would have no further purpose.
>>> > >
>>> > > ;o)
>>> > >
>>> > >
>>> >
>>> >
>>>
>>>
>>
>>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73591 is a reply to message #73589] |
Thu, 05 October 2006 00:43 |
Nappy
Messages: 198
Registered: September 2006
|
Senior Member |
|
|
Martin,
We think alot alike,maybe it because we are about the same age;with in days!
I think? I was born 4 July 1956,you the 3rd of July if I remember correctly?
respect
Nappy
"Martin Harrington" <lendan@bigpond.net.au> wrote:
>Huh, that's funny, I didn't read Nappy's post until I sent the previous
>one...
>It's not only me that's looking after you health
>--
>Martin Harrington
>www.lendanear-sound.com
>
>"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>>
>> DJ'
>> I'm starting to think it may be time for you to make the jump to a
>> Dualcore
>> intel box and
>> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
time
>> and
>> brain power into this,lord knows I'm exhausted just reading it. I think
>> you
>> would be
>> better using PARIS as a summing buss. At least thats what I'm coming to
>> believe.
>> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>> Intel
>> box and run Cubase 4 and be done with it.
>>
>> respect
>> Nappy
>> "DJ" <notachance@net.net> wrote:
>>>Hmmm......this just may not be possible to achieve. I've got both systems
>>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
The
>>>jury is still out on whether or not this is going to fly. The latency
>>>between EDS cards and the audio being streamed from ADAT modules that
are
>>>clocked to those cards may be an insurmountable issue here.
>>>Deej
>>>
>>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>>> The Cubase rig just crashed while not receiving any sync info at all
>>>between
>>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>>tuned.
>>>>
>>>>
>>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>>> > Further repeated testing has verified that when Paris ADAT sync output
>>>is
>>>> > hooked directly up to the RME audio interface ADAT sync input, if
>>>> > ASIO
>>>> > positioning protocall is selected as the Cubase sync sounce, even
if
>> the
>>>> RME
>>>> > transport is set to internal so that the Cubase transport is not
>>>> > chasing
>>>> the
>>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>> of
>>>an
>>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>>> >
>>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>>selected)
>>>> so
>>>> > that there is no interfacing between the Paris ADAT module and Cubase
>> SX
>>>> > works fine......no crashes of cubase SX when processing tracks from
>>>> multiple
>>>> > submixes in Paris.
>>>> >
>>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
do
>> the
>>>> > trick.
>>>> >
>>>> > Deej
>>>> >
>>>> >
>>>> >
>>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>>> > > OK,
>>>> > >
>>>> > > Before you guys start getting too exicted about this, it appears
>>>> > > that
>>>> > there
>>>> > > is one more hoop to jump through if you are using multiple MECs.
>>>> > > When
>>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
>> SX
>>>is
>>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>>>> from
>>>> > > two different MECs. This is likely due to the latency between EDS
>>>cards
>>>> > > causing a trainwreck with the clocking.
>>>> > > This will not be an issue to those who are not wanting to have
>>>> > > plugin
>>>> > > automation in SX. As long as SX is not slaving to the Paris
>>>> > > timeline,
>>>> the
>>>> > > audio passes through the audio interface on Cubase and back to Paris
>>>> with
>>>> > no
>>>> > > problem. If, however, you want to automate plugin parameters, you
>> will
>>>> > need
>>>> > > both machines timeline synced so that you can write automation data
>> to
>>>> > > Cubase SX.
>>>> > >
>>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
a
>> JL
>>>> > Cooper
>>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>>> > > slaving
>>>> > Cubase
>>>> > > SX to incoming MTC form the Datasync II.
>>>> > >
>>>> > > Thank goodness for yet another kludge. I thought I had finally
>>>succeeded
>>>> > in
>>>> > > accomplishing everything I started out to do and there was this
>>>> > > sudden
>>>> > > realization that my life would have no further purpose.
>>>> > >
>>>> > > ;o)
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>>
>>>>
>>>
>>>
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73592 is a reply to message #73591] |
Thu, 05 October 2006 02:00 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
you should see how deej makes toast...oy...264 ramblers standing on
end with the hoods removed about 3 inches apart. i mean it works but
just a tad excessive. but then, that's our deej isn't it.
On 5 Oct 2006 17:43:18 +1000, "Nappy" <mgrant01@san.rr.com> wrote:
>
>Martin,
>We think alot alike,maybe it because we are about the same age;with in days!
>I think? I was born 4 July 1956,you the 3rd of July if I remember correctly?
>
>respect
>Nappy
>
>"Martin Harrington" <lendan@bigpond.net.au> wrote:
>>Huh, that's funny, I didn't read Nappy's post until I sent the previous
>
>>one...
>>It's not only me that's looking after you health
>>--
>>Martin Harrington
>>www.lendanear-sound.com
>>
>>"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>>>
>>> DJ'
>>> I'm starting to think it may be time for you to make the jump to a
>>> Dualcore
>>> intel box and
>>> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
>time
>>> and
>>> brain power into this,lord knows I'm exhausted just reading it. I think
>
>>> you
>>> would be
>>> better using PARIS as a summing buss. At least thats what I'm coming to
>
>>> believe.
>>> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>
>>> Intel
>>> box and run Cubase 4 and be done with it.
>>>
>>> respect
>>> Nappy
>>> "DJ" <notachance@net.net> wrote:
>>>>Hmmm......this just may not be possible to achieve. I've got both systems
>>>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
>The
>>>>jury is still out on whether or not this is going to fly. The latency
>>>>between EDS cards and the audio being streamed from ADAT modules that
>are
>>>>clocked to those cards may be an insurmountable issue here.
>>>>Deej
>>>>
>>>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>>>> The Cubase rig just crashed while not receiving any sync info at all
>>>>between
>>>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>>>tuned.
>>>>>
>>>>>
>>>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>>>> > Further repeated testing has verified that when Paris ADAT sync output
>>>>is
>>>>> > hooked directly up to the RME audio interface ADAT sync input, if
>
>>>>> > ASIO
>>>>> > positioning protocall is selected as the Cubase sync sounce, even
>if
>>> the
>>>>> RME
>>>>> > transport is set to internal so that the Cubase transport is not
>>>>> > chasing
>>>>> the
>>>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>>> of
>>>>an
>>>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>>>> >
>>>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>>>selected)
>>>>> so
>>>>> > that there is no interfacing between the Paris ADAT module and Cubase
>>> SX
>>>>> > works fine......no crashes of cubase SX when processing tracks from
>>>>> multiple
>>>>> > submixes in Paris.
>>>>> >
>>>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
>do
>>> the
>>>>> > trick.
>>>>> >
>>>>> > Deej
>>>>> >
>>>>> >
>>>>> >
>>>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>>>> > > OK,
>>>>> > >
>>>>> > > Before you guys start getting too exicted about this, it appears
>
>>>>> > > that
>>>>> > there
>>>>> > > is one more hoop to jump through if you are using multiple MECs.
>
>>>>> > > When
>>>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
>>> SX
>>>>is
>>>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>>>>> from
>>>>> > > two different MECs. This is likely due to the latency between EDS
>>>>cards
>>>>> > > causing a trainwreck with the clocking.
>>>>> > > This will not be an issue to those who are not wanting to have
>>>>> > > plugin
>>>>> > > automation in SX. As long as SX is not slaving to the Paris
>>>>> > > timeline,
>>>>> the
>>>>> > > audio passes through the audio interface on Cubase and back to Paris
>>>>> with
>>>>> > no
>>>>> > > problem. If, however, you want to automate plugin parameters, you
>>> will
>>>>> > need
>>>>> > > both machines timeline synced so that you can write automation data
>>> to
>>>>> > > Cubase SX.
>>>>> > >
>>>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
>a
>>> JL
>>>>> > Cooper
>>>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>>>> > > slaving
>>>>> > Cubase
>>>>> > > SX to incoming MTC form the Datasync II.
>>>>> > >
>>>>> > > Thank goodness for yet another kludge. I thought I had finally
>>>>succeeded
>>>>> > in
>>>>> > > accomplishing everything I started out to do and there was this
>
>>>>> > > sudden
>>>>> > > realization that my life would have no further purpose.
>>>>> > >
>>>>> > > ;o)
>>>>> > >
>>>>> > >
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73593 is a reply to message #73583] |
Thu, 05 October 2006 02:02 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
aren't all the machines set to the same sample rate?
On Wed, 4 Oct 2006 22:44:51 -0600, "DJ" <notachance@net.net> wrote:
>I wonder if this isn't working because some of the UAD-1 plugins (like the
>Neve EQ for instance) are upsampling what is essentially a Paris audio file
>being played *through* SX with none of the downsampling possible that would
>normally be part of the DSP process in SX to resolve the sample rate of the
>plugin to the project sample rate/clock source. If so, that would certainly
>explain some things. It might also explain why the UAD-1 card with ADAT I/O
>that was on the boards a few years ago went nowhere and why the POCO,
>Duende, etc. do not have digital I/O and only work in a plugin format. If
>these processors were
>upsampling/downsampling in real time, the SR converters/clocking shenanigans
>that would be necessary to bring the audio signal back to the project sample
>rate would put the pricepoint through the roof.
>
>Well.....it's just a thought........
>
>;O)
>
>Deej
>
>
>
>
>"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
>> Well.........I'm baffled by this and I'm just going to let it slide for a
>> while. Looping audio *through* SX so that it functions as a standalone FX
>> processor has been a total bust so far. OTOH, streaming tracks directly
>from
>> SX (lots of them) to Paris and summing there does not create the clocking
>> trainwreck that looping through the inserts does. I guess it must be the
>> loop that is causing it as opposed to the one way trip.
>>
>> C'est la ****'in vie
>>
>> ;o)
>>
>> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> > OK,
>> >
>> > Before you guys start getting too exicted about this, it appears that
>> there
>> > is one more hoop to jump through if you are using multiple MECs. When
>> > looping audio from Paris *through* Cubase SX channels while Cubase SX is
>> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>from
>> > two different MECs. This is likely due to the latency between EDS cards
>> > causing a trainwreck with the clocking.
>> > This will not be an issue to those who are not wanting to have plugin
>> > automation in SX. As long as SX is not slaving to the Paris timeline,
>the
>> > audio passes through the audio interface on Cubase and back to Paris
>with
>> no
>> > problem. If, however, you want to automate plugin parameters, you will
>> need
>> > both machines timeline synced so that you can write automation data to
>> > Cubase SX.
>> >
>> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
>> Cooper
>> > Datasync II unit which converts ADAT timecode to MTC and then slaving
>> Cubase
>> > SX to incoming MTC form the Datasync II.
>> >
>> > Thank goodness for yet another kludge. I thought I had finally succeeded
>> in
>> > accomplishing everything I started out to do and there was this sudden
>> > realization that my life would have no further purpose.
>> >
>> > ;o)
>> >
>> >
>>
>>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73596 is a reply to message #73591] |
Thu, 05 October 2006 03:37 |
Martin Harrington
Messages: 560
Registered: September 2005
|
Senior Member |
|
|
You're right Nappy...life's too short....
--
Martin
www.lendanear-sound.com
"Nappy" <mgrant01@san.rr.com> wrote in message news:4524b796$1@linux...
>
> Martin,
> We think alot alike,maybe it because we are about the same age;with in
> days!
> I think? I was born 4 July 1956,you the 3rd of July if I remember
> correctly?
>
> respect
> Nappy
>
> "Martin Harrington" <lendan@bigpond.net.au> wrote:
>>Huh, that's funny, I didn't read Nappy's post until I sent the previous
>
>>one...
>>It's not only me that's looking after you health
>>--
>>Martin Harrington
>>www.lendanear-sound.com
>>
>>"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>>>
>>> DJ'
>>> I'm starting to think it may be time for you to make the jump to a
>>> Dualcore
>>> intel box and
>>> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
> time
>>> and
>>> brain power into this,lord knows I'm exhausted just reading it. I think
>
>>> you
>>> would be
>>> better using PARIS as a summing buss. At least thats what I'm coming to
>
>>> believe.
>>> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>
>>> Intel
>>> box and run Cubase 4 and be done with it.
>>>
>>> respect
>>> Nappy
>>> "DJ" <notachance@net.net> wrote:
>>>>Hmmm......this just may not be possible to achieve. I've got both
>>>>systems
>>>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
> The
>>>>jury is still out on whether or not this is going to fly. The latency
>>>>between EDS cards and the audio being streamed from ADAT modules that
> are
>>>>clocked to those cards may be an insurmountable issue here.
>>>>Deej
>>>>
>>>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>>>> The Cubase rig just crashed while not receiving any sync info at all
>>>>between
>>>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>>>tuned.
>>>>>
>>>>>
>>>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>>>> > Further repeated testing has verified that when Paris ADAT sync
>>>>> > output
>>>>is
>>>>> > hooked directly up to the RME audio interface ADAT sync input, if
>
>>>>> > ASIO
>>>>> > positioning protocall is selected as the Cubase sync sounce, even
> if
>>> the
>>>>> RME
>>>>> > transport is set to internal so that the Cubase transport is not
>>>>> > chasing
>>>>> the
>>>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>>> of
>>>>an
>>>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>>>> >
>>>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>>>selected)
>>>>> so
>>>>> > that there is no interfacing between the Paris ADAT module and
>>>>> > Cubase
>>> SX
>>>>> > works fine......no crashes of cubase SX when processing tracks from
>>>>> multiple
>>>>> > submixes in Paris.
>>>>> >
>>>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
> do
>>> the
>>>>> > trick.
>>>>> >
>>>>> > Deej
>>>>> >
>>>>> >
>>>>> >
>>>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>>>> > > OK,
>>>>> > >
>>>>> > > Before you guys start getting too exicted about this, it appears
>
>>>>> > > that
>>>>> > there
>>>>> > > is one more hoop to jump through if you are using multiple MECs.
>
>>>>> > > When
>>>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
>>> SX
>>>>is
>>>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
>>>>> > > looped
>>>>> from
>>>>> > > two different MECs. This is likely due to the latency between EDS
>>>>cards
>>>>> > > causing a trainwreck with the clocking.
>>>>> > > This will not be an issue to those who are not wanting to have
>>>>> > > plugin
>>>>> > > automation in SX. As long as SX is not slaving to the Paris
>>>>> > > timeline,
>>>>> the
>>>>> > > audio passes through the audio interface on Cubase and back to
>>>>> > > Paris
>>>>> with
>>>>> > no
>>>>> > > problem. If, however, you want to automate plugin parameters, you
>>> will
>>>>> > need
>>>>> > > both machines timeline synced so that you can write automation
>>>>> > > data
>>> to
>>>>> > > Cubase SX.
>>>>> > >
>>>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
> a
>>> JL
>>>>> > Cooper
>>>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>>>> > > slaving
>>>>> > Cubase
>>>>> > > SX to incoming MTC form the Datasync II.
>>>>> > >
>>>>> > > Thank goodness for yet another kludge. I thought I had finally
>>>>succeeded
>>>>> > in
>>>>> > > accomplishing everything I started out to do and there was this
>
>>>>> > > sudden
>>>>> > > realization that my life would have no further purpose.
>>>>> > >
>>>>> > > ;o)
>>>>> > >
>>>>> > >
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73597 is a reply to message #73593] |
Thu, 05 October 2006 05:02 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Yes, they are, but the UAD-1 upsamples during processing with the Fairchild,
1073, Pultec and some others.
"rick" <parnell68@hotmail.com> wrote in message
news:gei9i2tdu1nimf16gnf75mfl7hsb0lpb82@4ax.com...
> aren't all the machines set to the same sample rate?
>
> On Wed, 4 Oct 2006 22:44:51 -0600, "DJ" <notachance@net.net> wrote:
>
> >I wonder if this isn't working because some of the UAD-1 plugins (like
the
> >Neve EQ for instance) are upsampling what is essentially a Paris audio
file
> >being played *through* SX with none of the downsampling possible that
would
> >normally be part of the DSP process in SX to resolve the sample rate of
the
> >plugin to the project sample rate/clock source. If so, that would
certainly
> >explain some things. It might also explain why the UAD-1 card with ADAT
I/O
> >that was on the boards a few years ago went nowhere and why the POCO,
> >Duende, etc. do not have digital I/O and only work in a plugin format. If
> >these processors were
> >upsampling/downsampling in real time, the SR converters/clocking
shenanigans
> >that would be necessary to bring the audio signal back to the project
sample
> >rate would put the pricepoint through the roof.
> >
> >Well.....it's just a thought........
> >
> >;O)
> >
> >Deej
> >
> >
> >
> >
> >"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
> >> Well.........I'm baffled by this and I'm just going to let it slide for
a
> >> while. Looping audio *through* SX so that it functions as a standalone
FX
> >> processor has been a total bust so far. OTOH, streaming tracks directly
> >from
> >> SX (lots of them) to Paris and summing there does not create the
clocking
> >> trainwreck that looping through the inserts does. I guess it must be
the
> >> loop that is causing it as opposed to the one way trip.
> >>
> >> C'est la ****'in vie
> >>
> >> ;o)
> >>
> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >> > OK,
> >> >
> >> > Before you guys start getting too exicted about this, it appears that
> >> there
> >> > is one more hoop to jump through if you are using multiple MECs. When
> >> > looping audio from Paris *through* Cubase SX channels while Cubase SX
is
> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
> >from
> >> > two different MECs. This is likely due to the latency between EDS
cards
> >> > causing a trainwreck with the clocking.
> >> > This will not be an issue to those who are not wanting to have plugin
> >> > automation in SX. As long as SX is not slaving to the Paris timeline,
> >the
> >> > audio passes through the audio interface on Cubase and back to Paris
> >with
> >> no
> >> > problem. If, however, you want to automate plugin parameters, you
will
> >> need
> >> > both machines timeline synced so that you can write automation data
to
> >> > Cubase SX.
> >> >
> >> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
> >> Cooper
> >> > Datasync II unit which converts ADAT timecode to MTC and then slaving
> >> Cubase
> >> > SX to incoming MTC form the Datasync II.
> >> >
> >> > Thank goodness for yet another kludge. I thought I had finally
succeeded
> >> in
> >> > accomplishing everything I started out to do and there was this
sudden
> >> > realization that my life would have no further purpose.
> >> >
> >> > ;o)
> >> >
> >> >
> >>
> >>
> >
>
|
|
|
|
| Re: UH OH!!......not good! [message #73599 is a reply to message #73591] |
Thu, 05 October 2006 05:20 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
June 29 1950 here.
;o)
"Nappy" <mgrant01@san.rr.com> wrote in message news:4524b796$1@linux...
>
> Martin,
> We think alot alike,maybe it because we are about the same age;with in
days!
> I think? I was born 4 July 1956,you the 3rd of July if I remember
correctly?
>
> respect
> Nappy
>
> "Martin Harrington" <lendan@bigpond.net.au> wrote:
> >Huh, that's funny, I didn't read Nappy's post until I sent the previous
>
> >one...
> >It's not only me that's looking after you health
> >--
> >Martin Harrington
> >www.lendanear-sound.com
> >
> >"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
> >>
> >> DJ'
> >> I'm starting to think it may be time for you to make the jump to a
> >> Dualcore
> >> intel box and
> >> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
> time
> >> and
> >> brain power into this,lord knows I'm exhausted just reading it. I think
>
> >> you
> >> would be
> >> better using PARIS as a summing buss. At least thats what I'm coming to
>
> >> believe.
> >> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>
> >> Intel
> >> box and run Cubase 4 and be done with it.
> >>
> >> respect
> >> Nappy
> >> "DJ" <notachance@net.net> wrote:
> >>>Hmmm......this just may not be possible to achieve. I've got both
systems
> >>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
> The
> >>>jury is still out on whether or not this is going to fly. The latency
> >>>between EDS cards and the audio being streamed from ADAT modules that
> are
> >>>clocked to those cards may be an insurmountable issue here.
> >>>Deej
> >>>
> >>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
> >>>> The Cubase rig just crashed while not receiving any sync info at all
> >>>between
> >>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
> >>>tuned.
> >>>>
> >>>>
> >>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
> >>>> > Further repeated testing has verified that when Paris ADAT sync
output
> >>>is
> >>>> > hooked directly up to the RME audio interface ADAT sync input, if
>
> >>>> > ASIO
> >>>> > positioning protocall is selected as the Cubase sync sounce, even
> if
> >> the
> >>>> RME
> >>>> > transport is set to internal so that the Cubase transport is not
> >>>> > chasing
> >>>> the
> >>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
> >> of
> >>>an
> >>>> > audio track from Submix 2/card B/MEC 2 starting to play.
> >>>> >
> >>>> > Setting sync source in Cubase SX to MTC (with no midi interface
> >>>selected)
> >>>> so
> >>>> > that there is no interfacing between the Paris ADAT module and
Cubase
> >> SX
> >>>> > works fine......no crashes of cubase SX when processing tracks from
> >>>> multiple
> >>>> > submixes in Paris.
> >>>> >
> >>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
> do
> >> the
> >>>> > trick.
> >>>> >
> >>>> > Deej
> >>>> >
> >>>> >
> >>>> >
> >>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >>>> > > OK,
> >>>> > >
> >>>> > > Before you guys start getting too exicted about this, it appears
>
> >>>> > > that
> >>>> > there
> >>>> > > is one more hoop to jump through if you are using multiple MECs.
>
> >>>> > > When
> >>>> > > looping audio from Paris *through* Cubase SX channels while
Cubase
> >> SX
> >>>is
> >>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
looped
> >>>> from
> >>>> > > two different MECs. This is likely due to the latency between EDS
> >>>cards
> >>>> > > causing a trainwreck with the clocking.
> >>>> > > This will not be an issue to those who are not wanting to have
> >>>> > > plugin
> >>>> > > automation in SX. As long as SX is not slaving to the Paris
> >>>> > > timeline,
> >>>> the
> >>>> > > audio passes through the audio interface on Cubase and back to
Paris
> >>>> with
> >>>> > no
> >>>> > > problem. If, however, you want to automate plugin parameters, you
> >> will
> >>>> > need
> >>>> > > both machines timeline synced so that you can write automation
data
> >> to
> >>>> > > Cubase SX.
> >>>> > >
> >>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
> a
> >> JL
> >>>> > Cooper
> >>>> > > Datasync II unit which converts ADAT timecode to MTC and then
> >>>> > > slaving
> >>>> > Cubase
> >>>> > > SX to incoming MTC form the Datasync II.
> >>>> > >
> >>>> > > Thank goodness for yet another kludge. I thought I had finally
> >>>succeeded
> >>>> > in
> >>>> > > accomplishing everything I started out to do and there was this
>
> >>>> > > sudden
> >>>> > > realization that my life would have no further purpose.
> >>>> > >
> >>>> > > ;o)
> >>>> > >
> >>>> > >
> >>>> >
> >>>> >
> >>>>
> >>>>
> >>>
> >>>
> >>
> >
> >
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73600 is a reply to message #73583] |
Thu, 05 October 2006 05:28 |
Don Nafe
Messages: 1206
Registered: July 2005
|
Senior Member |
|
|
Ya know I actually understood that....scarey
would putting SX into record mode complete that circuit in the UAD?
DOn
"DJ" <notachance@net.net> wrote in message news:45248dc6@linux...
>I wonder if this isn't working because some of the UAD-1 plugins (like the
> Neve EQ for instance) are upsampling what is essentially a Paris audio
> file
> being played *through* SX with none of the downsampling possible that
> would
> normally be part of the DSP process in SX to resolve the sample rate of
> the
> plugin to the project sample rate/clock source. If so, that would
> certainly
> explain some things. It might also explain why the UAD-1 card with ADAT
> I/O
> that was on the boards a few years ago went nowhere and why the POCO,
> Duende, etc. do not have digital I/O and only work in a plugin format. If
> these processors were
> upsampling/downsampling in real time, the SR converters/clocking
> shenanigans
> that would be necessary to bring the audio signal back to the project
> sample
> rate would put the pricepoint through the roof.
>
> Well.....it's just a thought........
>
> ;O)
>
> Deej
>
>
>
>
> "DJ" <notachance@net.net> wrote in message news:452475f8@linux...
>> Well.........I'm baffled by this and I'm just going to let it slide for a
>> while. Looping audio *through* SX so that it functions as a standalone FX
>> processor has been a total bust so far. OTOH, streaming tracks directly
> from
>> SX (lots of them) to Paris and summing there does not create the clocking
>> trainwreck that looping through the inserts does. I guess it must be the
>> loop that is causing it as opposed to the one way trip.
>>
>> C'est la ****'in vie
>>
>> ;o)
>>
>> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> > OK,
>> >
>> > Before you guys start getting too exicted about this, it appears that
>> there
>> > is one more hoop to jump through if you are using multiple MECs. When
>> > looping audio from Paris *through* Cubase SX channels while Cubase SX
>> > is
>> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
> from
>> > two different MECs. This is likely due to the latency between EDS cards
>> > causing a trainwreck with the clocking.
>> > This will not be an issue to those who are not wanting to have plugin
>> > automation in SX. As long as SX is not slaving to the Paris timeline,
> the
>> > audio passes through the audio interface on Cubase and back to Paris
> with
>> no
>> > problem. If, however, you want to automate plugin parameters, you will
>> need
>> > both machines timeline synced so that you can write automation data to
>> > Cubase SX.
>> >
>> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
>> Cooper
>> > Datasync II unit which converts ADAT timecode to MTC and then slaving
>> Cubase
>> > SX to incoming MTC form the Datasync II.
>> >
>> > Thank goodness for yet another kludge. I thought I had finally
>> > succeeded
>> in
>> > accomplishing everything I started out to do and there was this sudden
>> > realization that my life would have no further purpose.
>> >
>> > ;o)
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73601 is a reply to message #73600] |
Thu, 05 October 2006 05:27 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Hmmmm...........maybe so?
"Don Nafe" <dnafe@magma.ca> wrote in message news:4524f895@linux...
> Ya know I actually understood that....scarey
>
> would putting SX into record mode complete that circuit in the UAD?
>
> DOn
>
>
> "DJ" <notachance@net.net> wrote in message news:45248dc6@linux...
> >I wonder if this isn't working because some of the UAD-1 plugins (like
the
> > Neve EQ for instance) are upsampling what is essentially a Paris audio
> > file
> > being played *through* SX with none of the downsampling possible that
> > would
> > normally be part of the DSP process in SX to resolve the sample rate of
> > the
> > plugin to the project sample rate/clock source. If so, that would
> > certainly
> > explain some things. It might also explain why the UAD-1 card with ADAT
> > I/O
> > that was on the boards a few years ago went nowhere and why the POCO,
> > Duende, etc. do not have digital I/O and only work in a plugin format.
If
> > these processors were
> > upsampling/downsampling in real time, the SR converters/clocking
> > shenanigans
> > that would be necessary to bring the audio signal back to the project
> > sample
> > rate would put the pricepoint through the roof.
> >
> > Well.....it's just a thought........
> >
> > ;O)
> >
> > Deej
> >
> >
> >
> >
> > "DJ" <notachance@net.net> wrote in message news:452475f8@linux...
> >> Well.........I'm baffled by this and I'm just going to let it slide for
a
> >> while. Looping audio *through* SX so that it functions as a standalone
FX
> >> processor has been a total bust so far. OTOH, streaming tracks directly
> > from
> >> SX (lots of them) to Paris and summing there does not create the
clocking
> >> trainwreck that looping through the inserts does. I guess it must be
the
> >> loop that is causing it as opposed to the one way trip.
> >>
> >> C'est la ****'in vie
> >>
> >> ;o)
> >>
> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >> > OK,
> >> >
> >> > Before you guys start getting too exicted about this, it appears that
> >> there
> >> > is one more hoop to jump through if you are using multiple MECs. When
> >> > looping audio from Paris *through* Cubase SX channels while Cubase SX
> >> > is
> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
> > from
> >> > two different MECs. This is likely due to the latency between EDS
cards
> >> > causing a trainwreck with the clocking.
> >> > This will not be an issue to those who are not wanting to have plugin
> >> > automation in SX. As long as SX is not slaving to the Paris timeline,
> > the
> >> > audio passes through the audio interface on Cubase and back to Paris
> > with
> >> no
> >> > problem. If, however, you want to automate plugin parameters, you
will
> >> need
> >> > both machines timeline synced so that you can write automation data
to
> >> > Cubase SX.
> >> >
> >> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
> >> Cooper
> >> > Datasync II unit which converts ADAT timecode to MTC and then slaving
> >> Cubase
> >> > SX to incoming MTC form the Datasync II.
> >> >
> >> > Thank goodness for yet another kludge. I thought I had finally
> >> > succeeded
> >> in
> >> > accomplishing everything I started out to do and there was this
sudden
> >> > realization that my life would have no further purpose.
> >> >
> >> > ;o)
> >> >
> >> >
> >>
> >>
> >
> >
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73602 is a reply to message #73589] |
Thu, 05 October 2006 06:21 |
Nei
Messages: 108
Registered: November 2006
|
Senior Member |
|
|
Martin, I'm with you & Nappy. I like tinkering, too, but at
some stage if something gets too convoluted, you start reaching
a point of diminishing returns. Deej, have you considered that
part of your issue with sync/lock might be that you're going in
& out of both machines in digital? What would happen if you
switched to analog? I mean, you've got good convertors on both
ends there, so I'd hardly think signal degradation would be a
problem.
Either that or just track in Paris, export the files so you can
mix in SX (even upsample to 96k on the way in, if you must!) so
you can use all your EFX, but use four submixes out of your
Multiface analog outs, then back into your Paris box to sum in
live mode. That way you get to hit those Paris convertors one
more time, in fact. :)
Heck, with most of the stuff you do (bluegrass, folkish stuff,
etc) "clean" is good... you could live perfectly happily with
just SX & those nice clean RME convertors.
Heaven forbid! lol
Neil
"Martin Harrington" <lendan@bigpond.net.au> wrote:
>Huh, that's funny, I didn't read Nappy's post until I sent the previous
>one...
>It's not only me that's looking after you health
>--
>Martin Harrington
>www.lendanear-sound.com
>
>"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>>
>> DJ'
>> I'm starting to think it may be time for you to make the jump to a
>> Dualcore
>> intel box and
>> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
time
>> and
>> brain power into this,lord knows I'm exhausted just reading it. I think
>> you
>> would be
>> better using PARIS as a summing buss. At least thats what I'm coming to
>> believe.
>> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>> Intel
>> box and run Cubase 4 and be done with it.
>>
>> respect
>> Nappy
>> "DJ" <notachance@net.net> wrote:
>>>Hmmm......this just may not be possible to achieve. I've got both systems
>>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
The
>>>jury is still out on whether or not this is going to fly. The latency
>>>between EDS cards and the audio being streamed from ADAT modules that
are
>>>clocked to those cards may be an insurmountable issue here.
>>>Deej
>>>
>>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>>> The Cubase rig just crashed while not receiving any sync info at all
>>>between
>>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>>tuned.
>>>>
>>>>
>>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>>> > Further repeated testing has verified that when Paris ADAT sync output
>>>is
>>>> > hooked directly up to the RME audio interface ADAT sync input, if
>>>> > ASIO
>>>> > positioning protocall is selected as the Cubase sync sounce, even
if
>> the
>>>> RME
>>>> > transport is set to internal so that the Cubase transport is not
>>>> > chasing
>>>> the
>>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>> of
>>>an
>>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>>> >
>>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>>selected)
>>>> so
>>>> > that there is no interfacing between the Paris ADAT module and Cubase
>> SX
>>>> > works fine......no crashes of cubase SX when processing tracks from
>>>> multiple
>>>> > submixes in Paris.
>>>> >
>>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
do
>> the
>>>> > trick.
>>>> >
>>>> > Deej
>>>> >
>>>> >
>>>> >
>>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>>> > > OK,
>>>> > >
>>>> > > Before you guys start getting too exicted about this, it appears
>>>> > > that
>>>> > there
>>>> > > is one more hoop to jump through if you are using multiple MECs.
>>>> > > When
>>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
>> SX
>>>is
>>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>>>> from
>>>> > > two different MECs. This is likely due to the latency between EDS
>>>cards
>>>> > > causing a trainwreck with the clocking.
>>>> > > This will not be an issue to those who are not wanting to have
>>>> > > plugin
>>>> > > automation in SX. As long as SX is not slaving to the Paris
>>>> > > timeline,
>>>> the
>>>> > > audio passes through the audio interface on Cubase and back to Paris
>>>> with
>>>> > no
>>>> > > problem. If, however, you want to automate plugin parameters, you
>> will
>>>> > need
>>>> > > both machines timeline synced so that you can write automation data
>> to
>>>> > > Cubase SX.
>>>> > >
>>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
a
>> JL
>>>> > Cooper
>>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>>> > > slaving
>>>> > Cubase
>>>> > > SX to incoming MTC form the Datasync II.
>>>> > >
>>>> > > Thank goodness for yet another kludge. I thought I had finally
>>>succeeded
>>>> > in
>>>> > > accomplishing everything I started out to do and there was this
>>>> > > sudden
>>>> > > realization that my life would have no further purpose.
>>>> > >
>>>> > > ;o)
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>>
>>>>
>>>
>>>
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73605 is a reply to message #73599] |
Thu, 05 October 2006 07:32 |
Nappy
Messages: 198
Registered: September 2006
|
Senior Member |
|
|
What a bunch we are here!
That explains it.
DJ,I want you to know I've got a ton of respect for you,and I
think what you're doing in your studio is very creative.
It truly makes my head spin,and I think I'm a pretty smart guy.
Keep your note on this whole process I may go your way in the end,who knows.
I like to keep a open mind. Thanks for blazing t trail for us all!
respect
Nappy
"DJ" <notachance@net.net> wrote:
>June 29 1950 here.
>
>;o)
>
>"Nappy" <mgrant01@san.rr.com> wrote in message news:4524b796$1@linux...
>>
>> Martin,
>> We think alot alike,maybe it because we are about the same age;with in
>days!
>> I think? I was born 4 July 1956,you the 3rd of July if I remember
>correctly?
>>
>> respect
>> Nappy
>>
>> "Martin Harrington" <lendan@bigpond.net.au> wrote:
>> >Huh, that's funny, I didn't read Nappy's post until I sent the previous
>>
>> >one...
>> >It's not only me that's looking after you health
>> >--
>> >Martin Harrington
>> >www.lendanear-sound.com
>> >
>> >"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>> >>
>> >> DJ'
>> >> I'm starting to think it may be time for you to make the jump to a
>> >> Dualcore
>> >> intel box and
>> >> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot
of
>> time
>> >> and
>> >> brain power into this,lord knows I'm exhausted just reading it. I think
>>
>> >> you
>> >> would be
>> >> better using PARIS as a summing buss. At least thats what I'm coming
to
>>
>> >> believe.
>> >> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>>
>> >> Intel
>> >> box and run Cubase 4 and be done with it.
>> >>
>> >> respect
>> >> Nappy
>> >> "DJ" <notachance@net.net> wrote:
>> >>>Hmmm......this just may not be possible to achieve. I've got both
>systems
>> >>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
>> The
>> >>>jury is still out on whether or not this is going to fly. The latency
>> >>>between EDS cards and the audio being streamed from ADAT modules that
>> are
>> >>>clocked to those cards may be an insurmountable issue here.
>> >>>Deej
>> >>>
>> >>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>> >>>> The Cubase rig just crashed while not receiving any sync info at
all
>> >>>between
>> >>>> Paris and Cubase. Not good. I've got another trick up my sleeve.
Stay
>> >>>tuned.
>> >>>>
>> >>>>
>> >>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>> >>>> > Further repeated testing has verified that when Paris ADAT sync
>output
>> >>>is
>> >>>> > hooked directly up to the RME audio interface ADAT sync input,
if
>>
>> >>>> > ASIO
>> >>>> > positioning protocall is selected as the Cubase sync sounce, even
>> if
>> >> the
>> >>>> RME
>> >>>> > transport is set to internal so that the Cubase transport is not
>> >>>> > chasing
>> >>>> the
>> >>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>> >> of
>> >>>an
>> >>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>> >>>> >
>> >>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>> >>>selected)
>> >>>> so
>> >>>> > that there is no interfacing between the Paris ADAT module and
>Cubase
>> >> SX
>> >>>> > works fine......no crashes of cubase SX when processing tracks
from
>> >>>> multiple
>> >>>> > submixes in Paris.
>> >>>> >
>> >>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
>> do
>> >> the
>> >>>> > trick.
>> >>>> >
>> >>>> > Deej
>> >>>> >
>> >>>> >
>> >>>> >
>> >>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> >>>> > > OK,
>> >>>> > >
>> >>>> > > Before you guys start getting too exicted about this, it appears
>>
>> >>>> > > that
>> >>>> > there
>> >>>> > > is one more hoop to jump through if you are using multiple MECs.
>>
>> >>>> > > When
>> >>>> > > looping audio from Paris *through* Cubase SX channels while
>Cubase
>> >> SX
>> >>>is
>> >>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
>looped
>> >>>> from
>> >>>> > > two different MECs. This is likely due to the latency between
EDS
>> >>>cards
>> >>>> > > causing a trainwreck with the clocking.
>> >>>> > > This will not be an issue to those who are not wanting to have
>> >>>> > > plugin
>> >>>> > > automation in SX. As long as SX is not slaving to the Paris
>> >>>> > > timeline,
>> >>>> the
>> >>>> > > audio passes through the audio interface on Cubase and back to
>Paris
>> >>>> with
>> >>>> > no
>> >>>> > > problem. If, however, you want to automate plugin parameters,
you
>> >> will
>> >>>> > need
>> >>>> > > both machines timeline synced so that you can write automation
>data
>> >> to
>> >>>> > > Cubase SX.
>> >>>> > >
>> >>>> > > I am hoping to solve this problem by sending Paris ADAT sync
to
>> a
>> >> JL
>> >>>> > Cooper
>> >>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>> >>>> > > slaving
>> >>>> > Cubase
>> >>>> > > SX to incoming MTC form the Datasync II.
>> >>>> > >
>> >>>> > > Thank goodness for yet another kludge. I thought I had finally
>> >>>succeeded
>> >>>> > in
>> >>>> > > accomplishing everything I started out to do and there was this
>>
>> >>>> > > sudden
>> >>>> > > realization that my life would have no further purpose.
>> >>>> > >
>> >>>> > > ;o)
>> >>>> > >
>> >>>> > >
>> >>>> >
>> >>>> >
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >
>> >
>>
>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73611 is a reply to message #73605] |
Thu, 05 October 2006 08:06 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Hey Nappy,
I like to try to make DAWs perform unnatural acts. :o)
I'll keep everyone posted if I can find a way to get this happening. Dave
(EK) had some suggestions yesterday that I'm going to try.
Cheers,
Deej
"Nappy" <mgrant01@san.rr.com> wrote in message news:4525177b$1@linux...
>
> What a bunch we are here!
> That explains it.
> DJ,I want you to know I've got a ton of respect for you,and I
> think what you're doing in your studio is very creative.
> It truly makes my head spin,and I think I'm a pretty smart guy.
> Keep your note on this whole process I may go your way in the end,who
knows.
> I like to keep a open mind. Thanks for blazing t trail for us all!
>
> respect
> Nappy
>
> "DJ" <notachance@net.net> wrote:
> >June 29 1950 here.
> >
> >;o)
> >
> >"Nappy" <mgrant01@san.rr.com> wrote in message news:4524b796$1@linux...
> >>
> >> Martin,
> >> We think alot alike,maybe it because we are about the same age;with in
> >days!
> >> I think? I was born 4 July 1956,you the 3rd of July if I remember
> >correctly?
> >>
> >> respect
> >> Nappy
> >>
> >> "Martin Harrington" <lendan@bigpond.net.au> wrote:
> >> >Huh, that's funny, I didn't read Nappy's post until I sent the
previous
> >>
> >> >one...
> >> >It's not only me that's looking after you health
> >> >--
> >> >Martin Harrington
> >> >www.lendanear-sound.com
> >> >
> >> >"Nappy" <mgrant01@san.rr.com> wrote in message
news:45242cc2$1@linux...
> >> >>
> >> >> DJ'
> >> >> I'm starting to think it may be time for you to make the jump to a
> >> >> Dualcore
> >> >> intel box and
> >> >> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot
> of
> >> time
> >> >> and
> >> >> brain power into this,lord knows I'm exhausted just reading it. I
think
> >>
> >> >> you
> >> >> would be
> >> >> better using PARIS as a summing buss. At least thats what I'm coming
> to
> >>
> >> >> believe.
> >> >> I'm going to use my old B&W G3 for my PARIS system and build a
Dualcore
> >>
> >> >> Intel
> >> >> box and run Cubase 4 and be done with it.
> >> >>
> >> >> respect
> >> >> Nappy
> >> >> "DJ" <notachance@net.net> wrote:
> >> >>>Hmmm......this just may not be possible to achieve. I've got both
> >systems
> >> >>>clocked to the Lucid....No ADAT sync is interfaced with the RME
cards.
> >> The
> >> >>>jury is still out on whether or not this is going to fly. The
latency
> >> >>>between EDS cards and the audio being streamed from ADAT modules
that
> >> are
> >> >>>clocked to those cards may be an insurmountable issue here.
> >> >>>Deej
> >> >>>
> >> >>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
> >> >>>> The Cubase rig just crashed while not receiving any sync info at
> all
> >> >>>between
> >> >>>> Paris and Cubase. Not good. I've got another trick up my sleeve.
> Stay
> >> >>>tuned.
> >> >>>>
> >> >>>>
> >> >>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
> >> >>>> > Further repeated testing has verified that when Paris ADAT sync
> >output
> >> >>>is
> >> >>>> > hooked directly up to the RME audio interface ADAT sync input,
> if
> >>
> >> >>>> > ASIO
> >> >>>> > positioning protocall is selected as the Cubase sync sounce,
even
> >> if
> >> >> the
> >> >>>> RME
> >> >>>> > transport is set to internal so that the Cubase transport is not
> >> >>>> > chasing
> >> >>>> the
> >> >>>> > Paris timeline, Cubase will crash within 5 seconds of the
beginning
> >> >> of
> >> >>>an
> >> >>>> > audio track from Submix 2/card B/MEC 2 starting to play.
> >> >>>> >
> >> >>>> > Setting sync source in Cubase SX to MTC (with no midi interface
> >> >>>selected)
> >> >>>> so
> >> >>>> > that there is no interfacing between the Paris ADAT module and
> >Cubase
> >> >> SX
> >> >>>> > works fine......no crashes of cubase SX when processing tracks
> from
> >> >>>> multiple
> >> >>>> > submixes in Paris.
> >> >>>> >
> >> >>>> > Thanks for you input on this Dave. Hopefully the Datasync II
will
> >> do
> >> >> the
> >> >>>> > trick.
> >> >>>> >
> >> >>>> > Deej
> >> >>>> >
> >> >>>> >
> >> >>>> >
> >> >>>> > "DJ" <notachance@net.net> wrote in message
news:452403c4@linux...
> >> >>>> > > OK,
> >> >>>> > >
> >> >>>> > > Before you guys start getting too exicted about this, it
appears
> >>
> >> >>>> > > that
> >> >>>> > there
> >> >>>> > > is one more hoop to jump through if you are using multiple
MECs.
> >>
> >> >>>> > > When
> >> >>>> > > looping audio from Paris *through* Cubase SX channels while
> >Cubase
> >> >> SX
> >> >>>is
> >> >>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being
> >looped
> >> >>>> from
> >> >>>> > > two different MECs. This is likely due to the latency between
> EDS
> >> >>>cards
> >> >>>> > > causing a trainwreck with the clocking.
> >> >>>> > > This will not be an issue to those who are not wanting to have
> >> >>>> > > plugin
> >> >>>> > > automation in SX. As long as SX is not slaving to the Paris
> >> >>>> > > timeline,
> >> >>>> the
> >> >>>> > > audio passes through the audio interface on Cubase and back to
> >Paris
> >> >>>> with
> >> >>>> > no
> >> >>>> > > problem. If, however, you want to automate plugin parameters,
> you
> >> >> will
> >> >>>> > need
> >> >>>> > > both machines timeline synced so that you can write automation
> >data
> >> >> to
> >> >>>> > > Cubase SX.
> >> >>>> > >
> >> >>>> > > I am hoping to solve this problem by sending Paris ADAT sync
> to
> >> a
> >> >> JL
> >> >>>> > Cooper
> >> >>>> > > Datasync II unit which converts ADAT timecode to MTC and then
> >> >>>> > > slaving
> >> >>>> > Cubase
> >> >>>> > > SX to incoming MTC form the Datasync II.
> >> >>>> > >
> >> >>>> > > Thank goodness for yet another kludge. I thought I had finally
> >> >>>succeeded
> >> >>>> > in
> >> >>>> > > accomplishing everything I started out to do and there was
this
> >>
> >> >>>> > > sudden
> >> >>>> > > realization that my life would have no further purpose.
> >> >>>> > >
> >> >>>> > > ;o)
> >> >>>> > >
> >> >>>> > >
> >> >>>> >
> >> >>>> >
> >> >>>>
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >
> >> >
> >>
> >
> >
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73619 is a reply to message #73597] |
Thu, 05 October 2006 11:34 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
are we talking bit rate or sample rate? i no longer have my uad card
but thought they worked at the pre specified rate of the audio. maybe
you can put a dummy file in sx to lock the uad sample rate to match
the rest.
On Thu, 5 Oct 2006 06:02:41 -0600, "DJ" <notachance@net.net> wrote:
>Yes, they are, but the UAD-1 upsamples during processing with the Fairchild,
>1073, Pultec and some others.
>
>
>"rick" <parnell68@hotmail.com> wrote in message
>news:gei9i2tdu1nimf16gnf75mfl7hsb0lpb82@4ax.com...
>> aren't all the machines set to the same sample rate?
>>
>> On Wed, 4 Oct 2006 22:44:51 -0600, "DJ" <notachance@net.net> wrote:
>>
>> >I wonder if this isn't working because some of the UAD-1 plugins (like
>the
>> >Neve EQ for instance) are upsampling what is essentially a Paris audio
>file
>> >being played *through* SX with none of the downsampling possible that
>would
>> >normally be part of the DSP process in SX to resolve the sample rate of
>the
>> >plugin to the project sample rate/clock source. If so, that would
>certainly
>> >explain some things. It might also explain why the UAD-1 card with ADAT
>I/O
>> >that was on the boards a few years ago went nowhere and why the POCO,
>> >Duende, etc. do not have digital I/O and only work in a plugin format. If
>> >these processors were
>> >upsampling/downsampling in real time, the SR converters/clocking
>shenanigans
>> >that would be necessary to bring the audio signal back to the project
>sample
>> >rate would put the pricepoint through the roof.
>> >
>> >Well.....it's just a thought........
>> >
>> >;O)
>> >
>> >Deej
>> >
>> >
>> >
>> >
>> >"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
>> >> Well.........I'm baffled by this and I'm just going to let it slide for
>a
>> >> while. Looping audio *through* SX so that it functions as a standalone
>FX
>> >> processor has been a total bust so far. OTOH, streaming tracks directly
>> >from
>> >> SX (lots of them) to Paris and summing there does not create the
>clocking
>> >> trainwreck that looping through the inserts does. I guess it must be
>the
>> >> loop that is causing it as opposed to the one way trip.
>> >>
>> >> C'est la ****'in vie
>> >>
>> >> ;o)
>> >>
>> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> >> > OK,
>> >> >
>> >> > Before you guys start getting too exicted about this, it appears that
>> >> there
>> >> > is one more hoop to jump through if you are using multiple MECs. When
>> >> > looping audio from Paris *through* Cubase SX channels while Cubase SX
>is
>> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>> >from
>> >> > two different MECs. This is likely due to the latency between EDS
>cards
>> >> > causing a trainwreck with the clocking.
>> >> > This will not be an issue to those who are not wanting to have plugin
>> >> > automation in SX. As long as SX is not slaving to the Paris timeline,
>> >the
>> >> > audio passes through the audio interface on Cubase and back to Paris
>> >with
>> >> no
>> >> > problem. If, however, you want to automate plugin parameters, you
>will
>> >> need
>> >> > both machines timeline synced so that you can write automation data
>to
>> >> > Cubase SX.
>> >> >
>> >> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
>> >> Cooper
>> >> > Datasync II unit which converts ADAT timecode to MTC and then slaving
>> >> Cubase
>> >> > SX to incoming MTC form the Datasync II.
>> >> >
>> >> > Thank goodness for yet another kludge. I thought I had finally
>succeeded
>> >> in
>> >> > accomplishing everything I started out to do and there was this
>sudden
>> >> > realization that my life would have no further purpose.
>> >> >
>> >> > ;o)
>> >> >
>> >> >
>> >>
>> >>
>> >
>>
>
|
|
|
|
| Re: UH OH!!......not good! [message #73620 is a reply to message #73602] |
Thu, 05 October 2006 11:36 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
then he'd be in my world.
On 5 Oct 2006 23:21:11 +1000, "Neil" <OIUOI@OIU.com> wrote:
>
>Martin, I'm with you & Nappy. I like tinkering, too, but at
>some stage if something gets too convoluted, you start reaching
>a point of diminishing returns. Deej, have you considered that
>part of your issue with sync/lock might be that you're going in
>& out of both machines in digital? What would happen if you
>switched to analog? I mean, you've got good convertors on both
>ends there, so I'd hardly think signal degradation would be a
>problem.
>
>Either that or just track in Paris, export the files so you can
>mix in SX (even upsample to 96k on the way in, if you must!) so
>you can use all your EFX, but use four submixes out of your
>Multiface analog outs, then back into your Paris box to sum in
>live mode. That way you get to hit those Paris convertors one
>more time, in fact. :)
>
>Heck, with most of the stuff you do (bluegrass, folkish stuff,
>etc) "clean" is good... you could live perfectly happily with
>just SX & those nice clean RME convertors.
>
>Heaven forbid! lol
>
>Neil
>
>
>"Martin Harrington" <lendan@bigpond.net.au> wrote:
>>Huh, that's funny, I didn't read Nappy's post until I sent the previous
>
>>one...
>>It's not only me that's looking after you health
>>--
>>Martin Harrington
>>www.lendanear-sound.com
>>
>>"Nappy" <mgrant01@san.rr.com> wrote in message news:45242cc2$1@linux...
>>>
>>> DJ'
>>> I'm starting to think it may be time for you to make the jump to a
>>> Dualcore
>>> intel box and
>>> 2 UAD PCI-e cards running Cubase 4. I know you have invested alot of
>time
>>> and
>>> brain power into this,lord knows I'm exhausted just reading it. I think
>
>>> you
>>> would be
>>> better using PARIS as a summing buss. At least thats what I'm coming to
>
>>> believe.
>>> I'm going to use my old B&W G3 for my PARIS system and build a Dualcore
>
>>> Intel
>>> box and run Cubase 4 and be done with it.
>>>
>>> respect
>>> Nappy
>>> "DJ" <notachance@net.net> wrote:
>>>>Hmmm......this just may not be possible to achieve. I've got both systems
>>>>clocked to the Lucid....No ADAT sync is interfaced with the RME cards.
>The
>>>>jury is still out on whether or not this is going to fly. The latency
>>>>between EDS cards and the audio being streamed from ADAT modules that
>are
>>>>clocked to those cards may be an insurmountable issue here.
>>>>Deej
>>>>
>>>>"DJ" <notachance@net.net> wrote in message news:45240fc0@linux...
>>>>> The Cubase rig just crashed while not receiving any sync info at all
>>>>between
>>>>> Paris and Cubase. Not good. I've got another trick up my sleeve. Stay
>>>>tuned.
>>>>>
>>>>>
>>>>> "DJ" <notachance@net.net> wrote in message news:45240db7@linux...
>>>>> > Further repeated testing has verified that when Paris ADAT sync output
>>>>is
>>>>> > hooked directly up to the RME audio interface ADAT sync input, if
>
>>>>> > ASIO
>>>>> > positioning protocall is selected as the Cubase sync sounce, even
>if
>>> the
>>>>> RME
>>>>> > transport is set to internal so that the Cubase transport is not
>>>>> > chasing
>>>>> the
>>>>> > Paris timeline, Cubase will crash within 5 seconds of the beginning
>>> of
>>>>an
>>>>> > audio track from Submix 2/card B/MEC 2 starting to play.
>>>>> >
>>>>> > Setting sync source in Cubase SX to MTC (with no midi interface
>>>>selected)
>>>>> so
>>>>> > that there is no interfacing between the Paris ADAT module and Cubase
>>> SX
>>>>> > works fine......no crashes of cubase SX when processing tracks from
>>>>> multiple
>>>>> > submixes in Paris.
>>>>> >
>>>>> > Thanks for you input on this Dave. Hopefully the Datasync II will
>do
>>> the
>>>>> > trick.
>>>>> >
>>>>> > Deej
>>>>> >
>>>>> >
>>>>> >
>>>>> > "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>>>>> > > OK,
>>>>> > >
>>>>> > > Before you guys start getting too exicted about this, it appears
>
>>>>> > > that
>>>>> > there
>>>>> > > is one more hoop to jump through if you are using multiple MECs.
>
>>>>> > > When
>>>>> > > looping audio from Paris *through* Cubase SX channels while Cubase
>>> SX
>>>>is
>>>>> > > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>>>>> from
>>>>> > > two different MECs. This is likely due to the latency between EDS
>>>>cards
>>>>> > > causing a trainwreck with the clocking.
>>>>> > > This will not be an issue to those who are not wanting to have
>>>>> > > plugin
>>>>> > > automation in SX. As long as SX is not slaving to the Paris
>>>>> > > timeline,
>>>>> the
>>>>> > > audio passes through the audio interface on Cubase and back to Paris
>>>>> with
>>>>> > no
>>>>> > > problem. If, however, you want to automate plugin parameters, you
>>> will
>>>>> > need
>>>>> > > both machines timeline synced so that you can write automation data
>>> to
>>>>> > > Cubase SX.
>>>>> > >
>>>>> > > I am hoping to solve this problem by sending Paris ADAT sync to
>a
>>> JL
>>>>> > Cooper
>>>>> > > Datasync II unit which converts ADAT timecode to MTC and then
>>>>> > > slaving
>>>>> > Cubase
>>>>> > > SX to incoming MTC form the Datasync II.
>>>>> > >
>>>>> > > Thank goodness for yet another kludge. I thought I had finally
>>>>succeeded
>>>>> > in
>>>>> > > accomplishing everything I started out to do and there was this
>
>>>>> > > sudden
>>>>> > > realization that my life would have no further purpose.
>>>>> > >
>>>>> > > ;o)
>>>>> > >
>>>>> > >
>>>>> >
>>>>> >
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73628 is a reply to message #73619] |
Thu, 05 October 2006 13:46 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Rick,
some UAD-1 plugins upsample the signal while processing it......the sneaky
bastards.
"rick" <parnell68@hotmail.com> wrote in message
news:mujai210kurc2or3ne8ek78h4coqmv54pi@4ax.com...
> are we talking bit rate or sample rate? i no longer have my uad card
> but thought they worked at the pre specified rate of the audio. maybe
> you can put a dummy file in sx to lock the uad sample rate to match
> the rest.
>
> On Thu, 5 Oct 2006 06:02:41 -0600, "DJ" <notachance@net.net> wrote:
>
> >Yes, they are, but the UAD-1 upsamples during processing with the
Fairchild,
> >1073, Pultec and some others.
> >
> >
> >"rick" <parnell68@hotmail.com> wrote in message
> >news:gei9i2tdu1nimf16gnf75mfl7hsb0lpb82@4ax.com...
> >> aren't all the machines set to the same sample rate?
> >>
> >> On Wed, 4 Oct 2006 22:44:51 -0600, "DJ" <notachance@net.net> wrote:
> >>
> >> >I wonder if this isn't working because some of the UAD-1 plugins (like
> >the
> >> >Neve EQ for instance) are upsampling what is essentially a Paris audio
> >file
> >> >being played *through* SX with none of the downsampling possible that
> >would
> >> >normally be part of the DSP process in SX to resolve the sample rate
of
> >the
> >> >plugin to the project sample rate/clock source. If so, that would
> >certainly
> >> >explain some things. It might also explain why the UAD-1 card with
ADAT
> >I/O
> >> >that was on the boards a few years ago went nowhere and why the POCO,
> >> >Duende, etc. do not have digital I/O and only work in a plugin format.
If
> >> >these processors were
> >> >upsampling/downsampling in real time, the SR converters/clocking
> >shenanigans
> >> >that would be necessary to bring the audio signal back to the project
> >sample
> >> >rate would put the pricepoint through the roof.
> >> >
> >> >Well.....it's just a thought........
> >> >
> >> >;O)
> >> >
> >> >Deej
> >> >
> >> >
> >> >
> >> >
> >> >"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
> >> >> Well.........I'm baffled by this and I'm just going to let it slide
for
> >a
> >> >> while. Looping audio *through* SX so that it functions as a
standalone
> >FX
> >> >> processor has been a total bust so far. OTOH, streaming tracks
directly
> >> >from
> >> >> SX (lots of them) to Paris and summing there does not create the
> >clocking
> >> >> trainwreck that looping through the inserts does. I guess it must be
> >the
> >> >> loop that is causing it as opposed to the one way trip.
> >> >>
> >> >> C'est la ****'in vie
> >> >>
> >> >> ;o)
> >> >>
> >> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >> >> > OK,
> >> >> >
> >> >> > Before you guys start getting too exicted about this, it appears
that
> >> >> there
> >> >> > is one more hoop to jump through if you are using multiple MECs.
When
> >> >> > looping audio from Paris *through* Cubase SX channels while Cubase
SX
> >is
> >> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being
looped
> >> >from
> >> >> > two different MECs. This is likely due to the latency between EDS
> >cards
> >> >> > causing a trainwreck with the clocking.
> >> >> > This will not be an issue to those who are not wanting to have
plugin
> >> >> > automation in SX. As long as SX is not slaving to the Paris
timeline,
> >> >the
> >> >> > audio passes through the audio interface on Cubase and back to
Paris
> >> >with
> >> >> no
> >> >> > problem. If, however, you want to automate plugin parameters, you
> >will
> >> >> need
> >> >> > both machines timeline synced so that you can write automation
data
> >to
> >> >> > Cubase SX.
> >> >> >
> >> >> > I am hoping to solve this problem by sending Paris ADAT sync to a
JL
> >> >> Cooper
> >> >> > Datasync II unit which converts ADAT timecode to MTC and then
slaving
> >> >> Cubase
> >> >> > SX to incoming MTC form the Datasync II.
> >> >> >
> >> >> > Thank goodness for yet another kludge. I thought I had finally
> >succeeded
> >> >> in
> >> >> > accomplishing everything I started out to do and there was this
> >sudden
> >> >> > realization that my life would have no further purpose.
> >> >> >
> >> >> > ;o)
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >>
> >
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73630 is a reply to message #73601] |
Thu, 05 October 2006 14:53 |
Don Nafe
Messages: 1206
Registered: July 2005
|
Senior Member |
|
|
I take it my suggestion didn't work
Don
"DJ" <notachance@net.net> wrote in message news:4524fa4b@linux...
> Hmmmm...........maybe so?
>
> "Don Nafe" <dnafe@magma.ca> wrote in message news:4524f895@linux...
>> Ya know I actually understood that....scarey
>>
>> would putting SX into record mode complete that circuit in the UAD?
>>
>> DOn
>>
>>
>> "DJ" <notachance@net.net> wrote in message news:45248dc6@linux...
>> >I wonder if this isn't working because some of the UAD-1 plugins (like
> the
>> > Neve EQ for instance) are upsampling what is essentially a Paris audio
>> > file
>> > being played *through* SX with none of the downsampling possible that
>> > would
>> > normally be part of the DSP process in SX to resolve the sample rate of
>> > the
>> > plugin to the project sample rate/clock source. If so, that would
>> > certainly
>> > explain some things. It might also explain why the UAD-1 card with ADAT
>> > I/O
>> > that was on the boards a few years ago went nowhere and why the POCO,
>> > Duende, etc. do not have digital I/O and only work in a plugin format.
> If
>> > these processors were
>> > upsampling/downsampling in real time, the SR converters/clocking
>> > shenanigans
>> > that would be necessary to bring the audio signal back to the project
>> > sample
>> > rate would put the pricepoint through the roof.
>> >
>> > Well.....it's just a thought........
>> >
>> > ;O)
>> >
>> > Deej
>> >
>> >
>> >
>> >
>> > "DJ" <notachance@net.net> wrote in message news:452475f8@linux...
>> >> Well.........I'm baffled by this and I'm just going to let it slide
>> >> for
> a
>> >> while. Looping audio *through* SX so that it functions as a standalone
> FX
>> >> processor has been a total bust so far. OTOH, streaming tracks
>> >> directly
>> > from
>> >> SX (lots of them) to Paris and summing there does not create the
> clocking
>> >> trainwreck that looping through the inserts does. I guess it must be
> the
>> >> loop that is causing it as opposed to the one way trip.
>> >>
>> >> C'est la ****'in vie
>> >>
>> >> ;o)
>> >>
>> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> >> > OK,
>> >> >
>> >> > Before you guys start getting too exicted about this, it appears
>> >> > that
>> >> there
>> >> > is one more hoop to jump through if you are using multiple MECs.
>> >> > When
>> >> > looping audio from Paris *through* Cubase SX channels while Cubase
>> >> > SX
>> >> > is
>> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being looped
>> > from
>> >> > two different MECs. This is likely due to the latency between EDS
> cards
>> >> > causing a trainwreck with the clocking.
>> >> > This will not be an issue to those who are not wanting to have
>> >> > plugin
>> >> > automation in SX. As long as SX is not slaving to the Paris
>> >> > timeline,
>> > the
>> >> > audio passes through the audio interface on Cubase and back to Paris
>> > with
>> >> no
>> >> > problem. If, however, you want to automate plugin parameters, you
> will
>> >> need
>> >> > both machines timeline synced so that you can write automation data
> to
>> >> > Cubase SX.
>> >> >
>> >> > I am hoping to solve this problem by sending Paris ADAT sync to a JL
>> >> Cooper
>> >> > Datasync II unit which converts ADAT timecode to MTC and then
>> >> > slaving
>> >> Cubase
>> >> > SX to incoming MTC form the Datasync II.
>> >> >
>> >> > Thank goodness for yet another kludge. I thought I had finally
>> >> > succeeded
>> >> in
>> >> > accomplishing everything I started out to do and there was this
> sudden
>> >> > realization that my life would have no further purpose.
>> >> >
>> >> > ;o)
>> >> >
>> >> >
>> >>
>> >>
>> >
>> >
>>
>>
>
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73638 is a reply to message #73630] |
Thu, 05 October 2006 17:47 |
animix
Messages: 356
Registered: September 2006
|
Senior Member |
|
|
Haven't tried it yet Don.
"Don Nafe" <dnafe@magma.ca> wrote in message news:45257cfd@linux...
> I take it my suggestion didn't work
>
> Don
>
>
> "DJ" <notachance@net.net> wrote in message news:4524fa4b@linux...
> > Hmmmm...........maybe so?
> >
> > "Don Nafe" <dnafe@magma.ca> wrote in message news:4524f895@linux...
> >> Ya know I actually understood that....scarey
> >>
> >> would putting SX into record mode complete that circuit in the UAD?
> >>
> >> DOn
> >>
> >>
> >> "DJ" <notachance@net.net> wrote in message news:45248dc6@linux...
> >> >I wonder if this isn't working because some of the UAD-1 plugins (like
> > the
> >> > Neve EQ for instance) are upsampling what is essentially a Paris
audio
> >> > file
> >> > being played *through* SX with none of the downsampling possible that
> >> > would
> >> > normally be part of the DSP process in SX to resolve the sample rate
of
> >> > the
> >> > plugin to the project sample rate/clock source. If so, that would
> >> > certainly
> >> > explain some things. It might also explain why the UAD-1 card with
ADAT
> >> > I/O
> >> > that was on the boards a few years ago went nowhere and why the POCO,
> >> > Duende, etc. do not have digital I/O and only work in a plugin
format.
> > If
> >> > these processors were
> >> > upsampling/downsampling in real time, the SR converters/clocking
> >> > shenanigans
> >> > that would be necessary to bring the audio signal back to the project
> >> > sample
> >> > rate would put the pricepoint through the roof.
> >> >
> >> > Well.....it's just a thought........
> >> >
> >> > ;O)
> >> >
> >> > Deej
> >> >
> >> >
> >> >
> >> >
> >> > "DJ" <notachance@net.net> wrote in message news:452475f8@linux...
> >> >> Well.........I'm baffled by this and I'm just going to let it slide
> >> >> for
> > a
> >> >> while. Looping audio *through* SX so that it functions as a
standalone
> > FX
> >> >> processor has been a total bust so far. OTOH, streaming tracks
> >> >> directly
> >> > from
> >> >> SX (lots of them) to Paris and summing there does not create the
> > clocking
> >> >> trainwreck that looping through the inserts does. I guess it must be
> > the
> >> >> loop that is causing it as opposed to the one way trip.
> >> >>
> >> >> C'est la ****'in vie
> >> >>
> >> >> ;o)
> >> >>
> >> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
> >> >> > OK,
> >> >> >
> >> >> > Before you guys start getting too exicted about this, it appears
> >> >> > that
> >> >> there
> >> >> > is one more hoop to jump through if you are using multiple MECs.
> >> >> > When
> >> >> > looping audio from Paris *through* Cubase SX channels while Cubase
> >> >> > SX
> >> >> > is
> >> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being
looped
> >> > from
> >> >> > two different MECs. This is likely due to the latency between EDS
> > cards
> >> >> > causing a trainwreck with the clocking.
> >> >> > This will not be an issue to those who are not wanting to have
> >> >> > plugin
> >> >> > automation in SX. As long as SX is not slaving to the Paris
> >> >> > timeline,
> >> > the
> >> >> > audio passes through the audio interface on Cubase and back to
Paris
> >> > with
> >> >> no
> >> >> > problem. If, however, you want to automate plugin parameters, you
> > will
> >> >> need
> >> >> > both machines timeline synced so that you can write automation
data
> > to
> >> >> > Cubase SX.
> >> >> >
> >> >> > I am hoping to solve this problem by sending Paris ADAT sync to a
JL
> >> >> Cooper
> >> >> > Datasync II unit which converts ADAT timecode to MTC and then
> >> >> > slaving
> >> >> Cubase
> >> >> > SX to incoming MTC form the Datasync II.
> >> >> >
> >> >> > Thank goodness for yet another kludge. I thought I had finally
> >> >> > succeeded
> >> >> in
> >> >> > accomplishing everything I started out to do and there was this
> > sudden
> >> >> > realization that my life would have no further purpose.
> >> >> >
> >> >> > ;o)
> >> >> >
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >>
> >>
> >
> >
>
>
>
|
|
|
|
| Re: AHhhh.........HA!!! [message #73645 is a reply to message #73628] |
Fri, 06 October 2006 02:48 |
rick
Messages: 1976
Registered: February 2006
|
Senior Member |
|
|
well, that's almost as dumb as me.
On Thu, 5 Oct 2006 14:46:25 -0600, "DJ" <notachance@net.net> wrote:
>Rick,
>
>some UAD-1 plugins upsample the signal while processing it......the sneaky
>bastards.
>
>"rick" <parnell68@hotmail.com> wrote in message
>news:mujai210kurc2or3ne8ek78h4coqmv54pi@4ax.com...
>> are we talking bit rate or sample rate? i no longer have my uad card
>> but thought they worked at the pre specified rate of the audio. maybe
>> you can put a dummy file in sx to lock the uad sample rate to match
>> the rest.
>>
>> On Thu, 5 Oct 2006 06:02:41 -0600, "DJ" <notachance@net.net> wrote:
>>
>> >Yes, they are, but the UAD-1 upsamples during processing with the
>Fairchild,
>> >1073, Pultec and some others.
>> >
>> >
>> >"rick" <parnell68@hotmail.com> wrote in message
>> >news:gei9i2tdu1nimf16gnf75mfl7hsb0lpb82@4ax.com...
>> >> aren't all the machines set to the same sample rate?
>> >>
>> >> On Wed, 4 Oct 2006 22:44:51 -0600, "DJ" <notachance@net.net> wrote:
>> >>
>> >> >I wonder if this isn't working because some of the UAD-1 plugins (like
>> >the
>> >> >Neve EQ for instance) are upsampling what is essentially a Paris audio
>> >file
>> >> >being played *through* SX with none of the downsampling possible that
>> >would
>> >> >normally be part of the DSP process in SX to resolve the sample rate
>of
>> >the
>> >> >plugin to the project sample rate/clock source. If so, that would
>> >certainly
>> >> >explain some things. It might also explain why the UAD-1 card with
>ADAT
>> >I/O
>> >> >that was on the boards a few years ago went nowhere and why the POCO,
>> >> >Duende, etc. do not have digital I/O and only work in a plugin format.
>If
>> >> >these processors were
>> >> >upsampling/downsampling in real time, the SR converters/clocking
>> >shenanigans
>> >> >that would be necessary to bring the audio signal back to the project
>> >sample
>> >> >rate would put the pricepoint through the roof.
>> >> >
>> >> >Well.....it's just a thought........
>> >> >
>> >> >;O)
>> >> >
>> >> >Deej
>> >> >
>> >> >
>> >> >
>> >> >
>> >> >"DJ" <notachance@net.net> wrote in message news:452475f8@linux...
>> >> >> Well.........I'm baffled by this and I'm just going to let it slide
>for
>> >a
>> >> >> while. Looping audio *through* SX so that it functions as a
>standalone
>> >FX
>> >> >> processor has been a total bust so far. OTOH, streaming tracks
>directly
>> >> >from
>> >> >> SX (lots of them) to Paris and summing there does not create the
>> >clocking
>> >> >> trainwreck that looping through the inserts does. I guess it must be
>> >the
>> >> >> loop that is causing it as opposed to the one way trip.
>> >> >>
>> >> >> C'est la ****'in vie
>> >> >>
>> >> >> ;o)
>> >> >>
>> >> >> "DJ" <notachance@net.net> wrote in message news:452403c4@linux...
>> >> >> > OK,
>> >> >> >
>> >> >> > Before you guys start getting too exicted about this, it appears
>that
>> >> >> there
>> >> >> > is one more hoop to jump through if you are using multiple MECs.
>When
>> >> >> > looping audio from Paris *through* Cubase SX channels while Cubase
>SX
>> >is
>> >> >> > slaved to Paris ADAT sync, Cubase crashes once audio is being
>looped
>> >> >from
>> >> >> > two different MECs. This is likely due to the latency between EDS
>> >cards
>> >> >> > causing a trainwreck with the clocking.
>> >> >> > This will not be an issue to those who are not wanting to have
>plugin
>> >> >> > automation in SX. As long as SX is not slaving to the Paris
>timeline,
>> >> >the
>> >> >> > audio passes through the audio interface on Cubase and back to
>Paris
>> >> >with
>> >> >> no
>> >> >> > problem. If, however, you want to automate plugin parameters, you
>> >will
>> >> >> need
>> >> >> > both machines timeline synced so that you can write automation
>data
>> >to
>> >> >> > Cubase SX.
>> >> >> >
>> >> >> > I am hoping to solve this problem by sending Paris ADAT sync to a
>JL
>> >> >> Cooper
>> >> >> > Datasync II unit which converts ADAT timecode to MTC and then
>slaving
>> >> >> Cubase
>> >> >> > SX to incoming MTC form the Datasync II.
>> >> >> >
>> >> >> > Thank goodness for yet another kludge. I thought I had finally
>> >succeeded
>> >> >> in
>> >> >> > accomplishing everything I started out to do and there was this
>> >sudden
>> >> >> > realization that my life would have no further purpose.
>> >> >> >
>> >> >> > ;o)
>> >> >> >
>> >> >> >
>> >> >>
>> >> >>
>> >> >
>> >>
>> >
>>
>
|
|
|
|
Goto Forum:
Current Time: Wed Nov 13 17:38:26 PST 2024
Total time taken to generate the page: 0.03057 seconds
|
The PARIS Forums
Search
Help
Members
Register
Login
Home
