M4A encoder problem

[Dat Ei]

Re: M4A encoder problem

Hey Frank,

if the installation of dBpa went well, and you see no problems with that installation, I would repeat just the installation of the codec. If you have installed the 64bit Version of dBpa, you would usually see an 64bit Installation of the codec too.


Dat Ei

[Frank Johnson]

Re: M4A encoder problem

Hey Frank,

if the installation of dBpa went well, and you see no problems with that installation, I would repeat just the installation of the codec. If you have installed the 64bit Version of dBpa, you would usually see an 64bit Installation of the codec too.


Dat Ei

Hi Dat Ei[
Many thanks
Turned off Win Defender but Codec still tried to install 32 bit version judging by file name in security check box.
Any suggestions?

Cheers Frank

[Dat Ei]

Re: M4A encoder problem

What security checkbox are you talking about?


Dat Ei

[Frank Johnson]

Re: M4A encoder problem

What security checkbox are you talking about?


Dat Ei

Hi Dat Ei[

The box that asks whether you want the app to make changes to your computer and names the app.

Cheers Frank

[Frank Johnson]

Re: M4A encoder problem

What security checkbox are you talking about?


Dat Ei

Hi Dat Ei[

The box I was referring to was the User Account Control

Cheers Frank

PS I may not be about till Monday.

[Frank Johnson]

Re: M4A encoder problem

Hi all
Back now
Still trying to install the dBpoweramp-Codec-m4a FDK (AAC) Encoder.
I have uninstalled the Music Converter ans run the reset program and reinstalled with antivirus disabled. All seemed to go well and it seems to have installed the 64 bit version but when I try to install the m4a encoder it tries to load the 32 bit version. If I allowThe installation to complete and try to use the encoder, it can be selected in Music Converter but no compression options appear. If I click convert no converted file is created and the error message shown in my original request for help appears.

Has anyone got any ideas please?

Cheers Frank

[Spoon]

Re: M4A encoder problem

You are best to uninstall dBpoweramp then force the 32 bit version of dBpoweramp, see:

https://forum.dbpoweramp.com/showthread.php?33251-dBpoweramp-64-bit-and-32-bit-Compatibility

[Frank Johnson]

Re: M4A encoder problem

Hi Spoon

Many thanks for your patience

Installed as 32 bit as suggested. All went well until the install screen where it wanted to install to Program files.I had to create an Illustrate folder in the Program files X86 folder and change the target install folder to that. All then went well and the compression settings appeared . The conversion seemed to go to plan.

Many Many Thanks for all your and DatEI's help. Very much appreciated and very grateful. You saved the day.

Cheers gratefully
Frank Johnson

[whorfin]

Re: M4A encoder problem

I had this problem too, and found none of the advice given to be helpful. Dropping this here for future googlers and to help out those who come after.

My problem started with the obsolete support files on the Nimbie site, which were 32-bit only.
The upshot of all this is that [and I believe Spoon has noted this before] "if you have EVER installed any dBpoweramp component as 32-bit to a given directory, you won't be able to install 64-bit components to that same directory"

The issue seems to be that uninstalling 32-bit components fails to clean out registry entries used to check for 32-bit installs. Here's how to fix that.

Installers check for the existence of the key

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SpoonInstall\dBpoweramp

if it exists, they check for "dBconfig.exe" in that directory. If it's there, you get 32-bit install, no questions asked.

So, if you have removed all 32-bit components and only want 64-bit from now on, try the following:
[warning! expert mode! own risk ahead!]

open regedit
go to this node

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\SpoonInstall

confirm the presence of both

dBpoweramp

and

dBpoweramp64

keys

Delete the non-64 bit version, ie

dBpoweramp

For good measure, repeat the above in the below path; it may all be fine if the registry reflector did its job

HKEY_CURRENT_USER\Software\SpoonInstall

Now try your installer again, and rejoice in the 64-bit installation going correctly this time, without losing your settings and other configurations.

It would sure be nice if uninstalling 32-bit removed that key. Another fix would be for the installer to
check if the "dbConfig.exe" at the 32-bit path is actually a 64-bit executable. If so, it's a 64-bit install, yo.

Cheers