John,
We'll need a clarification of your system. MN v4.0 & 4.1 were limited to
2GB connectivity. MN 4.2 was 4GB, and supported higher bandwidth. There
never was a v4.5. As far as supporting only 1 client, that is conditional.
Avid differentiates between "Finishing" and "Non-finishing" clients. This
is based on resolution and stream count. They have documentation that
explains how these are defined, and how many clients various Unity
configurations can support. How many and what type of crates of drives do
you have? And, do you know how many Allocation Groups those drives are
split into? In many scenarios, bandwidth only allows 1 "Finishing" client
per Allocation Group, or crate of drives. It might be that you've been
lucky. Meanwhile, outputting from one system is fewer streams that multiple
systems rendering. "Š Am I wrong to think that with rendering the system
could just delay the render process Š". Apparently so.
Best regards,
Randy
*************************************
Randall L. Rike, ACI, ACSR Mac€Win€Unity€ISIS€DS
(818) 406-8480 Mobile
IndyPix4U@PortablePost.com
From: John Moore <bigfish@pacbell.net>
Reply-To: Avid-L2 <Avid-L2@yahoogroups.com>
Date: Fri, 9 Sep 2011 15:53:50 -0700 (PDT)
To: Avid-L2 <Avid-L2@yahoogroups.com>
Subject: [Avid-L2] Avid Unity 4.5.12 ish DNX 220?
I've been working on an older unity version 4.5.12 ish so I'm told. We just
did several projects and DNX220X and had some issues with some of the
clients dropping out and losing server contact. I was able to output to
HDCamSR with no stalls to speak of. I'm now on an DNX220 project and when I
try to render in multiple bays they all seem to go belly up after a few safe
color limit renders. The symphony keeps on chugging without issue when the
mc soft stations choke. We've rebooted the unity and power cycled the vixel
switches. I'm told by the AE that for DNX220X Avid says this unit can only
support 1 client. Clearly we've been pushing the system but how come I can
output to tape without a hitch but can't have multiple bays rendering. Am I
wrong to think that with rendering the system could just delay the render
process until the data comes down the pipe if there is a bottleneck caused
by inadequate bandwidth on the system. I remember in
the past the Avid didn't like importing from a slow source and would often
require moving the source to the avid's desktop to get it to import. Is
rendering like this too. I know we're pushing the system but for renders I
don't understand why something I would think can take its' time would cause
unity client issues and stalled and incomplete renders especially when I can
digital cut without a hitch. Perhaps I've just been lucky on my outputs so
far.
John Moore
Barking Trout Productions
Studio City, CA
bigfish@pacbell.net <mailto:bigfish%40pacbell.net>
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
If you want to donate to Red Cross quake relief, you can do so through your cell phone. Text redcross to 90999 to make a $10 donation. It will be on your next cell bill.
No comments:
Post a Comment