Bug 127056 - LUG Radio podcast not playing full length
Summary: LUG Radio podcast not playing full length
Status: RESOLVED DUPLICATE of bug 130185
Alias: None
Product: amarok
Classification: Applications
Component: Podcast (show other bugs)
Version: 1.4-SVN
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-10 04:02 UTC by nikosapi
Modified: 2006-08-05 03:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description nikosapi 2006-05-10 04:02:09 UTC
Version:           svn revision 539234 (using KDE KDE 3.5.2)
Installed from:    Fedora RPMs
Compiler:          gcc 4.1.0 
OS:                Linux

Out of all the podcasts I'm subscibed to LUG Radio is the only one that produces this error.
amaroK downloads the file fine (right file size and length (in xmms)) but when I play the file in amaroK the files cut off around ~35 min. When I play that exact same file in xmms it plays the whole way through.
To add to the confusion, when I transfer the file to my iPod (through amaroK) the same problem occurs. When I transfer the same file through GTKpod it plays the whole way through.
LUGRadio's website is: http://www.lugradio.org/ and the feed I'm using is: http://www.lugradio.org/episodes.rss
Comment 1 EJ Finneran 2006-05-23 03:46:52 UTC
I'm seeing the same behavior in Amarok 1.4 on Kubuntu Dapper.  The file is all there but it seems like a bug in Amarok's player because xmms or another player will play the whole file back.
Comment 2 Ian Monroe 2006-05-23 04:33:41 UTC
What engine do you use.
Comment 3 nikosapi 2006-05-23 04:51:13 UTC
xine
Comment 4 Tobias Niwi 2006-07-31 09:42:24 UTC
I have this experience generally. All my podcasts aren't played to the end. I have tested it with Amarok 1.4.1 with Xine and Helix. But I guess it is a different problem in my case.
Comment 5 Martin Aumueller 2006-08-05 03:33:14 UTC
This appears to be the same problem as in bug 130185.

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