Bug 1316672

Summary: cd ripper writes incorrect length tags, no XING header for VBR data
Product: [Fedora] Fedora Reporter: Herbert Carl Meyer <hcmeyer>
Component: rhythmboxAssignee: David King <amigadave>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 23CC: bnocera, gkrithi8, hcmeyer
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-12-20 19:22:52 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Herbert Carl Meyer 2016-03-10 17:59:56 UTC
Description of problem:
Ripping a CD produces incorrect track length information.
On playback, seek does not work properly, will seek past end of track, with unpredictable results.

Version-Release number of selected component (if applicable):
3.3

How reproducible:
100%


Steps to Reproduce:

1. Rip a CD, example used is Mike Oldfield/Tubular Bells

2. Watch correct track lengths indicated during rip process

3. Playback ripped tracks, lengths shown are too long, will seek beyond end of track

Actual results:

Incorrect track lengths shown

Expected results:

Correct track lengths

Additional info:

Tubular Bells used because there are only 4 tracks on disk.

Album Jacket says track times are 25:58, 23:20, 3:53, 2:48
Rhythmbox ripped tracks show lengths 40:15, 39:12, 4:53, 3:16
K3b ripped tracks show length 26:01 for first track (shown by rhythmbox)

Running MP3Diags over tracks produces error message about missing XING header in rhythmbox ripped tracks, and MP3Diags can correct tracks, show same time as K3b ripped tracks.

Comment 1 Fedora Admin XMLRPC Client 2016-09-15 15:16:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora Admin XMLRPC Client 2016-09-16 07:08:53 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2016-11-24 16:01:18 UTC
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2016-12-20 19:22:52 UTC
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 5 gkrithi8 2017-11-18 09:05:43 UTC
is this still reproducible ?

Comment 6 Herbert Carl Meyer 2017-11-27 14:23:13 UTC
No, system is updated.