At the end of encoding a file with cyrillic characters in name WinLame crashes leaving a .tmp file at the destination folder. If source is renamed to Latin-only characters, it's encoded successfully.
Hello Dmitriy,
Today I released winLAME 2017 beta 1. Please try if the bug is fixed with this version. I put some testing in processing non-ASCII file names and tags, so it should be fixed.
Thanks!
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, Michael.
The same, winLAME 2017 beta 1 detects internal error and provides minidump. It leaves *.mp3.temp file in destination folder.
I used standalone ZIP and installed vcredist_x86_vc14.exe from it. There are sample .wav and minidump attached. It may happen you have to set system codepage to CP1251 to be able to manage the .wav file.
Hi Dmitriy,
I looked at the minidump and figured out that the output file may be generated, but for some reason the mp3 output data buffer is not created, resulting in the crash when writing out the data to the file. I fixed the crash itself, but I'm not sure if this fixes the problem, since I couldn't reproduce the problem at my machine due to different code pages.
I made a new Appveyor build of winLAME with the bug fixes (2.17.1.16): https://ci.appveyor.com/project/vividos/code/build/artifacts
Could you try if this winLAME.exe fixes your problem?
Thanks!
Regards,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
could you please upload/email missing libs, if any?
Dmitriy
On 10.05.2017 22:01, Michael Fink wrote:
Hi Dmitriy,
I looked at the minidump and figured out that the output file may be
generated, but for some reason the mp3 output data buffer is not
created, resulting in the crash when writing out the data to the file.
I fixed the crash itself, but I'm not sure if this fixes the problem,
since I couldn't reproduce the problem at my machine due to different
code pages.
I made a new Appveyor build of winLAME with the bug fixes (2.17.1.16): https://ci.appveyor.com/project/vividos/code/build/artifacts
Could you try if this winLAME.exe fixes your problem?
Thanks!
Regards,
Michael
Status: pending Group: winLAME-2017-beta1 Labels: charset Created: Thu Jan 07, 2016 04:39 PM UTC by Dmitriy Kuznetsov Last Updated: Thu Mar 30, 2017 06:11 PM UTC Owner: Michael Fink
At the end of encoding a file with cyrillic characters in name WinLame
crashes leaving a .tmp file at the destination folder. If source is
renamed to Latin-only characters, it's encoded successfully.
Hi Dmitriy,
the winLAME.exe from the build is meant to be placed in the folder where a pre-installed or pre-unzipped winLAME 2017 beta 1 is located. Does that work? When not, I have to do a build by myself and give you the updated zip archive.
Regards,
Michael
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've started the test build, hanks to your explanation. It reports
internal error, leaves .tmp(which is not correct .mp3 and cannot be
played) and saved attached minidump.
Also it reports internal error(with minidump) encoding the same file
renamed with latin characters, leaves .tmp and produces correct .mp3
Hi Dmitriy,
the winLAME.exe from the build is meant to be placed in the folder
where a pre-installed or pre-unzipped winLAME 2017 beta 1 is located.
Does that work? When not, I have to do a build by myself and give you
the updated zip archive.
Regards,
Michael
Status: pending Group: winLAME-2017-beta1 Labels: charset Created: Thu Jan 07, 2016 04:39 PM UTC by Dmitriy Kuznetsov Last Updated: Wed May 10, 2017 07:01 PM UTC Owner: Michael Fink
At the end of encoding a file with cyrillic characters in name WinLame
crashes leaving a .tmp file at the destination folder. If source is
renamed to Latin-only characters, it's encoded successfully.
Hi Dmitriy,
thank you for the zip file with the .wav file, and the dump file. I set the "Region" settings to "Russian Federation" on my computer and could extract the zip file successfully. Encoding with my current version of winLAME was successful, though. I got an mp3 file with the same name as the .wav file.
I also took a look at the dump file and could see where winLAME was crashing on your computer. I added some more code to prevent this, and also added a more detailed error message when the output mp3 file is created.
Hello Dmitriy,
Today I released winLAME 2017 beta 1. Please try if the bug is fixed with this version. I put some testing in processing non-ASCII file names and tags, so it should be fixed.
Thanks!
Michael
Hi, Michael.
The same, winLAME 2017 beta 1 detects internal error and provides minidump. It leaves *.mp3.temp file in destination folder.
I used standalone ZIP and installed vcredist_x86_vc14.exe from it. There are sample .wav and minidump attached. It may happen you have to set system codepage to CP1251 to be able to manage the .wav file.
Thanks Dmitriy, I will look into the file and minidump!
Hi Dmitriy,
I looked at the minidump and figured out that the output file may be generated, but for some reason the mp3 output data buffer is not created, resulting in the crash when writing out the data to the file. I fixed the crash itself, but I'm not sure if this fixes the problem, since I couldn't reproduce the problem at my machine due to different code pages.
I made a new Appveyor build of winLAME with the bug fixes (2.17.1.16):
https://ci.appveyor.com/project/vividos/code/build/artifacts
Could you try if this winLAME.exe fixes your problem?
Thanks!
Regards,
Michael
Hi, Michael
Looks like the build is experiencing a DLL hell trouble on start. The
previous one, 2010 beta 2 starts successfully with following dll-s list:
bass.dll
basscd.dll
basswma.dll
libFLAC.dll
libgcc_s_sjlj-1.dll
libmad.dll
libmmd.dll
libmp3lame.dll
libogg-0.dll
libopus-0.dll
libopusfile-0.dll
libsndfile-1.dll
libspeex.dll
libvorbis.dll
libwinpthread-1.dll
msvcp140.dll
nLAME.dll
vcruntime140.dll
winLAME.0407.dll
could you please upload/email missing libs, if any?
Dmitriy
On 10.05.2017 22:01, Michael Fink wrote:
Related
Bugs:
#66Hi Dmitriy,
the winLAME.exe from the build is meant to be placed in the folder where a pre-installed or pre-unzipped winLAME 2017 beta 1 is located. Does that work? When not, I have to do a build by myself and give you the updated zip archive.
Regards,
Michael
Hi, Michael
I've started the test build, hanks to your explanation. It reports
internal error, leaves .tmp(which is not correct .mp3 and cannot be
played) and saved attached minidump.
Also it reports internal error(with minidump) encoding the same file
renamed with latin characters, leaves .tmp and produces correct .mp3
Probably you may find useful *.wav, which has cyrillic chars in name -
https://yadi.sk/d/bdLzw_vN3J7NEU
Best regards,
Dmitriy
On 12.05.2017 17:59, Michael Fink wrote:
Hi Dmitriy,
thank you for the zip file with the .wav file, and the dump file. I set the "Region" settings to "Russian Federation" on my computer and could extract the zip file successfully. Encoding with my current version of winLAME was successful, though. I got an mp3 file with the same name as the .wav file.
I also took a look at the dump file and could see where winLAME was crashing on your computer. I added some more code to prevent this, and also added a more detailed error message when the output mp3 file is created.
Could you again test the latest appveyor build of winLAME:
https://ci.appveyor.com/project/vividos/code/build/artifacts (should be build 2.17.1.21).
Thank you!
Regards,
Michael
Hi Dmitriy,
Please retest this bug with the newly released winLAME 2017 beta 2 version. Thanks!
Regards,
Michael