Premiere CS3 and quad core rendering? at DVinfo.net
DV Info Net

Go Back   DV Info Net > Cross-Platform Post Production Solutions > Adobe Creative Suite
Register FAQ Today's Posts Buyer's Guides

Adobe Creative Suite
All about the world of Adobe Premiere and its associated plug-ins.

Reply
 
Thread Tools Search this Thread
Old June 12th, 2008, 08:46 PM   #1
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
Premiere CS3 and quad core rendering?

I have had a quad core and CS3 for almost a year and the increase in rendering speed has been great when using the Adobe media encoder. All 4 cores are always cranking and cutting render times compared to my work dual core almost in half.

Tonight, I loaded up an HD project that is in Canon 24f and I am converting it to 16x9 SD DVD mpg at 8mbps. It is only 10 minutes long and is taking 25+ minutes to render, and when I look at the processors it is only using 25%! What is up all of a sudden?

2 things that might have changed since I last noticed all 4 cores getting utilized.

Adobe pushed out a Premiere update adding Sony Xdcam EX support (3.0.2??)

Microsoft pushed out SP3.

Is possible one of these has caused issues with threading across 4 cores? Heck.....at 25% I am really only using 1 core. This stinks if I have somehow lost the benefits of quad processing.

Thanks.
Marty Hudzik is offline   Reply With Quote
Old June 12th, 2008, 09:10 PM   #2
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
I may have stumbled onto something. When I create a new project using the Adobe HDV-1080-24p preset and import the same clips into my timeline, I get amazing render speeds! The thing cooks and rendered 1 minute of the timeline to an mpg in about 20 seconds or so. At that rate the entire 10 minutes would render in 3.5 minutes vs. 25 minutes in the original project. I had downloaded the Adobe presets for Canon HDV 24f that were designed for PPRO2, but they worked great before. Now it seems they may be problematic in CS# with the latest updates form Adobe which included a new preset to take the place of the PPRO2 canon presets.

I will post if I see anything else interesting here.
Marty Hudzik is offline   Reply With Quote
Old June 12th, 2008, 09:12 PM   #3
Major Player
 
Join Date: Jan 2008
Location: Rancho Santa Margarita, California
Posts: 201
Do you have all the recent updates from Adobe?
__________________
Mitchell J. Skurnik
http://www.mjcsstudios.com/ - EX1, 4x hoodman 16GB, Libec Tripod, Sony LAV
Mitchell Skurnik is offline   Reply With Quote
Old June 12th, 2008, 09:15 PM   #4
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
I feel like I am talking to myself but here is another bit of useful information. The issue is caused by "de-interlacing" being checked in the output box of Adobe Media Encoder. This is tunred on by default and it somehow causes your render to be single core threaded.

Weird? I had noticed this glitch in CS3 where most of the mpg presets have deinterlace checked by default which essentially halves your resolution when outputting to Blu-ray....but I never noticed this issue with only using a single core.

Good LUck....hopefully I Will spare some of you running into these issues.

Out!
Marty Hudzik is offline   Reply With Quote
Old June 15th, 2008, 07:06 AM   #5
Major Player
 
Join Date: Feb 2007
Location: Orlando, FL
Posts: 404
Wow, so the de-interlacing is single-core aware? That seems like a bit of a problem on their end!

Thanks for the info, I have a Q6600 and I've noticed the media encoder is pretty slow here when I've used it recently, and CPU usage hovers between 24 and 26%. I'll try unchecking that box, since all my footage is progressive, with rare exceptions.

Thanks!
Eric
Eric Shepherd is offline   Reply With Quote
Old June 15th, 2008, 09:10 PM   #6
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
eric,

Any luck verifying this? Just because I found it on mine doesn't mean it happens to every prmiere cs3 install.

Thanks
Marty Hudzik is offline   Reply With Quote
Old June 16th, 2008, 12:24 AM   #7
Major Player
 
Join Date: Feb 2006
Location: Surrey, UK
Posts: 680
Marty, thanks for your comments and suggestions...i'm afraid i have nothing to contribute to this, but am about to make a jump to quad core (from dual) so all of this input is helpful.

also, how much would you say having one aids the actual editing of HD...i.e. HD clips start to stutter when I run 2 or 3 effects...how about with a quad core?
Richard Wakefield is offline   Reply With Quote
Old June 16th, 2008, 08:38 AM   #8
Major Player
 
Join Date: Jan 2008
Location: Rancho Santa Margarita, California
Posts: 201
I really cant comment. I have been running 2 Dual core opterons now for 3 years...
__________________
Mitchell J. Skurnik
http://www.mjcsstudios.com/ - EX1, 4x hoodman 16GB, Libec Tripod, Sony LAV
Mitchell Skurnik is offline   Reply With Quote
Old June 24th, 2008, 01:04 PM   #9
Regular Crew
 
Join Date: Jun 2008
Location: San Diego, CA / Apex, NC
Posts: 81
I don't have this problem when deinterlacing on my quad core. I do, however, only have one core used when I'm doing noise reduction through adobe media encoder (I wish they'd just implement it as a plug-in for finer control).
__________________
Douglas Thigpen
http://www.dthigpen.com/ - http://www.nicetryproductions.com/
Douglas Thigpen is offline   Reply With Quote
Old June 25th, 2008, 06:20 AM   #10
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
Make sure we are talking about the same deinterlacing control here. I am not referring to the one that you acces from the timeline and apply to individual clips. I am referring to an option in the Adobe Media Encoder itself that is on the "output" screen. For some reason when I choose a 24P HDV template to work from, this check box is on by default and is on a screen that is behind the source screen. Why would I want to deinterlace 24P to output anyway? Regardless, if I miss this (which I have done many times accidentally) my renders to mpg2 HD are 3 to 5 times longer to output and the resulting file is lower res as a result. Also only one core seems to carry the load explaining the excessive render times.

If I uncheck this option then I see all 4 cores jump in, virtually 100% usage and the render is done in record time.

So please make sure when testing this that you are using the deinterlace option in Adobe Media Encoder....not deinterlace on the timeline.

Peace.
Marty Hudzik is offline   Reply With Quote
Old June 25th, 2008, 09:23 AM   #11
Major Player
 
Join Date: Jan 2008
Location: Rancho Santa Margarita, California
Posts: 201
You could always export an uncompressed movie (File>Export>Movie) then use windows media encoder to compress it. That program will use up all of your cores :).
__________________
Mitchell J. Skurnik
http://www.mjcsstudios.com/ - EX1, 4x hoodman 16GB, Libec Tripod, Sony LAV
Mitchell Skurnik is offline   Reply With Quote
Old June 25th, 2008, 10:06 AM   #12
Trustee
 
Join Date: Jul 2004
Location: Canton, Ohio
Posts: 1,771
If I don't choose deinterlace then all of my cores are in use anyway! Remember in my case, de-interlace was checked by accident (or as a default that I didn't want anyway).

Also, exporting uncompressed 1080P HD footage is a pain because of the excessive storage for me.

Peace.


Quote:
Originally Posted by Mitchell Skurnik View Post
You could always export an uncompressed movie (File>Export>Movie) then use windows media encoder to compress it. That program will use up all of your cores :).
Marty Hudzik is offline   Reply
Reply

DV Info Net refers all where-to-buy and where-to-rent questions exclusively to these trusted full line dealers and rental houses...

B&H Photo Video
(866) 521-7381
New York, NY USA

Scan Computers Int. Ltd.
+44 0871-472-4747
Bolton, Lancashire UK


DV Info Net also encourages you to support local businesses and buy from an authorized dealer in your neighborhood.
  You are here: DV Info Net > Cross-Platform Post Production Solutions > Adobe Creative Suite


 



All times are GMT -6. The time now is 07:12 AM.


DV Info Net -- Real Names, Real People, Real Info!
1998-2024 The Digital Video Information Network