It’s time for some clock rate matching

Comments, chapters, ... Slides Search
Loading Click here to add:
Subscribe to notifications

When subscribed to notifications, an email will be sent to you for all added annotations.

Your user account has no email address.

Information on this media

17 views
Matching different clocks is a common problem in real-time audio processing — audio may originate from one device, and may need to be rendered to a different device driven by a different clock, possibly running at a slightly different rate. Managing these clock rate differences is an important factor in avoiding underruns and overruns in real-time audio applications. This problem is partially addressed in GStreamer via GstClock's synchronisation and GstAudioBaseSink's clock slaving mechanisms. As the new de-facto Linux audio subsystem, PipeWire also implements clock rate matching and adaptive resampling, building on work done in the JACK community over the last decade and more. In this talk we will lay out the basics of the problem space, and then review the state of the art in both PipeWire and GStreamer. Contrasting the approaches taken should be interesting in itself, and maybe we'll find some new ideas to be inspired by. While the subject matter is a little bit in the weeds, there will be a gentle introduction for audience members with varying levels of familiarity with the topic.
Creation date: Oct. 8, 2024
Speakers: Arun Raghavan
License: CC BY-SA 3.0
Links:

Other media in the channel "GStreamer Conference 2024"