|
|
Why we need a carrier of YOUR bankdata…back somewhere else…
First we have to invent mp3 then copy all songs
without to pay
Then we have to distribute the stuff like
http://www.imesh.com
and so on..
free music IS nice. Most people likes music = smart (not da car)
Download da track What is it?
http://computer.howstuffworks.com/mp31.htm
Using facts
like these, certain parts of a song can be eliminated without significantly
hurting the quality of the song for the listener. Compressing the rest of the
song with well-known compression techniques shrinks the song considerably -- by
a factor of 10 at least. (If you would like to learn more about the specific
compression algorithms, see the links at the end this article.) When you are
done creating an MP3 file, what you have is a "near CD quality" song.
The MP3 version of the song does not sound exactly the same as the original CD
song because some of it has been removed, but it's very close.
From this
description, you can see that MP3 is nothing magical. It is simply a file
format that compresses a song into a smaller size so it is easier to move
around on the Internet and store.
So
MPEG is the
acronym for Moving Picture Experts Group. This group has developed compression
systems used for video data. For example, DVD movies, HDTV broadcasts and DSS satellite systems use MPEG compression to fit video and
movie data into smaller spaces. The MPEG compression system includes a
subsystem to compress sound, called MPEG audio Layer-3. We know it by its
abbreviation, MP3.
So we have
different versions of mpeg and compression techniques
http://www.mp3-converter.com/mp3codec/bitrates.htm
CBR vs. VBR
Most of the
information you'll read in this book and elsewhere assumes that the bitstream is being encoded at a constant bitrate (CBR). In other words, if
you specify a 128 kbps encoding, then that's what you're going to get, start to
finish. The drawback to CBR is that most music isn't
structured with anything approaching a constant rate. Passages with many
instruments or voices are succeeded by passages with few,
simplicity follows complexity, and so on. The response to this situation has
been the development of variable bitrate
(VBR) encoders and decoders, which vary the bitrate
in accordance with the dynamics of the signal flowing through each frame. VBR technology was first implemented by Xing, which is now
owned by Real Networks, but is now supported by dozens, if not hundreds, of
third-party products.
Rather than
specifying a bitrate before encoding begins, the user
specifies a threshold, or tolerance, when encoding with VBR.
All notions of bits per second go right out the window, of course; instead, one
selects VBR quality on a variable scale. Confusingly,
this scale is represented differently in different encoders.
(confusion is the art
of adding confusion in contracts programming etc to get people to sleep and
accept that so others make holes in
your pocket …) = crime
While MusicMatch Jukebox gives you a scale of 1 to 100, the LAME
command-line encoder lets you specify a quality of 0 to 9, where the scale
represents a distortion ratio. Therefore, you can't just assume that higher
numbers mean higher quality-see the documentation for your encoder before
proceeding, or run the tests yourself. In any case, the scales are essentially
arbitrary; think of them as though you were using a slider to control
the overall quality versus file size ratio as you might with a JPEG editor.
http://www.mp3-converter.com/mp3codec/implementation.htm
The
specification only serves to guarantee a baseline consensus in the
community regarding how certain things will operate. An encoder developed
according to the MP3 specification will be capable of outputting a
"compliant bitstream" that can be played
successfully with any MP3-compliant decoder, just as you can create a JPEG file
in any image editor under any operating system and expect it to display
properly in any JPEG-compliant image viewer on any operating system
So we need a holdingtank for YOUR DATA out of YOUR machine or YOUR MOBILEPHONE (like mobile banking?) nada no chance for any
mp3 on your Mobbie? Or mp3 playerrrrrr
http://www.google.gr/search?hl=el&q=i-mode&meta=
A good
example of the kind of freedom left to developers is the fact that the MP3
standard does not specify exactly how to treat the upper end of the spectrum,
above 16kHz. Since human auditory
perception begins to diminish greatly (with age and exposure to loud volumes) between
16kHz and 20kHz, some developers have historically chosen
to simply chop off frequencies above 16kHz, which can be beneficial at low bitrates, since it leaves more bits available for encoding
more audible frequencies. Xing, for example, did this with the first versions
of their very fast codec. Later, they rewrote their codec to handle frequencies
up to 20kHz (probably at the behest of the audiophile
MP3 community).
1 tank
The
potential problem with running this kind of test lies in the fact that your
playback hardware may itself not be
capable of reproducing frequencies above, say, 17kHz
2 tank
the MP3 spec
allows for a "reservoir of
bytes," which acts as a sort of overflow buffer when the desired
amount of data cannot be stored in the given timeframe. In actual practice,
this reservoir is not a separate storage space in the file, but rather the "empty space" left
over in frames where the necessary information was encoded into the
available space with room to spare. In other words, the byte
reservoir is a portion of the algorithm
3 tank
stereo
versus mono and
largely
insensitive to the location of the
source of sounds at the very low
and very high ends of the frequency
spectrum.
And
the road out???
If joint stereo is used in M/S
(middle/side) mode, the left and right channels aren't encoded separately. Instead,
a "middle" channel is encoded
as the sum of the left and right channels, while a " side"
channel is stored as the difference between the left and the right.
So
http://www.mp3-converter.com/mp3codec/id3.htm
While
players developed to the actual ISO MPEG specification will know how to handle
either type, the specification itself is unfortunately vague on this point. It simply states that a player
should look for a " sync
header," without specifying
exactly where seeking should
start and stop. This (salmon?) laxness in the spec has caused some
controversy among developers of ID3-enabled applications, who naturally don't want
their applications seeking blindly
through 1GB image files, should the user happen to hand one to the application.
Fortunately, the ID3v2 spec is more specific on the matter.
What do we have ? holdingtanks-a road out-
We then
need to throw in adware spyware
viruses backdoors in windows little bit of sweet dual channel motherboards with
radiosenders and then we have all this near the cash machines
and atm machines making healty
“stock and shares at nice values..)
I ask what is the point…. Hmm
email for further checkup? kajander@nodns.org
Intressting
marketing JUST one of da few pir
(ooosorry) privatized telcos..
Renault F1 ? Avec qu… moi?... to slow boiling over ? no water?
is it da eva jolly boy AGAIN…behind ? nada
chance? To mucho pernodo (prefer whiskey..)