James Ewart
Forum Replies Created
-
Thanks okay got it… I just click on it at the moment…I don’t find clicking to be so much extra work but most people seem to find it rather tedious it seems. I kind of like clicking…feels like I’m splicing a piece of film.
-
Good call but no it doesn’t…just checked….
-
It just feels like we are still trying to find workarounds to do some very basic operations rather than just being able to do them.
-
The trouble is it would be nice to have the option to lock off audio tracks that you did not want bladed or deleted..and I cannot figure out how that would work.
-
Just been trying to sot this out again today…it’s annoying.
The offending shortcuts (Control, 2,3,4) have the words “System reserved” next to them in the Command Editor.
I did have to disable a system shortcut in Keyboard OS preferences to get control 1 to work (Mission Control switch to desktop 1 is also Control 1).
I’ve been on to Apple and trashed prefs and trashed system refs but still no cigar.
Bizarrely if I log in as another “guest” user and launch FCP, those shortcuts are not greyed out in the command editor and work.
Somebody clever out there may know????
Have a good weekend all
-
Yup..I could not get used to not having it there and now it’s there I have decided I don’ need it most of the time and have disabled it.
-
Got that thank you Michael.
-
okay found the relevant help section now thanks
-
which is quite cool because you can select three ranges from one clip and drop them all into the timeline at once. Not that I am aware of ever needing to do that…but how do you delete and what are the keyboard shortcuts …there seem to be more keyboard shortcuts than ever before I think.
And I’m with you I was using keywords to mark up clips…this seems a little lazy and liable to get a bit messy.
Still can’t figure how to delete.
-
Thanks I’ve noticed these appeared now but also before that if you used match frame (shift F) it remembered which bits you used for that clip in the timeline anyway so what’s the point…it only seems to remember the most recent range in the event browser no?
How did you do it before by the way?