That seems to be standard behavior. The way we and many others approach that is to assign the bin name to the tape name when you link to ama. Usually the bin name is the folder name the media is in which should represent the card/disk the media came from. For some reason when I ama to the Red R3D files the bin gets the volume name which is the hard drive on my laptop and not the folder name. There may be a preference I have to change. Once you assign the tape name and transcode then when you go back to remount the ama clips for uprez you just add the same tape name and relink. That seems to be working for us in our limit ama endeavors. With Red it's looking like the suggestion to stay either all ama or all RCX makes a lot of sense. So far the ama route seems to be the most straight forward for us.
--- In Avid-L2@yahoogroups.com, Michael Brockington <brocking@...> wrote:
>
> Something that I ran into with assigning tape names to AMA RED clips:
> if you have to relink your AMA files (if they go offline for some
> reason) this would clobber the tapenames I had assigned. You might want
> to check if this still happens.
>
> Cheers,
> --Michael
>
> On 12-04-29 7:30 PM, johnrobmoore wrote:
> >
> > I took my Red Test Files and used RedCineX Pro to export mxf files and
> > an aaf. It seems like I ended up with a bonus ale in the target folder
> > or perhaps I accidentally hit one of the other buttons to generate an
> > ale. The aaf worked on my sndx 4.0.5 mac system. Comparing the RCX
> > generated files to the ama transcodes from the AE station with mcsoft
> > 5.5 the blacks are elevated and the highs are a little lower. Blacks
> > that are close to 0 on the ama clips are close to 100 millvolts on the
> > RCX clips. I left the "M" choice on the level choices and Red Gamma
> > etc... at what they are defaulted to in RCX. This was a fresh RedCineX
> > install as the older builds I had did not support 29.97 dnx. Funny on
> > launching the fresh install it told be there was an upgrade which I
> > said yes to. One thing I found was the aaf clips imported would not
> > allow me to alter the tape name no matter what I tried. I could
> > however rename the tape name on the ama transcoded clips to matc h
> > those of the ama and I could then relink my test sequence to the aaf'd
> > clips. If I cut a sequence with the aaf'd clips that matched the test
> > sequence if I then decomposed it I could rename the tape name to match
> > the original ama'd transcoded clips and then I could relink to the ama
> > media. So far the ama route seems the best image with the least amount
> > of futzing. With the aaf RCX route the tape name became the clip name
> > is this something that could be changed? I will have to dig a little
> > deeper. I would have thought clicking the "M" choice instead of "D"
> > would translate the camera metadata just like we did with the ama
> > settings in the Avid transcode but there is a definate difference in
> > levels between the two sets of media. Is there another generic pass
> > through the camera metadata settings in RCX I'm missing?
> >
> > --- In Avid-L2@yahoogroups.com <mailto:Avid-L2%40yahoogroups.com>,
> > "Terence Curren" <tcurren@> wrote:
> > >
> > > Test it.
> > >
> > > I can tell you that if the files are imported originally, I have to
> > go the EDL, RedCineX conform, retranscode at higher rez, drop media in
> > and import AAF, then relink route.
> > >
> > > --- In Avid-L2@yahoogroups.com <mailto:Avid-L2%40yahoogroups.com>,
> > "johnrobmoore" <bigfish@> wrote:
> > > >
> > > > So that means that if we created mxf 10:1 avid media using
> > RedCineX and dropped those into an existing avidmediafiles folder and
> > brought the clips in using media tool those clips would be considered
> > imports? Am I confused about RedCineX's functionality here. Does it
> > only create QT files for Avid import or does it also create Avid mxf
> > media directly. I thought it did both but I don't know why I think
> > that. It sounds like we'd have to go the aaf route or ale route to
> > then import the RedCineX QT files based on those bins. Would that
> > allow for the addition of Tape Names to then relink using ama?
> > > >
> > > > --- In Avid-L2@yahoogroups.com <mailto:Avid-L2%40yahoogroups.com>,
> > "Terence Curren" <tcurren@> wrote:
> > > > >
> > > > > No. Imports link to imports. AMA links to AMA.
> > > > >
> > > > > --- In Avid-L2@yahoogroups.com
> > <mailto:Avid-L2%40yahoogroups.com>, "johnrobmoore" <bigfish@> wrote:
> > > > > >
> > > > > > Will Red CineX generated clips still allow for an ama relink
> > to the original R3D files? So far our simple ama all avid test has
> > worked fine.
> > > > > >
> > > > > > --- In Avid-L2@yahoogroups.com
> > <mailto:Avid-L2%40yahoogroups.com>, Greg Huson <Greg@> wrote:
> > > > > > >
> > > > > > > John- dont fear the redcine-x!
> > > > > > >
> > > > > > > Hh
> > > > > > >
> > > > > > > ________________________
> > > > > > > Greg Huson
> > > > > > > Secret Headquarters, Inc
> > > > > > > Greg (at) SecretHQ.com
> > > > > > > www.SecretHQ.com
> > > > > > > DigitalServicsStation.com
> > > > > > >
> > > > > > > On Apr 28, 2012, at 12:16 AM, "Job ter Burg (L2B)" <Job_L2@>
> > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > MC works with Rocket, but ONLY during transcode (not
> > playback) and ONLY when the Media Creation R3D Setting is set to Full
> > Debayer.
> > > > > > > > Also, it requires a very specific combination of Red
> > Rocket firmware and driver versions.
> > > > > > > >
> > > > > > > > If you install RedCine-X on the same system, that can use
> > the Rocket card as well and gives you more options (lower Debayer
> > settings for instance).
> > > > > > > >
> > > > > > > > On 28 apr. 2012, at 00:40, John Moore wrote:
> > > > > > > >
> > > > > > > > > Can someone remind me if Avid supports Red Rocket when
> > dealing with Red ama linked transcoding to Avid media?
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > [Non-text portions of this message have been removed]
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> >
>
>
> [Non-text portions of this message have been removed]
>
No comments:
Post a Comment