Skip to main content

Topic: lossyWAV 1.3.0 Development Thread (Read 147896 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
  • GeSomeone
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #325
lossyWAV beta 1.2.3i have stronger supression noise in audible range.

I using wavelab6 for audio compare between original and lossywav and gain for inverted difference +50db.

It seems to me that you only looked at the difference signal, this tells not all without showing the source signal. It could be that lossyWav(version i) is "hiding" the introduced noise better "behind" the source signal.
At the end of the day the only thing that counts is, whether the noise is (more) audible?
In theory, there is no difference between theory and practice. In practice there is.

  • Ljubo44
  • [*]
lossyWAV 1.3.0 Development Thread
Reply #326
lossyWAV beta 1.2.3h is best codec ever. 1200kb/s from lossywav is Better than wavpack hybrid at 1600kb/s because in silence lossywav added noise , and, where audio signal is available, that is not changed. In wavpack hybrid situation is reversed. Silence is unchanged but audio peaks in higher band is changed.

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #327
Back from holidays I see more development has been going on.
I just tried furious and eig with new i version using -Q X.

I'm sorry to say that this is a quality regression. furious is easily ABXable in the sec. 0 ... 0.8 range (and I wouldn't call it acceptable as I did with the previous versions tested). And I ABXed eig 9/10 though this wasn't easy for me as I'm pretty insensitive to temporal smearing. I must say though that also with version g I had a slight suspicion that eig wasn't totally fine but this belief could not be backed up at all by my ABXing, so it didn't have any meaning.
lame3995o -Q1

  • Ljubo44
  • [*]
lossyWAV 1.3.0 Development Thread
Reply #328
The world need a codec to compress 24-bit audio in HR sample rates like QTAAC on 16-bit 44,1kHz (-tvbr 127). Where the silence is to add noise, Where the audio is to leave unchanged. No exist that codec yet. I hope in the next versions in LossyWav.

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #329
I'd like to try version b1.2.3h.
Can somebody give me a link to it, please?
lame3995o -Q1

  • Ljubo44
  • [*]
lossyWAV 1.3.0 Development Thread
Reply #330

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #331
Thanks a lot.
lame3995o -Q1

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #332
@halb27:

Could I ask you to please test 1.2.3i using the --nodccorrect parameter? This would allow me to rule out (or in) the recent DC offset correction.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #333
I just had a few minutes where it was quiet at my home (a problem at the moment) and tested version i -Q X --nodccorrect with furious. Again it was very easily ABXable 10/10.
The --nodccorrect version BTW has a lower bitrate by 20 kbps for furious.
I hope I get more quiet moments today and would like to test version h and other previous versions in direct comparison.
  • Last Edit: 04 May, 2011, 05:02:44 AM by halb27
lame3995o -Q1

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #334
Finally it was quiet around here.
I tested versions c, f, g, h, i, i --nodccorrect for furious in an immediate sequence.
Quality of versions f, g, h, i, i --nodccorrect is about the same, so no regression from g to i. I'm just more sensitive to furious at the moment.
But version c of furious was harder to ABX for me than were the other versions.
  • Last Edit: 04 May, 2011, 12:24:12 PM by halb27
lame3995o -Q1

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #335
lossyWAV beta 1.2.3j attached to post #1 in this thread.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #336
Nick, you're great at creating heuristics for improving quality!

Version b1.2.3.j -Q X is excellent with furious (I ABXed it 7/10, and I compared it with the version i result which is real bad in comparison).
I could not ABX eig, though it would be great if someone else could try this (can't get rid of a slight suspicion but I am not the one to ABX it).

Average bitrate of b1.2.3.j -Q X for my standard test set is 303 kbps.
lame3995o -Q1

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #337
lossyWAV beta 1.2.3k RC1 attached to post #1 in this thread.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • GeSomeone
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #338
I see some quick developments now.

Nick, in the version below you introduced --limit defaults to the (new) standard quality scale,
lossyWAV beta 1.2.3a RC2

I was wondering if those values change depending on the sample rate? (common case 48kHz vs. 44.1kHz) and if that would make any significant difference.

BTW I will regard the current version RC6 myself .
In theory, there is no difference between theory and practice. In practice there is.

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #339
BTW I will regard the current version RC6 myself .
Point taken

The upper limit for determination of allowable bits-to-remove (i.e. noise-to-add) does not change with sample-rate, only quality preset. The user can opt to increase the upper limit to a maximum of 20kHz.
  • Last Edit: 08 May, 2011, 02:35:46 PM by Nick.C
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #340
I just tried version 1.2.3k in direct comparison to 1.2.3j using -Q X on furious and eig, as usual.

For furious using version k I arrived at 6/6 which turned into a 7/10. With version j for comparison I arrived at 5/5 which turned into a 8/10.
I'd judge the two versions to be very good to the same degree on furious.

For eig using version k I arrived at 5/5 which turned into a 9/10. With version j for comparison I stopped at 1/4 as I clearly can't ABX it.
To me version j is clearly superior on eig.
  • Last Edit: 09 May, 2011, 03:34:16 AM by halb27
lame3995o -Q1

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #341
@halb27 - thanks again. There was a "bug" in 1.2.3j - although it seems to be beneficial to eig.

lossyWAV beta 1.2.3l RC7 attached to post #1 in this thread.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #342
Using 1.2.3.l -Q X I couldn't ABX eig nor furious (6/10 in both cases).

Using version k for comparison I also couldn't ABX them (furious: 7/10, eig: 3/10).

Obviously I am less sensitive today to temporal smearing (varying sensitivity is gonna be a major problem for me) so this isn't very meaningful. I'll try again and report when I am able to ABX eig with version k again.
  • Last Edit: 10 May, 2011, 03:25:20 AM by halb27
lame3995o -Q1

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #343
lossyWAV beta 1.2.3m RC8 attached to post #1 in this thread.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • Batman321
  • [*][*]
lossyWAV 1.3.0 Development Thread
Reply #344
Sorry to ask, but why do we need lossy wav or lossy flac?

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #345
There's no such thing as 'we need or don't need lossyWav'.
If you want lossless encoding: use a lossless codec, you don't need lossyWav.
If you want lossy encoding: you can use any lossy codec according to your needs, quality is excellent even when using good old mp3 with high bitrates, so you don't need lossyWav either.

But lossyWav is an enrichment to the world of lossy encoding:

- other than the with usual transform codecs where the musical information is transformed from the time to the frequency domain with codec specific limitations and a lot of heuristic decision making with their potential flaws on specific occasion, the lossyWav signal path is very simple reducing just the number of bits per wave sample. However - though to a minor extent - heuristics is done too, and is relevant especially at the lowest quality settings.

- if you use the standard quality or above, probability of audible issues is extremely close to zero. In a sense you get lossyWav preprocessed FLAC files with the quality of lossless FLAC files but smaller file size. Again this is not totally different from the world of other lossy encoders where you find yourself in a similar or the same situation when using very high bitrates, especially if the codec allows for extremely high bitrates like AAC does.

- from the encoding principles lossyWav + a lossless codec cannot be compared well with a transform codec but much better with the lossy variant of a lossless codec, most notably wavPack lossy. The advantage of lossyWav here is that you have a choice of the final codec, and with FLAC a widely supported codec is available which works very well together with lossyWav. Moreover quality control is supposed to be better with lossyWav than with wavPack lossy, though at extremely high bitrate this isn't much of a concern.

- as lossyWav is a preprocessor to a lossless codec like FLAC, you can always losslessly transcode the say lossyWav + FLAC result to another losseless codec like say TAK some day later in case this turns out to be useful for whatever reason, for instance when the new codec is more widely supported on players, or if it is more efficient.

lossyWav just adds to your choices. And as it isn't just another of the many transform codecs it's a very welcome addition IMO.
  • Last Edit: 12 May, 2011, 04:30:35 AM by halb27
lame3995o -Q1

  • Batman321
  • [*][*]
lossyWAV 1.3.0 Development Thread
Reply #346
That's exactly what I wanted to know, thanks 

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #347
lossyWAV beta 1.2.3n RC9 attached to post #1 in this thread.

(I think this may just be the one....)
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • Nick.C
  • [*][*][*][*][*]
  • Developer
lossyWAV 1.3.0 Development Thread
Reply #348
lossyWAV beta 1.2.3o RC10(!) attached to post #1 in this thread.
lossyWAV -q X -a 4 -s h -A --feedback 2 --limit 15848| FLAC -5 -e -p -b 512 -P=4096 -S-

  • halb27
  • [*][*][*][*][*]
lossyWAV 1.3.0 Development Thread
Reply #349
I tested furious and eig using -Q X.

I ABXed 1.2.3o for furious 8/10 and  eig 4/10. Quality is excellent, even furious testing was hard.
Results for 1.2.3m were the same in a practical sense (furious 7/10 [but I don't think version o is worse], eig 4/10).

For a comparison I tested version j on furious which came out fine in an earlier test: 7/10, but to me version 1.2.3o is a tiny bit better (with version j there were more situations when I was pretty sure I heard a difference and I was right, with version o it was more of a guessing throughout though successful most of the time).
For another comparison I tested version k on eig which I was able to ABX in an earlier test. Again I did not succeed: 5/10.


Nick, my impression is: lossyWav has matured so much that further minor modifications are not worth while, at least at the moment. What's really lacking is reassuring quality on a broader basis. Though this seems to be a problem anyway I think as long as there aren't very promising new ideas it's best to really stick to the latest version (or the next one if you have already something new in mind), and to clearly say so that this is the release candidate.
Hopefully this may invite more testers to participate.
  • Last Edit: 17 May, 2011, 05:32:18 AM by halb27
lame3995o -Q1