- From: <bugzilla@jessica.w3.org>
- Date: Tue, 21 Aug 2012 01:53:36 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18571
Timothy B. Terriberry <tterribe@vt.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tterribe@vt.edu
--- Comment #8 from Timothy B. Terriberry <tterribe@vt.edu> 2012-08-21 01:53:36 UTC ---
(In reply to comment #5)
> Most of the Vorbis content I've seen tends to keep frame durations around ~23ms
> (ie 1024 @ 44100). My guess is that the higher numbers are for higher sample
> rate content.
It's actually for lower-bitrate content.
> samples per coded frame though. There may be counter examples, but in my
> experience the Xiph codecs (Vorbis, Opus?) tend to be the only ones that have
> varying output sample counts.
It is not hard to configure Opus to always use a constant frame size (in fact,
this is what all the current tools do by default... right now you would have to
write some custom code to be able to change it). But that can only be enforced
if you control the encoder.
(In reply to comment #7)
> It isn't clear to me how much distance there would be between such points in
> practice. That would also only work for cases where you are switching between
In practice, they would line up on any transient. Depending on the content,
that may not be often enough (it's also possible to construct pathological
streams where they would _never_ line up).
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Tuesday, 21 August 2012 01:53:37 UTC