I'm still working on a few bugs, but I thought I'd share some screen
shots. These demonstrate a small amount of layout improvement in gnome-volume-control through the use of no more than a single mixer flag, along with more generousity/flexibility in how g-v-c handles mixer tracks. The only "interface" change in gstreamer was addition of a new flag, GST_MIXER_NO_RECORD, which indicates that the mixer should not have a "record" control associated with it. I anticipate being able to use this to eliminate some ofthe private #ifdef sun hacks that are in Sun's copy of the code as well. Note that in the screenshots, the "beep" slider is associated with the pc beeper, and isn't a normal output track. (It can easily be moved to the 'playback' tab if we believe that's a better location for it. Right now I like it where it is because it shows that the "Switches/Options" tab lays out sliders differently than the Playback and Record options. For the curious, these snapshots were taken on OpenSolaris with the Boomer code base... the system is an Ultra 20 using an AC'97 controller with an ALC655 codec. What I'd like to know, and still haven't heard back, is how receptive are the gstreamer maintainers likely to be in the face of changes to accommodate stuff like this. (I've tried my best to make the changes vendor/platform neutral, so they should be useful for stock OSS installations as well.) -- Garrett ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
On Tue, Feb 3, 2009 at 1:03 AM, Garrett D'Amore <[hidden email]> wrote:
> > What I'd like to know, and still haven't heard back, is how receptive are > the gstreamer maintainers likely to be in the face of changes to accommodate > stuff like this. (I've tried my best to make the changes vendor/platform > neutral, so they should be useful for stock OSS installations as well.) Garrett, I haven't been following the discussion about mixer stuff much. However, general policy: API additions that make sense (I assume yours do; I haven't checked) are fine, so long as existing code continues to work (i.e. you can't change existing semantics, API, or ABI). Filing a bug with your suggested changes to the mixer interfaces, along with a detailed description of why, is probably the best way to make forward progress with this stuff. Mike ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.sourceforge.net/lists/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |