PDA

View Full Version : Debugging missing titles from database



Bill Moseley
2005-03-22, 14:29
I'm running CVS from yesterday.

Trying to understand why the database show the counts I'm expecting:

$ fgrep audiodir ~/.slimserver.pref
audiodir = /home/moseley/music

$ find /home/moseley/music -name \*.mp3 -o -name \*.ogg -o -name \*.flac -type f | wc -l
2257

$ telnet localhost 9090
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
info total songs ?
info total songs 1056 <<<<<------------- why not 2257?
info total artists ?
info total artists 321

What steps should I take to see the difference?


Do the Slim/* perl modules provide an interface I can use for my own
scripts?

For example, I'd like to use the same code Slim uses for accessing
track metadata (id3/vorbis tags). I'd like to use File::Find and
recurse my music folder and use the Slim modules to gather the meta
data. It would be helpful to have a small tool where I can pass a
file name and see how slimserver parses and how it would index. I
know I can turn on debugging and rescan, but I'd like to be able to
work with single files.

I'd also like to be able to do database queries directly on the
database. Then I could compare with the database and see what files
are not indexed. Any example scripts for this?

Thanks,



--
Bill Moseley
moseley (AT) hank (DOT) org

Steve Baumgarten
2005-03-22, 14:38
Bill Moseley wrote:

> It would be helpful to have a small tool where I can pass a
> file name and see how slimserver parses and how it would index. I
> know I can turn on debugging and rescan, but I'd like to be able to
> work with single files.

I've used the log file in the past. Start the server with the --log
option and then do a full rescan. It will list every track it finds. You
can then do your own find, massage both the log file and the find output
a bit, and do a diff. Not a perfect solution, but still quite useful.

> I'd also like to be able to do database queries directly on the
> database. Then I could compare with the database and see what files
> are not indexed. Any example scripts for this?

Funny, I was just thinking of putting one together -- I just this
afternoon grabbed a copy of the schema from svn.slimdevices.com (I only
saw a PNG file -- is there something in plain text format somewhere?). I
still have to write some perl code to read from the SQLite tables.

Basically I just wanted something to dump what's in the database to a
flat file for easier inspection.

(Having said that, the last time I checked, the server had picked up all
my tracks and albums correctly, at least as compared with the output of
a find command.)

SBB




Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.

Bill Moseley
2005-03-22, 23:39
On Tue, Mar 22, 2005 at 04:38:38PM -0500, Steve Baumgarten wrote:
> Bill Moseley wrote:
>
> > It would be helpful to have a small tool where I can pass a
> >file name and see how slimserver parses and how it would index. I
> >know I can turn on debugging and rescan, but I'd like to be able to
> >work with single files.
>
> I've used the log file in the past. Start the server with the --log
> option and then do a full rescan. It will list every track it finds. You
> can then do your own find, massage both the log file and the find output
> a bit, and do a diff. Not a perfect solution, but still quite useful.

I used the -d_scan option. First rescan got the same numbers -- but
then I deleted the .slimserversql.db and got numbers that just about
matched what find was saying.

> >I'd also like to be able to do database queries directly on the
> >database. Then I could compare with the database and see what files
> >are not indexed. Any example scripts for this?
>
> Funny, I was just thinking of putting one together -- I just this
> afternoon grabbed a copy of the schema from svn.slimdevices.com (I only
> saw a PNG file -- is there something in plain text format somewhere?). I
> still have to write some perl code to read from the SQLite tables.
>
> Basically I just wanted something to dump what's in the database to a
> flat file for easier inspection.

That would be nice. I need to clean up a lot of tags, first. Any
plugins for editing tags in the web interface? Probably slower than
I'd like to work, but it would be nice for fixing things as the show
up in play lists.

I just searched for "rain" (those in the Bay Area can appreciated
that today) and had a handful of duplicates. It would be nice to be
able to flag those for testing and removal later on right from the
web interface. I suppose writing a playlist could work.

--
Bill Moseley
moseley (AT) hank (DOT) org