...
Architecture Diagram to start with:
session manager able to configure dsp?
one client per each ALSA device in case of hardware mixing
open/ proprietary networkmanager separate!
...
Gateway/Portal handling ressource/ACL management. Returning ressource URI (socket or network endpoint) ?
George: original idea is to create and configure the pipewire socket; more discussion needed
Potentially desired mechanism for content protection:
1) client connects using (no / invalid) token
...
- In a car we have (proprietary) network managers. The pipewire session manager needs to communicate with these and provide an API.
- Similar for copy protection mechanisms.
- Thus session manager cannot (shouldn't try) to abstract all of these.
- System management might be on external hardware
- Security provided by a gateway/portal that handles ressource managment and authoriztion.
- Need to take HDCP/content protection in mind (e.g. videvinewidevine)
TODO: Session Manager first.
...
- static and/or default config vs dynamic configuration at runtime
- handle device removal
- graph inplemented in HW level
- kernel-based security
- content protection
- role of the gateway
- external authority ?
nodes appearing inside pipewire, representing the devices and the clients
client connected to alsa device through DSP and using a filter plugin in the middle
gateway in session manager ?
hardware device graph, somewhere else in the car
wireplumber internal design