Opie and Anthony 2009-12-04-O&A CF128k VBR mp3
- Type:
- Audio > Other
- Files:
- 1
- Size:
- 157.17 MiB (164801859 Bytes)
- Tag(s):
- Opie and Anthony Rich Vos
- Uploaded:
- 2009-12-05 00:45:57 GMT
- By:
- mothergoose56
- Seeders:
- 0
- Leechers:
- 0
- Comments
- 4
- Info Hash: 41B92ABA2F3E09702F080835C2BDA09FA89B30EE
(Problems with magnets links are fixed by upgrading your torrent client!)
Opie and Anthony XM/Sirius show commercial-free uncensored 128k VBR mp3 Rip+Edit mg56 12/4/09 quick rundown: More Ventura fallout on Bill O'Reilly, Steven Seagal, Rich Vos in-studio, two new homeless for the OAHSS. For more O&A try shuazien: https://piratebayproxy.live/user/shuazien/ ------------------------------------------------------------------ Piratebay sale may happen at the end of the month (again)! Get your O&A here: https://isohunt.com/release?poster=mothergoose56 BOOKMARK THIS IMMEDIATELY so you can get O&A if/when tpb is gone. ------------------------------------------------------------------
File list not available. |
"what difference does it make when you convert an audio file into a higher bitrate?"
The 128k VBR's actually average about around 112k - but they peak at 128k
when needed, hence the "variable". During the quiet moments it drops when
not needed, hence the saving in file size. You are getting a slight drop
in quality from the re-encode, but (if I may gloat a bit) you are starting
with a pretty good source so it won't be too noticable. I've had people tell
me that 128k is too high, and it probably is a bit. I could get by with 112k
max, but I figure the vbr works it out in the end. I definitely noticed a
difference with only 96k max though.
If I were you I'd try cbr encodes at 96k, 112k and compare it to your 128k's.
You might find that it solves your vbr issues and saves you some file size too.
The 128k VBR's actually average about around 112k - but they peak at 128k
when needed, hence the "variable". During the quiet moments it drops when
not needed, hence the saving in file size. You are getting a slight drop
in quality from the re-encode, but (if I may gloat a bit) you are starting
with a pretty good source so it won't be too noticable. I've had people tell
me that 128k is too high, and it probably is a bit. I could get by with 112k
max, but I figure the vbr works it out in the end. I definitely noticed a
difference with only 96k max though.
If I were you I'd try cbr encodes at 96k, 112k and compare it to your 128k's.
You might find that it solves your vbr issues and saves you some file size too.
BTW, I've been trying to reply but I got "db error" every time.
The ones and the twos and the eights.
Thanks bud.
Thanks bud.
Cheers!!
Comments