Ron James
Forum Replies Created
-
Iryna,
I’ve had this happen on one workstation and it drove me up the wall. Even after “fixing” it, the problem would sometimes return. This was on a 24″ iMac with the aluminum keyboard.
For me, it happened after I set the Mac OS pref’s to use Function keys as standard (not for volume, etc).
Then all my shortcuts stopped working in FCP. Command-Z, Command-C, Control-V, etc, etc.
Here’s the solution I can up with: In FCP, go to the Tools Menu > Keyboard Layout. Select the default keyboard layout. If it’s already selected, select another, then the default. This should restore your shortcuts.
-
Le Coyote, I’m hoping you’ll get notification of this reply! I’m having this exact same problem with my keyboard right now. It’s a machine I don’t ever work on and the F10 keys, etc, were still mapped to expose. So I went in and fixed it *with Final Cut Pro still open* and now the all kinds of things don’t work, like Command-z and many other combinations.
I suspect I’ve hit on this bug. Do you have any more info or ever heard of a way to fix it? I can’t get it fixed no matter what I try.
-
I’m not sure about the second one you mention, but the F9 is probably related to your System preferences, unless you’re saying F10 works, but not F9? You don’t really explain.
It sounds like, though, you need to go into your Mac System Preferences > Keyboard and Mouse > Keyboard shortcuts. Then you need to remap the expose keys (F9, F10, etc) I just add a shift in front of them, so now I clear all windows by hitting shift-F11. Now your keys should be reclaimed in FCP.
-
I swear by my Panasonic BT-LH1700W.
https://catalog2.panasonic.com/webapp/wcs/stores/servlet/ModelDetail?storeId…
Joey, I just came across this post trying to research a bit more info on these Panny monitors. Do you know if they’re capable of displaying interlacing? My concern, specifically, is the monitors ability to display interlacing problems, such as reversed fields in graphics, etc.
Thanks for any info!
-
[Shane Ross] “iMac…avoid for this.”
Don’t knock the iMac’s. I’ve cut feature-length projects on a few and had an easier time than on some G5’s I’ve worked on. You just have to be half-smart with maintaining a healthy system. I know a lot of people aren’t and should probably avoid iMac’s.
I really detest the newer ones with glossy screens, though. They’re really ugly and hard on my eyes.
-
Do a search and you might find some of my older posts regarding FCP file management and workflow. You can really strangle yourself if you don’t do things right from the very beginning. The database gets bloated and this is exactly what happens.
I’ve posted at least four or five times on the subject, though, so you should be able to find info on how to fix your situation now and prevent it in the future.
Good luck!
-
That’s a good idea! I’m going to try that. At least, I’ll be able to eliminate yet another factor. The deck only seems to have one setting related to this, which is FAM (setting it to file transfer mode) but who knows.
Thanks, Don.
-
Don, I checked all those pref’s and a few were different. I also updated to 2.7.1.
Now I’m getting an error with subclips: “cannot read file (insert name of mxf file)”
Everything else still works fine.
When you mentioned the camera it made me think I neglected to mention I’m using a deck (PDW-F70). My next plan is to check all the deck settings. Ugh, frustrating.
Thanks again for your help,
Ron
-
That’s excellent, Don! Thanks a lot for taking the time to pass on these settings. I’m working this evening, so I’m going to go through all of these. I’m thinking I’ve got to be missing something simple, especially based on the fact that it’s happening to me on two different machines with two different versions of the Transfer software. Strangely, v.1.1 works fine for me.
Weird.
-
Thanks a lot, Brian!
I should try the newer version of XDCAM transfer, perhaps. I thought I had the latest, but apparently not. If you have any ideas of what else I might be missing (even obvious) please let me know.