SV8 wishes

r2d · 27 December 2006, 12:18 pm

Hello,

SV8 is on it's way. One target of the first SV8 release is lossless conversion from SV7 files, so there will be limited changes in the compression engine.
You can see the current SV8 schedule of conditions ( http://trac.musepack.net/trac/wiki/S...leOfConditions ) in the Musepack Trac Wiki. I'm waiting for your wishes / comments / improvement suggestions on this stream.

Shy · 28 December 2006, 10:52 am

Note that requesting elimination of internal clipping and improved huffman coding (~2% size gain) is not needed, as that's already done

.

reezeh · 07 January 2007, 12:50 am

All I can think of, and my personal wishlist is easy streamability and maybe an app or plugin to allow it with foobar2k or some commonly used media player. Hopefully the basic data in the mpc files will be identical or close as hinted at so far

kmart · 17 January 2007, 05:04 am

Not sure if you saw the post over in Hydrogenaudio so I thought I'd bring it up here.

Is it too late to change the format/structure of the Encoder Info block? It was suggested that it could be useful to store more information about the --quality setting used for encoding. The original poster wanted to store two decimal places but that would take at least 10 bits. However, using 7 bits (the 4 currently used as well as the 3 unused bits) we could store one decimal place and still keep the Encoder Info block at 32 bits.

That way we could save --quality 0.0 - 10.0 and still have some room for some reserved/experimental settings.

r2d · 20 January 2007, 10:06 am

Quote:

Originally Posted by kmart

Not sure if you saw the post over in Hydrogenaudio so I thought I'd bring it up here.

Is it too late to change the format/structure of the Encoder Info block? It was suggested that it could be useful to store more information about the --quality setting used for encoding. The original poster wanted to store two decimal places but that would take at least 10 bits. However, using 7 bits (the 4 currently used as well as the 3 unused bits) we could store one decimal place and still keep the Encoder Info block at 32 bits.

That way we could save --quality 0.0 - 10.0 and still have some room for some reserved/experimental settings.

I've seen it, and plan to do as you said. Just need to change the spec (and the code). Don't worry about the changes in the spec, everything can still be changed.

27 December 2006, 12:18 pm	#1
r2d Musepack developer Join Date: Sep 2006 Location: Villeurbanne - France Posts: 36	SV8 wishes Hello, SV8 is on it's way. One target of the first SV8 release is lossless conversion from SV7 files, so there will be limited changes in the compression engine. You can see the current SV8 schedule of conditions ( http://trac.musepack.net/trac/wiki/S...leOfConditions ) in the Musepack Trac Wiki. I'm waiting for your wishes / comments / improvement suggestions on this stream.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Need Someone's Help With MPC (SV8?) Decoding.	Ptomaine	Development	3	10 August 2006 06:13 pm
SV7.5 \| SV8	KHRoN	General	3	13 November 2005 04:49 pm

28 December 2006, 10:52 am	#2
Shy Admin Join Date: Jul 2004 Posts: 372	Note that requesting elimination of internal clipping and improved huffman coding (~2% size gain) is not needed, as that's already done .

07 January 2007, 12:50 am	#3
reezeh Member Join Date: Mar 2006 Location: Bradford, UK Posts: 1	All I can think of, and my personal wishlist is easy streamability and maybe an app or plugin to allow it with foobar2k or some commonly used media player. Hopefully the basic data in the mpc files will be identical or close as hinted at so far

17 January 2007, 05:04 am	#4
kmart Member Join Date: Jun 2006 Location: MA, USA Posts: 2	Not sure if you saw the post over in Hydrogenaudio so I thought I'd bring it up here. Is it too late to change the format/structure of the Encoder Info block? It was suggested that it could be useful to store more information about the --quality setting used for encoding. The original poster wanted to store two decimal places but that would take at least 10 bits. However, using 7 bits (the 4 currently used as well as the 3 unused bits) we could store one decimal place and still keep the Encoder Info block at 32 bits. That way we could save --quality 0.0 - 10.0 and still have some room for some reserved/experimental settings.