HydrogenAudio

foobar2000 v0.9.4 beta 1 is available.

Download at http://foobar2000.org/beta/ (http://foobar2000.org/beta/)

Changelog?

changelog:

0.9.4

    * Properties dialog improvements
    * Startup/shutdown speed optimizations
    * Added LAME version and partial settings detection for MP3 files
    * Replaced old “Fix MP3 Header” command with a new set of MP3-related utility commands
    * “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations
    * “Copy” button in components list
    * freedb support now included with the installer
    * Rewritten embedded cuesheet metadata handling
    * Rewritten ReplayGain info editor dialog

Changelog?

From http://foobar2000.org/changelog.html (http://foobar2000.org/changelog.html)

Properties dialog improvements
Startup/shutdown speed optimizations
Added LAME version and partial settings detection for MP3 files
Replaced old “Fix MP3 Header” command with a new set of MP3-related utility commands
“ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations
“Copy” button in components list
freedb support now included with the installer
Rewritten embedded cuesheet metadata handling
Rewritten ReplayGain info editor dialog

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

WoW me 

I'm glad to see ID3 v2.3 support in 0.9.

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

WoW me 

I'm glad to see ID3 v2.3 support in 0.9.

How do you know it's ID3v2.3 support?

Quote from: haregoo on 2006-09-06 19:59:40

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

WoW me 

I'm glad to see ID3 v2.3 support in 0.9.

How do you know it's ID3v2.3 support?

Just try it. Then use mp3tag or other tagger to check the version.

Thanks for the ID3v2.3 support!

Awesome!  Can I confirm that external cue sheet support has been changed as well (before I do something stupid to my collection!)?  All the Index 00's are now retained and the additional (previously unsupported) fields are now supported?  I am in the process of embedding those cuesheets but was leaving 0.8.3 around in the meantime.

Thanks!!

• Rewritten embedded cuesheet metadata handling

Oooh, I wonder what it does? Does anyone know? (No, I don't want to try it out myself now... )

Has hell really frozen over?  ID3v2.3 support!  Excellent!

Does "Rebuild mp3 stream" include "Fix vbr mp3 header"? (if being applied on a vbr mp3)

Another question. I don't know if "apply replaygain to mp3 data" is new: This does touch the file. Does it do mp3gain? Why don't you store undo information then?

I'd also like to know what has been changed with regard to cuesheets. Please?

RE:  * Replaced old “Fix MP3 Header” command with a new set of MP3-related utility commands
Can anyone elaborate on that please? Thank you.

Here are the new commands:

(http://img113.imageshack.us/img113/6273/nmptq1.png)

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

* Added LAME version and partial settings detection for MP3 files

Where should that function be ? I don't see anything in the propertities dialog 

* Rewritten ReplayGain info editor dialog

I liked the old layout more, but i don't use that too often anyways...

* Properties dialog improvements

If i open the propertities window for a single file, the text in the field window is auto-wrapping, but for multiple files not. Is this intentional ?
(http://img481.imageshack.us/img481/555/fieldsad6.th.png) (http://img481.imageshack.us/my.php?image=fieldsad6.png)
(Maybe this was in before, i just didn't notice it)

Thanks for the new version, btw !

EDIT:

Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly, i have to open Task manager and end task manually...

Works here under W2KSP4

I have no problem viewing the LAME settings:

(http://img142.imageshack.us/img142/811/jipfr8.png)

OK, i was able to find some MP3s where the 'Tool' field is available. But on the most files encoded by myself with fb2k & LAME 3.97b there's no 'Tool'...
Your propertities windows look different. Are you using a custom windows theme ?

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

With this option activated, i lost my %rating% tags and embedded dynamic lyrics when the file was updated (play_counter).
The plugin "Lyric Show Panel" is unable to write lyrics to file

Quote from: Maurits on 2006-09-06 20:02:52

How do you know it's ID3v2.3 support?

Just try it. Then use mp3tag or other tagger to check the version.

Thanks! I love the sour "common bugs in other software’s ID3v2 implementations" remark by the way. 


Is ID3v2.4 still default? Can't test it here because haven't got a Windows box around right now...

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

With this option activated, i lost my %rating% tags and embedded dynamic lyrics when the file was updated (play_counter).
The plugin "Lyric Show Panel" is unable to write lyrics to file

Geez, that's why you don't use a beta "productively" on your actual music files right away... but rather on copies to see if any of your collected meta data gets lost or transformed in any way.

I think this would be a good time to add "KS: Primary Output Device" to the Output device dropdown list.

Anybody else want this too?

Is ID3v2.4 still default? Can't test it here because haven't got a Windows box around right now...

Yep.

Thanks for properties box improvements, selectable read-only field makes tag edit easier. The copy button works like a charm too. Also it seems startup is a lot faster now for the first run and about 10% faster for any restart.

EDIT:There's percent statistic in the properties dialog if you select multiple files.

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

With this option activated, i lost my %rating% tags and embedded dynamic lyrics when the file was updated (play_counter).
The plugin "Lyric Show Panel" is unable to write lyrics to file

I too lost my LYRICS tags when changing to the "Compatibility" mode (test database though  ).  I am using dug's foo_lyricdb.  The component can find the lyrics for my files, but it will not save it to a tag.  It will work with V2.4 tags though.  Anyone else have this issue?  Would this be a bug in fb2k 0.9.4 beta 1 or with dug's component?

play count unofficial still doesn't work which is a shame. Although I'm tempted to move for the 2.3 support... shame the official playcount doesn't have the options I need yet.

What to do?

One day maybe. 

Peter said something here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=46855&view=findpost&p=415144) about not retaining unsupported fields in id3v2.3 mode. Wonder if that's the reason.

EDIT: Lorraine which option you need, if it's write to tag option then it's already in the official playcount. IIRC someone has already made an unofficial playcount version that work with 0.9.3 (so I guess it also works with 0.9.4) can't dig it with out search though.

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

With this option activated, i lost my %rating% tags and embedded dynamic lyrics when the file was updated (play_counter).
The plugin "Lyric Show Panel" is unable to write lyrics to file

Please file proper bug reports, each of them in a new thread. Otherwise it's impossible for the dev's to keep track of things. (Not to mention the fact that this thread will be closed if you don't  )

citay, you should add a note to the first post about bug reports going to the support forum...

Peter, would you please add a previous/next button if one entry is marked? Now, we have to exit the dialog, mark the next entry, and revisit again...

Peter, would you please add a previous/next button if one entry is marked? Now, we have to exit the dialog, mark the next entry, and revisit again...

There's no previous/next button on purpose (would be bad design afaik). If you want to edit multiple entries just select them and double click or "right click --> edit --> Individual Values" on the fieldname in the properties dialog. You'll be able to enter all the tags one by one for each selected item. That's the way it's supposed to be done.

Request to moderators to move this thread to the general section of the foobar subforum.
Thank you

Request to moderators to move this threhttp://www.hydrogenaudio.org/forums/index.php?act=Post&CODE=02&f=2&t=48037&qpid=428174ad to the general section of the foobar subforum.
Thank you

100% agree with that. It's the first time (http://www.hydrogenaudio.org/forums/index.php?act=Search&CODE=show&searchid=8fd5ca6df3e61283676ad14fb04245e9&search_in=titles&result_type=topics&highlite=%2Bfoobar2000) I ever see a beta version of foobar2000 being validated as new. And there were hundreds beta version of foobar2000 released in the past. This new is simply going against the explicit rules explained by Tigre:

News about software should be submitted for major releases only with important changes (no separate news threads about bugfix releases, language versions etc.)

http://www.hydrogenaudio.org/forums/index....st&p=204188 (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=20857&view=findpost&p=204188)[/color][/s]


EDIT: good decision

Well, EAC V0.95 prebeta 5 is explicitly mentioned in that thread too.

Beta 1 trumps prebeta 5 any day in my book. You might argue that EAC releases are much less frequent than fb2k, but fb2k releases have slowed down too recently.

Quote from: Squeller on 2006-09-07 10:00:39

Peter, would you please add a previous/next button if one entry is marked? Now, we have to exit the dialog, mark the next entry, and revisit again...

There's no previous/next button on purpose (would be bad design afaik). If you want to edit multiple entries just select them and double click or "right click --> edit --> Individual Values" on the fieldname in the properties dialog. You'll be able to enter all the tags one by one for each selected item. That's the way it's supposed to be done.

I know how editing works. This is rather for viewing purposes. To have a quick file information overview over multiple, single files. I mean one by one.

BTW, the percentage thing in multiple files info is nice, but wouldn't it be rather handy to have simply the number of files available instead of percent?

Thanks for fulifilling my request. Im a clean freak forum-wise :$

citay, you should add a note to the first post about bug reports going to the support forum...

Peter, would you please add a previous/next button if one entry is marked? Now, we have to exit the dialog, mark the next entry, and revisit again...

You are totally right. By this I got two to three warnings because of this.

I like the new version. I'll test it further, to see if I can find some quirks. I already posted two crashlogs concerning continuator.

Peter said something here (http://www.hydrogenaudio.org/forums/index.php?s=&showtopic=46855&view=findpost&p=415144) about not retaining unsupported fields in id3v2.3 mode. Wonder if that's the reason.

EDIT: Lorraine which option you need, if it's write to tag option then it's already in the official playcount. IIRC someone has already made an unofficial playcount version that work with 0.9.3 (so I guess it also works with 0.9.4) can't dig it with out search though.

O, you're right. I found it (http://www.hydrogenaudio.org/forums/index.php?showtopic=42625&st=125&p=417705&#) and it works with this version too.  Thank you!

OK, i was able to find some MP3s where the 'Tool' field is available. But on the most files encoded by myself with fb2k & LAME 3.97b there's no 'Tool'...

Strange. I can view the information with files produced by the latest 3.97b3, via foobar2000 or not. Examples:

(http://img234.imageshack.us/img234/8656/m1ah0.th.png) (http://img234.imageshack.us/my.php?image=m1ah0.png)

(http://img212.imageshack.us/img212/544/m2ty3.th.png) (http://img212.imageshack.us/my.php?image=m2ty3.png)

Your propertities windows look different. Are you using a custom windows theme ?

I'm using Windows Classic. In what way does it look different?


Also, does anyone have information about the new cuesheet handling?

(http://img127.imageshack.us/img127/9499/proppn7.th.png) (http://img127.imageshack.us/my.php?image=proppn7.png)
No Tool here, while it was encoded with LAME 3.97b2 for sure. But i was able to dig up some more files where it is shown correctly, so maybe these mp3s are somehow 'different'...
And your propertities window is different probably because i'm using Win2K, i just had no XP around the check it.

Did you try the solution from here (http://www.hydrogenaudio.org/forums/index.php?showtopic=48045&hl=)?

If that doesn't work, perhaps some of your files were encoded differently, e.g. by the LAME DLL instead of the command-line encoder, etc. ?

You are totally right. By this I got two to three warnings because of this.

Those warnings didn't come from me. However, seeing how you openly discuss warnings given by our staff, you are (again, as i see from the warnlogs) in violation of TOS #7: "Further concerns regarding an action should be communicated via a private message to the staff member".

Reload button, arrghhh 
Thanks for the info, i missed that thread somehow, now it's fine

Howdy,
Columns UI still causes Foobar 0.9.4 Beta 1 to crash on Vista RC1. How do I contact the author, so it (hopefully) can be fixed
Thanks

Having no issues so far with the new beta, got a request though.
Someone already requested this in the previous beta period: Having a ComboBox for fields with multiple values in the Properties dialog. That would make the unification of tags much easier.

[TOS7 criticism snipped]

I keep receiving sharing violation errors when trying to add or remove tags from songs that are currntly playing. It appears to have started with the 0.9.4b1. Is anyone else experiencing this problem?

Also, the $info(extrainfo) tag is now gone so to figure out if an MP3 is CBR or VBR it looks like we'll have to start parsing $info(codec_profile).  No big deal but it's a significant change that breaks many trackinfo scripts.

* Startup/shutdown speed optimizations
    * Added LAME version and partial settings detection for MP3 files

Thanks for that, much appreciated.

* Replaced old “Fix MP3 Header” command with a new set of MP3-related utility commands

Probably already asked but... is there a brief guide for dummies explaining when and how those utilities should be used?

Alessandro

Quote from: The Link on 2006-09-07 10:24:25

Quote from: Squeller on 2006-09-07 10:00:39

Peter, would you please add a previous/next button if one entry is marked? Now, we have to exit the dialog, mark the next entry, and revisit again...

There's no previous/next button on purpose (would be bad design afaik). If you want to edit multiple entries just select them and double click or "right click --> edit --> Individual Values" on the fieldname in the properties dialog. You'll be able to enter all the tags one by one for each selected item. That's the way it's supposed to be done.

I know how editing works. This is rather for viewing purposes. To have a quick file information overview over multiple, single files. I mean one by one.

I agree with this here 100% for the same reason. Next/previous buttons are very nice for viewing purposes, especially for looking at the Properties/Properties section. The way metadata editing for multiple selected files is done at the moment is perfect, but it has nothing to do with this request IMHO, since editing and viewing are not related in this case.

A drop-down selection box in case multiple files were selected in order to only see the info for a single track might be nice too: "All, <file #1>, <file #2>,..." but on the other hand might be impossible to handle when an entire database of serveral thousand tracks was selected. So I think simply reselecting the individual tracks in the playlist is best kept the way it is in this case. Only one more thing added to the "Prev/next button" wish: in case multiple tracks were selected pressing the Next/Prev buttons should of course start reselecting the first or last track of a selection and redisplaying its info in the Prop window... that's the default behaviour of a lot of programs with similar buttons.

EDIT: Oh I got another idea. Make the Properties windows update "live" as the user selects files in the playlist. Something similar to the columns UI. At the moment (0.9.3 final) it is possible to "do stuff" outside the properties window when it is open, also reselecting tracks in the playlist, but this has no effect on the info being displayed in the Properties window.

Btw, I guess this should better be split off to a thread in the suggestions subforum because this doesn't discuss this particular beta release directly and was merely a last-minute-request for the final version of 0.9.4 I suppose...

Quote from: GIS on 2006-09-06 23:03:27

Quote

* “ID3v2 Writer Compatibility Mode” with workarounds for common bugs in other software’s ID3v2 implementations

With this option activated, i lost my %rating% tags and embedded dynamic lyrics when the file was updated (play_counter).
The plugin "Lyric Show Panel" is unable to write lyrics to file

Geez, that's why you don't use a beta "productively" on your actual music files right away... but rather on copies to see if any of your collected meta data gets lost or transformed in any way.

It also discards all unsupported and unknown frames. No ReplayGain for you, either. Be thankful you get to keep your embedded album art.

Howdy,
Columns UI still causes Foobar 0.9.4 Beta 1 to crash on Vista RC1. How do I contact the author, so it (hopefully) can be fixed
Thanks

ask musicmusic to fix that. IIRC, columns_ui crashes foobar2000. foobar2000's default plugins and default application do not. but i don't have windows so i can't confirm this.

Howdy,
I sent him a PM. Hope it gets fixed soon. Very frustrating, as I can't use Foobar properly on Vista!

you can use the default interface. it's been doing wonders on my system.

Yes, but it is not what I like. The Columns don't line up as neat.

hi there

the changelog looks quite promising, I don't understand everything though.

I noticed that AMIPwrapper doesn't work here for some reason. a popup says "Unable to load plugin". In the Preferences Dialog, there is an entry called AmipWrapper, but foobar crashes when you click on it.

there is also a problem with columns_ui, or maybe I did something wrong. enabling the columns UI interface makes foobar to one big grey window with nothing in it.. but it seems to work for most of the people here, so maybe it's just me

also, I am a bit confused because of some entries in here. what exactly is new/better with the ID Tags? better compatibility with other players? I understood it like a "downgrade" from V.2.4 to V.2.3, correct me if I'm wrong..
this may be a silly question, but how exactly does this effect an average user who just wants to play songs, Rip CDs, tag and rate his files with foobar?

thank you!

also, I am a bit confused because of some entries in here. what exactly is new/better with the ID Tags? better compatibility with other players? I understood it like a "downgrade" from V.2.4 to V.2.3, correct me if I'm wrong..

I don't think it's a case of 'better'. As the new preference setting states: "non-specification-compliant, slow, activates workarounds for common bugs in other software".

The most common example of why this might be useful is for iTunes, which doesn't cope well with v2.4 tags, but displays v2.3 no problems. So converting and tagging mp3's in foobar with the compatibility mode means that those mp3 tags will display in iTunes.

Yes, but it is not what I like. The Columns don't line up as neat.

since when does the default interface use columns?

since when does the default interface use columns?

It has for quite some time with $tab() -- even 0.8 did it.

Quote from: yong on 2006-09-06 22:04:34

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

Please file proper bug reports, each of them in a new thread. Otherwise it's impossible for the dev's to keep track of things. (Not to mention the fact that this thread will be closed if you don't  )

Ok the bug has comfirmed, cause by foo_dsp_headphones9.dll,
fb2k 0.9.4b1 finally can exit properly after remove this dsp plugin.

I will file a bug report to the plugin author soon

[deleted]

I have a shared music collection, I maintain all the tags in foobar but some people use Media Player to play songs, and every time they do it cocks up the tags (truncates title, album etc., fiddles with genre, removes all my special tags like disc etc.). Will using ID3v2.3 fix this? If so, I'm definately downloading 0.9.4 beta 1, it'll save me a lot of headaches!

It should solve your WMP and truncate title, album, etc problem but about custom tag maybe you will lost them. ID3v2.3 support in 0.9.4b1 only support official field that's listed here (http://wiki.hydrogenaudio.org/index.php?title=Foobar2000:ID3_Tag_Mapping).

The annoying update window is still there 

will you change your version right away when the new version or beta version comes out?

Quote from: Mangix on 2006-09-08 15:20:28

since when does the default interface use columns?

It has for quite some time with $tab() -- even 0.8 did it.

$tab? that's a function. it doesn't really implement columns

$tab() will allow you to simulate columns of text in the default UI if you use it to separate text like this

TEXT1$tab()TEXT2$tab()TEXT3

They are not real columns, there will be no borders for you to resize or anything like that. However, it's rather useful if you want your playlist to appear in columns such as:

%list_index%.$tab()%album artist% - %title%$tab()%length%

btw musicmusic has posted a new beta in the columnsui thread that corrects the incompatibility issues with vista.

Beta 2 is out, mainly in response to a playlist saving bug.

Release highlights:
- fixed playlist writer crash
- other minor fixes

http://www.foobar2000.org/beta/index.html (http://www.foobar2000.org/beta/index.html)

http://foobar2000.org/beta/index.html (http://foobar2000.org/beta/index.html)

Release highlights:
- fixed playlist writer crash
- other minor fixes

I think there was a refresh issue with the properties window which now has been fixed.

Wishlist: When we select multiple files, the properties window provides us with various tech info for multiple files...

e.g.

BS; Lancer [20051118] (based on aoTuV b4a [20051105]) (17.5%); LAME3.98a (7.7%); Xiph.Org libVorbis I 20040629 (1.8%)

At the moment we can see the full info only via a hint. I suggest using the same mechanism as when double clicking a multi value tag (opening a separate window)...

I find repsonse a bit laggy with the new 0.9.4 beta 2 - when i click on a song on the playlist, there is a noticable pause before the track begins to play, and album art also shows the lag. This did not happen with beta 1.

I find repsonse a bit laggy with the new 0.9.4 beta 2 - when i click on a song on the playlist, there is a noticable pause before the track begins to play, and album art also shows the lag. This did not happen with beta 1.

Did you happen to upgrade album art panel around the same time?  The new version (0.2.4) processes all wildcard matches, which would cause a pause like you describe.

yes . . . . did upgrade the album art panel. should i then be using the old version??

downgraded album art panel to 0.2.1b and the lag is gone!! thanks for the info.

downgraded album art panel to 0.2.1b and the lag is gone!! thanks for the info.

Dont downgrade. I had the same problem. Look at this thread (http://www.hydrogenaudio.org/forums/index.php?showtopic=39924&st=675) I had the same issue and the answer was given to me quickly.

The new version of albumart processes all the wildcards so all you have to so is be more specific and add a couple more specific sources so it doesnt get confused

OK. upgraded back to 0.2.4 album art panel and tweaked the source code as suggested. Seems to be working fine and at the moment even the erratic no cover artwork seems to be displaying ok. Will keep my fingers crossed - had some problems with the upgrading and downgrading. An error message said a dll file caused foobar to close itself. But after removing album art panel dll and then adding it again, everything seems to be fine.

Anyway, thanks again musosticky.

Is "Fix vbr mp3 header" a subset of "Rebuild mp3 stream"?

Is "Fix vbr mp3 header" a subset of "Rebuild mp3 stream"?

How would it be? Whereas the first just fixes the headers the second rewrites the whole file (stripping any bad stuff). Hover the mouse over the commands and look in the status bar for more details.

man subset

A = Fix vbr mp3 header
B = Rebuild mp3 stream

Does "rebuild mp3 stream" include "fix mp3 vbr header"?

(http://upload.wikimedia.org/wikipedia/en/thumb/d/d6/Venn_A_subset_B.png/150px-Venn_A_subset_B.png)

The question is, if I have e.g. time calculation problems in an mp3 and perform the rebuild mp3 stream function, I will probably not have to "fix the vbr header"?

EDIt: typo

No.

The question is, if I have e.g. time calculation problems in an mp3 and perform the rebuild mp3 stream function, I will probably not have to "fix the vbr header"?

No.

Hm, well, yes. Thanks for clearing this up.

Ah, fb2k devs. Abrupt as ever. I love it.

Is that "No" as in "No, you won't have to fix it" or "No, the assumption that you won't have to fix it is wrong"?

Any chance 0.9.4 could allow you to set the number of rereads to perform, when a crc mismatch is found during a cd rip?

Long time user, first time caller.

I know at least a dozen people are taken aback by the 'Updating Files -> Processing' popup that foobar 0.9 has when dealing with ID3 tags. This is particularly frustrating when using the official playcount plugin, with the 'synchronize with id tags' option enabled, as every song pops up this dialogue.

Is it possible to include an option to 'disable' this popup. Particularly the fact it's popping up even if foobar is minimized to the system tray.

This minor issue, for some, is a major issue stopping people from moving from 0.8 -> 0.9

Just thought I'd mention it.

Long time user, first time caller.

I know at least a dozen people are taken aback by the 'Updating Files -> Processing' popup that foobar 0.9 has when dealing with ID3 tags. This is particularly frustrating when using the official playcount plugin, with the 'synchronize with id tags' option enabled, as every song pops up this dialogue.

Is it possible to include an option to 'disable' this popup. Particularly the fact it's popping up even if foobar is minimized to the system tray.

This minor issue, for some, is a major issue stopping people from moving from 0.8 -> 0.9

Just thought I'd mention it.

How come I don't see the pop-up everyone is complaining about? I'm using 0.9.4 Beta 2 and the official Playback Statistics plugin. The pop-up did occur when I first upgraded to 0.9.x but since 0.9.3 final version, it has not appeared.

Have you got it set to synchronise the tags with the database? Or whatever the setting was...I changed to the unofficial version so I could set the point at which the tags were written i.e not halfway through the bloody song

Yes, set to sync automatically. And yes, cannot control when it decides to write the tags. I used the unofficial version for a while and have some issues with it on 0.9.3 - though I can't remember what it was.

Switching over to using this version of Playback Statistics has its problems like a different tag name and the coded timestamp. But that's a issue discussed on another thread (http://www.hydrogenaudio.org/forums/index.php?showtopic=46582&st=0)

Ah, fb2k devs. Abrupt as ever. I love it.

Is that "No" as in "No, you won't have to fix it" or "No, the assumption that you won't have to fix it is wrong"?

You think too much. 

Yeah the issues were the incompatibility with v0.9.3 onwards but that was fixed shortly. You should venture back in my opinion its worth it just to determine when the tags are applied and you can use the masstagger to change the field names for playcounting.

You think too much. 

I get confused easily by double-negatives and the like.  The developers' oft-minimalist approach to communication doesn't always help.

Yeah the issues were the incompatibility with v0.9.3 onwards but that was fixed shortly. You should venture back in my opinion its worth it just to determine when the tags are applied and you can use the masstagger to change the field names for playcounting.

Well, actually i have set Foobar to read both play_counter and play_count. Anyway, once the track is played, the Playback Statistics re-writes the tag into the new format while preserving the actual count - so i figure at some point when all the tracks have been played under the new plugin, all the tags will be updated.

Ah, fb2k devs. Abrupt as ever. I love it.
Is that "No" as in "No, you won't have to fix it" or "No, the assumption that you won't have to fix it is wrong"?

Yes, probably no.  Well, if mp3 stream rewriting and tag writing both are deterministic, we could do exact comparison of files to get the answer.

beta3. (http://www.foobar2000.org/beta/index.html)

Release highlights:
- ABX bugfixes
- Added WMA tag editing support

beta3. (http://www.foobar2000.org/beta/index.html)

Quote

Release highlights:
- ABX bugfixes
- Added WMA tag editing support

Ive just tried beta 3 and WMA tag editing does not appear to be working.

[/quote]
Ive just tried beta 3 and WMA tag editing does not appear to be working.
[/quote]

I created a test file with WMP11 beta 2 and for me it works.

Deleted foo_input_std and installed over the top again and its now working. I think something may of just gone wrong when i installed the first time round.

Edit:And now its not working, just had 2 crashes whilst tagging the same set of WMA's

Illegal operation:
Code: C0000005h, flags: 00000000h, address: 0B703FF2h
Access violation, operation: read, address: 0AA63D70h
Call path:
entry=>app_mainloop
This is the first crash logged by this instance.
Code bytes (0B703FF2h):
0B703FB2h:  1A 7A FF FF 8B F0 85 F6 89 75 FC 0F 84 F6 7F FF
0B703FC2h:  FF FF 46 04 8B 46 04 3B 47 10 0F 84 00 83 FF FF
0B703FD2h:  8D 45 FC 50 53 8B CF E9 BD 7F FF FF 8B FF 55 8B
0B703FE2h:  EC 8B 45 08 8B 48 34 8B 55 08 8B 42 34 8B 09 50
0B703FF2h:  FF 51 40 5D C2 04 00 6A 28 E8 B4 75 FF FF 85 C0
0B704002h:  59 0F 84 0D FE 03 00 8B C8 E8 21 00 00 00 85 C0
0B704012h:  89 45 FC 0F 84 28 19 06 00 89 70 20 8B 06 56 FF
0B704022h:  50 04 8B 45 08 8B 4D FC 89 08 E9 8D C0 FF FF 33
Stack (0012F474h):
0012F454h:  85BE5584 BF82AD00 B8313B80 B8313B80
0012F464h:  BF800B3B 84723020 BF82AE47 BBF42DF8
0012F474h:  0B041688 0012F494 0B71CDF7 0B0670D0
0012F484h:  0034A0E0 0034C4E8 0034A110 0034F998
0012F494h:  0012F4AC 0B71D5F6 00000000 0B0670D0
0012F4A4h:  0034C510 0012F5F0 0012F4BC 0B707174
0012F4B4h:  0034C4E8 00000000 0012F4E0 0B71CC79
0012F4C4h:  0034C510 00000058 00000004 0B71D5A2
0012F4D4h:  0034C4E8 0B066DA8 0B047D00 0012F4EC
0012F4E4h:  0B71CC96 0034C4E8 0012F510 0B71C330
0012F4F4h:  00000001 0B0435C0 0B71C34E 0B0435C0
0012F504h:  00000001 0B71C3DF 003492E0 0012F53C
0012F514h:  0B71C421 00000001 0B058CF8 0B067FD0
0012F524h:  003492E0 00000000 00000001 0B0435C0
0012F534h:  0B0435C0 00000000 0012F56C 0B71A07D
0012F544h:  003492E0 003492E0 0012F534 0012F564
0012F554h:  0012F558 00000068 00000001 00000000
0012F564h:  00000001 001BFDC0 0012F580 0B78FCB2
0012F574h:  001BFE60 00000000 003492E0 0012F5A0
0012F584h:  0B71B8BA 001BFE60 00000002 003492E0
Registers:
EAX: 0B041688, EBX: 00000000, ECX: 0AA63D30, EDX: 0B0670D0
ESI: 00000001, EDI: 0034C510, EBP: 0012F478, ESP: 0012F474
Crash location: "wmvcore", loaded at 0B6F0000h - 0B936000h

Loaded modules:
foobar2000                       loaded at 00400000h - 004F3000h
ntdll                            loaded at 7C900000h - 7C9B0000h
kernel32                         loaded at 7C800000h - 7C8F4000h
COMCTL32                         loaded at 773D0000h - 774D2000h
msvcrt                           loaded at 77C10000h - 77C68000h
ADVAPI32                         loaded at 77DD0000h - 77E6B000h
RPCRT4                           loaded at 77E70000h - 77F01000h
GDI32                            loaded at 77F10000h - 77F57000h
USER32                           loaded at 77D40000h - 77DD0000h
SHLWAPI                          loaded at 77F60000h - 77FD6000h
SHELL32                          loaded at 7C9C0000h - 7D1D5000h
ole32                            loaded at 774E0000h - 7761D000h
shared                           loaded at 10000000h - 10029000h
comdlg32                         loaded at 763B0000h - 763F9000h
IMM32                            loaded at 76390000h - 763AD000h
LPK                              loaded at 629C0000h - 629C9000h
USP10                            loaded at 74D90000h - 74DFB000h
msctfime                         loaded at 755C0000h - 755EE000h
foo_abx                          loaded at 009E0000h - 00A13000h
foo_albumlist                    loaded at 00A20000h - 00A60000h
foo_audioscrobbler               loaded at 00A80000h - 00AB0000h
WS2_32                           loaded at 71AB0000h - 71AC7000h
WS2HELP                          loaded at 71AA0000h - 71AA8000h
foo_autoplaylist                 loaded at 00B10000h - 00B40000h
foo_bitcompare                   loaded at 00B60000h - 00B87000h
foo_cdda                         loaded at 00BB0000h - 00BE6000h
foo_common                       loaded at 00C10000h - 00C4A000h
foo_converter                    loaded at 00C70000h - 00CD9000h
foo_dbsearch                     loaded at 00D00000h - 00D5C000h
foo_dsp_skip_silence             loaded at 00D80000h - 00D8A000h
MSVCR80                          loaded at 78130000h - 781CB000h
foo_dsp_std                      loaded at 00DB0000h - 00DF1000h
foo_freedb2                      loaded at 00E20000h - 00E60000h
foo_input_std                    loaded at 00E80000h - 00F94000h
foo_masstag                      loaded at 00FC0000h - 01010000h
foo_playcount                    loaded at 01030000h - 01058000h
foo_playlist_manager             loaded at 01080000h - 010C7000h
foo_pqview                       loaded at 010F0000h - 0110C000h
foo_random                       loaded at 01130000h - 0116F000h
foo_rgscan                       loaded at 01190000h - 011D8000h
foo_sic                          loaded at 01200000h - 01257000h
foo_uie_albumart                 loaded at 01380000h - 013B8000h
gdiplus                          loaded at 4EC50000h - 4EDF3000h
OPENGL32                         loaded at 5ED00000h - 5EDCC000h
GLU32                            loaded at 68B20000h - 68B40000h
DDRAW                            loaded at 73760000h - 737A9000h
DCIMAN32                         loaded at 73BC0000h - 73BC6000h
foo_uie_albumlist                loaded at 093F0000h - 0942F000h
foo_uie_console                  loaded at 09450000h - 0946C000h
foo_uie_quicksearch              loaded at 09490000h - 094D8000h
foo_uie_tabs                     loaded at 09500000h - 09526000h
foo_uie_trackinfo_mod            loaded at 09550000h - 0959A000h
MSVCP80                          loaded at 7C420000h - 7C4A7000h
foo_ui_columns                   loaded at 095B0000h - 0964B000h
foo_ui_std                       loaded at 09670000h - 096C7000h
foo_utils                        loaded at 096F0000h - 09729000h
foo_verifier                     loaded at 09750000h - 09780000h
foo_version                      loaded at 097A0000h - 097C6000h
dbghelp                          loaded at 59A60000h - 59B01000h
VERSION                          loaded at 77C00000h - 77C08000h
uxtheme                          loaded at 5AD70000h - 5ADA8000h
IMGHOOK                          loaded at 30000000h - 30047000h
netapi32                         loaded at 5B860000h - 5B8B4000h
appHelp                          loaded at 77B40000h - 77B62000h
CLBCATQ                          loaded at 76FD0000h - 7704F000h
COMRes                           loaded at 77050000h - 77115000h
OLEAUT32                         loaded at 77120000h - 771AC000h
CRYPT32                          loaded at 77A80000h - 77B14000h
MSASN1                           loaded at 77B20000h - 77B32000h
WINTRUST                         loaded at 76C30000h - 76C5E000h
IMAGEHLP                         loaded at 76C90000h - 76CB8000h
WLDAP32                          loaded at 76F60000h - 76F8C000h
SETUPAPI                         loaded at 77920000h - 77A13000h
urlmon                           loaded at 77260000h - 77300000h
Secur32                          loaded at 77FE0000h - 77FF1000h
SSSensor                         loaded at 0A9A0000h - 0A9B5000h
WINMM                            loaded at 76B40000h - 76B6D000h
DrvTrNTm                         loaded at 6BC00000h - 6BC1A000h
DrvTrNTl                         loaded at 6BC20000h - 6BC3D000h
msdmo                            loaded at 736B0000h - 736B7000h
mswsock                          loaded at 71A50000h - 71A8F000h
DNSAPI                           loaded at 76F20000h - 76F47000h
winrnr                           loaded at 76FB0000h - 76FB8000h
wshbth                           loaded at 751D0000h - 751EE000h
rasadhlp                         loaded at 76FC0000h - 76FC6000h
hnetcfg                          loaded at 662B0000h - 66308000h
wshtcpip                         loaded at 71A90000h - 71A98000h
DSOUND                           loaded at 73F10000h - 73F6C000h
wdmaud                           loaded at 72D20000h - 72D29000h
msacm32                          loaded at 72D10000h - 72D18000h
MSACM32                          loaded at 77BE0000h - 77BF5000h
midimap                          loaded at 77BD0000h - 77BD7000h
KsUser                           loaded at 73EE0000h - 73EE4000h
wmvcore                          loaded at 0B6F0000h - 0B936000h
WMASF                            loaded at 0BB40000h - 0BB7A000h

Stack dump analysis:
Address: 0B71CDF7h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+000133EAh)
Address: 0B71D5F6h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00013BE9h)
Address: 0B707174h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCheckURLScheme" (+00001BDFh)
Address: 0B71CC79h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+0001326Ch)
Address: 0B71D5A2h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00013B95h)
Address: 0B71CC96h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00013289h)
Address: 0B71C330h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00012923h)
Address: 0B71C34Eh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00012941h)
Address: 0B71C3DFh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+000129D2h)
Address: 0B71C421h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00012A14h)
Address: 0B71A07Dh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00010670h)
Address: 0B78FCB2h, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateSyncReader" (+000029D1h)
Address: 0B71B8BAh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateEditor" (+00011EADh)
Address: 0B6FB88Ah, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Address: 0B78EDEAh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateSyncReader" (+00001B09h)
Address: 0B78D54Eh, location: "wmvcore", loaded at 0B6F0000h - 0B936000h
Symbol: "WMCreateSyncReader" (+0000026Dh)
Address: 00ECB126h, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 00F44BFCh, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 00ECD77Bh, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 00F47A38h, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 00ECD603h, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 00F46360h, location: "foo_input_std", loaded at 00E80000h - 00F94000h
Address: 0119E149h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 7C809B47h, location: "kernel32", loaded at 7C800000h - 7C8F4000h
Symbol: "CloseHandle" (+00000000h)
Address: 011BE298h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 0119EDBEh, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011BF483h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011AF010h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011B1220h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 0119814Ah, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 0119ED50h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011BFF9Dh, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 01198049h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A0877h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A0819h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D48734h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetDC" (+0000006Dh)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D5418Dh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000002B2h)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D70467h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DeregisterShellHookWindow" (+000001CFh)
Address: 77D541B0h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000002D5h)
Address: 77D53FD9h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000000FEh)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D4D0A5h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "EnumDisplayMonitors" (+00000142h)
Address: 77D4B50Ch, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefWindowProcW" (+000001D0h)
Address: 7C90EAE3h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "KiUserCallbackDispatcher" (+00000013h)
Address: 77D53F5Ah, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+0000007Fh)
Address: 77D4DAF6h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DestroyWindow" (+0000000Ch)
Address: 01197899h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D488DAh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetWindowLongW" (+00000034h)
Address: 011C0148h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A0892h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A0819h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D48734h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetDC" (+0000006Dh)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D5418Dh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000002B2h)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D70467h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DeregisterShellHookWindow" (+000001CFh)
Address: 77D541B0h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000002D5h)
Address: 77D53FD9h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "PrivateExtractIconExW" (+000000FEh)
Address: 011A07C0h, location: "foo_rgscan", loaded at 01190000h - 011D8000h
Address: 77D541E2h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000000h)
Address: 77D484FCh, location: "USER32", loaded at 77D40000h - 77DD0000h
Address: 77D485A4h, location: "USER32", loaded at 77D40000h - 77DD0000h
Address: 77D54204h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000022h)
Address: 77D48734h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetDC" (+0000006Dh)
Address: 77D541E2h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000000h)
Address: 77D541E2h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000000h)
Address: 77D48816h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetDC" (+0000014Fh)
Address: 77D541E2h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000000h)
Address: 77D70467h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DeregisterShellHookWindow" (+000001CFh)
Address: 77D48830h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetDC" (+00000169h)
Address: 77D489CDh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetWindowLongW" (+00000127h)
Address: 77D541E2h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DefDlgProcW" (+00000000h)
Address: 77D4EC03h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "CallNextHookEx" (+00000100h)
Address: 77D61B4Dh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "AppendMenuA" (+0000006Eh)
Address: 77D70467h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DeregisterShellHookWindow" (+000001CFh)
Address: 77D489F0h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "GetWindowLongW" (+0000014Ah)
Address: 77D48A10h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DispatchMessageW" (+0000000Fh)
Address: 77D5E097h, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "IsDialogMessageW" (+000000DBh)
Address: 0042FC8Eh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 77D4DAEAh, location: "USER32", loaded at 77D40000h - 77DD0000h
Symbol: "DestroyWindow" (+00000000h)
Address: 004BEBA0h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 0042FD00h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 10002DD2h, location: "shared", loaded at 10000000h - 10029000h
Symbol: "uCallStackTracker::uCallStackTracker" (+00000032h)
Address: 004C0520h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00D4DAEAh, location: "foo_dbsearch", loaded at 00D00000h - 00D5C000h
Address: 0043085Fh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004C03BCh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004BFB18h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004BFB18h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 7C910732h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+0000015Eh)
Address: 00400000h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004C7690h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 7C910732h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+0000015Eh)
Address: 7C911538h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "wcsncpy" (+00000AA9h)
Address: 7C911596h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "wcsncpy" (+00000B07h)
Address: 7C9106EBh, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+00000117h)
Address: 004E41C0h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 7C91056Dh, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlFreeHeap" (+00000130h)
Address: 1000C391h, location: "shared", loaded at 10000000h - 10029000h
Address: 7C90EE18h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "strchr" (+00000117h)
Address: 7C9106F0h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+0000011Ch)
Address: 7C90EE18h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "strchr" (+00000117h)
Address: 7C9106F0h, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+0000011Ch)
Address: 7C9106EBh, location: "ntdll", loaded at 7C900000h - 7C9B0000h
Symbol: "RtlAllocateHeap" (+00000117h)
Address: 004939FDh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004E4240h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 0044E438h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00447CCBh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00498E3Dh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00496B40h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004C0530h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 10002D87h, location: "shared", loaded at 10000000h - 10029000h
Symbol: "uPrintCrashInfo_SetDumpPath" (+000000A7h)
Address: 004C0530h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004AF185h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004C0530h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00430A66h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00400000h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004E09B0h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00496844h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00491D3Ch, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00491D36h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004B49F0h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004B3960h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004E4238h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00496B40h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004AF578h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00495FA4h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00400000h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 00496B40h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 7C816FD7h, location: "kernel32", loaded at 7C800000h - 7C8F4000h
Symbol: "RegisterWaitForInputIdle" (+00000049h)
Address: 7C839AA8h, location: "kernel32", loaded at 7C800000h - 7C8F4000h
Symbol: "ValidateLocale" (+000002B0h)
Address: 7C816FE0h, location: "kernel32", loaded at 7C800000h - 7C8F4000h
Symbol: "RegisterWaitForInputIdle" (+00000052h)
Address: 0049600Dh, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004E0049h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004F0044h, location: "foobar2000", loaded at 00400000h - 004F3000h
Address: 004B0063h, location: "foobar2000", loaded at 00400000h - 004F3000h

Version info: 
foobar2000 v0.9.4 beta 3
UNICODE

Additional info:
Playlist Manager 1.0.2  (foo_playlist_manager)
Common services 0.1  (foo_common)
Standard Input Array 1.0  (foo_input_std)
foobar2000 core v0.9.4 beta 3  (Core)
Converter 1.0.1  (foo_converter)
Playlist tools 0.5.8  (foo_utils)
Console panel 0.2  (foo_uie_console)
Masstagger 1.6  (foo_masstag)
CD Audio Decoder 2.1.1  (foo_cdda)
Audioscrobbler 2.1  (foo_audioscrobbler)
Album Art Panel 0.2.3  (foo_uie_albumart)
Binary Comparator 1.1  (foo_bitcompare)
Randomized playlist entry 1.2.3  (foo_random)
Default User Interface 0.9acc  (foo_ui_std)
WMA Decoder 1.1  (foo_input_std)
Tabbed panel modifyed 0.2.1  (foo_uie_tabs)
ReplayGain Scanner 2.0.2  (foo_rgscan)
Database search 1.3.1 beta 11  (foo_dbsearch)
Playback Statistics 1.3.1  (foo_playcount)
Components versions viewer 0.3  (foo_version)
foosic music database 1.0 beta 11  (foo_sic)
Track info panel mod 0.5 beta [Aug 30 2006 - 16:35:44]  (foo_uie_trackinfo_mod)
freedb Tagger 0.5.2a  (foo_freedb2)
FLAC decoder 1.1.0  (foo_input_std)
Standard DSP array 1.0  (foo_dsp_std)
Skip silence 0.1  (foo_dsp_skip_silence)
File Integrity Verifier 1.0.1  (foo_verifier)
ABX Comparator 1.3.1  (foo_abx)
Quick Search Toolbar 2.8h  (foo_uie_quicksearch)
Columns UI 0.1.3 beta 1v5  (foo_ui_columns)
Album List 3.2.0  (foo_albumlist)
Autoplaylist Manager 1.0  (foo_autoplaylist)
Album list panel 0.2.1 beta 4  (foo_uie_albumlist)

Edit again make that 5 crashes that have occured because of this now, im gonna stop trying.

The problem is in MS WMA runtime and not on our side, there's very little we can do about it. You can try updating Windows Media Player etc to the latest version.

thanks peter for finally adding wma tag editing - nice to know you listen to what people want  keep up the good work!!!

what are the plans for the next release just fixes or features?

Thanks for all your work Peter.

The problem is in MS WMA runtime and not on our side, there's very little we can do about it. You can try updating Windows Media Player etc to the latest version.

Ok thanks, by latest version do you mean WMP 10 or 11 beta 2

Quote from: Peter on 2006-09-15 19:16:19

The problem is in MS WMA runtime and not on our side, there's very little we can do about it. You can try updating Windows Media Player etc to the latest version.

Ok thanks, by latest version do you mean WMP 10 or 11 beta 2

That depends on the version you currently have installed on your system

The LAME profile recognition isn't quite right. For LAME versions less than 3.94, it says Vx, when it should say apx (where x is the level).

And it doesn't recognize LAME 3.89 -remix MP3s at all.

Also, there's $codec() for %codec% but no $codec_profile() for %codec_profile%. Not a big deal really, but that seems a bit inconsistent.

The LAME profile recognition isn't quite right. For LAME versions less than 3.94, it says Vx, when it should say apx (where x is the level).

Why do you need this? Its just a name. E.g. v0=-preset extreme in older lames. Just a command line preset name.

And it doesn't recognize LAME 3.89 -remix MP3s at all.

Hi!

Could you tell me which encoding is used with the id3v2.3 compatibility mode in foobar 0.9.4 beta? Is it ISO-8859-1 or UTF-16?
(My mp3 player can only read ISO-8859-1).

If it's only UTF-16 could you add an advanced option to switch between ISO-8859-1 and UTF-16?

Thanks in advance.

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

i'm having the same problem but before i upgraded from 0.9.3 i noticed that i had 4 instances, taking at least 23mb of ram each, in task manager when foobar was closed.

no one else is having the same problem?  maybe no one has really checked, i didn't notice until now.

Quote from: showdax on 2006-09-19 04:07:04

The LAME profile recognition isn't quite right. For LAME versions less than 3.94, it says Vx, when it should say apx (where x is the level).

Why do you need this? Its just a name. E.g. v0=-preset extreme in older lames. Just a command line preset name.

Code: [Select]

And it doesn't recognize LAME 3.89 -remix MP3s at all.

The older versions of LAME don't have -V, and they're not equivalent in those versions. For instance, for 3.90.3 -ape, foobar2000 says it's -V2, while for 3.96.1 -ape, it says it's -V0.

Like I said, I believe -V was introduced in 3.94 (or maybe 3.95?), so before that, you should be using --alt-preset. It's not difficult at all to detect the profiles. You can still check the preset in the header, and if that doesn't work, you can look at the VBR method, ATH and low pass values.

Dnuos (http://brodierao.com/projects/dnuos/) and Oidua (http://oidua.suxbad.com) can do this just fine. It's not at all complicated.

Great news!  With foobar2000 v0.9.4B3 all tags now come over during conversion to WMA.

Assuming you have Windows Media Encoder components installed, you can set up a foobar converter as follows:

Encoder: Custom
Encoder: c:\windows\system32\cscript.exe
Extension: wma
Parameters: c:\progra~1\wi15da~1\encoder\wmcmd.vbs -input %s -output %d -profile a128
Format is: Lossy
Highest BPS mode supported: 24
Encoder name: WMA
Bitrate (kbps): 128
Settings: -profile a128

This will produce WMA files -- fully tagged as were the source files -- at 128 bitrate.  Other encoding settings are explained in the help file that installs with WME components.

WME is here: http://www.microsoft.com/downloads/details...;displaylang=en (http://www.microsoft.com/downloads/details.aspx?familyid=5691ba02-e496-465a-bba9-b2f1182cdf24&displaylang=en)

Note that your "short file name" directory for WME may be something different than my "wi15da~1".

Enjoy!

WoW, there's someone dare to advertise M$ here lol.

wma. It's not only about hatred, it's like "who cares?"

nice. cuesheet editing via the porperties box is working almost properly now. i rememeber that older 0.9x versions created strange fiels when you looked at the cuesheet in a text editor. (when opening 0.9x edited files with 0.8.3 it looked like that: http://songbird.dyndns.info/wvpack.png (http://songbird.dyndns.info/wvpack.png) )


anyway i have some questions:
is it intended that foobar changes the position of some fields in the cuesheet and is it intended that the editing of a field in an embedded cue causes the removal of the "PERFORMER" field?

comparison:

original:

PERFORMER "Coldplay"
TITLE "Mince Spies"
REM REPLAYGAIN_ALBUM_GAIN -6.25 dB
REM REPLAYGAIN_ALBUM_PEAK 0.988800
FILE "Coldplay - 2001 - Mince Spies.wav" WAVE
  TRACK 01 AUDIO
    TITLE "Have Yourself A Merry Little Christmas (Jo Whiley / BBC R1 Session)"
    PERFORMER "Coldplay"
    INDEX 01 00:00:00
    REM REPLAYGAIN_TRACK_GAIN -5.98 dB
    REM REPLAYGAIN_TRACK_PEAK 0.988708
  TRACK 02 AUDIO
    TITLE "Yellow (The Alpha Remix)"
    PERFORMER "Coldplay"
    INDEX 00 02:38:50
    INDEX 01 02:39:62
    REM REPLAYGAIN_TRACK_GAIN -6.35 dB
    REM REPLAYGAIN_TRACK_PEAK 0.988800

foobar 0.9.4beta updated cuesheet

PERFORMER "Coldplay"
TITLE "Mince Spies"
REM REPLAYGAIN_ALBUM_GAIN -6.25 dB
REM REPLAYGAIN_ALBUM_PEAK 0.988800
FILE "Coldplay - 2001 - Mince Spies.wav" WAVE
  TRACK 01 AUDIO
    TITLE "Have Yourself A Merry Little Christmas (Jo Whiley / BBC R1 Session)"
    REM REPLAYGAIN_TRACK_GAIN -5.98 dB
    REM REPLAYGAIN_TRACK_PEAK 0.988708
    INDEX 01 00:00:00
  TRACK 02 AUDIO
    TITLE "Yellow (The Alpha Remix)"
    REM REPLAYGAIN_TRACK_GAIN -6.35 dB
    REM REPLAYGAIN_TRACK_PEAK 0.988800
    INDEX 00 02:38:50
    INDEX 01 02:39:62

I know that if given a choice an educated person will try to avoid WMA, but I still think it's good that fb2k is getting decent support for the format anyways. I'm actually trying out dbPowerAmp right now primarily because I need to experiment with WMA files, and would have prefered to us fb2k for this task instead seeing as I use it for everything music related these days. See, I bought an Xbox 360 several weeks ago and am having a lot of issues with getting music to play between the two applications that are available for streaming media to the Xbox. These are Windows Media Connect, which is made by Microsoft, and TVersity which is a third party app. I like the latter more since I can play internet radio. However, TVersity is balking at the way I have my music files organized, where as WMC won't play internet radio but has no issues with my file organization. Very frustrating. Hence why I want my collection in WMA format, to hopefully prove a point on another forum.

Anyways, to the point of why I actually wanted to make a post in this thread. I noticed that dbPowerAmp copies all tags to the WMA files it makes when I transcode from my APE files. This includes ReplayGain. Version 0.9.3.1 of foobar 2000 doesn't see the RG tags at all. I'm only guessing 0.9.4 Beta is the same. Not sure how much of an issue this really is, but I suppose it could be for some users, and hence why I thought I should bring it up.

Edit: Also, properties say WMA 9 was used, when in fact it was WMA 9.1 Pro (which I can see when I hover over the files thanks to dbPowerAmp). Not trying to be a pest or anything, just help things along. Maybe I better give 0.9.4 beta a try myself, because if these issues have been fixed then I'm just making a fool of myself hehe.

wma. It's not only about hatred, it's like "who cares?"

Ok, I get it, but let me tell you why I care:

- My music library is in Ogg, but my kids' DAPs don't support it.  For them, WMA is a fine solution that puts as many tunes as possible in their flash at a quality they are perfectly happy with

- I like to use foobar for as much as I can and it bothered me that I had to launch some other application just to convert files for my kids

- WMA tag editing and conversion support is something that was in foobar v8.3 and has been missing from v9.x up until now; some people on this board were reluctant to make the transition due to this

- One of the wonderful foobar developers spent time putting this functionality into the new release and I wanted to let him know that the work is appreciated

- WMA Lossless and WMA Pro, while not particularly widely supported, are both contemporary and capable codecs

- I'm not going to bow to the pressure sometimes felt in this group to not talk about WMA simply because it is a Microsoft product; I'm not a MS fanboy, neither do I dismiss them out-of-hand

- If we don't talk about WMA, how will it ever get better?

Thanks.

Quote from: Squeller on 2006-09-21 10:06:20

wma. It's not only about hatred, it's like "who cares?"

Ok, I get it, but let me tell you why I care:

- My music library is in Ogg, but my kids' DAPs don't support it.  For them, WMA is a fine solution that puts as many tunes as possible in their flash at a quality they are perfectly happy with

- I like to use foobar for as much as I can and it bothered me that I had to launch some other application just to convert files for my kids

- WMA tag editing and conversion support is something that was in foobar v8.3 and has been missing from v9.x up until now; some people on this board were reluctant to make the transition due to this

- One of the wonderful foobar developers spent time putting this functionality into the new release and I wanted to let him know that the work is appreciated

- WMA Lossless and WMA Pro, while not particularly widely supported, are both contemporary and capable codecs

- I'm not going to bow to the pressure sometimes felt in this group to not talk about WMA simply because it is a Microsoft product; I'm not a MS fanboy, neither do I dismiss them out-of-hand

- If we don't talk about WMA, how will it ever get better?

Thanks.

Great post Apesbrain! By the way, is it possible to get foobar2000 0.9.4 beta 3 to convert to WMA 9.1 Pro? I got your settings working fine just now, but I get an error when I try some of the other settings listed in the help file for WME. All my succesful conversions say WMA v2 in foobar too. Thanks!

Edit: I found the problem. An 'error flushing file' message is given when –a_setting Q98_48_2_24 is added to the command line, which is as follows (straight from the help file pretty much):

c:\progra~1\window~4\encoder\wmcmd.vbs -input %s -output %d -a_codec WMA9PRO -a_mode 2 –a_setting Q98_48_2_24

Take out the -a_setting and I do indeed get a WMA 9.1 Pro file. VBR Quality 75, 44 kHz, 2 channel, 24-bit, one pass, all according to dbPowerAmp (which I guess must be the default... fb2k just says WMA9 pretty much).

CD writer bug:
Blip (~200 ms) of random music at the end of all tracks EXCEPT Track 01 

- Nero 6
- MP3 files

[deleted]

CD writer bug:
Blip (~200 ms) of random music at the end of all tracks EXCEPT Track 01 

- Nero 6
- MP3 files

This is discussed, and apparently solved here (http://www.hydrogenaudio.org/forums/index.php?showtopic=43861) and here (http://www.hydrogenaudio.org/forums/index.php?showtopic=44945).

Do you have the latest burninate plugin?  I think this was fixed quite a long time ago.

The latest version is 2.0.1.

Turns out I was using 2.0, I actually believed burniante was part of the installation.

Anyway, I add that like the way the properties dialog is coming along. What I'm missing is the way Winamp put side-by-side ID3v1 and ID3v2 info in one panel. I wondered who could use that (such as the aforementioned Winamp style or for power users having ID3v2 + APE). Seems like sometimes I edit fields in FB2K and ID3v2 is unaffected, or ID3v2 fields don't show up when there is ID3v1 present. [Personally I like to rid myself of as many ID3v2 tags as possible, which is two clicks in Winamp but one file at a time.]

i apoligize if this is a newbie question, but since going from beta 1 to 3, i lost the actual bitrate in the status bar.  could someone post their code?  heres what i have now.  im not sure if this is all of it. 

// set quality-info (bitrate, etc.)
$puts(quality,$if2(%__codec_profile%,

$puts(ratio,
$if($or($strstr(%__compression%,Lossy),$stricmp(%codec%,DualStream)),,
$muldiv($info(bitrate),1000,
$div($mul(%samplerate%,$info(bitspersample),$channels()),100)
)))
$ifgreater($get(ratio),0,$ifequal($get(ratio),100,,$get(ratio)'%' compr.)
,[%bitrate%kbit])

[$info(mod_channels) channels]

$if($strcmp($codec(),MP3),' '$if2(%__extrainfo%,CBR)
[' / '$upper($abbr(%__mp3_stereo_mode%))])
))
// -----------------------------------------

i apoligize if this is a newbie question, but since going from beta 1 to 3, i lost the actual bitrate in the status bar.  could someone post their code?

I haven't changed it from v0.9.4B3 default and here's what I have:

Preferences > Display > Title Formatting > Status bar

%codec% %bitrate%kbps %samplerate%Hz %channels%'  ¤  '%playback_time%[ / %length%]

Custom buttons doesn't seems to work on the beta. I only get blanks when I load fcb's.
Never mind.. I forget the dll libraries.

[Personally I like to rid myself of as many ID3v2 tags as possible, which is two clicks in Winamp but one file at a time.]

Use MP3Tag or TagScanner.

Quote from: yong on 2006-09-06 22:04:34

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

i'm having the same problem but before i upgraded from 0.9.3 i noticed that i had 4 instances, taking at least 23mb of ram each, in task manager when foobar was closed.

no one else is having the same problem?  maybe no one has really checked, i didn't notice until now.

here the same on windows xp sp2, fb 0.9.4 b3
edit: after a fresh installation it closes correctly again. maybe a 3rd party componet is causing?

Quote from: pencil on 2006-09-20 03:55:56

Quote from: yong on 2006-09-06 22:04:34

Thx for the release~!
Btw just found out a bug, fb2k 0.9.4 b1 couldnt exit properly,
i have to open Task manager and end task manually...

i'm having the same problem but before i upgraded from 0.9.3 i noticed that i had 4 instances, taking at least 23mb of ram each, in task manager when foobar was closed.

no one else is having the same problem?  maybe no one has really checked, i didn't notice until now.

here the same on windows xp sp2, fb 0.9.4 b3
edit: after a fresh installation it closes correctly again. maybe a 3rd party componet is causing?

fixed!: you were right, it was a component, so i decided to try deleting a few i wasn't using one-by-one.  but but but i got it on the first try, i closed all instances of foobar, deleted "foo_dsp_atsurround.dll" and now it closes fine.

i didn't even have that plugin enabled and it might not be the same for everyone but hey, i'm hapee.  avoid that plugin i guess.