#110 Problem with wv / dsd tags

[Anonymous]

I have a problem that was driving me crazy until I discovered the cause and I hope that with the next relase we can solve ..... I convert my dsf files on linux with a terminal command like this "wavpack -hmv - import-id3 * .dsf ", the problem lies in the import of tags, practically once I get the wv file I edit it with a program called Kid3 but Foobar still reads several tags of the old dsf file even though there are not in the wv file. ... I noticed it because with a Foobar album he never put it in track order, so I realized that he goes to read the old numbering of the dsf file, in a nutshell if you have a dsf file with track number 2 and then I convert it to wv and change the numbering to 1 Foobar goes to read what was in the old dsf file, I think it's a bug, I also noticed that it also goes to read other tags that were in the dsf file but that after having transformed it in wv I removed, Foobar reads them the same ...... I hope l what can be solved.
Thank you

[David Raden]

I have what I believe is a related problem. I leave the files in iso format. I've been tagging them successfully for years using this plugin. However, there are some discs, and now some tracks on some discs that the tags shown are the original tags and not the ones I have edited. There is at least one disc where no tags show up even though the xml file appears to be .

I looked at the XML file where one track will not take the new tag for the track title. It looks like it is correct, but when I search on "Soldier's March" only the tags that show up correctlyin Foobar are found. I've attached the xml file for the disc. Here's a screen shot of the two tracks in Foobar. The correct title for track one is "A Soldier's Tale - Part I The Soldier's March".

Another interesting thing I just noticed is that track one, which is 3:03 long has been playing for well over 19 minutes and counting, the progress bar for the track is stuck at the far right.

[Andrea Brandi]

I can confirm that there's an issue tagging wavepack files that contain dsd signal when using this plugin. Tagging them via Foobar ("Editable Tags" checked) result in corrupted files/tags that need to be fixed using external editor like mp3tag. If "Editable Tags" is not checked, wavepack files are simply impossible to edit via Foobar.

I tried uninstalling "foo_input_sacd" and tagging works just fine.

I also noted that when "foo_input_sacd" is installed, if you check a .wv file right clicking on it and then "properties > details > General", under "Tag type" you can see "id3v2.3", but that's wrong, .wv have "APEv2" tag format (checked via mp3tag).

On the other hand, when foo_input_sacd is not there, under the same "Tag type" voice i correctly see "apev2", and tagging works.

[Andrea Brandi]

Ok, I found an "experimental" version inside the "interim" folder of the project and seems working with wavepack with Foobar stable branch (v1.4.6). Unfortunately there're trouble with the latest beta (v1.5 beta 14).

EDIT: Well, it doesn't work at all. It looks like the plugin is bypassed staying on the bottom in "Playback > Decoding" list so that the default "wavpack" comes in action.

[Anonymous]

Please read the other bug reports before entering duplicated and confusing info

[Maxim V.Anisiutkin]

I put the newer one in interim folder. Now all tag handling for .WV files is put at foo_input_std.dll mercy.