Opened 13 years ago
Closed 13 years ago
#121 closed enhancement (fixed)
There should be a managed latency control for VS API
Reported by: | ph3-der-loewe | Owned by: | ph3-der-loewe |
---|---|---|---|
Priority: | medium | Milestone: | RoarAudio major release 0.4 |
Component: | VS API | Version: | 0.4beta3 |
Keywords: | latency, latency management | Cc: | themaister, ph3-der-loewe |
Architecture: | Compiler: | ||
Difficulty: | Kernel: | ||
Operating System: | Parent Tickets: | ||
Patch attached: | no | Protocol: | RoarAudio |
Sound driver: | Topic: | New feature |
Description
There should be a sub-module of VS API to manage latency. This module should check the latency and adjust buffers and such according to the control goal.
There should be 3 different modes:
- full automatic mode (may search a good latency which is not minimum to make it more robust against buffer underruns. Maybe it should soft control the latency to be at (min + (max - min)/2).)
- get latency as low as possible. maybe with different levels of aggression.
- fixed latency mode. A mode in which the closed loop control will try to get latency to a fixed and given value.
Subtickets
Change History (2)
comment:1 Changed 13 years ago by ph3-der-loewe
- Owner changed from themaister to ph3-der-loewe
- Status changed from new to assigned
- Does mainly apply to buffered mode
- P-controller seems to be best for within/near tolerance band. Maybe different P-gain or additional D for out of band controlling to optimize speed. (Only of interest at start of stream and on change of target latency)
- Depends on changes in VIO layer to support better buffer control
- Can be done within normal calls to roar_vs_latency() and operate in background.
comment:2 Changed 13 years ago by ph3-der-loewe
- Resolution set to fixed
- Status changed from assigned to closed
- Version changed from current to 0.4beta3
simple implementation is done.
Note: See
TracTickets for help on using
tickets.