Export Output has a glitch no matter what I try. Started with the last release of Premiere?

[danlockhart]

Current version. 

I have tested this every which way you can imagine.  I updated the NVIDIA drivers to the current version and tested with hardware encoding on.  Got the same glitch.  I've been working on this for several days and spent many hours of time testing. 

I need help. 

I successfully exported video a week ago. 
https://www.youtube.com/watch?v=yfPMKGkpsnY&t=18s 

This is super frustrating. 

[Graeme Bull]

I'm not sure if this is too obvious, but have you considered rolling back a version of Premiere?

It might be a good idea to lay out what you're doing though as it's not easy to understand. I believe you have 360 video that you've made into 4k normal. Did you use a plugin (Gopro's FXreframe) or just in Premiere? Try to be as detailed as you can as to what you've brought in, editing, output etc.

[Graeme Bull]

Here's your response for other people to read:

Really? OK.

1) the source file was a GoPro Max .360

2) I converted the .360 files to .mov files using the GoPro Max Exporter.

3) I then imported the .mov files into Premiere.

4) I spent several hours/days editing the .mov files in Premiere.

5) I exported the projected, initially using Match Source, Max depth, Max quality

6) After exporting for 8 hours the video had the same glitch as described above.

7) Tested a smaller version of the export many times, using hardware encoing, using software encoding, different resolutions, different quality settings and all had the same glitch.
8) You can even see I even installed the latest NVIDIA driver which was released August 27, 2021 (about three weeks ago). But as I said I tested with just software encoding too.

9) I can view the 360 .mov files in GoPro VR viewer and I can even upload AND view the unedited .mov files successfully in YouTube.
10) In my original edits I used GoPro VR Horizon, Lumetri Color, Audio Ducking and Cross Disolve transitions.

11) In my testing I did not use any effects, ducking or transitions.

12) I tested Preset Match Source High Bitrate 5760X2880, Preset YouTube 2160P 4K Ultra HD, Preset YouTube 1080P Full HD all with hardware encoding (High Bitrate would not take the "hardware" setting) and without hardware encoding (software encoding). The same glitch appeared in all my testing.
13) SUMMARY

I'm current in my Windows updates:

And I have not changed or added any hardware (other than to update NVIDIA driver) to my system since my last successful export. 

My conclusion is that something changed either in the latest release of Windows or Premiere that creates the problem for Premiere.  I will not be rolling back my latest installation of Windows.  That would be just stupid. 

Your comment:

"I'm not sure if this is too obvious, but have you considered rolling back a version of Premiere?"
TOO OBVIOUS? I'm pointing out a potential problem with the latest release of Premiere and you make a comment like this?  Is there some kind of advisory to your customers to just roll back the software to the previous version if you have any problems with our software? To be honest I find this comment somewhat disrespectful and condescending. 

"It might be a good idea to lay out what you're doing though as it's not easy to understand. I believe you have 360 video that you've made into 4k normal. Did you use a plugin (Gopro's FXreframe) or just in Premiere? Try to be as detailed as you can as to what you've brought in, editing, output etc."

I hope that I've given you enough information to make it "easy" for you to understand.

I did not use "reframe" in this project because I have never been successful of creating a 360 export that has reframe in it.

Here is what my processors look like on my IBuyPower computer.

[Graeme Bull]

Good luck with your problem. Too bad you're so rude to people who are just trying to help you. I'm not adobe support, just somebody here that tries to help as many people as possible.

[danlockhart]

Ok.  Thanks for your comments and posting of my comments for other people to read.  Yes, making a comment like "I'm not sure if this is too obvious" felt disrespectful to me. 

It was a long comment that wouldn't post for me. Under your name it says "Adobe Community Professional"  One might assume that title is Adobe support. I'm glad people can read all my comments.  I tried posting it several times.  I'm glad if others can see the situation and have wasted as much time on this problem as I have.  If it helps them in any way, great.  

Good luck to you.

[Christian.Z]

Have you tried deleting preview files?

[danlockhart]

No. What does that do? 

[danlockhart]

Yes, I have now tried deleting preview files and it didn't help.  The export still has gltiches.

Thanks for the suggestion though.

[Michael Grenadier]

First thing to try is a smart render

https://community.adobe.com/t5/premiere-pro-discussions/faq-what-is-smart-rendering/td-p/10648488

by any chance was the material shot on a smartphone or a screen recording?  If so, the issue may be that the source has a variable frame rate.  Here's how to confirm it and fix it

use mediainfo to determine whether your source is variable or constant frame rate

https://mediaarea.net/en/MediaInfo/Download

if it's variable use handbrake to convert to constant frame rate

https://handbrake.fr
and here's a tutorial on how to use handbrake

https://www.youtube.com/watch?time_continue=34&v=xlvxgVREX-Y

[danlockhart]

I recorded this video with a GoPro Max 360.

[danlockhart]

After many hours of testing and many exports with various settings, I have determined that I'm still unable to export with any type of VR effects (VR reframe or VR horizon) and not get artifacts.  I am able to export successfully without any VR effects.  On the 5760X2880 Match Source export, it renders everything. On the 3840X2160 YouTube4K preset it renders but, there is a black circle in the top of the video (I assume this is due to the dimensions).  The YouTube4K preset gives a cleaner, higher quality, render than the Match source 5760.  

I tested with current version of Premiere V15.4.1 build 6 and  a back version V15.0 with the same bad result. I also attempted the Smart Render.  I tested with the deletion of the preview files with the same bad results.

All the footage was shot with the same frame rate, with the same GoPro Max 360 camera.

The problem is still open for me, but I've moved on by not using any VR effects if I want to export in VR.