Summary: | Amarok (taglib) fails to tag .ra (realaudio) files | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Ariel <ubuntu> |
Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED NOT A BUG | ||
Severity: | normal | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Old (liba52) RealAudio format file |
Description
Ariel
2006-12-28 04:05:13 UTC
Created attachment 19052 [details]
Old (liba52) RealAudio format file
mplayer: audio decoder: [liba52] AC3 decoding with liba52
Unfortunately I'm unable to make Amarok crash when showing the tags of this file. Do you happen to have one which makes Amarok crash? Sorry if I was not clear enough. To clarify. amarok does _not_ crash on this. It just fails to tag '.ra' files and gives up on scanning the collection. On a separate note: I think the if (>5% failure ratio) then give-up solution is misguided also. The best solution is to definitely log all failures (and report to the user as amarok is doing) but continue the scan till all the collection is scanned. I think there's no good reason to give up in the middle because some unsupported files exist in the collection, 5%, 10% even 50% is ok. The user just wants files tagged, even if there's a small success ratio the tagging is still useful. Just my personal preference. Thanks. SVN commit 617355 by aumuell: don't crash when encountering files with no tags during collection scan CCBUG: 139299 M +1 -1 collectiondb.cpp --- trunk/extragear/multimedia/amarok/src/collectiondb.cpp #617354:617355 @@ -3404,7 +3404,7 @@ fillInBundle( values, *bundle ); valid = true; } - else if( MediaBrowser::instance()->getBundle( bundle->url(), bundle ) ) + else if( MediaBrowser::instance() && MediaBrowser::instance()->getBundle( bundle->url(), bundle ) ) { valid = true; } Thanks very much for clearing up the misunderstanding. The reason why we don't continue indefinetely when errors are encountered until all the collection has been scanned is, that installation errors might be the real cause of the problem. And then it's no use wasting any additional time. |