Keep Track Of Your Filenames

[darkewolf]

I guess that it is possible that the program that I use to rip (goldwave) could be adding that info to the files. Not sure, I dunno. It's using the LAME codecs for mp3.

ID3 tags? 'Splain that to somebody that is sorta new to this, please?

[echidna]

Originally posted by darkewolf+9 November 2003 - 11:39--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (darkewolf &#064; 9 November 2003 - 11:39)</td></tr><tr><td id='QUOTE'>I guess that it is possible that the program that I use to rip (goldwave) could be adding that info to the files.&nbsp; Not sure, I dunno.&nbsp; It&#39;s using the LAME codecs for mp3.

&nbsp; ID3 tags?&nbsp; &#39;Splain that to somebody that is sorta new to this, please?[/b]

ID3 is a means of keeping text &#39;meta-data&#39; with digital audio files
more specifically;

<!--QuoteBegin-http://www.id3.org/history.html
The past

Once upon a time, there were some giant companies that, with the failure of the 4-channel battle fresh in mind, formed an expert group with the mission to invent tomorrow&#39;s technology in sound compression. Fortunately, they did. The format, named MPEG Layer 3 or for short MP3, took advantage of the fact that our ears are not nearly as good as we generally believe them to be, and thus omitting frequencies that we wouldn&#39;t hear anyway. They also made the format suitable for streaming by letting the sound be represented in small, individually compressed blocks of audio data. Each block had a header containing some information relevant to the decoding process. As they ended up with a few bits to much, they used them for some additional information such as a &#39;copyright&#39; bit and a &#39;private&#39; bit.

Since the format had such an outstanding compression and still very good sound quality, it was soon adapted as the de facto standard for digital music. The lack of possibilities to include textual information in the files was however disturbingly present. Suddenly, someone (Eric Kemp alias NamkraD, I&#39;ve been told) had a vision of a fix-sized 128-byte tag that would reside at the end of the audio file. It would include title, artist, album, year, genre and a comment field. Someone, possibly the very same someone, implemented this and everyone was happy. Soon afterwards, Michael Mutschler, the author of MP3ext, extended this tag, called ID3, to also include which track on the CD the music originated from. He used the last two bytes of the comment field for this and named his variant ID3 v1.1. (more information about ID3 and ID3v1.1 can be found here).

The present

The ID3 v1.1 tag still had some obvious limitations and drawbacks, though. It supported only a few fields of information, and those were limited to 30 characters, making it impossible to correctly describe "The Hitchhiker&#39;s Guide to the Galaxy from BBC Radio" as well as "P.I. Tchaikovsky&#39;s Nutcracker Suite Op. 71 a, Ouverture miniature danses caractéristiques by The New Philharmonic Orchestra, London, conducted by Laurence Siegel". Since the position of the ID3 v1.1 tag is at the end of the audio file it will also be the last thing to arrive when the file is being streamed. The fix size of 128 bytes also makes it impossible to extend further. That&#39;s why I (Martin Nilsson) and several along with me thought that a new ID3 tag would be appropriate.

The new ID3 tag is named ID3v2 and is currently in a state of &#39;informal standard&#39;. That is, we decided, since there were less and less improvements and additions made, to proclaim the draft as a standard (an informal one since no standardization body has approved this decision). You can find the informal standard here. ID3v2 is often followed by its revision number, i.e. the current informal standard is ID3v2.4.0.[/quote]

hope th@ helps

ed. :: fixing hyperlink

[darkewolf]

aye, it verifies what I thought you were talking about, thanks

[iHadYourMomLastNight]

Originally posted by echidna+6 November 2003 - 01:56--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (echidna @ 6 November 2003 - 01:56)</td></tr><tr><td id='QUOTE'>

Originally posted by iHadYourMomLastNight+6 November 2003 - 10:02--></div><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (iHadYourMomLastNight @ 6 November 2003 - 10:02)</td></tr><tr><td id='QUOTE'> on another note, what quality bitrate do you people rip your mp3's at. all ive heard the past few weeks is that you don't want any less than 192kps VBR if possible. &nbsp; i used to rip at 128kps and i did notice quite a difff when i switched to 160kps, but i really can' t hear the difference between 160kps CBR & 192kps VBR.
what bitrate do you guys rip at?[/b]

lame --alt-preset standard
it seems to encode at between 160-192 and higher at variable bitrate, depending on the data. B)


PS :: ripping is getting audio CDs onto hard disk, encoding is making a compressed version of a rip.

<!--QuoteBegin-barbarossa@ 6 November 2003 - 01:13

When you edit the details in kazaa (lite) you are editing the details as stored in the .dbb files in the DB folder of the kazaa (lite) installation.

i can't find any DB folder in my K++ install

<!--QuoteBegin-Exploring - Kazaa Lite K++
C:\Program Files\Kazaa Lite K++
C:\Program Files\Kazaa Lite K++\BannedIPs
C:\Program Files\Kazaa Lite K++\Kazupernodes
C:\Program Files\Kazaa Lite K++\Kazupernodes\Data
C:\Program Files\Kazaa Lite K++\Skins
C:\Program Files\Kazaa Lite K++\web[/quote]

but since i can't find them and K++ still works fine, i don't know what you mean [/b][/quote]

[iHadYourMomLastNight]

Originally posted by echidna@5 November 2003 - 13:22


does anyone know if we should be using version 1 or version 2 of ID3?
which version is kazaa using?

i use version 2 and the reason why is here Audio Tagging Intro.....

on another note , i found something interesting this evening. someone on this thread posted earlier about the Kazaa reading the tag wrong.
here&#39;s what i found..........i was ripping(encoding, watever) at CBR(constant bit rate) 160/kps. i thought i couldn&#39;t tell the diff. well, many argued with me so i sat down in front of my hi fi at home ( has pc running to amp) and listened over and over to a STone Sour song that i ripped at CBR 160kps, CBR 192kps, & VBR 160-192kps. i could barely notice a diff if any at all. if i did notice a diff it was in the hi freq. range and not the lows (perhaps it was a better encoding of the voice. im unsure). anywayz that was enuff to convince me to use the VBR rate of 160-192kps. using that bit rate was just a bit bigger than the 160 CBR but not near as big as the 192 CBR. that tells me that 160 CBR is close but needs just a little more hard drive space for the complicated parts of the song. since there is no bit rate between 160 and 192 i reccomend using the VBR(variable bit rate 160-192). OK i know wat your thinxing "where the hell is this stoner going with this".
here&#39;s the kicker........Kazaa lite recognized all my id3v2 tags that were ripped at 160kps CBR but once i changed to the VBR of 160-192kps the tags were listed wrong thru Kazaa lite ( the my kazaa in the software engine) the times of the songs were wrong (usually longer than they actually are), the sizes of the files were listed wrong as well, and most annoying of all is that Kazaa lite listed the songs ripped at 128kps&#33;&#33;&#33;&#33;&#33;&#33; That&#39;s terrible cuz at this higher bit rate the song&#39;s quality is much better than at 128&#33;&#33;&#33;&#33; it makes me wonder how many songs ive past by in kazaa becuz of it listing it as 128kps.
Does anyone know how to remedy this. Now MusicMatchJukeBox read the tags correctly. Window Media Player 9 did as well, but the mini Windows media Player 2 read the times incorrectly as well.
Is there some kind of decoder i need to install that is new enuff to read these VBR mp3&#39;s accuratley? or just deal with it........ i dunno , do you?