> Thanks, I had a look. Is this a correct understanding: > > - the xrdp server will call something like "pacmd load-module > module-xrdp-sink format=x rate=y" and thereby sets up the connection between > PulseAudio and xrdp. Yup, well, I was editing the default.pa file but that looks like a better way to set the sink :) > - the xrdp sink just talks to the xrdp server over the unix socket. It's > the xrdp server that then combines this with video/display output and sends > to the client. Exactly. >>> Third, we talk about an xrdp sink, will there also be an xrdp source, or >>> is >>> this not needed, for what reason? >> >> >> Yes, we need a source too. Again, no dependency. Just a domain socket >> API. >> >> If you don't want to label it xrdp, it could be a generic unix domain >> socket sink / source. >> Maybe other remote desktop projects can use it. > > > In short, I don't mind this code going in (after a more detailed review, > perhaps). I however suspect that we're going to get bug report about missing > A/V synchronisation quite soon, and then we should tell people that this > needs to be resolved in xrdp rather than PA. Does that seem reasonable? Absolutely. I don't think any of xrdp users will blame PA for AV synchronization but maybe. Jay
