ZigZagJoe

Any logs would be good. (both PS and Sproxy). Get the one from PS's savedir if you can, as it has non-abbreviated URLs and timestamps which would be useful. If there is no PS log, go into PS settings, advanced tab, and click "start logging". the buggon will say stop logging if it is logging (or has just started logging).

Can you get the SProxy log from the same time? and the non-abbreviated PS log? it looks like it was requesting non-sniffed songs, so i want to try to match up the various URLs and see if there were extras.

Click on the fader picture. It will come up with a title bar you can use to drag it around then. The settings for the fader are under "Extras" (ripped = saved) The failure screen there is probably the tuner warning thing again. Can be safely ignored. Hmm, odd. Does it give any indication that it sniffed the song which is now playing? If it said nothing all it sounds like it didn't catch the URL, which makes little sense.

I should note that iPods, evidently, do not support AACplus (the encoding that Pandora and thus pandorasaver uses) much like iTunes does not. On top of that, iTunes is bloody minded about the whole thing and refuses to put music on it that does not have .m4a extension (suppose there is no reason to not change it, however.) So, the end result is yes, an iPod will play AAC files, but it can't play AACplus files properly as apple does not support SBR (end result - they are missing all highs. I would not call that playing well.)

Sounds good. (it writes the png files because the external tool expects a png file to embed, if available) First and second one are caused by a small error in which when pandora has some sort of problem & sends a tuner warning, whose URL contains the tags it uses to decide what to do. It ends up trying to parse a HTML document like it was XML, hence the problem. Last one is some silliness in the listview control. Yeah, i really ought to completely rework how files are handled and move to having the thread dispatch a new class for processing a song, instead of handling them one-by-one. That way, it could spawn as many threads as cores are available for encoding. To change the length of the song would be near impossible without bundling a bunch of files [different length aacs to be sent], and even then there would be hard to predict how long it would take. I might write a simple tool depending on interest that encodes all the mp4/aac/m4a files it finds in a directory to mp3, and convert en masse (it would be trivial with code that already exists in PS - it has code to read/write ID3s and of course the conversion stuff is handled by faad/lame) Possibly in a few days I'll release a new version with some small fixes and more changes in the innards of SProxy (learning more than i ever wanted about HTTP protocol. Also, non compliant servers be damned)

I see. I blame vista tbh :P

Yes, it is. (it has been discussed earlier in the thread). If turbo mode was enabled while it was converting the aac pandora sends to mp3, eventually bad things would happen (overflows and such). Simply put it's getting a new song every 5 or so seconds but encoding takes over 30 seconds. Also, brofix, the link didn't work (forums rejected it). Are you using the older version because you had trouble with the new one? (i released 1.008 a few days ago). Just curious

Do you mean the tag name or how the files are organized? If you want to put them in a seperate folder you could change the save folder (obviously), or change the organization structure to something like Pandora - %artist%\%album%\ If you mean the tags, that would be not necessarily hard to do but I'm not quite sure where that would go on the config layout. At the moment, pandora saved tracks are tagged with a comment of "Ripped by PandoraSaver [Z]"

Unknown. I might try building it with mono sometime.

Known bug. Related to minimize to tray. (fixed in latest version)

In IE, tools -> internet options -> connections -> LAN Settings -> Uncheck use a proxy server (while SProxy is NOT running). Then hit okay, and okay again. Do get me a log if you get a sec, so i can see what the errors were.

what uses a lot of cpu - sproxy? around 20% would be normal for turbo ripping. the browser using a lot of cpu is not abnormal, however, considering it is almost constantly downloading new tracks and trying to play them. I've also noticed that the flash player tends to leak memory over time. Also, check for message boxes- important errors are typically shown in them - i.e something has gone gravely wrong and probably can't continue normally, or it is something the user needs to know. I find windows likes to hide them from me, making a sound, but they are below all the other windows. I usually have them put a message in the respective log before showing the message box, however, so if everything has stopped and you can't see anything try the log. Nah, see, I *wanted* an exit note that was not US so i could try if it would allow me to download tracks from a non-us IP address. It's alright.

mmm, bugger. I guess that means they do indeed filter by IP at the audio download servers now. And they just kill the connection if it isn't. Atleast the exemption is working properly otherwise. (The E prefix is for exempt: those URLs are not going through the configured proxy). Then again, i am not sure, as some of my friends who are not in the US tried a pandora URL and it worked fine. Odd. Can't get tor to get me a non-us exitnode (the one time i wish i wasn't in the US...)

hmm, indeed, i have replicated this on windows 7. by replicated, i mean it happens and i haven't the faintest what would be causing it. Atleast i can try to figure it out. It seems to be related to the listview. Right when it is about to scroll, freeze. Might be related to the forced double-buffering. Yup, sure enough, without it works. I've updated the current link with one that had double buffering disabled. I guess a flickery display is better than one that does not work at all.

Does the proxy-exception for data stuff (under advanced settings) work? It makes it download audio, the flash applet, and anything non pandora directly, not through proxy, which should obsolete low-bandwidth mode. I wasn't able to properly test it as i'm living in the US, and it would not fail me (with the you are not in US etc) stuff if it hadn't worked. the option is named "only send pandora control urls through SProxy configured proxy". A bit of a mouthful. Try checking it for me when you get a moment. You'll want to reload pandora as well, for the best test.

You can try taking the PandoraSaver.DLL from the last version and overwriting the new version's with it. It *should* work, but more importantly it will tell me what the problem might be (if that one loads successfully). What are the last lines in sproxy's log? (SPLog.txt)

you can download the old version if add -old before .zip (SPPS1.000d1.007a-old.zip or what not). What was the last line in sproxy's log? Hmmmmmm. tried the pandora gadget (i just noticed it.) It appears to send playlist data via an encrypted SSL tunnel...actually, any data of interest goes via SSL. If the main tuner implements this, it would be game over for ripping music from pandora, atleast in the short term. I know Fiddler has some way to go about doing man in the middle attacks to allow SSL data decryption, but it requires you to mess with the certificates and is a general PITA. Oops, figured it out. I had moved a block of code to the wrong spot, and so pandora was expecting long data but only getting the short file (the headers that should have been changed were already sent). Disabling turbo mode should do fix it atm, I'll upload a fixed version after i am done sorting some changes i've made. Okay, try http:// zzj.itf-inc.com/SPPS1.002b1.008a.zip (OUTDATED) Changelog, etc: Improved request recipt Improved POST handling Fix for sending headers prior to allowing tampering: this was breaking turbo mode Other bugfixes which I've forgotten. Killed the dreadful flicker in the list of requests when many are being handled at once

Try deleting SProxy.conf - i moved options around and renamed a few (I think?) and that could be causing a snafu somewhere (though, it shouldn't...) Did sproxy literally freeze as in have the os call it non-responsive? I don't have vista (and don't particularly want it for that matter), so no gadget anytime soon :P

Try enabling low bandwidth mode. Also, ensure that those files ripped are the correct length and not too short. I find that it will start doing that when pandora times out or otherwise fails to load in a timely manner. It's a bit odd. For the hell of it, I ran the siege benchmark on both fiddler and sproxy. The objective was to load google as many times as it could within 1 minute. Sproxy turned in at 1/3 the memory use of fiddler, 16mb to fiddlers 54mb; (fiddler keeps responses in RAM until they are disposed of, as a result it leaks memory like a sieve. though, that only accounts for 200*6kb worth) Sproxy used about half the CPU use of fiddler, which was 100% for one core (on fiddler). Sproxy got 2765 hits to fiddler's 2346. (meanwhile, a direct connection turned in 3681 requests) All were using 25 simultaneous connections, with no keep-alive. Neither proxy failed a request. Conclusion is that Sproxy does indeed introduce some connection latency when using many connections, when used "normally" there is little visible difference between an uninhibited connection. Also, the actual download speed is not affected at all. (SProxy will note the download speed for files that take >1 second to load.)

If a song is played on a station, it gets added to that station's playlist file (doesn't matter if it is in other playlists already for other stations). Songs are appended to the end of the file. (It creates a new playlist file for each station)

Playlists only contain one entry for a certain song. Got song means it added it to the queue; the worker thread will take care of any pending ones every 5 sec or so.

Hmm, well, i can't find anything else to test (abuse) on it so it's release time. Now up to version 1.002a for SProxy and 1.008a for PandoraSaver. Changes of note: PS: New - Song-fader window: displays songs when sniffed or ripped. Auto-launch command on start (url or browser, etc) Exemptions for data urls (bypass Tor for audio when using it for location-fooling) Improved strict duplicate checking. It is now the default. (checks for songformat.* , ie files with the same name with any extension) Hidden config options such as thumbs up downloading have been exposed in the config form. Bugfixes - Blacklist now functions correctly with turbo mode. Album art with flat directory structure Station tag not functioning properly Fix for overly-long file names not matching properly. Auto-reload now enabled for mini player Memory use improved Others which i can't recall SP: New - New & Improved connection core. (Pre-req to keep-alive implementation) Greatly improved memory use. Support for url exemptions (not exposed to user atm) Files larger than 8mb will be sent directly, so SProxy isn't allocating (sizeofresponse * 3) at times. Some bugfixes. Binaries: http://zzj.itf-inc.com/SPPS1.002a1.008a.zip Firefox Portable: http://zzj.itf-inc.com/Firefox-P-SProxy.zip Extract the firefox portable zip into where SProxy.exe is located. Overwrite SProxy.conf if you want it to automatically launch when you start SProxy. If you do not want to overwrite your config, add "FireFox-P/LaunchFirefoxPortable.exe" as the autorun command, under PS advanced options. PS is at 4143 lines and SProxy 3082 (not really a simple proxy anymore is it?) (Add new posts instead of editing - i just noticed this) No. Already went over this. If IE settings are not written, then flash will not use SProxy and PandoraSaver can't rip music. Hence why i have put much work into making everything work properly - so apps can go through this and encounter no problems. Although I haven't done any serious benchmarking; in comparison to sending all traffic through fiddler, SProxy is much faster under the torture test (close firefox with 50 or so tabs open: a normal load for me, and then reopen it which means it loads a shit ton at once). Rather, I didn't notice any difference between direct and through this. Also, if this crashes, it writes the settings back (though, in prior versions probably not - this one has a global exception handler which will.)

Yeah. I've already exposed that option in the newest one - just need to finish some testing. Hmm. Something is messed up; that's about all i can tell from that. I'd recommend trying the firefox portable I'm going to release with the new version (after I finish some testing, to swat some odd bugs). The overnight stress test went good, memory use is still 16mb, with 22.5k requests handled, 25026297075 (23.3GB) bytes downloaded, and 9 hours 30 minutes running. PS ripped 194 of 11743 songs sniffed (turbo mode).

Some sleep, yes :P Got it. What's happening is that it is finding the already existing album art, thus not re-writing it and so it uses the old one, which is for the song you just ripped as ripped files are not being segregated. I'll make it name album arts for their specific album from now on.

What do you see in the logs for both SP and PandoraSaver? You might attach a screen of SProxy's window while you load pandora, and this problem occurs. And, what is your connection like? (but, i'm assuming that is not a problem otherwise you would have mentioned it earlier...) Odd. You could try low-bandwith mode and see if that makes any difference at all. Also, minimize to tray seems to be having .NET failures from time to time - 25% or so chance of something going belly up and making it hairball. Is odd. Think i found it, however.