-
Switched…then switched back?
-
Took at a look in editing Resolve, looks like an alternative and tried going back to Adobe CS 5. The grass was brown not green. Looking at Lightworks a try. Anyone have experience with The Foundry Heiro? Looking that as well.
-
What’s wrong with the white dot? I love that thing! 70% of the time what I want in the inspector is automatically there whiteout having to manually select a clip. If you need to select something else then you do, but law of averages for me is that it’s saved LOADS of manual selection clicks and mouse moves.
-
No. Not me. I’ve been very happy with both Avid and Premiere. Both worked out better than I expected.
-
[Chris Harlan] ” Not me. I’ve been very happy with both Avid and Premiere. Both worked out better than I expected.”
Hmmmm….also an interesting answer. What were you expecting, and how are they better?
-
[David Lawrence] ”
Dissolve from black with transition alignment set to beginning (or ending) of clip.In FCPX, dissolves always center-allign between the gap and the clip. Not what I want.”
Oddly, I used to use the heck out of that too in 7, but I haven’t missed it in years. I’m not sure why. We have other things we do, like a custom made dip to black generator (as well as fade from black, and fade to black generators) that we drop on top if we don’t have footage handles. Also, just being able to drag the center of the transition quickly may also play a part. Also, just throw the clip whose dissolve center you want to change on secondary, put your dissolve on the end of it, and extend it wherever you want the transition to go.
End of the day, I think that might be a legacy X thing. After a while you forget you ever did that. At least I did.John Davidson | President / Creative Director | Magic Feather Inc.
-
[Tim Wilson] “[Chris Harlan] ” Not me. I’ve been very happy with both Avid and Premiere. Both worked out better than I expected.”
Hmmmm….also an interesting answer. What were you expecting, and how are they better?
“Well, I was quite the fan of FCP, and really doubted that I’d find something as good for what I do. I had to really relearn Avid when I went back to it, and kind of resented the interface at first. It grew on me, and once I’d absorbed the mode metaphor, I found that I really enjoyed the interface. I love the source timeline, and the trimming mode, but I also really like the smart tool, which was new for me. Premiere, on the other hand, has pretty much everything I liked about FCP–flexibility, being number one–but is more mature. I feel very comfortable moving back and forth between the two. I still use FCP 7 now and again, as well. Between the three, I’m quite content.
-
[John Davidson] “Oddly, I used to use the heck out of that too in 7, but I haven’t missed it in years. I’m not sure why…
…End of the day, I think that might be a legacy X thing. After a while you forget you ever did that. At least I did.”Outside of actual bugs, and few MIA features I feel exactly the same way about how X works. I think that’s why some of the complaints people have sound silly to me. Not that they’re not valid complaints from the POV of whoever has ’em. It’s just that I’m used to how the timeline etc works now and I do the same stuff I always did, just differently.
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
[Tim Wilson] “”Okay, I’ve been using Legend, and X isn’t for me, so I’m going to Media Composer or Premiere,” and who THEN says, “Wow, I thought that that was going to work a lot better than it did. Turns out I didn’t like this other thing much at all, so I’m going to go to X after all.””
This happens to me repeatedly. Except I go back to the Legacy. And I did try FCPX several times.
-
The relinking issue is the main reason that I lost all trust in FCPX, and submitted to Adobe.
The issue ruined a complete show for me, because FCPX suddenly would not recognise any media (just because it had been loaded into Premiere for a test). I tried to clean the meta-data, but FCPX was still a bitch – so eventually ended up relinking (MTS files) from the original SD card. Everything came back in to FCPX out of sync, and I had to go through every darn cut and move every single audio key frame manually.
That is what I call a TOY and not a TOOL.
– No Parking Production –
Adobe CC, 3 x MacPro, 3 x MbP, Ethernet File Server w. Areca ThunderRaid 8…. and FCPX on trial
-
[Morten Ranmar] “(just because it had been loaded into Premiere for a test”
That must have been some time ago. Apple had a stop-gap fix for a while, and then Adobe changed/fixed their XMP. Haven’t heard anything about it since.
[Morten Ranmar] “That is what I call a TOY and not a TOOL.”
Wrong thread, that’s a few posts below. 🙂
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~
Reply to this Discussion! Login or Sign Up