[Jim Giberti]

[Richard Herd] “”P” is your friend here because it allows you to put audio in the primary wherever you want it by placing it and then sliding it where you want. You can assign a role to it and export accordingly.”

“P” really doesn’t get the respect it deserves does it?
Also “,” and “.” these are the things that make a hybrid approach possible in X.

We should start a thread of the little things (P certainly is a big thing) that make editing fast and that are demonstrably different from legacy and other NLEs. They can get overlooked because of that.

Like, in audio editing, Control/+ Control/- for making fast 1DB adjustments to clips.

[Jim Giberti]

[TImothy Auld] “That was fun. And you’re right – G6 all the way. So, I’ll bring the champagne and shots and you bring the jet and the women. Deal?”

I just found this post out of context Timothy, but whatever the context was, I’m in.

[Jim Giberti]

[Aindreas Gallagher] “there you go see? – someone who actually honest to God knows what they are talking about.”

Yeah, I’m going to quote Andrew, just so people think I’m smart.
Unattributed of course.

[Jim Giberti]

Yeah, I’d love some sense from you guys too.

I’ve been avoiding the 1.04, MB and yes, Lion upgrade because we’re jammed with projects and systems seem to be going well.

I won’t deny I’m a bit timid about introducing any variables into the system now that it’s working smoothly.

Is there any sense that 1.04 (or X in general) is operating better in Lion?

Likewise Mark’s question, is the process simple and clean enough to do during, say, lunch…a long lunch….with cocktails?

[Jim Giberti]

[Bret Williams] “So…. We still cant copy and paste Keyframes in FCP? That’s been a feature request since 1.0. Sigh.
“

This is part of the ever growing lost of “niggling things that X can’t do that working editors and designers need it to do”.

I was just designing a TV close last night, a lot of elements that needed the same curves. This simple, basic feature would have saved me the cost of the program.

Apple needs to assign a team of “non-visionaries” who can look at the host of simple, essential functions that they seem to have ignored in their celebration of brilliance.

[Jim Giberti]

There are so many niggling things like this with retiming, the color color board, etc. They just needed to spend more time with it to make the actual operation of the program match it’s potential.

It’s not like a typical 1.0 release – they’ve been developing it as the FCP replacement for half a decade or so.
IMO, these constant “why can’t I do these these obviously important things” simply reflect Apple’s lack of focus on the day to day needs of current working professionals.

I like and use the program, but Apple needs and deserves the criticism. THis is basic editing 101 stuff and stuff that they used to provide. Perhaps it will move them to get a list of these obvious and egregious missing functions delivered.

There are a half a dozen, simple, critically missing elements to the Color Board alone that would make it a genuinely great tool – they just need to do their job and make it more than a potentially great NLE.

[Jim Giberti]

[Marvin Holdman] “Not personal? Read Rand?
“

I have. It was like reading cartoons without the colorful pictures.

[Jim Giberti]

Just to echo the general opinion – it’s simply semantics if you think the flexibility has been stripped away.

Using the project browser is a pretty slick way to show a client multiple versions of a project and as Craig mentions, played in real time outside of the timeline.

Likewise, Auditioning (which has come in really handy for in-house comparisons of grades and FX as well as alternate takes) is a very slick way of showing clients comparative edits.

Not that it doesn’t need to catch up on a lot of basic niggling things and a few big ones, but a lot of the issues that seem to put people off about X are things that they don’t understand exist but are different.

And often better.

[Jim Giberti]

[Frank Gothmann] “Yes, but that a very different kind of h264. Most NLEs can handle that. My post was specifically with regards to blu-ray h264 (files which are high profile 4.1) as par Mr. Schechtman’s statement. I have to work with such files very, very often btw. Without PP/Adobe Media Encoder I’d have a problem.
“

That I wouldn’t know, we never work with blu-ray files. We transcode everything to Pro Res but I tried working natively with camera h.264 files and was surprised at how well X did with them.

[Jim Giberti]

[Frank Gothmann] “There are different flavours of h264. Are you sure it’s high profile. Basically, use the Blu-ray preset from compressor, encode something with it and see if X can digest it.”

I wouldn’t need to do that.

It’s h.264 as most of us use it – right out of the camera. In this case 5D IIs, files dumped right from the CF cards onto Macs and edited directly into the timeline in FCPX.