forumhome :: pariswiki :: parisblog :: mikeaudet :: thesoniq :: thePARISmap :: gearslutz :: reaper
The PARIS Forums


Home » The PARIS Forums » PARIS: Main » Cubase control room.....
Cubase control room..... [message #97372] Sat, 22 March 2008 19:52 Go to previous message
Deej [5] is currently offline  Deej [5]
Messages: 373
Registered: March 2008
Senior Member
This is a multi-part message in MIME format.

------=_NextPart_000_0016_01C88C5E.9E03E910
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

"I think" my little dual opteron 185 is gonna have plenty of horsepower =
to track 20 inputs simultaneously at 3ms latency. Any further tracking =
would be dubbing maybe 1 or two tracks while playing back the =
prerecorded tracks. this also looks pretty simple if I'm not using a =
heavy load of UAD-1 plugins. If I were to use them, I can disable them =
all for dubs in the UA control panel.=20

I'll tell you what........if I can get this CR function going and it's =
working nicely, and if you can find the mobo I use, this will be a very =
powerful, UAD-1/Powercore w/ Magma DSP friendly and economic DAW to =
build for a native system. I'm slamming the PCI bus with 9 devices ( 4 x =
UAD-1's, 2 POCO's and 3 RME HDSP cards) during mixdown cramming enough =
bandwidth through the bus to choke an elephant and the NForce chipset =
just shrugs it off. I can playback 40 tracks with a 90% UAD-1 DSP usage, =
a 90% POCO usage on two cards and a respectable number of native plugins =
at 1024 buffers when I'm mixing with no dropouts.=20

I'm digging this DAW. I just didn't think it had the capabilities to =
really function efficiently with Cubase Control Room and never really =
tried it because I had a monster cue system in place before Cubase 4 =
came out.=20

I may have have misunderestimated the capabilities of this system. I =
don't quite have my head around the CR function yet though. For some =
reason, I'm not hearing the input signal in the cans, though the click =
is working.=20

Crap!!! I guess I'm actually gonna have to RTFM

If I can satisfy myself that this will work reliably, I'll post up my =
specs in detail here in case someone wants to build a relatively =
inexpensive native DAW with lots of potential.

;)
------=_NextPart_000_0016_01C88C5E.9E03E910
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.6000.16608" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>"I think" my little dual opteron 185 is =
gonna have=20
plenty of horsepower to track 20 inputs simultaneously at 3ms latency. =
Any=20
further tracking would be dubbing maybe 1 or two tracks while playing =
back the=20
prerecorded tracks. this also looks pretty simple if I'm not using a =
heavy load=20
of UAD-1 plugins.&nbsp;If I were to use them, I can disable them all for =
dubs in=20
the UA control panel. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'll tell you what........if I can get =
this CR=20
function going and it's working nicely,&nbsp;and if you can find the =
mobo I use,=20
this will be a very powerful, UAD-1/Powercore w/ Magma DSP =
friendly&nbsp;and=20
economic DAW to build for a native system. I'm slamming the PCI bus =
with&nbsp;9=20
devices (&nbsp;4 x UAD-1's, 2 POCO's and 3 RME HDSP cards) during =
mixdown=20
cramming enough bandwidth through the bus to choke an elephant and the =
NForce=20
chipset just shrugs it off. I can playback 40 tracks with a 90% UAD-1 =
DSP usage,=20
a 90% POCO usage on two cards and a respectable number of native plugins =
at 1024=20
buffers when I'm mixing with no dropouts. </FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I'm digging this DAW. I just didn't =
think it had=20
the capabilities to really function efficiently with Cubase Control Room =
and=20
never really tried it because I had a monster cue system in place before =
Cubase=20
4 came out.&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I may have have =
<EM>misunderestimated</EM> the=20
capabilities of this system. I don't quite have my head around the CR =
function=20
yet though. For some reason, I'm not hearing the input signal in the =
cans,=20
though the click is working.&nbsp;</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Crap!!! I guess I'm actually gonna have =
to=20
RTFM</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>If I can satisfy myself that this will =
work=20
reliably, I'll post up my specs in detail here in case someone wants to =
build a=20
relatively inexpensive native DAW with lots of potential.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>;)</FONT></DIV></BODY></HTML>

------=_NextPart_000_0016_01C88C5E.9E03E910--

Report message to a moderator

[Message index]
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Harvard...masters of the obvious
Next Topic: I'm gonna get me some of these
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Thu May 30 13:51:05 PDT 2024

Total time taken to generate the page: 0.01661 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.1.0.
Copyright ©2001-2020 FUDforum Bulletin Board Software