>> If you want something quick-and-dirty, with all the AV-sync issues >> inherent in your custom protocol due to lack of timestamps or other >> latency indicators on the wire, and can wait until June 6, I can help >> you add ESD protocol support in XRDP. This way, not a single line of >> PulseAudio source code would need to be changed. >> > > I have to correct myself. The ESD protocol does have server-internal latency > reported. It doesn't report latency between the server and the client, but > in our case it is determined solely by the amount of buffered data in the > socket buffers, which PulseAudio already knows. > > So, it only remains to add support for three protocol elements (auth, > playing stream, reporting latency) inside xrdp, which should be easy, as you > have already done 80% of the work by implementing your custom protocol. I really want something that is clean, efficient and optimal in design. The source and sink for xrdp now really really work well. They also look good. You can run pavucontrol and see that, yes, the xrdp sink is running. I don't want a TCP or UDP connection for each session or a confusing sink or source name. There can be xrdp servers with 50 users. That's 50 pulseaudio daemon on one machine. I'll take your advise but I hope you can understand my requirements. I already tied so many recommendations(from pa) that just didn't cut it. One thing that I really think you guys should do is allow out of tree modules build support. We would not need this discussion if you had a clean and stable API like so many other projects. Jay
