Duke Sweden
Forum Replies Created
-
Hey Chris. No, not just Premiere Pro. Any sounds. From Youtube, from VLC. I did research and it seems to be a common thing. Like I said I tried all the “solutions”. I’ll just have to wait it out for a “fix”.
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 -
Duke Sweden
August 10, 2017 at 2:18 am in reply to: NVIDIA Card with Yosemite and Premiere causing major graphics failureGee, Brent, your problems sound AWFULLY similar to the ones I had. Maybe your computers are real “crap”.
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 -
Duke Sweden
August 10, 2017 at 2:14 am in reply to: Open a newer premiere Pro project on a slightly older version of Premiere Pro.You can get the last update to cc 2015 here:
https://helpx.adobe.com/creative-cloud/kb/creative-cloud-previous-version-apps-download.html?red=a&tduid=49e19a998d310d6634d2f60cf0c58bbd&url=https://helpx.adobe.com/creative-cloud/kb/creative-cloud-previous-version-apps-download.htmlScroll down a bit and you’ll see it.
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 -
Duke Sweden
August 8, 2017 at 11:06 pm in reply to: NVIDIA Card with Yosemite and Premiere causing major graphics failureWell, well, well….
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 -
Hey Todd, no, that was the first PC I got, an 8910. I brought that back when the 8920 went on sale that weekend. I also brought back the GTX 1050 and got the GTX 1050ti. So the toolkit had nothing to do with the problems with this box. It is odd, though, that this box had the same exact problems as the first PC.
The 8920 came with 16 gig of RAM. I added another 16 gig of Crucial which I’ve read is very good. According to B&H it is more than compatible.
Anyway it just appears to be bugs I had to work out. Changing my power options from never off to balanced seems to have done the trick as I haven’t had any problems since.
The only odd behavior today is, I shot a 5 minute clip, did some lumetri tweaks, added FilmConvert and Cosmo plugins. It rendered the first time in 1 hour, 20 minutes, and without changing anything except to ADD effects to the audio, the next time it rendered in 8 minutes. Go figure.
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, Walter. I know it’s not necessary to clear my media cache every day, I’m just being anal until I get this thing running smoothly, which it is now.
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 -
Hey Jeff. I always encode to my H drive, that’s what it’s for. I save final encodes to my F drive. I was testing Media Encoder so I just sent that file to my Desktop so I could find it easy enough to delete when I was done, but, yeah, normally I don’t render to my C drive.
Anyway it’s running really smoothly lately so I thank you again for pointing me to the Dell XPS PC’s. Other than these weird problems which are slowly sorting themselves out, this thing rips.
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 -
Well, all I know is, my new PC (specs below) plays everything smoothly, even with effects and lumetri added. My only problems, which appear to have been fixed, was with Media Encoder failing every once is a while.
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 -
Duke Sweden
August 7, 2017 at 11:30 am in reply to: How to keep project nice and clean. (probably easy)Create a bin, open it, then import your stuff. I myself had been doing a hackneyed version of that but my latest project, I created sound, images, green screen etc. folders in the folder holding my assets, and the same in Project window. Then when I imported my sound effects I opened that folder in Media Browser, opened the sound effects bin in the Project window, and imported, etc.
So in your case just create a bin called timelines, open it, and then import your timelines.
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 -
But, as I said, when I encoded it again it ran smooth, no problems. Is that normal in cases like this? If a Lumetri setting is causing a fail, shouldn’t it fail every time? Again, I’m just looking for answers. If anybody thinks I’m “whining” just ignore me.
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