That would be correct AFAIKQuote:
Originally posted by Jamie L@3 October 2003 - 14:53
Couldn't find a definat solution to the problem. I'm guessing there isn't one?
BOT
Printable View
That would be correct AFAIKQuote:
Originally posted by Jamie L@3 October 2003 - 14:53
Couldn't find a definat solution to the problem. I'm guessing there isn't one?
BOT
I already said what the simpel solution was
2 things
screechign is casued by bad encoding I work with radio and almost got the sack once ofr f*ck up a commercial from it
another thing
it is possible that the RIAA have made thease bad encodes
heres what I think happens
RIAA worker makes a track called Evanscenes Falling its badly corruped of course
kazaa noob user sees it 2 months before release and doesn't realise its too early download it fast
then next person spreads spreads they dont bother to delete
another thing
ppl keep telling me PG is great blocks the RIAA
so when we all download screeching mp3s ??? how does it help if its supposingly the RIAA spreading them??
third post, woo hoo, go me
three things: first, i URGE everyone to ignore my posts, as they are usually written very early in the morning while under the impression of multiple mental and chemical imbalances. sleep deprivation being the most rampant.
second of all, thanks adster, for NOT maliciously attacking my ramblings and assorted coffee remarks. its appreciated.
lastly, i don't appreciate being called an idiot.
that being said, i'll move on
sharing music may not be illegal, but copyright infringment is, and they are nothing the same.
sounds good, but from the RIAA's standpoint it isn't true. thats the basis of their intire argument. they claim-i say "claim" b/c i don't have a copy of the friggin contract for copyright right here in front of me-that by "sharing" or downloading music that you haven't paid for, while others have, you are in violation of said laws. forthwith (lol, i just wanted to use that word), if you purchase any music, on any medium, you are bound to not reproduce that music in any fashion (views of RIAA and some CD labels, possibly all).
the thing that i wonder about is how do they think that 1/3 to 1/2 of these songs get out here? where i live, KISS 95.1 is the best station for popular music. all you need is a simple 3-10 dollar cable from radio schnack to connect the boombox to the computer, a decent software package, and good radio signal. convert the wav file to mp3 if thats how your's records, and there you go. as far as liscensing fee's go, the stations-or their corresponding company owners-make every bit of that money back on ads, and in many cases more so.
and with the advent of DISH and DTV's digital music channels, plus XM radio and other satellite radio broadcasters, its easier than ever to just rip the songs out of the air than to even bother with going to the store to get the CD.
i tried to read my first post, but i got confused, so i apologize to everyone who tried to read it as well.
and i agree with one of the earlier posts...if it is the RIAA doing this to the MP3s, isn't that just as illeagal as what we're doing? or would they just hire some tech lev. 5 to do this in his-or her- spare time?
and i'm still DL'ing, even while i type.
feel free to comment, just leave off on the name calling. not only is it disrespectful to ppl that you don't even know, but its disrespectful to ppl that you possibly DO know, and thats even worse. and what if i were some psycho-hacker? not that i am, but you just don't know anymore. my kid brother could be for all i know.
ps, anyone have a link to the winMX DL? i'm too lazy to go look for it :P
ps2, sux....lol :lol:
:oQuote:
Originally posted by cscwcu@5 October 2003 - 06:39
where i live, KISS 95.1 is the best station for popular music. all you need is a simple 3-10 dollar cable from radio schnack to connect the boombox to the computer, a decent software package, and good radio signal. convert the wav file to mp3 if thats how your's records, and there you go.
Sorry to Pooh-Pooh your concept, but i would never rip music off radio, because they all use limiting and compression on the output and a lot of time they sound bad.
The end result is inferior sounding songs which is just as bad as having corrupted ones IMHO :P
The Screetching is the RIAA. What they have done is very sneaky. Somehow they have found a way to spoof the hashing system. Here is what they do.
They do a search for a popular song say "remedy" By jason mantz
Using a legit copy of kazaa, they look at the search packets to find the hash that the legit file shows up as.
They have either a hacked copy of kazaa or more likely a program that edits the outgoing packets so that the hash that gets reported to the fast track network is the same as the hash for the valid file.
They send the screetching file as with the legiitmate hash.
The problem is they are sending it from a direct T3 connection with low latency. When you click on the file, you try to download from wherever it is avialable. Unfortunately, since RIAA has lots of bandwith, sooner or later you get some part of the file from them. THis is why the screetching is in different parts of the song every time you try to download. Solution try to download from an individual person.
A better solution would be a tool that would identify the ip addresses for each user that way when you get a suspicious user with 10 copies of a song, you could block that IP. THe RIAA people dont let you search user which makes it harder to identify that user individually.
i used to have the problem with the screeching sounds in the music files, but then i deleted them and i dowloaded another music file and well t isnt happening to me any more now :D
That Lumidee track is the first one that I had this problem with. Nearly drove me crazy trying to get a clean copy of it. In the end I limited the download to come from no more than three sources, and I got it OK.Quote:
Originally posted by Kain777@4 July 2003 - 11:32
i had exspecially problems with every version of this tracks:
Lumidee - Never leave you
and
Joe Budden - pump it up
ciao
BTW, if you get a corrupted copy, delete it straight away, otherwise you're just making the problem worse by sharing it with others.
@ NetworkMaster
Nice post, and I agree with You.
BOT
I can't stand fakes any longer!!! If you do find a working song, how about labeling the song by putting a *non-fake* tag before the song... This can be done by going to My Kazaa Lite K++ -> Right Click on file and then go to edit details then filling out the appropiate box. or simply renaming the song.
Then this will make sure that we don't waste time downloading screeching,looping etc.. dodgy files.
KAZZA LITE USED TO ROCK BUT NOW... :swear:
but then people will catch on and start labeling all songs like that so yeah try soulseek you might be suprised by how much you like itQuote:
Originally posted by mp3geek@6 October 2003 - 10:14
I can't stand fakes any longer!!! If you do find a working song, how about labeling the song by putting a *non-fake* tag before the song... This can be done by going to My Kazaa Lite K++ -> Right Click on file and then go to edit details then filling out the appropiate box. or simply renaming the song.
Then this will make sure that we don't waste time downloading screeching,looping etc.. dodgy files.
KAZZA LITE USED TO ROCK BUT NOW... :swear:
Just limit your downloads to come from only two or three people, and nine times out of ten you'll get a good download. Labelling won't work, like Kwahya says; the RIAA would catch on and label their corrupted files the same.Quote:
Originally posted by mp3geek@6 October 2003 - 16:14
I can't stand fakes any longer!!! If you do find a working song, how about labeling the song by putting a *non-fake* tag before the song... This can be done by going to My Kazaa Lite K++ -> Right Click on file and then go to edit details then filling out the appropiate box. or simply renaming the song.
Then this will make sure that we don't waste time downloading screeching,looping etc.. dodgy files.
KAZZA LITE USED TO ROCK BUT NOW... :swear:
Ok, from my experiences I'm quite sure this isn't the RIAA.
I've probably downloaded 25-30 screeching songs now, and yesterday I noticed a pattern. All of these songs had a significant amount of sources, but those which screeched had mixed sources. What I mean by this is that some of the sources were different songs but with the same track name. Or the same song with a different bitrate.
Try Nothingface - Ether (192). You get a massive amount of sources, over 150. But a small number of them are actually a song by Nas (160). I checked some of the other songs that people have complained about here and noticed the same thing.
I have no idea how to fix this, but I'm pretty sure it occurs when the search function adds different songs under the one sources simply because they have the same title. I can't explain why this has only happened recently, perhaps that has something to do with the RIAA. Anyway, just my observations...
Okay, so I tried download Clarity- John Mayer and those first ten seconds were sounding good and smooth jazz, then it goes boom and I can hear cats and Satan and my stupid modem. This was the second corrupt file I remember ever downloading, the other was Stupid Girl- Cold. And I thought it was no big deal and it was just something in my mp3 players or something, and thought that if i went here, I could get the solution.
And then I find that there's a post about 30+ pages long on my same problem; so this has to be RIAA. You have to admit, it's a pretty good idea.
Someone make a list of all the songs reported
Anyways, for the Clarity file that scared the piss out of me when that screech came on, has a 3906 bandwith and 40 users, and the file sizes are different. Don't know what else to report because I'm new and computer illiterate.
I've downloaded a lot of these "screeching" files, i hate them and the first one scared the hell out of me.
Anyway it always seems that when the bandwidth is 3906 it usually is a corrupted file. I don't know if this is a RIAA bandwidth or not but I'm going to try and download the songs that everyone is having problems with and see if it has anything to do with the 3906 bandwidth.
And the corrupted files almost always seem to have a million sources.
I came across a topic I felt I had to share in the hope that there would and could be a solution for....:
:angry: Those who understand will be bored by this - but it might help some others make sense of what's going on.
There have been a lot of references here to "fake files". It turns out though it's much more evil than just planting some fake files. RIAA's hackers are taking advantage of a serious flaw in Kazaa's Hashing system to plant files which as far as the KAZAA search algorithms are concerned are identical to the real files. In reality parts of these files have been replaced with the 'orrible noise people are compaining about.
Because the bad files look the same to Kazaa as the good ones, and because when you download you usually download pieces of the file from multiple sources it's totally possible to get a corrupted piece with that 'orrible noise from one user that effectively ruins your whole download, and also creates yet another corrupted version of the file.
The defect in the Kazza protocols is that the identification of a song for the purposes of search is based on a "hash" : this is a large number computed by say adding all of the bytes of data in the song together and taking the last N digits or bits (in reality a fancier algorithm would be used). Kazza F!@#$ed up big time because they designed their hash algorithm to only include certain chunks of the file rather then every single byte and which chunks are included (and not) is very well known. So RIAA can fool the hash algorithm by trashing the bytes of the file which aren't included in the hash calculation. The trashed file will then have the same hash as the good file and will be downloaded as part of it.
What is really "nice" here is that this spreads corrupted sections of the file into new downloads due to Kazaa's multi-source feature - it spreads almost like a virus. Narsti!
The one thing that everyone can do now is to DELETE CORRUPTED FILES IMMEDIATELY!!!!
Beyond that, if KLite could download files into a non-shared directory then people could listen to the files to make sure they're OK before sharing them. KLite could implement features to support verifying files and moving them to shared.
In the end it may be necessary for Kazaa to fix their hash algorithm in which case software will probably need to be upgraded. Whether in the present legal climate they will feel safe fixing their bug is open to question.
And by the way, the defect that RIAA exploits is not inherently limited to any one bandwidth - if they aren't planting 192 bit rate files today, it's only because they ain't gotten around to it - they could.
podiboq
Yes, I hope all noobs read this.
:blink:
No I didn't. But it's not what I mean. This is a solution after downlaod. Let's get the root of evil. Try to filter before download.
No?
Deep Purple--Smoke on the Water
There are a bunch of different users who have it, but every single one, at some point in the song, break out into a noise that sounds like a microphone pointed at a speaker while a hundred babies scream into it and a 40-inch speaker plays white noise at full blast. I hate it. AND I CAN'T GET THE BLOODY SONG OUT OF MY HEAD. DAH-DAH-DAH--DAH-DAH-DA-DA--DAH-DAH-DAH-DA-DA. AHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
:o
the RIAA can't legally do this, can they? Even if we are stealing their blahdfkjslakfjds...?
Yep, podibug has hit the nail on the head here.
I hope the developers read this so they can try to fix the problem.
:shifty:
I have a solution to the problem::
go here and look at the post buy brownguy02:
http://forum.win-drivers.co.uk/index.php?s...opic=3144&st=0&
download the attached program installer and run it. it will place a program called "noel's mp3 scanner" on your desktop. simply place this program inside your music directory and run it to scan your downloaded files. it will automatically find corrupted songs with the screeching noise and place them in a quarentined folder inside of your music folder. just do this before you burn a cd and then you wont end up with the crap on it and you'll know which songs you need to redownload. also.. delete the songs once they go into the quarentined folder. if we continue to allow corrupted music to be shared on the kazaa network, things will only get worse. please distribute this installer as widely as possible. the more people we can get to rid their music libraries of corrupted riaa songs, the less problems all of us will have downloading.
again, the link is here:
http://forum.win-drivers.co.uk/index.php?s...opic=3144&st=0&
look at the post by brownguy02.
please post this installer on other forms or host it and provide a better link to the program. thank you.
:-)
It's not really a solution though. Unless everyone adopts it the screeching songs will remain.Quote:
Originally posted by brownguy022@8 October 2003 - 08:06
I have a solution to the problem::
ok......
I apologize for my first post being huge
My findings on the situation-
I don't think this has to do with new cds- I was trying to download jimi hendrix songs and it was screwing up...
I don't think it has to do with the file being screwy on person no 1s computer- That would not have caused the file transfer to speed up drastically.... I mean to 5x the normal speed (I use dialup and downloads seldom exceed 2kps- theese files were goin at 10kps, typically in the middle of the download. it's slow as usual in the begining of the song, then in the middle it speeds up like nuts, then at the end of the song it slows down again... maybe the horrible grating sound I hear in the middle of the song is somehow proportional to the size of the song...look for a pattern guys)
I do believe the money making part of the industry has something to do with it- the only problems that ever ocurred for me showed up as I was trying to download a file that was owned by a massive amount of people... and big organizations do their best work when the masses are involved...I stick to excellent file rating files that only one user has, no problem...
I would also like to point out that it is more than likely a LACKEY from the RIAA, probably SERVERAL of them, reading this forum and getting a huge kick out of how defenseless we are, and everytime we post about some pattern we saw, they deal with it... remember, they have a huge amount of money.
I think it has to do with the servers they are uploading them from... I think SOMEHOW they have found a way to force the download to come in at a crazy rate, scrambling it to shit. I also thin a lot of the people have stopped using kazaa already because of this, and most of what is left are the mindless song downloading drones with broadband and RIAA lackeys, neither of which are going to "weed out" the bullshit.
MY solution would be this... make a new client, and whenever the pattern I mentioned before in a transfer comes up, cut the supliers account, end it once and for all right there. Give people that aren't doing it willingly a warning and a few weeks to fix it, the bam, hit everybody screwing with the system hard.
I see this as the most final way of doing it....or something similar to this (if you find a better way to catch whoever is fucking with these song download)
if you find they are NOT the ones suplying the download but are intercepting the downloads somehow, they must be hacking into the server... which is illegeal (not to mention uncharacteristic, but then again they have started using our tactics against us) and Kazaa could fight back with a lawsuit of its own...show them we can play their game... keep in mind they have a lot of money....
there is a solution to every problem, and the best place to start with this one is to find patterns... that's the way computers are.
that even a more huge post :lol: :lol:
:blink:
Guys guys.... listen. Let's not get carried away, ok? Fact is that the mp3's are getting fucked, deliberately! We should try getting the corrupted songs out before to download them. I'm sorry but I know for sure a lot of people are unaware of the urgency of this. So... try to check everything before you share. In the meantime the guys from KazaaLite++ will surely come up with a solution. What reminds me, these guys do this for fun.... DONATE..
;-)
podiboq
:(
Well I have the same problem. And it doesn't matter if it's a new song or and oldie. One thing I know is that it's caused by only one comapny (man). When you open the mp3 file in a wordpad or something like this you'll see that there is a pattern - the same in every mp3. I've tried to download many mp3 - till now - with no succes. I hope the same thing won't happend to the movies.
I think it's not a big problem to write a programm which would "catch" the bad files, but it will only work if this programmm would be a part of Kazaa. If there won't be any patch soon then Kazaa will be one big chaos.
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.
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.Quote:
Originally posted by rappersk@9 October 2003 - 01:46
something that seems right on the surface
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*
ok.. man your problem that is REALLY going on is all in your HeD...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...
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: