I am puzzled.
My system Dell Precision T5400, Intel Xeon CPU X5450@3.ghz (2 processors), 12 gb ram, 64bit.
I have a Nvidia Quadro FX 3800. Premiere is using the mercury driver.
I am rendering from 3dsMax at 1280x720. When I import the sequence, my system cannot even play it back in the preview window. It plays about every 10th frame, if I am lucky.
Is there a setting I am missing?
No. Apparently I need to read about recommended workflow for animated sequences.
I went to "file - Import" selected the first file in the sequence, selected the "numbered stills" button.
Premiere imported the sequence, then I double click it, It loads in the preview window, but stutters in the playback.
Is this not the correct workflow?
Thanks for any help you can provide.
OK lots more info needed. What version of PrP are you running? The format size of your tiff sequence. After importing try dropping the clip on the Make Sequence button to create a timeline. Are you using an external monitoring hardware (AJA, Kona, etc)? What kind of raid array are you using and what is its read / write speeds?
This might be redudndant of what you know but just in case a Google search revealed this from Addobe...
I am new to the Premiere world. I bought Elements, but when I had the trouble, I downloaded Premiere Pro 5.5 as a test. I am rendering individual frames .tiff format at 1280x720. I am creating a Sequence using a preset of HDV 720p30, as this matches my files.
This is taking place on my local machine so there is no additional hardware not mentioned in the first post. There is no raid array. The drive is a 7200 rpm WD 6gb/s.
My files meet all of the settings recommended in the link.
Sorry, but I cannot find a "make sequence" button.
Thanks again for all your help.
FongOverland "I am new to the Premiere world".
Then I strongly urge you to read this book. It really helped me out when I switched from another NLE. There is a lot to know and this will help you avoid lots of gotchas.
BTW a Google searchevealed this...
Watch this entire video for clarification on making a sequence from a clip. Good luck!
Working with uncompressed image sequences for animation is different
than working with video footage. There is not a lot of
information/solutions mentioned on the web on this topic. Unless I am
mistaking, and people could correct me, CUDA engine won't help to play
them in real time.
Another thing: Image sequences do not have presets regarding frame rate.
Before importing, set frame rate for Undeterminate Media Timebase in
Edit > Preferences > Media.
For full HD projects (I don't know about 1280 x 720), the hard drive
cannot handle the load as Jim Simon mentioned. Best is to have your
project created on an array of RAID 0 hard drives (I have 4 x 7,200 rpm
You could also reduce the Playback resolution.
Le 2012-02-08 13:48, lasvideo a écrit :
Re: Mercury, CUDA, and what it all means
created by lasvideo <http://forums.adobe.com/people/lasvideo> in
/Premiere Pro CS5 & CS5.5/ - View the full discussion
I branched this thread from a thread that it isn't really related to.
As others have suggested, playing back an image sequence doesn't exercise the CUDA capabilities of the GPU. The bottlenecks in such playback are in decoding (on the CPU) and in getting the data off the hard disk and across the bus into the CPU.
See this page for resources about making Adobe Premiere Pro (and After Effects) work faster: http://adobe.ly/eV2zE7
To be clear then, playing back my sequence in the editor doesn’t use the CUDA? This implies that it only uses CUDA in rendering?
Another interesting quirk…If I set the sequence to cycle playback, each time it plays through the sequence it become a bit smoother. Eventually it plays without a hitch. It takes about 10 times through the sequence, but it does smooth out.
> To be clear then, playing back my sequence in the editor doesn’t use the CUDA? This implies that it only uses CUDA in rendering?
No, you misunderstand. CUDA is not used for decoding. Decoding is done on the CPU. Decoding is the hard part of working with TIFF files (as is getting the rather large data off of the disk and across the bus into the CPU).