Same exact file names on the NAS, linked up fine after they were moved off ISIS. Lion based editors won't link AT ALL. Not even a file name like... 1.jpg. We just went through all this fun last week- We made Bill, and Avid aware- but we've pressed forward with the non-Avid NAS.
JDS
--- In Avid-L2@yahoogroups.com, "Dom Q. Silverio" <domqsilverio@...> wrote:
>
> We could not get it to work with ISIS 3.x with Snow Leopard clients unless
> the file name was abbreviated substantially, even using generic NAS. Bill
> said that the 64 bit version fixes the issue.
>
>
>
> Dom Q. Silverio
>
>
> On Tue, Dec 4, 2012 at 11:42 AM, jeffsengpiehl <jeffsengpiehl@...>wrote:
>
> > Moving Picture will not work with ISIS 4.0or 4.1 on Lion or Mountain Lion
> > based Avid's. PC's, no problem. Snow Leopard, no Problem. We've
> > gone with an non-Avid NAS setup to support Moving Picture.
> >
> > JDS
> >
> > --- In Avid-L2@yahoogroups.com, "Dom Q. Silverio" <domqsilverio@>
> > wrote:
> > >
> > > I am unsure what this ACSR is referring to but we have several ISIS in
> > > operation supporting PCs and Macs (Avid and FCP) using Sapphire, Boris CC
> > > and MovingPicture.
> > >
> > > Moving Picture requires the 64 bit, because the 32 bit cannot handle
> > > certain network paths (the same issue appears with consumer NAS).
> > >
> > > It may be certain plugins cannot handle certain network paths?
> > >
> > >
> > > DQS
> > >
> > > Dom Q. Silverio
> > >
> > >
> > > On Tue, Dec 4, 2012 at 11:09 AM, Steve Hullfish <steve4lists@>wrote:
> > >
> > > > From another thread, I asked whether DS is incompatible with ISIS.
> > (which
> > > > is something I heard)
> > > >
> > > > The other incompatibility that I heard about with ISIS is that plugins
> > > > really screw it up. I can't believe this is true. Again the ACSR
> > strongly
> > > > advised NOT to load any plugins onto ISIS connected MC6.5 machines. The
> > > > ISIS is brand new (actually hasn't been delivered yet). The ACSR said
> > > > plugins only work on ISIS if you do a mixdown of EVERYTHING, even if
> > ALL
> > > > networked MCs have the IDENTICAL plugins. This sounds very bad. Plug
> > ins
> > > > are critical and ISIS is critical to many installations, so how can
> > this
> > > > be? Can anyone with concrete experience shed any light on using 3rd
> > party
> > > > plugins (Baselight, Sapphire, Boris BCC, Tiffen) with MC 6.5 and the
> > latest
> > > > rev of ISIS?
> > > >
> > > > While I have that select audience's attention, what best-practices do
> > you
> > > > use with ISIS for storing and sharing Avid projects?
> > > >
> > > > Steve Hullfish
> > > > contributor: www.provideocoalition.com
> > > > author: "The Art and Technique of Digital Color Correction"
> > > >
> > > > ------------------------------------
> > > >
> > > > Search the official Complete Avid-L archives at:
> > > > http://archives.bengrosser.com/avid/
> > > > Yahoo! Groups Links
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > [Non-text portions of this message have been removed]
> > >
> >
> >
> >
> >
> > ------------------------------------
> >
> > Search the official Complete Avid-L archives at:
> > http://archives.bengrosser.com/avid/
> > Yahoo! Groups Links
> >
> >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (5) |
No comments:
Post a Comment