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

[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]

Originally Posted by boyumeow

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

Originally Posted by boyumeow

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 tool?

[boyumeow]

Whoa, didn't know that Delphi 14 was so expensive, or else I might consider donate to U , 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]

Originally Posted by boyumeow

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...

Originally Posted by boyumeow

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:




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




[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.

[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:

Originally Posted by LoRd_MuldeR

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...rojects#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...rojects#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]

Originally Posted by 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"

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.



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

[Adolph]

Hi, first of all I want to thank LoRd_MuldeR for this great app.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. 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?

[LoRd_MuldeR]

Originally Posted by 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?

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.

[LoRd_MuldeR]

Originally Posted by 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.

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.