Transform on still images reset after 10.3 update?

Hi all.

I was looking at a completed video that I had done in 10.2.3 and noticed that some of my key framed transforms on my still images have reset after updating to 10.3. So I no longer have some of the motion attributes that I had set in 10.2.3 It's mainly on scale setting.

Has anyone else had this issue?

Yeah. Something definitely up with 10.3 and still images. If you have a still image in a project with some motion control, mouse-over that clip and see if anything odd happens. For one thing the size selector above the viewer bouinces between 19% and 39% and the image no longer fits the 1920x1080 frame.

This is happening where I had two or more images above the main storyline. Also if there are two or more images that have a transition which created a new storyline.

Hard to describe, but if you fool around with this you may see this behavior. I have to go to a meeting now but will try some other tests.

I haven't encountered any problems with still images yet (just lucky I think) but I have had issues with audio in projects coming from 10.2 > 10.3.

I had edited within a clip in the timeline in 10.2 (i.e. I opened the clip with Open in Timeline and cut music down in length / looped segments of it). Now that the project has been updated to 10.3, if I Open Clip to see the segments, some of my segments have been muted / contain no sound (with no volume line to be dragged up - weird). I had to match frame to the head of the segment and replace with an overwrite edit to get my sound back.

I remember when you update the library FCP does say there might be audio anomalies. Sounds like you found some.

Isn't there a support doc from Apple about this or something?

Yes, here is the Apple document describing audio behavior when updating old libraries.
support.apple.com/en-us/HT207124

Thanks. I know about the audio issue, but this thread has to do with motion transform resetting after updating to 10.3. My viewer window seems to be acting oddly too. If I mouse over (skim) a photo clip in project, the image fills Viewer window and adjusting spatial conform has no effect. I'll trash prefs to see if that does anything.

Sorry for hijacking the thread Jonathan. I was responding to Suzero's question on audio. Seems there are two topics in this thread but since you are the OP, your's should be addressed. My apologies. To your end, I haven't seen this behavior, but I only opened 1 or 2 previous projects. I'll experiment a bit more and post back if I have any info on that.

Hey DGW,

No worries about hijacking. I've probably done that so many times it's ridiculous!

I did trash preferences, which took a surprising amount of time, about a minute and a half. I also re-rendered project since prior to archiving I deleted all render and generated files.

What's odd is that this happens on a few clips, but not all. The actual pan and zoom out that I did all work, but the scaling parameters have just gone away. Also, is "Scale All" something new to 10.3? I just don't recall. Here is another mystery: I had an image that was exhibiting this problem, but I did a "Lift from timeline" and it set the image to my desired scale :blink: This worked on one image.

And unfortunately I don't work in FCP X all the time since my work is divided between still and video, and lately it's been mostly still, so like anything else if you step away from editing after a couple of months, and Add to that the 'ol brain is 60 years old and...well we all have stories.

Stories, yes, once upon a time I had a teenage step-daughter who thought everyone in the universe should be hanging on every word out of her mouth. Oh, wait, did I say "once upon a time I had"? Mistake corrected...

"Scale All" is simply redone UI. I think 10.2 and before just said Scale, and you could open the section for X and Y. What you see in 10.3 is different for that parameter than previous versions.

So I think I fixed my issue by opening a back up of my library and all appears good. I then deleted the problem library and re-named the back-up. So either I did something dumb between my last back up and the FCP update, or something just got messed up.

Happy again

Jonathan