[Tangier Clarke]

This is taken from another thread I started recently (https://forums.creativecow.net/thread/59/863089)

– Artifacts show up in Quicktime, FCP X (10.3 and previous version), VLC, any media player I’ve tried.
– When playing footage forward we don’t see them (rarely). Playing them in reverse seems to show them much more.
– We’re using macOS Sierra. Problem existed pre-sierra as well.
– The digital artifacts will still show up on our ProRes 422 exports.
– We generally qualified SDHC media by SanDisk.
– Frame rates are primarily 23.98.
– Some shoots we never see these artifacts and then suddenly they’ll appear. It’s inconsistent so we can’t pin this down.
– Seems to be more prevalent in low light shoots, but not exclusive.
– We offload our cards (rewrap not transcode) using EditReady (KYNO testing in progress)
– The artifacts show up in the original , but not the proxies we make in FCP X.
– We’ve retired cards thinking it’s the cards, but it still shows up on relatively new cards.
– It’s showing up in both cameras on a multicam shoot, but not necessarily at the same moment for camera A and B.
– One C100 is new than the other by well over a year or two.

[Tangier Clarke]

It is up to date. After copying my folders over though to the top level of the other computer, now the user’s plugins in the motion templates directory aren’t being recognized. The top level one are though which was the goal.

[Tangier Clarke]

I hadn’t tried that. Is that necessary. I did use X-FX handler and noticed that “.localised” was in the name but didn’t think that I actually had to add that to the folder names. I just thought they were hidden parts of the folder names.

Ironically it just started working once I copied all of the pertinent folders over to the top directory. Before there were only “Generators” and “Effects”. For some reason, launching Motion never created the folders so I just copied them from my computer and it worked.

I can’t say for sure why, but it did.

[Tangier Clarke]

Wow!! Simon that is fantastic so much easier. I would love to know your thinking behind this method. I did it myself and it worked like a charm, but I can’t wrap my head around how you got to this method and it’s the thinking that’s where the real magic lies.

Each of my snapshots shows different text (text layers representing names of our shows). The only thing I lost in this process is that each of my text layers had a text tracking behavior on them. Although this method works it wouldn’t allow me to retain the tracking, perhaps because the clone layer is not (on it’s own) a text layer. I am not sure.

In creating snapshots like this have you come across a way to rearrange the snapshot order. In my case I want to make them alphabetical so editors have an easy time finding what they need int he popup.

Thanks again Simon. I don’t think I would have come up with this if only by accident, trial and error.

[Tangier Clarke]

This is exactly what I have done on my own. Thank you though. What I am trying to do is figure out a way not to have to manually adjust the opacity sliders for each element; particularly because my pop up menu will be growing over time.

So if I adjust the opacity for item 1 from 0%to 100%, all other sliders (or opacity values) respond by going from 100% to 0%.

[Tangier Clarke]

Thanks for the reply, but that is precisely what I don’t want to do. That’ what I have already done.
I am trying to avoid having to affect the state of each opacity individually.

For ex.
Menu:
Item 1
Item 2
Item 3
Item 4

For item 1 to be visible I have to set the opacity to zero for all of the others. For item 2 to be visible I have to set 1,3, and 4 to be zero, etc. As I add items later on I have to do this over and over for each one.

Instead I’d like to be able to set the opacity of item 1 to 100 and this will trigger all others to be zero. If I set Item 4 to be 100% opacity, I’d want items 1,2,and 3 to be zero automatically; sort of the way you can use parameter behaviors to link parameters of other things.

I am using this to make a generator for FCPX that will update over time with more menu items.
Hopefully this makes more sense. It’s sort of like having parameter behaviors for rig states.

[Tangier Clarke]

I can actually drag clips on the second storyline now without the spinning beachball showing up on my more-than-adequately setup iMac 5K with thunderbolt RAID attached.

[Tangier Clarke]

So the 10.3.2 update seems to fix the issue of dragging clips on the second storyline being so slow.

[Tangier Clarke]

Already set to default.

[Tangier Clarke]

New Mac Pro

Built in batch syncing
Built in batch export
Built in clip exporting
Slate recognition software for marking on a clip.
To be able to drag a secondary storyline clip without the beachball (happens on multiple well-qualified machines)
Better media management for archiving.