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

[LoRd_MuldeR]

Okay, after some debugging I found the cause of the issue!

When FAAD2 prints out the current Progress, it first writes the text "[x%] decoding <filename>" into an internal buffer, before it then actually prints that text out to the console. And, as this text includes the filename, the size of the buffer that is required to hold the text, depends on the length of the file name, obviously. For some reason, however, they made the buffer only 200 characters long. With very long file names this can be too short and we get a nice buffer overrun!

[Motenai Yoda]

how do u fixed? Can I suggest to simply use cout<< operator to concatenate and push out the strings, or use something like strCount() or size_of() to know how long the filename is?

[LoRd_MuldeR]

I increased the buffer from 200 to 300 char's, which should be enough, assuming file name won't exceed MAX_PATH char's. But to be sure, and because in UTF-8 encoding one "character" can take multiple char's (bytes), I also replaced the highly unsafe sprintf() with the safe snprintf_s(). Using the "cout" object is not possible in a plain C program, that is C++ stuff. And sizeof() doesn't tell you anything, if you have char* pointer.

BTW: It seems all the reason why they print into a buffer first, instead of using printf() right away, is because they are going to pass the same text into SetConsoleTitle() too.

(The patch will be included in the LameXP repository, as always)

[LoRd_MuldeR]

LameXP v4.06 RC-3

Changes between v4.05 and v4.06 [unreleased]:
* Updated Opus encoder/decoder libraries to v1.0.1 and Opus-Tools to v0.1.5 (2012-09-22)
* Updated mpg123 decoder to v1.14.4+ (2012-09-24), compiled with GCC 4.7.1
* Updated Qt runtime libraries to v4.8.3 (2012-09-13), compiled with MSVC 10.0
* Updated MediaInfo to v0.7.60 (2012-09-07), compiled with ICL 12.1.7 and MSVC 10.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a bug with the "Store temporary files in your system's default TEMP director" checkbox
* Fixed a buffer overflow in FAAD2 decoder which could cause crashes with very long file names
* Fixed a regression in Qt v4.8.3 that broke Drag&Drop support (details #1 (https://bugreports.qt-project.org/browse/QTBUG-27265)) (details #2 (https://codereview.qt-project.org/35297))
* Reworked the "About..." dialog – now using a custom dialog instead of message boxes

Note: Because home.pages.at has stopped the service after many years, my web-site sadly is no longer available under the "free.pages.at" address :(

The following mirrors are still available: #1 (http://mulder.brhack.net/) #2 (http://mulder.bplaced.net/) #3 (http://mulder.cwsurf.de/) #4 (http://mulder.6te.net/)

[LoRd_MuldeR]

LameXP v4.06 RC-4

Changes between v4.05 and v4.06 [unreleased]:
* Updated Opus encoder/decoder libraries to v1.0.1 and Opus-Tools to v0.1.5 (2012-09-22)
* Updated mpg123 decoder to v1.14.4+ (2012-09-24), compiled with GCC 4.7.1
* Updated Qt runtime libraries to v4.8.3 (2012-09-13), compiled with MSVC 10.0
* Updated MediaInfo to v0.7.61+ (2012-10-28), compiled with ICL 12.1.7 and MSVC 10.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a bug with the "Store temporary files in your system's default TEMP director" checkbox
* Fixed a buffer overflow in FAAD2 decoder which could cause crashes with very long file names
* Fixed a regression in Qt v4.8.3 that broke Drag&Drop support (details #1 (https://bugreports.qt-project.org/browse/QTBUG-27265)) (details #2 (https://codereview.qt-project.org/35297))
* Reworked the "About..." dialog – now using a custom dialog instead of message boxes

[LoRd_MuldeR]

LameXP v4.06 RC-5

Changes between v4.05 and v4.06 [unreleased]:
* Updated Opus encoder/decoder libraries to v1.0.1 and Opus-Tools to v0.1.5 (2012-09-22)
* Updated mpg123 decoder to v1.14.4+ (2012-09-24), compiled with GCC 4.7.1
* Updated ALAC decoder to refalac v0.56 (2012-10-24), based on reference implementation by Apple
* Updated Qt runtime libraries to v4.8.3 (2012-09-13), compiled with MSVC 10.0
* Updated MediaInfo to v0.7.61+ (2012-10-28), compiled with ICL 12.1.7 and MSVC 10.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a bug with the "Store temporary files in your system's default TEMP director" checkbox
* Fixed a buffer overflow in FAAD2 decoder which could cause crashes with very long file names
* Fixed a regression in Qt v4.8.3 that broke Drag&Drop support (details #1 (https://bugreports.qt-project.org/browse/QTBUG-27265)) (details #2 (https://codereview.qt-project.org/35297))
* Reworked the "About..." dialog – now using a custom dialog instead of message boxes

[LoRd_MuldeR]

LameXP v4.06 has been released :)

Changes between v4.05 and v4.06 [2012-11-04]:
* Updated Opus encoder/decoder libraries to v1.0.1 and Opus-Tools to v0.1.5 (2012-09-22)
* Updated mpg123 decoder to v1.14.4+ (2012-09-24), compiled with GCC 4.7.1
* Updated ALAC decoder to refalac v0.56 (2012-10-24), based on reference implementation by Apple
* Updated Qt runtime libraries to v4.8.3 (2012-09-13), compiled with MSVC 10.0
* Updated MediaInfo to v0.7.61+ (2012-10-28), compiled with ICL 12.1.7 and MSVC 10.0
* Updated language files (big thank-you to all contributors !!!)
* Fixed a bug with the "Store temporary files in your system's default TEMP director" checkbox
* Fixed a buffer overflow in FAAD2 decoder which could cause crashes with very long file names
* Fixed a regression in Qt v4.8.3 that broke Drag&Drop support (details #1 (https://bugreports.qt-project.org/browse/QTBUG-27265)) (details #2 (https://codereview.qt-project.org/35297))
* Reworked the "About..." dialog – now using a custom dialog instead of message boxes

[SeeMoreDigital]

Downloading and installing now.... Many thanks :)

[Dogway]

at last LameXP doesn't have any conflict with Comodo on the new version.
The bad news is it doesn't recognise qaac.exe.
If you care for presentation, there's a mispell in spanish "Mostar DropBox", where it should be "Mostrar".
You're welcome : P

edit: found the hidden gem qaac.exe v.1.39, working great now, thanks!

[LoRd_MuldeR]

at last LameXP doesn't have any conflict with Comodo on the new version.

I didn't change anything... because there is nothing I could do, on my side, against buggy A/V software.

So I guess, whatever the problem in Comodo was, they have fixed the bug on their side...

See also:
http://lamexp.sourceforge.net/doc/FAQ.html#96205e91

The bad news is it doesn't recognise qaac.exe.

Please follow the install instructions here:
http://lamexp.sourceforge.net/doc/FAQ.html#71a113b0

You may need to update your QAAC add-in for LameXP, if yours is too old...

If you care for presentation, there's a mispell in spanish "Mostar DropBox", where it should be "Mostrar".
You're welcome : P

Well, I have to rely on traslators for all languages, except for English and German.

If you think you can improve the Spanish translation, please feel free to have a look at:
http://lamexp.sourceforge.net/doc/Translate.html

I will fix this one typo for the next release. So thanks for the report.

[Dogway]

You may need to update your QAAC add-in for LameXP, if yours is too old...
Yes I found out just right after posting.

I didn't do anything to Comodo (update database nor software) so I don't know, maybe it was something on your side (without noticing) or that I correctly enabled permissions, although I doubt I didn't do this the first time.

Thank you.

[LoRd_MuldeR]

http://img703.imageshack.us/img703/7214/clipboard04xj.png

For anybody who cares, here is the first Visual Studio 2012 build of LameXP:
http://www.mediafire.com/file/rl546gd6j4yvav1/LameXP-ALPHA.2012-11-15.Release-Static.Build-1188.exe

As one might expect, this build will not run on Windows XP (or even older). It also will need a CPU with SSE2 support, because Visual Studio defaults to /arch:SSE2 now and I didn't see a reason to change that. If the binary doesn't run on older OS anyway, it doesn't make any sense to still care about archaic CPU's. Other than that, you shouldn't see any difference with the new build.

[SeeMoreDigital]

For anybody who cares, here is the first Visual Studio 2012 build of LameXP:
http://www.mediafire.com/file/rl546gd6j4yvav1/LameXP-ALPHA.2012-11-15.Release-Static.Build-1188.exe

Thanks... It opens fine with Win7 32-bit ;)

[manolito]

http://img703.imageshack.us/img703/7214/clipboard04xj.png

For anybody who cares, here is the first Visual Studio 2012 build of LameXP:
http://www.mediafire.com/file/rl546gd6j4yvav1/LameXP-ALPHA.2012-11-15.Release-Static.Build-1188.exe


I just hope that you are not planning to abandon XP support any time soon...:scared:


Cheers
manolito

[LoRd_MuldeR]

Don't worry, I won't drop Windows XP support!

Maybe I will make the switch to VS2012 after Microsoft has finally released the "Update 1" for VS2012, which is supposed to restore Windows XP targeting support, yay ;)

I don't know if it will be possible to restore Windows 2000 support the same way I could do it with VS2010, so I might be forced to drop Windows 2000 support.

(Currently I'm still undecided whether my eyes will be able to permanently bear the clunky interface of VS2012, but "Update 1" is also supposed to bring back some colors ^^)

[Przemek_Sperling]

I ripped some CDs and coded them with Opus. The quality is great but one thing seems to be a bit weird to me. As I ripped them from CDs the source is sampled at 44 kHz, but if I compress it with Opus and play with AIMP or foobar the players show 48 kHz sampling rate. Are the files resampled? Is it usual behavior for the codec orI am doing something wrong?

[LoRd_MuldeR]

Please see:
http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=97051&view=findpost&p=808895

Opus does not natively support 44Khz. The idea is that since 48Khz can store a 44Khz signal, this simplifies the algorithm. Then, it just stores the original format and size so that a decoder could decode to the same values, but a decoder is allowed to decode at another samplerate. [...] Every non-48Khz input rate will internally be converted to 48Khz. So the output will always be at 48Khz. If you don't trust the internal resampler then you could always go and use something like SoX.


See also:
http://wiki.xiph.org/OpusFAQ#How_do_I_use_44.1_kHz_or_some_other_sampling_rate_not_directly_supported_by_Opus.3F

Note that it's generally preferable for a decoder to output at 48kHz even when you know the original input was 44.1kHz, not only because you can skip resampling but also because many inexpensive audio interfaces have poor quality output for 44.1k. [...] input files at these rates [above 48 kHz] are internally converted to 48 kHz, and then only frequencies up to 20 kHz are encoded. The reason is simple: lossy codecs are designed to preserve audible details while discarding irrelevant information. Since the human ear can only hear up to 20 kHz at best (usually lower than that), frequency content above 20 kHz is the first thing to go.

[Przemek_Sperling]

Thank you for the links. They explain everything :thanks:

[LoRd_MuldeR]

LameXP v4.07 Alpha-4

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Updated Qt runtime libraries to v4.8.4 (2012-11-23), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.5 (2012-11-23)

Note: This build was made with "Update 1" of Visual Studio 2012, so this build is supposed to work under Windows XP again (as opposed to Visual Studio 2012 RTM). If you encounter any issues under Windows XP, please report!

[Kadai]

Not sure if someone has reported it yet... but (at least on Linux / Kubuntu 12.10 ... running LameXP on top of Wine) I have got a consistent problem when the tags of the files being encoded have quotes on the name.

For example, if the file has a title tag like (and named also): マジカ"ルゼ"アクション編曲バトル! ... the file won't convert and will threw a error.

This have happened to me with flac files, but they have something in common... the tags are UTF-8 encoded (so far I know).

Now, I'm not sure if this also happens on Windows (because I do not have a windows box at hand), but this error has been consistent with me, with the 4.06 final version, so I decided to report it.

Other one I have seen that threw me the error is:
ゆうかぜ (Yoshino Yoshikawa "Pollarstars" remix)

Hope it is helpful.

[LoRd_MuldeR]

Hi, Kadai.

LameXP provides full Unicode support. Also all CLI tools used by LameXP either support Unicode file names or have been patched by me to support Unicode file names.

Nonetheless tags can still be problematic, because some tag formats, like ID3v1, do not defined which encoding/codepage is used. They simply store 8-Bit characters encoded in an undefined (system-specific) codepage. There neither is an indication of the codepage being used, nor is Unicode (e.g. UTF-8 or UTF-16) supported/used. Thus it is impossible to know which codepage was used to create those tags. If your system's default codepage for 8-Bit characters doesn't happen to be the same as the creator's codepage happened to be, then the tags will be read as garbage. That's not a limitation/bug of LameXP, but a shortcoming of the ID3v1 format! The only solution is using ID3v2 instead of ID3v1, because ID3v2 does properly support Unicode (it uses UTF-16 encoding by definition). Of course, if we have an existing file with only ID3v1 tag, there is nothing we could do :(

Anyway, even if the tag cannot be read correctly for the reasons explained before, this certainly shouldn't cause an error. So it's probably an issue with Linux/Wine. LameXP is currently Windows-only with Windows XP and Windows 7 being the primary platforms that I use for development and testing. Wine might work too, but there is no guarantee. Random things might break! I once tested Wine (Ubuntu 12.10) and couldn't find any serious issues, except for a few graphic glitches. But as you neither mentioned what error exactly you got nor provide an example file to reproduce the issue, it is impossible to say what happened.

If you provide the required info, I might be able to look into this more in detail...

[LoRd_MuldeR]

LameXP v4.07 Alpha-5

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Updated Qt runtime libraries to v4.8.4 (2012-11-29), compiled with MSVC 11.0
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.5 (2012-11-23)

[LoRd_MuldeR]

LameXP v4.07 Alpha-6

Changes between v4.06 and v4.07:
* Upgraded build environment to Microsoft Visual Studio 2012 with Update-1
* Added option to select the "overwrite mode" to advanced options tab
* Added option to filter the log entries on the "processing" dialog (see context menu)
* Updated Opus encoder/decoder libraries to v1.1.x and Opus-Tools to v0.1.6 (2012-12-07)
* Fixed handling of certain characters when passing meta tags on the command-line

[SeeMoreDigital]

Hi LoRd_MuldeR,

I've got some 'surround sound' DTS audio CD's that I'd like to convert to 6Ch FLAC files for storage and playback via my NAS.

As with all 'surround sound' DTS audio CD's, the extracted streams are (rather annoyingly) 2Ch PCM.WAV @ 1411Kbps 44.1 KHz/16-bits files!

Can LameXP be configured to convert such sources to 6Ch FLAC?


Cheers

[LoRd_MuldeR]

If it has been "extracted" as 2 channels (stereo) PCM already, how should we get a 6 channel signal from that? :confused:

Maybe you confused DTS with Dolby ProLogic? The latter indeed stores 4 channels (left, right, center, back) in a Stereo signal and the 4 channels can then be restored from the Stereo signal using a ProLogic decoder.

[SeeMoreDigital]

If it has been "extracted" as 2 channels (stereo) PCM already, how should we get a 6 channel signal from that? :confused:
Personally, I don't know ;)

A few years ago I seem to remember an application that could convert such sources. I think it was BeSweet based... I really can't remember for sure :eek:

[LoRd_MuldeR]

If that tool can generate a "true" 6 channel signal from only 2 channels, some magic must be involved :p

[SeeMoreDigital]

If that tool can generate a "true" 6 channel signal from only 2 channels, some magic must be involved :p
I can only imagine there's some channel decoding information within the DTS.WAV files header which is passed to the decoder...

If you're interested I can provide a short sample?!

[LoRd_MuldeR]

DTS streams can be stored in a RIFF/WAVE container and LameXP will handle such files just fine (using ValibDec).

If, however, it is a 2ch PCM WAVE file, as you said earlier, I don't see how this should be possible.

MediaInfo will reveal what it actually is...

[SeeMoreDigital]

MediaInfo will reveal what it actually is...MediaInfo reports the DTS files as containing 2 channels. Indeed, it does not recognise that the file contains DTS audio!

However, VLC player (along with MediaPlayer Classic) reports the DTS files as containing 6 channels: -

http://i45.tinypic.com/2port3a.png

And when the bit-stream is passed to a DSS amp via SPDIF or HDMI you obtain six 'discrete' DTS channels...


Cheers

[LoRd_MuldeR]

Looks like we have a DTS stream that was put into a WAVE/RIFF Container as if it was PCM (2.0).

Probably the result of putting a DTS stream on an Audio-CD as if it was PCM data, hacking around the Audio-CD specifications :rolleyes:

What does a "standard" CD Player (with no special support for this kind of disc) output on its analog outputs with that disc?

Just loud garbage, I guess...

[SeeMoreDigital]

Yes, you just hear a load of (white) noise via a CD players 'analogue' outputs...

[Kurtnoise]

If, however, it is a 2ch PCM WAVE file, as you said earlier, I don't see how this should be possible.
Maybe, you should try this (http://www.movie2digital.at/index.php?page=Thread&threadID=54286)...

[SeeMoreDigital]

Maybe, you should try this (http://www.movie2digital.at/index.php?page=Thread&threadID=54286)...
I've also just discovered that DTS Parser v2 (http://forum.doom9.org/showthread.php?t=109206) offers the ability to extract the DTS stream out of the .WAV container.

Unfortunately, the extracted DTS stream appears to be slightly corrupted because neither MediaInfo or LameXP is able to read them.

However, UsEac3to v0.9.2 'is able' to read the extracted stream and generate a 6Ch PCM.WAV file, which can then be read by LameXP :D

[LoRd_MuldeR]

Maybe, you should try this (http://www.movie2digital.at/index.php?page=Thread&threadID=54286)...

Sure, somehow we can create an "upmix" from 2ch data. But that's not what he wants.

Apparently he has a real 5.1 DTS stream, only stored inside a WAVE/RIFF file as "fake" PCM 2ch data :scared:

[SeeMoreDigital]

Indeed...

For all those interested. Here's a 2Ch Surround Sound DTS sample (http://www.sendspace.com/file/gmcuxn).


Cheers

[LoRd_MuldeR]

Indeed...

For all those interested. Here's a 2Ch Surround Sound DTS sample (http://www.sendspace.com/file/gmcuxn).


Cheers

Valdec will process that file fine. It detects one error, which probably is the invalid WAVE/RIFF header:
valdec.exe "DTS-stored-as-FakePCM-Wave.wav" -w "Decompressed.wav"

We can also extract the "raw" stream:
sox.exe DTS-stored-as-FakePCM-Wave.wav" -t raw "Raw-Stream.bin"

Still MediaInfo won't recognize it as a DTS stream :rolleyes:

That's not very surprising though, because DTS bitstream errors must be expected here! That's because the Audio-CD was never created for bit-accurate reading. Instead read errors will be "fixed" by interpolating the "missing" data. That of course is done under the assumption that the data, which is defined as PCM data, actually is PCM data. It obviously can't lead to a "reasonable" result with DTS data...

Last but not least, adding support for this kind of file to LameXP is technically impossible, because your file is bit-identical to a proper PCM 2.0 WAVE/RIFF file containing white noise!

(In theory we could test any PCM Wave file by passing it through the DTS decoder and see whether it decodes any valid DTS frames, but that's not really a practicable method)

[SeeMoreDigital]

Well thanks for trying, it's much appreciated.

At least my request has finally pushed me into finding an alternative (albeit long winded) method of encoding my DTS-CD sources to multi-channel FLAC files.

All I need to do now is find now is a decent 'network capable' hardware player that supports playback of multi-channel FLAC files.

I had hoped that my Onkyo TX-NR609 amp was able to do this but unfortunately they're only played back/decoded as 2Ch :eek:

[~bT~]

Hi my Lord! Just a lil bug report or maybe user error..

In advanced options--channel mode/sampling rate-- if I tick the 'enforce stereo' option then the encoding fails using an .mp4 file which contains aac audio.

I'm using the latest version.

Cheers for the updates!

[LoRd_MuldeR]

Hi my Lord! Just a lil bug report or maybe user error..

In advanced options--channel mode/sampling rate-- if I tick the 'enforce stereo' option then the encoding fails using an .mp4 file which contains aac audio.

I'm using the latest version.

Cheers for the updates!

~bT~, please send me your log, so I can have a look...

[Motenai Yoda]

Maybe you confused DTS with Dolby ProLogic? The latter indeed stores 4 channels (left, right, center, back) in a Stereo signal and the 4 channels can then be restored from the Stereo signal using a ProLogic decoder.
If I'm not wrong dpl can archive up to 5.1 channels in a stereo track.

[LoRd_MuldeR]

After all it turned out he has a "true" 5.1 DTS stream - only camouflaged as fake PCM 2.0 to hack around the Audio CD specifications.

[LoRd_MuldeR]

LameXP v4.07 Alpha-7

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

[apilonte]

I have taken audios with my audio recorder, and wanted them to be converted from wav to flac format by LameXP. Since the recorder has taken mono audio tracks I expected the flac files to have a mono track, too. But LameXP, at least with its default settings, gave me stereo tracks. Of course, left and right channel are identical. So the rendered flac file is even bigger than the original wav file. With Audacity (a freeware audio editor), which is using the LAME codecs, too, conversion is done from mono to mono. That's why I hope, LameXP can do it as well and I only didn't press the right button.

My question ist: How can I have LameXP to render flac mono tracks?

Greetings
Heinrich

[LoRd_MuldeR]

Hello, Heinrich.

First of all, Wave (PCM) to FLAC conversion has nothing to with LAME at all :sly:

Secondly, if a FLAC file with two identical Mono channels comes out twice as big as uncompressed PCM, then that's a good example of how bad (or non-existing) the inter-channel compression of FLAC is ;)

Finally, I am not quite sure how your Mono Wave file can end up as Stereo FLAC file. Can you post your log?

[apilonte]

Can you post your log?Certainly, if I only knew where to find it. Searching in LameXP's F.A.Q.s I found a slice of text saying "In that case you can double-click on the failed item in order to view the log." But in my case nothing really failed. And if I double-click on the titel just been converted, I get the "meta information", which I don't think will tell you much.

[LoRd_MuldeR]

You can click on "succeeded" items just as well to show the log ;)

(And here I'm talking about the "Processing" window, not about the main window)

[apilonte]

This is the log. Input file: channels=1 (line 8); output file: channels=2 (line 39). Hope you see the reason why a second channel has been created.

Heinrich


LameXP v4.06 (Build #1170), compiled on 2012-11-04 at 13:56:05

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

C:/DOKUME~1/Heinrich/LOKALE~1/Temp/d039e52d80114476ab85d728a3a4a0a0/lxp_sox.exe --i "D:/Heinrich/Eigene Musik/MesseRohrdorfProbe.wav"

Input File : 'D:/Heinrich/Eigene Musik/MesseRohrdorfProbe.wav'
Channels : 1
Sample Rate : 44100
Precision : 24-bit
Duration : 01:34:29.92 = 250043400 samples = 425244 CDDA sectors
File Size : 750M
Bit Rate : 1.06M
Sample Encoding: 24-bit Signed Integer PCM

Exited with code: 0x0000

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

--> Number of channels is: 1

C:/DOKUME~1/Heinrich/LOKALE~1/Temp/d039e52d80114476ab85d728a3a4a0a0/lxp_sox.exe -V3 -S --guard --temp . "D:\Heinrich\Eigene Musik\MesseRohrdorfProbe.wav" C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\7548e458743848c29fbdc9cc9c8e4121.wav channels 2

C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe: SoX v14.4.0
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO formats: detected file format type `wav'
Input File : 'D:\Heinrich\Eigene Musik\MesseRohrdorfProbe.wav'
Channels : 1
Sample Rate : 44100
Precision : 24-bit
Duration : 01:34:29.92 = 250043400 samples = 425244 CDDA sectors
File Size : 750M
Bit Rate : 1.06M
Sample Encoding: 24-bit Signed Integer PCM
Endian Type : little
Reverse Nibbles: no
Reverse Bits : no
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO sox: Overwriting `C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\7548e458743848c29fbdc9cc9c8e4121.wav'
Output File : 'C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\7548e458743848c29fbdc9cc9c8e4121.wav'
Channels : 2
Sample Rate : 44100
Precision : 24-bit
Duration : 01:34:29.92 = 250043400 samples = 425244 CDDA sectors
Sample Encoding: 24-bit Signed Integer PCM
Endian Type : little
Reverse Nibbles: no
Reverse Bits : no
Comment : 'Processed by SoX'
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO sox: effects chain: input 44100Hz 1 channels
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO sox: effects chain: gain 44100Hz 1 channels
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO sox: effects chain: channels 44100Hz 2 channels
C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\lxp_sox.exe INFO sox: effects chain: output 44100Hz 2 channels
Done.

Exited with code: 0x0000

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

C:/DOKUME~1/Heinrich/LOKALE~1/Temp/d039e52d80114476ab85d728a3a4a0a0/lxp_flac.exe -7 --channel-map=none -T title=MesseRohrdorfProbe -T "comment=Encoded with LameXP" -T track=1 -f -o "D:\Heinrich\Eigene Musik\MesseRohrdorfProbe (3).flac" C:\DOKUME~1\Heinrich\LOKALE~1\Temp\d039e52d80114476ab85d728a3a4a0a0\7548e458743848c29fbdc9cc9c8e4121.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.
7548e458743848c29fbdc9cc9c8e4121.wav: WARNING: skipping unknown sub-chunk 'fact' (use --keep-foreign-metadata to keep)
7548e458743848c29fbdc9cc9c8e4121.wav: wrote 425447346 bytes, ratio=0,284

Exited with code: 0x0000

[LoRd_MuldeR]

Okay, I had a quick look and it turns out that the FLAC encoder class does not have 1 channel (mono) in the list of supported channel counts.

Consequently the input will be up-converted to 2 channels (stereo), before it is sent to the FLAC encoder.

Unfortunately I'm not quite sure whether I omitted 1 channel (mono) intentionally in the list of supported channel counts for FLAC or just forgot it :confused:

Anyway, I will do some more testing when I have more time...

[apilonte]

I will do some more testing when I have more time...

Thank you. Would be nice if you could find some minutes to look after it.

Heinrich