Bug 306827 - Unknown bit rate and zero length on track properties
Summary: Unknown bit rate and zero length on track properties
Status: RESOLVED NOT A BUG
Alias: None
Product: amarok
Classification: Applications
Component: Collections/Local (show other bugs)
Version: 2.6.0
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: 2.7
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-15 10:55 UTC by Amir Ghassemi
Modified: 2012-09-16 20:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Amir Ghassemi 2012-09-15 10:55:58 UTC
After updating to 2.6.0 and adding two albums, I've noticed bit rate and length not detected. older tracks which scanned with older versions were fine. I though it's file corruption. tried MP3Diags and EasyTag which i worked with them before, but this time with no success.
I've noticed deleting/removing files has nothing with Amarok's MySQL DB (at least on 2.6) so deleted associated database and rescanned collection. This time bit rate, sample rate and length for every tracks is unknown.
metaflac for flac files detects bit rate. Picard, EasyTag and MP3Diags are fine. but Amarok fails.


Reproducible: Always

Steps to Reproduce:
1. Open amarok.
2. Open a file. Amarok > Play Media
3. Select track from playlist. Right click and "edit track details"
Actual Results:  
Summary tab contains:
Length: 0:00
Bit rate: ?
Sample rate: Unknown

Expected Results:  
See these on Summary tab:
Length: mm:ss
Bit rate: 320 kb/s


Changes i applied for 2.6.0 compilation:
added libfoa for music fingerprint search ability.
no success after disabling foa and recompiling.
Comment 1 Myriam Schweingruber 2012-09-15 12:02:20 UTC
Which phonon backend do you use?
Comment 2 Amir Ghassemi 2012-09-15 13:28:51 UTC
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.
Comment 3 Amir Ghassemi 2012-09-15 13:49:20 UTC
(In reply to comment #1)
> Which phonon backend do you use?

Gstreamer. same problem with vlc.
Comment 4 Myriam Schweingruber 2012-09-16 12:47:44 UTC
Thank you for the feedback.
Comment 5 Matěj Laitl 2012-09-16 14:27:55 UTC
Does this happen only for Local Collection tracks, or also for tracks outside of collection folders you browse through Amarok file browser?
Comment 6 Amir Ghassemi 2012-09-16 15:43:15 UTC
(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..
Comment 7 Matěj Laitl 2012-09-16 16:13:57 UTC
(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.
Comment 8 Amir Ghassemi 2012-09-16 19:55:29 UTC
(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.
Comment 9 Matěj Laitl 2012-09-16 20:13:39 UTC
(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..