Hello!
I know this is not a good command line option and that I should use --alt-preset cbr 128 or --alt-preset 128 if I want an ~128 kbps encoding, but my crappy MP3 players skips and pops if I don't use the parameters below. Anyway, LAME 3.90.3 Modified + APE & CUE support crashes when using the following command line:
"--apeinput -b 128 -m s --nores --noshort --strictly-enforce-ISO"
Here is the error message:
"The instruction at '0x00000000' referenced memory at '0x00000000'. The memory could not be 'read'".
Could it be that the modified LAME version is not compatible with the Monkey's Audio DLL 3.99?
Regards,
Sebastian Mares
Full Version: LAME 3.90.3 Modified + APE & CUE
AFAIK decoding monkey's 3.99 files requires an updated decoder. Meaning 3.98 and older formats can be decoded with the new decoder, but 3.99 cannot be decoded with the old decoder.
I assume 3.90.3 Modified + APE & CUE still makes use of the old monkey's decoding libraries.
I assume 3.90.3 Modified + APE & CUE still makes use of the old monkey's decoding libraries.
I did a quick test with 3.90.3 Modified + APE&CUE and MACDLL.dll (both version 3.97 and 3.99). The result was successful (I could encode a MAC file created by MAC 3.97 without any error). But I didn't perform any compatibility test after MAC 3.99 release. So I'm not sure the modified version works well with MAC 3.99. 
I used following command line:
lame --apeinput -b 128 --nores --noshort --strictly-enforce-ISO CDImage.ape
Can you encode the problem sample in WAVE format if you decode the MAC file first?
The modified LAME uses DLL version of MAC decoding engine (MACDLL.dll).
I used following command line:
lame --apeinput -b 128 --nores --noshort --strictly-enforce-ISO CDImage.ape
Can you encode the problem sample in WAVE format if you decode the MAC file first?
QUOTE
I assume 3.90.3 Modified + APE & CUE still makes use of the old monkey's decoding libraries.
The modified LAME uses DLL version of MAC decoding engine (MACDLL.dll).
QUOTE(Sebastian Mares @ May 7 2004, 05:18 PM)
Hello!
I know this is not a good command line option and that I should use --alt-preset cbr 128 or --alt-preset 128 if I want an ~128 kbps encoding, but my crappy MP3 players skips and pops if I don't use the parameters below. Anyway, LAME 3.90.3 Modified + APE & CUE support crashes when using the following command line:
"--apeinput -b 128 -m s --nores --noshort --strictly-enforce-ISO"
Here is the error message:
"The instruction at '0x00000000' referenced memory at '0x00000000'. The memory could not be 'read'".
Could it be that the modified LAME version is not compatible with the Monkey's Audio DLL 3.99?
Regards,
Sebastian Mares
I know this is not a good command line option and that I should use --alt-preset cbr 128 or --alt-preset 128 if I want an ~128 kbps encoding, but my crappy MP3 players skips and pops if I don't use the parameters below. Anyway, LAME 3.90.3 Modified + APE & CUE support crashes when using the following command line:
"--apeinput -b 128 -m s --nores --noshort --strictly-enforce-ISO"
Here is the error message:
"The instruction at '0x00000000' referenced memory at '0x00000000'. The memory could not be 'read'".
Could it be that the modified LAME version is not compatible with the Monkey's Audio DLL 3.99?
Regards,
Sebastian Mares
I wouldn't call it a MP3 player if it can't:
- decode mid/side channels
- decode short blocks
- make use of the bitreservoir
Well, I only paid about 10 € for it, so it's OK.
I also don't need high quality audio when I am outside.
Edit 1: I have my "lame.exe" file placed inside the "system32" folder together with the "MACDll.dll" version 3.99.
If I encode a PCM WAV file with the above settings, everything works OK, so I assume it is a Monkey's Audio related problem.
Edit 2: My files are also encoded using MAC 3.99.
I also don't need high quality audio when I am outside.
Edit 1: I have my "lame.exe" file placed inside the "system32" folder together with the "MACDll.dll" version 3.99.
If I encode a PCM WAV file with the above settings, everything works OK, so I assume it is a Monkey's Audio related problem.
Edit 2: My files are also encoded using MAC 3.99.
QUOTE(Sebastian Mares @ May 8 2004, 03:06 AM)
Edit 1: I have my "lame.exe" file placed inside the "system32" folder together with the "MACDll.dll" version 3.99.
If I encode a PCM WAV file with the above settings, everything works OK, so I assume it is a Monkey's Audio related problem.
Edit 2: My files are also encoded using MAC 3.99.
If I encode a PCM WAV file with the above settings, everything works OK, so I assume it is a Monkey's Audio related problem.
Edit 2: My files are also encoded using MAC 3.99.
Weird. I couldn't reproduce your problem even though I encode a file created by MAC 3.99.
CODE
C:\>lame --apeinput -b 128 --nores --noshort --strictly-enforce-ISO waiting.a
pe
+ Modification for Cuesheet Support Version 0.5.3
+ Modification for Monkey's Audio (APE) Support.
Available at http://www.geocities.com/nyaochi2000/lame/
LAME version 3.90.3 MMX (http://www.mp3dev.org/)
CPU features: i387, MMX (ASM used), SIMD, SIMD2
Using polyphase lowpass filter, transition band: 15115 Hz - 15648 Hz
Encoding waiting.ape to waiting.ape.mp3
Encoding as 44.1 kHz 128 kbps j-stereo MPEG-1 Layer III (11.1x) qval=5
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
771/774 (100%)| 0:02/ 0:02| 0:02/ 0:02| 9.4778x| 0:00
average: 128.0 kbps LR: 269 (34.75%) MS: 505 (65.25%)
Writing LAME Tag...done
pe
+ Modification for Cuesheet Support Version 0.5.3
+ Modification for Monkey's Audio (APE) Support.
Available at http://www.geocities.com/nyaochi2000/lame/
LAME version 3.90.3 MMX (http://www.mp3dev.org/)
CPU features: i387, MMX (ASM used), SIMD, SIMD2
Using polyphase lowpass filter, transition band: 15115 Hz - 15648 Hz
Encoding waiting.ape to waiting.ape.mp3
Encoding as 44.1 kHz 128 kbps j-stereo MPEG-1 Layer III (11.1x) qval=5
Frame | CPU time/estim | REAL time/estim | play/CPU | ETA
771/774 (100%)| 0:02/ 0:02| 0:02/ 0:02| 9.4778x| 0:00
average: 128.0 kbps LR: 269 (34.75%) MS: 505 (65.25%)
Writing LAME Tag...done
I confirmed the file C:\waiting.ape was successfully created by version 3.99, looking at file information with Monkey's Audio official GUI frontend.
I also confirmed LamedropXPd V.1.3.3, which is released before 3.99 release just as my modified lame, works fine with 3.99 only if we replace MACDLL.dll included in the LamedropXPd package with new one.
Just tested with --alt-preset standard and still no success.
The MAC files I created were encoded using the MAC GUI.
The MAC files I created were encoded using the MAC GUI.
I see. Lame engine seems to have nothing to do with the problem. Can the file be processed with LamedropXPd V.1.3.3?
I replaced the MACdll.dll file with the new 3.99 one and tried to encode, but I get the same crash.
OK. Summary of your problem is:
- get crash when using ape files created by Monkey's Audio 3.99
- get crash with programs using MACDLL.dll interface such as Lame 3.90.3 with APE patch and LamedropXPd V.1.3.3
- the files are successfully decoded with official software
- the version of MACDLL.dll is 3.99
I want to solve your problem, but it's time to sleep and I will leave home for a short trip this weekend. Anyway, I will look into this problem.
If you have a small sample to reproduce the problem, upload the file somewhere or send it to my email address (no bigger than 1MB) (nyaochi AT hotmail DOT com).
- get crash when using ape files created by Monkey's Audio 3.99
- get crash with programs using MACDLL.dll interface such as Lame 3.90.3 with APE patch and LamedropXPd V.1.3.3
- the files are successfully decoded with official software
- the version of MACDLL.dll is 3.99
I want to solve your problem, but it's time to sleep and I will leave home for a short trip this weekend. Anyway, I will look into this problem.
If you have a small sample to reproduce the problem, upload the file somewhere or send it to my email address (no bigger than 1MB) (nyaochi AT hotmail DOT com).
OK, I have sent you the encoded "Completition Sound" to your e-mail address. The summary you made is correct.
The sample you sent to me actually caused crash in my environment. But after installing Monkey's Audio 3.99 Update 4, the bug was gone. Install MACDLL.dll included in 3.99 Update 4 SDK package, and you will be happy, I hope.
You can delete this one. For some strange reason, it was submitted twice.
Thanks! One more thing... I don't need to reencode my files, right?
QUOTE(Sebastian Mares @ May 12 2004, 12:43 AM)
Thanks! One more thing... I don't need to reencode my files, right?
Perhaps. I don't know much about the status of Monkey's Audio 3.99 (I'm sticking with 3.97
), but I didn't see any encoding bug in Monkey's Audio Forum so far.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.