thanks for the tip seth. will try that one out.
cheers
b
On Dec 18, 2013, at 9:08 AM, Seth Isaac Buncher <seth_buncher@hotmail.com> wrote:
Hi,That bug got smooshed in v6, as Bruce mentioned. If you're comfortable in the console, you might try the IgnoreQTRate command:"IgnoreQTRate -- This will ignore the edit rate in a Quicktime file and import the file as if it is sampled at the current project rate."It's a toggle-able command, so it could be backwards on your system.Warmly on a cold day,Seth
To: Avid-L2@yahoogroups.com
From: cutandcover@gmail.com
Date: Tue, 17 Dec 2013 18:02:44 -0500
Subject: Re: [Avid-L2] Relinking / Batch Import of graphics wonky
Here's what I know - if you batch import anything, and it's longer than the length of the original clip, MC will compress the new import to match the old length. This generally sucks, and I always have to check it (as in, "hey graphics editor, please render the exact number of frames for your revised graphic so I can batch it") So I figured if that is true, then the opposite should also be true. But I guess not.
On Tue, Dec 17, 2013 at 5:42 PM, Bruce Tovsky <bruce@skeletonhome.com> wrote:
nope. it's a known bug, likely squashed in v6 & 7, but i'm for the moment stuck in 5.5 till i can get through several critical projects - no horses in midstream etc - so can muddle through. doing them one-at-a-time by repointing the clips to the files manually, not quite as fast….
cheersbOn Dec 17, 2013, at 3:44 PM, Mark Spano <cutandcover@gmail.com> wrote:Isn't that an issue with length? Check the original editor's clips for length and then set your import settings to match.On Tue, Dec 17, 2013 at 3:14 PM, Bruce Tovsky <bruce@skeletonhome.com> wrote:
hi all
i'm restoring a doc in mc 5.5.3 / os x 10.6.8 on a NitrisDX system and everything is hunky dory until i do the graphic batch reimport (i consolidated the seq and am batching the numerous graphic files - mostly tiff's and psd's of photos that are animated.) : some files reimport just fine and some give me an error: "Exception: IMPORT _TOO_SHORT". filetype doesn't seem to be the culprit.
any tips or hints appreciated.
cheers
b
__._,_.___
Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (8) |
.
__,_._,___
No comments:
Post a Comment