31 May
2025
31 May
'25
2:26 p.m.
On Fri May 30 23:00:06 2025 +0000, Nikolay Sivov wrote:
We need to figure out how to avoid this additional field.
since the presentation clock does not support the thinning parameter, the media session needs to hold it, somehow. perhaps we should query a source for it or something?
does changing the rate of the presentation clock actually change the return value of the media session's GetRate() as well and is this tested? maybe the problem is that the media session should hold both rate and thin on its own.
this is also the reason I added the "clock is unaware of thinning" test in the first place, because an initial version of my patch just forwarded the thin parameter to the clock and made it support that, but that's wrong.