After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636711 - Audio track splits incorrectly parsed
Audio track splits incorrectly parsed
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
2.32.x
Other Linux
: Normal major
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-12-07 16:44 UTC by John Nelissen
Modified: 2018-09-21 17:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Track 10 edit info following automatic split (fixed number of parts =10) (26.94 KB, image/png)
2010-12-07 16:44 UTC, John Nelissen 		Details

Description John Nelissen 2010-12-07 16:44:54 UTC 
Created attachment 176016 [details]
Track 10 edit info following automatic split (fixed number of parts =10)

New audio project (lecture) approximately 52 minutes long.

Tried to use the automatic split feature to enable listeners to "back up" at about five minute intervals instead of re-playing in entirety.  (Fixed parts and fixed intervals were attempted.)

Problem:
Track numbers are shifted such that the first interval of audio is the highest numbered track on cue sheet.  If ten tracks selected track 10 contains first five minutes of audio and track 1 contains the next five, etc.

If I attempt to override the automatic parsing I receive an error on the highest numbered track indicating it is too short and that 6 seconds will be added.  The start and stop times for that track then are reset to some (apparently) arbitrary value.
Comment 1 GNOME Infrastructure Team 2018-09-21 17:11:32 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/brasero/issues/152.