"Clunky" was probably the wrong word.  ** And I was refering to Avid being "clunky" **  Whilst less familiar and therefore slower on PP what I refer to is the choppy playback, the delay as it refreshes media in a project every time you open it, the frequent "... stopped responding" (freq compared to Avid) software glitches, the problems with video drivers.  The "interesting" glitches when using NewBlue titler that dont manifest in Avid.  Many gripes introduced since CC2015.  And with such a dedicated, clean, compliant PC if it wont work for me... 

It is hard to like something that feels like "Russian Roulette" when it upgrades and then how it breaks its connections to AE and Encoder unless you upgrade all apps.  So on AE for example I have lots of plugins that need to be re-bought to work on CC2017.  But CC2015 AE has all I need so why spend over $1000 - but now PP wont talk to AE so if an old project is dynamically linked, that is now broken.

But so many features I love - side by side timelines, copy/paste attributes, colour correction.

That Avid falls further and further behind is sad.

DStone:

The difference between a qualified card and a disqualified one is whether or not GPU effects will be used. It doesn't mean that the card won't work, but ACPL (GPU effects) is disabled.

The K2000M is blacklisted.

After a few email exchanges with Marianna (a year ago or so) about the why (after all, this GPU has 2 GB RAM), I decided to take a chance and comment out the 2GB K2000M in the blacklist; so far without issue ....

BenoitM:

After a few email exchanges with Marianna (a year ago or so) about the why (after all, this GPU has 2 GB RAM), I decided to take a chance and comment out the 2GB K2000M in the blacklist; so far without issue ....

To be honest, I didn't run any perf test to compare GPU enabled/disabled with this GPU.

So perhaps the K2000M is blacklisted just because it does not improve MC performance on ACPL effects...

carlgmi:

what I refer to is the choppy playback, the delay as it refreshes media in a project every time you open it, the frequent "... stopped responding" (freq compared to Avid) software glitches, the problems with video drivers.  The "interesting" glitches when using NewBlue titler that dont manifest in Avid.  Many gripes introduced since CC2015.  And with such a dedicated, clean, compliant PC if it wont work for me... 

Carl I agree on all of those points and yet still find that the improved workflow on output more than compensates for the odd glitch or 10 minutes of lost work. And I've also experienced crashes on Avid as well that have robbed me of 10 or 15 minutes of work.

carlgmi:

It is hard to like something that feels like "Russian Roulette" when it upgrades and then how it breaks its connections to AE and Encoder unless you upgrade all apps.

carlgmi:

but now PP wont talk to AE so if an old project is dynamically linked, that is now broken.

I don't use dynamic link as I find a traditional workflow of render and replace more efficient. Using dynamic link tends to slow down Premiere Pro so much with an AE project on the timeline - so it's just as easy to use render and replace - which is what I'd be doing on Avid anyway. The only problem on Avid is that R and R works well with traditional import but breaks occasionally with linking, whereas PP doesn't.

carlgmi:

So on AE for example I have lots of plugins that need to be re-bought to work on CC2017.  But CC2015 AE has all I need so why spend over $1000

I do understand the reluctance if its going to cost you over a $1000...nearly all my plugins still work.. I think one AE script is broken on the Mac. Mind you I don't use too many plug-ins - I think I have Element, Optical Flares, Particular and some Trapcode plugins that came with Particular. I use a lot of scripts as they save time and they do need to be upgraded but usually free or inexpensive..