Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Exit
FlyingFourFun
Enthusiast
FlyingFourFun
Enthusiast
Activity
Aug 02, 2025
07:52 AM
1 Upvote
@Ann Bens did you notice they export and timeline settings are are interlaced? I was expecting to see combing, wondering if the artifacts are a result of the interlace source, timeline and export? I have not worked with Interlaced footage for years, and the last project I deinterlaced it before editing started... Not to toss you a red hearing on this, just wondering about the interlacing impacts. If the OP shares a original clip, I would be willing to try the project myself and see what results I get too as I have some time between projects right now....
... View more
Jul 28, 2025
04:06 PM
Microsoft seems to have put out a statement related to the May updates for stability: Microsoft confirms Windows 11 24H2 stability issues, affecting games, tests performance fixes some potentialy relevent text: “This update addresses an issue observed in rare cases after installing the May 2025 security update and subsequent updates, causing devices to experience stability issues,” Microsoft noted in the document first spotted by Windows Latest. It is worth noting that Microsoft won’t tell us what really caused performance issues, but if you were affected, your device would have become unresponsive and stopped responding in some cases. " “Some devices became unresponsive and stopped responding in specific scenarios,” Microsoft added." Microsoft is testing the fix for stability issues in Windows 11 KB5062660, which, as I noted above, is an optional release. This means the patch is not downloaded automatically, but you’ll get these fixes when Microsoft releases Windows 11’s August 2025 Patch Tuesday update on August 12, 2025." Looks like the preview releases were available a few days, maybe check your windows update history to see if this update was already applied, mine has been:
... View more
Jul 28, 2025
04:01 PM
@Tsimdux well that confirms its probably not over clocking. I really wish I had a 5090 FE to test with right now... I have time as I'm between projects, so it would be ideal.
... View more
Jul 28, 2025
08:58 AM
1 Upvote
There are faulty GPU' chips that nvidia has managfcatured, but there is also a good chance that these 3rd party boards are building thiers differently and thus seeign different issues. Power management on the board is the most likly, especialy these overclock versions of the cards. If someone has one of these cards with issues, I wonder if they can try turning down the clock and memory speeds of them to factory OEM standard and see if there are any issues. Does anyone with a founders edition card have any of these issues would be a good data point.
... View more
Jul 27, 2025
12:23 PM
1 Upvote
@Adolfo H. I forgot to mention, it would be nice to possible at least have the option for the playhead to move to the cut point after the trim. currently it stays at the absolutate value on the time line, and I would find it helpfull if it could also follow the trim, so I can start playing the video without moving the playhead manualy. Maybe this would not work for everyone, but if it was at least an option I think it would be valuable. I am looking forward to the next update of the trim tool to see if you have changed it in some way.
... View more
Jul 26, 2025
06:45 PM
@Tsimdux interesting discovery - lookign forward to seeign how this plays out. I would like to test it, but I have a 3090 and none of the freezing issues expressed here.
... View more
Jul 26, 2025
06:09 PM
I am finding it annoying when using this to trim the start of clip, specifically when I want to trim/snap to the playhead position.. Its not obvious that is it snapping to the playhead, and all the thumbs changing as you drag is visually disturbing. The snapping to play head needs to be improved, and the thumbs maybe should not change when triming to avoid the visual noise they currently generate. It seems they are pulling the image from the current trimmed to point, and this doesn't need to be happening until at least the trim has exceeded the frame size of the thumb on the timeline - it seems to update (currently) for every frame moved in the trim.
... View more
Jul 25, 2025
08:51 AM
Chen292594190kp11 there is some logic to your approach of using game drivers and windows 10. Reading through hundreds of posts in the gaming community, gamers seem to have found acorrelation between a windows update from May of 2025 and the interplay with the newer nvidia drivers (they listed a version I just cant recall it right now). Your solution aligns with avoiding both the windows cumulative update and nvidia driver that the gaming community is pointing to for issues. With that said, I am confident that the engineering teams involved understand the issue and are working on a solution, and I think this will be solved 'soon' - but that will not be soon enough, I think soon is 2 weeks. For the record, this is my personal speculation I have no connections that could inform confirm or deny this - so take it as hope or fantasy....
... View more
Jul 23, 2025
06:01 PM
@Jawad335818487twc thats good advice for a work around that may asisst a good deal of people, thanks for sharing.
... View more
Jul 23, 2025
06:00 PM
I hav ebeen readign through a numner of other support forums, and even the gamers are seeing issues and they are deep diving into firmware. The more I visit other forums, the feel its more likly a driver issue. Hopefully its not a defect in the GPU design - which is not unheard of. Could explain why the volume of 5000 series available is low... Things like this, and maybe more we dont fulyl know about yet: NVIDIA GeForce RTX 50 Cards Spotted with Missing ROPs, NVIDIA Confirms the Issue, Multiple Vendors Affected | TechPowerUp
... View more
Jul 23, 2025
03:19 PM
2 Upvotes
@R Neil Haugen I believe the root of the export issues and possible a few others is a driver issue at its base, that will either get resolved by Nvidia, or in collab with adobe and blackmagic... I saw in the release notes there was a cuda library update, OpenCL layer update and lots of changes in the driver that could be the cause (including some comments on NVENC response changes in the driver). Hopefully we are not far from a fix, but I feel like this not 100% on adobe at this point.
... View more
Jul 23, 2025
09:28 AM
Id really like to know if this brings stability to the 5000 series cards - I am still trying to get my hands on a 5090, and I know I would not be happy if that card didn't work when I got it, and installed it - its not really a good time swapping out GPU's these days with all the different power connections now between the 3 and 5 series cards. Hopefully some feedback come sin soon. In the mean time, the 3090 with this version seems okay, I have had light use so car, and nothing is more broken 🙂 but I don't see any fixes. only thing I am watching close is when I start to play a video on the timeline, it doesn't start smooth, but after a second it fine. Not sure if its always happening or not until I get some more time in with the driver.
... View more
Jul 22, 2025
06:11 PM
1 Upvote
Today a new version came out, release notes are here in this PDF: 577.00-win10-win11-nsd-release-notes.pdf For those with the 5000 series cards, having issues, it might be worth trying this driver and advising if it corrected some/any of your issues. I noticed there was some nvenc encoder changes in the list, also Cudu and Open CL subsystem updates that may be relevent. I dont have a 5000 series card to test with or I would. 2.7.5 Behavior Change in NvEncCreateBitstreamBuffer API of Video Codec SDK In the NVIDIA driver, Release 415 and later, the behavior of the Video Codec SDK API (NvEncCreateBitstreamBuffer) has been changed to return NV_ENC_ERR_UNIMPLEMENTED instead of NV_ENC_SUCCESS when the encoder instance is configured to run in the motion estimationonly mode. As an indirect consequence of this change, the AppEncME sample application from the Video Codec SDK prior to SDK version 8.2.16 will crash due to a bug in the NvEncoder class.
... View more
Jul 21, 2025
04:16 PM
@Richard M Knight I keep trying to upvote the correct answer, it will not let me - just wanted to also say Thanks - problem solved with your advice!
... View more
Jul 21, 2025
04:11 PM
1 Upvote
@jamieclarke I wrote a nice response out to you, and the forum dumped it when I hit submit (it errored with "idea not found" and deleted my post), so this one will be shorter. Before @Richard M Knight pointed out Linear color setting, (which solved it), I tested it without the BCC effect, and same result. I also tested with version 24.3 and it also did the exact same. Enabling Linear Color solved the issue in both the 24.4 Built 83 and 24.3 versions of premier, works flawless. I never noticed this issue before, and I use this treatment often. Also; this project was never rendered for preview, does it make sense that a setting grouped in the previews would have this effect on a project that was not rendered for previews? that seems like the incorrect place to put that... Also, no frustration on this, minor issue, but thank you for the empathy none the less.
... View more
Jul 21, 2025
04:01 PM
1 Upvote
@jamieclarke Okay, wow - didnt see this comming as a solution - but you solved it by putting me into the right place with this. I had this off by default, and the issue was present: But turnign in on and the problem goes away: However, this is listed in the preview section, I am not building previews, this is all viewed without a rendering of preview files.... not sure how a setting that seems tied to preview generation is effecting the clips in this way.
... View more
Jul 20, 2025
08:02 PM
I have found a bug in the opacity of clips. I have the same clip being stacked three layers deap, intent is to use a 9x16 in a 16x9 video frame. I have the main video in Track V1, and in Track V2 I have a mirrored video, that I apply a blur and reduce the opacity to 20% to fill the rest of the screen. The source clip is a ProRes 422 HQ video, REC 709 The error is a lower than expected opacity on the video used on the right of this screen capture: The video on the right 1/2 of the screen happens to be in V2, but if I move it to V3 or V4 (and leave V2 black same condition exists). However if I move V1 track to the top of the stack, the opacity is correct for all layers. This is the settngs for the Opacity of the clips in question: If I try to crop out the main center video on the right hand part of the clip, expecting it to effect the clip below differently so the reduced opacity is not visable, it crops the video as if there is no extra black footage to the right (I hope that make sense) - basicaly it does what is expected, and crops the visable part of the video and there is no extra pixels to the right that may be causing the transparency issue. Additional observation is that when I play around with the clips placement on the video track, I notice that the clip that is on the left hand 1/3 of the screen, affects the opacity of the video clip on the right 1/3 of the screen. It can be demonstrated by turning off the video layer: With the video layer on: And now I turn off the video layer on the left side of the screen and you will see the right hand 1/3 video appear brighter with no intervention: Attempting to crop the video on the left, has no effect on the opacity of the clip on the right 1/3 side of the screen. This is Beta Version 25.4 Build 83, Windows 11 Pro for Workstations 24H2, Studio Diver nvidia 576.80 if that is needed. My work around was to change the layer for now.
... View more
Jul 19, 2025
12:21 PM
Thanks Ann, I dont typicaly use warp stabilzie (I'm pretty commited to Mocha Pro for this) but since I was testing the Beta, I thought I would try the built in effects and stumble into this as a result. It might be 'normal' but its not very pleasent either. The error was also concerning - and seems to have some effect on UI element rendering if nothing else.
... View more
Jul 19, 2025
10:01 AM
I have a ran a few other tests, continued with the Mocha stabilzie and the process as completed without error a few times. This error might not be specific to render and replace, as I cant get it to specificaly on demand happen, and there might have been soemthign else happening to cause that error. Not sure how to further troubleshoot this. will try a few more things and see what happens. If it matters, the test clip I have is about 12 min long.
... View more
Jul 19, 2025
09:51 AM
2 Upvotes
Just wondering (and maybe possible It exists and I don't know how to do this) - but why can you not do a render and replace using media encoder? I'm running into use cases where the CPU and GPU are not busy, and a render and replace running within Premier doesn't allow me to use premier, leaving tons of capacity in the system to do the render and replace as a background task. I would LOVE to see more ways to use ME to background process things like render and replace and any other suitable processes. hopefully other feel having this option would allow more work to get done when premier can remain usable while a background task runs. For example, here is how much CPU and resoures are beign used when I an doing a render and replace and a export to ProRES HQ at the same time of a 12 min clip. My system doesnt even feel this rendering... it would be really nice to have the option to render and replace with Media Encoder also (in addition to within premier) like the export project process works.
... View more
Jul 19, 2025
09:41 AM
I am getting this error when attempting to do a render and replace media; Source clip is Iphone HLG2100, H265 Effects applied to clip is Mocha Pro, stabilize Module is enabled for rendering. Output target was ProRes HQ The error message pops up in lower right of Premier, after a min or so and the render replace dialog remains frozen on "analyzing project". The dialog remains active, there is no freeze, and I am able to Cancel the process. I have tried render and replace on a clip without the MochaPro Stabilize, and no effects, it completed with no error. Attempting now to duplciate the error consistently to see what happens.
... View more
Jul 18, 2025
07:41 PM
4 Upvotes
I am getting this error in the beta 25.4.0 build 83 All I have done to generate this is drop the warp stabilize effect on 3 clips, turned on detailed and turned off fast. the error appears a short time after the the clip starts to analyze for warp stabilize. Not sure if the timeline itself is generating this error when it draws the thumbs, or the warp stabilize effect is generating it as it processes the clips. CPU and GPU are not very busy when this happened, or SSD's In this state while warp stabilize is running, premier is highly non responsive on Time line scroll, other windows are performing fine. If I move to a place on the timeline where none of the clips I have warp stabilize working on, the timeline returns to normal performance, and can play video smooth in the program monitor also. it seems that the thumbs for the time line stopped drawing after these errors appeared: I had continue thumbs on at the time, but I changed it back to show head and tail only when this screen shot is taken: If I zoom into the time line more the heads or tails still don't redraw:
... View more
Jul 18, 2025
07:19 PM
@Tsimduxthat's too bad its already disabled. If one didn't turn on the global setting there should be no reason for it play a role then. That also explains the crazy stuff I was seeing when I forced the global setting to on - PP probably doesn't work well with the setting enabled which is why the driver profile says to keep it off. I still think we will see an nvidia driver update paired with an adobe PP update that will correct this for the 5000 series cards. I look forward to when they release the update and maybe give some insight in how ti was corrected. But like others, I hope this fix comes very quick now. Thanks for taking a stab at looking at it.
... View more
Jul 18, 2025
02:20 PM
@pentian they did offer the one know workaround, which is to turn off HW encoding when exporting.... confirmed its not ideal, empathy was expressed. They will never tell you when a fix might happen because no one knows until they solve it, that it’s fixed or thought to be fixed. This is standard in the software dev world. As as aside, I was just reading that Divinci didnt have support for the 5000 series either when the cards first starting appearing, it was held back at the start... not sure if they have support now. But that might speak to the idea tha maybe these 5000 cards have something different about them... The issue may not even be Adobe's at this point. The 5000 series card have all sorts of issues, including defective GPU processors that are not know until you use tools like GPU-Z and confirm the missing video processors.... which most people don’t even know is a problem with these cards unless you are watching the game review channels. If you want to try and trouble shoot something with your 5000 series cards, I have a hunch based on something I saw when testing another system related to resizable bar. This setting gave us HUGE performance gains!! Check yours now! I think the advice in this video is bad for content creators, it specifically tells you to force on the feature so its active 100% of the time. I tried this with the expectation Premier would be faster, but what it did was memory got way out of hand, and the GPU would lock up. Putting the setting back to normal allowed the same system to run fine. My hunch I wanted to test, was if turning off resizable bar fully, would allow premier to run properly with the 5000 series cars. Based on my interpretation of the complains people have had, and what I saw when I turned this feature fully on - they struck me as similar. I had plans to try it when I got my 5090, but today I still can’t find an available founders edition in Canada. If you have time and ambition, maybe give it a try and report back on what happens. I know you probably want to focus on your work and not bother with this BS testing, but when in a pickle sometimes trying something leads to an answer. It’s a long shot, so your call - if I had a 5090 I would be testing it myself.
... View more
Jul 18, 2025
09:32 AM
Not sure if this has been noticed before but thought I would point it out. I have a test project I have been having issues with in 25.3, and I decided to try loading it in Beta. First, I will say beta runs way smoothing, and this text project that I had issues (I have other posts about it) would play back fine, unless I created a proxy for editing. Work around was to interpret the footage to 60FPS, and that allowed it to play smoothly. When importing into the Beta, none of this was needed worked perfectly. In my initial quick testing last night, I was only looking for smooth playback. I decided to dig into it more this morning and noticed there was a black flash between clips in my test project. I zoomed in and found a missing frame: The bottom clip is the one imported from the 25.3 project, The clip above is the same, but dropped in fresh from within this project. I can edit the bottom clip and slide its end point back, and that would fix the issue. After sliding the end point back, I could not extend it back to the original spot where the frame was missing. When making this correction manual, the video plays perfectly and no black frames of video. I had 4 clips on the timeline, and all of them had this issue. Two things to report I would imagine - there might by an issue opening older projects and either version 25.3 incorrectly put the clip on the timeline, and the beta project importing is working fine, or the beta has some error related to this. OR version 25.3 in the only version that has an issue, and all my playback issues in 25.3 are related to this extra frame being reported in the file. Which also sort of makes sense to me as manual interpret to 60FPS would allow 25.3 to play back the proxies created from premier to be smooth. (as using Media encoder to create the proxy outside premier, and attaching them they will also play fine if memory serves me correct, it was only when creating within premier. Either way, this is a variance in how the beta is handling this - I can’t figure out what the root cause is, but it seems important enough that if this was to roll into production, and someone were get an extra black frame at the end of every clip for a imported project it would be a challenge.
... View more
Jul 17, 2025
09:59 PM
1 Upvote
@Fergus H I just installed the Beta version of PP tonight, and ran some test on a project I was having jittery play back. I was intrigued by the prospect the beta might play back smooth with the proxy's I was having issues with. Sure enough, my playback with proxy enabled has been resolved with no manual work around. But I was also looking at the color management of the thumbs, and I can tell you they are not colored managed... do I need to turn it on? or should it be on by default? or is it not in the Beta release yet? as a re read your note, I think you may have said color managed thumbs was still on the road map... just wanted to confirm this detail. As an aside, the new timeline is in fact really smooth, responsive - I am now finally able to turn on continues thumbs and have it usable! first time in years actually. Also I am again, after years of not being able to, I can now play back the project at 2x, 3x and 4x without issues - not sure exactly what happened in the beta to allow this compared to the production version - but I am honestly surprised.... pretty excited to see what else has improved over the next few days of working with it.
... View more
Jul 17, 2025
09:53 PM
1 Upvote
a quick update. I decided to take the plug and use download the beta tonight and retest my project file I was using - and the Beta versions of premier and media ecoder, apperently dont have this bug anymore. Timeline playback to be honest seems very improved even as I switch back and forth between beta and non beta... So far, it seems the next release may actualy solve this without the work arounds - fingers crossed.
... View more
Jul 17, 2025
09:50 PM
I am not convinced there are wide spread issues with the 5000 series. The forum is basicaly a collection of people who ahve issues. I am confident there are many people without problems and the 5000 series. Frankly, Id still buy (and I am hoping to secure) a 5090 FE - there is no way I would buy a 4090 right now if I had a choice, if there is a glitch, I am sure it will be sorted soon. As a matter of fact I decided to run the beta, and found that the latest beta solves a playback glitch I was having... I dont thin its even documented that this glitch was resolved yet, but its fixed butterly smooth playback. I am not convinced there is a wide spread issue with the 5000 series, and if there are a few glitches, I suspect they will be corrected shortly.
... View more
Jul 16, 2025
10:18 AM
Thats too bad, they were a very relaible source for this info all in one place, and very detailed. GLad they still have pugent bench at least.
... View more
Copyright © 2025 Adobe. All rights reserved.
AdChoices