Better handling of nonplayable files

Crash dump

Amarok suggests a bad taglib

Thanks for the bug report. What taglib version are you using? Run `apt-cache policy libtag1c2a` to see what version you're running.

Amarok is just a front end to the multimedia backend that actually plays the music files, so if it can't play a file it's a problem with the backend. To find out which you're using, Settings -> Configure Amarok -> Engine -> Sound System.

Thanks for handling this.

$ apt-cache policy libtag1c2a
libtag1c2a:
  Installed: 1.4-4
  Candidate: 1.4-4
  Version table:
 *** 1.4-4 0
        500 http://gb.archive.ubuntu.com edgy/main Packages
        100 /var/lib/dpkg/status

It's not that amarok can't play .ra files, as such, but the fact that
after it fails to scan more than so many files in the collection, it
1) gives up scanning
2) shows a modal dialog that stops the next track playing until it is
acknowledged

While the underlying problem may be taglib, the way amarok handles it is
annoying.

Sam

Let's work together and figure out what would be the best outcome when this happens.

I think it'd be nice if the collectionscanner ran the entire scan, skipping over the files it couldn't handle, and then deliver one of those yellowish notifications in the bottom left corner with some text along the lines of:

 "Multiple files could not be added to the collecion because the current backend (<insert backend here>) can not play those files. Please consider using a different backend instead, if possible, or uprade your current backend to a newer version that can play those files."

Hopefully much less verbose than that. What do you think would be the optimal situation once this occurs?

I think you describe an excellent behaviour.

It handles any taglib failure gracefully and continues to play what it
can without interruption.

and to clear my wife's good name, I'm Sam, not Anne, but she was logged
in while I was playing music.

Sam

I'll search on the Amarok bug tracker if I can find a similar bug to link this one to. Until then, I'm marking it wishlist.

It looks like there is a bug in the kde bugtracker, #136430, that has the same issue as this. I've linked this bug to that one at the top of this page.

A developer there would like a copy of a file that causes the collectionscanner to crash. Please register an account at bugs.kde.org and provide a file for him at http://bugs.kde.org/show_bug.cgi?id=136430

Thanks

Thanks Andrew,

I submitted an audio file.

Sam

Thanks. We'll see what the Amarok guys come up with then.

fixed upstream, and in 1.4.5