#95
  • Created on
    2011-02-01 20:02
  • Reported by
    rbencina
  • Status
    Fixed
  • Priority
    Normal (3)
  • Assigned to
    philburk
  • Milestone
    V19-M1
  • Plan Level
    -
  • Permission type
    Private
  • Due Date
    -

Attachments

Related Tickets

Add new subtask or bug
Edit

Merge Requests

PA/CoreAudio reported streamInfo->input/ouputLatency may not take driver latency into account

According to the report here:
http://music.columbia.edu/pipermail/portaudio/2009-June/009205.html

Yann writes:

I'm not familiar with the details of CoreAudio but from a quick code
inspection, it looks like the CoreAudio latency calculation for
streamRepresentation.streamInfo.inputLatency / outputLatency doesn't
take into account the latency portion attributable to the driver (i.e.
at minimum I would have thought it would include the capture/playback
buffer latency). There are some comments in the code which question
the way the latency is calculated.

For more info about computing CoreAudio latency values see the comments in ticket #175 PA/CoreAudio recommended deviceInfo->default*Latency is 0

META TICKET: #181 [META] ensure reported streamInfo->input/ouputLatency values are correct
User picture
  on 2011-02-05 00:38 *
By rbencina
CoreAudio provides quite detailed latency information to the client, so I agree that this should be fixed.
User picture
  on 2011-07-22 03:48 *
By philburk
PA now queries the device and system latencies. These are taken into account when handling suggestedLatency. Reported input and output latencies are now based on the sum of multiple latencies. The actual latencies still need to be verified by direct measurement.
User picture
  on 2012-01-27 01:18 *
By rbencina
Status changed from New to Fixed
TRAC migration: propagating ticket status from TRAC