This has been an age old question since Mp3s were created. However, I'm going to disagree with you there on saying that CD quality = 192kb. I've heard 192kb files and they sound like complete garbage. If you're looking for true "CD quality" that would be LPCM 44100 Hz 16 bits stereo for a bitrate of 1411 kbps.
It really does depend on the file. However, if we're talking about most 192KB music files, they tend to sound "tinny" or shallow. There's not a lot of depth to the sound as compared to quality you would get from a CD.
It's very easy to tell the difference between 192kbps and FLAC if you have a decent subwoofer and the song ever goes below 30hz. On run-of-the-mill speakers and earbuds, probably not.
It's extremely rare for music to contain anything below 30Hz. Even below 40Hz is rare. The only place you're likely to find such low frequencies is sound effects in movie soundtracks.
Interestingly, a lot of "bass heavy" music focuses on frequencies around 50Hz, not the really deep sub-bass. This makes sense when you consider human hearing. Those higher frequencies sound much louder to us, and they're still low enough to get the tactile feeling.
I've heard this before elsewhere and the response then was that the person was confusing kilobits with kilobytes. 1411kbps/8bits/byte = 176.375Kbps. The closest you can get to that is 192Kbps. There's a big difference there.
From Wikipedia's page on Compact Disc Digital Audio:
Each audio sample is a signed 16-bit two's complement integer, with sample values ranging from −32768 to +32767. The source audio data is divided into frames, containing twelve samples each (six left and right samples, alternating), for a total of 192 bits (24 bytes) of audio data per frame.
That has nothing to do with the bitrate -- the fact that you're getting a different unit on your 192 should be in an indication (bits or bits/frame, as opposed to kilobits/second).
CDs store audio as 16 bit samples, with 44100 samples per second. This gives a bitrate of 16 bits * 44100 Hz = 705600 bits/second (705.6 Kbps). This is per channel, so the total bitrate of the format is 1411.2 kbps, as stated (modulo rounding) by the GP.
EDIT: in fact, the article you link specifically says (a couple sections further down) that the bitrate is 1411.2 kbps.
Plunk | Remote | Full-Time whoisplunk.com
- Biz Dev/Outside Sales - Web/Mobile Developers
Plunk is a digital marketing agency focused on how emerging technology can be used to connect people with the things they care about.
Biz Dev/Sales: We are currently looking for motivated individuals to help grow our business. This is for all major cities across the U.S. You'll help us work to establish our partnership pipeline as well as look for direct client work. Competitive compensation package available. Developers: We are looking for experienced Developers who have an eye for detail and can work in an agile team.
Please send resumes to jobs@plunkus.com for consideration.
This tip is the equivalent to "Dial 0 when you reach an IVR." Having been in Support in the past I can tell you there is nothing worse than having someone email some random Exec because you're not getting anywhere with Support. While I'm not trying to defend what happened here, I can certainly empathize. I liken to someone who has worked as a Waiter/Waitress. When they go to a restaurant they'll have more empathy for someone than someone that hasn't done that job. But yeah, they should have noticed what the problem was in a better way and, if things were escalating, either pass it off to someone else or let their Manager know things we getting heated.
If you really want a "pro tip" about Support, ask your Rep to inform their Manager. If things aren't going well you have every right to keep going up the chain of command. If that doesn't work, keep going. Somehow you'll reach the right Exec instead of just guessing.
Plunk is a digital marketing agency focused on how emerging technology can be used to connect people with the things they care about.
Biz Dev/Sales: We are currently looking for motivated individuals to help grow our business. This is for all major cities across the U.S. You'll help us work to establish our partnership pipeline as well as look for direct client work. Competitive compensation package available.
Developers: We are looking for experienced Developers who have an eye for detail and can work in an agile team.
Please send resumes to jobs@plunkus.com for consideration.
I should have been more clear. I was looking at how many API calls a typical app would make when gathering data. Is it in the hundred, thousands? On average. Or that too wide of a question to get an accurate metric?
It's too wide of a question because of several reasons:
1. What do you count as an API request? Do you mean requests to "external" APIs? Or do you mean requesting content from the actual app server (e.g. Facebook loading timeline content)? Which API requests are you interested in?
2. What is a "typical app"? A game? A news reader? Twitter?
Even if someone could give you an answer that answer would most likely be irrelevant. API requests are a design choice. You can build the same app making 100 requests or 1 request for the same content. Both have tradeoffs.
Obviously it also depends on how much the user uses the app.
1. In this case an API request would be GET and POST of data.
2. I'm looking for a range here. And this is just gathering data from an app. So on the high end think Candy Crush. On the low end, your everyday lower tier app.
I recognize the API design is a choice, but in this case I'm looking to find out how many API requests would typically be made to gather data for the most popular app vs. an everyday run of the mill app.
Plunk is a digital marketing agency focused on how emerging technology can be used to connect people with the things they care about.
Biz Dev/Sales: We are currently looking for motivated individuals to help grow our business. This is for all major cities across the U.S. You'll help us work to establish our partnership pipeline as well as look for direct client work. Competitive compensation package available.
Developers: We are looking for experienced Developers who have an eye for detail and can work in an agile team.
Please send resumes to jobs@plunkus.com for consideration.
This seems a bit misleading. You still have to get everything set up through your application and that takes some Developer knowledge. What am I missing?
I'm really trying to stay objective here because I do love me some Mixpanel. However, I'm curious what the response will be to someone with nominal Developer skills who outsourced their app, but sees this as an opportunity to save some money to get data. Seems like a poor experience from a user perspective to get this codeless product going.
We tend to see it as there are many more people in the world who aren't developers that get some valuable data as opposed to guessing or using their gut. For developers, we still have a manual way to do this.
