Adrian Chadd
9572684af7
Since it's not immediately obvious whether the current TX path handles
...
fragment rate lookups correctly, add a comment describing exactly that.
The assumption in the fragment duration code is the duration of the next
fragment will match the rate used by the current fragment. But I think
a rate lookup is being done for _each_ fragment. For older pre-sample
rate control this would almost always be the case, but for sample
it may be incorrect more often then correct.
2012-10-26 16:31:12 +00:00
..
2012-10-22 11:57:26 +00:00
2012-10-26 05:48:53 +00:00
2012-10-25 15:45:32 +00:00
2012-10-23 16:03:00 +00:00
2012-10-26 14:50:16 +00:00
2012-10-22 17:50:54 +00:00
2012-10-26 14:36:02 +00:00
2012-10-26 02:09:55 +00:00
2012-10-10 08:36:38 +00:00
2012-10-26 16:31:12 +00:00
2012-10-25 21:08:02 +00:00
2012-10-22 17:50:54 +00:00
2012-10-09 14:32:30 +00:00
2012-10-24 18:21:22 +00:00
2012-10-26 03:02:39 +00:00
2012-10-26 16:01:08 +00:00
2012-09-14 22:00:03 +00:00
2012-10-26 00:08:50 +00:00
2012-10-22 02:12:11 +00:00
2012-10-25 09:39:14 +00:00
2012-10-16 13:37:54 +00:00
2012-10-22 21:09:03 +00:00
2012-10-25 09:39:14 +00:00
2012-10-25 09:39:14 +00:00
2012-10-23 08:33:13 +00:00
2012-06-01 03:59:08 +00:00
2012-10-25 09:39:14 +00:00
2012-07-10 21:02:59 +00:00
2012-10-14 22:33:17 +00:00
2012-08-14 11:45:47 +00:00
2012-10-22 17:50:54 +00:00
2012-10-22 17:50:54 +00:00
2012-10-22 03:00:37 +00:00
2012-10-10 08:36:38 +00:00
2012-10-22 11:57:26 +00:00
2012-10-23 02:20:11 +00:00
2012-10-25 19:30:58 +00:00
2012-10-22 17:50:54 +00:00
2012-10-20 12:07:48 +00:00
2012-10-26 16:01:08 +00:00
2012-10-10 08:36:38 +00:00
2012-10-22 17:50:54 +00:00
2012-10-24 18:32:37 +00:00
2012-10-22 13:06:09 +00:00
2012-10-22 02:29:53 +00:00