LameXP v4.21 Final · Build #2382 (2023-12-29) [Archive] - Page 18

real.finder

2nd January 2013, 14:03

LameXP v4.05 (Build #1100), compiled on 2012-09-03 at 22:48:43
-------------------------------
C:/Users/SHEKO6~1/AppData/Local/Temp/e85c168fcc05486f9728f8b3be211cdc/lxp_avs2wav.exe D:\sheko6000.2\lossless.avs C:\Users\SHEKO6~1\AppData\Loca\Temp\9\e85c168fcc05486f9728f8b3be211cdc\c45608c1de5845c7b8f83f9a597e4938.wav
avs2wav v1.3 [Aug 16 2011]
by Jory Stone <jcsston@toughguy.net>, updates byLoRd_MuldeR <mulder2@gmx.de>
Input: D:\sheko6000.2\lossless.avs
Output: C:\Users\SHEKO6~1\AppData\Local\Temp\9\e85c168fcc05486f9728f8b3be211cdc\c45608c1de5845c7b8f83f9a597e4938.wav
Checking Avisynth...
Done
Analyzing input file...
Done
Opening output file... Done
[Audio Info]
TotalSamples: 364299776
TotalSeconds: 7590
SamplesPerSec: 48000
BitsPerSample: 16
Channels: 6
AvgBytesPerSec: 576000
Dumping audio data, please wait:
All samples have been dumped. Exiting.
Dump size exceeds 4 GB, cannot save as RIFF/Wave file!
Error while closing output wave file!
Exited with code: 0xFFFFFFFA

LoRd_MuldeR

2nd January 2013, 16:05

Hi, real.finder.

Indeed, as a matter of fact, the maximum size of a RIFF/WAVE file is 4 GB. Do you have any specific question/suggestion? :confused:

BTW: Please use ... tags for pasting logs and other lengthy stuff...

real.finder

2nd January 2013, 16:57

thank you for fast reply

BTW: Please use ... tags for pasting logs and other lengthy stuff...

sorry, I forgot to do that; more like, I see it not necessary because I post the log directly

any way, I think it's avs2wav, avs2wav has a lot of Issues, like it not work if there is no video in avs script

any way I use a big pcm wav file size 4.7 gb directly without an avs script and lamexp work normally

for suggestion, you can use avs2pipemod (http://forum.doom9.org/showthread.php?p=1565165#post1565165) instead of avs2wav, because it work even if there is no video in avs script and more things

for file 4gb and over, it show warning but it work for me

avs2pipemod.exe -wav "x.avs" > "x.wav"

pause

D:\x>avs2pipemod.exe -wav "x.avs" 1>"x.wav"
avs2pipemod[info]: writing 11776.767 seconds of 48000 Hz, 6 channel audio.
avs2pipemod[warning]: audio size over 32bit limit (4GB), clients may truncate audio.
avs2pipemod[info]: finished, wrote 11776.767 seconds [100%].
avs2pipemod[info]: total elapsed time is 60.708 sec.

mediainfo

General
Complete name : D:\x\x.wav
Format : Wave
File size : 6.32 GiB
Duration : 3h 16mn
Overall bit rate mode : Constant
Overall bit rate : 4 608 Kbps

Audio
ID : 0
Format : PCM
Format settings, Endianness : Little
Codec ID : 1
Duration : 3h 16mn
Bit rate mode : Constant
Bit rate : 4 608 Kbps
Channel(s) : 6 channels
Sampling rate : 48.0 KHz
Bit depth : 16 bits
Stream size : 6.32 GiB (100%)

I wonder how eac3to work for very big file

thank you again

LoRd_MuldeR

2nd January 2013, 17:34

The WAVE/RIFF file format has a size limit of 4 GB. That's a direct consequence of the fact that chunk sizes are defined as 32-Bit integers (unsigned). There is no way around that, except for changing the specifications. That of course wouldn't be WAVE anymore and all programs would have to be updated to support the new format! And indeed, there is the RF64 format that resolves the issue. Only problem: Support for RF64 is pretty much non-existing in audio tools of today! At the same time, some tools use an "ugly" hack to write "normal" WAVE files larger than 4 GB, by simply setting the "size" value to the maximum possible value (~4 GB) and then writing as much data as they have. In other words: They write past the end of the file! Such file obviously is non-standard and broken! Whether any subsequent tool will be able to process the "broken" file is sheer luck.

About avs2wav issues: There may be some other problems in that tool, which I'd have to investigate. But the 4 GB limit is not a bug or limitation of avs2wav. It simply is not possible to write a (correct) WAVE file larger than 4 GB. Unless you have a time machine to go back to the early 90's and convince Microsoft to define the WAVE format with 64-Bit size fields (rather than 32-Bit), nothing can change that... :p

real.finder

2nd January 2013, 17:47

I see, but what about avs2pipemod?

In the end, we will not use the wav file officially, it's just a temporary file within lamexp operations

LoRd_MuldeR

2nd January 2013, 21:02

I see, but what about avs2pipemod?

I'd prefer to fix my avs2wav tool.

In the end, we will not use the wav file officially, it's just a temporary file within lamexp operations

The temp file will be processed by the encoder, so unless all encoders supported/used by LameXP are able to read a "broken" Wave file, creating such a file is pointless.

Also, what if the user selects Wave/PCM output ???

real.finder

2nd January 2013, 22:18

so, what about wave 64 in temporary file within lamexp operations?

and you can make the output in 4gb limit as usual by make the temporary file within lamexp operations only use the fixed avs2wav or avs2pipemod

The choice is yours

thank you again

LoRd_MuldeR

2nd January 2013, 22:29

so, what about wave 64 in temporary file within lamexp operations?

As said before, support for RF64 Wave files is pretty much non-existing in the relevant audio tools. None of the encoders used by LameXP can read this.

LoRd_MuldeR

17th January 2013, 21:33

LameXP v4.07 Beta-1
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/2013-01-17/

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-01-17)
* Fixed handling of certain characters when passing meta tags on the command-line

LoRd_MuldeR

25th January 2013, 01:15

LameXP v4.07 Beta-2

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-01-24)
* Fixed handling of certain characters when passing meta tags on the command-line

Atak_Snajpera

25th January 2013, 13:18

Lord_Mulder
I was always wondering why this thread (tool) is not in Audio section? Instead it sits lonely in development section like outcast ;)

SeeMoreDigital

25th January 2013, 13:29

Lord_Mulder
I was always wondering why this thread (tool) is not in Audio section? Instead it sits lonely in development section like outcast ;)
Agreed...

LoRd_MuldeR

25th January 2013, 14:37

I think it could fit into both sub-forums. Originally I opened the thread under "Development", because it was a tool that I was developing myself and I didn't want to imply that this is a "finished" product. I would have put it under "Audio", if I had wanted to discuss about some third-party audio tool. But that wasn't the case. I'm not quite sure whether it should be moved to "Audio" nowadays. But I think moving the thread, after all the time, might confuse some people...

SeeMoreDigital

26th January 2013, 12:56

But I think moving the thread, after all the time, might confuse some people...
I would suppose that all the people who are really interested in LameXP will have subscribed to the thread... So moving it over to the audio section would make no difference to them ;)

LoRd_MuldeR

3rd February 2013, 17:32

LameXP v4.07 Beta-3

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-01-24)
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Fixed handling of certain characters when passing meta tags on the command-line

LoRd_MuldeR

9th February 2013, 20:09

LameXP v4.07 Beta-4

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-02-09)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line

LoRd_MuldeR

12th February 2013, 22:42

LameXP v4.07 Beta-6
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/2013-02-12/

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-02-09)
* Updated Valdec decoder to v1.4.0a (2013-02-11), based on latest AC3Filter Tools
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line

real.finder

16th February 2013, 21:34

hi

Any idea about mka support in lamexp?

I use http://sourceforge.net/projects/aud-subsplitter

and the output is mka, for this I have to get it back to origin aac or mp3, etc...

To work with lamexp

thx

LoRd_MuldeR

16th February 2013, 21:42

The problem is that there can be any type of audio in a Matroska file. And all the decoders used by LameXP to decode the various audio formats do not support Matroska files as input.

We would need to demux the audio stream, e.g. via mkvextract (from MKVtoolnox), before decoding, but that currently doesn't fit into the design of LameXP...

manolito

21st February 2013, 00:45

LoRd_MuldeR

21st February 2013, 00:56

I just found out that the latest Beta version refuses to start on my (ancient) machine:

The last line in the console window is "CPU_TYPE_X86_GEN".
The program exits with the message: "Unhandled exception handler invoked, application will exit".

My machine: CPU Intel Celeron Coppermine 1.1 Ghz, MMX and SSE (no SSE2), 576 MB RAM. WinXP Pro SP3, all current updates.

That's interesting. Though I have no idea why that is :confused:

At that point, the application does nothing, but extract the binaries. It does not run any of them yet. And even if we assume that it extracts a "wrong" (unsupported) binary and eventually runs it, only the new process would crash - not the LameXP process itself. So it must be something in the extraction/initialization code...

I also tried to reproduce the behavior the behavior with:
LameXP.exe --force-cpu-no-sse --force-cpu-no-64bit

But works okay for me:
LameXP - Audio Encoder Front-End v4.07 Beta-6 (Build #1246)
Copyright (c) 2004-2013 LoRd_MuldeR <mulder2@gmx.de>. Some rights reserved.
Built on 2013-02-12 at 20:43:58 with MSVC 2012-U1 for Win-x86.

[...]

CPU flags overwritten by user-defined parameters. Take care!

CPU vendor id : GenuineIntel (Intel: 1)
CPU brand string : Intel(R) Core(TM)2 Quad CPU @ 2.40GHz
CPU signature : Family: 6, Model: 15, Stepping: 7
CPU capabilities : MMX: 1, SSE: 0, SSE2: 0, SSE3: 0, SSSE3: 0, x64: 0
Number of CPU's : 4

[...]

Thread is doing something important... Done

Selected CPU is: CPU_TYPE_X86_GEN
Extracting file: aften.i386.exe -> aften.exe
Extracting file: gpgv.exe -> gpgv.exe
Extracting file: elevator.exe -> elevator.exe
Extracting file: dcaenc.exe -> dcaenc.exe
Extracting file: avs2wav.exe -> avs2wav.exe
Extracting file: flac.exe -> flac.exe
Extracting file: gpgv.gpg -> gpgv.gpg
Extracting file: faad.exe -> faad.exe
Extracting file: lame.i386.exe -> lame.exe
Extracting file: mac.exe -> mac.exe
Extracting file: mediainfo.i386.exe -> mediainfo.exe
Extracting file: mpcdec.exe -> mpcdec.exe
Extracting file: mpg123.exe -> mpg123.exe
Extracting file: oggdec.exe -> oggdec.exe
Extracting file: oggenc2.i386.exe -> oggenc2.exe
Extracting file: opusdec.exe -> opusdec.exe
Extracting file: opusenc.exe -> opusenc.exe
Extracting file: refalac.exe -> refalac.exe
Extracting file: shorten.exe -> shorten.exe
Extracting file: sox.exe -> sox.exe
Extracting file: speexdec.exe -> speexdec.exe
Extracting file: tta.exe -> tta.exe
Extracting file: valdec.exe -> valdec.exe
Extracting file: wget.exe -> wget.exe
Extracting file: wma2wav.exe -> wma2wav.exe
Extracting file: wupdate.exe -> wupdate.exe
Extracting file: wvunpack.exe -> wvunpack.exe
All extracted.

Can you please try to find the last build that still worked on your old machine?
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/

Aside from this, I discovered that the latest version of SOX now (kind of) supports large WAV files in the WAVE_FORMAT_EXTENSIBLE format. This is very useful for me because I now can convert large multichannel AAC files to multichannel AC3 with normalization. The following command sequence works: (source is a large (> 5GB) 6ch WAV file)

sox.exe --ignore-length -t wav test.wav -t wav normalized.wav gain -n -1
aften.exe -readtoeof 1 normalized.wav test.ac3

So I see no reason why LameXP shouldn't do this also. Version 4.06 final does not work, even if I use the latest SOX version and add the custom command "-readtoeof 1" to Aften. I had hoped that version 4.07 Beta 6 had corrected this, but unfortunately I could not test it...:devil:

The problem is, we won't know when to pass "--ignore-length". Passing that always doesn't sound like a good idea...

manolito

21st February 2013, 02:06

OK, just tested almost evey 4.07 version starting with Alpha 4. No success, the last working version is 4.06 final. Every version after this shows the same behavior...:scared:

The problem is, we won't know when to pass "--ignore-length". Passing that always doesn't sound like a good idea...

Oh, I do think it is a good idea. From the SOX manual:
--ignore-length
Override an (incorrect) audio length given in an audio file’s header. If this option is given then
SoX will keep reading audio until it reaches the end of the input file.

Just like the Aften "-readtoeof 1" parameter which should always be present, I believe this SOX parameter won't do any harm, even in situations when it is not necessary. Requires some testing...

Cheers
manolito

LoRd_MuldeR

21st February 2013, 02:40

OK, just tested almost evey 4.07 version starting with Alpha 4. No success, the last working version is 4.06 final. Every version after this shows the same behavior...:scared:

Hmm, that's strange. We still need to figure out the exact build number, so I have a chance to figure out what exactly changed.

Version 4.06 Final is build #1170. The next build I uploaded is #1197 (2012-11-24):
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/2012-11-24/LameXP-ALPHA.2012-11-24.Release-Static.Build-1197.exe/download

Does that one already fail ???

Oh, I do think it is a good idea. From the SOX manual:

--ignore-length
Override an (incorrect) audio length given in an audio file’s header. If this option is given then
SoX will keep reading audio until it reaches the end of the input file.

Just like the Aften "-readtoeof 1" parameter which should always be present, I believe this SOX parameter won't do any harm, even in situations when it is not necessary. Requires some testing...

We really shouldn't force this behavior unless we absolutely need it, because:
If SoX simply ignores the length, i.e. it continues to reads until it stumbles upon the end of the file, it obviously cannot report progress. That's because if you have read X samples of an "unknown" length, how many percent of the whole thing you have processed? You simply cannot know until you are at 100%. Consequently this would break progress reporting in LameXP, which is a bad thing.
There may be perfectly legal RIFF files that have other (unspecified) data after the audio data in the first "data" chunk. The length info guarantees that we don't read beyond the first "data" chunk. If we blindly ignore the length info, we'll decode that "garbage" at the end of the file. I don't know how common such files are, but we are definitely trading one problem for another here. You could actually argue that WAV/RIFF files bigger than 4 GB are illegal by definition, while files that have additional data after the first "data" chunk definitely are allowed. By definition, all "unknown" chunks are simply ignored (skipped over). So there is a reason why they made it an option.

manolito

21st February 2013, 03:07

Version 4.06 Final is build #1170. The next build I uploaded is #1197 (2012-11-24):
http://sourceforge.net/projects/lame...7.exe/download

Does that one already fail ???

Yes it does. It just pops up the following message:
"Not a debug build. Please unload debugger and try again"
Needless to say that there is no debugger running on my machine.

We really shouldn't force this behavior unless we absolutely need it, because:
If SoX simply ignores the length, i.e. it continues to reads until it stumbles upon the end of the file, it obviously cannot report progress. That's because if you have read X samples of an "unknown" length, how many percent of the whole thing you have processed? You simply cannot know until you are at 100%. Consequently this would break progress reporting in LameXP, which is a bad thing.

I'd much rather do without progress reporting than with the current behavior which is simply annoying. When I try to convert such a file LameXP just does its thing for a long time (these are large files) without any warnings. It reports that it has successfully converted the file, but when I check the output I see that the file is truncated. This is unacceptable.

Cheers
manolito

LoRd_MuldeR

21st February 2013, 03:23

Yes it does. It just pops up the following message:
"Not a debug build. Please unload debugger and try again"
Needless to say that there is no debugger running on my machine.

Now that's sounds like a completely different problem :confused:

So do you only get that issue with that specific build? Is it reproducible? And only your "old" machine or on other machines too?

Also: With which build that issue is gone and you start getting the crash you described earlier?

(BTW: I could also send you a DEBUG build of the latest version, so you might be able to figure out where exactly it crashes...)

The code that would complain about a debugger has not changed at all since 2012-03-26 :eek:

I'd much rather do without progress reporting than with the current behavior which is simply annoying. When I try to convert such a file LameXP just does its thing for a long time (these are large files) without any warnings. It reports that it has successfully converted the file, but when I check the output I see that the file is truncated. This is unacceptable.

Don't forget that you are trying to process an invalid/broken/out-of-specs Wave file. So truncation this is actually the "expected" behavior, regarding the file format specifications ;)

I'm not totally against adding hacks to process such broken files more "gracefully", but only as long as it doesn't cause any bad side effects.

As explained before, always ignoring the length, not only brakes progress reporting (probably), but also could cause other valid files to decode garbage. So it's not really a good idea.

(Best heuristic I could think of in a few minutes is passing "--ignore-length" only for files whose size exceeds 4 GB)

manolito

21st February 2013, 21:45

Now that's sounds like a completely different problem :confused:

So do you only get that issue with that specific build? Is it reproducible? And only your "old" machine or on other machines too?

Also: With which build that issue is gone and you start getting the crash you described earlier?

(BTW: I could also send you a DEBUG build of the latest version, so you might be able to figure out where exactly it crashes...)

OK, those are the results of some heavy testing...

I tried the latest Beta on my Netbook Medion Akoya E1210 (the famous Aldi Netbook), and there were no problems whatsoever. The Atom CPU supports all SSE versions, memory had been upgraded to 2 GB.

On my desktop computer (Celeron Coppermine, only MMX and SSE, 576 MB RAM) all attempts to run the 4.07 versions of LameXP failed. I uninstalled all resident AntiVirus software and made sure that no A/V service was still running. I made the software run with 256 colors, I tried to run it in safe mode, nothing helped.

Version Alpha 4 from 2012-11-24 always gave me the debug build error, and all later versions up to Beta 6 issued the "Unhandled exception handler invoked..." message. And this behavior is reproduceable each and every time.

My conclusion is that XP support in Visual Studio 2012 Update-1 is limited. It's probably not worth your time to debug this.

(Best heuristic I could think of in a few minutes is passing "--ignore-length" only for files whose size exceeds 4 GB)

Yes, I could live with that...

Cheers
manolito

LoRd_MuldeR

21st February 2013, 22:24

OK, those are the results of some heavy testing...

I tried the latest Beta on my Netbook Medion Akoya E1210 (the famous Aldi Netbook), and there were no problems whatsoever. The Atom CPU supports all SSE versions, memory had been upgraded to 2 GB.

On my desktop computer (Celeron Coppermine, only MMX and SSE, 576 MB RAM) all attempts to run the 4.07 versions of LameXP failed. I uninstalled all resident AntiVirus software and made sure that no A/V service was still running. I made the software run with 256 colors, I tried to run it in safe mode, nothing helped.

I think we need a Debug build at this point. Please stay tuned...

Version Alpha 4 from 2012-11-24 always gave me the debug build error, and all later versions up to Beta 6 issued the "Unhandled exception handler invoked..." message. And this behavior is reproduceable each and every time.

I still don't see how this can happen only with specific builds. As said before, the code in question has not changed for ages...

My conclusion is that XP support in Visual Studio 2012 Update-1 is limited. It's probably not worth your time to debug this.

It works fine on all my Windows XP systems. Also I explicitly compile the LameXP "main" program with "/arch:IA32" so it is guaranteed to run fine on systems without SSE/SSE2.

(The default has changed to "/arch:SSE2" in Visual Studio 2012, as has been the case with ICL for a long time)

LoRd_MuldeR

24th February 2013, 02:49

LameXP v4.07 Beta-7

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-02-09)
* Updated Valdec decoder to v1.4.0a (2013-02-11), based on latest AC3Filter Tools
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed Keccak library to not crash on systems without SSE/SSE2 support

LoRd_MuldeR

5th March 2013, 22:48

LameXP v4.07 Beta-9

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-02-09)
* Updated Valdec decoder to v1.4.0a (2013-02-11), based on latest AC3Filter Tools
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed Keccak library to not crash on systems without SSE/SSE2 support

LoRd_MuldeR

17th March 2013, 18:15

LameXP v4.07 Beta-10

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-03-12)
* Updated Valdec decoder to v1.4.0a (2013-03-17), based on latest AC3Filter Tools
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

mike20021969

1st April 2013, 16:01

LameXP v4.08 has been released! :)

I still remember 1st April last year ;) :D

boyumeow

5th April 2013, 04:25

I still have that last year released in my computer :p.

LoRd_MuldeR

8th April 2013, 23:51

LameXP v4.07 Beta-12

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-08)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

LoRd_MuldeR

15th April 2013, 21:18

LameXP v4.07 RC-1

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-08)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated mpg123 decoder to v1.15.3 (2013-04-03), compiled with GCC 4.8.0
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

LoRd_MuldeR

16th April 2013, 23:38

LameXP v4.07 RC-2

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-08)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated mpg123 decoder to v1.15.3 (2013-04-03), compiled with GCC 4.8.0
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed handling of certain characters when renaming output files
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

LoRd_MuldeR

19th April 2013, 21:29

LameXP v4.07 RC-3

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-18)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated mpg123 decoder to v1.15.3 (2013-04-03), compiled with GCC 4.8.0
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed handling of certain characters when renaming output files
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

LoRd_MuldeR

23rd April 2013, 23:50

LameXP v4.07 RC-4

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-23)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated mpg123 decoder to v1.15.3 (2013-04-03), compiled with GCC 4.8.0
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed handling of certain characters when renaming output files
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

LoRd_MuldeR

28th April 2013, 23:23

LameXP v4.07 has been released! :)

Changes between v4.06 and v4.07 [2013-04-28]:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-2
* Minimum supported platform now is Windows XP with Service Pack 3 (download (http://www.microsoft.com/en-us/download/details.aspx?id=24))
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Added "Up One Level" button to the output folder tab
* Added Opus decoder option to output always at the native sample rate of 48.000 Hz
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2013-04-23)
* Updated Valdec decoder (2013-04-07), based on AC3Filter Tools v1.0a
* Updated mpg123 decoder to v1.15.3 (2013-04-03), compiled with GCC 4.8.0
* Updated MediaInfo to v0.7.62 (2013-02-22), compiled with ICL 12.1.7 and MSVC 10.0
* Updated Monkey's Audio binary to v4.11 (2013-01-20)
* Updated SoX to to v14.4.1 (2012-02-09), compiled with ICL 13.0 and MSVC 10.0
* Updated GnuPG to v1.4.13, compiled with GCC 4.7.2
* Updated language files (big thank-you to all contributors !!!)
* Fixed handling of certain characters when passing meta tags on the command-line
* Fixed handling of certain characters when renaming output files
* Fixed Keccak library to not crash on systems without SSE/SSE2 support
* Fixed LAME algorithm quality selector better match the LAME documentation (link (http://lame.cvs.sourceforge.net/viewvc/lame/lame/doc/html/detailed.html#q))

Octo-puss

29th April 2013, 07:51

Yay, new version!

Feature request: could you add an option to save settings to a file instead of registry? I like to carry settings with the program.

LoRd_MuldeR

29th April 2013, 09:37

Huh, the settings always are saved to an INI file :confused:

Octo-puss

29th April 2013, 21:26

Oh? Weird... Either I am blind (very possible), or it's not in the same folder as the program itself.

LoRd_MuldeR

29th April 2013, 21:31

Of course it is not, except when you are running the "portable" edition ;)

LameXP properly supports modern operating systems, which means Windows 2000 and above. Thus it will save configuration files at the one and only correct place: %APPDATA%

(Also note: If you run LameXP in "portable" mode, it is your obligation to make sure that the folder where "LameXP.exe" resides has write permissions)

Octo-puss

1st May 2013, 18:48

Yea that makes perfect sense, however... I copied my LameXP (portable, definitely no installer) to another disk, and then to another PC, ran it, and was immediatelly greeted with accept licence screen (seriously, is the sound in there necessary??), followed by that insane yell generic sound notification. I am absolutely sure I disabled sounds before.

Also - and probably most importantly - there is no ini or any other configuration-implying file in the folder I run it from, and nor does it appear when I change some settings and run LameXP again. The settings ARE saved, though.

edit:
Of course it's what I thought it would be: c:\Users\Administrator\AppData\Local\LoRd_MuldeR\LameXP - Audio Encoder Front-End\config.ini
Keep in mind I never installed the program.

LoRd_MuldeR

1st May 2013, 20:08

How can I use LameXP as a "portable" application?
→ http://lamexp.sourceforge.net/doc/FAQ.html#9fd53558

(And in addition to that, this time I made a "special build" of LameXP that always runs in "probable" mode, on request by a user)

Octo-puss

2nd May 2013, 08:35

Thanks.

LoRd_MuldeR

2nd May 2013, 20:26

Hi MuldeR i want to thank you for this amazing program and if someday the bugs and requests stop i'll be happy if you can implement a way to save the AAC audio only files as m4a. By default the output files are mp4 and its a bit tedious to rename them, but its such a minor thing that you can safely ignore it.

Hi. You are not the first one to ask for this, but I still don't like the idea. That's because I do not like to follow Appel's attempt to force us using a non-standard file extension. And because any halfway decent player application detects the file type by reading/analyzing the file header, rather than hastily making assumptions based on the file name.

See also:
http://en.wikipedia.org/wiki/MPEG-4_Part_14#Filename_extensions