LameXP v3.18 Final, Hotfix-2 (2010-05-08)

[MatLz]

If I have an encoding in X264 with filters or an other heavy application, speed of audio encoding in the same time is very slow...
No way in the .ini with strange hierogliphic line? ;)

[LoRd_MuldeR]

If I have an encoding in X264 with filters or an other heavy application, speed of audio encoding in the same time is very slow...

The encoder processes run at BELOW_NORMAL priority class for good reason. This way they won't "steal" any processing time from other applications running on the system at the same time. You know that LameXP was designed to push the CPU load to 100% even on multi-core system. Running the encoders at NORMAL priority class (or even increased priority) would certainly cause the system to "hang" and be unresponsive. But we want LameXP to run nicely in the background while we can continue our work (Web-Browser, Office, Audio/Video Player, etc) without limitations. The current implementation ensures this! The LameXP GUI process will run at ABOVE_NORMAL priority class in order to make sure it will be responsive all the time. But that's not a problem at all, because that process won't use much CPU time (usually below 3%).

If you are running x264 at the same time, you should make sure that the x264 process runs at BELOW_NORMAL or even IDLE priority class. Any proper x264 front-end will do that!

No way in the .ini with strange hierogliphic line? ;)

Nope, it's hardcoded. You can only change it by editing source code and re-compiling. Also I wouldn't call a human-readable INI file "hieroglyphic" :D

[MatLz]

I understand. If I need speed I will do it manually in the task gestionnary but if I have lot of files...
Edit the source code?....it's like chinese language for me...
Don't worry, I have strange needs sometimes.
;)

[LoRd_MuldeR]

I understand. If I need speed I will do it manually in the task gestionnary but if I have lot of files...

Raising the priority of a process doesn't necessarily make it run "faster". That's a common myth!

Only if a lot of processes request CPU time at the same moment, so that not all processes which are ready to run can actually run on the hardware in parallel, then some processes must be suspended while others are allowed to run immediately. In that case (and only in that case) the scheduler has to decide which processes are served first and which processes have to wait. That's the only case in which process priorities are important! As long as there's only one CPU-intensive application running on the system, while the other applications are idle (more or less), the priority doesn't matter. Raising the priority of your application won't make it run any faster then. Even worse: Raising the priority of a CPU-intensive task will cause other tasks to slow down and stop responding in time! Therefore all CPU-intensive tasks should run at a lower priority than the rest. Also since most applications will run with "NORMAL" priority, it's usually better to lower the priority of CPU-intensive tasks instead of increasing the priority of all other tasks. Messing with LameXP priorities shouldn't be required at all. In your case it appears that the "problem" was caused, because the priority of the CPU-intensive x264 process wasn't lowered...

[MatLz]

Lowering the priority of CPU-intensive tasks is better than increasing the priority of all the others.
I will not forget. Thanks for your very good explanation Lord.

[SeeMoreDigital]

LoRd_MuldeR,

Is the FLAC encoder supposed to be able to generate 6Ch files from 6Ch AC3 or 6Ch WAV sources? If it is, it's not functioning :(

LameXP v3.12 Final - Audio Encoder Front-End
Written by LoRd_MuldeR <MuldeR2@GMX.de>

--------------------------------------------------------------------------

Source File: C:\Users\SeeMoreDigital\Desktop\03 Hands Clean.AC3
Output File: C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_CDD70379.wav
Commandline: "C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_38724C2F.tmp\tool_valibdec.exe" "C:\Users\SeeMoreDigital\Desktop\03 Hands Clean.AC3" -w "C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_CDD70379.wav"


0.8% Frs: 85 Err: 0 Time: 0:00.109 Level: 0 dB FPS: 779 CPU: 50.1%
73.4% Frs: 6230 Err: 0 Time: 0:05.569 Level: 0 dB FPS: 1118 CPOpening audio output PCM16 3/2.1 (5.1) 48000...
---------------------------------------
Frames/errors: 8483/0
System time: 9064ms
Process time: 8938ms
Approx. 3.30% realtime CPU usage
U: 50.1%
74.2% Frs: 6301 Err: 0 Time: 0:05.679 Level: 0 dB FPS: 1109 CPU: 49.6%
100.0% Frs: 8483 Err: 0 Time: 0:09.064 Level: 0 dB FPS: 935 CPU: 0.0%

BYTES CAPTURED: 6906
EXIT CODE: 0

--------------------------------------------------------------------------

Source File: C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_CDD70379.wav
Output File: C:\Users\SeeMoreDigital\Desktop\03 Hands Clean.flac
Commandline: "C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_38724C2F.tmp\tool_flac.exe" --compression-level-8 --tag=Title="03 Hands Clean" --tag=Comment="Encoded with LameXP" --tag=Track=1 --force --output-name="C:\Users\SeeMoreDigital\Desktop\03 Hands Clean.flac" "C:\Users\SEEMOR~1\AppData\Local\Temp\LameXP_CDD70379.wav"

flac 1.2.1, Copyright (C) 2000,2001,2002,2003,2004,2005,2006,2007 Josh Coalson
flac comes with ABSOLUTELY NO WARRANTY. This is free software, and you are
welcome to redistribute it under certain conditions. Type `flac' for details.
LameXP_CDD70379.wav: WARNING: skipping unknown sub-chunk 'JUNK' (use --keep-foreign-metadata to keep)
LameXP_CDD70379.wav: ERROR: WAVE has >2 channels but is not WAVE_FORMAT_EXTENSIBLE; cannot assign channels

BYTES CAPTURED: 453
EXIT CODE: 1



Cheers

[LoRd_MuldeR]

Well, it seems that FLAC doesn't like the Wave file written by the Valib decoder and thus falls back to Stereo mode:

ERROR: WAVE has >2 channels but is not WAVE_FORMAT_EXTENSIBLE; cannot assign channels

If you know a workaround for that, please let me know...

[SeeMoreDigital]

If you know a workaround for that, please let me know...Funny you should mention this...

If you feed LameXP with a 6Ch AAC.mp4 or 6Ch Vorbis.ogg source, it is able to generate a 6Ch FLAC encode.

[LoRd_MuldeR]

Funny you should mention this...

If you feed LameXP with a 6Ch AAC.mp4 source, it is able to generate a 6Ch FLAC encode.

Obviously the Valib decoder is to blame here. Because it doesn't output a WAVE_FORMAT_EXTENSIBLE file, but the FLAC encoder expects such a file. The AAC decoder seems to be fine.

I neither see an option for Valib decoder to produce a WAVE_FORMAT_EXTENSIBLE file nor do I see an option for FLAC to make it read the file anyway :(

[Zenitram]

Okay, somebody brought the following problem to my attention: LameXP refused to open files, if there was a "\n" sequence in the path to the file.
I was able to track this down to a bug(?) in MediaInfo.

Sorry for the delay, I was a bit busy. A Development snapshot (https://sourceforge.net/projects/mediainfo/files/zzz_Development%20snapshots/0.7.20%2B/MediaInfo_GUI_20090902_Windows_i386_WithoutInstaller.7z/download) corrects it (the DLL is in the archive).
An official version will be released on Friday.

[LoRd_MuldeR]

LameXP v3.12 Hotfix-1 :)

Changes between v3.11 and v3.12:
* Added support for FLAC (Free Lossless Audio Codec) output
* Added progress display for individual files (for the "encoding" step only)
* Added a SSE2 (Pentium 4) build of the Ogg Vorbis encoder that will be used if supported by the CPU
* Added options to override the Nero AAC profile (be aware: it's not recommended to do that!)
* Added an option to analyze media files (powered by MediaInfo™)
* Added experimental support for Windows 7 taskbar progress indicator and overlay icons
* Updated LAME encoder to v3.98.2 (2009-09-05), compiled with ICL 11.0
* Updated MediaInfo to v0.7.21 (2009-09-04), using statically linked build
* Updated mpg123 decoder to v1.9.0 (2009-08-14)
* Updated Speex decoder to v1.2 RC-1 (2009-07-04)
* Updated AC3Filter Tools to v0.3a (2009-08-04)
* Updated language files (big "thank you" to all contributors !!!)
* Updated Auto-Update tool, from now on only signed updates will be accepted (using GnuPG)
* Fixed a number of minor glitches

I removed the workaround for the MediaInfo line-break bug, because that bug is fixed now. Thanks to Zenitram!
Also LAME v3.98.2 has been re-built with ICL 11.0. Thanks to John33 from Rarewares.org for providing the fresh build.
Last but not least I disabled the language detection code discussed here (http://forum.doom9.org/showthread.php?p=1317991#post1317991). Hope people are satisfied with that ^^

[Zenitram]

* Added an option to analyze media files (powered by MediaInfo™)

You're becoming a MediaInfo addict... ;-)

[LoRd_MuldeR]

You're becoming a MediaInfo addict... ;-)

I added that feature, because this way it's much easier to get people to send me useful information about files that won't convert properly :D

[Octo-puss]

[B]Also LAME v3.98.2 has been re-built with ICL 11.0.
What does this mean for us users? :) If anything. The encoding is a bit faster maybe?

[LoRd_MuldeR]

What does this mean for us users? :) If anything. The encoding is a bit faster maybe?

There should be no difference for the user. It may be slightly faster, but that's it.

[LoRd_MuldeR]

LameXP v3.12 Hotfix-2 :)

Changes between v3.11 and v3.12:
* Added support for FLAC (Free Lossless Audio Codec) output
* Added progress display for individual files (for the "encoding" step only)
* Added a SSE2 (Pentium 4) build of the Ogg Vorbis encoder that will be used if supported by the CPU
* Added options to override the Nero AAC profile (be aware: it's not recommended to do that!)
* Added an option to analyze media files (powered by MediaInfo™)
* Added experimental support for Windows 7 taskbar progress indicator and overlay icons
* Updated LAME encoder to v3.98.2 (2009-09-05), compiled with ICL 11.0
* Updated MediaInfo to v0.7.21 (2009-09-04), using statically linked build
* Updated mpg123 decoder to v1.9.0 (2009-08-14)
* Updated Speex decoder to v1.2 RC-1 (2009-07-04)
* Updated AC3Filter Tools to v0.3a (2009-08-04)
* Updated language files (big "thank you" to all contributors !!!)
* Updated Auto-Update tool, from now on only signed updates will be accepted (using GnuPG)
* Fixed a number of minor glitches

LAME v3.98.2 has been re-built with ICL 11.0 once again. This time the build should run on CPU's without SSE2 support too!
Thanks to Taurus on German Doom9 for reporting the issue. And many thanks to John33 from Rarewares.org for providing yet another build.
(Note that the LAME bundle downloads on Rarewares.org have been updated silently)

[LoRd_MuldeR]

LameXP v3.12 Hotfix-3 :)

Changes between v3.11 and v3.12:
* Added support for FLAC (Free Lossless Audio Codec) output
* Added progress display for individual files (for the "encoding" step only)
* Added a SSE2 (Pentium 4) build of the Ogg Vorbis encoder that will be used if supported by the CPU
* Added options to override the Nero AAC profile (be aware: it's not recommended to do that!)
* Added an option to analyze media files (powered by MediaInfo™)
* Added experimental support for Windows 7 taskbar progress indicator and overlay icons
* Updated LAME encoder to v3.98.2 (2009-09-05), compiled with ICL 11.0
* Updated MediaInfo to v0.7.21 (2009-09-04), using statically linked build
* Updated mpg123 decoder to v1.9.0 (2009-08-14)
* Updated Speex decoder to v1.2 RC-1 (2009-07-04)
* Updated AC3Filter Tools to v0.3a (2009-08-04)
* Updated language files (big "thank you" to all contributors !!!)
* Updated Auto-Update tool, from now on only signed updates will be accepted (using GnuPG)
* Fixed a number of minor glitches

Now the FLAC binary has been replaced with an ICL 11.1 build that should run on Non-SSE2 CPU's too. The previous FLAC build did not.

[SeeMoreDigital]

Marvellous work...

I guess the only major encoder that would be worth including now is AC3..... Did I say that out loud?

[LoRd_MuldeR]

Marvellous work...

I guess the only major encoder that would be worth including now is AC3..... Did I say that out loud?

Well, there is Aften. So this isn't too unrealistic. Will have a look when I have more time.

There's also still the WAVE_FORMAT_EXTENSIBLE problem outstanding with the Valib AC3/DTS decoder :rolleyes:

(BTW: At my university "SMD" refers to a Christian organization for evangelizing students ^^)

[SeeMoreDigital]

There's also still the WAVE_FORMAT_EXTENSIBLE problem outstanding with the Valib AC3/DTS decoder :rolleyes:Bummer!

(BTW: At my university "SMD" refers to a Christian organization for evangelizing students ^^) What a waste...

[MatLz]

Maybe stupid question again...
Is it possible to add an Avisynth input support in LameXP? LameXP needs 'real' files for food?

[LoRd_MuldeR]

Maybe stupid question again...
Is it possible to add an Avisynth input support in LameXP? LameXP needs 'real' files for food?

Maybe possible somehow. But not supported yet. And certainly not on my priority list currently ;)

(Since LameXP decodes any input to uncompressed Wave files first, we'd need a tool that can dump the input AVS script to an uncompressed Wave file)

[MatLz]

Maybe possible somehow. But not supported yet. And certainly not on my priority list currently ;)

(Since LameXP decodes any input to uncompressed Wave files first, we'd need a tool that can dump the input AVS script to an uncompressed Wave file)

No problem, I can wait.;)
For ponctual and particular needs I can use Nicaudio+Bepipe.

[LoRd_MuldeR]

Is the FLAC encoder supposed to be able to generate 6Ch files from 6Ch AC3 or 6Ch WAV sources? If it is, it's not functioning :(

there's also still the WAVE_FORMAT_EXTENSIBLE problem outstanding with the valib ac3/dts decoder
bummer!

It turned out that this was a bug in the Valib decoder from AC3Filter Tools:

It's a bug. It should create WAVE_FORMAT_EXTENSIBLE in this case. Thanks for the report.

The problem has been fixed. So expect a new LamXP release soon...

[SeeMoreDigital]

It turned out that this was a bug in the Valib decoder from AC3Filter Tools:

The problem has been fixed. So expect a new LameXP release soon...Hey, that's great news...

This fix means LameXP will become the only audio encoder I'll ever need to use :D

[LoRd_MuldeR]

LameXP v3.12 Hotfix-4 :)

Changes between v3.11 and v3.12:
* Added support for FLAC (Free Lossless Audio Codec) output
* Added progress display for individual files (for the "encoding" step only)
* Added a SSE2 (Pentium 4) build of the Ogg Vorbis encoder that will be used if supported by the CPU
* Added options to override the Nero AAC profile (be aware: it's not recommended to do that!)
* Added an option to analyze media files (powered by MediaInfo™)
* Added experimental support for Windows 7 taskbar progress indicator and overlay icons
* Updated LAME encoder to v3.98.2 (2009-09-05), compiled with ICL 11.0
* Updated MediaInfo to v0.7.21 (2009-09-04), using statically linked build
* Updated mpg123 decoder to v1.9.0 (2009-08-14)
* Updated Speex decoder to v1.2 RC-1 (2009-07-04)
* Updated AC3Filter Tools to v0.3b (2009-09-19)
* Updated language files (big "thank you" to all contributors !!!)
* Updated Auto-Update tool, from now on only signed updates will be accepted (using GnuPG)
* Fixed a number of minor glitches

I replaced the Valib decoder v0.3b with a fixed build that properly creates WAVE_FORMAT_EXTENSIBLE wave files when decoding multi-channel AC3 sources.
This should fix multi-channel AC3 to FLAC conversion. Thanks to SeeMoreDigital for bringing the issue to my attention and to Valex (AC3Filter project) for fixing the bug!

[LoRd_MuldeR]

LameXP v3.13 Beta-1 :)

Changes between v3.12 and v3.13:
* Updated LAME encoder to v3.98.2 (2009-09-26), compiled with ICL 11.1.046
* Updated MediaInfo to v0.7.22 (2009-09-25), using statically linked build (MSVC 9.0)
* Updated language files (big "thank you" to all contributors !!!)

This should fix a bug of the ICL 11.1 which caused LAME to hang on some Windows 7 systems.
I never encountered that problem on my Windows 7 system, but here is the update anyway.
The latest FLAC builds potentially suffer from the problem, so expect another quick update soon.

See also:
http://forum.doom9.org/showpost.php?p=1328818&postcount=8105

[LoRd_MuldeR]

LameXP v3.13 Beta-2 :)

Changes between v3.12 and v3.13:
* Updated LAME encoder to v3.98.2 (2009-09-26), compiled with ICL 11.1.046
* Updated FLAC encoder to v1.2.1b (2009-10-01), compiled with ICL 11.1.046
* Updated MediaInfo to v0.7.22 (2009-09-25), using statically linked build (MSVC 9.0)
* Updated language files (big "thank you" to all contributors !!!)

Now the FLAC encoder/decoder has been re-compiled with with ICL 11.1.046 too. Should fix a potential hang/crash on Windows 7.

See also:
http://forum.doom9.org/showpost.php?p=1328818&postcount=8105

[mr soft]

Thanks

That growl got me , I was wearing the earphones. :D

[LoRd_MuldeR]

Thanks

That growl got me , I was wearing the earphones. :D

Take this:
https://opensvn.csie.org/traccgi/mulder1984/changeset/361/

[LoRd_MuldeR]

LameXP v3.13 Beta-3 :)

Changes between v3.12 and v3.13:
* Updated LAME encoder to v3.98.2 (2009-09-26), compiled with ICL 11.1.046
* Updated FLAC encoder to v1.2.1b (2009-10-01), compiled with ICL 11.1.046
* Updated MediaInfo to v0.7.22 (2009-09-25), using statically linked build (MSVC 9.0)
* Updated language files (big "thank you" to all contributors !!!)
* Updated the Splash screen and modified the sound that plays on very first launch

[MatLz]

Hi Lord. Not yet downloaded the new release...but...you have remove your SCRRREAM??

[LoRd_MuldeR]

Hi Lord. Not yet downloaded the new release...but...you have remove your SCRRREAM??

Uhm, if mean the sound on the "About" screen: No, I did not remove it. Beat me for that :p

But this sound won't play when you run the application for the very first time. Now a system-specific sound will be played...

(Took me quite some time to locate Window 7's system startup sound in "imageres.dll" ^^)

[MatLz]

Certainly the best update since long time ago!...
What?...a joke?..of course!:)

I don't know W7 nor Vista...I'm a XP addict.
Now they put their sounds in dll??

[LoRd_MuldeR]

I don't know W7 nor Vista...I'm a XP addict.
Now they put their sounds in dll??

Nope. But they made it impossible the change the "system startup" sound in the control panel. All the other sounds can still be changed.

Also there still is a "Windows Startup.wav" file in the "Windows\media" folder, but that one contains only a one second "click" sound. It's obviously a dummy file ;)

After some research using good old ResourceHacker, I found the actual startup sound in the resource section of the DLL file mentioned before.

It appears Microsoft really doesn't want us to be able to edit the Windows 7 startup sound. Playing the sound from the DLL's resource is no problem though :D

[MatLz]

Wave:5080:1033 no? With reshack it seems it's easy to change that.
(Hope Bill doesn't see this thread...;))

[LoRd_MuldeR]

Wave:5080:1033 no? With reshack it seems it's easy to change that.
(Hope Bill doesn't see this thread...;))

You can't modify or replace Windows system files, at least not easily. On Windows 7 even the "Administrator" doesn't have full access. Only the "Trusted Installer" can change system files.
http://en.wikipedia.org/wiki/Windows_Resource_Protection

That's not really new. Windows XP has a similar method to protect your system files. It works differently though...

[MatLz]

We need 'the full power', modify the propriatary and give him the total control in the properties...
Well it's beyond my understanding....we pay $$$ for an exploitation system which normally give us the possibility to have a 'Personnal Computer', and it's the cross and the flag to change a simple sound...

[LoRd_MuldeR]

We need 'the full power', modify the propriatary and give him the total control in the properties...
Well it's beyond my understanding....we pay $$$ for an exploitation system which normally give us the possibility to have a 'Personnal Computer', and it's the cross and the flag to change a simple sound...

It's generally a good idea to protect system files against modification! Malware modifying system files to hide itself is probably the worst case :eek:

And if he really needs to, the Administrator can still take ownership of the "protected" file to modify/replace it. Needless to say that you must be very careful with that!

Why they made the startup sound a "protected" resource isn't clear to me. But there really are more serious things to worry about...

[MatLz]

I agree for critical files or actions....but a protection for a startup sound? I think it's too much to have do that, or change the old method which worked nice! People bielieve they have the wonderfull lastest thing under their hand, but they're wrong. In lot of cases the world is in regression, it's 'I give you a little something, I take you more liberty'.
Well...sorry to disturb your thread with that!
Maybe moderators will not like...so...what next in LameXP?

[LoRd_MuldeR]

No big plans currently. Time to get prepared for the next semester ;)

[MatLz]

The most important relative variable is time! And you must live before all. So, to release the LameXP264encoder, take your time!

[lucassp]

Hi,

Could someone please tell me how to enable HEAAC v2? Thanks!

[LoRd_MuldeR]

Hi,

Could someone please tell me how to enable HEAAC v2? Thanks!

You don't "enable" HE-AAC v2. That mode is especially designed for ultra-low bitrates and will hurt quality at medium/high bitrates.

The Nero AAC encoder will choose the suitable encoding mode, depending on the select bitrate (or quality). Iff suitable for the selected bitrate, it will use HE-AAC v2.

Anyway, you can enforce the HE-AAC v2 profile in LameXP's advanced options. This is not recommended at all! But it's up to you ;)

[SeeMoreDigital]

Hi,

Could someone please tell me how to enable HEAAC v2? Thanks!From the "Advanced Options" go to "Nero AAC Profile Override" and select "Enforce HE-AAC v2 Profile": -

http://i35.tinypic.com/2sbldus.png


Cheers

[lucassp]

Thanks guys!

I'm encoding at 48kbps. Should this bitrate enforce HEAAC v2 by default?

[LoRd_MuldeR]

Thanks guys!

I'm encoding at 48kbps. Should this bitrate enforce HEAAC v2 by default?

If 48 kbps doesn't use HE-AAC v2 with default settings ("Auto"), then obviously the Nero engineers have decided that HE-AAC v2 isn't preferable for that bitrate (and number of channels).

And if it is used, then you don't need to enforce HE-AAC v2 explicitly, because it's already used with default settings ;)

Please note: HE-AAC v1 = LC-AAC + Spectral Band Replication (http://en.wikipedia.org/wiki/Spectral_band_replication), HE-AAC v2 = LC-AAC + Spectral Band Replication + Parametric Stereo (http://en.wikipedia.org/wiki/Parametric_Stereo)

[black64er]

1. Every time when lameXP is started hi want to update it's self. Where is option that I forbid to do that and to never ask me again.

2. After a task is finished. You play me that sound over and over. And, I guess you'l never realise and now i must tell ya, if is to many files to be converted, task can last awhile, and man works other things while wait to finish your prg. Then what is hapenning? TADADTATYDUAUA I'm finish (playing stupid sound) says LameXP and get me hart atack every time I use it. That is a real pain for my ears!

3. Suppose I click About... option. And You do something stupid again. at my ears! with that terrible loud sample!!!

So, growup and change this 3 thing, please!

[LoRd_MuldeR]

1. Every time when lameXP is started hi want to update it's self. Where is option that I forbid to do that and to never ask me again.

2. After a task is finished. You play me that sound over and over. And, I guess you'l never realise and now i must tell ya, if is to many files to be converted, task can last awhile, and man works other things while wait to finish your prg. Then what is hapenning? TADADTATYDUAUA I'm finish (playing stupid sound) says LameXP and get me hart atack every time I use it. That is a real pain for my ears!

3. Suppose I click About... option. And You do something stupid again. at my ears! with that terrible loud sample!!!

So, growup and change this 3 thing, please!

Obviously you didn't even look at the application's advanced options (http://img291.imageshack.us/img291/5671/balloontooltipwl4.png) menu :rolleyes: :rolleyes: :rolleyes:

Also your way of complaining about a software that was given to you for free is absolutely unacceptable. Remember: I don't owe you anything!

If you have any feature requests, ask kindly and it may be implemented. But this way, no chance ;)

Oh, and expect a strike for your Rule #4 (http://forum.doom9.org/forum-rules.htm) violation very soon. Your PM has already been forwarded to the moderator team...

[black64er]

Obviously you didn't even look at the applications options menu :rolleyes: :rolleyes: :rolleyes:

Oh, and expect a strike for your Rule #4 (http://forum.doom9.org/forum-rules.htm) violation soon...

Well, You are right. All is there (options menu with right click button) - but I see them just now when you said that there's.

Sorry if I been rude, but, as I said - I get heart attack every time I use lameXP :)

[LoRd_MuldeR]

LameXP v3.13 Final :)

Changes between v3.12 and v3.13:
* Updated LAME encoder to v3.98.2 (2009-09-26), compiled with ICL 11.1.046
* Updated FLAC encoder to v1.2.1b (2009-10-01), compiled with ICL 11.1.046
* Updated MediaInfo to v0.7.22 (2009-09-25), using statically linked build (MSVC 9.0)
* Updated AC3Filter Tools to v0.31b (2009-10-01)
* Updated TAK decoder to v1.1.2 (2009-07-27)
* Updated mpg123 decoder to v1.9.1 (2009-10-09)
* Updated language files (big "thank you" to all contributors !!!)
* Updated the Splash screen and modified the sound that plays on very first launch
* Updated JEDI-VCL from v3.34 to v3.38 (2009-08-27)

[SeeMoreDigital]

LameXP v3.13 Final :)Many thanks mate :)

Great work as usual and kindly appreciated :)

[tipsypenguin]

Thanks LoRd_MuldeR

[LoRd_MuldeR]

LameXP v3.13 Final R2 :)

Changes between v3.12 and v3.13:
* Updated LAME encoder to v3.98.2 (2009-09-26), compiled with ICL 11.1.046
* Updated FLAC encoder to v1.2.1b (2009-10-01), compiled with ICL 11.1.046
* Updated MediaInfo to v0.7.23 (2009-10-16), using statically linked build (MSVC 9.0)
* Updated AC3Filter Tools to v0.31b (2009-10-01)
* Updated TAK decoder to v1.1.2 (2009-07-27)
* Updated mpg123 decoder to v1.9.1 (2009-10-09)
* Updated language files (big "thank you" to all contributors !!!)
* Updated the Splash screen and modified the sound that plays on very first launch
* Updated JEDI-VCL from v3.34 to v3.38 (2009-08-27)
* Updated GnuPG to v1.4.10 (2009-09-02)

Also fixed a minor bug with playing Windows system sounds (environment variables that may appear in the path to the sound file weren't expanded).

[olnima]

Is there any option to encode titles of / a whole CD without saving them to .wav first?

Thanks for your application,
Olnima

[LoRd_MuldeR]

No. There is no feature to rip tracks directly from Audio-CD in LameXP.

[olnima]

...maybe something for a boring november-weekend... :)

[LoRd_MuldeR]

...maybe something for a boring november-weekend... :)

Implementing a CD ripper would take me much more than just a weekend, I guess ;)

Also the chance for a "boring" weekend is extremely small this November, as I'm busy working on my thesis now :D

Last but not least I think that functionality is outside the scope of LameXP.

[Octo-puss]

For ripping the tracks, every sane person uses Exact Audio Copy.

[Karkas]

Sorry if this is a retarded, but I can't seem to figure out how to append/combine multiple mp3 files into 1 with this utility. I'm sure it is possible, but I am just overlooking something simple.

I don't really want to re-encode them, just combine.

I've searched around and can't find out how anywhere. If it isn't possible can you recommend something else? I don't trust the google'd garbage software.

Thanks

[MatLz]

Hi Karkas, LameXP is a nice and powerfull interface for encoding, it's not an editor.
Try mp3directcut for your need, with it you can join mp3 without recode them.

[LoRd_MuldeR]

Sorry if this is a retarded, but I can't seem to figure out how to append/combine multiple mp3 files into 1 with this utility. I'm sure it is possible, but I am just overlooking something simple.

No, it's not possible. You are using the wrong tool for what you try to achieve. Use Audacity, if you need a nice audio editor ;)
http://audacity.sourceforge.net/

[Karkas]

Thanks guys
:thanks:

[LoRd_MuldeR]

LameXP v3.14, Beta-5:
http://www.mediafire.com/file/nnnqymfzt2j/LameXP.2009-11-22.Beta-5c.zip (Mirror 1 (http://dl.dropbox.com/u/3191920/LameXP/LameXP.2009-11-22.Beta-5c.zip)) (Mirror 2 (http://ul.to/dtmcsa))

Changes between v3.13 and v3.14:
* Added Suspend and Resume buttons to the processing window
* Added another language: Spanish/Castlian (Spanish from Spain)
* Updated MediaInfo to v0.7.25 (2009-11-13), compiled with ICL 11.1.046
* Updated language files (big "thank you" to all contributors !!!)
* Fixed a number of minor glitches

Note: There's a new "SilentMode" mode now (available only from the INI file), which will suppress all messages boxes that don't require an explicit answer.

[digitaltoast]

Hi there; it's a great app, but I feel you should definitely get rid of that gigantic huge burping noise on the "about" screen.
I can't persuade someone to use it because of this!

[LoRd_MuldeR]

Hi there; it's a great app, but I feel you should definitely get rid of that gigantic huge burping noise on the "about" screen.

Sorry, but:
http://www.youtube.com/watch?v=bjEW7Y1Xbdo :D

(In English: "A bit of fun must be allowed")

I can't persuade someone to use it because of this!

Too bad. Imagine all the paying customers I loose :p

[digitaltoast]

Sorry, but:
http://www.youtube.com/watch?v=bjEW7Y1Xbdo :D
(In English: "A bit of fun must be allowed")
Too bad. Imagine all the paying customers I loose :p
Oh dear, now I feel bad. I use a lot of your applications, I think they are great. This app too is great, but if you want it to be perfect, just take the huge belching sound off.
That is all. No other criticism. I love this app and use it everyday.

[LoRd_MuldeR]

Oh dear, now I feel bad. I use a lot of your applications, I think they are great. This app too is great, but if you want it to be perfect, just take the huge belching sound off.

Do I hear some sarcasm here? :D

Really, I won't remove that sound from the official version. You can always turn off all sounds (including Uuaarrgh! (http://www.youtube.com/watch?v=frZWAdmUUD4&) sound) in the options. So if you dislike it so much, simply turn the sound off.

Last but not least, this is free software (http://en.wikipedia.org/wiki/Free_software). You can modify it according to your personal needs/preferences, e.g. you can add or remove whatever sounds you want ;)

[MatLz]

Hi my Lord, thx for your releases!...you've work a lot last days!...ha yes and big THX for the new links!(you know why...).

[LoRd_MuldeR]

LameXP v3.14, RC-3:
http://dl.dropbox.com/u/3191920/LameXP/LameXP.2009-11-29.RC-3.zip

Changes between v3.13 and v3.14:
* Added Suspend and Resume buttons to the processing window
* Added another language: Castilian Spanish (Spanish from north/central Spain)
* Updated MediaInfo to v0.7.25 (2009-11-13), compiled with ICL 11.1.046
* Updated mpg123 decoder to v1.9.2 (2009-11-20)
* Updated language files (big "thank you" to all contributors !!!)
* Updated JEDI-VCL from v3.38 to v3.39 (2009-11-05)
* Various minor fixes and improvements

[LoRd_MuldeR]

LameXP v3.14, Final :)

Changes between v3.13 and v3.14:
* Added Suspend and Resume buttons to the processing window
* Added another language: Castilian Spanish (Spanish from north/central Spain)
* Updated mpg123 decoder to v1.9.2 (2009-11-20)
* Updated MediaInfo to v0.7.25 (2009-11-13), compiled with ICL 11.1.046
* Updated AC3Filter Tools to v0.31b (2009-10-01), compiled with ICL 11.1.046
* Updated language files (big "thank you" to all contributors !!!)
* Updated JEDI-VCL from v3.38 to v3.39 (2009-11-05)
* Various minor fixes and improvements

[~bT~]

thank you me lord! :)

[kool]

is this meant for XP or any OS ? :p

[LoRd_MuldeR]

is this meant for XP or any OS ? :p

Initially LameXP was developed on Windows XP, but it is developed on Windows 7 now. There even are some Windows 7 specific features ;)

I assume it works on Windows Vista and on Windows 2000 as well, but I have no such test system. It does work under Linux/Wine though, tested with Ubuntu 9.04.

Legacy Windows systems (Windows 95, 98 and ME) are no longer supported. The number of users with such archaic OS is negligible.

Results of OS poll:
http://mulder.dummwiedeutsch.de/pub/poll/Poll_OS_2009.pdf

[kool]

Thank You

[LoRd_MuldeR]

LameXP v3.15, Alpha-2
http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2009-12-18.Alpha-2.zip

Nothing new since the last release yet. But I updated both, mpg123 and MediaInfo, to the latest versions.

[otmax]

Hi! My English is horrible, please excuse me.
LameXP is a great tool, but we are always have "but" :) I have two requests:
The first and the main: Please, add support to transfer tag's from source files. Just save them as is.
Second, if it's easy: an option to create several files from one (for example, from FLAC, which contains full album). With adding proper tag's, of course ;-)

[LoRd_MuldeR]

The first and the main: Please, add support to transfer tag's from source files. Just save them as is.

That's how LameXP works. Doesn't it?

Second, if it's easy: an option to create several files from one (for example, from FLAC, which contains full album). With adding proper tag's, of course ;-)

LameXP is a converter, not an editor. If you need to cut a long track into several shorter tracks, use an audio editor, such as Audacity.

[otmax]

That's how LameXP works. Doesn't it?
It doesn't. When option "Write metadata to files" switched ON, LameXP getting tags from fields, that was filled by user. When this option switched OFF, result tags are clear. I've tested by converting 3 files with metadata (.ape, .ogg, .mp3) to .ogg.


LameXP is a converter, not an editor. If you need to cut a long track into several shorter tracks, use an audio editor, such as Audacity.
I'm dont say about editing. Just generate tracks automatically, when source file is an album. For example, .ape or .ogg with information about tracks, which are contained in file.
Optionally, of course.

[LoRd_MuldeR]

It doesn't. When option "Write metadata to files" switched ON, LameXP getting tags from fields, that was filled by user. When this option switched OFF, result tags are clear. I've tested by converting 3 files with metadata (.ape, .ogg, .mp3) to .ogg.

That's exactly how it is intended!

If you overwrite the tags manually, it will use your tags, of course. The tags detected from the source files are only used, when you leave the corresponding field empty ;)

And of course turning the meta tag writing off does what one would expect. It doesn't write any meta tags...

I'm dont say about editing. Just generate tracks automatically, when source file is an album. For example, .ape or .ogg with information about tracks, which are contained in file.
Optionally, of course.

Splitting a file into several tracks is editing. At least from my point of view. It currently doesn't fit into the concept of LameXP :rolleyes:

[LoRd_MuldeR]

LameXP v3.15 Xmas-Edition:

Changes between v3.14 and v3.15:
* Added support for Nero AAC encoder v1.5.1.0
* Updated mpg123 decoder to v1.10.0 (2009-12-05)
* Updated MediaInfo to v0.7.26 (2009-12-18), compiled with ICL 11.1.051
* Updated AC3Filter Tools to v0.31b (2009-10-01), compiled with ICL 11.1.051

http://fc04.deviantart.net/fs23/f/2007/346/1/5/Santa_hat_Emoticon_by_CheddarMan.png

[~bT~]

Thank you LoRd_MuldeR! A belated merry xmas and hope u have a fantastic new year! Thanks for all the updates this year and here's hoping there are many more to come next year ;)

[LoRd_MuldeR]

LameXP v3.16 Alpha-2:
http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2010-01-07.Alpha-2.zip

Changes between v3.15 and v3.16:
* Updated WavPack decoder to v4.60.1 (2009-11-29)
* Updated MediaInfo to v0.7.27 (2010-01-04), compiled with ICL 11.1.054
* Updated GnuPG to v1.4.10b (2009-09-03), compiled with GCC 4.2.1

[fripp21]

Hi. Seems to be a great app!

I had some problems though. The app did not start after installation. I dl-ed the v3.16 alpha-2.

Have Windows 7 (64 bits). Is the app supposed to work on this set-up?

Thanks in advance.

[LoRd_MuldeR]

I had some problems though. The app did not start after installation. I dl-ed the v3.16 alpha-2.

Some more info please. "The app did not start" isn't a very helpful error description. What exactly did happen?

Have Windows 7 (64 bits). Is the app supposed to work on this set-up?

My main development machine has Windows 7 (64-Bit) installed ;)

[fripp21]

Oh, thanks - quick reply.

Well, I installed the app. Seemed to be ok. But when I started it the first time it "freezed", the icon came up on screen but the application "did not respond". I had to right-click and end the application. I have uninstalled it now. Maybe try again?

Do I have to reboot after installation?

I have successfully installed and tried both "Avidemux 2.5" and "SMPLayer". Very nice applications!

Thanks.

[LoRd_MuldeR]

Well, sometimes Windows "thinks" that the application does not respond while it's busy, for example when LameXP is starting up ("splash screen").

In Windows 7 (maybe also Vista, never used it) there is a new dialog that will pop up if an applications doesn't respond immediately, which looks like a "crash" dialog.

But it's not a crash! Simply wait until LameXP has initialized. And don't try to "click away" the spalsh screen, as that won't work.

Side note: I have noticed that A/V software can slow don't the start of LameXP significantly. Especially the "file activity" scanner of M$ Security Essentials :rolleyes:

[fripp21]

Ok, thanks. That make sence. I'll install it again and let the first start-up take it's time.

I'll let you know later.

Thanks again!

[Motenai Yoda ^.^]

Great application!

but with v3.15 Xmas using Lame Algorithm Quality on Maximum Quality or High Quality , with vbr quality to 4 do the same commandline? (-q0)
also is possible use the .m4a extension for nero aac files instead of .mp4?

ps a feature request, an "on the fly encoding" option for lame encoding if normalizzation is turned off...

sorry for my english

[LoRd_MuldeR]

but with v3.15 Xmas using Lame Algorithm Quality on Maximum Quality or High Quality , with vbr quality to 4 do the same commandline? (-q0)

Huh? If you use Quality (VBR) compression mode, then then the "Quality/Bitrate" slider controls the "-V" option of LAME. That's a Filesize -vs- Quality option.

The "Lame Algorithm Quality" slider controls the "-q" option of LAME. That's a Speed -vs- Quality option and it applies to all compression modes...

also is possible use the .m4a extension for nero aac files instead of .mp4?

Possible indeed ;)

But the one and only "correct" (regarding the MPEG-4 Standard) file extension for MP4 files is ".mp4", so that's what LameXP will continue to use.

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

ps a feature request, an "on the fly encoding" option for lame encoding if normalizzation is turned off...

What is "on the fly" encoding supposed to mean?

If you don't use any filters (currently there's only Normalization) and if your source is uncompressed Wave-Audio (PCM), then the source file will be fed directly into LAME.

But if your source is something different from uncompressed Wave, we must decode the source first. There's no other way!

I know that LAME can also accept MP3 files as input directly. But there are many formats that LameXP supports as input, but LAME doesn't accept.

Furthermore there are many encoders supported by LameXP that don't accept MP3 files as input. Decompressing everything to PCM Wave Audio first is the best solution!

(BTW: With N encoders and M audio formats, there are NxM possible combination. And I certainly won't implement special paths for each combination ^^)

[Motenai Yoda ^.^]

The "Lame Algorithm Quality" slider controls the "-q" option of LAME. That's a Speed -vs- Quality option and it applies to all compression modes...together modes use -q0, I think -q0 for Maximum and -q2 for High.

I ustat only with -V 4 so i don't know if there are switch for regarding a better quality on middle/low bitrate and vbr modes.

But the one and only "correct" (regarding the MPEG-4 Standard) file extension for MP4 files is ".mp4", so that's what LameXP will continue to use. yes I know, but my personal portable player don't would play a .mp4 file.

But if your source is something different from uncompressed Wave, we must decode the source first. There's no other way... a pipeling can be used to connect decoder to encoder without that a wav file is needed to write.

[LoRd_MuldeR]

together modes use -q0, I think -q0 for Maximum and -q2 for High.

I ustat only with -V 4 so i don't know if there are switch for regarding a better quality on middle/low bitrate and vbr modes.

I don't get your point. The "-V" and "-q" options are two independent options.

While "-V" controls Quality -vs- Bitrate for VBR mode, the "-q" option controls Quality -vs Speed for all modes.

And that's exactly how it is used in LameXP.

yes I know, but my personal portable player don't would play a .mp4 file.

Don't ask me to implement workarounds for bugs in your player.

Instead ask your manufacturer to fix that serious bug in the player (via Firmware update). And if they don't provide a fix in time, return the broken device to the shop.

(If I allow ".m4a" output, tomorrow the next user will ask for ".xyz", because his player "requires" yet another weird/wrong extension)

a pipeling can be used to connect decoder to encoder without that a wav file is needed to write.

I know how pipes work ;)

But not all encoders used by LameXP can read input from STDIN. And not all decoders used by LameXP can write output to STDOUT.

As said before, with N decoders and M encoders, I cannot implement special paths for each of the NxM combinations!

And another issue: If an encoder reads the input from STDIN, it (usually) doesn't know the length of the input and thus cannot display progress information.

After all, using temporary intermediate files is the most feasible solution for me. I'm not planning to change that...

[Motenai Yoda ^.^]

I don't get your point. The "-V" and "-q" options are two independent options.

While "-V" controls Quality -vs- Bitrate for VBR mode, the "-q" option controls Quality -vs Speed for all modes.

And that's exactly how it is used in LameXP.

forget -V and vbr.

I would tell u "With 3.15 using "Lame Algorithm Quality" on "Maximum Quality" or "High Quality" use -q0. "High Quality" should use -q2 or -h, isn't?"

[LoRd_MuldeR]

Sorry, I still don't get your point. The "-q" option isn't related to VBR mode, nor is it related to ABR mode.

It's simply a "Quality -vs- Speed" option for LAME in general and thus applies to all encoding mode (VBR, ABR and CBR) in the same way.

Furthermore "-h" is simply an alias for "-q 2". So if you set "-q" explicitly (which LameXP does), then "-h" is superfluous!

In LameXP the user can control "-V" (for VBR mode) and "-q" (for all modes) independently. And LameXP's default is "-q 2" aka "-h".

And setting "Lame Algorithm Quality" to "High Quality (Recommended)" will indeed pass the "-q 2" paramter to LAME.

[LoRd_MuldeR]

LameXP v3.16 Alpha-3:
http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2010-01-11.Alpha-3.zip

Changes between v3.15 and v3.16:
* Added support for Nero AAC encoder v1.5.3.0 (2009-12-29)
* Updated WavPack decoder to v4.60.1 (2009-11-29)
* Updated MediaInfo to v0.7.27 (2010-01-04), compiled with ICL 11.1.054
* Updated GnuPG to v1.4.10b (2009-09-03), compiled with GCC 4.2.1

Please note that the Nero AAC encoder v1.5.3.0 can be obtained by re-downloading the v1.5.1.0 package from the Nero web-site!

[LoRd_MuldeR]

LameXP v3.16 Final :)

Changes between v3.15 and v3.16:
* Added support for Nero AAC encoder v1.5.3.0 (2009-12-29)
* Disable DPI warning on Vista and later, as they handle DPI != 96 much better than WinXP
* Updated WavPack decoder to v4.60.1 (2009-11-29)
* Updated MediaInfo to v0.7.27 (2010-01-04), compiled with ICL 11.1.054
* Updated GnuPG to v1.4.10b (2009-09-03), compiled with GCC 4.2.1

[mr soft]

Disable DPI warning on Vista and later, as they handle DPI != 96 much better than WinXP

Big :thanks: as usual, especially for this ^ It was diving me nuts.

LameXP v3.16 Final
Is it ever really the end. :devil:

[LoRd_MuldeR]

Big :thanks: as usual, especially for this ^ It was diving me nuts.

Sorry, I hadn't noticed that Vista & Win7 finally handle scaling for non-standard DPI's much better. WinXP always destroyed the layout with Non-96 DPI. Thus the warning :rolleyes:

http://i47.tinypic.com/2v85pvp_th.png (http://i47.tinypic.com/2v85pvp.png) http://i46.tinypic.com/znwuv7_th.jpg (http://i46.tinypic.com/znwuv7.jpg)

Is it ever really the end. :devil:

"Final" just refers to "release version", as opposed to "Alpha" or "Beta" versions that are intended for testing only.

[LoRd_MuldeR]

LameXP v3.17 Alpha-3
http://www.mediafire.com/file/mj3zemdektt/LameXP.2010-02-03.Alpha-3.zip

Changes between v3.16 and v3.17:
* Updated TAK decoder to v2.0.0 (2010-01-07)
* Updated ALAC decoder to v0.2.0 (2009-09-05)
* Fixed "No Disk" error box that could appear under rare circumstances

[MatLz]

Hi my Lord!
Is your 'error disk fixe' fixe that?:
http://forum.doom9.org/showpost.php?p=1317886&postcount=489

[LoRd_MuldeR]

Hi my Lord!
Is your 'error disk fixe' fixe that?:
http://forum.doom9.org/showpost.php?p=1317886&postcount=489

Probably. I have noticed that DirectoryExists() will popup a nasty message box when called with a path that is located on a removable disc -- if there's no disc in the drive :rolleyes:

So now I have implemented yet another check that is called before DirectoryExists() is called. This additional check will make sure that the drive is ready. If the path points to a drive that is not ready (e.g. CD-ROM drive without a disc), we will reject the path immediately instead of checking for its existence. This has been implemented at two locations where a message box could have been triggered...

[MatLz]

When I will be able to download this build (mediafire:devil: ) and if that (probably;)) fixes my really annoying issue....you will have a big big thx from me and I will send you chocolates!!
Thx

[LoRd_MuldeR]

LameXP v3.17, Alpha-4:
http://www.mediafire.com/file/mzwmtmzzogt/LameXP.2010-02-04.Alpha-4.zip (Mirror (http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2010-02-04.Alpha-4.zip))

Okay, I found a "smarter" way to avoid those message boxes. I have now implemented my own SafeDirectoryExists() function that simply is a wrapper around the native DirectoryExists() function, but will disable system error message boxes before the call to DirectoryExists() and re-enable them afterwards. That's similar to Delphi's SafeLoadLibrary() function. Furthermore all calls to DirectoryExists() in LameXP have been replace with the new SafeDirectoryExists(), which hopefully will avoid those "No Disc" message once and for all...

[MatLz]

Unfortunetely that doesn't resolve my problem...however there is a change:
Now it's 'Splash: LameXP.exe - No disk' instead of 'LameXP: LameXP.exe - No disk'
Sorry for the chocolates;) but thx for your work and your efforts!

[LoRd_MuldeR]

Well, now at least we can be sure that this message box isn't triggered by any call inside LameXP. That's because all calls to DirectoryExists() -- and also to FileExists(), by the way -- have been guarded with wrapper code that will set ErrorMode to SEM_FAILCRITICALERRORS before the actual call. After that change I was unable to re-produce the error message. Well, even before it could only happen under extremely rare circumstances. So unless I get more details on what triggers the message box, I cannot do anything. And are you 100% sure, you used the latest build ???

[MatLz]

Yes the latest (thx for the mirror link)
So what can I do to give you the informations you need to know?
I can only say the error box is old windows style...

[LoRd_MuldeR]

Please try with that DEBUG build:
http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2010-02-05.Debug-1.zip

Maybe we can track down the point where the error message is triggered. The last debug message right before the "No Disk" box would be relevant...

[MatLz]

Ok
Error box appears between CreateForm(TForm_Main, Form_Main) and TForm_Data.Create.

[LoRd_MuldeR]

Ok
Error box appears between CreateForm(TForm_Main, Form_Main) and TForm_Data.Create.

Now that is annoying! It means that the error message is triggered while the "Main" Form is created. So it's definitely not caused by my own code. Apparently it's triggered somewhere inside Delphi's internal Form creation code. That's code I have zero control over. Anyway, I have implemented yet another workaround: I will now disable the Win32 error messages before the native Form constructor is called an re-enable them afterwards. And that for all the Forms of LameXP. It's kind of ugly with all those wrapper functions, but I hope that finally resolves the problem...

LameXP v3.17 Alpha-5:
http://www.mediafire.com/file/a2dymmf2zw4/LameXP.2010-02-05.Alpha-5.zip (Mirror (http://dl.dropbox.com/u/3191920/Beta/LameXP/LameXP.2010-02-05.Alpha-5.zip))

[MatLz]

That does work now!
THANK YOU!
I PM you for the chocolates.
But:It's kind of uglyDon't do ugly things in your code only for me! Can it be a problem for 'real useful' error message and other users?

[LoRd_MuldeR]

There were several people who complained about the issue lately. Good to know that the workaround has fixed it, finally.

I said the solution is "kind of ugly" because I had to built a wrapper around Delphi's function, instead of fixing the underlying code. But there's no better way here...

And I certainly won't start modifying the Delphi VCL code :p

[LoRd_MuldeR]

LameXP v3.17 RC-3
http://www.mediafire.com/file/0gxi1ngdgyt/LameXP.2010-02-20.RC-3.exe

Changes between v3.16 and v3.17:
* Updated TAK decoder to v2.0.0 (2010-01-07)
* Updated ALAC decoder to v0.2.0 (2009-09-05)
* Updated MediaInfo to v0.7.28 (2010-02-19), compiled with ICL 11.1.054
* Fixed "No Disk" error message box that could appear under certain circumstances
* Fixed "...is not responding" error message box that could appear during startup
* Various minor fixes and improvements

[manolito]

Thanks LoRd_MuldeR for this nice app!

I have a request, though... (using 3.16 final right now). I have disabled the WinXP Balloon Tips with TweakUI (I do have my reasons for doing it), but LameXP reenables them every time I run it. Could you please turn this off?

And something else...
LameXP would certainly be my only audio converter if it did support AC3. Could you integrate Aften?


Cheers
manolito

[LoRd_MuldeR]

I have a request, though... (using 3.16 final right now). I have disabled the WinXP Balloon Tips with TweakUI (I do have my reasons for doing it), but LameXP reenables them every time I run it. Could you please turn this off?

Nope. Because I want to use Balloon Tooltips for various things. So it really is a pity if people turn them off :p

If an applications shows Balloon Tooltips, we can assume it has a reason for that. Otherwise you may want to get rid of that application.

http://img291.imageshack.us/img291/5671/balloontooltipwl4.png

<UPDATE> I have implemented a workaround that will re-disabled Balloon Tooltips on exit, if they were turned on at startup </UPDATE>

LameXP would certainly be my only audio converter if it did support AC3. Could you integrate Aften?

I could. It's not a big deal, because the internal "infrastructure" allows adding new encoders/decoders easily.

However the GUI would need to be rearranged. And therefore adding additional encoders is not planned for the upcoming release.

It's on my "TODO" list of a future release...

[manolito]

If an applications shows Balloon Tooltips, we can assume it has a reason for that. Otherwise you may want to get rid of that application.
For me this would mean to get rid of the whole OS...:devil:
These balloon tips have gotten on my nerves from day 1, and MS even decided to make it hard for the average user to get rid of them.

Anyway, thanks for the workaroud, works like a charm...

Cheers
manolito

[LoRd_MuldeR]

LameXP v3.17 Final :)

Changes between v3.16 and v3.17:
* Updated TAK decoder to v2.0.0 (2010-01-07)
* Updated ALAC decoder to v0.2.0 (2009-09-05)
* Updated MediaInfo to v0.7.28 (2010-02-19), compiled with ICL 11.1.054
* Fixed "No Disk" error message box that could appear under certain circumstances
* Fixed "...is not responding" error message box that could appear during startup
* Various minor fixes and improvements

[SeeMoreDigital]

Bummer... You got out the new version before I could ask you.

Errrm... How difficult would it be to add support for 7.1Ch AAC and FLAC encoding, from suitable sources, such as LPCM (.WAV)?


Cheers

[LoRd_MuldeR]

Bummer... You got out the new version before I could ask you.

Errrm... How difficult would it be to add support for 7.1Ch AAC and FLAC encoding, from suitable sources, such as LPCM (.WAV)?


Cheers

LameXP will sent the Wave file to the Nero AAC encoder "as-is". So if the Nero encoder does support 7.1 channels, this is supposed to work already.

But if the Nero encoder doesn't support 7.1 channels, then there's nothing I can do. I'm not a Nero engineer ;)

And the same applies to 7.1 channels FLAC support: It all depends on the encoder's capabilities. LameXP just feeds the Wave into the encoder...

[boyumeow]

Hi LM, sorry to pop-in again. Just something to report (maybe it was reported before).

Window Vista in English language, my songs' title are in Chinese characters, it fails during decoding time with LameXP. But if I renamed the titles in English, all went well and progress properly.

If I switch to Vista in Chinese language, all progress correctly too with Chinese characters.

Back to Vista in English language, using Microsoft Applocale to activate LameXP in Chinese language, I still get the same error during decoding time with Chinese characters.

So, I'm just wonder whether this will get fixed. Thanks.

[LoRd_MuldeR]

Hi LM, sorry to pop-in again. Just something to report (maybe it was reported before).

Window Vista in English language, my songs' title are in Chinese characters, it fails during decoding time with LameXP. But if I renamed the titles in English, all went well and progress properly.

If I switch to Vista in Chinese language, all progress correctly too with Chinese characters.

Back to Vista in English language, using Microsoft Applocale to activate LameXP in Chinese language, I still get the same error during decoding time with Chinese characters.

So, I'm just wonder whether this will get fixed. Thanks.

This is known and expected. It's because LameXP doesn't support Unicode. And it probably never will support Unicode, as Delphi 7.0 doesn't (properly) support Unicode :o

So all file names must be converted from Unicode to ANSI. That usually works fine! But if the Codepage for Non-Unicode applications isn't configured accordingly on your system, the "converted" file name will be invalid, as required characters are missing in the current Codepage, leading to a "wrong" ANSI representation of the file name. If you don't want to globally change the Codepage for Non-Unicode applications, you can use the Microsoft Applocale Wizard to change the Codepage for individual applications. But be aware: If you choose this method, you must launch the application via Applocale every single time!

(You can use WhatsMyCodepage.exe (http://mulder.googlecode.com/svn/trunk/LameXP/src/translations/WhatsMyCodepage.exe) to check what Codepage is currently configured for Non-Unicode applications. So you can compare the Codepages between different systems)

[boyumeow]

Ok, thanks LM, I believe I understand the point about Unicode support which I did suspect that is the cause. But the part about 'Microsoft Applocale' was not functioning in my case, its exactly the same result as without using it.

But, well, I still can use the long way to re-encode my songs, either rename or switch my language Codepage, which I don't find it any hazard cause I HAVE LameXP by LoRd_MuldeR, hehehe ;p.

Btw, just curious when will Delphi 7.0 be properly support Unicode, is it still in development.

Thanks.

[LoRd_MuldeR]

Btw, just curious when will Delphi 7.0 be properly support Unicode, is it still in development.

Nope. Delphi 7.0 was released back in 2002, so it's not under developed for almost one decade. In fact the Delphi IDE is owned/developed by a different company now.

The latest version of Delphi is "Delphi 2010" (aka "Delphi 14"). Starting with Delphi 2009 support for Unicode should be much better. At least the native "String" type is Unicode now.

Unfortunately a full version of an up-to-date Delphi would cost me ~1000,- € at least :p

But the part about 'Microsoft Applocale' was not functioning in my case, its exactly the same result as without using it.

Are you sure you selected the proper language? Most important: Did you verify that with my WhatsMyCodepage.exe (http://mulder.googlecode.com/svn/trunk/LameXP/src/translations/WhatsMyCodepage.exe) tool?

[boyumeow]

Whoa, didn't know that Delphi 14 was so expensive, or else I might consider donate to U :p, but wrong timing at the moment due to personal problem.

Not sure about how U meant to use Microsoft Applocale, I did verify with ur tool and it show my codepage is 1252 (western Europe). It just seem that applocale did change the GUI window of LameXP but when I start "Encode Now", the beginning decoder fail to see those songs title being translate, just seem to me that as if I need to activate aplocale for every single program throughout the whole encoding process.

I will report back after I try it out again, with my KIS disable too, just realize my KIS did something extra.

While it might seem to be my own problem too, cause I tweak my window for some performance purpose. Thanks.

[LoRd_MuldeR]

Not sure about how U meant to use Microsoft Applocale, I did verify with ur tool and it show my codepage is 1252 (western Europe).

Well, if you launched my 'WhatsMyCodepage' tool on your English system via AppLocale utility, then it should show the same Codepage as it would show on the Chinese system without AppLocale.

Given that you have selected the proper language in the AppLocale wizard...

It just seem that applocale did change the GUI window of LameXP but when I start "Encode Now", the beginning decoder fail to see those songs title being translate, just seem to me that as if I need to activate aplocale for every single program throughout the whole encoding process.

I just checked this. And the "AppLocale" settings definitely is forwarded from the main (GUI) process to the child (encoder) processes:

http://i45.tinypic.com/5npyky_th.png (http://i45.tinypic.com/5npyky.png)


But if nothing else helps, you can still try to open the "problematic" files with their short file name:

http://i46.tinypic.com/jzw2fc_th.png (http://i46.tinypic.com/jzw2fc.png)


[EDIT]

Here is an experimental build that provides an alternative 'Open' dialog for Unicode file names:
-Link removed-

Note that the file names will be converted to "short" (8+3) file names. Therefore you should only use the "new" dialog, if the "normal" dialog won't handle it.
It's still recommended to set the Codepage for Non-Unicode applications to the suitable Codepage for your file names...


[EDIT²]

This version includes a much improved version of the new Unicode-safe 'Open' dialog:
-Link removed-

Now multiple files can be selected and "long" file names are only converted to "short" file names if they contain unsupported characters.
If no serious problems are found, this will eventually replace the "normal" dialog. However be aware that Drag&Drop still is not Unicode-safe!
As before it is still recommend to configure the Codepage for Non-Unicode applications according to the file names you want to open...

[LoRd_MuldeR]

LameXP v3.18 RC-1 :)

Changes between v3.17 and v3.18:
* Added an Unicode-safe "Open" dialog: File names are converted to "short" names if required
* Updated LAME encoder to v3.98.3 (2010-02-28), compiled with ICL 11.1.054
* Updated mpg123 decoder to v1.10.1 (2010-02-27)

[boyumeow]

Well LM, indeed, there is problems with my windows environment, just that I could not found the fault. But ur unicode-safe "open" dialog did a good trick. Anyway, I will stick to the manual work as I have say before, cause I would not be able to identify all my songs with the unicode translated titles.

I never afraid of this little manual work, nothing is perfect. I'm just worry that I increase Ur trouble.

And I still had to thanks you for your hard work. :thanks:

[LoRd_MuldeR]

LameXP v3.18 RC-2 :)

Changes between v3.17 and v3.18:
* Added an Unicode-safe "Open" dialog: File names are converted to "short" names if required
* Updated MediaInfo to v0.7.29 (2010-03-08), compiled with ICL 11.1.060
* Updated LAME encoder to v3.98.3 (2010-02-28), compiled with ICL 11.1.054
* Updated mpg123 decoder to v1.10.1 (2010-02-27)

[SeeMoreDigital]

Is there any likelihood of adding say... an AC3 encoder?

[LoRd_MuldeR]

The same still applies:

Marvellous work...

I guess the only major encoder that would be worth including now is AC3..... Did I say that out loud?

Well, there is Aften. So this isn't too unrealistic. Will have a look when I have more time.

As mentioned before, LameXP's backend is organized in a way that allows adding new encoders/decoders quite easily. Updating and extending the GUI is what needs work.

Unfortunately I'm very busy at the moment...

[LoRd_MuldeR]

LameXP v3.18 Final :)
http://mulder.dummwiedeutsch.de/home/?page=projects#lamexp

Changes between v3.17 and v3.18:
* Added an Unicode-safe "Open" dialog: File names are converted to "short" names if required
* Updated LAME encoder to v3.98.4 (2010-03-23), compiled with ICL 11.1.054
* Updated MediaInfo to v0.7.30 (2010-03-26), compiled with ICL 11.1.060
* Updated mpg123 decoder to v1.11.0 (2010-03-20), compiled with GCC 4.4.3

[LoRd_MuldeR]

LameXP v3.18 Final, Hotfix-1 :)
http://mulder.dummwiedeutsch.de/home/?page=projects#lamexp

Changes between v3.17 and v3.18:
* Added an Unicode-safe "Open" dialog: File names are converted to "short" names if required
* Updated LAME encoder to v3.98.4 (2010-03-23), compiled with ICL 11.1.054
* Updated MediaInfo to v0.7.30 (2010-03-26), compiled with ICL 11.1.060
* Updated mpg123 decoder to v1.12.1 (2010-03-31), compiled with GCC 4.4.3
* Updated Ogg Vorbis decoder to v1.9.7 (2010-03-29), compiled with MSVC 9.0
* Updated language files (big "thank you" to all contributors !!!)

[MatLz]

Hi my Lord,

I wonder if it is possible to add an option like that:

"don't delete intermediary temp wav files if the source file hasn't been remove from the list to have the possibility to directly encode with other settings"

[LoRd_MuldeR]

Hi my Lord,

I wonder if it is possible to add an option like that:

"don't delete intermediary temp wav files if the source file hasn't been remove from the list to have the possibility to directly encode with other settings"

Possible? Yes. Easy to do? Not really. Will it happen? Nope.

Usually it's preferable to clean up TEMP files as soon as possible. That someone re-encodes the same files twice or even more is... unlikely.

And even if some one does that, having to decode the files again every single time isn't a significant problem.

Decoding time -vs- encoding time is like 1:100 ;)

[nakTT]

Thanks for the latest update, Lord.

:thanks:

P/S: I also downloaded your updated x264 guide.

[Adolph]

Hi, first of all I want to thank LoRd_MuldeR for this great app.:thanks:Mainly because the program uses the latest release on Lamev3.98.4 and ogg aoTuV codecs. What I've found odd it that when I open the program it takes too much time to load(2 minutes 31 seconds) and seems to use a lot of CPU usage when loading because I can clearly hear the fan speeding up during this process.:confused: Is this normal with this application because its just a front end.Unfortunately I'm not a developer to check the code. I run the latest version LameXP v3.18 Final
Windows Vista 32 bit
AMD Turion 64 X2 1.80 GHz
2430MB memory RAM

Please advise
lots of thanks in advance

[LoRd_MuldeR]

This is most likely caused by insanely slow anti-virus software. Try to temporarily disabled the "real-time scanner" (guard) of your a/v software and see if it makes any difference.

I personally recommend Avira AntiVir (Personal Edition), as it is one of the fastest scanners along with a reasonably low false-positive rate...

[nakTT]

Hi Lord,

Since I can manually add Nero components in the application folder, is there any way for me to do the same for OggVorbis and others?

:thanks:

[LoRd_MuldeR]

Hi Lord,

Since I can manually add Nero components in the application folder, is there any way for me to do the same for OggVorbis and others?

:thanks:

Nero "components" ???

I think you mean the Nero AAC encoder, which has to be added manually to the application folder. That's required only because I cannot redistribute the Nero AAC encoder along with LameXP.

All the other encoders supported by LameXP are already "built-in", so you don't need to add them manually. This includes the Ogg Vorbis encoder.

And adding arbitrary encoders, that aren't supported by LameXP yet, isn't possible by putting them into the application folder. You would need to modifying the LameXP source codes. Or ask kindly ;)

By the way: Adding support for Aften (AC-3) is on my long-term "Todo" list, but I'm too busy at the moment...

[nakTT]

Yes, that is what I meant. So that I can manually update existing codec with the latest one (without having to bother you :) )

Since it is no possible at this point, then I will ask you nicely ( ;) ) when we have a new codec to be updated.

:thanks:

[LoRd_MuldeR]

Yes, that is what I meant. So that I can manually update existing codec with the latest one (without having to bother you :) )

Since it is no possible at this point, then I will ask you nicely ( ;) ) when we have a new codec to be updated.

:thanks:

I do my best to keep all the "built-in" encoders up-to-date. However there in fact is a way to overwrite the internal encoders ;)

Just put the encoder binary at:
<Install Directory>\Dev\<Build Number>\Bin\Foo.exe

This of course only works with the encoders that already are supported by LameXP. And it can screw things up if you put a wrong/unsupported binary.

[nakTT]

I do my best to keep all the "built-in" encoders up-to-date. However there in fact is a way to overwrite the internal encoders ;)

Just put the encoder binary at:
<Install Directory>\Dev\<Build Number>\Bin\Foo.exe

This of course only works with the encoders that already are supported by LameXP. And it can screw things up if you put a wrong/unsupported binary.
Glad to hear that ;) but I can't seems to find any directory at all.

I currently using non-installed (portable) version of the software. I can't see any other folder inside the main folder. Please advise.

[LoRd_MuldeR]

I currently using non-installed (portable) version of the software. I can't see any other folder inside the main folder. Please advise.

It won't be there. You need to create it yourself. And there is no "portable" version, as there is no non-portable version ;)

The installer will extract the 'LameXP.exe' to the desired directory and create startmenu shortcuts. But that's it. All the rest is identical to the 'Zip' release.

[nakTT]

It won't be there. You need to create it yourself. And there is no "portable" version, as there is no non-portable version ;)

The installer will extract the 'LameXP.exe' to the desired directory and create startmenu shortcuts. But that's it. All the rest is identical to the 'Zip' release.
I mean the Zip release :)

I see, so I will try to create the folder.

Any idea how can I encode audio (using nero aac) to m4a file instead of current mp4 file.

:thanks:

[nakTT]

I do my best to keep all the "built-in" encoders up-to-date. However there in fact is a way to overwrite the internal encoders ;)

Just put the encoder binary at:
<Install Directory>\Dev\<Build Number>\Bin\Foo.exe

This of course only works with the encoders that already are supported by LameXP. And it can screw things up if you put a wrong/unsupported binary.
Any idea where can I find Foo.exe?

As for the directory, is the below correct?

C:\LameXP\Dev\Build 87\Bin\Foo.exe

[LoRd_MuldeR]

Any idea where can I find Foo.exe?

You won't find it anywhere. You can put it into the aforementioned directory manually, so LameXP will find and use it instead of the "built-in" binary.

Also note that "Foo.exe" was just an example!

So you must use "tool_lamenc.exe" for LAME, "tool_oggenc_i386.exe" or "tool_oggenc_sse2" for Ogg Vorbis, "tool_flac.exe" for FLAC and so on...

As for the directory, is the below correct?

C:\LameXP\Dev\Build 87\Bin\Foo.exe

Nope. Replace "Build 87" with "87" and it will be correct ;)

Any idea how can I encode audio (using nero aac) to m4a file instead of current mp4 file.

.m4a is just a different (and incorrect!) file extensions for MP4 files containing audio.

The one and only "correct" extension for MP4 files (according to the specifications) is .mp4 and that is what LameXP uses.

Anyway, a simple "Right-click -> Rename" in Windows Explorer will do it ;)

(Given that your Explorer isn't crippled to hide the file extension, which is the case with a freshly installed Windows)

[nakTT]

Hi Lord,

Many, many thanks for a very detail guide. I believe with your guide, even a noob like me can get it done. Many thanks again Lord.

Where do you normally download these:
1) tool_lamenc.exe
2) tool_oggenc_i386.exe
3) tool_flac.exe" and others

Or you compile it yourself?


Regarding the extension, forgive me for not being specific enough. What I meant is excluding the rename the file extension. Anyway, I did and still use the trick when using LameXP. ;)

[LoRd_MuldeR]

Where do you normally download these:
1) tool_lamenc.exe
2) tool_oggenc_i386.exe
3) tool_flac.exe" and others

Or you compile it yourself?

If you don't want to (or can't) compile them yourself from the sources (available from the official project web-sites), you will need to find a pre-compiled binary somewhere around the internet :p

http://www.rarewares.org/index.php is a great site for pre-compiled audio tools, like encoders and decoders. Most of the "built-in" binaries I took from there. Some I compiled myself.

[nakTT]

If you don't want to (or can't) compile them yourself from the sources (available from the official project web-sites), you will need to find a pre-compiled binary somewhere around the internet :p

http://www.rarewares.org/index.php is a great site for pre-compiled audio tools, like encoders and decoders. Most of the "built-in" binaries I took from there. Some I compiled myself.
Hi Lord, you got it right. Noob like me can't (yet ;) ) compile myself.

rarewares version of the latest oggvorbis is crashing all the time on me. Confirmed by people at HA forum. Any other place that you normally go to get the binary?

I can see that LameXP using oggvorbis aoTuV b5.7 (2009-03-01). Any idea how can I use the latest test version; aoTuV post-b5.7 (2010-03-14) ( http://www.geocities.jp/aoyoume/aotuv/test.html ) with LameXP? I have tried the directory trick but to no avail.

:thanks:

[LoRd_MuldeR]

Hi Lord, you got it right. Noob like me can't (yet ;) ) compile myself.

rarewares version of the latest oggvorbis is crashing all the time on me. Confirmed by people at HA forum. Any other place that you normally go to get the binary?

Most sites only mirror the Rarewares.org binary. I think you should ping John33 about your crash problem!

(BTW: Are you using the "P4 only" or the "Generic" build?)

I can see that LameXP using oggvorbis aoTuV b5.7 (2009-03-01). Any idea how can I use the latest test version; aoTuV post-b5.7 (2010-03-14) ( http://www.geocities.jp/aoyoume/aotuv/test.html ) with LameXP?

The latest aoTuV release is 2009-03-01 ;)

You are pointing to the latest "test" version of aoTuv, which, as the name implies, should only be used for testing, but certainly not for long-term archiving of audio files.

Also the test versions only include a "reference binary" of venc.exe, which cannot be used for LameXP. There are no sources released!

So we will have to wait for AOYUMI to make a final release of the next aoTuV, including sources. Then we finally can get a new build OggEnc.exe with new aoTuV improvements.

[nakTT]

Most sites only mirror the Rarewares.org binary. I think you should ping John33 about your crash problem!

(BTW: Are you using the "P4 only" or the "Generic" build?)



The latest aoTuV release is 2009-03-01 ;)

You are pointing to the latest "test" version of aoTuv, which, as the name implies, should only be used for testing, but certainly not for long-term archiving of audio files.

Also the test versions only include a "reference binary" of venc.exe, which cannot be used for LameXP. There are no sources released!

So we will have to wait for AOYUMI to make a final release of the next aoTuV, including sources. Then we finally can get a new build OggEnc.exe with new aoTuV improvements.
Crash on all version. Hope they will update soon as I'm not the only one facing the problem.

Perhaps I forgot for bold the word "test" in my question. :p


Lord, any idea on how can I use the aoTuV latest test (;)) version (not necessarily using LameXP)? I thank you in advance.

:thanks:

[LoRd_MuldeR]

From the venc.exe help screen:

aoTuV Post Beta 5.7 - OggVorbis Encoder (c)2003-2010 Aoyumi

usage: venc [options] InputFileName [OutputFileName]

InputFileName is "input wav file name" or "-"(standard input)

[options] <general> (There are exclusive relations)
-qVALUE This value sets audio quality-level. It is between
-2 (low quality) and 10 (high quality). [VBR mode]
-bVALUE This value sets tagets bitrate (in kbits). [ABR mode]

[options] <enc-ctl> (Non-recommendation)
-ub=VALUE Upper bitrate setting (in kbits) for "-b".
-lb=VALUE Lower bitrate setting (in kbits) for "-b".
-lowpass=VALUE Overwrite default low-pass filter setting. New
low-pass filter value is between 2 and 99 (in kHz).
-ibtune=VALUE This relatively changes the noise masking value of
impulse block. This value is between -15 and 0.

[options] <other>
-downmix If the input stream is stereo, the stream of stereo
is converted into mono.
-resample=VALUE The VALUE sets new sampling rate.
-padding=VALUE This adds padding of VALUE (byte) to vorbis comment
domain.
-ignore_length The data length header is ignored.
-i Display of this software information.

Somthing like venc.exe -q5 "c:\foo\bar.wav" "c:\temp\out.ogg" should do the job.

[nakTT]

Somthing like venc.exe -q5 "c:\foo\bar.wav" "c:\temp\out.ogg" should do the job.
I assume "foo" is what ever the folder name, right?

as for -q5, for this test version only 0, -1, -2 will work. I got you there :p

Just kidding Lord, you has been very helpful to me. Thanks bro.


:thanks:


P/S: Thanks again Lord, it works like a charm.

[Adolph]

Thanks again LoRd_MuldeR.I temporarily disabled my McAffe Security Center like you suggested to check if LameXP loaded faster and it worked. LameXP booted really fast like in 3 seconds.
thanks again and keep up the good work

[Adolph]

sorry LoRd_MuldeR one more thing, I'd love to see support for Musepack as output. Can this be possible on future updates if it is not much too ask?
thanks a lot
you're the real LoRd:)

[nakTT]

sorry LoRd_MuldeR one more thing, I'd love to see support for Musepack as output. Can this be possible on future updates if it is not much too ask?
thanks a lot
you're the real LoRd:)
I second that.

Thanks Lord.

[LoRd_MuldeR]

Thanks again LoRd_MuldeR.I temporarily disabled my McAffe Security Center like you suggested to check if LameXP loaded faster and it worked. LameXP booted really fast like in 3 seconds.
thanks again and keep up the good work

Yet another reason to keep away from McAfee :rolleyes:

sorry LoRd_MuldeR one more thing, I'd love to see support for Musepack as output. Can this be possible on future updates if it is not much too ask?

Not currently planned. But never say never...

[nakTT]

Hi Lord,

If you don't already know, people at rarewares has already released the fixed version of the latest oggvorbis. If its not too much trouble, hope you can update LameXP with it. Thanks.

[LoRd_MuldeR]

Hi Lord,

If you don't already know, people at rarewares has already released the fixed version of the latest oggvorbis. If its not too much trouble, hope you can update LameXP with it. Thanks.

As said before, LameXP includes the version of OggEnc that uses the aoTuV-improved Vorbis encoder. The latest OggEnc release with aoTuV still is 2009-03-04. It will be updated as soon as either a new aoTuV version becomes available or the pending aoTuV improvements are merged into the "offical" Vorbis libraries. Furthermore LameXP never used the apparently broken 2010-03-27 release of OggEnc.

[nakTT]

As said before, LameXP includes the version of OggEnc that uses the aoTuV-improved Vorbis encoder. The latest OggEnc release with aoTuV still is 2009-03-04. It will be updated as soon as either a new aoTuV version becomes available or the pending aoTuV improvements are merged into the "offical" Vorbis libraries. Furthermore LameXP never used the apparently broken 2010-03-27 release of OggEnc.
Oops, I may have missed the part saying that LameXP only use auTuV version of ogg. Sorry for any inconvenience. I thank you anyway.

As for the merger, I heard that it is supposed to be in this release but later they said it is postponed to the next release instead. It is (among other) to avoid regression if I remember it correctly. Perhaps you know better than me and would like to share the real reason?

[LoRd_MuldeR]

It's mentioned here that they postponed the merging of psy-tunings (i.e. aoTuV) to a later release:
http://www.hydrogenaudio.org/forums/index.php?showtopic=79765&st=0&p=696408&#entry696408

That's all info I have. Let's hope they will do it soon, so we don't need to worry about two different flavours of Vorbis (up-to-date vs. psycho-acoustically-improved).

[nakTT]

Thanks for the info.

Yeah, I also hope they will do it sooner rather than later. Personally I prefer aoTuV since most people said it is better than the official one.

[MatLz]

Sorry for my late reply...Decoding time -vs- encoding time is like 1:100 ;)So you could claim 'LameXP is now 1% faster*'







(*in rare cases):)

No it's a joke, I understand.

[manolito]

Hi LoRd_MuldeR,

I have one question and one request...:)

Request first: Whenever I update LameXP to a new version, all my previous settings are gone, I have to reenter all my settings. Is it possible to teach the installer so that it will carry over all previous settings to the new version?

And now my question which concerns AC3 to WAV conversion:
Whenever I convert a 2-channel AC3 to WAV with LameXP, this WAV file plays OK in MPC, WaveLab also has no problems with it. But when I try to use this file with MuxMan to author a DVD, MuxMan rejects the file.

OTOH when I use good old HeadAC3he (version 0.24-a13) to do this conversion (one-pass mode, no sample rate conversion or normalization), the resulting WAV file is accepted by MuxMan. Do you have an explanation?


Cheers
manolito

[LoRd_MuldeR]

Request first: Whenever I update LameXP to a new version, all my previous settings are gone, I have to reenter all my settings. Is it possible to teach the installer so that it will carry over all previous settings to the new version?

The settings for each version of LameXP are stored separately.

If you look at "C:\Users\John Doe\AppData\Roaming\MuldeR\LameXP\Settings.ini" in a text editor, you'll see that there is one section per LameXP version.

You can hack the INI file and rename the sections to port your settings into a newer version. At your own risk, of course ;)

And now my question which concerns AC3 to WAV conversion:
Whenever I convert a 2-channel AC3 to WAV with LameXP, this WAV file plays OK in MPC, WaveLab also has no problems with it. But when I try to use this file with MuxMan to author a DVD, MuxMan rejects the file.

Might be a WAVE_FORMAT_PCM -vs- WAVE_FORMAT_EXTENSIBLE issue. See for details:
http://www.microsoft.com/whdc/device/audio/multichaud.mspx

Anyway, I think mpucoder (http://forum.doom9.org/member.php?u=78) would be the man to ask about MuxMan issues...

[LoRd_MuldeR]

LameXP v3.18 Final, Hotfix-2 :)
http://mulder.dummwiedeutsch.de/home/?page=projects#lamexp

Changes between v3.17 and v3.18:
* Added an Unicode-safe "Open" dialog: File names are converted to "short" names if required
* Fixed mpg123 decoder to work on Windows 2000 (reported by Tim Womack)
* Updated LAME encoder to v3.98.4 (2010-03-23), compiled with ICL 11.1.054
* Updated MediaInfo to v0.7.32 (2010-05-02), compiled with ICL 11.1.065
* Updated mpg123 decoder to v1.12.1 (2010-03-31), compiled with GCC 4.4.4
* Updated Ogg Vorbis decoder to v1.9.7 (2010-03-29), compiled with MSVC 9.0
* Updated language files (big "thank you" to all contributors !!!)

[CpT]

Thanks man, This is a great app!

[ckmox]

thanks for the updates

[skrowl]

Request: Can you please make the output filenames from the nero aac encoder .m4a rather than .mp4? Some video players (including several I tested on my android phone) assume that anything with a .mp4 extension is a video, so they pause whenever I lock my phone. I believe that .m4a is the standard extension for an audio-only aac file anyhow: http://en.wikipedia.org/wiki/MPEG-4_Part_14#.MP4_versus_.M4A_file_extensions

Thank you!

[LoRd_MuldeR]

Request: Can you please make the output filenames from the nero aac encoder .m4a rather than .mp4? Some video players (including several I tested on my android phone) assume that anything with a .mp4 extension is a video, so they pause whenever I lock my phone. I believe that .m4a is the standard extension for an audio-only aac file anyhow: http://en.wikipedia.org/wiki/MPEG-4_Part_14#.MP4_versus_.M4A_file_extensions

Thank you!

Nope. The only "correct" extension for MP4 files is ".mp4" and that's the extension I'll use. If Apples thinks they need their own extension, then that's their problem. I don't care ;)

.MP4 versus .M4A file extensions

The existence of two different file extensions for naming audio-only MP4 files has been a source of confusion among users and multimedia playback software. Since MPEG-4 Part 14 is a container format, MPEG-4 files may contain any number of audio, video, and even subtitle streams, making it impossible to determine the type of streams in an MPEG-4 file based on its filename extension alone. In response, Apple Inc. started using and popularizing the .m4a file extension. Software capable of audio/video playback should recognize files with either .m4a or .mp4 file extensions, as would be expected, as there are no file format differences between the two. Most software capable of creating MPEG-4 audio will allow the user to choose the filename extension of the created MPEG-4 files. [...] The only official file extension defined by the standard is .mp4. [...] The common but non-standard use of the extensions .m4a and .m4v is due to the popularity of Apple’s iPod, iPhone, and iTunes Store.

[Ajax_Undone]

Hey LoRd_MuldeR just pointing out a bug.

When I convert multiple Albums of Tracks the track number gets screwed up...

http://img690.imageshack.us/img690/6702/songs.png (http://img690.imageshack.us/i/songs.png/)

Uploaded with ImageShack.us (http://imageshack.us)

[LoRd_MuldeR]

Hey LoRd_MuldeR just pointing out a bug.

When I convert multiple Albums of Tracks the track number gets screwed up...

The track numbers are assigned according to the file's position in the source files list!

And there are various options to sort the files on the list, including "by track number" ;)

[dforionstar]

LoRd_MuldeR:

Thank you for the awesome LameXP application.

Unfortunately I am unable to use it as the screen fonts are not scalabel and I get the message saying I should use 96 dpi.

In my opinion, that is an outdated restriction, as present-day configurations come in a multitude of display and screen sizes. In my case, I use a notebook PC with 15.4" screen size, WSXGA+ (1680 x 1050) native resolution. I normally use a resolution of 1440 x 900, 144dpi, extra large system fonts. Even at these settings, LamXP fonts are very small.

I hope in future releases, you will be encouraged to address this.

Danke!/Thank you!

[LoRd_MuldeR]

LoRd_MuldeR:

Thank you for the awesome LameXP application.

Unfortunately I am unable to use it as the screen fonts are not scalabel and I get the message saying I should use 96 dpi.

In my opinion, that is an outdated restriction, as present-day configurations come in a multitude of display and screen sizes. In my case, I use a notebook PC with 15.4" screen size, WSXGA+ (1680 x 1050) native resolution. I normally use a resolution of 1440 x 900, 144dpi, extra large system fonts. Even at these settings, LamXP fonts are very small.

I hope in future releases, you will be encouraged to address this.

Danke!/Thank you!

The warning has been removed long ago, but only for Windows Vista and later (that means for Windows 7 too). That's because starting with Vista, DPI settings different from 96 are handled much better. The content of the window is now upscaled by the OS rather than by the application (unless the application explicitly indicated that it is "DPI-aware"). LameXP is not DPI-aware! Using DPI settings different from 96 causes the layout to be destroyed on Windows XP and earlier (see below). Thus the warning will remain for older OS versions. I can only recommend to update your OS, if possible...


Please compare these:

http://i47.tinypic.com/2v85pvp_th.png (http://i47.tinypic.com/2v85pvp.png)

http://i46.tinypic.com/znwuv7_th.jpg (http://i46.tinypic.com/znwuv7.jpg)

[LoRd_MuldeR]

LameXP v3.19 Alpha-3 :)
http://www.mediafire.com/file/d4m5tymfxdq/LameXP.2010-07-12.Alpha-3.exe

Changes between v3.18 and v3.19:
* Updated MediaInfo to v0.7.34 (2010-07-09), compiled with ICL 11.1.065
* Updated mpg123 decoder to v1.12.3 (2010-07-11), compiled with GCC 4.6.0
* Updated language files (big "thank you" to all contributors !!!)
* Fixed decoding of certain invalid WavPack files

[rtjnyoface]

After all the time I've ever spend encoding audio and video files I just came across LameXP. I must say, it's a really awesome program, really. From metadata support to sampling rate, quality preferences, my gosh. It's really a great program. Thanks Mulder!

Oh, and if my memory serves me correctly, ipods (at least the ones not capable of displaying video) don't play mp4 files. But I don't know, my memory may not be serving me too well :)

Anyhoo, thanks again!

edit: oh! and multithreading (well, using a different thread for each instance) is SOOO FUC&^NG AWESOME! The time that nero aac ui uses to encode lamexp does in a small fraction of the time. This should be donationware my friend, holy shite. You have all the features of commercial software in a GNU proggy. Fu*^ng amazing. Thanks again!

[LoRd_MuldeR]

Oh, and if my memory serves me correctly, ipods (at least the ones not capable of displaying video) don't play mp4 files. But I don't know, my memory may not be serving me too well :)

From all that I know (not that I would ever buy/use any Apple products) the iPod only accepts AAC audio streams that are stored in a MP4 container.

However it seems that these morons decided that MP4 files, which only contain a single audio streams, will only be recognized as audio files with an incorrect ".m4a" file name :rolleyes:

LameXP will create MP4 files with the correct ".mp4" file name, of course...

[rtjnyoface]

No dear sir. I've only been using the m4a extension for my ipod. And from what I know, itunes converts them to aac, not mp4.

[LoRd_MuldeR]

No dear sir. I've only been using the m4a extension for my ipod. And from what I know, itunes converts them to aac, not mp4.

Sorry, you don't know what you are talking about. We must distinguish between the stream format and the container format here:

No matter what, the audio streams are in the AAC (Advanced Audio Coding) audio format. Furthermore the AAC streams are usually stored in a MP4 container (MPEG-4 Part 14).

The one and only correct file name extension for MP4 files, according to the MPEG-4 specifications, is .mp4 and nothing else. The .m4a extension was Apple's idea :rolleyes:

A proper application will recognize a MP4 file regardless of its file name (extensions) - by looking at the file header!

Software that relies on file name extensions to "detect" the file format is silly and error-prone by definition. Software that even relies on an incorrect extension simply is brain-dead.

LameXP outputs AAC streams stored in a MP4 container. And those files are stored with the correct .mp4 file name extension.

I will never change that, just because of one company's incompetence. If you really must, rename your audio-only MP4 files from .mp4 to .m4a in Explorer and that's it...

[Chimel]

Late thank you, but the forum would not let me post and then I forgot! ^-^
So glad I found LameXP, I was using Switch Sound File Converter, but the buggers asked me more money when I moved from Vista to Windows 7!
I saw "batch processing" and switches mentioned several times, does it mean LameXP has a command line mode?
For the sake of me I haven't been able to find it.

It's great that you added WMA support after that Softpedia review (or rather before that, as you mentioned), but I have to agree with the comment about the 3 sounds in Setup, About and Encoding, the latter one is real bad when you've switched to other tasks and may have cranked up the volume... It would be great to have at least a silent option, but I guess that's not a priority.

Manolito and some other commenters are right, the settings should really be persistent across updates, the settings.ini manual hack is lame(xp?). Every single application work this way, and I now have files that were converted with the wrong settings because I didn't realize LameXP has reset them all. I have no way to find them now.

That Delphi Unicode limitation really sucks for the artist, album or song names retrieved automatically from the Internet. Whether it's classical composers such as Bedřich Smetana or Leoš Janáček or Scandinavian folk-metal songs such as Erämaan Ärjyt, they are all in unknown different code pages, so AppLocale and batch processing cannot be used. On the other hand, many cheap MP3 players don't support Unicode either, an option to convert all extended characters to pure ASCII could be nice.

But I digress, I appreciate you're doing the best with what little time you have and that old Delphi build, and you have all my :thanks: for that essential tool!

My audio conversion routine, couple of times a week:
- Get a bunch of CDs, mostly used. Insert them into my Win7 PC's CD player, with Windows Media Player set to rip them automatically (into lossless WMAs).
- Review/edit the artist/album/title/genre/folder/file names.
- Run a batch file that calls LameXP to create MP3s out of the WMAs in the same folder.
- Same script then moves the MP3s to a non-indexed folder with robocopy /mov, and the WMAs and artwork to my audio library with robocopy /move.

That's why I was wondering about batch processing and switches at the beginning, I thought I could specify which folder to add and encode, maybe even bypass the 3 manual "Close" buttons at the end of each batch. That would really rock! I'd be glad to help.

[Karkas]

Great program LoRd_MuldeR, thanks a million!

However, I recently ran into a problem transcoding large FLAC files to AAC.

It seems to error out because it is converting the flac to wav as intermediate to AAC, but the wav cant be larger than 4gb. Is there a work-around? 64bit wav codec or soemthing I can add in or some other way?

Thanks in advance

[LoRd_MuldeR]

Great program LoRd_MuldeR, thanks a million!

However, I recently ran into a problem transcoding large FLAC files to AAC.

It seems to error out because it is converting the flac to wav as intermediate to AAC, but the wav cant be larger than 4gb. Is there a work-around? 64bit wav codec or soemthing I can add in or some other way?

Thanks in advance

If that is a limitation of the FLAC decoder (which I think is the case here), then there isn't anything I could do on my side.

And of course you can install 64-Bit "Codecs" on your system, but LameXP won't care, as all the decoders/encoders are "built-in" ;)

(BTW: You don't need 64-Bit code to support files bigger than 4 GB. This is possible with 32-Bit code just fine.
You only have to use the proper data type. And 64-Bit data types are available in 32-Bit code)

[Karkas]

If that is a limitation of the FLAC decoder (which I think is the case here), then there isn't anything I could do on my side.

And of course you can install 64-Bit "Codecs" on your system, but LameXP won't care, as all the decoders/encoders are "built-in" ;)

(BTW: You don't need 64-Bit code to support files bigger than 4 GB. This is possible with 32-Bit code just fine.
You only have to use the proper data type. And 64-Bit data types are available in 32-Bit code)

Thanks for getting back to me:thanks:

Do you know of any other projects that would allow me to coververt my large FLAC file to AAC? They can playback fine...

[LoRd_MuldeR]

Do you know of any other projects that would allow me to coververt my large FLAC file to AAC? They can playback fine...

If the FLAC CLI encoder/decoder doesn't work, then MPlayer/MEncoder and FFmpeg would be the usual candidates to try, I guess...