![]() ![]() My system is fast enough that it should have zero issues, unless it actually is an nVidia graphics driver thing as so many respondents seem to imply. System: Intel i7-6900 (8 cores w/hyperthreading = 16, 3.2GHz), 64G RAM, nVidia GTX1080 (8G), Win 10, all with the very latest drivers. ONLY the VTs for the new ones go black (as well as the Program Monitor), until I quite PR and restart it. All other VTs for the MGTs in My Library, including previous ones I have exported as well as the many built-in Adobe ones, still show just fine. After two or three such exports, not only does the Program Monitor go black, but the new MGTs refuse to show their Video Thumbnails in the EG panel. In my case, the black Program Monitor occurs when I export an Essential Graphics clip as a new Motion Graphics Template in My Library. But Premiere itself could not.Īfter that I had wondered if After Effects was slightly more stable than Premiere when memory intensive files are involved?Īdding my two cents here. ![]() ![]() I repeated the export a few times just to be sure it wasn't by chance and sure enough, After Effects could perform the export of the Premiere sequence. To my surprise, the Premiere sequence exported first time when the process was undertaken by After Effects. And also, my Mac is a bit older.Īs a last resort I decided to import the Premiere sequence I was having the problem with as a Dynamic Link into After Effects on my 2014 MacBook Pro 15 inch and tried exporting through the After Effects Render Queue, using very similar settings as I'd been using when in Premiere to do the export. It's understandable that Premiere might have a problem with what was a very inefficiently constructed file. Once again, I thought, OK - fair enough, this file has been constructed without converting each JPG to low res, the file must be the problem. But same result at the same point in the process each time. I tried loads of different ways of exporting, through the standard Premiere export options, and through Media Encoder, lots of different settings / codecs / various GPU settings / switching GPU off etc etc etc. I managed to narrow the problem down to somewhere around 3/4 of the way through what as I remember was an approximately 5 minute film but I couldn't get beyond this in terms of figuring out exactly where the problem lay within the student's file. I thought at the time that the problem was perhaps a corrupt JPG or Premiere may have run out of memory - as I said, there were many many high res JPGs. Premiere kept crashing at the same specific point in the export process. I took the file home with me and experimented and experimented on my own 2014 15 inch MacBook Pro with 16GB RAM and 2GB Nvidia GPU - now not the newest of Macs. Now in fairness to Premiere, the student had made a long video comprised of many many many high res JPGs - so I felt it was pretty understandable that Premiere would struggle - it was an older computer after all, and the video had been constructed from lots of images, with each one being of a very considerable file size. I replied to this discussion some years ago - don't know if this is relevant but I hope this info may be useful to you.Ī few months ago I was helping one of my students with a problem exporting from Premiere on a 2013 15 inch MacBook Pro with 16GB RAM.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |