I have a dual quad core processor, hardware is not the issue.  If you had read my comment about trimming the clips you might have deduced that.

I also have the same issue with CS5.5 trail version, specially when using nikon D7000 files, CS5 itself had some issues now CS5.5 looks more trouble.

What type of DSLR is that clip from?  It would be interesting to get a clip from the same kind of camera to try.  Let me know and I will try to locate another clip from the same model to try.

KMS

I found some interesting results that I will post tomorrow with some screen shots....seems like there is a problem in CS5.5 specific to the D7000.

KMS

csqaraqlino,

I found a website (http://tinyurl.com/6hfom6c) that had numerous D7000 files to download and non of them would play smoothly.  I don't have any experience with Nikon DSLR footage (all my DLSR footage is from Canon cameras).  So, I decided to find footage from other Nikon models and I was able to find footage from Nikon's D300S and D5100.  Footage from those two models played fine in CS5.5.  I'm not sure what is different about the D7000, but the difference may be effecting your Footage Firm clips as well.  What codec does the Footage Firm clips use?  If I right click on a Canon T2i file in the project window and select "Properties" I get a dialog box like the one below for all the camera clips except the D7000:

When I pull up the clip properties for the D7000 clips, it looks like this:

It's strange that it show such fluctuations in the data rate.  I'm not sure why all other DSLR clips show up as MPEG under movie type and there isn't a Data Rate Analysis, but footage from the D7000 shows up as Quicktime for the movie type along with the Data Rate Analysis.  Seems like a bug in CS5.5.  I don't believe that it is a video card driver problem.  I wish someone from Adobe would jump in here.  I may start a new thread outlining the details.  What does the clip properties look like in CS5?

If I just re-name the file from .MOV to .mpg it plays fine.

I put both on the timeline and the .MOV will stutter and the .mpg plays smooth.

Maybe this will work with you as a work-around.

Glad you got it working.

When it comes down to it all we really want is for things to work.

GLenn

Kevin,

I noticed that these clips are using High profile versus, say Canon DSLR clips which use Baseline profile. Is that the source of the issue? These do appear to be latching into the QT32Server process, instead of functioning with the native Premiere importers, resulting in the rather abyssmal performance, I assume--changing the extension to MPG forces Premiere to use the MPEG handler instead of the QT handler.

Just curious

The suggested workaround doesn't appear to work for Win 7. 

i also have horrible stuttering problems with my canon 60d  footage.its so bad you  cannot work in PPcs5.5.

i reinstalled PPcs5 lastninght,updated  to latest version,imported same files on same computer.......... PP works worlds better!!!!!!!!!!

i can now actually work with my canon files.

so if anyone from adobe is here, if it matters,this is not only a nikon problem its canon as well.

if working strictly with native dslr files,demo cs 5.5 before updating

hello Colin . i reinstalled CS5 from CS5.5

CS 5.5 cannot play my canon files

CS 5    plays my canon files

this is on the same exact computer no hardware changes

i wish it were that simple

ive been trying to troubleshoot my problems for the last month nothing seems to help except,  going back to PP cs5.

again, this is on the exact same computer with no hardware change.

if i can open dslr file x in PPcs5 edit, scrub, add effects with for the most part no problems at all

then open same exact dslr file x in PPcs5.5 and cannot scrub,edit,add any effect

i would think there is a prob with cs5.5?

also not trying to flame and i know its hard to tell someones emotion via text. sincerly appriciate everyones help

p.s i switced to PP from vegas pro. all files work fine with perfect scrubbing, editing in vegas pro

on the exact same machine. its a bit frustrating

i will update if i make any foward progress