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 356707 - Suspected caps neg problems cause horrifically broken audio
Suspected caps neg problems cause horrifically broken audio
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: dont know
git master
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-09-19 10:40 UTC by Jono Bacon
Modified: 2008-05-06 12:54 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Debug log (161.80 KB, application/x-gzip)
2006-09-19 10:42 UTC, Jono Bacon
Details

Description Jono Bacon 2006-09-19 10:40:34 UTC
Please describe the problem:
When recording and playing back audio at the same, there seem to be some terrible problems where the audio at the beginning of the playback audio is very jittery and broken. Wim suspects it could be caps negotiation problems thrashing it.

This problem manifests in Jokosher. This is what I do:

  import audio into a track
  play audio
  stop
  add second track, select the input and record
  (hear broken audio for a few seconds and then stablises)
  play all audio
  add new instrument, select input and record
  (very broken, skippy audio again at the beginning)
  press play, loooong delay before audio plays
  play again

I have attached a debug log when running the above steps.

Steps to reproduce:
1. 
2. 
3. 


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Jono Bacon 2006-09-19 10:42:00 UTC
Created attachment 73028 [details]
Debug log
Comment 2 Wim Taymans 2007-03-06 08:50:36 UTC
is this still a problem?
Comment 3 Sebastian Dröge (slomo) 2008-05-06 12:54:57 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!