Bug 291775 - ape/cue files are not played correctly
Summary: ape/cue files are not played correctly
Status: RESOLVED DUPLICATE of bug 187587
Alias: None
Product: amarok
Classification: Applications
Component: general (show other bugs)
Version: 2.5-git
Platform: openSUSE Linux
: NOR normal
Target Milestone: 2.6
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-17 13:28 UTC by Alin M Elena
Modified: 2012-04-24 12:15 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Alin M Elena 2012-01-17 13:28:35 UTC 
Version:           2.5-git (using Devel) 
OS:                Linux

I have an ape/cue cd...
I load the ape file in the play list and it correctly loads all the tracks.
However when I play first track it stops at the end.
I start the second track by hand and then will start from the first track again and stop at the end of the second track
something like that happens for the third track too... starts and first stops after third.

I use phonon-vlc as a backend

Alin

Reproducible: Always

Steps to Reproduce:
...

Actual Results:  
...

Expected Results:  
...

OS: Linux (x86_64) release 3.2.0-4-desktop
Compiler: gcc
Comment 1 Myriam Schweingruber 2012-01-17 15:51:55 UTC 
I presume this is a cue file which is in the collection, right? In that case this is a duplicate of bug 187587
Comment 2 Alin M Elena 2012-01-17 16:02:24 UTC 
NO... I load the ape file from amarok's file browser.

the folder that contains the ape/cue is listed under the collection folder.

but I do not see the connection with the indicated bug... 

Alin
Comment 3 Myriam Schweingruber 2012-01-17 21:48:32 UTC 
Well, it is in the collection, that is the point, it doesn't matter if you start it from the files browser. Please try with a file that is not in a collection folder
Comment 4 Myriam Schweingruber 2012-02-29 10:57:00 UTC 
Any news about this?
Comment 5 Myriam Schweingruber 2012-04-24 12:15:58 UTC 

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