Bug 378558 - wrong length aussumed for streaming ogg
Summary: wrong length aussumed for streaming ogg
Status: RESOLVED WORKSFORME
Alias: None
Product: amarok
Classification: Applications
Component: Playback/Streams (show other bugs)
Version: 2.8.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: 2.9
Assignee: Amarok Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-04-08 13:57 UTC by Martin Schröder
Modified: 2022-12-04 05:15 UTC (History)
1 user (show)

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


Attachments
1 minute stream rip (801.00 KB, video/ogg)
2017-04-08 13:57 UTC, Martin Schröder
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Schröder 2017-04-08 13:57:44 UTC
Created attachment 104921 [details]
1 minute stream rip

The attached ogg is captured by using streamripper on public ogg streams.

It contains 1 minute of music, but amarok believes it's much longer, making accurate positioning in the file difficult. It is only an example; other files show the problem (a 80 minute rip is claimed to have a length of 62 hours).

Other players (audacity, deadbeef, audacious) don't have this problem.
Comment 1 Myriam Schweingruber 2017-04-08 21:46:14 UTC
Does this happen with both Phonon backends? Don't forget to restart Plasma after changing the Phonon backend.
Comment 2 Martin Schröder 2017-04-08 23:45:15 UTC
(In reply to Myriam Schweingruber from comment #1)
> Does this happen with both Phonon backends? Don't forget to restart Plasma
> after changing the Phonon backend.

This installation offers only the GStreamer backend.
And please - why does the *backend* effect the way Amarok parses input files?
Comment 3 Myriam Schweingruber 2017-04-12 08:54:49 UTC
Simply because all sound related actions are performed by the phonon backend, including getting the length of a stream. We had differences in stream or track length reports in the past, and those definitely were backend related
Comment 4 Justin Zobel 2022-11-04 03:10:19 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 5 Bug Janitor Service 2022-11-19 05:13:48 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Bug Janitor Service 2022-12-04 05:15:23 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!