ryanw said:Right... because iPods currently aren't selling well?
And YOU know that NOT quoting a person and NOT writing a reply is a good way to indicate that you are NOT commenting about what they wrote.matticus008 said:And YOU know that my comment wasn't necessarily directed AT you.
What part of "BITrates are pretty much usually referenced in BITS that's why it's called BITrates...as opposed to BYTErates" did you not understand?And also I'm sure you're aware that while all of this talk of why we don't use bytes for bitrates is nice, the word "bitrate" pretty much takes care of it right off the bat, and that's great, but that wasn't the point.
That's B.S. Bits are usually the basis for the unit of measurement regarding data rates (transmission). Bytes are usually the basis for the unit of measurement regarding storage/space.Since this thread deals with Bluetooth and hence data transmission, we are ultimately speaking of the transfer of bytes as a more concrete and functional discussion.
No it wasn't, but thanks for using bitrate instead of byterate. The point was that someone erroneously stated what the bitrate of CDs were to begin with. Knowing the real-world performance of any transmission protocol ain't gonna help you evaluate what can be done if you significantly underestimate the level that is required...which is exactly what I was pointing out.The bitrate of CD quality music is a separate issue from transmitting data across an RF connection, so the point was placing the requirements of CD audio in comparison to the transmission capacity of Bluetooth 2.0, while not failing to remember the various factors that can affect transfer speed and reduce actual available bandwidth.
No, it's a misconception. A loose generalization would mean that audio CDs did average out to 1200 kbps or in the ballpark thereof. That is significantly wrong. Audio CDs are exactly 1411 kbps, not a bit more or less.And the 150K/sec reference isn't a misconception, it's a loose generalization. CD drives do not read at a uniform velocity across the entire disc, meaning that any single number to refer to data handling is not constant, but variable.
Of course, but that's not what I was talking about. Sending CD audio out at AS DATA in speeds less than that of the bit rate of the audio doesn't do much in terms of listening to the audio in real-time now does it?1X CD-ROM drives for data purposes could indeed handle CD-audio through the IDE or SCSI connector
"Digital audio extraction development" had nothing to do with it. Drives at the time (1X) could simply not rip data fast enough to support a CD audio stream PERIOD. While some machines may have had bus issues, hell, some do today, playing audio CDs through SCSI or IDE was not going to happen until 2X drives came out.but for the purposes of early CD-audio, it went straight to the audio subsystem because of latency and data overhead on the bus, and because digital audio extraction was underdeveloped.
C'mon you guys. These "my encyclopedia is bigger than yours!" contests really shouldn't be discussed in this thread. Or any, if I could choose.MacSlut said:And YOU know that NOT quoting a person and NOT writing a reply is a good way to indicate that you are NOT commenting about what they wrote...
BLAH BLAH BLAH BLAH
...This is why I specifically said "play audio CDs", instead of "rip audio from CDs"."Digital audio extraction development" had nothing to do with it. Drives at the time (1X) could simply not rip data fast enough to support a CD audio stream PERIOD. While some machines may have had bus issues, hell, some do today, playing audio CDs through SCSI or IDE was not going to happen until 2X drives came out.
MacSlut said:<snip>
Jean-Pierre Bob said:I speak and understand French, even if my mothertongue is Dutch ;-)
I just listened to the interview that you can find in real audio on this page: http://www.mactouch.com/breve.php?id_breve=0484 at the bottom
The Motorola guy says:
"Il y a des iPods qui vont sortir bientôt avec la technologie Bluetooth"
Translation: "There are Ipods that will come out soon with Bluetooth technology."
Manowatt said:I'm surprised no one has pointed out the similarities this story shares with the recently announced Griffin BlueTrip...
http://griffintechnology.com/products/bluetrip/index.php
Although their tech specs are not very enlightening, it sounds promising. Has anyone heard anything more on this? Anybody seen a photo of the transmitter?
_b
Chaszmyr said:And lets not confuse bits and bytes here, people. 3mbps means 3 megabits per second. 3 megabits per second isn't anywhere close to 3 megabytes per second.
For a bit of perspective: Bluetooth 2.0 is less than half the speed of USB 1.1
That's great that you like to use a unit of measurement that is imprecise at not what is used by any major media or print publication. Remember though that *I* was not the one trying to correct someone for using K versus k, I was correcting someone who was significantly off in what they thought the bit rate was for CDs.combatcolin said:MacSlut switch to decaff mate.
I and many other people like to use Kbytes instead of Kbits as you can relate more easily to it.
No, no, no...an audio CD not only needs "150K" to work (in realtime) it needs significantly *more* than that. It needs exactly 1411kbps...not as an average, but a constant rate.And an audio CD does not need all the 150K transfer speed to work, somthing i remember from my Spectrum days when they were talking about hooking normal cd players to a spectrum and transfering the information that way.
Uh, no I wasn't. MSCONVERT originally posted that an audio CD was "1.4 Mbit/sec" and thus way too large for bluetooth 1.0. They were correct in the bitrate of an audio CD (rounded down). COMBATCOLIN tried to correct MSCONVERT by saying audio CDs were 150K/sec. All I did was post "no, audio CDs are 1411kbps". How was that being hostile? If "it doesn't matter" then why where either of you trying to correct MSCONVERT or myself who were entirely correct to begin with? You're argument is essentially, "we like using K instead of k and we like pretending that audio CDs have significantly lower data rates than 1411kbps". I'm sorry if the truth hurts your feelings.matticus008 said:Otherwise, it's a public forum, and you were being needlessly hostile against a guy who used a 1x CD speed instead of the exact bitrate of the audio WHICH DOESN'T MATTER.
Yes they were. This was exactly what MSCONVERT was originally posting about when COMBATCOLIN erroneously tried to correct him on the bitrate of audio CDs. As far as "my confusion" over bits and bytes, I'm not the one trying to use the term contrary to every major media and print publication, nor am I the one who thinks 1411/8 = 150 or even exactly 176 for that matter.EDIT: And just to inform you, no one is talking about playing CDs live over Bluetooth, so your confusion over bits and bytes and "real time" CD playback can just be skipped.
migue said:it says that the transmitter works with all dockable iPods up to 4G, but doesn't mention the mini. This - may be a confirmation that Apple intends to push BT 2.0 (don't forget, it has more bandwidth but consumes 40% less power) across the board starting with the mini 2G and next generation iPods. would also mean that the nine iPod automobile makers mentioned at the keynote can now have a standard BT receiver - instead of a dock for each generation, which saves costs.
sinisterdesign said:all i know is that I would be happy w/ a friggin' remote (bluetooh, RF, IR or gamma rays, i don't care) that can control my iTunes/Airpot XP so i don't have to keep running downstairs when i want to skip a track.
BillHarrison said:Plus syncing wirelessly is kinda nifty too. Come on apple, add a bigger color screen, and some pda functions, and this pocket pc can go out the window!
Bill
qzak said:it does mention the mini....
"What iPods are compatible with BlueTrip?
BlueTrip works with all dockable iPods (3G, 4G, iPod mini, and iPod photo). "