Google Music: The Best Service That Nobody’s Using
thepowerbase.com
thepowerbase.com
I didn't use it and uninstalled it by dragging the app icon into the trash. Didn't work.
I tried the AppDelete path. No go.
I googled around and found I was not the only one. Uninstall is broken and you are basically stuck with a prompt twice a day to install the Google Music app until you reinstall your OS or go slogging through the guts of your box, throwing switches you don't understand by mixing internal uninstall tutorials (ok, to be fair, this is how you do just about everything...).
In conclusion, that app is a daily annoyance and I'd caution people against installing it.
This seems to be a trend lately in Google's desktop software that I'm not comfortable with. On both my Linux and Mac machines 'ps aux | grep -i chrome' shows background processes running long after I've quit Chrome.
I don't see any GUI options to turn these off (there used to be an option in 'about: flags' that I think was related), and I have to end up killing them from the command line.
Not cool, Google.
All it does is serve as a reminder not to use or install any other Google app.
They are still used sometimes at concerts or carnivals to tally up people entering a location for records keeping, and to make sure that you're under fire code.
I have one of these counters too, but I only use it on the range to keep track of how many targets I've hit by sheer chance. ;)
[1] http://9cloud.us/c/general/pictures/album/36357/id/1239690/
I've also had issues where the app wanted to completely reupload my entire library. No thanks---I now just keep it set to monitor an empty directory.
Err... Actually iTunes weaves your ID into files you buy and nobody seemed to notice evidently (so it wasn't a big deal).
It's not free, but at just over $2 a month, it seems to give Apple a lot more flexibility with bargaining with the publishers, which makes me feel a bit more secure about the future of the service and my personal music collection.
Also, it's surprisingly nice to have it match against songs that are already uploaded to their service, It took over a month to get my entire library into the Google Music cloud, yet all my music was available in iTunes match within the hour.
"Does iTunes Match stream or download songs? On a computer, any songs stored in iCloud will stream over the air when played, though you can download them at any time by clicking the iCloud download button. iOS devices will start playing tracks from iCloud as they download and will store them so that you can listen to them later even if you don’t have a network connection. Apple TV only streams songs."
And the Linux app sucks rocks. My memory is that it's an enormous pain to get installed on F16/x86-64. It doesn't understand the standard proxy environment variables or gconf settings, and in fact when used behind a proxy, THE UI LOCKS UP SOLID a few seconds after starting. So I can't use it at work. (Because who wants to listen to music at work?)
I wouldn't even care, except that I have to use the desktop app. Even things that I'd think would work as web apps aren't there. You can't upload from a web app. You can't manage play lists from a web app.
That said, the Android player app is actually not bad at all, and I do use it. But the cloud side of the equation is a total fail from my perspective.
For some reason Google Music will use almost 2.5x the amount of data that Pandora or Spotify use on my phone. (Keep in mind this is with Background data and High quality streaming turned OFF!)
In this mobile data cap / throttle world that we live in I can't afford to have my music app use more than 2gb of a data a month!
I have loaded up a bunch of old radio shows & lectures for which I would not have the space on my phone but w/ Google Music I'm all set.
If the team can figure out easy streaming podcasts (like Android Double Twist but without so much spammy/crap content) they will have themselves a nice little business
But, it isn't illegal to own pirated music. It is just illegal to distribute them. So perhaps this isn't a problem?
> A ripped copy of a song put up online can be
> as unique as a fingerprint
If they are just MD5'ing the file, then changes to the metadata could cause this fingerprint to change. > But, it isn't illegal to own pirated music. It is
> just illegal to distribute them. So perhaps this
> isn't a problem?
Record companies (IIRC) have successfully argued that streaming your own music to yourself is a 'broadcast/performance' to a single person. There are many ways that they could attempt to go after this.I like having lots of music, and paying for it, but I am not a fan of owning a physical CDs.
IANAL, but it was always my impression that that owning and pirating music was illegal, but it was just that the lucrative civil damages suits come from targeting distributors. If Google Music becomes a central hosting platform, then subpoenaing them for information about customers with known contraband music might become trivial technically and therefore economically feasible.
1. Login to Google Music once from an American IP address.
2. Use it forever from any IP address.
My workflow is the following:
1. Wait for Amazon MP3 special for album I want
2. Buy album
3. Download to Mac with MP3 downloader
4. Sync Google Music with iTunes library.
5. Stream Google Music to phone and browser at work.
This way I have a physical master to use how I see fit. Prices are usually better on Amazon than iTunes store, $4 per album unless I'm buying from a personal favorite on release day. Selection is basically universal.
I've been liking this scrobbler/lyrics looker-upper for the web client:
http://www.danielslaughter.com/projects/google-music-with-la...
I finally decided to buy a few albums during the big music sale G Music promoted during the holiday season. Unfortunately every time I'd check out it would prompt me to log in again. During this I noticed that at least some element of the process was using a different subdomain than the album page I was checking out from. Not sure if the login cookie just wasn't persisting across differing subdomains domains or my browser was set to block cookies set by third parties, but I vaguely remember having to manually whitelist the domain in Chrome's cookie exception manager to complete my purchase. It took a moment to figure out because there was no particular useful error - just the prompt to log in again.
I have no idea if I previously changed a setting in Chrome that resulted in this annoyance or if it was a default setting in Chrome, but that nearly prevented me from buying from Google's music service. There's no way someone like my Mom or sister would've figured that out. I hope they resolved that component assuming the problem wasn't limited to just my set up because at the time I thought it was rather silly that I wasn't able to easily purchase from a Google browser without modifying settings.
http://support.google.com/androidmarket/bin/static.py?hl=en&...
We're sorry. Google Music is currently only available in the United States.
Obviously this setup is rather technical, and requires a nontrivial bit of setup work, but the fact that it is often easy to have ideas for substantial life improvements and then implement them well, with free software, has left me a bit disenchanted with the offerings from large, generally innovative companies like Google and Apple (a similar hack for streaming music to an AirPort Express from MPD can be had with the raop-play module for PulseAudio, for example).
I love Google Music, though not in a browser. It's a really great service once you run it in Nuvola Player (multimedia keys support, switching to Grooveshark and other services).
Too bad you have to "cheat" to register from Europe.
I wish they had a download option for all the music not just the music that I bought on google. That would help me to get rid of all the music on my computer.
It doesn't help that I already spent a month uploading my music to Amazon. I'm not going through that again anytime soon.
Well that's simply false. If I ripped a CD myself, it wouldn't be byte-for-byte identical as the copy on Pirate Bay. In fact, if I rip it myself and don't share that rip with anyone it should probably be unique within the system.
And how hard would it be to figure out who has illegal copies of an unreleased album?
The issue is that the audio CD standard ("Red book") does not require block-accurate addressing during seeking[1]. This allows you to still be able to play scratched up CDs, with the trade off being that even discs that aren't scratched up that bad may not give you a byte-for-byte copy on different reads.
To try and account for this, CD ripping programs like EAC have to make multiple read passes and apply certain algorithms to determine where jitters occur and only take the "good parts."
[1]: http://en.wikipedia.org/wiki/Jitter#Compact_disc_seek_jitter
EDIT: I confused C2 error pointers and Accurate Stream. Mea culpa.
I don't see how ripping could be so different if people use the same settings.
The "lossy" part of MP3 is that the encoder decides to throw away frequency bands to reduce the information size.
This is more than just choosing a bitrate and being done with it - different encoders treat different bands as important or unimportant, attempting to make a smaller sized file still sound better.
$ ls -l KDE_Startup_new.wav
-rw-r--r-- 1 jerf jerf 970882 Feb 27 21:42 KDE_Startup_new.wav
$ lame KDE_Startup_new.wav 1.mp3
$ lame KDE_Startup_new.wav 2.mp3
$ md5sum *mp3
0bc5fee9b5d67ca2d6f1bf61a186067a 1.mp3
0bc5fee9b5d67ca2d6f1bf61a186067a 2.mp3Some multi-threaded encoders may be non-deterministic (from using concurrency), but encoding MP3s (or nearest equivalent) on modern hardware is generally fast enough for casual use even on a single thread, and parallelizing the operation would be better done at the level of tracks rather than within a track.
MP3 compression works by FFT-ing the audio stream, which is something that has to be ingested sequentially. It's not realtime since the encoder does it much faster than realtime, but it is doing sequential analysis of the file.
Usually a high quality encoder does multiple passes of the file to better fit it's FFT with the source material.
My feature wishlist:
* iOS native app
* nested playlists
* smart playlists
* playlist pictures
* playlist export
* gapless playback
* built-in scrobbling to last.fm
* volume control in android store
* music manager instant recognition(heh, my reply made more sense with the original title)