Skip to main content

Topic: Wavpack hybrid & MAC : MAX, XLD, PLAY (Read 5740 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • zorba
  • [*][*]
Wavpack hybrid & MAC : MAX, XLD, PLAY
Hello,

I've just noticed that PLAY and MAX (from sbooth.org) behave strangely with wavpack hybrid correction files.

How to be sure that wavpack correction files are read by MAX or PLAY when "track info" shows only 400kb ?
Moreover, while playing the song, I can rename or remove the correction files... without being warned that the file is used by the application...

So I encoded some lossless hybrid wavpack into another format. mp3 first, then wav

I used MAX 0.7.1, then XLD  to encode .wv into .mp3.

So, my lossless song  "clint eastwood.wv" is in the same folder than its correction files "clint eastwood.wvc" - that makes the whole lossless.

I first encoded "clint eastwood.wv" in lame V5, then deleted "clint eastwood.wvc", and encoded again "clint eastwood.wv" in lame V5.
The mp3 files are identical while the source should not be. How bizarre

6 404 344 bytes

The same test with XLD produces 2 different sizes with VBR mp3

6 403 001 bytes / with wv + wvc in the same folder
6 300 794 bytes / with only wv


but produces a similar file with .WAV and CBR 320
60 592 268 bytes / WAV
13 742 793 bytes / 320

I don't get it.

  • zorba
  • [*][*]
Wavpack hybrid & MAC : MAX, XLD, PLAY
Reply #1
with MAX 0.8.1, it seems better

the v5 mp3 are
6 404 344 bytes WITHOUT correction files and
6 449 771 bytes WITH correction files

when I try to delete WVC while decoding, there is no warning and the result is 6 449 771 bytes

Can OSX deal with a deleted file ??? it's strange!

with ogg Q3

4 458 423 bytes (with wvc) vs 4 444 670 bytes (without wvc)



  • Big_Berny
  • [*][*][*]
Wavpack hybrid & MAC : MAX, XLD, PLAY
Reply #2
Hi!
so let's have a look.

I used MAX 0.7.1, then XLD to encode .wv into .mp3.

I first encoded "clint eastwood.wv" in lame V5, then deleted "clint eastwood.wvc", and encoded again "clint eastwood.wv" in lame V5.
The mp3 files are identical while the source should not be. How bizarre

6 404 344 bytes

Ok, here it looks like it doesn't use the correction file.

Quote
The same test with XLD produces 2 different sizes with VBR mp3

6 403 001 bytes / with wv + wvc in the same folder
6 300 794 bytes / with only wv

Here it looks like the correction file is used. Altough I don't understand what you did different here...

Quote
but produces a similar file with .WAV and CBR 320
60 592 268 bytes / WAV
13 742 793 bytes / 320

This is logical because WAV is umcompressed - so size is always the same for songs with the same length. Same for CBR where also all songs with the same length get the same size.

with MAX 0.8.1, it seems better

the v5 mp3 are
6 404 344 bytes WITHOUT correction files and
6 449 771 bytes WITH correction files

when I try to delete WVC while decoding, there is no warning and the result is 6 449 771 bytes

Probably the WVC is already loaded into the ram then.

Quote
with ogg Q3

4 458 423 bytes (with wvc) vs 4 444 670 bytes (without wvc)

This looks ok, too.

So only your first example looks a bit strange. Altoiugh I don't really understand what you did different in example 1 and 2...

Big_Berny
  • Last Edit: 16 March, 2009, 09:06:19 AM by Big_Berny

  • zorba
  • [*][*]
Wavpack hybrid & MAC : MAX, XLD, PLAY
Reply #3
Hi Big_Berny,

example 1 : test with MAX
example 2  : test with XLD

thank you for your answers regarding wav, CBR and RAM.

When you talk about length, you mean song length or is something else?

  • Big_Berny
  • [*][*][*]
Wavpack hybrid & MAC : MAX, XLD, PLAY
Reply #4
Hi Big_Berny,

example 1 : test with MAX
example 2  : test with XLD

Ok, so it looks like MAX doesn't support the correction files. Maybe you should contact a developer.

Quote
thank you for your answers regarding wav, CBR and RAM.

When you talk about length, you mean song length or is something else?

No problem!  And yes, I meant songlength.

Big_Berny