1000 Kbps Music

[Semarias Alfna]

Doesanyone know the bit rate of the songs that come on the Slotradio cards? My guess would be that it is pretty low in order to fit 1000 songs and have room left over to add your own songs to the card.

My guess is that the Slotradio card is 4GB, since there are Slotradio+ cards available that have 4 GB free space. If the Slotradio card was 8 GB, then the Slotradio+ cards would have 8 GB of free space. A thousand songs in 4 GB would mean a bitrate of 128 kbps, but the Slotmusic Oldies card sounds better than 128 kbps mp3, so some more advanced/better sounding format is probably used.

My guess is that the Slotradio card is 4GB, since there are Slotradio+ cards available that have 4 GB free space. If the Slotradio card was 8 GB, then the Slotradio+ cards would have 8 GB of free space. A thousand songs in 4 GB would mean a bitrate of 128 kbps, but the Slotmusic Oldies card sounds better than 128 kbps mp3 , so some more advanced/better sounding format is probably used.

The reason for this is that kbps stands for Kilobytes per second (remember our keys above), so literally how many KB per second of song do I need. The more KBPS the file is, the more of the original audio file that can be converted without having to remove what your PC thinks it should remove.

For example if you go into iTues to convert your CD into MP3 we are given the options below. If you need help converting your CD into MP3, you can check out our other Blog on using iTunes to convert MP3.

I am sure that most of us have more than 100 songs, unlikely to have over 4000 so an MP3 player with 8GB should do the job, if full of music, then our 16GB MP3 version will cover you off or an MP3 player with interchangeable memory

Most music streaming sites will download in different file formats, the all work slightly differently, for example iTunes uses their own file type so if you purchase these, you need to use them on an Apple device, try and take it to a friends then it won't work, Amazon download in Mp3 which is more universal.

These come down to file type, such as JPEG, BMP, GIFF, all of these will compress your pictures in different ways, some being harsher than others. With compression, the program you use will remove certain parts of the photo, the more its compressed, the worse the image looks, the programs we have can only guess what to remove, normally taking the odd pixel or combining a few.

JPEG is a good middle of the range file type that keeps a decent picture but not taking up masses of space. For a full list and breakdown of different file types you can have a look on Wiki as there are far to many to mention here.

What difference does this make? Well if you get a picture that's 10 dots across and down, your 100 dots if zoomed in become larger and it will distort the picture, get a 4K HD TV and you have 4096 x 2160 pixels so it takes a lot of zooming before these start to become blurry, it is this (partially) that gives you the better image but at a greater file size.

Well a lot, but even with all this there isn't a definitive answer that can be given, even with all this, the same phone at the same resolution could take 2 images that differ in size, this is just down to how digital photos are processed and the software tricks that come into force, if you play it safe at 2MB per image then you can't go wrong, if your a pro photographer with the top of the line equipment then this won't be accurate but if you taking a pic on holiday or a selfie with your mates, its a fine rule. Therefore here is a rough guide on how much memory you need.

This is an easier one to answer, there is of course your PC, most PC's today will come with 100+GB (50,000 images or 25,000 songs) if you need to have a backup of your data then one of the many cloud providers such as Google or Apple can be used as an extra hard drive, normally for free, great as a backup but no good for portability.

Want your files to be portable and easily accessible everywhere, then a flash drive should work, it acts like an external hard drive, just by plugging into the USB port, also great if you have a digital photo frame.

Generally, the lower the bitrate, the lower quality of sound. Lower quality means you have a smaller frequency range in your song (high frequencies drop off with lower kbps). This equates to playing a song say in a club, it would sound like it was recorded with a potato as opposed to a professional studio. It's like a low-resolution image compared to 4K.

Songs on your music streaming services are usually encoded in 128-320kbps files in various formats. Music bought from iTunes is encoded as 256kbps AAC. And music from Beatport can be 320kbps MP3 codecs or WAV/AIFF files. Confused yet? Bring in the potatoes.

MP3 (MPEG-1 Audio Layer 3) would be the potato you find in fast food fries. It's cheap, tasty and everywhere. It's a lossy format, as in to reduce the original audio file significantly it had to be compressed losing audio information. That's why MP3 is a cheap potato, and also a dying format.

AAC (Advanced Audio Codec) would be the slightly better potato that is replacing the MP3. It's like the chips you find at the hipster pubs with aioli. It's also a lossy format. You will find AAC music will have ".m4a" or "AAC" file extensions. Make sure you check that your DJ equipment accepts AAC (most new ones do anyway).

WAV (Waveform Audio File) and AIFF (Audio Interchange File Format) are both uncompressed audio files (lossless format) as they retain all audio information. These are the original potatoes, still fresh and unpeeled; and are usually over 100MB. These are what producers are working with until the files need to be mastered and dithered.

I was DJing at a pretty popular club and decided to put a rare track I found from the internet. The ID3 tag said the MP3's bitrate was 320kbps. In the club, all the club goers and I found out it was the notoriously 128kbps potato sound upscaled as 320kbps. Never again.

This problem wouldn't have happened if I used a bitrate checker like Spek Audio Spectrum Analyzer ("Spek" is Dutch for bacon, hence the pig logo). Spek checks the true frequencies of the track and determines the true bitrate.

This utility calculates the size of audio files (both uncompressed, PCM/IEEE FP audio, such as .WAV/ .W64/ .RF64, .AIFF/.AIF and also lossy compressed files such as MP3, WMA, AAC and OGG Vorbis), according to the recording duration and file settings you choose:

Enter the duration of your file in hours, minutes, seconds and milliseconds. Calculating the size of uncompressed files also requires the Sample Rate, Bit Depth and Channel information (but not the Bit Rate, which is automatically calculated). In addition to the duration, calculating the size of compressed files such as MP3 etc. requires only the Bit Rate information (in this case the Sample Rate, Bit Depth and Channel information is ignored). For compressed files encoded with CBR (Constant Bit Rate), the displayed file size should be as accurate as possible (notwithstanding variables such as header information etc- see below). For compressed files encoded with VBR (Variable Bit Rate), the displayed file size can be slightly less accurate because in this case the bit rate can vary depending on the programme material.

I have a 16GB sd card and would like to know how many hours of telephone quality audio, mono could be fitted into this. I read in an earlier post of yours, that when you made a blank recording lasting 74 minutes, it took up about 68mbs of memory. From that you concluded that there were 234 lots of 74 mins wav capacity on the sd card. Ie 290hours.

Hello, my question is the following: At the same sampling frequency, why is the size of an 8-bit WAV half that of a 16-bit WAV if 256 resolution positions are stored in 8 bits and in 16 bits do they keep 65536?

You just stopped my brain being fried. Working out 3 gigs this weekend with 14 tracks of differing rates, time etc. I either launched my calculator oot the widow or used this and, woo hoo, in seconds I had all answers for all 3 gigs. Pure magic. Thanks

Glad you found this site useful and that you found a solution. You are indeed correct, though your formula could be simplified for clarity. In fact, the simplest formulae for calculating either file size, duration or bit rate would be:

A sound engineer has chosen to record the background audio for an upcoming movie in stereo. To produce a high quality non-compressed digital audio file, the sound engineer will use a bit depth of 16 and a sample rate of 88kHz. What would be the approximate resulting file size for a 1.5 minute 37 second audio track?

Since you ask for my advice; I suggest that you always record to WAV files in future (which are uncompressed and non-lossy) and NOT mp3 (which are both compressed AND lossy). Mp3 is fine as a delivery format but (for several reasons too involved to go into here) far from ideal as a recording format. Personally, I would always record spoken material (music is a little different) as a standard WAV file at either 44.1kHz/16-bit or 48kHz/16-bit. You can then convert to mp3 (or whatever other format may be required) for delivery, keeping the original WAV files intact in case you might need to convert them to a different format later without any loss of audio quality.

1. Is this really an audio file? If so, 47 kbps is extremely low (even for a lossy compressed format) and would likely represent pretty poor audio quality. Reducing it further may even render it useless.

2. If you really must lower the bit rate, then you should convert the file again (but with the new settings) from the original, uncompressed audio file. Converting an already lossy compressed file again will reduce its quality even further.

I think the binary (2^10) to decimal (1000) converter is off. It just multiplies by 1.024, but that only works for KiB -> kB. For MiB -> MB it needs 1.024^2, for GiB -> GB 1.024^3, and so on, given that the binary prefix equivalent is 2^(10*n/3), where n is the power in 10^n.

3a8082e126