After some time I've managed to stabilize my computer (with some help ).
I'm having some trouble though...
I can't seem to get my AVCHD files to scrub smoothly in Pp5.5. I'm beginning to believe that the fault lies with Pp5.5 itself, not my hardware or settings.
My software is up-to-date v5.5.2.
I've gone through Harm's tune tips and have changed almost everything except creating a new page file.
I've searched the forums, but have not found a fix for this problem.
I'm also having issues with certain features when creating titles. Such as: slow feedback when changing the "degree" of the text (it takes sometime for the degree number to change onscreen...basically jumps around). When scrubbing the linear gradient option, I'm also seeing some lagging. I've circled the areas in RED on the image below.
I've included some screen shots in order to help you guys help me......let me know if you need any more info.
This is driving me bonkers.
Adobe PP CS5.5
OS: Windows 7 Pro
CPU: Intel Core i7 3930K 3.2GHz
CPU cooling: intel liquid cooling solution
Motherboard: ASUS P9X79 Pro
Memory: 32GB Samsung 1.35v
GPU: ASUS GTX 570 1280mb
Boot Drive: 180GB corasir Force GT SSD
Storage: Seagate 7200rpm 1TB HDD x2 RAID 0
PSU: Cooler Master 1000w Pro Gold
Optical Drive: pioneer
Case: Fractal Designs Full Tower (1) 180mm fan + (3) 140mm fans + (1) 120mm fan
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.).
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.
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..."
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.
No overclocking. Just feeding my DRAM a bit more voltage, otherwise it is unstable with 32Gb and all DIMMS populated.
Thanks for the step-by-step...much appreciated.
I have already tried the "adjust for best performance"...it did not help. Thanks though.
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.
You can try a free version of the cineform codec with this download:
If you do, please report the results.
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.)
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?
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.
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.
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.