Bug 72497

Summary: k3b should accept m3u files without extended info
Product: [Applications] k3b Reporter: Tomas Hoger <thoger>
Component: Audio ProjectAssignee: k3b developers <k3b>
Status: CONFIRMED ---    
Severity: wishlist CC: ana, cwiesen
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Tomas Hoger 2004-01-12 18:46:04 UTC 
Version:           0.10.3 (using KDE 3.1.4)
Installed from:     (testing/unstable)
Compiler:          gcc version 3.3.2 (Debian)
OS:          Linux (i686) release 2.4.21-debian

I think k3b should support M3U *without* extended info, i.e. m3u files, which only contains list of mp3s (oggs, wavs, ...).  When I add such "plain" playlist to audio projects, k3b complaints about unsupported file format.  Using #EXTM3U as first line of m3u file (and no other additional info) fools k3b to accept it, but it's not very comfortable.  Since "plain" playlists are very common and supported by mp3 players, I think they should be accepted by k3b too.  Hence all files with .m3u extension should be treated as playlist.

Thanks!
Comment 1 Tomas Hoger 2004-05-19 22:03:20 UTC 
I've been asked by KDE Team's beg mail to review this report.  I confirm this is still valid with KDE 3.2.2 and K3B 0.11.9.

Anyway I took a quick look into the code and I tried to disable check for #EXTM3U in src/projects/audiocd/k3baudiodoc.cpp in K3bAudioDoc::readM3uFile functions.  However, problem arises for MP3s, for which this function is called too ;(.
Comment 2 Sebastian Trueg 2004-05-19 22:08:11 UTC 
that's the problem: we need auto-detection. So one possibility would be to check if the first line points to an existing file. But that cannot be done by reading a line since the file may be binary...
Comment 3 Sebastian Trueg 2004-09-16 12:09:41 UTC 
*** Bug 89112 has been marked as a duplicate of this bug. ***
Comment 4 Ariel 2008-10-07 06:41:24 UTC 
*** This bug has been confirmed by popular vote. ***