I'm still working on 6.0.3, but I think there have been some changes
around this in recent versions. Is it now considered a robust workflow
to assign proper tape names to file-based media, so it's possible to
relink by tapename and timecode for file-based material?
I remember Michael Phillips' advice when AMA was new-ish, which was not
to try to mix filename-based and tapename-based relinking.
Thanks,
--Michael
On 13-01-16 10:53 PM, namyrb wrote:
> For any folder structured media, we have the production crew copy them into
> folders during offload that would represent Tape names. So when you AMA
> link to volume it should create a new bin with the tape name. From there
> you can give all clips in each bin an actual tape name or create a custom
> bin column and move it right next to the Name bin column. That way you can
> easily differentiate between all of those duplicate filenames.
>
> On Wed, Jan 16, 2013 at 9:44 PM, johnrobmoore bigfish@pacbell.net> wrote:
>
>> **
>>
>>
>> You may be correct as I've not utilized any of the batching features but
>> it does organize card data into structured folders and can add time code
>> and reel names to help handle the wonderful world of file based ambiguity
>> we get to live with these days. If only someone who worked at Videotoolshed
>> read this list? Then we could get a definitive answer. Oh wait..... '-)
>>
>>
>> --- In Avid-L2@yahoogroups.com, Michael Brockington wrote:
>>> Please correct me if I'm wrong, John, but I don't think QTChange can do
>>> anything with the AVCHD file structure -- I believe it only works its
>>> magic with quicktimes.
>>>
>>> Thanks,
>>> --Michael
>>>
>>> On 13-01-16 10:17 AM, johnrobmoore wrote:
>>>> Sounds like some of the functionality that QT Change provides for
>>>> offloading card and organizing files. Just a great program and I only
>>>> use it to add QT and burn in TC. There is a bunch of stuff for
>>>> batching cards imports. IIRC. Check VideoToolshed.
>>>>
>>>> --- In Avid-L2@yahoogroups.com ,
>>>> Michael Brockington wrote:
>>>>> How are folks dealing with consumer AVCHD cameras that don't allow
>>>>> setting custom clip names or prefixes? Every time a memory card is
>>>>> formatted, the camera starts capturing another series of identically
>>>>> named clips -- "00000.MTS", "00001.MTS" etc.
>>>>>
>>>>> If I AMA these clips into Avid and transcode, they appears to retain
>>>>> timecode, but I think the identical clip names have the potential to
>>>>> cause me grief when I try to relink to the original files. (Am I
>> being
>>>>> too paranoid?)
>>>>>
>>>>> Currently I convert such files externally, creating new DNxHD175
>>>>> quicktimes, using Adobe Media Encoder CS5.5.1. These effectively
>> become
>>>>> my new master footage. I batch rename the output quicktimes to add a
>>>>> unique cardname prefix to the filename then AMA the hi-rez
>> quicktimes,
>>>>> and transcode them to lower-rez DNx36 for offline editing. There are
>> a
>>>>> few downsides to this approach:
>>>>> 1. Large DNx175 files clogging up my hard drives
>>>>> 2. Two transcodes instead of one is time-consuming
>>>>> 2. Adobe Media Encoder doesn't appear to pass AVCHD timecode through
>>>>> to its Quicktime outputs in any way that Avid can understand.
>>>>> Discarding that info makes me nervous.
>>>>>
>>>>> Is there a better approach?
>>>>>
>>>>> Is there a utility that would allow renaming of clips within the
>> AVCHD
>>>>> file structure without breaking the structure, for instance?
>>>>>
>>>>> Is there a better software choice for transcoding that would at least
>>>>> preserve timecode from AVCHD files in the transcoded quicktimes?
>>>>>
>>>>> Thanks for any suggestions,
>>>>> --Michael Brockington
>>>>>
>>>>
>>>
>>>
>>> [Non-text portions of this message have been removed]
>>>
>>
>>
>
> [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
>
>
>
>
>
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (7) |
No comments:
Post a Comment