-
1. Re: AVCHD and Premiere...slow going
Harm Millaard Apr 25, 2012 11:55 PM (in response to RByds4te)Please run Process Explorer (See Sysinternal Utilities) and post a screenshot of all processes running. Also confirm that your video drivers are 296.10 or later.
-
2. Re: AVCHD and Premiere...slow going
JEShort01 Apr 26, 2012 5:01 AM (in response to RByds4te)There is a lot on these forums where certain things have clogged performance that are not related to hardware: codec packages installed, MOV "wrappers" on some media, errant drivers, etc. I would suggest running the PPBM5 benchmark (www.ppbm5.com) to get a reality check regarding how your PC is performing against a known project. That way, you will know with certainty whether you need to keep chasing hardware or something else. Please report the individual "scores" back to this forum as well.
Another benchmark to consider, which is really easy to do, is running HD Tune Pro (30 day eval is free) with block size = 2MB to insure your RAID is up to snuff. You should be getting a nice smooth waterfall decay in performance from the first part of you array (fastest) to the last part (slowest) with no massive spikes down. With your 2x1TB you should see #'s around: max = 230, min = 110 MB/s.
One tweak to suggest if you have not done it alreay is for your RAID 0 array: Win7 drive properties, click Policies tab, check both boxes: "Enable write caching on the device" and "turn off windows write cache buffer flushing on the device". This may help your build which has a fast CPU, tons of RAM, and is really light on number of drives relative to your other components. I will assume too that ALL your files are on the RAID 0 array (projects, media, cache, scratch, etc.); if they are not, try that. SSDs are great boot / program drives, but they do not work so great for CS5 / CS5.5 work.
Finally, two tips to use in the meantime so you can get some work done: 1) leave MPE enabled and do a "Sequence / Render entire work area" (from the menu) and 2) play with playback resolution (right click on playback window / playback resolution) to get your scrubbing and playback to work well. On the playback resolution, do play with different options; sometimes "full" may even work better than the easier resolutions (1/2, 1/4, etc.).
Regards,
Jim
-
-
-
5. Re: AVCHD and Premiere...slow going
Harm Millaard Apr 27, 2012 2:38 AM (in response to RByds4te)Those screenshots look pretty decent. Of course turning off Safari before editing and turning off Microsoft Security can help to improve performance. Are you currently overclocking with the AI utility? That takes quite some resources and turns the voltages much higher than you would like.
-
6. Re: AVCHD and Premiere...slow going
JEShort01 Apr 27, 2012 3:23 AM (in response to RByds4te)To get to the policies tab from the properties panel shown in your screen grab:
- go to hardware tab
- select "drive" (your RAID 0 array in this case)
- select "properties" button
- go to Policies "tab"
- check both boxes "enable..." and "turn off..."
That's it!
Jim
-
7. Re: AVCHD and Premiere...slow going
Bill Gehrke Apr 27, 2012 8:01 AM (in response to RByds4te)Just for a trial why don't you turn off your custom setting on performance and set for best performance and see if that makes any difference.
-
8. Re: AVCHD and Premiere...slow going
ECBowen Apr 27, 2012 7:50 AM (in response to RByds4te)The Scrubbing issue is a know issue with CS5.5. Cs5 did not have that problem which means it's tied to the caching model for CS5.5. When you are user interfacing in the titler, bring up the task manager and set it to always on top. Then start making adjustments and see if the interfacing/adjustments only use 1 thread like the key manipulation. If so then that is what is causing that lag.
Eric
ADK
-
9. Re: AVCHD and Premiere...slow going
RByds4te Apr 27, 2012 8:13 AM (in response to Harm Millaard)Harm,
No overclocking. Just feeding my DRAM a bit more voltage, otherwise it is unstable with 32Gb and all DIMMS populated.
Jim,
Thanks for the step-by-step...much appreciated.
Bill,
I have already tried the "adjust for best performance"...it did not help. Thanks though.
-
-
11. Re: AVCHD and Premiere...slow going
ECBowen Apr 27, 2012 9:04 AM (in response to RByds4te)Well atleast 1 component of what you are manipulating there is single threaded which is why 1 core is so high. What were you changing at that time?
EricADK
-
12. Re: AVCHD and Premiere...slow going
RByds4te Apr 27, 2012 10:12 AM (in response to ECBowen)Eric,
the text rotation.
-
13. Re: AVCHD and Premiere...slow going
RByds4te Apr 30, 2012 11:10 AM (in response to RByds4te)First, a big thanks to those that have contributed thus far.
I'm curious to why this know issues has not been addressed by Adobe. The reason why I chose premiere pro 5.5 was the ability to natively edit AVCHD.
Any of the Adobe guys care to chime in on this discussion? Does Premiere pro 6 solve the scrubbing and lagging issues?
I'm still open to suggestions, I would really like this fixed.
-
14. Re: AVCHD and Premiere...slow going
Bill Gehrke Apr 30, 2012 3:50 PM (in response to RByds4te)I in no way represent Adobe but I have not seen your problem, of course I have never rotated text. I have seen a few portions of Adobe that have not fully utilized all the cores.
-
15. Re: AVCHD and Premiere...slow going
RByds4te May 1, 2012 3:24 PM (in response to RByds4te)What about cineform NEOSCENE?
http://cineform.com/products/neoscene/
Do you guys think that could solve my scrubbing problems?
-
16. Re: AVCHD and Premiere...slow going
jamesp2 May 2, 2012 1:53 PM (in response to RByds4te)You can try a free version of the cineform codec with this download:
http://gopro.com/3d-cineform-studio-software-download/
If you do, please report the results.
-
17. Re: AVCHD and Premiere...slow going
RjL190365 May 2, 2012 3:11 PM (in response to jamesp2)The free Cineform Studio is intended only for users of GoPro's own camera products. That program will not allow the user to export from Premiere to Cineform. For that the user must purchase a paid Cineform program. (Yes, I tried the free Cineform Studio, and it did not include any plugins whatsoever for Adobe Creative Suite.)
-
18. Re: AVCHD and Premiere...slow going
jamesp2 May 2, 2012 7:49 PM (in response to RjL190365)Is there anything which prevents you from using the program to export your .mts clips to cineform, and then importing the cineform clips into PP? It's not a Premiere plug-in, but why would you need one?
-
19. Re: AVCHD and Premiere...slow going
RjL190365 May 2, 2012 8:05 PM (in response to jamesp2)The trouble is that the version of the encoder that comes with the free Studio does not support all .mts files. In my own experience, some of the .mts clips failed to import successfully.
In addition, I frequently export edited video movies for further reprocessing. In this case, I either need the Adobe plugin that only comes with the paid versions of Cineform (the plugin allows me to export a movie from Premiere encoded with Cineform) or export the movie as full uncompressed.
-
20. Re: AVCHD and Premiere...slow going
jamesp2 May 3, 2012 8:32 AM (in response to RjL190365)How about Avid DNxHD, which is free? I believe it's possible to export your .mts files through PP and then bring them back into the project, and export again as DNxHD.
Can't swear to it, because I haven't done it. But I believe others have.
-
21. Re: AVCHD and Premiere...slow going
RByds4te May 3, 2012 8:36 AM (in response to RByds4te)Not sure if this helps diagnose, but...after rendering the footage in the work area (from yellow to green) the scrubbing issues and choppy playback no longer occur.
-
23. Re: AVCHD and Premiere...slow going
RByds4te May 3, 2012 11:10 AM (in response to John T Smith)Thanks for the link.
I've already read through that though. I just wanted to see if rendering the work area and having everything work better threw up any flags.
-
24. Re: AVCHD and Premiere...slow going
RjL190365 May 3, 2012 11:48 AM (in response to jamesp2)Can't recommend DNxHD with Adobe because Adobe does not support any MXF files encoded with DNxHD. Thus, the only choice that's even compatible with Adobe would be MOV, which will force QuiRckTime to be run, which severely slows down performance and causes a severe gamma shift in the encoded video.















