Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Apple TVBR vs CVBR (Read 24644 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Apple TVBR vs CVBR

I've been reading over these forums and I know similar topics have been covered before, but I couldn't find a clear and concise answer for a long-standing question I've had. I realize Fraunhofer FhG is another excellent choice for an AAC encoder, but for the purposes of this discussion, I will be referring solely to the Apple/qaac encoder.

So, let's open the can of worms:

I know TVBR uses the max bit-reservoir (between ~10 and 6144 bits) but I'm curious what advantage there is of using one over the other. Apple CVBR got an "about the same, but slightly better than" Apple TVBR in the most recent listening test at ~96 kbps, so what's the trade-off there? Should I interpret this as something like: TVBR is more efficient with space, CVBR may be "better" statistically, but there's little real-world difference between the two? I've read a bunch of threads on this already but I've never found a straightforward answer as to what the pros/cons are for each.

Re: Apple TVBR vs CVBR

Reply #1
Here's the thing: TVBR isn't tuned properly,  and it actually sounds worse than CVBR. I guess, though, that Apple bets that most of people using Apple AAC listen to it on pissant little headphones won't notice the quality downgrade. But if you do the ABX tests, you'll easily be able to hear the difference. Compared to FHG AAC? It's faster, but quality-wise, gets edged out a little by Apple AAC (which isn't saying much.)

FDK AAC, though, shows promise. Tests I've done show that it achieves transparency at 180 kbps. And that's compared to a similar Apple AAC file encoded at 320 kbps. And it's designed to use less battery power than other AAC versions. In any case, I'd do you own ABX tests so that you can decide for yourself what works best for you.

BTW: Apple using TVBR allows them to claim that you "get the same quality" at iTunes when you purchase AAC music files from them that you used to get with the previous version. That's total crap. The files are a little smaller, and don't sound as great as before.

Re: Apple TVBR vs CVBR

Reply #2
I've been researching this for a couple weeks now. I did a fair amount of ABX testing with various codecs at various settings. Here is one of the tracks I was able to ABX at ~96 kbps and ~128 kbps.

96 kbps Apple AAC TVBR:
Spoiler (click to show/hide)

128 kbps Apple AAC TVBR:
Spoiler (click to show/hide)

96 kbps Apple AAC CVBR:
Spoiler (click to show/hide)

128 kbps Apple AAC CVBR:
Spoiler (click to show/hide)

I failed both TVBR and CVBR at 160 kbps, but the lower bitrates were hardly what I could call terribly annoying. There were some tracks where I failed even at 96 kbps. I haven't noticed any discernible difference between TVBR and CVBR in my ABX testing yet, so I'm wondering what would be the reason to use one over the other.

Do you have any examples of tracks where you were able to ABX the TVBR at a given bitrate but not the CVBR at the same bitrate?

Re: Apple TVBR vs CVBR

Reply #3
It has actually very simple explanation.

Settings for ~96 kbps: http://listening-tests.hydrogenaud.io/igorc/aac-96-a/index.htm
TVBR - --tvbr 46  - real bitrate  ~94-95 kbps - have score 4,391 in public test
CVBR  --cvbr 96 - real bitrate ~100-101 kbps - score is 4,342.

It's bitrate variation. Both CVBR and TVBR are pretty the same.
Use any of them.

FDK AAC, though, shows promise. Tests I've done show that it achieves transparency at 180 kbps. And that's compared to a similar Apple AAC file encoded at 320 kbps.
Far from reality. 
There is no AAC encoder better than Apple at 96 kbps and higher.  As simple as that.



Re: Apple TVBR vs CVBR

Reply #4
the score values for cvbr and tvbr are swapped in your text

Re: Apple TVBR vs CVBR

Reply #5
It has actually very simple explanation.

Settings for ~96 kbps: http://listening-tests.hydrogenaud.io/igorc/aac-96-a/index.htm
TVBR - --tvbr 46  - real bitrate  ~94-95 kbps - have score 4,391 in public test
CVBR  --cvbr 96 - real bitrate ~100-101 kbps - score is 4,342.

It's bitrate variation. Both CVBR and TVBR are pretty the same.
Use any of them.

FDK AAC, though, shows promise. Tests I've done show that it achieves transparency at 180 kbps. And that's compared to a similar Apple AAC file encoded at 320 kbps.
Far from reality. 
There is no AAC encoder better than Apple at 96 kbps and higher.  As simple as that.




Wasn't talking about 96 kbps, but FDK AAC 180 VBR vs Apple AAC 320kbps. Again, people should do their own ABX tests to find out what works for them. At that setting, FDK AAC sounded pretty damned transparent to my ears.

Re: Apple TVBR vs CVBR

Reply #6
So show us where Apple AAC isn't transparent at 180 kbps.
This 180 kbps vs 320 kbps comparison is meaningless.

Re: Apple TVBR vs CVBR

Reply #7
Wasn't talking about 96 kbps, but FDK AAC 180 VBR vs Apple AAC 320kbps. Again, people should do their own ABX tests to find out what works for them. At that setting, FDK AAC sounded pretty damned transparent to my ears.
And I wasn't talking  just about 96 kbps either.
if You make a claim You should back them with something.

Re: Apple TVBR vs CVBR

Reply #8
It has actually very simple explanation.

Settings for ~96 kbps: http://listening-tests.hydrogenaud.io/igorc/aac-96-a/index.htm
TVBR - --tvbr 46  - real bitrate  ~94-95 kbps - have score 4,391 in public test
CVBR  --cvbr 96 - real bitrate ~100-101 kbps - score is 4,342.

It's bitrate variation. Both CVBR and TVBR are pretty the same.
Use any of them.

FDK AAC, though, shows promise. Tests I've done show that it achieves transparency at 180 kbps. And that's compared to a similar Apple AAC file encoded at 320 kbps.
Far from reality. 
There is no AAC encoder better than Apple at 96 kbps and higher.  As simple as that.

Thank you, IgorC. Looks like I'm going to use TVBR since the file size is typically smaller. As for the bitrate, I have more ABX testing to do before I decide but I'm leaning more toward either ~96 kbps or ~128 kbps. I'm not looking for 100% transparency on all tracks; I'm just looking for something that's transparent for most tracks and not annoying for the ones that aren't.

Re: Apple TVBR vs CVBR

Reply #9
I agree with igorc I've had issues with FHG at mode 5. where some ambient/tamer noise music/doom metal sound iffy because there bitrates are 90 to 140kbps. My Sunn 0))) sample thread says the same.

But i just use it as a back up for albums that fail with apple AAC, like Damaged + Destroyed by Emil Beaulieau.

Re: Apple TVBR vs CVBR

Reply #10
I did some more ABX testing (and updated my ABX component). These results aren't directly related to the TVBR vs CVBR discussion, but I found them quite shocking.

Apple AAC TVBR ~96 kbps (V45):
Spoiler (click to show/hide)

Apple AAC TVBR ~128 kbps (V63):
Spoiler (click to show/hide)

LAME MP3 VBR ~190 kbps (V2):
Spoiler (click to show/hide)

Here I was tinkering with the AAC bitrate, not realizing that the format I'm trying to replace (LAME MP3) is not even as good at 190 kbps as 128 AAC in this particular example! 96 is too low; for the tracks I am able to ABX at that bitrate, it's too noticeable. I'm a little late to the party, but I'm pretty impressed with AAC so far.

Re: Apple TVBR vs CVBR

Reply #11
I have redone some tests from the previous post and I guess this track is just hard to encode. Maybe I got a little too excited earlier but either way, I don't find the AAC artifacts as annoying as the MP3.

Apple AAC TVBR ~128 kbps (V63) (.m4a SHA-1 doesn't match previous test because I re-encoded):
Spoiler (click to show/hide)

Apple AAC TVBR ~160 kbps (V82):
Spoiler (click to show/hide)

For the files I am able to ABX, it seems as though increasing the bitrate doesn't give me a huge boost in quality. I may end up settling on 128 since it's a good trade-off between space and quality (for me).

 

Re: Apple TVBR vs CVBR

Reply #13
To my ears, Apple AAC sounds totally fucking horrible, even at 320 kbps. It's not tuned properly at all.

Yet no ABX test.

If you have an issue with proving statements with ABX testing you should probably have read the rules for the forum before joining.
This is no a placebo tolerant place.  Prove you statements or don't spread unproven nonsense.


8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objective support for their claims.  Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings.  Graphs, non-blind listening tests, waveform difference comparisons, and so on, are not acceptable means of providing support.

The only troll is you that does not adhere to the basic rules of the forum.
Sven Bent - Denmark

Re: Apple TVBR vs CVBR

Reply #14
To my ears, Apple AAC sounds totally fucking horrible, even at 320 kbps. It's not tuned properly at all.

Yet no ABX test.

If you have an issue with proving statements with ABX testing you should probably have read the rules for the forum before joining.
This is no a placebo tolerant place.  Prove you statements or don't spread unproven nonsense.


8. All members that put forth a statement concerning subjective sound quality, must -- to the best of their ability -- provide objectivMe? Troll? HAH! This from somebody who represents a forum who lets a so-called moderator, who's really a troll (i..e greynol) go after people all the time, then do nothing when he abuses his power to get away with it. The guy & his friends tricked me once into doing an ABX test & posting the results afterwards. Guess what? All they could do was make excuses, questioning the methodology of the test itself while "coincidentally" avoiding the results, which proved I was right, All they cared about what their agenda, attacking anyboe support for their claims.  Acceptable means of support are double blind listening tests (ABX or ABC/HR) demonstrating that the member can discern a difference perceptually, together with a test sample to allow others to reproduce their findings.  Graphs, non-blind listening tests, waveform difference comparisons, and so on, are not acceptable means of providing support.

The only troll is you that does not adhere to the basic rules of the forum.

Troll? Me? That's funny. Especially coming from somebody who represents a forum that looks the other way when a particular "moderator" (i.e. troll) regularly goes after people here, then uses his power to get away with it. That dude & his friends actually tricked me into that "posting ABX results" thing awhile back. Didn't matter that the results proved him wrong. He & his friends just attacked me, questioning the very methodology of the test to try and shut me up. That's why I not going to bother wasting my time with that crap.

But I guess it's just "coincidence" that Apple came up with that "Mastered for iTunes" crap? That was their way of telling the world "Yeah, we know TVBR sucks. That's why we convinced the music industry to help us make it not sound as much like crap." I can take any song, convert it into both TVBR & CVBR (at the highest settings), and CVBR will win every single time. But, again, nobody has to believe me. Do your own ABX tests. Despite what some think, this stuff ain't rocket science.

And lets get real here. "Rules" are whatever the hell certain people here pull out of their asses to try and shut people up when their world view is threatened. This thread is a reminder of that. Lame move harassing me by PM'ing me troll messages. And one of the from a so-called "moderator" What are you? A bunch of goddamned 5 yr. olds? And some people wonder why some leave this forum and never come back? You people are pathetic!

Re: Apple TVBR vs CVBR

Reply #15
Apple uses constant bitrate because it gives predictable file size.

All listening test results I have seen suggests their quality is practically identical at the same bitrate.
Your comment about the quality difference is against test results and user experiences. People have used Apple's AAC in TVBR mode for years with software such as QAAC and there have been no quality complaints.

If you have a sample file that turns bad with TVBR many people would be eager to see it. I know I would.

Re: Apple TVBR vs CVBR

Reply #16
Troll? Me?
How many accounts have you had here and why did you create them?

Especially coming from somebody who represents a forum
sven_Bent doesn't represent this forum any more than you do, though I would happily prefer for people aware of the rules to represent it and for people like yourself who flagrantly violate them to go away.

That dude & his friends actually tricked me into that "posting ABX results" thing awhile back. Didn't matter that the results proved him wrong. He & his friends just attacked me, questioning the very methodology of the test to try and shut me up.
Link please.

That's why I not going to bother wasting my time with that crap.
...and people here shouldn't bother wasting their time reading about your unsubstantiated unicorn sightings.

But I guess it's just "coincidence" that Apple came up with that "Mastered for iTunes" crap?
What does that have to do with TVBR vs. CVBR?

That was their way of telling the world "Yeah, we know TVBR sucks.
It doesn't take a rocket scientist to see that you have absolutely no idea what you're talking about.

"Rules" are whatever the hell certain people here pull out of their asses to try and shut people up when their world view is threatened.
*Their* world view is threatened?!? I love the irony!

some leave this forum and never come back
That certainly wouldn't be you, now, would it?  :D

You people are pathetic!
Says the sock puppet throwing yet another temper tantrum.

For those who are curious, I can honestly say that I have no record of ever sending "ghostman6842" a PM, nor have I taken any administrative action against him (issued warnings, restricted posting privileges, binned or deleted posts, etc.).

Re: Apple TVBR vs CVBR

Reply #17
Troll? Me? That's funny. Especially coming from somebody who represents a forum that looks the other way when a particular "moderator" (i.e. troll) regularly goes after people here, then uses his power to get away with it. That dude & his friends actually tricked me into that "posting ABX results" thing awhile back. Didn't matter that the results proved him wrong. He & his friends just attacked me, questioning the very methodology of the test to try and shut me up. That's why I not going to bother wasting my time with that crap.

But I guess it's just "coincidence" that Apple came up with that "Mastered for iTunes" crap? That was their way of telling the world "Yeah, we know TVBR sucks. That's why we convinced the music industry to help us make it not sound as much like crap." I can take any song, convert it into both TVBR & CVBR (at the highest settings), and CVBR will win every single time. But, again, nobody has to believe me. Do your own ABX tests. Despite what some think, this stuff ain't rocket science.

And lets get real here. "Rules" are whatever the hell certain people here pull out of their asses to try and shut people up when their world view is threatened. This thread is a reminder of that. Lame move harassing me by PM'ing me troll messages. And one of the from a so-called "moderator" What are you? A bunch of goddamned 5 yr. olds? And some people wonder why some leave this forum and never come back? You people are pathetic!

1: Yes. you are spewing out stuff without backing it up with some real evidence when asked for it. That is  troll'ish behavior

2: I am not representing the forum .I have nothing to do with it beside being and user for many years. But I do believe in its objective to filter out placebo and none-scientific nonsense .

3: it is normal when you put forth theories that it gets scrutinized. That you take that as an attack against you, just shows your lack of understanding the scientific way.

4: babbling about slogans and homebrewed theories does not validate as an evidence. you have been asked and showned a proper way for it. yet you still all back on this child like argumentation.

5: The rules are states and objectively count for all of us. if you think the burden of proof is to high to lift maybe it just you that is wrong. but they are made to empower theories and change by validating them in a scientific way. that oyu cnat life the wualtiy of argumentation to that level does not mean it shut people up. it just means you probably need to do so until you have enough evidence to support it.  Plenty of people have showed lack of quality or founds issues through these means without any issues.

6: people have been leaving rational thinking for decades. that is not only this forum sadly. we cant educate people that don't want to be educated but prefer to stay in their blissful ignorance. I can only show you the way. You have to step through it yourself

if you still believe in what you are saying. You could have proven this a lot faster than the time you have been using on fighting  people asking you for a proof, being it test-samples or ABX.
People have asked into it because they are curios of your claim. You are acting like a spoiled child because people just don't jump aboard your hyper train immediately .
Sven Bent - Denmark

Re: Apple TVBR vs CVBR

Reply #18
The Listening Tests wiki page quotes the following for the most recent AAC Test:

http://wiki.hydrogenaud.io/index.php?title=Hydrogenaudio_Listening_Tests
"Quicktime CVBR ~> TVBR ~>Fraunhofer > CT > Nero"

meaning "About the same, but slightly better than". And in the Plot of the complete result, you can also witness that "slightly"

Those tests used:

 QuickTime True VBR (via qtaacenc)
--tvbr 46 --highest --samplerate keep
QuickTime Constrained VBR (via qtaacenc)
--cvbr 96 --highest --samplerate keep

Onto the bitrate comparison. Quote: "The codecs and settings were calibrated to provide ~96kbps on a large variety of music." In most samples TVBR had a lower bitrate. Leading to a mean of 93-94 versus 101 of CVBR.

Which raises the question. Are the small quality differences between the two just proportional to the bitrate difference?

It has been a while since the last test (2011) what has changed since then?

Would this be a reasonable test: TVBR is encoded first and then the CVBR bitrate is selected to match the TVBR (per song sample)

Re: Apple TVBR vs CVBR

Reply #19
The difference in bitrate is not the cause.  The purpose of the variable bitrate is keep quality constant by applying more or less bits per sample depending on the complexity of the music...  more complex...more bits...less complex...less bits.

The TVBR files are not properly tuned, as has been mentioned before, which leads to noticeable artifacts in the resulting encoded file.  These artifacts get more noticeable the lower the bitrate gets.

I personally use the iTunes Plus preset (qaac), which uses TVBR at a bitrate around 256 kbps.  The resulting file is completely transparent to me when I've tried to ABX it.

I don't believe there is any other way to get TVBR files out of iTunes, but that may have changed since I last checked.  The other VBR settings were actually ABR files... IIRC.
JXL

Re: Apple TVBR vs CVBR

Reply #20
I was playing with this CVBR vs TVBR (both @ the 80kbps setting) briefly a moment ago and I am pretty sure I do hear a difference in a specific part of a song as the TVBR file is 59kbps and the CVBR file is 82kbps. basically the singers vocals at a specific point in the song you can hear a artifact with the TVBR file where as it's gone with the CVBR file.

but I wonder if it's possible for the reverse to be true? ; like say a TVBR file ends up having a noticeably higher bit rate on a random song than the CVBR file and a artifact appears on the CVBR file but is gone on the TVBR file. because if this can happen, maybe TVBR would be the all around better choice due to it being a little more efficient with the bit rate. but then again, since CVBR seems to force bit rates more stable around your selected bit rate setting then it would be the all around safer choice if I am concerned with boosting sound quality a bit even though I suspect my average bit rate over the collection of songs will be a bit higher.

any thoughts or suggestions? ; or would I be better off using CVBR over TVBR when using such a low bit rate as 80kbps for overall sound quality reasons? ; because given the tests shown in this topic, it seems @ 96kbps it's about the same either way, but could it be different with 80kbps(?), or does that CVBR vs TVBR pretty much hold consistent throughout the bit rate spectrum in that it's too-close-to-call between the two settings overall?

but with that said, the overall song seems to be similar sound quality as I can't say, outside of the thing I mentioned (maybe a little more, but that's the only thing I feel fairly confident on claiming), that there is any noticeable difference for me.

NOTE: both files are AAC-LC (qaac 2.67, CoreAudioToolbox 7.10.9.0. encoded using Foobar2000 v1.3.17) and I was doing this test on my PC's Klipsch Pro-Media speakers. also, the song I used on the above test... 'Violin' from 'Amos Lee - Mission Bell (2011)' about 46 seconds into the song where he says 'shakedown' (specifically the 'shake' part) is where the CVBR and TVBR difference is noticeable.
For music I suggest (using Foobar2000)... MP3 (LAME) @ V5 (130kbps). NOTE: using on AGPTEK-U3 as of Mar 18th 2021. I use 'fatsort' (on Linux) so MP3's are listed in proper order on AGPTEK-U3.

Re: Apple TVBR vs CVBR

Reply #21
Hi ThaCrip, I did some TVBR and CVBR testing mostly on 128kbps, and I also hear some difference between them, but it's not about artifacts, but a sudden volume drop on TVBR, and I didn't hear that volume drop on CVBR...

Maybe AAC choose lower bitrate on certain part on TVBR, especially on lower bitrate...And I didn't hear that volume drop on TVBR Q91 192kbps...

It's a Japanese rock song, a lot of fast pace guitar and drum, that volume drop occur on a choir and drum part, as I remember it's happened twice on that song...

Re: Apple TVBR vs CVBR

Reply #22
I personally use the iTunes Plus preset (qaac), which uses TVBR at a bitrate around 256 kbps.  The resulting file is completely transparent to me when I've tried to ABX it.

Sorry Conan, I think I spotted an Error.

The Encoder Configuration Page claims that:
Code: [Select]
High Quality(128k)   -a128 -q1
iTunes Plus(256k)    -v256 -q2  (lowercase v, cvbr)

TVBR would be capital V as indicated in the usage options:
Code: [Select]
AAC TVBR 	--tvbr, -V (default)
AAC CVBR --cvbr, -v
AAC ABR --abr, -a
AAC CBR --cbr, -c
ALAC --alac, -A

It doesn't seem Apple uses TVBR on any of their presets. Unless the information is outdated.

https://github.com/nu774/qaac/wiki/Encoder-configuration



Re: Apple TVBR vs CVBR

Reply #23
Thanks for the info faizikari.

but I think instead of trying to run things to the edge on the quality side of things, ill just use the 96kbps TVBR setting instead (as it seems like a safe minimum as any lower and the chances of sound quality loss start to shoot up) and have to be a bit more selective on what I decide to fill the 2GB of internal storage space (probably more like 1.9GB or not much over that because I got Rockbox on it) on my old Sansa e250 (I had it 10 years this month I think). I am just doing this in case I ever decide to remove the 16GB MicroSDHC card from it in the future as then there will still be music on the internal memory if I need to use it (with the 16GB MicroSD card I just stick with 128kbps TVBR mode for important music and 96kbps for less important music as that's about as efficient as I can get and is pretty safe on sound quality to given tests around here).

but after looking around in these forums some more (i.e. https://hydrogenaud.io/index.php/topic,98951.msg821109.html#msg821109 ; basically that post and the four posts following it) I am starting to think CVBR is not really worth using overall given it seems to use roughly 7% more bit rate (maybe a fair amount more depending on the type of music you got) and the sound quality difference is negligible at 96kbps. so the extra storage space savings (with TVBR) are all around better than any tiny quality difference there may be (with CVBR) especially given 96kbps+ scores pretty well straight up in sound quality regardless of TVBR or CVBR. so instead of considering CVBR @ 80kbps, like I was attempting to do, I just went with TVBR @ 96kbps as I think there was only about a 10kbps average difference between the two (with TVBR being about 10kbps higher) as I would rather take the sound quality bump with 96kbps over 80kbps. 'maybe' CVBR is a little safer(on sound quality) if your using 80kbps and lower but then again since I am talking strictly AAC-LC (since it's standardized) it seems with Foobar2000 and it's Encoders Pack (with QAAC) that with CVBR it defaults to AAC-HE mode on anything lower than 80kbps (which 64kbps is the next lowest setting below 80kbps) but you can uncheck the box, which forces AAC-LC with CVBR, but I noticed a clear difference in basic sound quality @ 64kbps with AAC-LC on TVBR and CVBR as CVBR has a muffled sound to the overall sound (this does this on all songs as they lack clarity) in comparison to the FLAC where as with TVBR it still uses AAC-LC @ 64kbps settings (and everything lower (56/48/40)) and does not have the muffled sound at 64kbps (although I assume there will be a fair amount of artifacts etc). I know you can always enable the AAC-HE on the setting below 80kbps with CVBR, which cleans up the sound, but then device compatibility suffers, as those won't work on my Sansa e250 device as it requires too much CPU etc. but basically if my device could play AAC-HE files then it would have no problem playing Opus in which case I would just use Opus since it's better than AAC based on tests around here (in fact, AAC-HE is completely unusable on my Sansa e250 (music plays briefly and stops and continues) and device is nearly unusable) where as Opus is not completely unusable but it's not good enough to use either as you can see it's still taxing the CPU etc because when playing Opus, while they play, the general device navigation is quite sluggish).

@Makaki... I think CVBR 256kbps is what iTunes generally uses. while it's high quality sound, as no one will question the sound quality at that bit rate, it's largely a waste of storage space as you can have strong sound quality at literally half of that bit rate(i.e. 128kbps).

but given what I read around here.... it seems most people will likely prefer 96 or 128 or 160 settings since those are the sweet spot ranges as any lower than 96 and your really gambling with sound quality loss and any higher than 160 efficiency is pretty much shot as the sound quality gains beyond that seem to be slim if not very slim. I would suggest 128kbps for most people as it's quite efficient and does not lack on sound quality either as I suspect once someone hits the 128kbps rate your going to start to have to really nit pick to find flaws in the sound.
For music I suggest (using Foobar2000)... MP3 (LAME) @ V5 (130kbps). NOTE: using on AGPTEK-U3 as of Mar 18th 2021. I use 'fatsort' (on Linux) so MP3's are listed in proper order on AGPTEK-U3.

Re: Apple TVBR vs CVBR

Reply #24
ThaCrip, that slight volume drop actually didn't bother me as much, but I didn't expect to noticed it with my cheap earphone, and I did my ABX on TVBR Q64 128kbps and I didn't hear any artifacts, and TVBR Q64 128kbps maybe the lowest that I can go...

But on the safe side, I convert all my music collection to TVBR Q91 192kbps...

Based on an amazing listening test from Jplus, there's only one problem sample on 96, and also one problem sample on 128...

https://hydrogenaud.io/index.php/topic,99359.0.html