[Charlie Austin]

[Ievgenii Larin] “Adobe is flirting too much with FCP7 editors. I guess Adobe is risking to stuck in the past if they continue to appease editors with things they’ve already seen in FCP7, not trying to create something different.”

Well, that’s their market for Pr right now. They may even snag some Avid folks, though MC 7 looks like it’ll slow that down. Apple already skated to the puck, but that puck is in a scary neighborhood for some folks right now.

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

What are the FCPX sequence settings? I don’t use Vimeo, but I just looked the resolution choices in the destination settings, and it’s fairly limited. I’d export a master file from FCPX and upload it to Vimeo through a browser. Again, not a Vimeo user so I’m not sure….

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Greg Andonian] “it’s very telling that Premiere Pro 7- which Adobe, as we all know, has built with a heavy emphasis on user feedback and requests- has gone in the exact opposite direction, and people are now cheering the fact that FCP Legacy- which Apple destroyed so they could focus on showing us the future of editing- has now been re-incarnated.”

I think the reason Pr 7 seems like “legacy reincarnated” is because it’s likely that the majority of those feature requests came from legacy users. As Craig points out, up until maybe a year ago, X wasn’t really viable for pro work. It certainly is now, despite the fact that there is still more to be done. I don’t think Apple were wrong, they just fumbled the initial release, which I think they know. At this point, as Craig points out, it’s just a more diverse NLE world. A good thing. 😉

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Nick Toth] “FCP X does not like .dv files.”

Nobody likes DV files. said the guy who has 2 projects in X using dozens of DV sources. Anamorphic DV. With different Aspect ratios. Fun! I captured them into FCP 7 though, so that part was easy. Is that an option for the OP?

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Nicholas Kleczewski] “I have an entire production and post agency with locations in NYC, LA, Vegas, and Virginia to switch over in the coming months. I’ve been devising ways to “make FCPX work” hoping a 10.1 would bring proper shared collaboration abilities, but after all this I will strongly be considering Premiere.”

Not sure this is the case, but if you prefer X and your “sticking points” are collaboration and/or better audio capabilities, I think waiting a bit longer, assuming you can, might be worth it. Just based on my own speculation… Not any actual facts or anything. lol

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Mark Morache] “At $17.99, it would pay for itself with just one use. It needs to keep copies of the project file without copying every render in the folder”

It does. You can choose whatever you want it to back up, from just the project/event file, to all your media. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[David Powell] “As far as the range selection problem goes, a simple mark to markers command as existed in 7 and Avid would solve the whole thing, oh yeah and colored markers so I can differentiate from my editing marks.
“

Maybe not ideal, but a workaround might be to use chapter markers. set a “start” mark as usual, but in the pop up make it a chapter marker. It’ll give you a little pin which you can drag out to your end point. You can make a bunch of these, then, using the timeline index, you can jump to the start of each “chapter”, hit “I”, click the marker in the index (not the timeline!) again to see the pin at the end. scrub the playhead in the timecode strip at the top of the timeline only, – click anywhere else and the range goes away, as you know – … (or skim) to the out point, hit “o”, delete. repeat as needed.

Again, not the same as mark to markers, but sorta close? Just a thought…

setting a range to markers seems pretty do-able, so… at the risk of sounding like a broken record… send feedback. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[David Powell] “I’m on 10.06 on OS 10.7 and I get green glitches with or without added effects. Its been that way since 10.03 with me (which is when I started using X). The only solution is to “Send to Compressor”. This seems to fix to problem at least on export. Copying the project without including renders will help temporarily within the NLE, but they will show up agai”

I honestly think the solution is to upgrade the OS and App.

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[David Powell] “My timeline is 100% multi-clip based off of one long multi-clip in the event browser, and one problem Im running into is when I match frame, I can only set an in point. I cant transport through the clip to an outpoint from the event browser to make a select. I can’t even play through a multi-clip from the event browser. This is a big letdown for me.”

You may have already done so, but i’d shoot some feedback to Apple, with as much detail as possible. They do read that stuff. 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Charlie Austin]

[Don Walker] “Really? I’ve been curious about what type of work could be done on MacBook Air with FCPX. I never thought about any of the Adobe products running well on one.”

Well, I really haven’t done a lot on it, but X seems to run fine, even doing EZ multicam stuff (2or3 angles) MC 6.5 and Pr run OK. I haven’t pushed it, or done anything requiring heavy GPU lifting, but i think it’d be OK for quick, basic cutting. YMMV as they say. Maybe I’ll bring something crazy home from work and see how it does, just for laughs… 🙂

————————————————————-

~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~