Space bar no longer plays clip in browser; disclosure triangle expands instead

Thanks for your reply.

I’m wondering if this might be down to a system language/keyboard setting, or maybe something that changed in the most recent update. For the last few years I’ve always been able to preview clips (in list or filmstrip mode) with the spacebar, then set in/out points and insert/overwrite — but now it opens disclosure or (if no disclosures available) opens up a Video/ Audio role selector, floating in the middle of the app (see image attached) - which is bizarre.

Another thing that’s thrown me off is Cmd+Option+K (to open the Command Editor). It used to open with the search bar already active, so I could start typing straight away. Now it doesn’t, and I have to hit Tab three times to get into the search field. Also a weird change.

I think I figured out the underlying issue—it seems to have been a kind of “default active bug” that actually worked in my favour.

• The clip filmstrip (not the filmstrip view/mode) used to be active by default. So when I selected a clip in list view, the small filmstrip at the top would automatically activate, letting me play it and set in/out points quickly.
• Same with the Command Editor—the search bar was active by default, so I could type straight away.

This behaviour was really efficient, especially in list view where you’re reviewing hundreds of clips. NLEs usually minimise mouse/trackpad use, so being able to just arrow through clips and set in/out points without extra clicks made sense.

Now that behaviour is gone, it slows the workflow a lot.

I would normally ask my edit team, but as senior editor I didn’t want to confuse or throw anyone off — I’ve been a strong advocate for moving our editors to Mac + FCPX from the usual PC + Premiere/Resolve (both of which I’ve used for 10+ years).

That’s why this inconsistency is frustrating. If I’ve been doing something a certain way for years, and it suddenly behaves differently, just say it was changed in an update — don’t make it out like it’s always been that way. There are plenty of reports online of similar issues, so I know I’m not alone here.

For the record, I run a purist workflow: no third-party add-ons, no plugins, no tinkering. Just clean installs and standard use. This is the first (and hopefully last) time I’ve run into something that feels more like a bug than user error. Given FCPX’s reputation as a solid NLE, it’s a bit disappointing.

Wow, that did it! One click and sorted—I'm in awe.

Thanks so much.

On the command editor, I can still get around pointer-less by tabbing three times, so that’s a good workaround too.

Really appreciate your contribution, and hopefully this helps anyone else who gets blindsided by the same thing.

There are loads of responses I’d love to upvote ⬆️ (including this one), but looks like I’ve hit my daily limit.

(deleted)

how do i delete responses?