IMO, senseless transcoding of lossy to lossless should be disabled in programs like this, perhaps helping to reduce the number of people who may believe that there is something to gain from doing so. This isn't anything against your program - just a general point.

IMO, senseless transcoding of lossy to lossless should be disabled in programs like this, perhaps helping to reduce the number of people who may believe that there is something to gain from doing so.

I couldn't have said it better myself. Why even give the idiots a tool with which to create "lossless" files which aren't lossless at all? I truly think that the ignorant and uninitiated believe that when they convert MP3 to lossless they are "decompressing" the MP3. Arrrrgggggh!

One more suggestion, maybe you can add an option to view the cover art in ID3 and FLAC Tags?And to manipulate them manually would be great as well. ;-)

This will be supported in BonkEnc v1.1 which will feature a complete tag editor. You will be able to edit all ID3v2, Vorbis Comment and MP4 metadata fields and it will be possible to save the tags back to the original files.

QUOTE (gottkaiser @ Feb 6 2007, 13:31)

One more question: Wy do you distinguish UTF-16BE and UTF-16LE for the ID3v2 tag encoding?What is the difference?

The difference is in the byte order. In UTF-16BE the most significant byte of a character comes first while in UTF-16LE the least significant byte is first.

BonkEnc uses UTF-16LE by default as it is compatible with the ID3v2.3 standard. UTF-16BE was added in ID3v2.4 which is not supported by all players (e.g. not by Windows Media Player).

Do you think of implementing multi core support?So that it would be possible to encode differnet songs simultaneously on the different cores to save time.Somthing like in "dBpoweramp Music Converter R12".Don't know how difficult it is to implemt this feature. But woulkd be nice to have it in future.

Version 1.1 will have multi core support. It will be possible to convert multiple files and to encode to different formats simultaneously.

For CD ripping, encoding multiple tracks at once will be supported only if you have multiple CD drives and are ripping more than one disc. It just makes no sense to encode multiple tracks from one disc at the same time, because the drive would need to seek all the time.

Sometimes I do weird things just for compression testing purposes, or for example distributing lossy-compressed samples in FLAC format for an ABX test. Don't disable the feature, just add a warning.

I do think there are some possible uses for the feature. So a warning should be fine. However, the warning needs to be BIG AND BOLD so that the idiots don't actually believe that they are magically converting lossy files to lossless files. Something along the lines of ATTENTION - YOU ARE ABOUT TO CONVERT A LOSSY COMPRESSED FILE TO A LOSSLESS FORMAT WHICH DEFEATS THE ENTIRE PURPOSE OF USING LOSSLESS ENCODING! might be sufficient. But then, considering some of the goofballs I've met on the internet who knows? They'll probably just ignore the warning. But hey, at least it's an attempt to keep lossless files from being diluted with bad encodes, albeit a weak attempt.