Skip to main content
Participant
August 3, 2021
Question

Screen Tearing XAVC S 4K 422 10bit

  • August 3, 2021
  • 12 replies
  • 16488 views

I switched up my settings on my Sony FX3 to XVAC S 4K 422 10 bit before visiting DC with my daughter.  I took a ton of footage using this setting, only to come home, upload everything to premiere and discover that there is a TON of screen tearing happening.  At first I thought it was just Premiere being problematic w/ playback, but even after exporting, it shows up in the file.

 

Camera - Sony FX3

Laptop - MacBook Pro Apple M1 16 Gig

 

Please help,  I've googled to the end and back.

 

 

12 replies

Kevin-Monahan
Community Manager
Community Manager
August 6, 2021

Hi Michael,

It's a known issue with the 10 bit footage and 15.4. You can try an 8 bit codec or another codec, if the camera allows it. You can also use an earlier version of Premiere Pro. The team hopes to fix it soon. Sorry about that.

 

Regards,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participant
August 6, 2021

Hi Kevin,

 

Thanks for the quick reply. For now I'll switch back to an 8 bit codec. As a follow up question, I was looking at purchasing a Ninja V or V plus to take full advantage of the cameras sensor. Will I run into any similar issues working with ProRes?  Or does premiere handle that well?

Kevin-Monahan
Community Manager
Community Manager
August 10, 2021

No, I'm actually a fan of that device, Michael. I think it would be fine. ProRes is rock solid. Only issue is large file sizes, which some people are a little unprepared for. 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Participant
August 3, 2021

I recently upgraded to 15.4 on my M1 Mac Mini and random rectangular glitches started appearing across my footage. I thought it was just while I was edited but soon discovered the glitches are being baked in. Yes I sent a finished project to a client and they weren't happy.

 

I rolled back to the previous version and the problem is gone, I was able to export with no glitches.

So now I'm paying a monthly subscription to use an old version of Premiere because the version that is supposed to be optimised for my chip doesn't work...

 

I've noticed lots of other people with the same issue in the Premiere Pro Facebook users group.

When will this be resolved?

Kevin-Monahan
Community Manager
Community Manager
August 3, 2021

Jake,

Sorry, friend. Looks like a format problem. I'm guessing you use Sony cameras? In that case, this is a bug and you should probably work in the earlier version, as you found. Since we have little information about your Mac or anything on your original footage, my solution is only a guess but it sounds like that's the path you need to take for now. Apologies on behalf of the product team for that.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
Kevin-Monahan
Community Manager
Community Manager
August 4, 2021

My Mac is included in the post title, it's a Mac Mini M1 with 16GB Ram and yes that's correct I'm using Sony cameras. Sony A7Siii.

 

My video files are 1080p 50fps H.264 -10 Bit . The bug also appears when I use Pro Res proxies as well.

 

Any idea when this bug will be fixed? is it being worked on already?


Hey Jake,

Sorry about that. Sounds like the footage is the issue then. The issue can be worked around by transcoding 10 bit footage to ProRes according to the engineering staff. I would create your proxies from these transcodes to see if that might work. Otherwise, you can use an earlier version of Premiere Pro or try a different format with your camera.

 

As to when certain bugs get fixed, it is one question I really can't answer directly. Sorry. Bug fixes are a moving target and may have unforseen dependencies. That, and Adobe simply doesn't allow me to answer "when" questions. So, I don't.

 

As an editor, the best thing to do is report that bug here. It can be upvoted there by others. Then, work in an earlier version and install the current version of the beta to see if it has been addressed or not. If it's not there now, it may be showing up in a future beta, hopefully. When it shows up in a beta build, it's on its way to get fixed in an upcoming version. That's the big indicator.

 

Apologies that I can't be more helpful. I am tracking the issue, a ticket is filed internally and am advocating on behalf of users like to you to fix this one ASAP.

 

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio