Slow MP3 conversion - detail

[eddeeedddeee]

When I log in to Win2k as administrator, I get 9x realtime encoding. When I log in as regular (not "super") user, I get .6-.8x.

Are ther suggestions for this problem somewhere?

-tom

[eddeeedddeee]

Re: Slow MP3 conversion - detail

More...

another regular user account works fine also. It appears to be something about the ONE account. The latest converter (registered) has been installed over an old, unregistered version, which had been used a few times. Must be some old settings. Where would they be?

-tom

[ChristinaS]

Re: Slow MP3 conversion - detail

It's not even supposed to work for non admin or power user accounts as far as I remember.

I think you only need one clean installation of the registered product.

There is something about read/write permissions to some folders I think, in order to allow other non-admin users to use the product. I'll see if I can find the thread on that.

[eddeeedddeee]

Re: Slow MP3 conversion - detail

Well, it works fine on most accounts, so that doesn't seem to be the issue. And it was as "clean" an installation as possible, in that I did remove the previous from the Control Panel.

- still looking...

[eddeeedddeee]

Re: Slow MP3 conversion - detail

For reference, Spoon answered this in 2003. The thing is to delete the user's (HKEY_CURRENT_USER>Software)>Illustrate>DBPowerAmp key (folder) in entirety from the registry. Some leftover entries in there apparently cause problems.

-tom

[Spoon]

Re: Slow MP3 conversion - detail

Deleting that registry folder will just mean that some settings were chosen that is slowing down dpoweramp (such as different mp3 compression settings).

[eddeeedddeee]

Re: Slow MP3 conversion - detail

Spoon,

Surely true, but there was nothing I could identify via the gui. I didn't go thru each entry in the reg folder, looking for a potential match in the gui, but I'm guessing there was one that was created in the previous version (don't remember which it was) that didn't correspond properly to a new one.

Perhaps this would be a good sticky answer for the many "slow" queries...