Michael
Forum Replies Created
-
A lot of the spot houses in NY and LA are changing to FCP. So this problem is a pain, but not an insurmountable one. Perhaps there’s a way to export a edl or batchlist and resort it in a spreadsheet program.
Let’s hope the next generation of FCP addresses these and other mundane, un-sexy, but vital features that Avid has had right for 15 years.
-
Scott:
I feel your pain. I need these lists for telecine too. I asked the same question on this forum a few weeks ago and didn’t get a reply, so I’ll help as much as I can.
Theoretically, you should be able to make a C-mode list (ascending source order) by choosing “Source, audio merged” from the sorting option menu in the EDL export dialog. In reality, in my experience, this produces a list from another planet. No logic to it that I could tell. It just doesn’t work, unless I’m missing something.
My workaround is to export a regular A-mode list and import that list into an Avid. I then change the sorting to C-mode and export. It works. If you have access to an Avid, that is.
I’m afraid this area is a real FCP weakness. Our assistants complain about it constantly.
Michael Heldman
Spot Welders -
Yes, but telecine bays transfering film to digibeta are still quite active. I take a c-mode list to telecine so we can work our way through the rolls in the most efficient way.
-
Funny, I was just about to post a similar question:
Is there a way to set an “in point” for a clip you’re about to drag into a layer?
I know that in and out points are set if you send clip from an FCP sequence to Motion, but what about a project that begins in Motion? Suppose one of the clips in my file browser is 8 minutes long and I only want to use 4 seconds of it that begin 5 minutes in?
Michael Heldman
Spot Welders -
When you say that “open sequences” are the RAM hogs, does “open sequences” refer to all the sequences in a project, or just those open in timeline tabs?
-
Wow, Mark, settle down. You seem to be reacting to some post other than mine.
Believe me, I know about Avid support. I’ve dealt with them for 15 years. I remember the days when you were lucky to get someone on the phone within a half-hour. And I, like many others, complained frequently about that service. And Avid support is much better now, I think mostly because of our complaints. And the fact that Avid’s support hasn’t been perfect doesn’t mean I don’t have the right to occasionally complain about Apple’s.
I’m simply saying that a product marketed to professionals deserves professional level support. This applies to Apple and Avid.
I posted about a specific incident and the irony of the message I got from the tech. I tried to be fair in my post and pointed out that we did reach an Apple tech, on a Saturday, within a few minutes. It was not at all a “I hate Apple” rant, as you seem to take it. Believe me, I know Xsan is difficult, and I know our problems could be our fault. I’m not above admitting user error. I just was hoping that a problem that a low level tech couldn’t solve would result in a quicker response from a higher level, not a slower one.
And c’mon, we all get nervous about down time. But it’s inevitable, and we all deal with it. In my second post I described how we coped with ours.
Believe me, Mark, I really want FCP and Xsan to be a success. That’s why I’ve invested in it and am trying to move away from a dependence on Avid. I’m on your side. So peace, okay?
Incidentally, I’ve been reading your posts on the Cow for a long time. I’ve clipped and saved quite a few. You’ve been very generous with your time and experience. And you probably have more working experience with Xsan than just about any video professional. That fact that you’re satisfied with it, working in a much more complex environment that ours, helped convinced me to buy it. I’m sure we’ll be happy with it too after our initial growing pains.
-
Fortunately, we only lost a few hours of work time, not a whole day. We were able to copy our media directly from the raid onto firewire drives and work the old fashioned way: with local storage.
-
Thank you, specialcase, for your quick and very clear response.
What you describe is the behavior I expected. As an experiment, I opened another copy of Motion on another machine and it all worked perfectly, control points visible, etc. SO…
I trashed my Motion prefs, and now it works perfectly on my machine too. Go figure…
-
I