Strange Sound, Screeching Songs...et Cetera

OK guys, THIS IS WHAT THE PROBLEM REALLY IS!!! So check this out. I'm dropping some real knowledge. Fu*k that RIAA sh*t and all that. That's bull.
The reason your downloaded MP3 makes that noisy and scratchy sound, it's because of how KaZaa Lite download works.
See, if you download a popular song, which usually is owned by many users more than 5, the download manager automatically tries to download the file from many users simultaneously.
Like... I have a MP3 file and you have the file too, then the 3rd person tries to download it and he gets it from both of us, you know? Like... if the file is 5Megs big, he downloads 2.5Megs from me and 2.5Megs from you... something like that.
Then the problem is, actually the files we have are DIFFERENT files!!!
So, the file does not have the integrity, since you have downloaded a file from two different files, which looked same because their sizes were same.
Try, if you download a file which is owned by ONLY ONE guy, this problem never happens.
Is there a solution for this problem? I DON'T KNOW YET. I am trying to do anything to download from only one guy, but it seems that the setting of KaZaA Lite is always forcing us to download from MANY members.
I don't know how to tell this to the programmers for KaZaA Lite, so could someone please report this to them if you know how to? There should be an option which disables downloads from many people but only one person.

http://www.mcbriens.net/liam/img/smilies/yes.gif

Quote:

---

Originally posted by rappersk@9 October 2003 - 01:46
something that seems right on the surface

---

But I download other song files from an upwards of 1,000 users (U2--Mysterious Ways) and I never have that problem. You are right, that is how K-Lite (and Kazaa) work, but I don't think that's the cause.

well I used a solution this guy posted way in the beginning. ANY file with a number in the filename at the start for example Will_Smith_-02-_XXXX.mp3 are ALWAYS files with the noise. when I downloaded the same file without the numbers they ALWAYS worked perfect. the numbers could be anywhere but usually the beginning. oh and I noticed always has the _ in the filename too.

moldavia

Yes,right more info from Zeropaid forum.

Quote:

---

It is true that users with NUMBERS behind their nicknames are in fact fake kazaa users. Or bots. I have Peerguardian and herees what i saw when i tried to download a new cd before the release dates.. Peerguardian blocked these ip's.. BUT IT DIDNT block the defualtuser, or kazaa lite improved user cause their ips was good in sharing the song.
Connection forcefully closed on: 66.28.91.205 - CORGENT
Connection forcefully closed on: 66.28.91.205 - CORGENT
Connection forcefully closed on: 216.144.229.145 - SHA1 Hash Faker
Connection forcefully closed on: 216.144.229.145 - SHA1 Hash Faker
Connection forcefully closed on: 66.28.101.200 - CORGENT
Connection forcefully closed on: 66.28.101.200 - CORGENT
Connection forcefully closed on: 66.28.101.7 - CORGENT
Connection forcefully closed on: 66.28.101.7 - CORGENT
Connection forcefully closed on: 66.28.91.216 - CORGENT
Connection forcefully closed on: 66.28.91.216 - CORGENT
Connection forcefully closed on: 66.28.101.197 - CORGENT
Connection forcefully closed on: 66.28.101.197 - CORGENT
Connection forcefully closed on: 66.28.101.197 - CORGENT
Connection forcefully closed on: 66.28.101.197 - CORGENT
Connection forcefully closed on: 216.144.229.143 - SHA1 Hash Faker
Connection forcefully closed on: 216.144.229.143 - SHA1 Hash Faker
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.15 - NCI
Connection forcefully closed on: 66.54.89.2 - NCI
Connection forcefully closed on: 66.54.89.2 - NCI
Connection forcefully closed on: 66.54.89.2 - NCI
Connection forcefully closed on: 66.28.101.210 - CORGENT
Connection forcefully closed on: 66.28.101.210 - CORGENT
Connection forcefully closed on: 66.28.101.210 - CORGENT
Connection forcefully closed on: 66.28.101.210 - CORGENT
You will see variable files of it.. more then 1 meg for a song at 128 quality to 7megs for 128 quality.. and the song or suppose to be song ends, and two or three minutes of noise afterwards.. Are they hashing up to the 400kbytes that kazaa does for real files and then filling in noise afterwards..? I will wait to the album is fully released to get the retail version, But i did this to prove a point that why use any name and can use the same name.. why people with numbers other then 69 behind them? there was 54 people sharing the same song, and all of them had numbers behind their nicks, not one defualt user or anything. So downloading from big users base is something to be left in past. I suggest we make a p2p program to have just OGG files.. and 192kbs only.. and able to update supernodes to block out these fake files.

---

* In reply to rappersk*

Quote:

---

OK guys, THIS IS WHAT THE PROBLEM REALLY IS!!! So check this out. I'm dropping some real knowledge. Fu*k that RIAA sh*t and all that. That's bull.
The reason your downloaded MP3 makes that noisy and scratchy sound, it's because of how KaZaa Lite download works.
See, if you download a popular song, which usually is owned by many users more than 5, the download manager automatically tries to download the file from many users simultaneously. Etc.. Etc...

---

ok.. man your problem that is REALLY going on is all in your HeD...

Yea if you download from one person you are set.... Not because its not splitting your file up between users but because.. That one person alone has that file and most likely They alone recorded it on their computer.
But see here is the part that blast yer Idea out of the water.. Go to Kazaa Lite K++ Options then to the K++ Advanced options tab.. From there put max scources per file to ONE and restart Kazaa. (that would be because it has the (*) hence you must restart for it to take effect) Now get back in and search for a file that you know is popular and fucks up.. Get the one with the MOST people sharing the same file as possible.. And press the plus(+) sign to pan it out... now download it from one of those people.. It might download from a different person but it is still downloading from ONE person and it is gonna be Fucked up Most of the time... You might happen to get one of those files downloading that are true without all the numbers but most of the time you will get shit. AND! also.. the reason you are giving would have been doing that all along.... This just started happening..

I would have to aggree with the person on here that said the riaa is Downloading a file then changing it in a way that kazaa wont detect and continuing to share it as the same file.. THAT is why every song you download has the garbled noise come in at a different time(well thats how it is with me anyway) because its splitting the files up and getting good songs here bad songs there...
Some people replyed to the person that posted that and said that if you change the file Kazaa detects it and assumes its a different file.. Well I DOUBT that kazaa scans ALL the code of every file and even if it did... With all the fuckin Geniuses out there that the RIAA CAN AFFORD to pay..Im sure they can come up with a way around...

As for avoiding it? heheh download from the ones that show their kazaa usernames as the amount of people sharing(1 person) or you can put your Max sources to one and start downloading check what yer downloading and if it is somthing with numbers then cancel and try again till you get somthing with out numbers. As for the numbers...They are probably there because the RIAA have a Bot that does it all aotomatically and that is the way it is programmed to store them.

Well anyway thats my ShiTTy little input on this OVERLY sized Topic..

Have a BlasT GuyS,
TeLLeK

:blink:

Exactly.... because if you would have checked your idea you would have used Winmx or something like that. And as I did before to open my mouth I found out that here is the same problem.... Think before you talk.

podiboq

One way you can use to avoid the bad MP3's is to download off of certain people. When you find a copy of the song you want to download 'Expand" the list of users by clicking on the "+" sign. If none of the users has a 4 digit bandwidth allocation then you will probably get the full unadulterated song. You can also use the "Fixer" as talked about elsewhere in this thread to fix the bad MP3's.

This problem will not go away until Sharman or somebody else changes the way Kazaa and Kazaa-Lite check file hashes for like matches to the MP3 or whatever you are wanting to download.

:)

So has anyone used this KCF to try to fix corruption,
looks nice but dose it work... :blink: