A Furry Peanut Posted June 7, 2017 Share Posted June 7, 2017 Does anyone know why this is happening? I have tried: - deleting and undeleting the clips from my timeline - copying and pasting onto new sequence - copying and pasting onto new project - renaming my premiere pro file - saving premiere pro to a different location (desktop) with different name then exporting to a different location, - change the renderer in AME from GPU Acceleration to Software Only - exporting directly from premiere pro instead of AME All the above methods did not work, the only solution I have found was exporting in a different format then converting it to mp4 however I was wondering if there was another way around this. I also noticed that whenever I try to export the "Around timecode" and "Rendering at offset" in the error message would be different but the "Error code" would always be -1609629695 Link to comment Share on other sites More sharing options...
OliKMIA Posted June 7, 2017 Share Posted June 7, 2017 The errors happens "around timecode 1:22:04 You could try to nest this sequence or render the clip at this time and insert the rendered clip back it in your timeline Also, during export, pick QUEUE, then you can choose to render using CPU or GPU. Sometime using CPU fixes the problem (but it will take more time to render) Link to comment Share on other sites More sharing options...
jcs Posted June 7, 2017 Share Posted June 7, 2017 @A Furry Peanut try disabling the Lumetri effect, which is where the error is reportedly happening. If that fixes the issue, recreate the Lumetri settings, one at a time until you find what is causing the error. Link to comment Share on other sites More sharing options...
Justin Bacle Posted June 7, 2017 Share Posted June 7, 2017 Hi had this one recently, this is a "cuda - GPU out of memory error". You should close your other programs (even your web browser and such as they use Video Ram) and restart premiere and start rendering I recommend using AME "alone" to render it as there will be more ram available as premiere will be openned "headless" if oppened by AME for rendering. If you're stuck, render with GPU only (but restart Premiere before rendering as switching from GPU to CPU might not empty ram) I have quite some problems with recent versions of Pr/Ae as my GPU is quite old now. The latest Cuda core takes waaay more gpu ram and GPUs under 2Gig of ram struggle :s Let us know if you have any success Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/7/2017 at 2:56 PM, OliKMIA said: The errors happens "around timecode 1:22:04 You could try to nest this sequence or render the clip at this time and insert the rendered clip back it in your timeline Also, during export, pick QUEUE, then you can choose to render using CPU or GPU. Sometime using CPU fixes the problem (but it will take more time to render) Expand On 6/7/2017 at 8:34 PM, Justin Bacle said: Hi had this one recently, this is a "cuda - GPU out of memory error". You should close your other programs (even your web browser and such as they use Video Ram) and restart premiere and start rendering I recommend using AME "alone" to render it as there will be more ram available as premiere will be openned "headless" if oppened by AME for rendering. If you're stuck, render with GPU only (but restart Premiere before rendering as switching from GPU to CPU might not empty ram) I have quite some problems with recent versions of Pr/Ae as my GPU is quite old now. The latest Cuda core takes waaay more gpu ram and GPUs under 2Gig of ram struggle :s Let us know if you have any success Expand I have already tried these two suggestions and unfortunately they have not worked for me On 6/7/2017 at 7:42 PM, jcs said: @A Furry Peanut try disabling the Lumetri effect, which is where the error is reportedly happening. If that fixes the issue, recreate the Lumetri settings, one at a time until you find what is causing the error. Expand I have too many clips with lumetri so instead I used "Global fx mute" and even with all the effects turned off, I still got the same error. Although in hindsight I do believe that rendering in a different format then converting to mp4 is more efficient then going through every clip with lumetri and disabling/enabling to see where the problem lies haha. Link to comment Share on other sites More sharing options...
Orangenz Posted June 8, 2017 Share Posted June 8, 2017 What is your video card. What plugins are you using. This is pc? How many and what type of screens? Resolution of project? Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 3:18 AM, Orangenz said: What is your video card. What plugins are you using. This is pc? Expand Nvidia GeForce GTX 970, Intel Core i7-4790k, 32gb ddr3 ram, 64-bit Windows 10. I only have Red Giant's Universe and Trapcode Suite installed. Link to comment Share on other sites More sharing options...
Orangenz Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 3:25 AM, A Furry Peanut said: Nvidia GeForce GTX 970, Intel Core i7-4790k, 32gb ddr3 ram, 64-bit Windows 10. I only have Red Giant's Universe and Trapcode Suite installed. Expand Video card memory? What plugins are you using on this specific project? Screens and resolution of project? Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 3:48 AM, Orangenz said: Video card memory? What plugins are you using on this specific project? Screens and resolution of project? Expand 3.5gb video card memory, for this specific project I used Red Giant's DeNoiser III and Universe. Project is 1080p at 29.97 fps filmed with canon 70D and t7i. Link to comment Share on other sites More sharing options...
Orangenz Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 3:53 AM, A Furry Peanut said: 3.5gb video card memory, for this specific project I used Red Giant's DeNoiser III and Universe. Project is 1080p at 29.97 fps filmed with canon 70D and t7i. Expand Trying to find out how many screens.. Can you go into the effects panel and make sure that nenoiser is at the very top of the effects list, ie. above lumetri Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 3:58 AM, Orangenz said: Trying to find out how many screens.. Can you go into the effects panel and make sure that nenoiser is at the very top of the effects list, ie. above lumetri Expand 2 screens. and no my denoiser was at the bottom, but I have just moved them to the top Link to comment Share on other sites More sharing options...
Orangenz Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 4:01 AM, A Furry Peanut said: 2 screens. and no my denoiser is at the bottom, I will start moving them to the top Expand Also note that Redgiant hardware requirements say that running two screens on a HD project requires 4GB of video memory. So try unplugging a screen. Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 4:10 AM, Orangenz said: Also note that Redgiant hardware requirements say that running two screens on a HD project requires 4GB of video memory. Expand Oh I actually never knew that, I'll keep that in mind the next time I edit Link to comment Share on other sites More sharing options...
Orangenz Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 4:23 AM, A Furry Peanut said: Oh I actually never knew that, I'll keep that in mind the next time I edit Expand More just the export stage. Link to comment Share on other sites More sharing options...
funkyou86 Posted June 8, 2017 Share Posted June 8, 2017 On 6/7/2017 at 8:09 AM, A Furry Peanut said: Does anyone know why this is happening? I have tried: - deleting and undeleting the clips from my timeline - copying and pasting onto new sequence - copying and pasting onto new project - renaming my premiere pro file - saving premiere pro to a different location (desktop) with different name then exporting to a different location, - change the renderer in AME from GPU Acceleration to Software Only - exporting directly from premiere pro instead of AME All the above methods did not work, the only solution I have found was exporting in a different format then converting it to mp4 however I was wondering if there was another way around this. I also noticed that whenever I try to export the "Around timecode" and "Rendering at offset" in the error message would be different but the "Error code" would always be -1609629695 Expand I had this issue as well, copied all my luts to AME's Lumetri/Creative folder, and it solved the problem. Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 5:32 AM, funkyou86 said: I had this issue as well, copied all my luts to AME's Lumetri/Creative folder, and it solved the problem. Expand I didn't use any luts for this Link to comment Share on other sites More sharing options...
funkyou86 Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 5:33 AM, A Furry Peanut said: I didn't use any luts for this Expand Still, it has something to do with the Lumetri panel. Are you using heavy grade? Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 8, 2017 Author Share Posted June 8, 2017 On 6/8/2017 at 5:38 AM, funkyou86 said: Still, it has something to do with the Lumetri panel. Are you using heavy grade? Expand Not to my knowledge, and I tried exporting with "Global fx mute" which is supposed to mute all effects including lumetri and I still got the problem. Link to comment Share on other sites More sharing options...
funkyou86 Posted June 8, 2017 Share Posted June 8, 2017 On 6/8/2017 at 5:46 AM, A Furry Peanut said: Not to my knowledge, and I tried exporting with "Global fx mute" which is supposed to mute all effects including lumetri and I still got the problem. Expand If you export the sequence from premiere, does it behave the same? The only thing which comes in my mind is to clear all cache, restart computer and try again. Link to comment Share on other sites More sharing options...
A Furry Peanut Posted June 9, 2017 Author Share Posted June 9, 2017 On 6/8/2017 at 5:54 AM, funkyou86 said: If you export the sequence from premiere, does it behave the same? The only thing which comes in my mind is to clear all cache, restart computer and try again. Expand Yes, and I just tried clearing all cache and restarting but unfortunately that did not work either. Oh well, this has been the only project where I have encountered this problem and hopefully it stays that way. Thanks to everyone for trying to help Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now