Lines Matching refs:bitrates

15708 	  When switching bitrates we set the old streams as cancelled, but it
15713 	  bitrates to avoid erroring out.
22706 	  bitrates will be ignored and 128 kbps output will be produced
22708 	  property values, so that people who try to set higher bitrates
30655 	  switching bitrates w/ decodebin2 group draining.
30788 	  mode, now we get the bitrates.
31851 	  bitrates.
31985 	  caused corrupted streams in higher bitrates and other circumstances.
59624 	  selecting stream bitrates
59885 	  adaptivedemux: track per-fragment bitrates.
61391 	  switch bitrates when needed
63493 	  * It would fail on files with bitrates higher than 52Mbit/s (not common)
65094 	  bitrates. It's not clear whether the "flag" code maps to this,
94721 	  dashdemux: switch bitrates without switching pads
94755 	  A small struct that keeps a short history of fragment download bitrates
94768 	  dashdemux: change bitrates based on the stream bitrate
94773 	  This avoids switching the bitrates for streams frequently because
94840 	  (changing bitrates for example), the new pads dashdemux creates
95626 	  mssdemux: switch bitrates without switching pads
95649 	  *relatively* lower connection setup time and achieve higher bitrates.
95661 	  downloadbitrate keeps a short history of bitrates and helps
95847 	  for switching bitrates during playback to adapt to network
95857 	  the manifest won't use the non-active streams to compute total bitrates
120288 	  In particular, don't allow silly low bitrates, and allow reaching
124410 	  When switching bitrates, we might end up switching to a different
136601 	  baseparse: post duration message if average bitrates is updated
144277 	  accurately calculate the min/avg/max bitrates for aacparse.
144287 	  well as the minimum and maximum bitrates. Subclasses can override a
189457 …ext/wavpack/gstwavpackenc.*: Use bitrate property solely for bitrates and add new bits-per-sample …
189465 	  Use bitrate property solely for bitrates and add new