| commit | e8f17308146f446bc46f6a3b787aed2406ce8d31 | |
| author | Thomas Guillem <thomas@gllm.fr> | |
| Thu, 13 Aug 2020 13:56:04 +0000 (13 15:56 +0200) | ||
| committer | Thomas Guillem <thomas@gllm.fr> | |
| Wed, 26 Aug 2020 14:01:11 +0000 (26 16:01 +0200) | ||
| tree | 20190a841955b65cb1727d417f1964b2d971fe0f | treesnapshot (tar.gz zip) |
| parent | 153073659a7e2d22213717eb3d678d307b3b2c1f | commitdiff |
player: add a metadata listener API
And use the loudness measurement as a first use case.
The main difference between metadata listeners the player listeners are:
- The information returned by metadata events is mainly useful for the UI, it
should not be used to control the player.
- It's not possible to call or lock the player from metadata events
- Registering a metadata could cost some CPU cycle since it may spawn a
measurement filter to get the requested metadata. Such cost should be
explained in the comment of vlc_player_metadata_option enum.
Some player events could be moved to metadata events, like the statistics one.
And use the loudness measurement as a first use case.
The main difference between metadata listeners the player listeners are:
- The information returned by metadata events is mainly useful for the UI, it
should not be used to control the player.
- It's not possible to call or lock the player from metadata events
- Registering a metadata could cost some CPU cycle since it may spawn a
measurement filter to get the requested metadata. Such cost should be
explained in the comment of vlc_player_metadata_option enum.
Some player events could be moved to metadata events, like the statistics one.