Error Encoding (MP3)

[tedclayton]

Hello -

I recently encountered an issue where Lame XP will not encode to MP3. I have tried my best to troubleshoot but was unsuccessful.

FYI - encoding to AAC works fine.

LAME 01172019.txt

[lordmulder]

Hello.

It looks like LAME encoder (lame.exe) could not be started, because "Access is denied". I don't know why this happens, especially when other encoders work fine. The way how LameXP "extracts" the required encoder binaries and how it launches these binaries when needed is exactly the same for all encoders.

Are you using a so-called "anti-virus" software, other than the standard Windows Defender? If so, then please try disabling or uninstalling it and then try again, to see if it makes a difference...

Regards.

[tedclayton]

After I sent my email I searched for more information on the LameXP website. It's the anti-virus software that's the issue. I use Sophos Home. When I uninstalled it LameXP was able to convert to any file format. Again - it only happens with the MP3 encoder, which is quite unfortunate.

On Sun, Feb 17, 2019 at 6:50 AM LoRd_MuldeR ***@***.***> wrote: Hello. It looks like LAME encoder (lame.exe) could not be started, because "Access is denied". I don't know why this happens, especially when other encoders work fine. The way how LameXP "extracts" the required encoder binaries and how it launches these binaries when needed is exactly the same for *all* encoders. Are you using a so-called "anti-virus" software, other than the standard Windows Defender? If so, then please try disabling or uninstalling it and then try again, to see if it makes a difference... Regards. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Anxa0G8l31qpuC0OvrLqjiQi5XFWFkMWks5vOUH5gaJpZM4aG4uP> .

-- Ted Clayton

[lordmulder]

Problems caused by "anti-virus" software are an ongoing annoyance for software developers. There is, unfortunately, not much we can do, if standard system functions – such as starting a new process – suddenly stop working for no comprehensible reason. That's especially true, if the exactly same program works fine without the "anti-virus" software on dozens of machines; it is clearly a bug in the "anti-virus" software.

Sometimes the detrimental effect of "anti-virus" software can be confined by putting our legitimate software on the "exclusion" list. For Sophos I found this, via a quick Google search:
https://docs.sophos.com/central/Customer/help/en-us/central/Customer/tasks/ep_scanningexclusions.html

Other than that, I can only suggest to either use a less intrusive "anti-virus" product (modern Windows comes with Windows Defender included, so there is no urgent need to install a 3rd-party scanner at all) or discuss the problem directly with Sophos support. Don't expect much help though. Experience shows that "anti-virus" vendors just ignore bugs in their software, unless a product like Microsoft Office or the like is affected. OpenSource tools with maybe a few thousand users are not considered "relevant" 😩

Regards.

[tedclayton]

Thanks for the link! I'm using Windows 7.

On Sun, Feb 17, 2019 at 12:07 PM LoRd_MuldeR ***@***.***> wrote: Problems caused by "anti-virus" software are an ongoing annoyance for software developers. There is, unfortunately, *not* much we can do, if standard system functions – such as starting a new process – suddenly stop working for *no* comprehensible reason. If the exactly same program works fine *without* the "anti-virus" on dozens of machines, it is clearly a bug in the "anti-virus" software. Sometimes the detrimental effect of "anti-virus" software can be confined by putting our legitimate software on the "exclusion" list. For Sophos I found this: https://docs.sophos.com/central/Customer/help/en-us/central/Customer/tasks/ep_scanningexclusions.html Other than that, I can only suggest to either use a less intrusive "anti-virus" product (modern Windows comes with Windows Defender included, so there is no urgent reason to install a 3rd-party scanner) or discuss the problem with Sophos support. Regards. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#77 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Anxa0BWamPuFn8CPbYQt0Q3AKt1nYU3fks5vOYxqgaJpZM4aG4uP> .

-- Ted Clayton