[Mauricio Lleras]

Absolutely agree on both counts.

[Mauricio Lleras]

Rony, I appreciate you taking time to go by most of the points I mentioned,
although I find your attitude a tad condescending here and there…
I do use Fcpx, don’t know how you got the impression I didn’t
-perhaps because I mentioned I wasn’t on the latest version?-,
but it’s not the only software I use;
I’m a freelancer, so got to go with what’s available or desired,
which is often not Fcpx…
And by the way, everyone uses the mouse too…
Anyway, I see you basically agree with most of what I brought up.
Glad to hear the annoying colour correction bug has been fixed.
Sad to see nothing much else is improved from version 10.4
on these many aspects….
Regarding some of your comments:

[Ronny Courtens] “I don’t think you are familiar with the Timeline Index. Select Tags in the Timeline Index and you will be able to search for any markers or elements in any markers on your timeline. Clicking on the result will bring you exactly to that marker.”

Again with the attitude…I do know the Index and see it can be used to accomplish this.
However it is an imperfect use, as it does not allow for searches at the library or event level,
you HAVE to put everything in a timeline
and if you want to search for it you have to open said timeline and search there,
leaving your actual edit (and requiring you to be sure in which selects timeline that thing you’re searching for is).
So, while definitely workable, it still is not as good as say, Avid’s way,
which allows for a project wide search and brings up all instances found in a project,
and if you then double-click on any of the results it will take you directly to the point you requested,
regardless of whether that marker lives in a clip or in a timeline;
and in the latter case, if the marker is in a closed timeline it will open it for you automatically
and place the playhead right where you want.
So there is room for improvement, especially for an NLE which is otherwise
so strong on the metadata/organizational/search levels…

Regarding syncing clips from the timeline, read Neil’s comment.
You may not find it necessary but there may be a variety
of situations in which you might want this.
As a matter of fact, I’m about to edit a low budget short
as a favour and it so happens they had a problem with the rental company
and so couldn’t get the gear to jamsync camera and sound,
and no sound was recorded on camera, so I’m left with an old-fashioned
manual sync on my hands; and although you could do this
without laying clips on the timeline, it is easier to check and perfect sync
if you do ( for instance nudging clips by subframe increments and such)
and may come in handy for delivering viewing dailies kemrolls.
So again, it may not be dearly missed by many,
but a small handy thing to have it certainly would be.

Again, as I said in my post, nothing I raised is per see a deal breaker.
And I too like FcpX a lot.
But all these things put together do get to be annoying
and leave you wishing for more,
especially when you see how good it can be in other aspects.

[Mauricio Lleras]

Ah Bill, you don’t know me, but like I said, I’ve been reading this forum almost from the beginning,
so I know you a little, and was definitely expecting you to chip in this discussion
in exactly the way you have, it’s almost Pavlovian, and your reply
reads like a copy paste from a hundred other similar replies you have written in the past.
Honestly, don’t you get tired?

If you were willing to read past my FCPX criticism, you would see
I said I actually love the app and am rooting for it.
It’s definitely not an issue that I can’t adapt to new workflows
or whatever, but rather that I’m truly wishing for it to get better.
As much greatness as there may be in the trackless paradigm or the magnetic timeline
or roles to name a few, there are definitely areas where FCPX is lacking
in serious ways and that make for a less than optimal experience.

If nothing is done to correct this and make the software better
it might never gain the traction that I think it deserves and hope it gets.

And if we stayed put with that “everything is perfect as is, just adapt” attitude
you keep displaying well I guess we’d still be stuck in 2011 without
any of these “old” or “needless” things we’ve gotten over the years such as
multicam editing, FCPXml, advanced color correction tools, etc….

Just because one is critic of something it doesn’t mean
everything must be changed or one is hoping for the product to betray it’s core conception,
it is rather and more often the display of a love for it and the simple wish of it
getting to be as great as we know it could be…

[Mauricio Lleras]

Better keyframing is one I forgot to mention but definitely needed…
Also out of sync indicators seem like a small but feasible request.
Role based mixer would be awesome but definitely
a lot more complex to design and code…

[Mauricio Lleras]

Well I do of course use other systems, mainly Avid but also Premiere, and maybe soon Resolve, which I use for Color or prepping.
They all have great stuff, and annoying stuff too.
The thing is the one I really root for is FCPX,
because it’s core design ideas are the ones I like most.
If they could just fix/enhance all those little things I’d truly be happy…

[Mauricio Lleras]

Thanks for the input Joe, did some tests exporting H264 at 1080p from the 4K Red files in Resolve and times were similar to yours (I also have a 2017 Imac), so pretty good all in all. Exports from Fcpx were surprisingly slow in comparison…

[Mauricio Lleras]

[Joe Marler] “However if you are only distributing lower-res dailies for viewing (not editing), this isn’t an issue because those exported files will contain whatever double system sound you chose to export. Typically this would be a mixdown of the the selected “high quality” channels in a stereo track, but it’s also possible to export an MXF with multichannel audio.”

Right, so essentially this would create two sets of files, the Fcpx image proxies and then low res exports.
I was wondering if I could use the fcpx create proxies command to get review dailies with sync sound in just one step…
Well; I guess it would’ve been just too easy…
But thanks

[Mauricio Lleras]

What about the fact that all marking actions (Mark In, Mark Out, Mark Clip, Clear In, Out, Clear both marks)
cannot be undone/redone? This is pretty annoying as well, besides, it’d be really nice if marks were put at the timeline level rather than the clip level.
But one of the things that most annoys and disconcerts me is not being able to simultaneously select and trim multiple edit points. This is to me a tremendous oversight and something I’m rather surprised not to find more often in these wish lists, seems like such a basic editing feature.
Don’t get me wrong, I like a lot of what X has to offer, but these little things put all together amount to a sometimes underwhelming experience.

[Mauricio Lleras]

So I came here wondering if 10.3 had solved this ludicrous issue when searching for markers
and or favorites. Has it? I’m still on 10.2 but will be starting shortly a doc on 10.3
and was wondering about logging strategies regarding that issue.

In the meantime, if it hasn’t I have found a workaround that works using favorites:
as others have posted, you can hit F to favorite, then tab twice to enter the favorite name
and hit enter again so the name sticks.
NOW, if you THEN KEYWORD THE FAVORITE
it will be properly searchable and when performing the search it will be the only result,
NOT the whole clip.
But, in order for this to work two things need to get done:
– apply the keyword AFTER you have tagged and named the favorite.
– conduct the search SELECTING FIRST the keyword collection it lives in (otherwise the search returns the whole clip as mentioned before).

So an example to be clear:
in a 30 minute clip named DAY 1, try loggin different moments that you like for broll use.
So hit F, enter favorite name, and THEN apply the keyword BROLL.
Do this for every moment.

Now, if you go to the BROLL keyword collection,
you will see a bunch of DAY 1 iterations that correspond to all your favorites.
If you now do a search by hitting command F for something like LAMP,
which let’s say you only have one of,
the filter will work accordingly and then the only clip displayed
will be the trimmed favorite range corresponding to LAMP (even though it still is named DAY 1…),
and not the whole clip.

Again, if you do the search at the event or library level this won’t work.
And again, if you first apply the keyword and then the favorite it won’t work either.

Granted, it’s clumsy too and I really can’t believe they haven’t fixed this yet
(PLEASE SOMEONE TELL ME THEY HAVE IN THE LATEST VERSION!!!)
but it can work and be of use to others who I know must be as desperate as I
to get a cleaner solution to this problem,
which by the way still doesn’t solve using markers.

Anyway, hope this helps but if you got news for me please post as fast as you can,
I’m diving in soon!
Thanks

By the way,
to make the workaround less cumbersome,
you can tag and name all of your favorites,
then select them all and then apply the keyword to them all
in one step (instead of everytime you do a favorite)
and it will work too.

[Mauricio Lleras]

So I came here wondering if 10.3 had solved this ludicrous issue when searching for markers
and or favorites. Has it? I’m still on 10.2 but will be starting shortly a doc on 10.3
and was wondering about logging strategies regarding that issue.

In the meantime, if it hasn’t I have found a workaround that works using favorites:
as others have posted, you can hit F to favorite, then tab twice to enter the favorite name
and hit enter again so the name sticks.
NOW, if you THEN KEYWORD THE FAVORITE
it will be properly searchable and when performing the search it will be the only result,
NOT the whole clip.
But, in order for this to work two things need to get done:
– apply the keyword AFTER you have tagged and named the favorite.
– conduct the search SELECTING FIRST the keyword collection it lives in (otherwise the search returns the whole clip as mentioned before).

So an example to be clear:
in a 30 minute clip named DAY 1, try loggin different moments that you like for broll use.
So hit F, enter favorite name, and THEN apply the keyword BROLL.
Do this for every moment.

Now, if you go to the BROLL keyword collection,
you will see a bunch of DAY 1 iterations that correspond to all your favorites.
If you now do a search by hitting command F for something like LAMP,
which let’s say you only have one of,
the filter will work accordingly and then the only clip displayed
will be the favorite range corresponding to LAMP (even though it still is named DAY 1…),
and not the whole clip.

Again, if you do the search at the event or library level this won’t work.
And again, if you first apply the keyword and then the favorite it won’t work either.

Granted, it’s clumsy too and I really can’t believe they haven’t fixed this yet
(PLEASE SOMEONE TELL ME THEY HAVE IN THE LATEST VERSION!!!)
but it can work and be of use to others who I know must be as desperate as I
to get a cleaner solution to this problem,
which by the way still doesn’t solve using markers.

Anyway, hope this helps but if you got news for me please post as fast as you can,
I’m diving in soon!
Thanks