Bug 272879

Summary: The collection scanner does not recognize tracks specified in cue files
Product: [Applications] amarok Reporter: sdeber
Component: Collections/LocalAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED DUPLICATE    
Severity: normal CC: mitchell, ralf-engels
Priority: NOR    
Version: 2.4.1   
Target Milestone: 2.4.1   
Platform: Debian unstable   
OS: Linux   
Latest Commit: Version Fixed In:

Description sdeber 2011-05-09 20:31:41 UTC
Version:           2.4.1 (using KDE 4.6.2) 
OS:                Linux

In amarok 2.4.1, if the music file is opened directly with amarok, then the cue file for it will be loaded correctly and all tracks are recognized. However, if the file is loaded with collection scanner, then cue information is not loaded at all. 

I tried to use amarokcollectionscanner from command line manually, the output confirms that the track information in the cue file is not recognized.

ak70@sdeber:~$ ls ~/Music/k
CDImage.ape  CDImage.ape.cue
ak70@sdeber:~$ amarokcollectionscanner ~/Music/k
<?xml version="1.0" encoding="UTF-8"?>
<scanner count="1">
    <!--Created by amarokcollectionscanner 2.4.1onMon May 9 20:36:10 2011-->
    <directory>
        <path>/home/ak70/Music/k/</path>
        <rpath>Music/k</rpath>
        <mtime>1304962119</mtime>
        <track>
            <uniqueid>0871a889715b9da22062dab7f9ee9aad</uniqueid>
            <path>/home/ak70/Music/k/CDImage.ape</path>
            <rpath>Music/k/CDImage.ape</rpath>
            <filetype>0</filetype>
            <title>CDImage</title>
            <bitrate>1060</bitrate>
            <length>953000</length>
            <samplerate>44100</samplerate>
            <filesize>126325260</filesize>
            <mtime>1300524908</mtime>
            <trackGain>-1</trackGain>
            <trackPeakGain>-1</trackPeakGain>
            <albumGain>-1</albumGain>
            <albumPeakGain>-1</albumPeakGain>
        </track>
    </directory>
</scanner>
ak70@sdeber:~$


Reproducible: Always
Comment 1 Myriam Schweingruber 2011-05-10 04:02:18 UTC

*** This bug has been marked as a duplicate of bug 187587 ***