[gstreamer-bugs] [Bug 574509] New: list_tracks causes assertion with pulsemixer, but not with alsamixer

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=574509

  GStreamer | gst-python | Ver: 0.10.14
           Summary: list_tracks causes assertion with pulsemixer, but not
                    with alsamixer
           Product: GStreamer
           Version: 0.10.14
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: gst-python
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: mblaesing at doppel-helix.eu
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: Unspecified
   GNOME milestone: Unspecified


Hey,

I tried the pulsemixer and got a failure. When invoking list_tracks, I didn't
get a tracklist as I would have expected.

This script:

#!/usr/bin/python
import gst

alsa = gst.element_factory_make('alsamixer')
alsa.probe_property_name('device')
alsa.device = alsa.probe_get_values_name("device")[0]
alsa.set_state(gst.STATE_PLAYING)
print alsa.list_tracks()
alsa.set_state(gst.STATE_NULL)

pulse = gst.element_factory_make('pulsemixer')
pulse.probe_property_name('device')
devices = pulse.probe_get_values_name('device')
pulse.device = devices[0]
pulse.set_state(gst.STATE_PLAYING)
print pulse.list_tracks()
pulse.set_state(gst.STATE_NULL)

Resulted in this:

mblaesing at enterprise:~$ python test4.py 
[<__main__.GstAlsaMixerTrack object at 0xa0c093c (GstAlsaMixerTrack at
0xa40d000)>, <__main__.GstAlsaMixerTrack object at 0xa0c0964 (GstAlsaMixerTrack
at 0xa40d0b8)>]

** (test4.py:2452): CRITICAL **: _wrap_gst_mixer_list_tracks: assertion
`GST_IS_MIXER (self->obj)' failed
[]
mblaesing at enterprise:~$ 

My assumtions would have been to get a list like in the alsa case.

I had a look at gnome-volume-control. This seems to use gstreamer for volume
control (at least I interpret that from the ldd output). There the pulse
devices are visible and showing the volume tracks. This led me to the
conclusion that the problem lies probably somewhere in the python bindings.

If you need more info - just ask - I run this test on debian SID and Ubuntu
Jaunty.

Thanks in advance

Matthias Bläsing


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=574509.