Stephanie Liskey
Forum Replies Created
-
Stephanie Liskey
July 29, 2013 at 11:32 am in reply to: 4% used of 24 GB RAM on HP workstation – need to speed processThanks for the response…I posted an update:
Update:
on my last render, I got AE to use %64 of my avail RAM! Much faster!!I am thinking this is attibutable to using the Neat Video Noise reduction plugin (I believe it pre-renders the noise correction for AE, freeing up a lot of energy).
I also took it off multiprocessor. Any advice would still be welcome…I want to understand better how to control my RAM allocation.
I have since got it up to %75…functioning ok, but still crashes if I go over 5 min or so of footage. I wish it could handle more. I know a weakness of my sys is slow drives…
Thanks,
Stephanie
Stephanie L
-
Stephanie Liskey
July 24, 2013 at 7:07 pm in reply to: 4% used of 24 GB RAM on HP workstation – need to speed processUpdate:
on my last render, I got AE to use %64 of my avail RAM! Much faster!!I am thinking this is attibutable to using the Neat Video Noise reduction plugin (I believe it pre-renders the noise correction for AE, freeing up a lot of energy).
I also took it off multiprocessor. Any advice would still be welcome…I want to understand better how to control my RAM allocation.
Stephanie L
-
Stephanie Liskey
July 24, 2013 at 5:27 pm in reply to: 4% used of 24 GB RAM on HP workstation – need to speed processI would love to know how to set my memory for this. Update: I am now trying AE CC version, in case the latest helps, and also Neat Video Pro Plugin. Also wanted to add I have NVIDIA quadro 4000 Card. I have seen out here and other places on internet that exporting Noise correction is always intensive – but I just would like it to be less intensive than 4 hours for 3 minutes of HD footage.
I am not sure what to select for memory/Cache.
What I was about to try was RAM Reserved for other apps – 7 GB
Ram for AE: 17 GB (I read that some should be reserved, and feel I may as well get other work done while this happens, as I have noticed it takes the same time if I work or don’t)Should I enable Multiprocessing? I was trying it before, but I saw on here that for noise correction output, that could just hurt. I don’t get it, but I am trying to optimize this process somehow.
Disk Cache – I have it set to 255 GB on the drive the program is on, rather than the drive the AE file is on, and outputting to that same drive (is it better to output to the drive the program is on, or the one the AE file is on?)
Thanks for input,
Stephanie
Stephanie L
-
Stephanie Liskey
March 28, 2012 at 8:18 pm in reply to: Trying to make a 960 x 720 project in Premiere from HD footage shot on an SLR and and HD CAMThanks for the idea!
We ended up patching together a mask in Avid. I am doing all the pieces in AFX and exporting as AVIs for my partner to string together in Avid and get the soundtrack going there.
I know these people have no real reason for this size requirement, it’s just hanging in there making problems for us.
When we are less under the gun, I will experiment more with this kind of tinkering for emergencies based on your suggestion.
~Stephanie
Stephanie L
-
Stephanie Liskey
March 1, 2011 at 9:17 pm in reply to: I want it all, a cheap fast external 4-Bay RAID that can swap machines..Hi –
I have a very “newbie” question.
I looked at the EvoVR Rackmount you mentioned. Is this something we could buy and it would have all the components ready to work as a steady drive to edit video on an Avid Media composer? We have a lot of HD footage now, and noticed our little 1 TB drive was packed, so it might be time to get something actually professional that would give us some backup and speed working with video.This may be overkill for us, as we are never needing remote access, etc. Do you have a simpler, cheaper solution idea for a basic RAID setup? Our goal is speed, efficiency, and redundancy (backup).
Also, if you or anyone can clarify – would it be bad to store other data besides video on the same drive? I was wondering if there is a reason Video needs it’s own kind of array.
Thanks,
Stephanie