Skip to main content
Home Documents Game Manuals I Scrobbler FAQ Hidden Preferences
I Scrobbler FAQ Hidden Preferences

I Scrobbler FAQ Hidden Preferences

Game Manuals · PDF
FilenameiScrobbler_FAQ_Hidden_Preferences.pdf
Size0.07 MB
Subsection I Scrobbler FAQ Hidden Preferences
Downloads1
Enjoying MacTrove? Anonymous downloads are free and unlimited. Create a free account to track favorites, contribute metadata corrections, and join the community chat.
Reader
I Scrobbler FAQ Hidden Preferences
/
Loading…
OCR / Text contents
Scrobbler FAQ Why does iScrobbler use so much memory? First off, the only memory number that can even get close to the actual memory used by iScrobbler is "Private Memory Size" (RPRVT), any other stat includes virtual memory (not actually backed by allocated physical memory) and/or shared library memory (not directly used by iScrobbler). See the Memory FAQ in the next post for more info. Having said that... For version 2.0 and later, large memory use will likely be do to the Local Charts data. It's the price paid for all the fancy stats the data can give you. As an upper limit, iScrobbler will use half the private memory used by iTunes. That should be a rare case though. The only way to reduce memory use is to disable the data collection using a hidden pref. In addition, iScrobbler 2 comes in a 64bit Intel flavor for Leopard and Core 2 users. This is the default binary for those systems and should run faster than the 32bit binary. However, it will also use 20%-30% more memory than the 32bit binary of iScrobbler. *************** 64-bit Note: It is completely normal for a 64bit app to have a 3+GB VM size. Again, the VM stat means next to nothing. *************** For version 1.5.x and earlier large memory use is usually because of the Album artwork cache. You can override the default cache limit using a hidden pref, or turn off the cache in the preferences. All versions of iScrobbler have been tested with a memory leak detector and there are no known memory leaks. Why does iScrobbler use so much CPU time? Again, this is the 2.0 and later Local Charts data gathering. The initial iTunes library import can use 80-90% of one CPU (or core) for many hours. After that, there will be spikes in CPU usage as songs are played or when chart maintenance is performed (every night at midnight, and every Sunday at noon GMT). Note: Leopard is about twice as fast as Tiger when operating on the chart data and the 64bit iScrobbler is even faster. What do the various menu colors represent? Orange = OS X thinks your local network connection is not available. All tracks will be queued and no submission will be attempted until OS X recognizes a valid network connection. Green = iScrobbler is attempting to submit one or more tracks. Red = The submission attempt failed. All tracks will be queued. Further attempts will be made until the submission is successful. Black = No submission has been made, or the last submission attempt succeeded. For Orange and Red colors, you can hover your mouse over the menu and a tool tip will appear with a more detailed explanation of the problem. Alternatively, you can open the Statistics window for the same information. Menu Note glyphs: Barred eighth notes: Tracks will be submitted. Sharp note (or number symbol): Tracks will not be submitted. Why doesn't the menu work? If the menu won't open when you click on the notes, the problem is you have Hide checked for the iScrobbler Login Item. If the menu opens when you click on th…

Showing first 3,000 characters of 9,005 total. Open the full document →

Subscribe to I Scrobbler FAQ Hidden Preferences
mp.ls