IPB

Welcome Guest ( Log In | Register )

WavPack 4.70.0 alpha version available, bug fixes, transcoding and verify features
bryant
post Apr 2 2013, 20:08
Post #1


WavPack Developer


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



I am in the process of completing the 4.70 release of WavPack and thought it would be a good time for an alpha (built with SVN 300) while I finish tweaking. The impetus for this release was to incorporate some bug fixes that had accumulated since 2009, but I decided to also include a few new features that I had been thinking about.

The most interesting new feature is the ability for the wavpack command-line executable to accept existing wavpack files as input (i.e., transcoding). This allows users to easily change the settings of files in their lossless collection. The process copies all tag information from the source, and even allows modification of the tags. Temp files are also used now when overwriting and a verify option has been added, so it's possible to safely do transcoding in-place (although this is an alpha version, so be careful!)

Note that care should be taken when transcoding to and from lossy files, and lossy to lossless transcoding is not allowed.

This release should generate identical files to the previous release (other than changes from bug fixes) and the performance should be similar (excepting differences from compiler revisions).

New features:
  • detect UTF-16LE encoding for tag text files (mostly a Windows thing)
  • use temporary files for safer overwriting
  • option to verify WavPack file integrity on creation (-v)
  • transcoding from existing WavPack files (with tag copy)
  • transition to Visual Studio 2008 (Windows)

Bug fixes:
  • seeking to last block failure (after finishing file)
  • memcpy() not always used correctly (Linux targets)
  • unsigned char issue (ARM targets)

Windows features ported to Linux:
  • clean handling of ^C
  • console title (with -z to defeat)
  • wildcards in tag specifications
  • 4GB file support on 32-bit OS

Windows 32-bit executables
Linux distro

Thanks in advance for any testing and/or suggestions! smile.gif
Go to the top of the page
+Quote Post
 
Start new topic
Replies
krafty
post Apr 4 2013, 02:59
Post #2





Group: Members
Posts: 282
Joined: 20-March 10
Member No.: 79175



QUOTE
I was thinking of adding a "--allow-huge-tags" option to allow embedding of up to 4 MB of tag data, with no single file over 1 MB. Would that be enough?


That would still rely on APEv2 tags, right?
What I meant was a native tagging format like FLAC has.
Can VorbisComments be implemented into WavPack?
Sorry to sound pesky, I'm not really pesky about this. Any remedy is ok.
Go to the top of the page
+Quote Post
bryant
post Apr 4 2013, 04:53
Post #3


WavPack Developer


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



QUOTE (krafty @ Apr 3 2013, 18:59) *
That would still rely on APEv2 tags, right?
What I meant was a native tagging format like FLAC has.
Can VorbisComments be implemented into WavPack?

Well I guess I'm confused then. I thought the problem was the desire to embed more than 1 MB of picture data into a WavPack file.

APEv2 tags are "native" to WavPack just like Vorbis comments are "native" to FLAC. Why would I want to implement Vorbis comments in WavPack? Doing that would break every program and device that supports WavPack files. Do Vorbis comments provide something important that APEv2 tags do not? The 1 MB limitation is something I have came up with to make the files more embedded-device friendly...it's not a APEv2 limitation (which actually specifies 8 KB as a limit).
Go to the top of the page
+Quote Post

Posts in this topic
- bryant   WavPack 4.70.0 alpha version available   Apr 2 2013, 20:08
- - krafty   Nice one Bryan! Been waiting for this feature....   Apr 2 2013, 20:29
|- - bryant   QUOTE (krafty @ Apr 2 2013, 12:29) What a...   Apr 3 2013, 18:50
- - db1989   Are you referring only to artwork? Tagging has bee...   Apr 2 2013, 20:32
- - larryfine   Thank You, bryant! I will test soon. I have se...   Apr 2 2013, 21:22
- - azaqiel   I like this release, having jumped the gun and tes...   Apr 2 2013, 23:39
- - temp1   good new,thank u, bryant. i'll try it   Apr 3 2013, 02:05
- - krafty   QUOTE Are you referring only to artwork? Yes. I t...   Apr 3 2013, 02:15
- - themanintheshadows_2451   Did a transcoding test of a WavPack file, and I di...   Apr 3 2013, 09:09
- - chi   I think the pkg-config file is not correct. From w...   Apr 3 2013, 13:58
|- - bryant   QUOTE (chi @ Apr 3 2013, 05:58) In summar...   Apr 3 2013, 19:04
- - krafty   QUOTE I was thinking of adding a "--allow-hug...   Apr 4 2013, 02:59
|- - bryant   QUOTE (krafty @ Apr 3 2013, 18:59) That w...   Apr 4 2013, 04:53
- - krafty   Sorry Bryant. It was my misunderstanding. Well can...   Apr 4 2013, 23:46
- - db1989   I don’t mean that you shouldn’t have the ability, ...   Apr 5 2013, 00:37
|- - bryant   QUOTE (db1989 @ Apr 4 2013, 16:37) I don’...   Apr 6 2013, 01:05
|- - Mr_Rabid_Teddybear   QUOTE (bryant @ Apr 5 2013, 17:05) This m...   Apr 6 2013, 13:42
- - krafty   Since I use mostly for lossless encodings, I think...   Apr 5 2013, 16:38
- - db1989   FWIW, to me, an all or nothing approach seems most...   Apr 5 2013, 17:47
- - greynol   It isn't like the source is closed.   Apr 5 2013, 17:58


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: 26th December 2014 - 10:49