Subsonic Forum

Release notes: viewtopic.php?f=4&t=9777&start=15#p51424

Feedback goes here.

Good Morning Hakko, let 0 7 19 run overnight. It seems that the the pickup of the missing artist info is still an issue.

The scanned picked up another 3200 artists bio info, but that was it...

the last played issue in the group works like u said, even though it would be nice to have a last played possibilty without using last.fm...

all for now..law

First try scanning again. viewtopic.php?f=11&t=10457

Ok Thanks ! Ill try it.

PS where is your "Donate" Button ?

Currently, there is no "Donate" button. My approach is to encourage people who enjoy the features I've added to donate money to charity instead (animal rights, doctors without borders, cure for cancer etc). If you do, feel free to post on the forum to encourage others to do the same, it always motivates me. Thanks!

@hakko: Version 0.7.19 is awesome! Thank you for updating the way artist biographies are updated from Last.fm. This addresses an issue I reported a few months ago... Thank you also for allowing the end user to set min/max time limits for track length when using radios.

So far everything works perfectly.

I have one question: The biography for one of my artists did not update to the latest information on Last.fm and there was no artist image, so I clicked Edit, deleted the biography text, then re-scanned. This did not fill in any information at all. I then deleted the artist from my music folder, re-scanned, then added the artist back to my music folder and scanned again. This was not successful either. It is not a huge problem, but I was wondering why this was occurring. Do I need to delete the artist from the postgre database, then re-scan? If so, do you know the code to run (I am using Ubuntu 12.10)?

Thank you in advance for your help!

As soon so you edit an artist biography, it'll never be updated from last.fm again (to not overwrite your changes). So you need to delete both your own artist info and the blocking of further lookups.

Code: Select all

delete from music.artistinfo where artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');
delete from library.webservice_history where calltype_id = 5 and artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');


hakko wrote:As soon so you edit an artist biography, it'll never be updated from last.fm again (to not overwrite your changes). So you need to delete both your own artist info and the blocking of further lookups.

Code: Select all

delete from music.artistinfo where artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');
delete from library.webservice_history where calltype_id = 5 and artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');


@hakko: I am not sure I am following your code example. Am I to assume that the actual code is in parenthesis, and the rest of the text is comments? Also, what woudl I need to run in order to get into postgre so that I can run your code? I am not very well versed in working with postgre sql...

On Ubuntu, you would run psql -U postgres -d musiccabinet in a terminal (don't know if psql is on your path), which provides a prompt to execute sql commands. Paste the two delete statements for your artist and press enter, then Ctrl+D to exit.

hakko wrote:On Ubuntu, you would run psql -U postgres -d musiccabinet in a terminal (don't know if psql is on your path), which provides a prompt to execute sql commands. Paste the two delete statements for your artist and press enter, then Ctrl+D to exit.

@hakko: Thanks... I will give it a go.

hakko wrote:On Ubuntu, you would run psql -U postgres -d musiccabinet in a terminal (don't know if psql is on your path), which provides a prompt to execute sql commands. Paste the two delete statements for your artist and press enter, then Ctrl+D to exit.

Whenever I run the command psql -U postgres -d musiccabinet I get the following: psql: FATAL: Peer authentication failed for user "postgres" Not sure why I can not be authenticated. I don't recall setting a password for user postgres. If for some reason I did, would I need to enter it as part of the command? If so, what is the syntax?

Do you have a file called ~/.pgpass containing a password? You do need a password and psql will ask you for it unless you have it stored in that file (or if you've su:ed into your postgres account?). You could also try the graphical tool called pgAdmin III (probably found in the same bin directory as psql), but it'll require a password as well...

Also, this (depending on where you connect from): http://stackoverflow.com/questions/2942 ... r-postgres

hakko wrote:Also, this (depending on where you connect from): http://stackoverflow.com/questions/2942 ... r-postgres

@hakko: Thank you for this information. I am now able to log into the database and make the desired deletions! Editing the /etc/postgresql/9.1/main/pg_hba.conf file to replace ident with md5 was the answer.

One thing I would like to point out, though, in case anyone else ever needs to delete artists from the postgre database. When running the following code"

Code: Select all

delete from music.artistinfo where artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');
delete from library.webservice_history where calltype_id = 5 and artist_id in (select id from music.artist where upper(artist_name) = 'Nirvana');

Since the code syntax contains "upper(artist_name) =" the artisi name needs to be entered in all upper case like NIRVANA or the commands will fail to delete anything.

Thank you for all of your help, hakko. You are amazing!

Thanks for DSub compability.