[Joby Anthony jr]

Optimize only pops if your footage isn’t natively optimized. In other words, more difficult to edit footage such as h.264 typically will provide the optimize check box. But if the codec of the footage is already edit-friendly enough, then the box stays greyed out and you’re otherwise good-to-go, at least from FCP’s editing needs.

Joby.

[Joby Anthony jr]

I’m not a super-user of Audition, so take this FWIW. But my first thought was wondering if that was a plosive into the mic? And even if not, wondering what impact applying the FFT effect would have (FFT -> Kill the Mic Rumble).

At least as a first pass. But I think ultimately, I’m not sure that you’d be able to get rid of it entirely, but could probably at least have some success at minimizing it by using the Spot Healing Brush Tool in the Spectral Frequency Display mode.

Joby.

[Joby Anthony jr]

I too couldn’t see the attachments. But my first thought was wondering about the type of bezier curve the keyframes default to. I’ve encountered oddities like that in the past that boiled down to this issue. Here’s a Larry Jordan link that explains it. It’s an older article, but I believe remains relevant.

FCP X: Keyframes and Curves | Larry Jordan

[Joby Anthony jr]

Forgive this very late posting, but I ran across this post and noticed no one had responded. So FWIW, my thoughts are image stabilization fighting for control. I don’t have any experience w/ the 605, but I know on our C100s we try and turn off all stabilization controls, even on the lens, whenever mounted to a tripod, for this very reason–a concern that whatever image stabilization exists in/on the camera ends up fighting the otherwise stable tripod. And wondered too, depending on where you were located, whether there was a tremor on the platform, like someone bumped it.

Anyway, my seat-of-the-pants first impression after looking at the footage. Am guessing/hoping you eventually figured it out, and if so would love to know what you learned.

Joby.

[Joby Anthony jr]

Good afternoon Tod!

I do not seem to experience what you’re describing with the transform effect. I too am running on silicone and v23.0.0. Anchor point seems to hold no matter what I do with the shutter angle. Seems to be working as expected on my system.

Joby.

[Joby Anthony jr]

Apologies Jeffrey, I don’t have a ton of experience with multi-channel audio, but wouldn’t that be something where you’d have to Modify -> Audio Channels in the project bin first, to separate all of the channels into Mono. And then from there, the Sequence settings would need to be setup for the output too. Which may auto setup for you if you were to simply make a sequence from the clip (e.g., drag and drop on to the small New Item icon)–maybe?

Joby.

[Joby Anthony jr]

Update #2 (for those following this). I’ve now posted a bug report to Adobe. Tagged on to another thread dated 2/11/22 reporting playback and export glitches off of a NAS. Not my problem exactly, but there does seem to be some type of issue with Adobe trying to nail-down all of the nuances of working with myriad footage types and the M1 architecture.

Oh! And have upgraded to the latest version (23.0.0, Build 63), and though the issue remains, I am now seeing the GPU and all of the cores get maxed out on exports. So definitely some performance improvements, just not in this specific use case.

And lastly, attaching a screenshot example of the glitching. Again, same issue whether playback or export. (And those are hands clasped together, in case you’re wondering.)

[Joby Anthony jr]

Good morning Bob (and all)!

Couldn’t agree more, but then I really only have myself to blame (and the tyranny of deadlines . . .). But yeah, Creativecow was there for me long before any of the other outlets (except for YouTube, which has already been mentioned as hit or miss). So out of loyalty, nostalgia, and the level of professionalism, I make this my primary source. But I’ll admit to sitting mostly in the stands, watching and learning from the conversations than participating. But then, what do I have to offer? (alas)

But agree with Mads, I hear you and see you.

Thank you Brie for the explanation of why my Inbox went dark!

And Eric, “Friends don’t let friends do awful workflows.” lol. +1 to that statement. Though I’m pretty sure I have some awful workflows, which goes back to “what do I have to offer?”

But nonetheless, thank you to all, including the Cow wranglers at homebase who have soldiered on through the ups and downs to try and keep Bessie unconstipated and running smoothly.

Joby.

[Joby Anthony jr]

Good morning Raydrick!

I’ve experienced similar issues on a recent M1 Studio too. Not the pathing issues, can’t help there other than to do what Mads said and consider upgrading to the latest. Guess you’d want to test that out.

But the renderer being greyed out, I “think” is an M1 thing. To toggle to Software Only you have to put Premiere into Rosetta 2 emulation, which is supposed to get Premiere to act like it would on an Intel machine. And from there, your results may vary, but at least you can then test out that option. Command+I the app and check the Rosetta 2 box.

As for the glitchy footage, I’ve been chasing down something similar. About a year ago all forums seem to suggest that Premiere had problems with h264. Mostly export related. And that the solution at the time was to go to the Beta version (which we’re well past now) and/or put it into emulation mode. So if you’re on an older version, you may indeed find some benefit from going to the latest.

But what I’ve been experiencing “seems” to relate to playback and export (within Premiere only) of AVCHD 60p (59.97) footage. Still testing, so this is only my latest working theory. But my current doable workaround as been to transcode the footage to ProRes HQ 30p (29.97) to match our timeline.

I feel your pain. Has definitely taken off some of the luster of the M1, especially given how powerfully fast it seems otherwise. Oh, and FWIW, I’m hearing that Davinci Resolve plays very nicely with these machines. No experience, but maybe another option to consider to get the film out on-time.

Joby.

[Joby Anthony jr]

Update:

I’m beyond frustrated. First thread was about simply documenting what I was experiencing–for posterity–as much for myself as for anyone else doing searches. Wasn’t really asking for any help unless it sounded familiar to someone. But now I am–some kind of clue, or something.

I noticed the other day the glitch (or better described as frame warping) in the Source monitor. Meaning, out goes the theory that it is related to graphics, alpha channels, framerate conversion going from 60 to 30 in the timeline.

Current theory? May have something to do with the way Premiere interprets the h264 codec, and specifically the 59.94 version of it. Maybe? Because I’m not seeing this anywhere else (e.g., FCP, Quicktime, Finder).

Testing of other outputs at 29.97 doesn’t seem to do it. At least as of right now in my small batch of testing. Our group has done thousands of videos over multiple years with the same workflow, and this issue has only popped up with the introduction of Apple Silicone into our group. And we’ve seen this across the laptop, iMac, and Studio. Same frame warping of footage. And it’s random. As in clearing the cache will make it disappear from one section of the footage, only to have it show up in another section.

So again, any clues to solving, or confirmations of the issues, would be helpful. Thanks all!