- Posts: 238
- Thank you received: 20
3 Post Moderation Rule for New Boarders (25 Jan 2021)
New boarders will have their posts moderated - Don't worry if you cannot see your post immediately.
Smart Collection Problem
- Squamish ed
-
Topic Author
- Offline
- Elite Member
-
Any ideas about why this is happening? It shows up elsewhere in the collection too and doesn't seem to be specific to one camera or file name.
Thanks
Ed
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
Those 'stamps' and skim clips are generated - so, I would give File/Delete Generated Render Files a chance…
Then…
select the Lib, and look in the Inspector what you have chosen as Cache location… maybe a drive actually not connected?
Or, due to be a spinner, that moment asleep, needs some time to spin-up = no pic?
Silly reason:
that clips starts with a black frame (??)
Finally:
how come, there is a second clip with identical name right under the black one??
Please Log in to join the conversation.
how come, there is a second clip with identical name right under the black one??"
The Event Browser's clip filter menu is set to Hide Rejected. That could easily mean the master clip had at least one Rejected range, breaking it up into two (or possibly more) clips with the same name.
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
FCPX.guru wrote: … The Event Browser's clip filter menu is set to Hide Rejected. That could easily mean the master clip had at least one Rejected range, breaking it up into two (or possibly more) clips with the same name.
ok …
But then how come, that the black one doesn't show any green or blue lines?
Please Log in to join the conversation.
I'd delete prefs and renders, and probably go in and delete all the thumbnail cache, also.
AND "hide rejected" doesn't mean anything but rejected clips and ranges are not shown. It will still show clips with no ratings.
Please Log in to join the conversation.
- Squamish ed
-
Topic Author
- Offline
- Elite Member
-
- Posts: 238
- Thank you received: 20
Thanks for answering - I appreciate your suggestions.
Today I started up the project again, ran the smart collection and the problem has disappeared. I tried repeatedly and couldn't find any symptoms of it any more.
I wonder if you were right about the disk needing to spin up Karsten. What doesn't fit that theory (with my limited knowledge of this technology) is why on some clips this occurred but not on others. All the clips are stored on the same device. If the disk needed to come up to speed wouldn't that affect all the data on it?
Anyway, since I can't convince the problem to show itself again :huh: I guess it's case closed.
Ed
Please Log in to join the conversation.
Please Log in to join the conversation.
- Karsten Schlüter
-
- Offline
- Moderator
-
- Posts: 3790
- Thank you received: 718
Squamish ed wrote: …I wonder if you were right about the disk needing to spin up Karsten. … All the clips are stored on the same device. If the disk needed to come up to speed wouldn't that affect all the data on it?…
… that indeed kills my assumption
at last, new generated render files fixed it.
Please Log in to join the conversation.


