Hi Nick:
I see the same sort of issue (intermittant - same error message,
horizontal blue line funkiness) working with AMA-linked R3D clips. In
my case, I am working with clips on an internal drive. I associate it
with having many bins open with large numbers of AMA files, or long
AMA-linked sequences. I suspect it's a symptom of running low on memory
-- AMA looks like a real memory hog.
Keep an eye on the percentage memory use in your project window. If
you can, I would try dividing your material into shorter sequences,more
bins with fewer clips in them, having fewer bins open at once, clearing
the menus in your source and record monitors, and of course, transcoding
to a native codec for real work.
Cheers,
--Michael
On 11-03-30 1:08 PM, nick_ravich wrote:
>
> Hello-
>
> Running MC5 on 2.66 & 2.93 GHz 8-core Mac Pros, OS 10.6.
>
> Recently shot our first batch of Xdcam HD footage - 1080/60i MPEG
> HDD422 50 mbps - and have kinda sucessfully ingested into Avid, off an
> external drive using, AMA volume link.
>
> Kind of sucessfully bec/ it's oddly intermitent - after a couple of
> failed attempts at ingesting (see below about repaired drive), I was
> able to get AMA volume link to work. Media appeared in bins & played
> back in app. But over time - say 2 or 3 launches of the app - it
> starts to get increasingly wonky. I've brought in 4 optical disks
> worth of media, into 4 separate bins. At certain point app won't let
> me open some of the bins and I get an "Exception: Failed to get the
> same temporal offset from the AMA Plug-in" error message. Also, the
> clips in the bins I can open play back really funkily, with odd
> horizontal blue line patterns.
>
> Also unsucessful in playing this footage in XDcam clipbrowser (though
> it will recognize my XDcam EX stuff.)
>
> Again, I'm linking directly from an external drive (to which the
> original optical disk media had been transferred.) Know that there was
> an issue with original field drive transfer to this working drive; one
> of the optical disk media sets/folders failed to transfer. I did a
> disk repair on the field drive and it seemed to correct itself. Is it
> possible there's some fatally corrupt bit of media that's messing
> things up?
>
> I assume it's not a case of a missing driver - since there's on other
> hardware besides the external drive involved. And the XDcam HD plug in
> is pre-installed. Will latest patch help? A responder to a previous
> related post suggested the below.
>
> Thanks,
>
> Nick.
>
> Here are the best guides:
> http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=367205
>
> and
> http://www.avid.com/ama
>
> and there are many, very good xdcam tutorial videos in my
> http://www.freddylinks.com pdf
>
> Make sure you have the correct OS:
> http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=267087
>
> The latest version, and MC patch: 5.0.x = 5.0.3.8 latest
> http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=379435
>
> The correct XDCAM, EX drivers (see readme Page 22 for the the version
> you have)
> http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=370951
> And that you don't have cabling issues, those could be trickier to solve.
>
> ..and I almost forgot this classic: Repair permissions
> http://avid.custkb.com/avid/app/selfservice/search.jsp?DocId=271837
>
>
[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