[Zachary Johnson]

Here’s a bug: I’m not able to select the topmost item within the project window. (Or twirl open the first item if it’s a folder.) I can select any other item below it.

If I retitle any other item so that it moves to the first of the list alphabetically, then it becomes unselectable and the previously unaccessible item becomes selectable. This is true of comp items, footage, solids, whatever.

I also am unable to resort the Project Window by the “Name”, “Label Group”, and “Comment” column headings. They are also unselectable. Type, Size, Media Duration, and File Path column headings are clickable, however.

I’m on Mac OS 10.10.5.

Edit: After opening a 13.8.1 project, I’m unable to reproduce this error, even in newly created projects.

[Zachary Johnson]

Will the upcoming BCC8 FxPlug release work with Final Cut Studio 3 applications (FCP7/Motion4) or just FCP-X and Motion 5?

[Zachary Johnson]

Actually, I’m now noticing this is how most (all?) the filters in BCC operate in Motion 3. I’ve spent the last couple months with BCC without the need to animate keyframes on anything besides the light filters, and I thought this was just their peculiarity, having never tried animating parameters on the others.

I guess all BCC 5 filters need to start at the beginning of the project.

Or maybe I’ve got some problem with my set up.

Motion 3.0.2.
BCC 5.0.1
OS 10.4.11
iMac Core 2 Duo
Radeon X1600

I’ll try it out on my MBP later to see.

[Zachary Johnson]

I think I have the same problem as this guy, and I think I know the solution. I’d like to report it as a bug, if it hasn’t been identified already:

Many of the light filters’ keyframes (rays, etc) only work if the filter is extended so that it begins at the start of the project. For instance: “BCC Rays Puffy” If the filter starts at frame 0, and I keyframe something, not a problem. If the filter in-point is frame 10 (because its parent clip starts at that point) and I keyframe something to happen from 20 to 30, the filter keyframes that action from 10 to 20. The filter determines its actual keyframes by subtracting the difference from the filter’s in-point to the project start from the intended keyframe positions.

Consequentially, when you’ve got a clip and filter far down into the timeline (farther from frame 0 than the filter length itself), no matter what keyframing you do, the filter will render the last keyframe values over the whole clip. I assume that’s what the original poster’s problem is.

The workaround is to lock all your keyframes and extend the filter’s in point to the beginning of the motion project, unlock them, and continue working. Or be sure to extend any applied filter’s inpoint to the head of the project before keyframing.

This would be a good 5.02 fix as this seems to happen with a lot of filters and is pretty frustrating.

…forgive what must be a patronizing and long post if this is a known issue.

Zach

[Zachary Johnson]

Okay. I think I might have more info. I looked through my panic logs and saw qmaster referenced in the crashed thread.

After removing all the qmaster and compressor files and installation receipts to all the FCS 6.0.2 apps and reinstalling FCS 6.0, I had no problems importing P2.

(https://docs.info.apple.com/article.html?artnum=302845)

Then I updated FCS apps back to .0.2 omitting the compressor 3.0.2 update. I was able to import P2.

Then I updated compressor (and qmaster) to 3.0.2, and tried importing, and I kernel panic-ed.

The panics don’t happen immediately, so I can’t be certain that {FCS 6.0/QT 7.3} or {FCS 6.0.2(-compressor3.0.2)/QT 7.3} would have kept going panic free. But I can say that I made it through three 16gb cards in each of those configurations. And then when I updated compressor, I kernel panic-ed on the first card I tried.

I’m going back to FCS 6.1 and holding off on a OSX reinstall, as I feel compressor/qmaster may be at fault and not quicktime 7.3.

Or is my logic faulty somewhere?

[Zachary Johnson]

I’m not familiar with dealing with the mxf files or backing up p2 cards etc. The way I’ve always dealt with getting my footage was through the log and transfer window with the camera attached. So I didn’t really explore the other options.

I remember though when I opened the “NO NAME” p2 drive that mounted, there were no files displayed within it. No folders, no “lastclip.txt” But if I went into Log and Transfer, I could see and playback all the clips in the previewer.

Mounting the same P2 card on my MBP that’s still running QT 7.2 showed all the files did indeed exist, however.

I cannot say with any certainty that the folders were missing from the card in every instance prior to my kernel panics. I’m not sure I checked everytime. A drive mounted, and I went straight to Log and Transfer.

I just did a more earnest reinstallation of FCP 6.0. (ie deleting all the preferences, frameworks, logs, package receipts, etc for compressor, qmaster, et al as described here: https://docs.info.apple.com/article.html?artnum=302845 prior to reinstalling) and I have since been unable to make it crash. And the files are showing up in NO NAME now.

I’m going to try reimporting this card, restarting, etc, until I can get it to crash again. If I can’t, maybe I figured something out here with my latest reinstall…

[Zachary Johnson]

I’m the guy from the Apple board getting kernel panics.

I’m on a pre-Aluminum Intel iMac.

My P2 issue is a little different than described above. I’m importing from card-in-camera via the log and transfer window. And I can preview the clips and access the media fine, but while capturing, the computer gives me the GSOD after a handful of clips.

I reverted to FCS 6.0 and still have the problem, so it’s either 10.4.11 or QT 7.3.

I need to revert to QT 7.2. What gets lost or saved after an “archive and reinstall” of the OS? My only experience is with the erase and reinstall procedure. This isn’t my dedicated editing machine, and there’s a mess of documents and apps and plug-ins I don’t want to lose off this machine…