Adobe Community: Latest Premiere Update..heads up...cuda

Currently Being Moderated

1. Steven L. Gotz,

Sep 30, 2012 5:54 PM in reply to shooternz

Report

I archived mine, sort of, by adding ".old" to the file name. However, I figure it is probably easier to overwrite the 680 with my 670 - only a one character change, and then just save the file.

Sigh!

You would think that they would have tested the 670 when they tested the 680 because it is basically the same thing. Well, almost anyway. I can't imagine that the firmware is different except for the part about how many cores it supports.

|

Mark as:

Currently Being Moderated

2. Jim Simon,

Sep 30, 2012 6:14 PM in reply to shooternz

Report

Yeah, after the 6.0.2 update I decided to just leave a copy of the hacked .txt file in My Documents. That way it's nothing but a Copy/Replace to get hardware acceleration back again.

|

Mark as:

Currently Being Moderated

3. Jeff Bellune,

Oct 1, 2012 8:04 AM in reply to Jim Simon

Report

Or just delete the darn thing. If the file doesn't exist, Pr enables hardware MPE by default.

Jeff

|

Mark as:

Currently Being Moderated

4. Jim Simon,

Oct 1, 2012 9:32 AM in reply to Jeff Bellune

Report

That's interesting.

|

Mark as:

Currently Being Moderated

5. shooternz,

Oct 1, 2012 11:16 AM in reply to Jeff Bellune

Report

Does it enable a card that is not on the cuda card list?

|

Mark as:

Currently Being Moderated

6. Jeff Bellune,

Oct 1, 2012 11:35 AM in reply to shooternz

Report

Yes. With no list to check against, all CUDA-capable cards are enabled.

Jeff

EDIT: Graphics memory may still be a limiting factor -- I don't have a low-memory card to check.

|

Mark as:

Currently Being Moderated

7. Steven L. Gotz,

Oct 1, 2012 7:14 PM in reply to Jeff Bellune

Report

First of all, thanks.

Now...

Why is this the first time we have heard of this? I thought this place was full of beta testers who should have known that! Geez!

You would think that someone would have thought to mention it back when the whole "hack" thing came up!

That's what happens when I drop out for a while? Really?

|

Mark as:

Currently Being Moderated

8. Jeff Bellune,

Oct 1, 2012 9:09 PM in reply to Steven L. Gotz

Report

It was mentioned when hardware MPE first appeared as a new feature in Pr. It's even possible that I mentioned it (although if I did, I wasn't the first). The idea just never gained any traction against the inertia generated by continual postings of how to do the "hack".

I thought I'd throw it out there again given the recent question(s) about having to modify the file each time Pr is updated.

Jeff

|

Mark as:

Currently Being Moderated

9. Jim Simon,

Oct 1, 2012 9:09 PM in reply to Jeff Bellune

Report

This is the first time I'm seeing the idea. It certainly is the easier method.

|

Mark as:

Currently Being Moderated

10. Steven L. Gotz,

Oct 1, 2012 9:28 PM in reply to Jeff Bellune

Report

@Jeff

I suppose I can forgive you.

It just ocurred to be that someone could simply write a batch file, like in the old days, to delete the file if it exists, when the PC starts up. Hmmm. I wonder if I remember how?

|

Mark as:

Currently Being Moderated

11. shooternz,

Oct 2, 2012 12:58 AM in reply to Steven L. Gotz

Report

Jeffs information (and revelation) makes not a jot of difference to those that have un supported cuda cards in regard to time or effort.

One either has to delete it or edit it.

Either way..where is any time or effort saved.

Why doesnt Adobe dump it !

Just like how every update re- installs a heap of Default international fonts (duplicates) that few use ...requiring effort to delete.

BTW: A batch file... is it really worth that?

|

Mark as:

Currently Being Moderated

12. tfi productions 44,

Oct 2, 2012 6:13 AM in reply to shooternz

Report

hello Shooternz,

can you direct me to where these 'default international fonts' are

so that i may, too, delete them...(ppro cs5.03 (production premium))

also, are there other 'bloat' files adobe installs that are safe to delete

so i can get some more of my ssd space back?

thanks a bunch,

jeffrey

|

Mark as:

Currently Being Moderated

13. Dave Merchant,

Oct 2, 2012 8:22 AM in reply to shooternz

Report

While some off-list cards work OK reasonably and some of the newer cards work perfectly, there are real issues with instability and overheating for others. Adobe has a responsibility to sell software that performs as advertised (indeed in some territories it's a legal duty). By accepting all CUDA cards they would have no way to know if the GPU-accelerated features are actually working properly on a particular install and could be accused of false advertising - hence the use of the Adobve approved cards list (AACL). If a user wishes to override the limitation by hacking the file they are implicitly negating Adobe's warranty, so there's no liability if their card gets cooked or an export is corrupted. To make it onto the AACL, cards go through a very exhaustive set of tests; going through all the chipset numbers a few variants may seem to have been forgotten but some just fail.

The reason for a text file moderating the AACL instead of something like a registry/plist entry or line in the preferences file is purely to make it simpler to do internal testing. The fact it opens up a route to apply hacks is a side effect.

shooternz wrote:

Why doesnt Adobe dump it !

|

Mark as:

Currently Being Moderated

14. Jim Simon,

Oct 2, 2012 11:47 AM in reply to Dave Merchant

Report

The fact it opens up a route to apply hacks is a side effect.

But a very pleasant one. I'd wager more folks are using hacked cards than approved.

|

Mark as:

Currently Being Moderated

15. shooternz,

Oct 2, 2012 12:56 PM in reply to Dave Merchant

Report

The reason for a text file moderating the AACL instead of something like a registry/plist entry or line in the preferences file is purely to make it simpler to do internal testing. The fact it opens up a route to apply hacks is a side effect.

Thanx Dave ..understood.

None of this is a big deal anyway and I only posted originally ( a PSA)...so those that did the update...might realise why their Mercury Hardware was suddenly not working.

|

Mark as:

Premiere Pro

Latest Premiere Update..heads up...cuda

Sep 30, 2012 5:31 PM

More Like This

Bookmarked By (0)

Answers + Points = Status