Duke Sweden
Forum Replies Created
-
I’m not whining. I’m just wondering why this PC, whose specs you can see in my sig, has difficulty handling what my previous PC handled with no problems (other than being super slow). I’m looking for answers. NOT whining.
It’s like owning a 2010 Mustang that I could do 90 mph in easily, then I get a Ferrari, but I can only do 70 because anything above it causes it to overheat.
Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Oh well, at least I’m on to something here 😉
Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Greg, that quote you included referred to Brent’s assertion that he has never seen a post from me in which everything worked flawlessly.
Anyway, I agree with Chris, but, again, what is the point of plugins if they don’t work. Strictly a rhetorical question. Thanks for responding.
Dell XPS 8920
Intel i7 core 7700 build
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Thanks Chris, but then what is the point of FilmConvert Pro and any other plugin if they cause crashes which, btw, after cleaning my media cache, (which I do every day) the same file rendered with no problem. So strange that with all the storage space I have now, all the processing power, all the GPU, this can’t handle stuff that the other PC handled, albeit veerrrrrrrry slowly, with no problem.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
I was literally sitting here running a test encode as I have since yesterday, to make sure things were all working normally after changing my power option, and I thought, well, I should update that thread to let everyone know that everything is working fine, and literally 2 seconds later, the encode FAILED!!! This time I took note of the reason, which I’m pasting below, and which makes no sense to me. Maybe one of you can figure it out. btw, the video merely had Lumetri tweaks, and one instance of FilmConvert Pro just to make it a bit heavier, nothing that my old PC couldn’t handle without failing.
08/06/2017 11:15:06 AM : Encoding Failed
————————————————————
Export Error
Error compiling movie.GPU Render Error
Unable to process frame.
Writing with exporter: H.264
Writing to file: \\?\C:\Users\john_\Desktop\P1000066.mp4
Writing file type: H264
Around timecode: 00:01:09:23 – 00:01:10:08
Rendering effect: AE.ADBE Lumetri
Rendering at offset: 69.958 seconds
Component: EffectFilter of type GPUVideoFilter
Selector: 9
Error code: -1609629695————————————————————
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Again, it’s not so much Premiere as it is Media Encoder, which hasn’t given me any problems today with the switch to a more reasonable power option.
Just for the record I checked crash reports and, even though Premiere Pro hasn’t crashed, there’s a report a mile long in the log directory. I won’t post the whole thing but this is the first 15 lines or so. Let me know if you see anything unusual:
Process: PProHeadless.exe [12848]
Path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2017\PProHeadless.exe
Product Version: 11.0.0.154
File Version: 11.0.0.154
Code Type: x64
Parent Process: dynamiclinkmanager.exe [11572]Date/Time: 2017-08-05 09:26:54 Eastern Daylight Time
OS Version: 10.0.15063.296
Report ID: 771f7228-0aa6-4b6e-b64a-2a85ca193f6aTime Awake Since Boot: 6917 seconds
Crashed thread: 29 [5024] THREAD_PRIORITY_NORMAL
Exception Code: 0xe06d7363 (C++ EH Exception)
Exception Parameters: 0x19930520 0x58b21cb0 0x2f945d30 0x2f100000
Exception Message:Application Specific Information:
C:\WINDOWS\System32\KERNELBASE.dllDell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0
-
Brent, with all due respect I haven’t heard from you before I got this new PC, which, btw, is a Dell XPS 8920, which Jeff Pulera recommended to me over a year ago when I first started looking for a more workstation worthy box. My previous PC was an HP which, contrary to public opinion, NEVER gave me problems, through 4 different boxes. Also, I have never seen anyone post on this board complaining that their computer was working flawlessly, so I guess I’m in good company. Now….
Chris, it’s not Premiere Pro that fails. The only thing it screws up with is, every once in a while, I get that error message saying that the project I’m trying to open used CUDA, which “is not available on this system”. I created the project “on this system”, of course CUDA is present, but it only opens in software mode. Closing Premiere Pro and reopening it does the trick.
The major problem is Media Encoder. Sometimes it works fine, I can encode while going back to Premiere Pro, or checking my email, or opening Chrome. But other times as soon as I leave the AME window, it fails. Rebooting the computer will fix that problem, but I’m guessing maybe you might be on to something with the overheating since I have my power options set to never sleep and never turn off the monitors. I will try a more sensible setting and see if that does the trick.
As for your other questions, I didn’t like the new essential graphics and essential sound of the latest PPro so I rolled back. I did have the latest version and had the same problem with AME, so that’s not a solution.
No RAM leaks, latest drivers ( I did roll back on the Nvidia driver, then updated to the latest one that came out a couple days ago.
Anyway, I have a feeling changing my power options might do the trick so I’ll give it a shot. If AME fails again I’ll check the error log and report back. Oh, and btw, Photoshop, Audition, After Effects, all work flawlessly.
EDIT: Well, so far, so good.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
I don’t remember being notified that Windows 10 updated recently but after reading your post I tried applying Denoiser III to a video clip. Well, Premiere Pro crashed in the weirdest way. I could still turn Denoiser on and off, delete it, add another plugin, but none of them actually affected the video, and the video stayed frozen, even after I deleted Denoiser. I actually had to reboot to get PPro to act normal again.
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Hey, Aaron. I don’t do this seriously enough to need that. I just need a player that plays back exactly what I see and hear in Premiere Pro. I’ve had problems like this previously, on other PC’s, mind you, where Media Player’s sound crapped out, and there was a time when VLC’s video playback was off color compared to the Program monitor in PPro.
I was using the “Movies and Video” player that comes with Windows 10 (just got this PC) and it was working great until last night. So I’m back to using VLC. No problems so far. But thanks for responding. Cheers!
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0 -
Just as a follow up I downloaded VLC and the sound is perfect. Friggin’ Windows 10….
Dell XPS 8920
GeForce GTX 1050ti
32 Gigs of RAM
3 7200 RPM SATA Drives
Windows 10 64-bit
Premiere Pro CC 2017 v.11.0