Re: Need API to read the CSRC on received tracks (#4)

On Aug 2, 2015, at 4:16 PM, Iņaki Baz Castillo <ibc@aliax.net> wrote:
> 
> It is extremely useful. It is just that we cannot use it because it is not exposed in the API, but the usecase is **really** big.

[BA] Big as in important for a single use case, or for multiple use cases? 

Also, what part is important?  CSRCs? Audio levels? Both? How frequently does the data need to be retrieved?

The basic polling approach is being implemented, but that is only for low frequency access for UI updates - not to obtain data for FFTs.

Received on Monday, 3 August 2015 01:09:15 UTC