LameXP v4.21 Final · Build #2382 (2023-12-29)

[real.finder]

thank you for reply :)

about wav, I wonder if using pipe between the decoder and encoder will override the 4g issue

Example with an avs:-

avs2pipemod -wav "script.avs" | venc -q4 - "OutputFileName.ogg"

pause

or

avs2pipemod -wav=16bit "script.avs" | venc -q4 - "OutputFileName.ogg"

pause

Example without avs:-

oggdec -o "input.ogg" | sox -S -t wav - -t wav - --norm=-0.5 | venc -q4 - "OutputFileName.ogg"

pause

or

oggdec -o "input.ogg" | sox -S -t wav - -t wav - gain -n -0.5 | venc -q4 - "OutputFileName.ogg"

pause

--------


and about the flac and the channels, if I use bassAudioSource in avs the channels order will be ok, that mean the problem in the decoder

thank you :)

[LoRd_MuldeR]

Using pipes would resolve the 4 GB issue, indeed. This has been discussed before.

The problem is: What is the exact format we send over the pipe? Is it "raw" PCM data? If so, how do we tell the second process the PCM format (channel count, sample rate, sample format)?

And if we do not send "raw" PCM, do we send a "fake" non-standard Wave header in front of the PCM data? Does every application support/recognize this?

In practice we would have to check for each pair of applications whether they can communicate via pipe - and how it can be done. For N applications this makes N^2 pairs to check...

[Dogway]

More bashing:
Disc Number metadata is not passed through (probably other tags as well)
Loading mini-windows looks 90's software
We have talked this before but auto-comment tag "Encoded by LameXP" is there to crap things out, I'm aware of your narcissism, but that is counter-productive, some people put valuable data on comments, and you not only wipe it out like nothing, but force everybody to do one added step to set the comments tag to nothing. If you want more exposure you should first take my advices for good and improve the software.

[LoRd_MuldeR]

Disc Number metadata is not passed through (probably other tags as well)

It is not technically possible to simply "pass through" meta tags. Please forget about that idea! If you re-encode an audio file, any meta tags will just disappear - unless you explicitly detect them from the original input file, remember them in a special data structure and explicitly re-embed them into the re-encoded file. This all doesn't happen by itself!

Now, LameXP supports at least 20 different input formats (decoders) and 8 different output formats (encoders). Consequently, retaining the meta tags is not trivial at all. That's especially because every encoder, decoder and file formats uses their own types of meta tags. There is no universal standard for meta tags that everybody in the world has agreed on. Instead, things have evolved over the decades. And often quite differently.

The good thing about standards is: There are so many to choose from...

Therefore, the "internal" meta data model of LameXP, i.e. the meta info that LameXP will "remember" for each file, has been designed to be a "smallest common denominator" for what is supported by all (most) file formats that LameXP deals with. And indeed, this was mostly inspired by ID3 v1. This doesn't mean that the "internal" meta data model of LameXP is perfect or that it will be fixed forever. But right now I don't have plans to change it.

Loading mini-windows looks 90's software

No idea what you are referring to, but feel free to elaborate... :rolleyes:

We have talked this before but auto-comment tag "Encoded by LameXP" is there to crap things out, I'm aware of your narcissism, but that is counter-productive, some people put valuable data on comments, and you not only wipe it out like nothing, but force everybody to do one added step to set the comments tag to nothing. If you want more exposure you should first take my advices for good and improve the software.

As I probably have explained earlier, I won't change the default value for the "comment" tag. You can change the "comment" value easily on the "meta data" tab at any time, just not the default value.

As long as this software is provided for free, I don't have to justify this decision. If you don't like it, you can file a feature request. In contrast to "more bashing", a polite feature request might actually motivate the developer to consider your change request. Anyway, you really cannot expect that your feature requests will be accepted right away. Different people have different opinions. And, in the end, it's the developer who has to make the decision which feature he likes or doesn't like in his software. Or which feature he can implemented with reasonable effort (and which ones he can not implement). There's no reason to be miffed if one of your requests gets discarded or postponed.

If you disagree with the developer and still would like the software to be changed in your way, you have two possibilities:


Get coding! As long as the software is provided as OpenSource, you are given the freedom to modify the software according to your own needs. Time to make something out of that ;)
If your coding skills are insufficient for a simple modification or you simply are too lazy, you can still hire a developer to implement the desired modification for you.

[LoRd_MuldeR]

LameXP v4.09 Alpha-8:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.15 (2013-10-05), compiled with GCC 4.8.1
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvementsImportant: Users updating from Alpha-6 or later may need to download/install the update manually this time, because there was a regression in Alpha-6 that prevents the auto-update installer from working correctly. It can happen that the update is downloaded correctly, but as soon as the installer is about to get launched it won't be able to initialize properly - instead it may complain about a missing file. In this case try with "Retry" or download manaually :o

[LoRd_MuldeR]

LameXP v4.09 Alpha-9:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.15 (2013-10-05), compiled with GCC 4.8.1
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvements

[Dark Eiri]

Will the next alpha support Opus 1.1? I'm curious to test it!

[LoRd_MuldeR]

Will the next alpha support Opus 1.1? I'm curious to test it!

Opus binaries from the v1.1 branch have been included/used since v4.07, but I will update the Opus binaries to the final v1.1 release soon :)

[LoRd_MuldeR]

LameXP v4.09 Alpha-10:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Added encoding support for Monkey's Audio (APE) format, including APEv2 tagging support
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated Opus encoder/decoder libraries to v1.1 and Opus-Tools to v0.1.8 (2013-12-05)
* Updated Monkey's Audio binary to v4.12 (2013-06-26)
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated MediaInfo to v0.7.65 (2013-11-20), compiled with ICL 14.0 and MSVC 12.0
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.15 (2013-10-05), compiled with GCC 4.8.1
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvements

[LoRd_MuldeR]

LameXP v4.09 Beta-1:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Added encoding support for Monkey's Audio (APE) format, including APEv2 tagging support
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated Opus encoder/decoder libraries to v1.1 and Opus-Tools to v0.1.8 (2013-12-05)
* Updated Monkey's Audio binary to v4.12 (2013-06-26)[/COLOR]
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated MediaInfo to v0.7.65 (2013-11-20), compiled with ICL 14.0 and MSVC 12.0
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.15 (2013-10-05), compiled with GCC 4.8.1
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvements

Happy new year! :)

[Nexin]

I missed this software encoder over the years it's a shame the name is LameXP. The name Lame I have associated over the years with mp3 only.

OT: Mp3 has very bad sound even from cd source to highest bitrates. Thankfully aac has come to our rescue it's a shame it is apple that released it. Now we have hardly no decent aac encoders. Wait for newer better than aac encoder that is also freely distributed without limitations for all to use.

I think more the answer will be as always lossless audio now that people are getting higher bandwidth fibre connections with storage options. Where Lossless always been easy to use with optical discs as cd, dvd, bluray and storage devices hdd including now larger capacity hdd TB drives, memory drives for pc, hardware and portable devices. Exception sdd that is still very expensive 2014 compared to other storage solutions also not so good with having only 10 year life limitation of all data on sdd disk. Other bdxl where is the 256gb disks even very few places sell bdxl blueray discs has been many years now since it was released (optical media consortium are at fault for this lazy) or maybe a better products is near that has scarred the optical consortium members.

[Octo-puss]

Anyone else wondering what does that post have to do with LameXP?

[LoRd_MuldeR]

I missed this software encoder over the years it's a shame the name is LameXP. The name Lame I have associated over the years with mp3 only.

Maybe I should officially rebrand LameXP to:
Superduper Anything to MP3/Vorbis/AAC/FLAC/Opus/APE Converter 2014 XXL Pro Ultra+ for Windows XP/Vista/7/8/8.1 :D

Joking aside, this program once started as a very simple LAME encoder GUI for WindowsXP, which was limited to WAVE to MP3 conversions - thus the name.

More and more features (like more encoders and decoders) have been added over the past 10 years of development. But I just never felt like "updating" the name of the program.

It's partly because that's the name people know for almost a decade now. And partly because I'm not very creative in thinking up names ;)

(Note: I know that Windows XP will reach end-of-life, once and for all, in a few months. I plan to support XP for a few more years though. But then I really need a new name!)

OT: Mp3 has very bad sound even from cd source to highest bitrates. Thankfully aac has come to our rescue it's a shame it is apple that released it. Now we have hardly no decent aac encoders. Wait for newer better than aac encoder that is also freely distributed without limitations for all to use.

Now that statement, which indeed is a bit off-topic, sounds mostly like a rant to me:

If MP3 at 320 kbps still doesn't sound transparent to your ears, you must either have an exceptional hearing ability, your were using a crappy MP3 encoder or something with your testing method/environment was borked :eek:

According to ABX tests, most people agree that LAME can achieve transparent quality way below the maximum bitrate:
http://wiki.hydrogenaudio.org/index.php?title=LAME#Recommended_encoder_settings

Furthermore, AAC is generally superior to MP3 at lower bitrates. But as the bitrates increase, the perceptual differences diminish - because at one point both formats will be transparent.

So if you want decent quality at ultra-low bitrates, AAC (or maybe nowadays Opus?) will obviously be a better choice than MP3. But if you are using medium to high bitrates, you can achieve great quality with any of them :)

Last but not least: There is FFmepg's AAC encoder, FAAC, Nero AAC encoder, QAAC (Apple/iTunes encoder) and libfdk_aac (Fraunhofer FDK encoder), just to name a few. How many AAC encoders do you need?

Anyone else wondering what does that post have to do with LameXP?

Except for the first statement - not much.

[Octo-puss]

Rest assured you do NOT need new name. People get used to a name after some time, and don't even think about its meaning anymore :P If it works, don't fix it - as a programmer you should know better :D

[justonce01]

Question:
When using the Custom Encoder Parameters under Advanced Options, do the parameters get "added" to the other settings or do I have to write the complete line there?

Example:
I've set up all the things under Compression (selected bitrate) and under Advanced Options things like LAME Algorithm Quality and Channel mode. I also want to add the --noreplaygain parameter. Now do I just add --noreplaygain (as pictured below)

http://i.imgur.com/m3bmRvY.png

or do I need to add everything else too (as pictured below)?

http://i.imgur.com/1ViuwyY.png

[LoRd_MuldeR]

When using the Custom Encoder Parameters under Advanced Options, do the parameters get "added" to the other settings or do I have to write the complete line there?

Custom parameters are added on top of the parameters that LameXP would generate normally, so you should avoid setting the RC-mode or bitrate there.

You can also inspect the complete command-line in the log, just to be sure...

[justonce01]

Custom parameters are added on top of the parameters that LameXP would generate normally, so you should avoid setting the RC-mode or bitrate there.

You can also inspect the complete command-line in the log, just to be sure...

Nice, thanks for the clarification.

[LoRd_MuldeR]

LameXP v4.09 RC-1:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Added encoding support for Monkey's Audio (APE) format, including APEv2 tagging support
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated Opus encoder/decoder libraries to v1.1 and Opus-Tools to v0.1.8 (2013-12-05)
* Updated Monkey's Audio binary to v4.12 (2013-06-26)
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated WavPack decoder to v4.70.0 (2013-10-19), compiled with ICL 14.0 and MSVC 12.0
* Updated MediaInfo to v0.7.67 (2014-01-10), compiled with ICL 14.0 and MSVC 12.0
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.16 (2013-12-13), compiled with GCC 4.8.1
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvements

[LoRd_MuldeR]

LameXP v4.09 RC-2:

Changes between v4.08 and v4.09 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Added encoding support for Monkey's Audio (APE) format, including APEv2 tagging support
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated Opus encoder/decoder libraries to v1.1 and Opus-Tools to v0.1.8 (2013-12-05)
* Updated Monkey's Audio binary to v4.12 (2013-06-26)
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated WavPack decoder to v4.70.0 (2013-10-19), compiled with ICL 14.0 and MSVC 12.0
* Updated MediaInfo to v0.7.67 (2014-01-10), compiled with ICL 14.0 and MSVC 12.0
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.16 (2013-12-13), compiled with GCC 4.8.1
* Updated the QAAC add-in for LameXP to QAAC v2.33 (2014-01-14), compiled with MSVC 12.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvementsDownload latest QAAC add-in here:
http://www.mediafire.com/download/38nv297501obvwv/LameXP.qaac-addin.2014-01-19.zip

[LoRd_MuldeR]

LameXP v4.09 Final has been released :)
https://github.com/lordmulder/LameXP/releases/latest

★ ★ ★ 10th Anniversary Edition ★ ★ ★

Changes between v4.08 and v4.09 [2014-01-26]:
* Upgraded build environment to Microsoft Visual Studio 2013 RTM
* Complete overhaul of the file analyzer, resulting in up to 2.5x faster file import speed
* Reworked the application initialization code, resulting in notably faster startup speed
* Added encoding support for Monkey's Audio (APE) format, including APEv2 tagging support
* Improved file analyzer to retain the original ordering of files imported from a playlist
* Improved internal encoder API, so each encoder can define its own configuration options
* Improved splash screen and working banner, using "sheet of glass" effect on supported OS
* Improved dropbox widget, including proper multi-monitor support
* Updated Opus encoder/decoder libraries to v1.1 and Opus-Tools to v0.1.8 (2013-12-05)
* Updated Monkey's Audio binary to v4.12 (2013-06-26)
* Updated mpg123 decoder to v1.16.0 (2013-10-06), compiled with GCC 4.8.1
* Updated WavPack decoder to v4.70.0 (2013-10-19), compiled with ICL 14.0 and MSVC 12.0
* Updated MediaInfo to v0.7.67 (2014-01-10), compiled with ICL 14.0 and MSVC 12.0
* Updated GNU Wget binary to v1.14.0 (2012-08-05), compiled with GCC 4.8.1
* Updated GnuPG to v1.4.16 (2013-12-13), compiled with GCC 4.8.1
* Updated the QAAC add-in for LameXP to QAAC v2.33 (2014-01-14), compiled with MSVC 12.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a resource (file descriptor) leak in "static" builds, didn't cause much harm though
* Various bugfixes and code improvements

[SeeMoreDigital]

Wow... has it really been ten years?

[LoRd_MuldeR]

Wow... has it really been ten years?

The oldest version I could find in my archives dates back to early 2004 ;)

http://i.imgur.com/9i8Ijj2.png

If you wonder why the Git version log only dates back to Nov 2010, that's because I switched to Git when I started porting LameXP to C++/Qt in late 2010.

Older versions were still developed with SVN, but the complete history got lost when the "free" SVN server, which I had used back then, was shut down once and for all - the pain of a centralized version control.

Not to mention that in the first few years I even didn't use a revision control system at all :p

[manolito]

Thanks very much for the new anniversary version. Feels a lot more responsive on my slow computer.
I still have to switch to 16bit colours before I can use it.

And finally McCartney made this "company for the rest of us" change its name... :D

http://i39.tinypic.com/2d1w8jp.jpg


Cheers
manolito

[LoRd_MuldeR]

Thanks very much for the new anniversary version. Feels a lot more responsive on my slow computer.

Great :)

I still have to switch to 16bit colours before I can use it.

As concluded earlier, this must be either an extremely rare bug in Qt, a buggy video driver or another oddness in your system.

At least I have not been able to reproduce this on any of my test systems, ranging from my old Windows XP notebook to a new Windows 8.1 computer.

Even works fine under Linux via Wine...

And finally McCartney made this "company for the rest of us" change its name... :D

Uargh! Why do you have to report this one day after the final release? :devil:

(Fixed the typo now)

[Chumbo]

LameXP v4.09 Final has been released :)
https://github.com/lordmulder/LameXP/releases/latest

★ ★ ★ 10th Anniversary Edition ★ ★ ★
Congrats! :eek:...I mean...:D

[trunket]

I just wanted to thank you for your latest final version of LameXP, it is great. I also like the new splash graphic. As far as the name LameXP goes, I thought about that at first too, but now it doesn't bother me, plus it's kind of a historical reference :)

But anyway, I really like your software. It's solid, clear, easy to use, has plenty of options. I especially love it since you implemented remembering the settings for the various encoders, that was great and I thank you for it (I was the one who nagged you for it before you implemented it).

Yeah, I think it's my favorite converter :D Great work.

[mike20021969]

I also like the new splash graphic.

It reminds me of KITT from 80's Knight Rider.

[LoRd_MuldeR]

It reminds me of KITT from 80's Knight Rider.

Probably not coincidence :devil:

[SeeMoreDigital]

Hi LoRd_MuldeR,

Over the weekend I've thought I'd have a go at generating some DTS-CD compliant audio files.

Anyway I fired up LameXP and noticed that the DCA encoder offers the ability to create DTS encodes from 32Kbps right up-to 4096Kbps.

Is there any particular reason why the maximum bit-rate exceeds 1536Kbps?


Cheers

[LoRd_MuldeR]

Over the weekend I've thought I'd have a go at generating some DTS-CD compliant audio files.

Anyway I fired up LameXP and noticed that the DCA encoder offers the ability to create DTS encodes from 32Kbps right up-to 4096Kbps.

Is there any particular reason why the maximum bit-rate exceeds 1536Kbps?

Why not? If dcaenc-2 supports those bitrates, why not expose them in the GUI? Doesn't mean you actually have to go that high, if you don't need/want to ;)

Also, if I recall correctly, not all bitrates will actually work with all sample-rate/channel-count combinations. Finally, the (maximum) bitrate for DTS-CD is 1,234 kbit/s, according to Wikipedia.

[SeeMoreDigital]

Also, if I recall correctly, not all bitrates actually work with all sample-rate/channel-count combinations...Indeed,

It was quite some time before I realized that a DTS-CD's bit-stream needs to be encoded at 1234Kbps, 44.1KHz/16-bit...

[LoRd_MuldeR]

Indeed,

It was quite some time before I realized that a DTS-CD's bit-stream needs to be encoded at 1234Kbps, 44.1KHz/16-bit...

It's not that surprising if you take into account that the Audio-CD standard doesn't officially support anything but uncompressed PCM.

The only reason why DTS-CD can work in practice, is because it stores the DTS-encoded data as if it was PCM data. And since the Audio-CD standard stipulates 44,100 Hz with 16-Bit/sample, the available bitrate is fixed.

BTW: The reason why the DTS-CD bitrate is 1234 kbit/s instead of 1411.2 kbit/s (which would be the "native" Audio-CD bitrate) is because DTS-CD only uses the lower 14-Bit of each 16-Bit sample.

[lansing]

very nice program, the gui looks pretty and control is easy to use, I tried avanti a couple of days ago and it was a big mess.

And I have a request, can you make the font size of the chinese characters bigger? Right now all the words look like they're smushed together.

[LoRd_MuldeR]

And I have a request, can you make the font size of the chinese characters bigger? Right now all the words look like they're smushed together.

It looks pretty much okay to me, as far as I can tell (but I can't read Chinese text, so I might be mistaken):

http://i.imgur.com/RQy9Lohs.jpg (http://i.imgur.com/RQy9Loh.jpg)

If it looks different on your side, this might be some kind of font issue :confused:

If it does look the same and if you still think you need a bigger font, I may look for a way to increase the font size in the whole application via Qt. Increasing the font size for each widget manually isn't really an option.

Other than that, you may always increase the Windows "DPI" settings. Right-click on Desktop, choose "Screen Resolution" and then "Make text and other items smaller or larger".

[LoRd_MuldeR]

It looks pretty much okay to me, as far as I can tell (but I can't read Chinese text, so I might be mistaken):

http://i.imgur.com/RQy9Lohs.jpg (http://i.imgur.com/RQy9Loh.jpg)

If it looks different on your side, this might be some kind of font issue :confused:

If it does look the same and if you still think you need a bigger font, I may look for a way to increase the font size in the whole application via Qt. Increasing the font size for each widget manually isn't really an option.

Other than that, you may always increase the Windows "DPI" settings. Right-click on Desktop, choose "Screen Resolution" and then "Make text and other items smaller or larger".

That was easier than expected. So here is a new test version:
http://sourceforge.net/projects/muldersoft/files/LameXP/Testing/LameXP-ALPHA.2014-03-12.Release-Static.Build-1531.zip/download

You can now use the new "--big-font" or even "--huge-font" startup options to get bigger overall fonts. And "--small-font" or "--tiny-font" for an opposite effect.

Though don't be surprised, if this breaks the layout ;)

[lansing]

--big-font is too big. Option to set font size by pixel can be good.

[LoRd_MuldeR]

--big-font is too big. Option to set font size by pixel can be good.

I have tweaked the font-sizes for "--big-font" and "--huge-font" a little:
http://sourceforge.net/projects/muldersoft/files/LameXP/Testing/LameXP-ALPHA.2014-03-12.Release-Static.Build-1532.exe/download

[lansing]

yes the --big-font look good, add some padding to the top and bottom of the tab title and everything should be good.

And I found the Chinese traditional translation quality pretty bad, most sentence translation doesn't make sense.

[LoRd_MuldeR]

And I found the Chinese traditional translation quality pretty bad, most sentence translation doesn't make sense.

As said before, I don't speak Chinese. So I have to rely on contributed translations. Feel free to improve it ;)

http://lamexp.sourceforge.net/doc/Translate.html

[Chimel]

Happy 10th anniversary!
Still works as good as the previous versions! ;)
Better even, no more wake up sound at the end of the conversion.

I noticed that both the Start menu group and the Program Files folder still have "4.06" in their name, you may want to remove all version numbers from both. If users want to use 2 versions of LameXP concurrently, maybe they can specify a different folder through the custom setup, but regular users should not have to be bothered by it.

Just a FYI, I also got a warning about a suspicious antivirus software slowing down LameXP, but I don't have anything like that, only the latest Microsoft Security Essentials on Windows XP SP3. I seem to remember I have the same false warning with the previous version.

Edit: I tried to submit this reply half a dozen times, can you please use random questions that are not hermetic? I could not answer any of those about audio and video stuff (could not even understand what most of the questions meant) and I had to open a separate browser tab for the question about the number of forum rules. Any plan to use questions real people can actually answer would be great. Probably only bots can make sense of the questions I saw and look up the answers so they can spam the forum. Or nerds.

[LoRd_MuldeR]

Happy 10th anniversary!

:thanks:

I noticed that both the Start menu group and the Program Files folder still have "4.06" in their name, you may want to remove all version numbers from both. If users want to use 2 versions of LameXP concurrently, maybe they can specify a different folder through the custom setup, but regular users should not have to be bothered by it.

If you make an "upgrade" install (i.e. install "over" an older version), the installer will use the same startmenu folder as the previous install used, so you won't end up with two separate stratmenu folders. If you make a "clean" install (i.e. first un-install old version, then install new version) this won't happen. The same applies to the LameXP installation folder.

It probably was not a good idea to include any version number into the default install/startmenu paths. And maybe I'm going to change that for future versions.

Just a FYI, I also got a warning about a suspicious antivirus software slowing down LameXP, but I don't have anything like that, only the latest Microsoft Security Essentials on Windows XP SP3. I seem to remember I have the same false warning with the previous version.

The warning is generally about "slow" startup speed. The threshold was chosen way above the startup times I get on my test systems, with MSE enabled. If the user gets slower startup times than that (and thus a warning is triggered), it most likely is caused by bad anti-virus software - since certain anti-virus programs can easily slow down the startup procedure by a factor of ten! But it's also possible that the system is just generally a bit slow.

Edit: I tried to submit this reply half a dozen times, can you please use random questions that are not hermetic? I could not answer any of those about audio and video stuff (could not even understand what most of the questions meant) and I had to open a separate browser tab for the question about the number of forum rules. Any plan to use questions real people can actually answer would be great. Probably only bots can make sense of the questions I saw and look up the answers so they can spam the forum. Or nerds.

This forum has been suffering from heavy spam attacks not too long ago. The moderators had a very hard time deleting all the rubbish in order to keep the forum usable. Therefore Doom9 has installed some mechanisms to keep the spambots out (and personally I have no control over that). Questions related to the actual topics of the forum seem to work very well to keep the bots out. And most "real" people, who are dedicated to audio/video transcoding, can answer them easily.

Sorry, if you had troubles. But it's unlikely the current anti-spam system will be changed anytime soon. Nobody here wants to be flooded by spam posts again...

[LoRd_MuldeR]

LameXP v4.10 Alpha-3:
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/2014-04-09/

Changes between v4.09 and v4.10 [unreleased]:
* Updated MediaInfo to v0.7.68 (2014-04-08), compiled with ICL 14.0 and MSVC 12.0
* Updated mpg123 decoder to v1.19.0 (2014-03-08), compiled with GCC 4.8.2
* Fixed a bug that could cause the cover artwork to be lost under certain circumstances
* Added command-line options to adjust the LameXP font size (see FAQ doc for details)

[lansing]

can you add a check in auto updater to see if the version the user is using a portable version or installer version? I'm using a portable version and the auto updater is downloading a installer for me.

[LoRd_MuldeR]

can you add a check in auto updater to see if the version the user is using a portable version or installer version? I'm using a portable version and the auto updater is downloading a installer for me.

Of course it does. The Auto-Update tool necessarily needs to download the installer. The ZIP file couldn't extract itself, obviously. Making LameXP extract the downloaded ZIP file, into the LameXP install folder, is not possible either - because the LameXP executable cannot be overwritten while it is still running. Instead, we download the setup program, into the TEMP directory. And once the installer has been launched (in "Auto-Update" mode), LameXP will terminate immediately. Then the installer can take over and do its job. Also note that, if the installer has been invoked from a "portable" version of LameXP, it will again create a "portable" version (i.e. the LameXP executable will again be installed as "LameXP-Portable.exe").

[LoRd_MuldeR]

LameXP v4.10 Beta-1:
http://sourceforge.net/projects/lamexp/files/Snapshots%20%28BETA%29/2014-04-25/

Changes between v4.09 and v4.10 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 with Update-1
* Updated Qt runtime libraries to v4.8.6 (2014-04-25), compiled with MSVC 12.0
* Updated Opus libraries v1.1.x and Opus-Tools v0.1.8 to latest Git Master (2014-04-13)
* Updated MediaInfo to v0.7.68 (2014-04-08), compiled with ICL 14.0 and MSVC 12.0
* Updated mpg123 decoder to v1.19.0 (2014-03-08), compiled with GCC 4.8.2
* Fixed a bug that could cause the cover artwork to be lost under certain circumstances
* Added command-line options to adjust the LameXP font size (see FAQ doc for details)

[Octo-puss]

Could you upload a portable build for me again please? :)

[LoRd_MuldeR]

Could you upload a portable build for me again please? :)

Sorry, but won't upload a separate "portable" build for each pre-release version. Just enable "portable" mode, as usual ;)

http://lamexp.sourceforge.net/doc/FAQ.html#9fd53558

[Octo-puss]

Oh sorry, I should have said I meant for the latest stable release (I haven't upgraded for several months).

[LoRd_MuldeR]

Oh sorry, I should have said I meant for the latest stable release (I haven't upgraded for several months).

The latest "stable" release is v4.09, so what you are looking for already is available here:
http://sourceforge.net/projects/lamexp/files/Miscellaneous/Special%20Builds/

[LoRd_MuldeR]

LameXP v4.10 Beta-2:

Changes between v4.09 and v4.10 [unreleased]:
* Upgraded build environment to Microsoft Visual Studio 2013 with Update-1
* Updated Qt runtime libraries to v4.8.6 (2014-04-25), compiled with MSVC 12.0
* Updated Opus libraries v1.1.x and Opus-Tools v0.1.8 to latest Git Master (2014-04-13)
* Updated MediaInfo to v0.7.69 (2014-04-26), compiled with ICL 14.0 and MSVC 12.0
* Updated mpg123 decoder to v1.19.0 (2014-03-08), compiled with GCC 4.8.2
* Fixed a bug that could cause the cover artwork to be lost under certain circumstances
* Added command-line options to adjust the LameXP font size (see FAQ doc for details)