Lame Encoder Locator Error

Bug #889314 reported by Dark St3alth
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mixxx
Invalid
Medium
Unassigned
1.9
Invalid
Medium
Unassigned

Bug Description

Windows 7 64-bit and Mixxx 1.9.2. I placed the LAME MP3 encoder in the Mixxx folder and restarted it. I ran Mixxx as an administrator and with normal privileges and still returns the same error. I thought it might be looking for a file "liblame.dll" as it still didn't like it, but that doesn't seem to be the case. I have followed the wiki page on installation, and the connection error is about a Internet connection/Authentication problem even though the details I provided were correct.

Screenshot attached, here is an additional source: http://img502.imageshack.us/img502/332/errorik.png

Tags: lame
Revision history for this message
Dark St3alth (hack3r-64) wrote :
Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Hey there,

Sorry for these maybe obvious questions, but please check the following:

1) You are running Windows 64-bit, but with MIxxx 32-bit. Did you make sure to copy libmp3lame.dll from x86 folder of the LAME release and not the x64 folder?

2) Did you install both Mixxx 32-bit and Mixxx 64-bit? Could it be possible that you are running the 64-bit version (located in c:\Program Files\Mixxx) but putting lame_enc.dll in the 32-bit version's folder (c:\Program Files (x86)\Mixxx)?

If you haven't installed the 64-bit version of MIxxx 1.9.2, could you please download and install that and try to use the 64-bit version? It could be that the 32-bit version of LAME does not work in Windows 64-bit for some reason.

Thanks for the report!
RJ Ryan

Changed in mixxx:
importance: Undecided → High
importance: High → Medium
Revision history for this message
Dark St3alth (hack3r-64) wrote :

Sure I'll give that a try and come back and comment with the results.

Revision history for this message
Dark St3alth (hack3r-64) wrote :

Ok, one interesting instruction that seemed to change things was:

"Rename the DLL to lame_enc.dll"

Worked with both 64 and 32 bit versions (with the correct lame.dll). Just a classic user error...

Side comment though, what's different with "lame_enc.dll" and "libmp3lame.dll"?

Revision history for this message
RJ Skerry-Ryan (rryan) wrote : Re: [Bug 889314] Re: Lame Encoder Locator Error

Hmm, interesting. In your screenshot you had a "lame_enc.dll" in the folder
though. Where did that come from? Did you download it previously or
something?

I don't think the name matters, though. We should just check for both.

On Fri, Nov 11, 2011 at 5:36 PM, Dark St3alth <email address hidden>wrote:

> Ok, one interesting instruction that seemed to change things was:
>
> "Rename the DLL to lame_enc.dll"
>
> Worked with both 64 and 32 bit versions (with the correct lame.dll).
> Just a classic user error...
>
>
> Side comment though, what's different with "lame_enc.dll" and
> "libmp3lame.dll"?
>
> --
> You received this bug notification because you are a member of Mixxx
> Development Team, which is subscribed to Mixxx.
> https://bugs.launchpad.net/bugs/889314
>
> Title:
> Lame Encoder Locator Error
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/mixxx/+bug/889314/+subscriptions
>

Revision history for this message
RJ Skerry-Ryan (rryan) wrote :

Since you solved the issue (renaming the DLL to lame_enc.dll) marking Invalid. Thanks for the report Dark St3alth.

Changed in mixxx:
status: New → Invalid
Revision history for this message
Swiftb0y (swiftb0y) wrote :

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/6104

lock status: Metadata changes locked and limited to project staff
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.