well, use to be...  with Covid not sure that's safe either. ... View more

Thanks Carlos, Ann's good eye on the position of the play head turned out to be the issue.   ... View more

Thank you for the information, I was in the middle of reading your reply when Ann's response came back.  Her observation was in fact the exact reason for my issue.  ... View more

Ann, I can't believe I Missed that! I guess in my excitement to test, I must have let the video play out, and didn't notice the head at the very end. An embarrassing moment, as soon as I read your note I knew it, but of course I just checked and yes, this is exactly what appears to be happening.   I have not had this before, but your 100% correct here.  User error on my part. Thanks for catching it. ... View more

SimonAllen; I read all the responses to your question; I would like to make one suggestion I didn't see. Have you performed a Trim for your SSD?   (Defrag for SSD).   I would also suggest you run the windows disk clean up if you have not done that recently.  Also Click on the "clean up system files button before you click on okay. Once that's done,  do the trim (defrag for SSD).     This is a bit of a long shot, as your issue appears to be with read performance,  Retrim largely is for write performance issues.  But its only a few min of work, and good practice anyways.   I hope this easy to implement advice finds you some success. ... View more

Andy 1968; His card does have NVENC: Video Encode and Decode GPU Support Matrix [NEW] | NVIDIA Developer   It's the bottom line of this Matrix GM206 He could compare the footage his using to what's supported on the matrix; OP might be using new footage/settings that genreate files not supported by his generation of NVENC. ... View more

If you do the upgrade to 15.2, I suggest you check your settings and ensure that it doesn't uninstall the current version you have. That way you can revert... also DO NOT open and save over a project file, often when you open in a newer version the project file cannot be read in older versions, at some point Adobe was trying to make this less of an issue but DO NOT take the chance with project files.   15.2 has a bit more issues that most people would enjoy (myself included).  15.1 was rather good for me, but 15.2 makes some substantial changes to the render engine move to DirectX 12.  If you don't have to be at 15.2, try 15.1 for a while.   As for how often hardware support drops between versions, it does happen, but you can mitigate that risk by checking the requirements before the upgrade, leaving your old version installed while you test the new version, not overwriting your older project files with new versions etc.  There is a discipline you need to follow to avoid upgrade drama. ... View more

Sounds like a normal thing that happens.  Premier does that to allow for playback to be smooth on systems; There is three things to check if your system can handle full quality playback, you can enable.   First, on the program monitor ensure: In the view menu, when your active window is the program monitor, change the playback and pause to full or what ever looks good anbd works for you:   And, again if your system can support it, turn on the "high quality playback"   As Peru Bob also suggested, rendering the timeline can also improve the playback so its not blurry.  The bottom line is you have to play with all these levers based on your system if you want things to be 'perfect' while previewing your work.  Your always making a trade, quality for speed.  Premier lets you tune those choices.   If, at the end of the day, I suspect your concern is on export that the text will be blurry.  If that's your true question, the short answer is it will not be.  You can export your work, and play it back it will be fine.  When you preview it without pre-rendering, premiere builds the scrolling text realtime, and it seems to have decided to lower the quality to keep the video smoothness on your system.  You can tweak the above settings and if your system can support it, it will play back perfectly clear if you don't have to much happening on the timeline while playing that part of your project.       ... View more

Can you paste the log files from media encoder?    A couple of quick observations.  Your memory, and your system, appears to be over clocked?  I'm not an overclock expert, but I goggle'd the I9 9900 and it says the memory is:   The specs you provided, show your memory at 1599, which if my memory is correct, needs to be doubled meaning your running at 3200 for speed.  you might have Memory XMP mode enabled, and while mother boards support those speeds, I have found that they often don't play well with resource intensive applications.   If you have this machine over clocked, I would suggest returning the memory speed to the default for the machine at the very lease.   If you have it over clocked, try putting it back to default before you export.  At this point, you have not described exactly what a 'crash' looks like, I am sure anyone reading your post would like to know more about it.  This memory speed was just an quick observation.     While we cannot see exactly what's on that timeline, it's also not overly complex.  The nature of your crash will provide insights.  Can we assume you have cleared media cache and all that typical stuff? Adobe Premiere Pro 2020 - How to delete all media cache files - YouTube   Also, have you tried other export options?  such as H265 or ProRes ?   Overall, more information on the nature of what happens, and any codes returned etc. would be helpful.  Also, is you 'crash' always in the same spot, or in the same way.  Please fill in the details for those that might be able to assist.   ... View more

Nothing to change as far as I can tell; Here is the release note:  It implies that DX12 replaced OpenGL, and it ONLY switches back to OpenGL if DX12 is not available.  But I'm not 100% sure - that's how I read the notes.   ... View more

That rolling shutter like effect might be screen tearing.  I had that issue, and the solution was to turn ON Vertical Sync for the Premier Applications in the nVIDIA control panel.   There is a post a made a few days ago, marked with the correct solution: Solved: Screen Tearing & Freezing When playing Back Premie... - Adobe Support Community - 12028311   ... View more

Thomas, your welcome!   I am running a 60hz refresh.    I only use this machine for video, so 60 is good enough for me 🙂 I have always left the NVidia control panel at default as not being a game player there has never been a need to mess with it.   The only application (I have) that seems to like to adjust things in Nvidia control panel is Topaz Video Enhance.  They seem to have published an 'optimized' mode for that application in a recent studio driver release.  But I have not tried the optimized settings for that app so I don't think that's connected to this issue. ... View more

It appears they have made a significant update to the way scrubbing timelines refreshes the program and source window when an h264/h265 video is in use.    When you drag the play head around, the video cards decode spikes, and can be driven to near 100% utilization on my 3090.    The reposition of and update of the video frame when scrubbing h264/265 timeline is very responsive.   It's impressive actually.  now if I can get the 'not responding to play' thing to not happen, I could be very happy with 15.2, ... View more

You're welcome! Glad to get you back on track and doing the creative part and getting frustrated waiting for things to finish. If you're still seeing some choppy playback when you render the timeline, you might need to tweak the seq settings, so it used a better codec for your machine.   Most of the time the ones that start with "DN" on the list below work well, try changing the setting, it should help.  BUT do not use the one with 1080i (interlaced) there is no reason to use interlaced - you will know if you need it, don't use it otherwise.     ... View more

Under what conditions does it do it?  I noticed that when I first open a project from a version earlier than 15.2 the bottom left corner of the screen will display this message: I was not able to capture the messages before it said 'all media loaded' but I have seen this process take a few min and the media was pending while it was doing it.  It seems, that based on your disk speed and volume of media, this can take a few minutes or more.   If I let it finish, it works fine, and contained to to be fine the next time I load the project.  I have not seen this before the 15.2 update, so keep that in mind. ... View more

I think the big gain here is HDR support... The performance is better in DX12 vs OpenGL, but the truth is pretty much DX12 is where the industry focus is and will be for the foreseeable future.   Stability, I believe is derived from the fact that there is constant (and consistent) development for DX12, bugs get reported faster, more often and thus give you stability.   The secret (once you're in the club) words they used in the release notes were 'modern development environment'.   Moving to DX12 is a good long-term plan.  The fact we get HDR support now, and a small 'speed bump' is good, but long term is why this change is important.   I suspect that we will see some features within premier get updates and performance will climb as portions of the code continue to get moderinized and stay in sync with the video card hardware and drivers much better going forward.    There is also a reduction in the cost of devolopement that Adobe will benifit from, but we will get updates and bug fixes quicker as the API's they need to manage gets reduced in complexity.   I also egerly await other persepectives, I look forward to seeing additional responses to your question. ... View more

Thomas; Thanks for the tip; I went in to apply the correction noted in your link and posted into the message.   The current state was already off (screen shot below).  I cannot say if that settings default value changed with the driver, I just applied, as I applied the driver update before I looked at this setting.   I can say that even in its off state, the tearing was there.  It was not until the vhold setting (noted by scrozier) was applied that the tearing resolved.  I'm still not convinced it's as good as it was before, but the tearing was not even bearable, so this is an improvement.   Thank you for the great advice, and direction none the less.  You tip may be applied as the default setting on the 462.59 05/11/2021 driver.  Maybe someone with an older version can check the setting before they update if we as a group feel its important to have that documented.     ... View more

scrozier Your solution worked.  As an important note, making the change with premier running did not take effect until premier was restarted.   Before I tried your suggestion, I tried the new driver that I posted about earlier, and it had the same issue, so I know for sure your setting was what made the problem go away.  I'm not convinced it's the overall correct solution, as the frame redraws are still more 'flickery' for me than playing outside of premier with media encoder.   I am going to try the suggestion proposed by Thomas also, and see how it effects the outcome.  I shall post shortly.   ... View more

I noticed the HD audio driver was also updated, screen shot below for the records.     ... View more

Thomas, thanks for the feedback, Looks like a new studio driver was just published 462.59 05/11/2021 I am going to download and retest with this driver and report back.... if it is still there, I will continue to test with your advice above.   ... View more

Not a pilot;  Some in the family (helicopters).   I fly Drones, less exciting, under most conditions anyways. My daughter is expecting to get her license also as she wants to go to space (so pilots license, and either a Medical or Engineering degree before entering the space program when that all works out).   If you have the time and money, being a pilot is great, everyone I know that owns aircraft loves it.   The final stages of writing the file are magnified when exporting to NAS, but always present.  Local disk seems to fly through the same process;  I have captured a number of data points and screen shots below to illustrate the point.   Here is what the folders look like when it starts: Here is what the folders look like after it reaches 100% in Media Encoder: On the test export to the NVMe, those 3 extra temp files where only there for about 40 seconds before moving on to the next test file in my que.   When its done, this is the only file left This is the text from the Log file for this test to NVMe   04/24/2021 06:11:24 PM : Queue Started - Source File: REDACTED - Output File: H:\TEST DELETE ME LATER\NVME EXPORT TEST.mp4 - Preset Used: CONVERT to H265 - Video: 3840x2160 (1.0), 59.94 fps, Hardware Encoding, Nvidia Codec, 00;30;00;00 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 40.00 Mbps - Encoding Time: 00:26:15 04/24/2021 06:37:39 PM : File Successfully Encoded * About 40 seconds of time of stuck at 100% before moving on to next item in que   Here is a screen shot of Task manager.  For good documentation purpose, the source for this sample 30 min project file is on a different NVME from the drive being exported to,  but as you will see there is only 1% utilization on the disk IO while premier processes the video.     For the Nas & USB Tests files in folder are the same as NVME test so I will not bother to repost them, you will have to trust me on that point I guess.   However here is an example of how the file grows in size, its slower so easy to capture when writing to a NAS and a few min later: Task Manager shows Network traffic significantly higher: Here is the Log file: - Source File: REDACTED - Output File: P:\Delete IF you need Space Only\NAS 10g EXPORT TEST.mp4 - Preset Used: CONVERT to H265 - Video: 3840x2160 (1.0), 59.94 fps, Hardware Encoding, Nvidia Codec, 00;30;00;00 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 40.00 Mbps - Encoding Time: 00:29:45 04/24/2021 07:07:25 PM : File Encoded with warning ------------------------------------------------------------ Adobe Media Encoder Could not write XMP data in output file.   I included the above to show that rendering it only took 25:38min, log file shows 29:45min,  I manually timed portion that was post 100% and got 4:07min.  So you can see the log file captures the total time even in the post 100% mux stages;   This is the point where you can see that the exact same file, is basically 10x longer to do the final mux of the different files.  The time, increased the larger the final file is.  The temp file grows to the same of the video,  then it disappear, then it muxes the audio file, and that disappears, then finally one file is left that's the final.  The XMP write error often happens, but not always, video always play fine BTW with or without the error.   The Task Manager for the test to NAS @ 10gb, note the network transfer speed is approx the same as the bit rate of the file.  This is while its rendering the file,  not the MUX (post 100% complete) task manager view.   And for the USB3 test file here is the stats, I don't think screen shots are needed as you can see the pattern. FIle took 25:33min to get to 100%, and then another 5:42 to Mux the 4 files down to one.  I was surprised as I thought the USB3 drive export was faster in this stage than the 10gb nas export, I guess I was wrong.   - Source File: REDACTED - Output File: J:\TEST DELETE ME LATER\USB3 EXPORT TEST.mp4 - Preset Used: CONVERT to H265 - Video: 3840x2160 (1.0), 59.94 fps, Hardware Encoding, Nvidia Codec, 00;30;00;00 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 40.00 Mbps - Encoding Time: 00:31:14 04/24/2021 07:38:39 PM : File Successfully Encoded 04/24/2021 07:38:39 PM : Queue Stopped   To sum this all up;  exporting to anything other than local disk (not usb) seems to take much longer to mux the final file.  It would be really nice if Media encoder at least started processing the next file in the que because the GPU and CPU sit with nothing to do, in that final mux stage.  Not to mention, the network traffic is very low and has room for another stream.   The USB drive was pushing around 100MBs when it was muxing if that matters, slower when it was rendering the video.   I hope that helps you capture the idea of what is happening with this.  for the record that (lets call it 4 min to 5 min on a 30 min clip) is for sure related to how long the exported clip is, so if you can improve this, it will have big impacts for those using NAS/USB and longer exports.   ... View more

I have the same experaince as you.  Its worse when exporting to non local disk or even USB, but not very noticible when exporting to my local NVMe drives.   I ended up watching the folder I was exporting into and found that after the export gets to 100%, media encoder seems to create a temp file that grows in size to the same as video file, then it appears to mux them, and removes the temp file.   Liek you, its releated to the project timeline lenght, and is magnified when exported to a NAS or USB drive.  I have not seen significant ethernet traffic to the NAS after the export, but yet its slow.   I honestly dont know if this is normal or not, but its been the case for me size I have ran premier.   I dont think I have had to wait hours however,  but like 30 min for 1.5 hour exports.  I run 10g newworking if that matters.   I am eager to see if others have some insight into this.  Its a very interesting question. ... View more

You can also referance this video as a suplement to the information shared by Neil. https://www.youtube.com/watch?v=xw7qBCA6gMk  ... View more