Activity › Forums › Adobe Premiere Pro › 5 Hours of RedONE footage to edit?
-
5 Hours of RedONE footage to edit?
Posted by Ralph Mccarron on July 23, 2012 at 12:43 amI have an Intel 7 Quad Core 960 @ 3.20 GHz machine GeForce Nvidia GT 440 with 1 GB of RAM and 19 gigs on the MOBO dedicated for Premiere.
Should I throw all of the audio and video on the timeline…..then render and then edit? I am using te GPU CUDA acceleration.
Or should I choose in and out points for each clip and then render and then start my editing.
The problem I am having is that when I edit with the GPU on Premiere starts using up all my RAM and I have to re-start the computer after about an hour of editing. My render is yellow on the timeline….
Also how can I tell how big my rendered files will be with 5 hours of footage.
Ralph Mccarron replied 14 years ago 2 Members · 7 Replies -
7 Replies
-
Angelo Lorenzo
July 23, 2012 at 5:08 amWhat version of Premiere? What is your GPU? Is the Mercury Engine set to hardware(GPU) or software only (Actually, I don’t think your GPU is doing much of anything, unless you’re using the CUDA text file hack)?
As far as RED footage, under your program monitor you should have some options including playback and pause resolution. Do you get any better performance/less long term issues if you set it to, say, 1/8th resolution?
Angelo Lorenzo
Fallen Empire Digital Production Services – Los Angeles
RED transcoding, on-set DIT, and RED Epic rental services
Fallen Empire – The Blog
A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks -
Angelo Lorenzo
July 23, 2012 at 5:59 amHm, it’s an off night. Either you edited your post with more info or I just totally missed your GPU details. I need me some more coffee 😉
Since the GT 440 isn’t an approved CUDA card for Premiere, try switching the mercury engine to software only along with the other tip in my previous post. Also, try with hardware on (I assume you have the hack) but make sure your drivers are up to date; if it’s a memory allocation issue with the GPU, I would assume it’s driver related.
Angelo Lorenzo
Fallen Empire Digital Production Services – Los Angeles
RED transcoding, on-set DIT, and RED Epic rental services
Fallen Empire – The Blog
A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks -
Ralph Mccarron
July 23, 2012 at 8:01 pmI have GPU set and my playback is 1/4. 1/8 is ghosted or greyed out so I can’t select it. If I try to edit the native footage with the rendder bar at yellow all of my RAM gets eaten up about an hour into my editing and I have to reboot my machine….
-
Ralph Mccarron
July 23, 2012 at 8:03 pmI have 6.0.1 and the latest Nvidia drivers if I switch to sftware only which I have the same thing happens. I will try to buy another card and see if this solves it….
-
Angelo Lorenzo
July 23, 2012 at 9:15 pmAs an aside, is your RED One footage 2k? 4k footage usually allows you to select 1/8th resolution. I digress…
If you’re having issues in software mode, It’s doubtful your GPU is having any bearing on a bad memory leak.
My initial guess was, that because it was an unsupported card running in hardware mode, that Premiere interacting with the drivers in hardware mode could cause some funkiness.
Premiere is RAM hungry, well most Adobe programs are, and I have no memory issues working with RED footage which I do on a nearly daily basis with my Windows 7 system.
The next thing I would suggest would be to grab a benchmarking program like Prime95 https://files.extremeoverclocking.com/file.php?f=205 or Memtest https://www.memtest.org/ (I assume you’re on Windows from your system specs). You can stress test your RAM and processor to make sure that it’s behaving normally just in general before pinning it to Premiere.
Angelo Lorenzo
Fallen Empire Digital Production Services – Los Angeles
RED transcoding, on-set DIT, and RED Epic rental services
Fallen Empire – The Blog
A blog dedicated to filmmaking, the RED workflow, and DIT tips and tricks -
Ralph Mccarron
July 24, 2012 at 1:13 amAdobe remotley tapped in my machine and cleaned up a lot of temp files etc and turned of my Black Magic Intensity Pro Card in my playback settings and set it back to Adobe DV. I’m going to run some tests and will repost….
-
Ralph Mccarron
August 2, 2012 at 3:20 amThe Ram problem was caused by Black Magic’s Intensity Pro Card. Their drivers sucked. I called them previously and they acted like nothing was wrong with their card. I called back again on 07-30-12 and they said on Friday 07-27-12 they had updated their drivers. I re-installed edited in Premiere for 8 hours and no RAM issues. It was the Black Magic drivers making my RAM crash and would only allow me 1 hour inside Premiere before it locked up? Now I’m having an audio sync output issue with the Intensity Pro….more problems to solve….I hope this helps anybody who was using the BlackMagic Intensity Pro with Premiere Pro CS6 6.01….
Reply to this Discussion! Login or Sign Up