The PARIS Forums: PARIS: Main » OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4

Home » The PARIS Forums » PARIS: Main » OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4

Show: Today's Messages :: Polls :: Message Navigator

OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4 [message #80734]

Mon, 26 February 2007 20:19

Deej [4]

Messages: 1292
Registered: January 2007

Senior Member

After jacking around with the Cubase 4 cue mix studio sends, etc. stuff, I
have found it overly complicated and generally redundant when interfacing
with the cue mix system I have here. The Furman HDS 16 will allow 16
simultaneous inputs and cubase will allow more than one source to a single
output. I have external reverbs on each of the remote mixers so tracking
with FX isn't an issue.

It's much easier to just create a mix template that busses mono or stereo
inputs directly to mono or stereo outs and then any tracks that are already
recorded and used as reference for dubs are just put on a stereo bus and
sent to a submix bus stereo out which is routed to the Furman main stereo
input and sent to the cans. Using ASIO direct monitoring, I just tracked 18
inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME
beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the
buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage
drops to around 10-15%. I like having that kind of headroom.

This is good news. Lots has been going on here behind the scenes and I
haven't had much time to get my head around how I would track big projects.
I'm getting musicians lined up for some upcoming sessions and I want4ed
things to run smoothly. This is easier than doing it with Paris using auxes
with my particular cue system..I don't have much experience with this native
stuff and I was sorta dreading hitting the latency wall. Doesn't look like
that will happen if I'm careful, especially with a slave DAW handling VSTi
chores.

This ASIO direct monitoring stuff is nice amd punching in/out is simple and
smooth with this system.

(breathing sigh of relief)

Deej

Report message to a moderator

Re: OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4 [message #80739 is a reply to message #80734]

Mon, 26 February 2007 23:27

Neil
Messages: 1645
Registered: April 2006

Senior Member

Deej, which RME driver is it that you're using? Got a link you
can point me to? Sounds like it might be a newer one than the
one I've got loaded.

Neil

"DJ" <www.aarrrrggghhh!!!.com> wrote:
>After jacking around with the Cubase 4 cue mix studio sends, etc. stuff,
I
>have found it overly complicated and generally redundant when interfacing

>with the cue mix system I have here. The Furman HDS 16 will allow 16
>simultaneous inputs and cubase will allow more than one source to a single

>output. I have external reverbs on each of the remote mixers so tracking

>with FX isn't an issue.
>
>It's much easier to just create a mix template that busses mono or stereo

>inputs directly to mono or stereo outs and then any tracks that are already

>recorded and used as reference for dubs are just put on a stereo bus and

>sent to a submix bus stereo out which is routed to the Furman main stereo

>input and sent to the cans. Using ASIO direct monitoring, I just tracked
18
>inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME

>beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the

>buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage

>drops to around 10-15%. I like having that kind of headroom.
>
>This is good news. Lots has been going on here behind the scenes and I
>haven't had much time to get my head around how I would track big projects.

>I'm getting musicians lined up for some upcoming sessions and I want4ed

>things to run smoothly. This is easier than doing it with Paris using auxes

>with my particular cue system..I don't have much experience with this native

>stuff and I was sorta dreading hitting the latency wall. Doesn't look like

>that will happen if I'm careful, especially with a slave DAW handling VSTi

>chores.
>
>This ASIO direct monitoring stuff is nice amd punching in/out is simple
and
>smooth with this system.
>
>(breathing sigh of relief)
>
>Deej
>
>

Report message to a moderator

Re: OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4 [message #80746 is a reply to message #80739]

Tue, 27 February 2007 06:21

Deej [4]

Messages: 1292
Registered: January 2007

Senior Member

Here's beta20

http://www.rme-audio.com/download/hdsp_wdm_beta20.zip

It's the final release candidate.

As usual, ghost is your friend. You may need to updateyour firmware first.

Deej

"Neil" <OIUOI@OI.com> wrote in message news:45e3cf49$1@linux...
>
> Deej, which RME driver is it that you're using? Got a link you
> can point me to? Sounds like it might be a newer one than the
> one I've got loaded.
>
> Neil
>
>
> "DJ" <www.aarrrrggghhh!!!.com> wrote:
>>After jacking around with the Cubase 4 cue mix studio sends, etc. stuff,
> I
>>have found it overly complicated and generally redundant when interfacing
>
>>with the cue mix system I have here. The Furman HDS 16 will allow 16
>>simultaneous inputs and cubase will allow more than one source to a single
>
>>output. I have external reverbs on each of the remote mixers so tracking
>
>>with FX isn't an issue.
>>
>>It's much easier to just create a mix template that busses mono or stereo
>
>>inputs directly to mono or stereo outs and then any tracks that are
>>already
>
>>recorded and used as reference for dubs are just put on a stereo bus and
>
>>sent to a submix bus stereo out which is routed to the Furman main stereo
>
>>input and sent to the cans. Using ASIO direct monitoring, I just tracked
> 18
>>inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME
>
>>beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the
>
>>buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage
>
>>drops to around 10-15%. I like having that kind of headroom.
>>
>>This is good news. Lots has been going on here behind the scenes and I
>>haven't had much time to get my head around how I would track big
>>projects.
>
>>I'm getting musicians lined up for some upcoming sessions and I want4ed
>
>>things to run smoothly. This is easier than doing it with Paris using
>>auxes
>
>>with my particular cue system..I don't have much experience with this
>>native
>
>>stuff and I was sorta dreading hitting the latency wall. Doesn't look like
>
>>that will happen if I'm careful, especially with a slave DAW handling VSTi
>
>>chores.
>>
>>This ASIO direct monitoring stuff is nice amd punching in/out is simple
> and
>>smooth with this system.
>>
>>(breathing sigh of relief)
>>
>>Deej
>>
>>
>

Report message to a moderator

Re: OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4 [message #80749 is a reply to message #80739]

Tue, 27 February 2007 06:34

Deej [4]

Messages: 1292
Registered: January 2007

Senior Member

Neil.........here's beta19.

http://www.rme-audio.com/download/hdsp_wdm_beta19.zip

This is the one I'm running. Looks like beta20 is giving some people fits
over on the RME forum. Anyway, like I said, ghost is always your friend.

Deek

"Neil" <OIUOI@OI.com> wrote in message news:45e3cf49$1@linux...
>
> Deej, which RME driver is it that you're using? Got a link you
> can point me to? Sounds like it might be a newer one than the
> one I've got loaded.
>
> Neil
>
>
> "DJ" <www.aarrrrggghhh!!!.com> wrote:
>>After jacking around with the Cubase 4 cue mix studio sends, etc. stuff,
> I
>>have found it overly complicated and generally redundant when interfacing
>
>>with the cue mix system I have here. The Furman HDS 16 will allow 16
>>simultaneous inputs and cubase will allow more than one source to a single
>
>>output. I have external reverbs on each of the remote mixers so tracking
>
>>with FX isn't an issue.
>>
>>It's much easier to just create a mix template that busses mono or stereo
>
>>inputs directly to mono or stereo outs and then any tracks that are
>>already
>
>>recorded and used as reference for dubs are just put on a stereo bus and
>
>>sent to a submix bus stereo out which is routed to the Furman main stereo
>
>>input and sent to the cans. Using ASIO direct monitoring, I just tracked
> 18
>>inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME
>
>>beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the
>
>>buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage
>
>>drops to around 10-15%. I like having that kind of headroom.
>>
>>This is good news. Lots has been going on here behind the scenes and I
>>haven't had much time to get my head around how I would track big
>>projects.
>
>>I'm getting musicians lined up for some upcoming sessions and I want4ed
>
>>things to run smoothly. This is easier than doing it with Paris using
>>auxes
>
>>with my particular cue system..I don't have much experience with this
>>native
>
>>stuff and I was sorta dreading hitting the latency wall. Doesn't look like
>
>>that will happen if I'm careful, especially with a slave DAW handling VSTi
>
>>chores.
>>
>>This ASIO direct monitoring stuff is nice amd punching in/out is simple
> and
>>smooth with this system.
>>
>>(breathing sigh of relief)
>>
>>Deej
>>
>>
>

Report message to a moderator

Re: OT........sorta'.....but increasingly sorta' not........tracking at low latency in Cubase 4 [message #80759 is a reply to message #80734]

Tue, 27 February 2007 14:49

LaMont
Messages: 828
Registered: October 2005

Senior Member

Hey DJ, well (my friend), this is why I added a mixer to the "whole" native
equation (for Tracking) ... :)

makes life so much easier when tracking & monitoring. As well as, I can use
my hardware like it was meant to be used.

This is where Paris & Pro Tools excel. Their patch bay routing is in another
league!! Pro Tools routing set up is really one it's greatest assets. Save
whole scale inputs and outputs and naming them for future use..

I hope that Steinberg continues to open up the VST platoform to allow for
more easy and flexible routing..
LAD

"DJ" <www.aarrrrggghhh!!!.com> wrote:
>After jacking around with the Cubase 4 cue mix studio sends, etc. stuff,
I
>have found it overly complicated and generally redundant when interfacing

>with the cue mix system I have here. The Furman HDS 16 will allow 16
>simultaneous inputs and cubase will allow more than one source to a single

>output. I have external reverbs on each of the remote mixers so tracking

>with FX isn't an issue.
>
>It's much easier to just create a mix template that busses mono or stereo

>inputs directly to mono or stereo outs and then any tracks that are already

>recorded and used as reference for dubs are just put on a stereo bus and

>sent to a submix bus stereo out which is routed to the Furman main stereo

>input and sent to the cans. Using ASIO direct monitoring, I just tracked
18
>inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME

>beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the

>buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage

>drops to around 10-15%. I like having that kind of headroom.
>
>This is good news. Lots has been going on here behind the scenes and I
>haven't had much time to get my head around how I would track big projects.

>I'm getting musicians lined up for some upcoming sessions and I want4ed

>things to run smoothly. This is easier than doing it with Paris using auxes

>with my particular cue system..I don't have much experience with this native

>stuff and I was sorta dreading hitting the latency wall. Doesn't look like

>that will happen if I'm careful, especially with a slave DAW handling VSTi

>chores.
>
>This ASIO direct monitoring stuff is nice amd punching in/out is simple
and
>smooth with this system.
>
>(breathing sigh of relief)
>
>Deej
>
>

Report message to a moderator

Re: OT........sorta'.....but increasingly sorta' not........trackingat low latency in Cubase 4 [message #80763 is a reply to message #80759]

Tue, 27 February 2007 14:56

EK Sound

Messages: 939
Registered: June 2005

Senior Member

COUGH, COUGH... ;-)

David.

LaMont wrote:
> Hey DJ, well (my friend), this is why I added a mixer to the "whole" native
> equation (for Tracking) ... :)
>
> makes life so much easier when tracking & monitoring. As well as, I can use
> my hardware like it was meant to be used.
>
> This is where Paris & Pro Tools excel. Their patch bay routing is in another
> league!! Pro Tools routing set up is really one it's greatest assets. Save
> whole scale inputs and outputs and naming them for future use..
>
> I hope that Steinberg continues to open up the VST platoform to allow for
> more easy and flexible routing..
> LAD
>
>
> "DJ" <www.aarrrrggghhh!!!.com> wrote:
>
>>After jacking around with the Cubase 4 cue mix studio sends, etc. stuff,
>
> I
>
>>have found it overly complicated and generally redundant when interfacing
>
>
>>with the cue mix system I have here. The Furman HDS 16 will allow 16
>>simultaneous inputs and cubase will allow more than one source to a single
>
>
>>output. I have external reverbs on each of the remote mixers so tracking
>
>
>>with FX isn't an issue.
>>
>>It's much easier to just create a mix template that busses mono or stereo
>
>
>>inputs directly to mono or stereo outs and then any tracks that are already
>
>
>>recorded and used as reference for dubs are just put on a stereo bus and
>
>
>>sent to a submix bus stereo out which is routed to the Furman main stereo
>
>
>>input and sent to the cans. Using ASIO direct monitoring, I just tracked
>
> 18
>
>>inputs to a Cubase 4 project at 0.7 ms latency (32k buffer) using the RME
>
>
>>beta19 driver. CPU usage on the Cubase meter was around 35-40%. Drop the
>
>
>>buffers to 1.5ms latency (64k buffer-still inaudible) and the CPU usage
>
>
>>drops to around 10-15%. I like having that kind of headroom.
>>
>>This is good news. Lots has been going on here behind the scenes and I
>>haven't had much time to get my head around how I would track big projects.
>
>
>>I'm getting musicians lined up for some upcoming sessions and I want4ed
>
>
>>things to run smoothly. This is easier than doing it with Paris using auxes
>
>
>>with my particular cue system..I don't have much experience with this native
>
>
>>stuff and I was sorta dreading hitting the latency wall. Doesn't look like
>
>
>>that will happen if I'm careful, especially with a slave DAW handling VSTi
>
>
>>chores.
>>
>>This ASIO direct monitoring stuff is nice amd punching in/out is simple
>
> and
>
>>smooth with this system.
>>
>>(breathing sigh of relief)
>>
>>Deej
>>
>>
>
>

Report message to a moderator

Previous Topic:	the next CD I buy
Next Topic:	FS Paris Gear

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Mon Jun 09 23:37:59 PDT 2025

Total time taken to generate the page: 0.04046 seconds