IPB

Welcome Guest ( Log In | Register )

 
Reply to this topicStart new topic
Determining WavPack version?
cubanresourceful
post Sep 25 2010, 18:45
Post #1





Group: Members
Posts: 23
Joined: 21-July 08
Member No.: 56090



I am wondering, since I have not been able to find a tool to determine which version encoder a particular WavPack audio file was encoded with. I tried using Foobar, Media Info, and MP3Tag to no avail.

Does anybody know a way to determine this?

Thank you! smile.gif
Go to the top of the page
+Quote Post
lvqcl
post Sep 25 2010, 19:27
Post #2





Group: Developer
Posts: 3219
Joined: 2-December 07
Member No.: 49183



wvunpack -s filename.wv

-> encoder version: 4
Go to the top of the page
+Quote Post
Robertina
post Sep 25 2010, 23:15
Post #3





Group: Members
Posts: 1228
Joined: 4-January 09
Member No.: 65169



I had the same question as cubanresourceful, however I would like to ask additionally whether it is possible to write the used encoder version directly into a to be generated WavPack file and an appropriate APEv2 tag during the conversion process with wavpack.exe. That way foobar2000 and other programs would be able to display that information in their properties dialogs without further efforts.

I checked the WavPack parameters but didn't find what I was looking for.
Go to the top of the page
+Quote Post
bryant
post Sep 27 2010, 01:07
Post #4


WavPack Developer


Group: Developer (Donating)
Posts: 1287
Joined: 3-January 02
From: San Francisco CA
Member No.: 900



It is possible to determine the high-order version number directly from a WavPack file (e.g., 1, 2, 3, or 4), but it is not possible to find the exact version number of the encoder. In retrospect this would have been a good idea, but I use md5 sums of the encoded files to check for regressions and so I decided not to include this because it would change the sums every revision.

To add this information to the APEv2 tag, it should be possible to just add this (or something similar) to the command-line:

CODE
-w "version=4.60"

Go to the top of the page
+Quote Post
cubanresourceful
post Sep 28 2010, 21:39
Post #5





Group: Members
Posts: 23
Joined: 21-July 08
Member No.: 56090



QUOTE (bryant @ Sep 26 2010, 18:07) *
It is possible to determine the high-order version number directly from a WavPack file (e.g., 1, 2, 3, or 4), but it is not possible to find the exact version number of the encoder. In retrospect this would have been a good idea, but I use md5 sums of the encoded files to check for regressions and so I decided not to include this because it would change the sums every revision.

To add this information to the APEv2 tag, it should be possible to just add this (or something similar) to the command-line:

CODE
-w "version=4.60"

That makes sense. I was aware of finding out the higher-order number, but seeing how 4.0 was first released in September 14, 2004, it would of been nice know how old my files are and maybe upgrading them haha (I know it doesn't makes sense but I think I have an OCD...).

I guess I'll wait until 5.0 comes out sometime in the future and then mass upgrade my files. smile.gif Thanks for the help bryant! And thanks to everybody else as well.
Go to the top of the page
+Quote Post
bryant
post Oct 6 2010, 19:10
Post #6


WavPack Developer


Group: Developer (Donating)
Posts: 1287
Joined: 3-January 02
From: San Francisco CA
Member No.: 900



QUOTE (cubanresourceful @ Sep 28 2010, 13:39) *
That makes sense. I was aware of finding out the higher-order number, but seeing how 4.0 was first released in September 14, 2004, it would of been nice know how old my files are and maybe upgrading them haha (I know it doesn't makes sense but I think I have an OCD...).

I understand your desire to have files encoded with recent versions, but as long as you just use lossless mode there have been no changes that would make any relevant differences since the 4.0 release.

However, if you use the lossy/hybrid mode, then there have been some improvements (like the addition of the dynamic noise shaping). You can generally find out if these options were used in your files by using the -s option under "modes".

David

Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 24th April 2014 - 11:13