Ouch it seems like it is due to file being created read only? As soon as I remove the read only mark, the adobe isn't crashing anymore. Hm, seems like it is other issue. Idk which one. It does it randomly.
Any way I can help you with debug? I can record a video with what is happening if it might help. I'd be happy to resolve it, as i like vouk a lot. Still just have to remove the RO option from folders and then am able to export. Maybe it is an anti virus software or something similar that is blocking the file?
It seems no other user has experienced these kind of issues. I've paused the AV and still the same. It is not due to RO protection. It just happens randomly. Like 3 times it is ok and other 5 times is not. And vice-versa. I've reinstalled the Premiere now. Also connector and plugin itself.
As soon as I save new preset it becomes doing these freezes. Anyway I can debug it further? Adobe Premiere just hangs and then windows says it is not responding.
I tried a lot of time loading AP without saved preset and it was working fine. When I saved the preset, closed the AP, opened it, tried to export media and bang. Topics details. Game-Ready Drivers. By Recency Recency Votes Hot. Filters 2. Mark as read. GeForce Announcing GeForce Hotfix Driver Windows 11 - Strange behaviour when gaming with two monitors.
Drivers newer than Screen Freezing on League of Legends end's game screen. DPC Watchdog Violation. Dispaly driver crashing and recovering.
Win 10 freezing at unlock with Small dips in fps but feels like a huge freeze. Battlefield 5 stuttering with new drivers. Have to reinstall nvidia drivers every reboot or low fps. Errors on This site uses Akismet to reduce spam. Search Join Now Login. Sort By. Notification Preferences.
Forum Actions. Report Post. Same problem here with premiere elements 13, definitely after updating nvidia driver for gf to Seems it is with all Elements versions prior to Can't really expect all owners to upgrade to 15 just because of some Nvidia driver change no real beenfit, as new versions hardly bring any useful changes.
If possible, please undo this change that causes this error. Unless it is something essential to other functions. Just ask the Mac people, and hear what a grief it is on MacOS with backward compatibility, it's absolutely horrible there. That said, Premiere elements 11 is a relatively old version. Maybe time to upgrade, or buy a newer version used? How much did you pay for the Nvidia card in your PC? I chose to upgrade my video card because I was no longer satisfied with my old one and had to save up for it.
But seeing that PE15 is not affected amazing coincidence? Well, as it also seems to affect Premiere Elements 13, and even version 11 is not that old, i guess you and others have a point, it really should work. No idea why a graphics driver breaks compatibility with a video editor, i always thought that video rendering should be a pretty straight forward task, but what do i know.
I have a workaround for this. It isn't ideal, but it allows me to work around the crash. This isn't the first time an Nvidia update and Premiere Essentials have had issues. Previously there was no fix but to roll back to older Nvidia drivers, and of course that works here too. But if you want to keep the latest drivers and still use Premiere Elements In my case version Do this.
Phil, " not happy. Since it is a current version, I suggest you start a online "chat" session with Adobe staff where they can trouble shoot your system remotely. I've upgraded to this and now I can work on 4K video. By the way, when I first tried a 4K video on the new laptop, it wouldn't open, so I followed the instructions, including emptying the media cache, then it worked great.
Are you using the "Render" preview button? My experience is that, as long as there is plenty of spare space, an SSD drive for the project, source files and scratch files significantly improves performance. But, there has to be plenty of spare space! Adobe Premiere Elements 's performance is absolutely abysmal! It constantly freezes to the point where it must be terminated, and is a complete pain as a consequence to try to work with it. The product is clearly not ready for release, even with the February update, but this is what Adobe's amateur developers and architects foist on Adobe's user base.
I recommend looking for an alternative product until Adobe get's its development act together. This is really, IMO, unforgiveable: Adobe should know better than to put out such beta stuff in a release.
In fact, such freezes easily manifest and are easy to reproduce: just try switching back and forth between Export mode and one of the other modes a few times, on an average computer system: pretty quickly you'll find the product freezing. Adobe's GUI is itself the problem. The product is clearly not ready for release My experience is the exact opposite.
Premiere Elements is on version I started with version 9. It has been very reliable on a series of four different windows laptops. I have a workflow that puts all the source, project, scratch and output files in project specific folders on an SSD.
I've been editing 4K with the last three versions. With the virus lockdown I'm spending time learning Premiere Pro. I'm finding Premiere Elements has several advantages, including a level of "simplicity". Without knowing more, my first guess is that you have an audio hardware problem. There have been posts here where the Audio Hardware settings go wrong, perhaps due to Windows updates.
Try setting them to something different or to "None". It seems that PrE and your computer can get bogged down on wrong audio and will bring the entire process to a halt. Another choice might be to try changes to the preview preferences in the General preferences tab. Or do both.
But disabling the microphone in Windows 10 is actually the ONLY way to mute the microphone successfully on many Windows 10 systems, as the Mute checkboxes and controls do NOT function properly on many Windows 10 installations.
Premiere Elements should be able to handle such situations gracefully, and if anything, simply notify the user that the sound hardware e. But these days, that seems to be too much for Adobe's folks.
0コメント