To give you a bit of context, iTunes (the music side) delivers its audio files at 256 kilobits per second, or kbps. But we do, and therefore you have to find a balance between audio quality and file size. That’s why the whole argument arises: if we didn’t have to worry about file size, we’d use the highest bitrate we could. And since we’re still sending this stuff over the interwebs, file size matters. Higher bitrates store more data, though – more thousands of bits – and therefore lead to higher file sizes. As you’d imagine, that naturally translates to higher quality for higher bitrates, since it stores more of the detail of the original. A higher bitrate means storing more of the complexity, and a lower bitrate means less. When related to audio, this refers to how much of the detail of that audio, or how much of its complexity, we can store. So that means it measures how many thousands of bits are sent from one place to another every second. The common unit for audio is kilobits per second. A bit is the smallest unit of data you can find, so that translates as the rate at which you can transfer data. We asked about bitrates in our Podcaster Cares Surveyīitrate as a concept is actually pretty simple – it’s just a measure of the rate at which you can transfer bits. Easy! But… there are a couple of caveats, so let’s cover them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |