Closed 2ji3150 closed 2 years ago
I'll take a look on CLI usage with some different versions to confirm whether it is a WavPack behavior change or a foobar2000 behavior change.
Foobar2000 does not use the CLI program to place the tags on the WavPack files. It uses its own tag library instead because it's already there to put tags on other formats.
But as you say, you should be able to use the wvunpack
program with the -ss
option to show you everything about the WavPack files, including all the tag information.
I would be interested in what you find out.
Thanks for the tips! I'll do some more rigorous procedures to figure out what's going on.
Sorry, that was my misunderstanding. No tag headers are generated when converting from foobar2000 without metadata. After adding one of the tags, the result is the same. Therefore, close the issue.
Hi David. Today I try to use the latest foobar2000 (v1.6.7) and WavPack (v5.4) to endode music. Then I found that the new encoded one does not contain Tag type. But all my old music which are also WavPacks all have Tag Types :
Apev2
Is this a behavior change due to WavPack?