|
|||||||||
|
Thread Tools | Search this Thread |
September 1st, 2008, 01:30 AM | #1 |
Regular Crew
Join Date: Dec 2005
Posts: 56
|
Stripping out timecodes from EX output
Hi,
To cut a long story short, our editting system (Avid Liquid) will not allow the transfer of EX based projects from between 2 machines due to timecode complexities. However it will allow transfer of files such as motions loops and still images that have a name only and no timecode Is there anyway to import the files (which we have to convert to mxf using clip browser first) and loose the timecode information- import as a file wth a file name only in other words? Can the cameras be set not to add tiemcode data? Kind regards, Stuart Last edited by Stuart Boreham; September 1st, 2008 at 01:32 AM. Reason: typos |
September 6th, 2008, 04:00 PM | #2 |
Regular Crew
Join Date: Jun 2006
Location: Atlanta GA
Posts: 190
|
I'm switching to FCP partially because Liquid (which I still think is far ahead of others, with background rendering and instant save and such) because it's EOL. However, I've cut a number of things on Liquid using my EX-1 footage.
Apparently the timecode info simply isn't carried into liquid. However, if you import the converted mpg4 clips into a project they do remain the same length. So, I had one thing from January that the client wanted to revise ... I could not get liquid to relink to the clips, and I tried everything I could think of. So, I reimported the clips, then had to take each clip on the timeline (the project was long since off the computer, so the original clips were also off the RAID), move it to an empty track (with another empty track above that), mark where the in point of the clip was on the timeline, then stretch out the original clip to it's head, put the reimported clip above it, match the start of the two clips, trim at the head and tail of the edit, then move the new clip into the original location of the old clip. It took a couple of hours but it worked. Not an ideal workflow. Since liquid will evidently not be updated I don't expect this workflow will be fixed. Maybe their replacement new product will work. I couldn't wait, hence FCP and waiting on renders. |
| ||||||
|
|