On Wed, 13.02.08 22:49, Lennart Poettering (mzerqung@xxxxxxxxxxx) wrote: > > On Wed, 2008-02-13 at 22:10 +0100, Lennart Poettering wrote: > > > PA provides the necessary information. It's just that Gst doesn't and > > > thus simply blocks waiting until it can write to the audio device the > > > next time, freezing the UI. > > > > Lennart, > > as PA has rerouting capabilities already, couldn't you simply reroute > > sound to /dev/null (and mic from /dev/null) ? > > > > This would prevent most older applications from crashing I guess. > > I don't see why apps should "crash" due to this. They might freeze and > then unfreeze again. But "crash"? No, hopefully not. If they are this > fragile than they should be fixed, instead of adding non-trivial > workarounds to PA. Don't forget that C-z is very similar to this kind > of freezing. If an app can't survive C-z than it needs fixing anyway I > would say. Oh, and let's not forget that I believe the expected user behaviour is music to stop and resume on session switch -- not muting. I mean, the information about this suspending is forwarded to the application by PA. However, the gst plugin isn't able to make any good use of that information, because afaik downstream elements are not supposed to change the state of the pipeline. Maybe some Gst guru can look into this and tell me what I should be doing with those events in Gst? Lennart -- Lennart Poettering Red Hat, Inc. lennart [at] poettering [dot] net ICQ# 11060553 http://0pointer.net/lennart/ GnuPG 0x1A015CC4 -- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
