| Summary: | Unknown bit rate and zero length on track properties | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Amir Ghassemi <ameretat> |
| Component: | Collections/Local | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | major | CC: | 123kash, matej, ralf-engels |
| Priority: | NOR | ||
| Version: | 2.6.0 | ||
| Target Milestone: | 2.7 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Amir Ghassemi
2012-09-15 10:55:58 UTC
Which phonon backend do you use? Reinstalled previous version (2.5.0-r2) from binary packages built after compilation on my host. Amarok throws error that collection db created with newer version and i droped it. everything works fine in this version. (In reply to comment #1) > Which phonon backend do you use? Gstreamer. same problem with vlc. Thank you for the feedback. Does this happen only for Local Collection tracks, or also for tracks outside of collection folders you browse through Amarok file browser? (In reply to comment #5) > Does this happen only for Local Collection tracks, or also for tracks > outside of collection folders you browse through Amarok file browser? Properties for Collection tracks that scanned by older versions, still shown correctly. But if i add another tracks to collection, or open a track outside Collection scanning path, Amarok couldn't detect them. I can say it's not just Properties like Bit rate or Length. ID3 tags aren't correctly detected neither. I've found it out after scanning full Collection (using new DB) with 2.6. Could you give me some hints how Amarok gets these data? I mean from any third party library or just with Amarok codes itself.. (In reply to comment #6) > (In reply to comment #5) > > Does this happen only for Local Collection tracks, or also for tracks > > outside of collection folders you browse through Amarok file browser? > > Properties for Collection tracks that scanned by older versions, still shown > correctly. But if i add another tracks to collection, or open a track > outside Collection scanning path, Amarok couldn't detect them. > > I can say it's not just Properties like Bit rate or Length. ID3 tags aren't > correctly detected neither. I've found it out after scanning full Collection > (using new DB) with 2.6. Oh, you should have told! It is almost for sure TagLib not present during the compilation. Did you compile Amarok yourself? Check the cmake output or attach it here if you don't see any problems in it. (In reply to comment #7) > (In reply to comment #6) > > (In reply to comment #5) > > > Does this happen only for Local Collection tracks, or also for tracks > > > outside of collection folders you browse through Amarok file browser? > > > > Properties for Collection tracks that scanned by older versions, still shown > > correctly. But if i add another tracks to collection, or open a track > > outside Collection scanning path, Amarok couldn't detect them. > > > > I can say it's not just Properties like Bit rate or Length. ID3 tags aren't > > correctly detected neither. I've found it out after scanning full Collection > > (using new DB) with 2.6. > > Oh, you should have told! It is almost for sure TagLib not present during > the compilation. Did you compile Amarok yourself? Check the cmake output or > attach it here if you don't see any problems in it. Thank you. It's Gentoo portage bug. Amarok 2.6 needs TagLib >= 1.7 but mine was older, so Amarok built without been linked to TagLib. BTW maybe be better to change CMake file and assign TagLib as essential dependency. (In reply to comment #8) > It's Gentoo portage bug. Amarok 2.6 needs TagLib >= 1.7 but mine was older, > so Amarok built without been linked to TagLib. BTW maybe be better to > change CMake file and assign TagLib as essential dependency. Good. Please file a Gentoo bug and add me to CC. We do emit big fat warning if TagLib is not found, but perhaps it is not enough.. |