Version 1.0 of BonkEnc is finally available! After five years of development this marks a great milestone for the BonkEnc project. The new release includes lots of bug fixes and some minor updates:
- support for keeping image tags when converting from FLAC to MP3
- support for CD ripping using the command line interface
- updated encoders: FLAC 1.1.4, FAAC 1.25, Ogg Vorbis aoTuV b5
- new translations: Romanian, Lithuanian
Download the new release at http://www.bonkenc.org/ (http://www.bonkenc.org/)
Enzo
Congratulations for the v1.0 release!
I really like your program and I'm looking forward to the future development. :-)
@enzo
I got some thought about the encoder setup interface:
For the "normal" user it's difficult to set the Encoder options.
I like that you can edit a lot of settings! Maybe you could add a button for expert settings? So the "normal" interface could have less settings (for the normal user).
For ideas have a look. in the Winamp encoder setting (MP3 / LC-AAC). They are really user friendly and easy to understand.
The FLAC encoder interface is alright. Maybe you could add a checkbox for the verify option?
I'm not sure if you already planed it. But maybe it's possible to change it?
Thanks for the development of BonkEnc!!!
Ps.: Maybe you have a idea for the recommended Bonk format settings (http://wiki.hydrogenaudio.org/index.php?title=BonkEnc#Recommended_Settings) for the Wiki?
Hmm, I have a question and a bug report. First, I like your app. I think it makes file coversion somewhat simpler than my first app or choice, fb2k. Keep in mind I'm demoing different apps with the people I work with in mind. fb2k is just too complex for them, so I've been trying out stuff like OmniEncoder and BonkEnc. Ok, so on to the important stuff -
Question -
Is it possible to use source directory information in the titleformatting to produce output directories/filename? fb2k accomplishes this via strings like $directory(%path%,1) which would extract the parent directory of the file, or $directory(%path%,2) which would extract the parent of the parent (2 dirs up). This is great for mirroring directory structures, etc.
Bug -
Encoder preset settings for LAME (possibly others, but untested) are goofed. The presets are not configuring all the encoder settings as they should.
For example -
Preset 'Extreme, fast' should equate to '-V 0 --vbr-new' as passed to lame.exe. However when I try it, it is using whatever the last VBR/CBR setting was as set in 'Custom Settings'. Basically if I have CBR 160 set in 'Custom Settings', then switch over to preset 'Extreme, fast', the resulting mp3 is encoded at CBR 160. I'm getting this info from fb2k->properties. I don't know how to check all the other advanced custom settings, but they might be wrong as well. The presets should only pass the minimum number of LAME developer recommended switches to the encoder, ie simply '-V 0 --vbr-new'.
It seems something is goofed with 'Custom Settings' and tagging as well. I converted a WAV to MP3 with custom settings for VBR mtrh (I'm assuming this is --vbr-new???) quality 0, tagged with id3v1 and 2 (no vorbis or ape tags) based off info I manually typed in.
What I got was a 160 CBR mp3 with unrecognized character boxes instead of tag info, and only a id3v2 tag.
I plan to have a completely new configuration dialog in v1.1. I think about having presets for all encoders where it makes sense.
Is it possible to use source directory information in the titleformatting to produce output directories/filename? fb2k accomplishes this via strings like $directory(%path%,1) which would extract the parent directory of the file, or $directory(%path%,2) which would extract the parent of the parent (2 dirs up). This is great for mirroring directory structures, etc.
This not possible yet, but I plan to add it in BonkEnc v1.1. I originally planned to have this feature in v1.0, but then had to delay it, because I didn't have time to implement it.
Encoder preset settings for LAME (possibly others, but untested) are goofed. The presets are not configuring all the encoder settings as they should.
For example -
Preset 'Extreme, fast' should equate to '-V 0 --vbr-new' as passed to lame.exe. However when I try it, it is using whatever the last VBR/CBR setting was as set in 'Custom Settings'. Basically if I have CBR 160 set in 'Custom Settings', then switch over to preset 'Extreme, fast', the resulting mp3 is encoded at CBR 160. I'm getting this info from fb2k->properties. I don't know how to check all the other advanced custom settings, but they might be wrong as well. The presets should only pass the minimum number of LAME developer recommended switches to the encoder, ie simply '-V 0 --vbr-new'.
I'll have a look at it. Seems weird to me, because if you set a preset, BonkEnc will make just one call to lame_set_preset and nothing more. For example for Extreme, fast:
lameFlags = lame_init();
lame_set_preset(lameFlags, EXTREME_FAST);
But maybe there's something else wrong.
These are actually two bugs. Both are fixed already in CVS and for the 1.0.1 release. The first one is that ID3v1 tags are not written correctly in VBR mode. The second one is that ID3v2 tags are not written correctly when the encoding is set to UTF-16LE and iconv.dll is not available.
To work around the second bug, get the file iconv.dll from the BonkEnc 1.0 zip package and copy it to your BonkEnc directory or reinstall BonkEnc with "International language support" selected in the installer.
Does anyone know how the Ogg Vorbis quality setting in Bonkenc relates to the more common Q -1 to 10 scale?
Since the Bonkenc quality scale goes from -0.1 to 1.0, you'd assume that you should just multiply by 10, but that doesn't seem to be the case.
When I encode songs with Bonkenc set to quality 0.4, it produces songs averageing 140-150 kbps, as opposed to ~128 kbps...
When I encode songs with Bonkenc set to quality 0.4, it produces songs averageing 140-150 kbps, as opposed to ~128 kbps...
Look at the nominal bitrate, not the actual one. When I specify -q5 with the normal encoder (oggenc2), I get an average bitrate that is not 160kbps, but the nominal bitrate is 160kbps.
So in your case, the nominal bitrate should be exactly 128kbps. In Winamp, the nominal bitrate is shown in the tags dialog (Alt+3).
When I encode songs with Bonkenc set to quality 0.4, it produces songs averageing 140-150 kbps, as opposed to ~128 kbps...
Look at the nominal bitrate, not the actual one. When I specify -q5 with the normal encoder (oggenc2), I get an average bitrate that is not 160kbps, but the nominal bitrate is 160kbps.
Thanks for the tip. However, it prooved me right I have to set Bonkenc to 0.3 to get Q4, or nominal 128kbps.
Thanks for the tip. However, it prooved me right I have to set Bonkenc to 0.3 to get Q4, or nominal 128kbps.
The quality value 0.30 equals -q3, 0.40 equals -q4 and so on. Simply multiply the BonkEnc quality setting by 10.
I just tested it, just to be sure, and I get (nominal) 112kbps with 0.30 and 128kbps with 0.40. Maybe you accidentially set something like 0.39 instead of 0.30. 0.39 will give you a nominal bitrate of 126kbps.
Btw. BonkEnc v1.0.1 has been released today.
BonkEnc v1.0.2 has been released. It includes translation updates, installer improvements and fixes some minor bugs.
Get it at BonkEnc.org (http://www.bonkenc.org/).
BonkEnc v1.0.2 has been released. It includes translation updates, installer improvements and fixes some minor bugs.
Get it at BonkEnc.org (http://www.bonkenc.org/).
Hi enzo,
Please check this thread out: http://www.hydrogenaudio.org/forums/index....showtopic=54415 (http://www.hydrogenaudio.org/forums/index.php?showtopic=54415). The current BoncEnc version seems to have a tagging problem.
I added a new FLAC sample file to my "embedded cover art samples" thread: http://www.hydrogenaudio.org/forums/index....st&p=487587 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=40860&view=findpost&p=487587).
An MP3 file which is converted from this sample with BonkEnc has only the following MP3 tags:
Album: Rating=5 (an incorrect tag value)
Artist: Who Knows
Genre: House
Title: Rating=5 (an incorrect tag value)
Year: 2002
Perhaps the BonkEnc developer finds the sample useful.
I just tried converting the sample with BonkEnc v1.0.2. The result is as follows:
[blockquote]TPE1 = Who Knows
TIT2 = 4s sample for testing embedded cover art
TALB = RATING=5
TRCK = 05
TYER = 2002
TCON = House
COMM = BonkEnc v1.0 <http://www.bonkenc.org/>
APIC = (JPEG image containing the HA logo)[/blockquote]There is a bug in BonkEnc's matching algorithm for Vorbis comment tags (as used by FLAC) thus making the value for album "RATING=5". I will fix that in the next release.
However, BonkEnc keeps the picture here. There is an option named "CopyPictureTags" in BonkEnc's config.xml file. It's enabled by default, maybe it has somehow been disabled in your configuration.
Other tags are not currently supported by BonkEnc. That's why most of the tags in the sample file get lost when converting. BonkEnc v1.1 will feature a complete tag editor and will support all tags.
Hmm, as I said my result was a bit different. Possibly my settings are wrong. However, I just downloaded the program today and only changed the GUI options to what seemed appropriate.
I uploaded the converted MP3 file and my config.xml file here: http://www.hydrogenaudio.org/forums/index....st&p=487587 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=40860&view=findpost&p=487587)
Hmm, as I said my result was a bit different. Possibly my settings are wrong. However, I just downloaded the program today and only changed the GUI options to what seemed appropriate.
I uploaded the converted MP3 file and my config.xml file here: http://www.hydrogenaudio.org/forums/index....st&p=487587 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=40860&view=findpost&p=487587)
Ah, the problem here is that you enabled the "Encode to single file" option. This is used to encode multiple tracks to a single audio file. In this case BonkEnc will use the album name for the title field which makes sense when you are encoding an album to a single file.
Ah, the problem here is that you enabled the "Encode to single file" option. This is used to encode multiple tracks to a single audio file. In this case BonkEnc will use the album name for the title field which makes sense when you are encoding an album to a single file.
I see. I didn't understand the option correctly. Without the "encode to single file" option conversion works as you described. Cover art is included and the only problem is with the Album tag.
Your program seems to be a nice tool. I am looking forward to seeing further development in the tagging area.
I have the new version of this and I have been trying to use this program for some time now to convert FLAC to mp3. I find this program very frustrating to use because there is so much involved in the "expert settings" that are not explained and I can't find any sort of manual anywhere that explains these things. If I don't use one of the custom settings to encode, there are several VBR options and quality settings with no explanation so I have no idea what these actually produce when I convert to mp3 format.
Also, I tried one of the "presets" in the drop-down menu, I believe it was the "medium-fast" setting for LAME and it gave me an mp3 file with a VBR that moves up and down + or - 5 kbps!! No clue what is going on here, but that's not even close to what I wanted. Is there some sort of manual or something that goes along with this program so I have even kind of a clue as to what some of the settings do?
I have the new version of this and I have been trying to use this program for some time now to convert FLAC to mp3. I find this program very frustrating to use because there is so much involved in the "expert settings" that are not explained and I can't find any sort of manual anywhere that explains these things. If I don't use one of the custom settings to encode, there are several VBR options and quality settings with no explanation so I have no idea what these actually produce when I convert to mp3 format.
Well, as the name suggests "expert settings" are mainly for experts so if you don't understand them you should not worry about them and leave them untouched. In general it's a good idea to use one of the presets for LAME or, if you want CBR encoding, simply select the desired bitrate and leave other settings at their default values. If you want VBR and you don't want to use the presets, select "VBR mtrh" and use the slider to set the desired quality level.
Also, I tried one of the "presets" in the drop-down menu, I believe it was the "medium-fast" setting for LAME and it gave me an mp3 file with a VBR that moves up and down + or - 5 kbps!! No clue what is going on here, but that's not even close to what I wanted. Is there some sort of manual or something that goes along with this program so I have even kind of a clue as to what some of the settings do?
There's just a brief tutorial available currently. You can find it in the program's help menu under "Help topics". However, it does not explain the LAME settings in detail. There are lots of guides to LAME settings available on the internet. Take a look at them if you need detailed descriptions for the various LAME options.
Well I am definitely not a noob to LAME by any means. I have been coming to these forums for a very long time. I have a very good working understanding of the settings of LAME and such but I really don't understand what is happening when I am selecting a "preset" in the program that is supposed to give me a certain result and I am not getting that result. If I am choosing the "medium" preset, I am supposed to be getting these parameters in the resulting mp3 file.... a target bitrate of 165 kbps VBR with a range of 145-185 kbps VBR. The resulting files are giving me a bitrate that fluctuates between 160-165 kbps. This is not making any sense to me, because whenever I use EAC with LAME at this setting, I get the parameters that I mentioned above and the bitrate goes up and down in the intervals that we all know and love (i.e. 128, 160, 192 etc.).
I have no idea why this is doing this, but I certainly would like to know...
I agree! I love the program and the portability but the setting layouts for the encoder are awfull in BonkEnk. Not just the lame settings aren't really beginners friendly.
That is an easy and nice example:
(http://s6.bilder-hosting.de/tbnl/7HR4C.jpg) (http://www.bilder-hosting.de/show/7HR4C.html)
You could have an "advanced options" button for the other setting.
Just a suggestion!
keep up the great work!
Maybe a Bug:
I just checked a new created Mp3 (BoncEnc v1.0.2, preset "Standart" and others) file with MP3val (http://www.hydrogenaudio.org/forums/index.php?showtopic=53341).
I got this error with all created Mp3 files:
"Wrong number of MPEG data bytes specified in Xing header"
So I guess that should be checked out.
If I am choosing the "medium" preset, I am supposed to be getting these parameters in the resulting mp3 file.... a target bitrate of 165 kbps VBR with a range of 145-185 kbps VBR. The resulting files are giving me a bitrate that fluctuates between 160-165 kbps. This is not making any sense to me, because whenever I use EAC with LAME at this setting, I get the parameters that I mentioned above and the bitrate goes up and down in the intervals that we all know and love (i.e. 128, 160, 192 etc.).
I really don't know why you would get such results. I just performed some tests just to be sure and BonkEnc with preset "Medium" gave me just the same result as "lame --preset medium". An average bitrate of 152 kbps with the bitrate going up and down between 96 and 192 kbps.
The MP3 stream (without any headers and tags) is bit by bit identical in the BonkEnc and LAME encoded files (with both being compiled with the same compiler).
Maybe a Bug:
I got this error with all created Mp3 files:
"Wrong number of MPEG data bytes specified in Xing header"
BonkEnc uses the function "lame_mp3_tags_fid" to create the Xing header so if that header is wrong it should be fixed in LAME.
However, the file already has ID3v1 and v2 tags when BonkEnc calls that function and that seems to be the problem. So I can probably fix this by writing the tags after LAME created the Xing header.
I really don't know why you would get such results. I just performed some tests just to be sure and BonkEnc with preset "Medium" gave me just the same result as "lame --preset medium". An average bitrate of 152 kbps with the bitrate going up and down between 96 and 192 kbps.
The MP3 stream (without any headers and tags) is bit by bit identical in the BonkEnc and LAME encoded files (with both being compiled with the same compiler).
Okay, an update...
I went ahead and tried to encode the FLAC files to mp3 again using the "Medium" preset and it looks like it came out okay this time. So, I have no idea what happened initially, but it appears to be giving me the result that I am looking for now.
I went ahead and tried to encode the FLAC files to mp3 again using the "Medium" preset and it looks like it came out okay this time. So, I have no idea what happened initially, but it appears to be giving me the result that I am looking for now.
Ok, nice to hear! Thanks for the info!
I got this error with all created Mp3 files:
"Wrong number of MPEG data bytes specified in Xing header"
I fixed it in LAME and submitted a bug report and patch to the LAME project.
The bug report (http://sourceforge.net/tracker/index.php?func=detail&aid=1711980&group_id=290&atid=100290), the patch. (http://sourceforge.net/tracker/index.php?func=detail&aid=1711981&group_id=290&atid=300290)
Btw. this will be fixed in BonkEnc v1.0.3 of course.
I'm just curious. Any news in the development for the next version? (Any date?)
I'm just curious. Any news in the development for the next version? (Any date?)
I originally planned to release v1.0.3 last weekend, but I didn't have the time to do it.
The VBR-MP3 bug will be fixed in v1.0.3 and the release will add support for files on network volumes. In addition I will try to make error messages more clear. The current versions only says "Cannot open file ..." when a file cannot be opened for some reason. v1.0.3 will include more detailed information like "Access denied", "Unsupported file format", "File not found" etc.
There have been some reports about crashes when converting FLAC to MP3 recently. I will have a look at it and will try to fix it before the release of BonkEnc v1.0.3.
In the v1.1 development line I'm currently working on specifying the new plug-in architecture (named BoCA, BonkEnc Component Architecture). More specifically I'm building a BonkEnc component SDK. However, there's not much progress as of yet.
BonkEnc v1.0.3 is now available from bonkenc.org (http://www.bonkenc.org/)!
Thanks man! Now the mp3 creating works fine. :-)
edit:
Somthing must be wrong with the copying of embedded pictures from FLAC to Mp3.
I can see the embedded pictures with Mp3tag (http://wiki.hydrogenaudio.org/index.php?title=MP3tag) v2.38 and with the Toaster plugin for Winamp. But not with AudioShell (http://www.softpointer.com/AudioShell.htm) v1.3.5. Everything works fine when I save the tags again with Mp3tag.
So I guess somthing is wrong how BonkEnc. v1.0.3 includes the Covers to the mp3 file.
Somthing must be wrong with the copying of embedded pictures from FLAC to Mp3.
I can see the embedded pictures with Mp3tag (http://wiki.hydrogenaudio.org/index.php?title=MP3tag) v2.38 and with the Toaster plugin for Winamp. But not with AudioShell (http://www.softpointer.com/AudioShell.htm) v1.3.5. Everything works fine when I save the tags again with Mp3tag.
This is a problem with AudioShell. It seems to get confused with empty picture descriptions encoded in Unicode.
The same problem exists in iTunes, maybe both programs are using the same ID3 tag library. See this post (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=54415&view=findpost&p=489327) for more information. I have already submitted a bug report to Apple.
There is a description field in every ID3v2 picture frame. BonkEnc uses Unicode by default to encode the description. If the description is not empty, iTunes will read it and everything works fine. However, if the description is empty (the usual case), iTunes is confused and refuses to accept the picture frame.
A workaround is to set the ID3v2 tag encoding in BonkEnc to something other than UTF-16LE or UTF-16BE (UTF-8 would work with iTunes, but WMP does not support it; so ISO-8859-1 is really the only choice).
I save my tags in Mp3tag with UTF-16. And it works fine with AudioShell. And I use the same (UTF-16LE) in BoncEnc.
So I still guess it's about BoncEnc v1.0.3 ;-)
Correct me if I'm wrong!
I save my tags in Mp3tag with UTF-16. And it works fine with AudioShell. And I use the same (UTF-16LE) in BoncEnc.
So I still guess it's about BoncEnc v1.0.3 ;-)
Even if you select UTF-16 in Mp3tag it will save picture descriptions as ISO-8859-1.
I made the following test to confirm this:
- Added a picture description with ID3-TagIT. It saved it in UTF-16.
- Saved the tag again with Mp3tag. It kept everything in UTF-16, except the picture description which it converted to ISO-8859-1.
Btw. you should be able to reproduce the problem (in AudioShell and iTunes) using ID3-TagIT as it seems to save tags the same way BonkEnc does.
Even if you select UTF-16 in Mp3tag it will save picture descriptions as ISO-8859-1.
Ok, thanks for testing!
Maybe BonkEnc could do the same in a future release? At least optional?
BonkEnc users, here is the link for the BonkEnc version of LAME 3.98 beta4 (http://www.verzend.be/v/8504263/LAME_3.98_beta4_BonkEnc.zip.html)
Includes history.html and Read Me.....
thanx to Robert Kausch
source (http://www.bonkenc.org/updates/LAME-3.98-beta4.zip)
This link maybe won't be available in the future, that why it's uploaded
BonkEnc v1.0.4 is out now! It fixes some minor bugs and includes translation updates.
Yout can download the new version from bonkenc.org (http://www.bonkenc.org/).
BonkEnc v1.0.4 is out now! It fixes some minor bugs and includes translation updates.
Yout can download the new version from bonkenc.org (http://www.bonkenc.org/).
Thanks for the new release!
Just one question. What advantage has the "NT-SCSI-DLL" option?
Just one question. What advantage has the "NT-SCSI-DLL" option?
Some people reported that BonkEnc detected only virtual CD drives in ASPI mode. The problem was solved by enabling NT SCSI mode.
The problem with ASPI is that there are lots of different ASPI drivers out there. Some of them seem to cause weird problems for applications like BonkEnc. The NT SCSI driver is the same everywhere and there don't seem to be such issues.
Version 1.0.8 of BonkEnc has been released today.
It now comes with LAME 3.98 and aoTuV Beta 5.5.
Further changes:
- preset 'Standard' is now the default for LAME encoding
- label/publisher and ISRC information is now preserved during conversion
- fixed quality level display in Vorbis encoder configuration
- fixed random crashes at program exit
Is this now the preferred ripper/encoder for those that used CDex and EAC before?
Is this now the preferred ripper/encoder for those that used CDex and EAC before?
For me it is . I have replaced my CDex with BonkEnc and am completely satisfied.
IMHO this is the best alternative to EAC, for people who want an easy-to use program
which just works (without the need of reading extensive config guides and setting too many options).
Thank you Robert for this little gem !
I released BonkEnc version 1.0.9 yesterday.
It updates LAME to version 3.98.1 (released on CVS only) to fix an issue with frequency filtering (LAME bug #2029282) and includes a reworked LAME configuration dialog which should reduce confusion about VBR settings and allows decimal values for VBR quality.
Further changes:
- updated Serbian, Polish and Swedish translations
- upgraded cdparanoia III to version 10.2
- fixed handling of comments in metadata
- various other bug fixes
I just released BonkEnc v1.0.10.
LAME has been updated to version 3.98.3 and Ogg Vorbis to aoTuV Beta 5.61.
Further changes:
- updated Japanese, Serbian, Norwegian and Spanish (Latin American) translations
- added an option to replace existing comments with default comment (old behaviour from before 1.0.9)
- added "encode to single file" checkbox to main window
- total length of all tracks in joblist is now shown above the joblist
- various bug fixes
Great software, but I would love cue support for flac and ape albums to cut them up in individual mp3s. Until then gotta keep EAC and Monkey's Audio on my PC.
I just released BonkEnc v1.0.11.
Changes:
- updated Italian, Serbian and Swedish translations
- added <directory> pattern to allow preserving existing directory structures
- fixed handling of non-ASCII characters when opening MP3 files with multiple tags
- fixed ID3lib to read and write correct ID3v2.4 tags
- fixed error resulting in not decoding FLAC files to the end in some situations
- fixed error opening large MP4 files
- upgraded FAAC to version 1.28
- upgraded FAAD2 to version 2.7
- upgrade to MP4v2 v2.0 alpha (to fix the issues with large files)
The new <directory> file name pattern implements an often requested feature. It allows to rebuild an existing subdirectory structure in the output directory. Its usage is explained in the "How to ...?" section of the manual.
You can get the new release from bonkenc.org (http://www.bonkenc.org/).
Great software, but I would love cue support for flac and ape albums to cut them up in individual mp3s. Until then gotta keep EAC and Monkey's Audio on my PC.
This will be supported in BonkEnc v1.1 - not in the near future, though.
BonkEnc v1.0.13 is available for download now.
It adds the multicore optimized encoders discussed in this thread (http://www.hydrogenaudio.org/forums/index.php?showtopic=73092). Besides that, the new release includes translation updates and some bug fixes.
You can download it from bonkenc.org (http://www.bonkenc.org/).