[John Welsh]

If you take graphics card out of the equation for a moment (meaning to expect no added speed from it if it’s never officially supported – and provided you don’t enable manually – and if it works) other key things to think about from your original post are RAM (go for at least 12GB, 16GB if you can swing it).

And also a fast primary hard drive. Until SSDs are less $ and have more capacity, a nice compromise is a Seagate Momentus Hybrid SSD (if it’s available for the laptop you are configuring).

*** Just in case – make sure you stay away from any kind of overclocking (CPU). It’s fine for gamers but not us. Laptops like Alienware and ASUS are built for the gaming crowd. They are great for us too since they have performance components within, but you’ll need stability which overclocking can affect.

[John Welsh]

Also check into an Asus G74SX-A1 (or and A2) in the process of upgrading 1900.00 or so will get you a similar set up.

GTX 560m inside (though it’s not on “the list”)

JW

[John Welsh]

Got it. Thanks, at least the temp fix is easy…
JW

[John Welsh]

Todd,

Yes,I have been batch renaming the file extensions and all is well.

Curious, is this a QT problem/limitation or is it something that fixable with a patch for Premiere?

Thanks for the attention to this subject…
JW

[John Welsh]

Hey Adam,

renaming definitely does the trick…and it’s a good fix until they patch this. Thanks lots.

John

[John Welsh]

Hi Kevin,

same footage (Nikon d7000). It’s been behaving lately, but I sometimes batch 50-70 short (duration) files. It’s not easy to reproduce as it’s random.

While we are discussing AME, I noticed when working with watch foiders the source file is copied to a new subfolder. Having the auto output folder is great but is there way to turn off each source file being moved to its own folder?

JW

[John Welsh]

Thanks Kevin, I though it may be a bug/upgrade issue since CS5 is pretty solid.

Also, with 5.5 Media Encoder long queues sometimes don’t finish. No crash, but files have to be subtracted/added and restarted. Where CS5 AME is fine.

John

[John Welsh]

Memory and drive speed also seem Ok. It only happens in 5.5, same files in 5 play fine.

Lowering playback resolution also doesn’t affect this either. What happens is I’ll start playback, 4-5 seconds go by then it gets choppy. I’ll stop playback, being again, 4-5 seconds later it’s choppy again.

[John Welsh]

Thanks Jeff,
I’m getting about 15%- 17% CPU usage tops, though several are “parked.”
JW

[John Welsh]

Adobe is just as guilty as anyone (as rushing their releases to market and having us pay to be beat testers)…I figure on exploring the new version about 6 months in…should be “safe” by then.