hello martin
what's happening with the SC plays?
The play counter is showing the wrong count. for example when I give a track 1000 plays it's showing done in the processing tab but when I check it directly its only 200-300 plays actually added.
can you please check the issue and solve it
Thanks
Soundcloud plays Problem
-
martin@rootjazz
- Site Admin
- Posts: 34696
- Joined: Fri Jan 25, 2013 10:06 pm
- Location: The Funk
- Contact:
Re: Soundcloud plays Problem
Plays from working proxies / blacklist proxies will have the same requests. SC do not return a response saying "we are not counting this play". They return "success".
So the program can only assume plays that got a returned success response were successful.
The issue here is using low quality scraped public proxies. SC are more on teh ball with detecting proxies / finding known sources and blacklisting them. The same if the same proxies are tried to be used to play tracks concurrently (multiple users trying to use same limited proxies).
This is basically out of my hands. It is best if you can find . provide your own unused / abused proxies, otherwise this is just going to be an ongoing issues.
--------------------------------
Public Proxy Issues:
Plays increase slowness is due to soundcloud changes and the fact you are using the same public proxies as every other user.
Soundcloud now blocks many public proxies. They also limit the plays a proxxy can do in a time period.
So just as you can scrape free proxies, so can every other SCM user, so can soundcloud.
IF 100 people are trying to give plays at the same time. Soundcloud can see one IP trying to play 100 tracks. This is not realistic, so only one play will work, the others will fail.
The best way is to use private proxies. You are using the same free public proxies as everyone else, this causes problems. Ultimately, free proxies are free because they are not very good, you get what you pay for. So if you use free proxies, they will be slow and many will fail
Regarding proxies. There is general information on the forum
https://rootjazz.com/forum/viewtopic.ph ... oxies#p393
https://rootjazz.com/forum/viewtopic.ph ... oxies#p256
How can I improve public proxy effectiveness?
https://rootjazz.com/forum/viewtopic.php?f=11&t=1213
Why do plays / proxies not work, log out so many errors?
https://rootjazz.com/forum/viewtopic.php?f=11&t=1212
One way to improve them is to get a verified list
When you use a proxy to increase a track plays, if it succeeds it is logged to your LOGS folder with the name
XXXXX_proxy-success.txt
where XXXX is a timestamp i.e. 20130918_
So if you scrape 1000 proxies, then setup an action to increase any track by 500 plays, once the action has complete you can go to your logs folder via:
HELP > LOGS > VIEW FOLDER
then look for the XXXXX_proxy-success.txt and that file will list all working proxies used for the plays action.
You can see this in the video tutorial:
https://www.youtube.com/watch?v=RF19yD5wtKw
Regards,
Martin
So the program can only assume plays that got a returned success response were successful.
The issue here is using low quality scraped public proxies. SC are more on teh ball with detecting proxies / finding known sources and blacklisting them. The same if the same proxies are tried to be used to play tracks concurrently (multiple users trying to use same limited proxies).
This is basically out of my hands. It is best if you can find . provide your own unused / abused proxies, otherwise this is just going to be an ongoing issues.
--------------------------------
Public Proxy Issues:
Plays increase slowness is due to soundcloud changes and the fact you are using the same public proxies as every other user.
Soundcloud now blocks many public proxies. They also limit the plays a proxxy can do in a time period.
So just as you can scrape free proxies, so can every other SCM user, so can soundcloud.
IF 100 people are trying to give plays at the same time. Soundcloud can see one IP trying to play 100 tracks. This is not realistic, so only one play will work, the others will fail.
The best way is to use private proxies. You are using the same free public proxies as everyone else, this causes problems. Ultimately, free proxies are free because they are not very good, you get what you pay for. So if you use free proxies, they will be slow and many will fail
Regarding proxies. There is general information on the forum
https://rootjazz.com/forum/viewtopic.ph ... oxies#p393
https://rootjazz.com/forum/viewtopic.ph ... oxies#p256
How can I improve public proxy effectiveness?
https://rootjazz.com/forum/viewtopic.php?f=11&t=1213
Why do plays / proxies not work, log out so many errors?
https://rootjazz.com/forum/viewtopic.php?f=11&t=1212
One way to improve them is to get a verified list
When you use a proxy to increase a track plays, if it succeeds it is logged to your LOGS folder with the name
XXXXX_proxy-success.txt
where XXXX is a timestamp i.e. 20130918_
So if you scrape 1000 proxies, then setup an action to increase any track by 500 plays, once the action has complete you can go to your logs folder via:
HELP > LOGS > VIEW FOLDER
then look for the XXXXX_proxy-success.txt and that file will list all working proxies used for the plays action.
You can see this in the video tutorial:
https://www.youtube.com/watch?v=RF19yD5wtKw
Regards,
Martin