[Andy Neil]

A lot of things here I’d like, though honestly, my own wants are fairly slight. Or at least, I can’t recall so many this early in the am. That said, here’s my non-exhaustive list:

TIERED MATCHFRAME LIKE AVID: Many people would like a better matchframe, but I specifically want one that works like Avid’s, only better. Matchframe a clip in timeline takes you to the keyword range of the clip in the browser, matchframe again from the browser, and it takes you to the master clip. Matchframe a multiclip in timeline, it opens the angle editor and matches to that frame and assigns that track as the monitoring track. Matchframe again and it takes you to the browser and the master clip. Same with compound clips or synchronized clips. Basically, you can keep matchframing until you’ve found the most basic element of your video.

MORE SHORTCUTS: We need more shortcuts and for more things. Charlie mentioned one for selecting clips vertically which would be great. Also, I’d like one for increasing the size of the timeline clips. I don’t mean changing between audio only view to the tetris view, I mean adjusting the clip size in the individual views. Not all of us are cutting on 30″ monitors and I hate using that slider. I hate using all sliders because they’re so imprecise.

PROJECT SCRUBBING/EDITING: We used to have this and it was took it away. I think it would be nice to be able to scrub a project like a clip and even mark IN/OUTs and edit that project into another project that way. As a corollary to that, Having tabs in the project pane similar to FCP7 where you can have more than one project open at a time and copy paste that way.

RANGE RENAMING: I’d love to have the ability to creating keyword ranges and then renaming the clip in the collection without it changing the master clip name. This could be as simple as having a new meta-data column for range names that’s the default view inside collections. But then all the people who use subclips in other NLEs to say, label interview bites would have a clean, simple workflow for the same inside X.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Noam Osband] “I worry that will make the system slow.”

I don’t think you’ll slow down X by creating lots of keyframes. All it’s doing is tagging metadata, very low overhead.

But if you’re trying break away from how FCP7 did things, you might consider organizing yourself and doing your selects in the browser where you can take advantage of all the great metadata features and only use the timeline to assemble your project.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

You can view keywords in the index. So, for example you create a keyword collection for each sound bite, then as you add those to your project, you can see the keyword for each clip and jump to their position in the project.

In fact, that might be your best solution. it doesn’t work with renamed favorites, but you can do it with collections.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

You can leave feedback by clicking on the Final Cut Pro menu and choosing Provide Final Cut Feedback.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

You are, and I recommend providing feedback to Apple about it. It would be nice to allow for a rename column for keyword ranges for just this sort of work.

However, something you CAN do is place markers on specific clips in your browser and name the markers. Then when you cut them into the timeline, you can view the names in the timeline index.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

You can view the contents of two collections simultaneously by selecting both in the event library. However, it won’t show duplicates of clips. If you have a clip with two keywords applied, it’ll only show up once in the browser, but the keywords are viewable in the browser so you should be able to tell easily that the keywords have been applied.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Well, if hard drive space is at a premium for you, and your project isn’t too big, you’re probably fine without the proxies. Your machine seems fast enough as long as you don’t have TOO many clips. The problem with editing files in their capture formats is that usually they need a lot of processor power to decompress and play in real time. So, if you start noticing serious lag, you may just want to bite the bullet and work with proxies as i-frame codecs like pro res don’t use nearly as much processor overhead.

Good luck and thanks for the kind words.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

[Sascha Engel] “Is there a way to match frame a point in the MultiCam timeline to editor set up timeline of the MultiCam clip?”

No, and this is something Apple really needs to fix with Multicam. First of all, send them feedback. If enough of us complain, hopefully they’ll fix this oversight.

Secondly, what resolution is your multiclip? Did you make a 1080 multiclip (it sounds like it). Have you considered making a 4K multiclip instead?

I haven’t worked with those resolutions in a multiclip before, but it seems to me that if you cut your 4K multiclip into a 1080 timeline, then you could just make transform adjustments in the inspector without having to go into the multiclip editor.

Of course, you’d have to resize all your 1080 clips because they’d show up small in the cut, but you just resize one and then copy paste attributes for the others. One warning if you do this: Don’t resize the 1080 clip in the multiclip editor and then expect it to look good when it’s sized down in the timeline. It won’t. Just do the cut and then size up the 1080 shots.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Depending on the source files, leaving them in place might not be an option because they can’t be edited natively. Certain camera files must be converted to prores.

Andy

https://plus.google.com/u/0/107277729326633563425/videos

[Andy Neil]

Nope. Although I think that’d be a good improvement. You should write up as feedback to Apple. They definitely do look at the feedback they get.

Andy

https://plus.google.com/u/0/107277729326633563425/videos