Jeff Markgraf
Forum Replies Created
-
Yes. Could be a bug.
In your experience, should a 23.98 clip play smoothly in a 29.97 timeline in FCP? I don’t have much experience with mixing frame rates in FCP, and Avid won’t even let you do it at all.
-
Hi Jeremy. It’s a 2.6 gig file. I could export a small part of it from FCP, but I don’t know if it would be an accurate copy of the original since FCP seems to be misinterpreting it.
-
Hi Oliver.
I may have misspoken. FCP sees the clip as 1080p 29.97. It sets the file as progressive. But is plays with an obvious interlacing problem which is fixed when I toggle the clip to one or the other field dominance. The jerkiness remains unless I set my timeline (project) to 23.98.
If I understand you correctly, you’re suggesting that Media Composer added the pulldown when it was digitized in the 29.97 project. I guess that makes sense. Not sure where the flags are getting set wrong.
I can’t open or import this file on Media Composer on this system. Not sure why. Even if I put the video and audio XMF files in the Avid MediaFiles folder at the root, Avid doesn’t see them. And they won’t AMA link when they’re split apart,I guess.
I’ll have to see what the file looks like on the Avid at work (from whence they came).
-
Oliver –
Right. Understood. It’s the standard Avid ripple function when using the yellow segment tool instead of the red segment tool. Been doing it without the picture view for years.
This is why I think the “magnetic” name is, I think, a bit of a distraction. Ripple editing certainly isn’t new, and that’s what magnetic is really referring to.
The more important function of the “magnetic” timeline is the way the clips move out of the way and overlap when dragged over each other. To me, that’s the real “paradigm shift” (sorry – I hate that phrase). Not overwriting (ala Avid) and not just going “thunk” and not moving (ala FCP7) is completely new for an NLE. (Pretty sure some DAWs do this by default.)
I know “non-destructive” is a fraught choice of words, but I think it comes closer to describing what’s actually important here.
-
Shawn –
So as I understand the tutorial, the colliding clips create crossfades, which I think is very much like Pro Tools. But the clips don’t actually move away and overlap like X.
As far as AutoRipple, it’s really just selective ripple editing, which is handy.
Unless I’m misunderstanding something, it still seems that X’s behavior is unique and inextricably tied to its lack of tracks.
-
Shawn –
How does that work in Vegas? (Never even seen a Vegas!)
I assume it has conventional tracks. Or does it layer the overlaps like a Fairlight? And does it overlap like X for video as well as audio? -
Oliver –
But overlapping clips in Avid results in overwriting the non-selected clip(s) that collide with the selected clips you’re moving. Which is normal if one assumes “I’m doing this because I mean to.” But it’s all too easy to do it by accident, and it’s an ongoing pain in the @#% to move the clips out of the way in order to protect them.
-
Isn’t the action of media moving out of the way (automatically ‘making a hole’ if you will) as you drag a clip around the timeline one of the big features of X’s timeline? Avid’s timeline certainly doesn’t do that.
Yes. This.
I’m not aware of any NLE except X that overlaps the clips to avoid collisions. I think the name “magnetic timeline” is a poor choice, since the “magnetism” is really just ripple editing, which any NLE can do. What might be a better, more accurately descriptive name?
-
Fair point. So…
Herb: “So I invite you to enlighten me on what you see as the strengths of multicam in X.”
Steve: “So I invite you to enlighten me on what you see as the strengths of the magnetic timeline in X.”
Let the games begin anew.
-
I don’t recall that the Sonnet needs a driver. My Echo II worked just fine when I upgraded my MacBookPro Retina to Yosemite. My ATTO Fiber card ghat I had in the Echo broke (driver not supported in Yosemite), but my Kona 3 worked great.