ZigZagJoe

I'm not sure i understand what you are asking- the AAC files from pandora are not re-encoded and are already in HE-AAC format. Or, do you mean provide the facility to use another encoder other than LAME? Currently, LAME's options are customizable under Advanced settings if you wish to use VBR etc to encode. Also, why would you want to specify the decoder? Faad seems to work fine? :S ATTN readers: Please make any follow ups in this thread. The version of PandoraSaver being used in this is outdated. Thanks.

Yes, Sproxy obsoletes fiddler/privoxy as a host for PS. I'll increase the timeout limit (that is one of the things I was worried about). By the way, is it a proxy timeout or a server communication timeout? it should be noted somewhere, the log probably. (i'll allow for both anyways) As for no music played, you might try firefox, and see if that works. Playing no music while displaying "It's taking longer..." while happily ripping away seems to be an IE-specific problem. I haven't the faintest what would cause that problem, though. If you can, PM me the results of http://127.0.0.1:8888/config on the newest beta version. It would be possible to put the PAC file somewhere and or modify the contents as it goes, but not the browser setup for it (nicely anyways). The method for programmaticly changing firefox's settings goes along the lines of killing firefox, molesting a file in the user's profile, and then re launching it. Rather nasty, if you ask me. Random statistics- I found a tool called cloc to count number of source lines; SProxy (the host program wrote from scratch) ends up at 2418 lines of code (excluding blank lines and comments) and PandoraSaver comes in at 2985 lines. (PS 1002 comes in at 1114) More than I expected. SProxy has been built 600+ times now (successfully); PS, I didn't use the automatic version incrementer on it. Certainly, C# has more "power" per line than I had expected. The beta version, located at http:// zzj.itf-inc.com/SP1.0bPS1.006BETA.zip(OUTDATED) has been updated to the most recent version. I haven't fixed the HTTP proxy-chaining not functioning proper, yet, but lots of other stuff has been fixed. (Do people even use HTTP proxies for this sort of thing?? Those public ones are godawful slow...) Of note is the miniature website it now hosts when you hit http://127.0.0.1:8888/ ; it shows the current status such as bytes transferred, number requests handled, uptime; also, the status of pandorasaver including known stations and songs. It also provides a page that shows _all_ configuration options, including that of PS ( http://127.0.0.1:8888/config ), EXCEPT any fields with "pass" in the name. Finally, it allows you to see the last 100 log lines ( http://127.0.0.1:8888/log ) Perhaps I can get a flash applet made to hit a server much like pandora would do; to test the config. OFC, you could just run pandora itself.

hmm, yeah, that does look like privoxy is not being used. you did run the install script in the privoxy zip, right? (Setup.RUNONCE.vbs) it sets fiddler to chain properly with privoxy (if everything is working properly you will see requests in privoxy's main window). Specifically, what it does is write two fiddler registry settings to ensure fiddler chains, and then writes the info (into IE settings) so fiddler catches it. Just found out what is wrong for those who get audio URLs but no XML data: IE is setup to use the proxy, (which flash takes from) and is thus making requests properly through the proxy, but the browser pandora is in is NOT set up properly and is not making requests through the proxy. You can try the beta at zzj.itf-inc.com/SP1.0bPS1.006BETA.zip (OUTDATED) . extract it somewhere, and run SProxy.exe. Simplish setup instructions for Tor+beta SP: Known problems in beta: HTTP Proxy-chaining is not currently functioning This essentially combines the function of fiddler and privoxy into one: it deals with any proxy chaining (tor) and allows PS to intercept data. Just run SProxy.exe, and setup your browser as if you were to use fiddler (by default, i have this listen on the same port) I should note the standalone seems to be significantly faster than fiddler when set to do all requests, probably due to how it handles the requests. if everything is working correctly on the standalone you should see a status report at http://127.0.0.1:8888/

Yeah, copy the log (and also check if there are any requests being made through fiddler - take a screenshot if you can) I assume you have opera setup to use fiddler already - are you using browserPAC or all traffic?

Might have to restart - if you uncheck the download button, it will have unchecked the only download positively rated songs checkbox unless you had don't automatically download any songs checked, thus it would've went and saved them all (possibly)

The song viewer, on the PandoraSaver menu on fiddler is how you approve songs (you can also access the menu on the pandora tray icon, if you have it enabled under settings. It shows a list of all the pending songs. Select one and hit the download button. Also, you should not use turbo download with mp3 conversion enabled, as it takes 30secs to a minute to convert a song. I'd recommend you use the song viewer while using turbo ripping; the download button may skip a song depending on the connection load. Here is a visual of all that:

Thanks! Those temp files are the music from pandora - they are kept as *tmp files while the songs are pending approval. If approved, they are moved (and renamed) appropriately. How are you approving the songs for download? the three triggers right now are either 1. positive feedback in pandora, 2. selected song on the song viewer and pressed download button, or three used the download button which can be integrated into pandora's page. If the download request is successful, you should see the song disappear from the song viewer, and it will note it in the log (something like title by artist to be downloaded) if you used the button. If you use the song viewer to approve a song, it will disappear from the viewer and you should see it log it as having taken action on the song in about 5 seconds. If it catches feedback, it will say something like "Song title by artist has been positively rated". The temp files *NOT* approved for download will stay until it hits the limit for queued songs (adjustable from 10 to 250 under advanced settings). They will also be deleted upon exit. Post a copy of the log when you approve a song and it doesn't download, if you get a sec. (The log viewer is accessible under log viewer on the tray icon or pandorasaver menu. double click where the text is to copy it all)

Try setting firefox to use fiddler for _everything_, that is, use 127.0.0.1 8888 as the proxy under settings and select use this proxy for all protocols. That will tell me if it is a problem with pandorasaver or something else. I think this might be a bug i found earlier, but this will tell me for sure. I'm going to box up the "beta" version of the standalone in a bit for testing if people want to. It works fine locally, except for HTTP proxy chaining; Tor and such are known to work. Some outside testing would be very handy for that.

It looks like pandorasaver did not sniff any XML song data. Try reloading pandora - you should see something similar to this when it started (and sniffed data) PandoraSaver started Inspecting XML doc: http://www.pandora.com/radio/xmlrpc/v21?rid=3752257P&method=sync Inspecting XML doc: http://www.pandora.com/radio/xmlrpc/v21?rid=3752257P&lid=55181377&method=getStations Sniffed station query Got station name 'Techno/Trance/Dance/Etc' (38518692694851649) Got station name 'Rawk and such.' (13776992420364353) Inspecting XML doc: http://www.pandora.com/radio/x...3=47507329&arg4=&arg5=&arg6=aacplus Sniffed playlist answer Got audio url: http://audio-sjl-a-1.pandora.com/access/...WKqsHL9Ep5SPGco%2BRkiixEYXkd9cPcESJ Got audio url: http://audio-sjl-t1-1.pandora.com/access/...hMnxN%2Fj%2Blz0XM7X5Tl10l0E2Xg%2FZy Got audio url: http://audio-sjl-a-1.pandora.com/access/...3xGETo4I7l3PoqiJTxqe%2B2UKn30T%2FPA Got audio url: http://audio-sjl-a-2.pandora.com/access/...CqTDnFi%2BsuVLcbWZKHWz%2B63s1UqHpqY Inspecting URL: http://audio-sjl-a-1.pandora.com/access/...3mmV%2BRmU3kh6Pli3Yg6Eg4ky9pfuvA%3D Matched audio URL: http://audio-sjl-a-1.pandora.com/access/...3mmV%2BRmU3kh6Pli3Yg6Eg4ky9pfuvA%3D The audio URLs ofc will be different, as will the station names. Are you using the browserPAC method to use fiddler, or ....?

PandoraSaver is now well obsolete. Take a look at Saver2, which features an improved turbo mode among other features such as a stand alone pandora client (no browser, no configuration!) plus support for other services and a new web interface. Saver2 thread: http://hak5.org/forums/index.php?showtopic=13598 Saver2 Site: http://zzj.itf-inc.com/s2/ This is no longer supported, and the source has been made available.

Check pandorasaver's log (it is a menu option on fiddler, and on the tray icon if you have that enabled. see http://i141.photobucket.com/albums/r49/zig.../PS_help_v1.gif ). I've heard of it ripping songs while pandora has not been playing in IE. This works independently of browser, the only requirement is flash 9; so I'm not sure if updating it would cause a problem. I don't know how this download is set up, except that it has fiddler and firefox in the same box; I'd recommend setting up your regular browser to use it and have done. See this thread. If there is errors in that log, double click in that window to copy everything to clipboard (the background of the window will change for a second reflecting this) and paste it in the thread I linked. As for legality, it really is a gray area. This is simply "recording" (in a sense) what Pandora sends you - it is not actively seeking out the songs. I recently fixed the only method to detect this (which was if something was watching album arts for duplicate requests), so it is effectively undetectable. Hmm, I think i better make a new thread for all this as the one is getting quite cluttered...

Probably a bug that was fixed a while ago (this is a bit out of date, iirc). Download the latest (plugin only) at http://zzj.itf-inc.com/PandoraSaver1005-ZZJ.zip and put the contents of /bin (pandorasaver.dll, faad.exe, and some other files) into fiddler's scripts dir. I'm not sure where this installs fiddler, so do a search for "PandoraSaver.dll".

nah, unrelated to port settings. the port settings getting changed is how this chains with fiddler - it writes to use privoxy, and then when fiddler launches, it reads those settings, "copies them" and then changes IE's settings to use fiddler first instead. fiddler will then use privoxy for any requests. It's a bit convoluted, but it does work. You might try firefox and see if that plays while ripping. (just set it to either use the browserPAC or 127.0.0.1:8888) I suppose i could make the station-in-composer field togglable, the comment would be a bit harder however (there isn't room in the config screen for it). Could make it a setting in the registry, i suppose. Somehow the proxy-host has started working perfectly overnight. I didn't touch anything, i swear! It scares me. Everyone: Please make any posts in http://hak5.org/forums/index.php?showtopic=12047 as this thread has gotten a bit too long Also, the standalone version has been released! (no fiddler or privoxy required anymore) See thread.

No problem. By the way, what browser are you using? I think someone else has reported this problem before (ripping, but not playing) with IE. As for launch sequence, I would first launch Tor, then Privoxy, then Fiddler, and finally the browser. Just playing it safe (it really shouldn't make much of a difference what order they are launched in, just that everything has been launched when you try to look at a page). I'm guessing the error is related to one of the proxies along the line loosing the rest of the request, thus ending up with a partial XML file. It's not a crippling error, just means that it will be unable to read the next 4 songs (probably). Might change the dialog box into a log message... Standalone Update: Still chuggin away. The tunnel stuff is being a right pain in the ass. (Pandora uses SSL to download the flash applet and authenticate, thus I must support tunneling for it.) Misc: It's an option to have this look up on Gracenote, I registered for that a long time ago and finally noticed that they sent me a message. If it allows a way to get large CD images, i'll probably implement it. Haven't had time to look at what exactly their API provides yet (besides the obvious song info). Though, i am not exactly clear what the non-commercial license entails - I'll have to make sure everything is fine with redistributing it and such.

In the interim, I have set up a privoxy for those who use Tor. Download http://zzj.itf-inc.com/Privoxy.PS.zip , extract it somewhere, and then run "Setup.RUNONCE.vbs" (which is in the zip). it will shutdown fiddler if it is running, set IE settings to use privoxy, set fiddler to chain with privoxy, and finally launch privoxy and fiddler. Afterwards, you can use "Run.PandoraSaver.vbs" to run privoxy and fiddler2, or "Uninstall.vbs" to reset IE's proxy settings. This script assumes that you have fiddler installed to C:/Program Files/Fiddler, if not, it will prompt you to manually run it. Use the browserPAC I mentioned before in your browser: What this package essentially does is use privoxy as a "translator" to allow fiddler to access SOCKS proxies (which is what Tor uses). Assumes Tor is using port 9050, if not, modify the line "forward-socks4a / 127.0.0.1:9050 ." in config.txt to reflect which port it uses. so, the end result is: Ye Olde Interwebz <=> TOR <=> Privoxy <=> Fiddler <= [PandoraSaver] => Your Browser, running Pandora I also uploaded a fixed version of PS with the filesize-reporting-error corrected. it doesn't effect anything, so you do not need to download it if you already have it already. link is same as always, http://zzj.itf-inc.com/PandoraSaver1005-ZZJ.zip

"got audio url: http://...." means it sniffed a playlist response which contained those URLs (and associated artist etc data with them), so when pandora requests a song with that url it knows what that song's info is. i have it echo them for log purposes so I can try to guess what went wrong if something errors. the keynotfound exception is the one i mentioned above - a small error in the code which reports if a file request is too short. you may safely ignore it. the double \ is because it always adds a trailing slash. it's legal by windows standards and should cause no problems. mp4tags only tags when a file is downloaded, as downloaded files have *no* tags at all. it will not tag again(overwrite) unless you have the option "always update file tags" set in advanced settings checked. unless you have "strict dup checking" in advanced settings checked, it effectively ignores song extensions. if you find it is ripping the same files already present lower the dup tolerance under advanced settings to 90. (from default of 100) so, if you have a song named artist - song.m4a it will see that and not re-download the song. (see the visual description at http://i141.photobucket.com/albums/r49/zig.../PS_help_v1.gif ) also, what do you mean by static data? (like what fields). i've contemplated having it look up songs on gracenote to better fill in fields, but ultimately decided it was not necessary.

the error in the page was probably caused by it hacking out some of the ads, probably. shouldn't cause it to save dat files, however.

i would try it; except, it is not free. So can't do much.

no problem! yes, they will all be 44kb in size. that is how turbo mode works - yoink the good mp4 that was downloaded, save it, then replace the data that the browser (and pandora) gets with a blank mp4 file that is only 5 seconds long. thus, it plays a song every 5 seconds. the caching stuff is just fiddler playing it safe. also, HUZZAH! that log finally told me what I wanted to know about an error that popped up from time to time. i've been trying to hunt it down forever; turns out that was part of the code which checked to make sure that data length was valid. but, it had a stupid mistake in the line that would report if something was wrong *doh*. It's nothing harmful, however. I found Pandora's servers from time to time hiccup (it could be caused by fiddler, i don't know) and give an error page, hence the need for code to catch it so we don't save 1kb files. i feel kinda stupid the bug was really harmless this entire time, though. seeing as it is playing fine now, i'm guessing your net framework had a problem reading the resource stream. I'll have to check and make sure that it is not a .net 3 specific thing, as that would be bad for general use (I don't think 3.0 is widely deployed yet)

Doesn't appear the file replace worked...was fiddler running when you tried? the "new" one will say "infos:" as opposed to details, and will have info on a few more lines. I checked the one uploaded, and it's the new one, so I'm guessing that something failed somewhere on your end. try re-downloading it. MD5sum of PandoraSaver.dll is "dd218c26cdbe0e383ab0213a251f34a8". you can get an app to test md5sum at http://zzj.itf-inc.com/md5sums.exe - drag the pandorasaver dll onto its exe and it will pop up a window with the computed md5sum. it should match if it is the correct version

You forgot to update pandorasaver (http://zzj.itf-inc.com/PandoraSaver1005-ZZJ.zip) with the new version i uploaded, which had some more debugging info which would be helpful to me. Download that and try turbo mode then. Glad you got your browser sorted. I think this is worth the time, simply because I learn stuff from it :D (truth be told, this is my first "major" C# project - usually used C++ and the like before)

Hmm. Uploaded a version with some more debugging info. If it gives the same error, try taking the "blank.mp4" that is in the src folder in the zip and stick it in fiddler's scripts dir, where faad lame etc are. If that fixes it, i'm guessing you may have an older version of the .net framework that (evidently) can't load embedded resources properly. I've changed the auto refresh code a little. Try checking now if the refresh tag is in the source. Also, 3600 will be 1800 if you have it set to 30minutes, or 7200 for 2 hours, etc (It's the number of seconds it waits to refresh) on a quick google, ocard:LoadSystemInfo() seems to be related to a paypal plugin..? not positive however. It is IE-specific evidently. As for the standalone proxy, i've got SOCKSv4 working fine, and SOCKSv5 mostly done (grrr non-compliant servers). stacking with HTTP proxies also works, though authentication is not implemented yet. still need to redo the streaming-communication for it to work well, however. When it is done, I am not responsible from any cases of interface poisoning that may result from viewing the gui. (this is a joke) Also, fixed a bug in that generated playlist files were started with a \ , thus rendering them unplayable in media players

Ah. I see. I'll upload it onto my site, then. http://zzj.itf-inc.com/BrowserPAC.js Hmm, yeah, according to that PAC file (one you linked), it uses a SOCKS proxy. So fiddler can't do anything. It appears if you download a proxy software called Privoxy can provide a regular HTTP proxy via Tor. If you set that up as the Http proxy and then launch fiddler it should work. (man that is a horrid way to do it, with 3 different pieces of software involved) I wonder if it is a similar case with that hotspotshield.

Yeah, I got your donation - Thanks! I'm not sure how to make IE use browserpac system; it seems to be non compliant and would route all traffic through fiddler even though just *pandora.com is supposed to be. EDIT try using http://zzj.itf-inc.com/BrowserPAC.js as the auto-config url. Firefox does respect it, however. Have not tested opera or chrome with PAC yet, but i'm thinking they will probably mind it properly as well. In testing the proxy I've just come to realize how much slowdown fiddler imposes - somewhere around 2x per 3x per connection. (so, on a page with a lot of items, it tends to bog down heavily) When you turned on turbo mode, in the view songs window - did it say something about "Full auto download enabled" in it, on a black background? If it does, run it for a bit (16 songs or so) on turbo mode and paste the log here (double click in the log window) For auto-refresh problems - check view-source in IE. near the top of the html there should be a line similar to "<meta http-equiv="refresh" content="3600">". if it is missing I'm guessing that IE must be butchering the line endings so that it does not match properly (it does a search and replace to insert the various bits into the webpage). It would be simple to fix. As for progress on the standalone version - getting there. SOCKS support remains to be implemented (rather simplish) but streaming-communication needs to be sorted still. Regular GETs (in which it downloads everything, allows for the mangling of the response, and then passes it on) work fine directly and through http proxy, but, to support SSL, which pandora uses to load the applet + initial auth, it has to pass data back and forth, which so far has been quite the pain. It "works" standalone, but it is a hack at best which of course fails when going through another proxy. Needs to be redone. After the proxy core is working fine, it will be very simple to convert the Saver to use it instead, because the method of operation is very similar to how fiddler works.

If you can get IE to work through Tor, then launch Fiddler, it should start working through Tor. If I remeber correctly, Tor is treated as a SOCKS proxy. I'm thinking you will need a translator that can use Tor as a HTTP proxy however; as Fiddler only does http/https. I've nearly finished the standalone version's server, however, and I plan on having support for SOCKS proxies in it.