Unless something changed, Avid MC will always import the whole file. It doesn't do partial file imports. I hope for your sake I'm wrong though.
Michael
-----Original Message-----
From: "Tony Quinsee-Jover" <tony@hdheaven.co.uk>
Sender: Avid-L2@yahoogroups.com
Date: Fri, 7 Oct 2011 13:49:54
To: <Avid-L2@yahoogroups.com>
Reply-To: Avid-L2@yahoogroups.com
Subject: [Avid-L2] AVCHD Hell
Hi guys,
I've asked this question on the Avid forums, but knowing that all the best
minds hang out here I thought this might actually be a better place to pose
my dilemma.
Our client offlined a half hour (24 min) show in PAL 16:9 using maybe 30% HD
mts files from a Panasonic MC1P camera. They pulled all these files in at
10:1 on their MC. I now have to online this show. It will be finished on DS,
but this question isn't DS related. This is also Prog 1 of a series of
shows, so this workflow needs to get nailed.
I opened the sequence on MC and consolidated it with 10f handles.
I selected "Batch Import" on the MC from the consolidated sequence, selected
MXF2:1, and pointed it to all the mts files.
After 48 hours MC still hadn't imported 50% of the files and the file it was
currently working on said that it had 34 hours to go!
Those files which had been imported appeared to be full length, rather than
consolidated, meaning that many of them were 30 minutes or more, for maybe 1
sec used.
It's been suggested that I'm asking a lot of a 32 bit application to not
only import but also rescale all the horrid files, so would I be better
importing them at HD (say DNxHD 185) and then switching back to my SD
timeline and then consolidating the media to SD? Would MC then only be
converting the few seconds used instead of the whole file? Sorry if this
last sentence is using some wrong terminology, but I'm no expert on MC these
days.
Cheers in advance,
Tony
HD Heaven Media Limited (company no: 07061040) is registered in England and
Wales at Sapphire Heights Courtyard, 31 Tenby Street North, Birmingham B1
3ES
[Non-text portions of this message have been removed]
[Non-text portions of this message have been removed]
No comments:
Post a Comment