[gstreamer-bugs] [Bug 471372] New: Jokosher fails to record

[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=471372

  GStreamer | don't know | Ver: 0.10.14
           Summary: Jokosher fails to record
           Product: GStreamer
           Version: 0.10.14
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: don't know
        AssignedTo: gstreamer-bugs at lists.sourceforge.net
        ReportedBy: john at thegreens.co.uk
         QAContact: gstreamer-bugs at lists.sourceforge.net
     GNOME version: 2.17/2.18
   GNOME milestone: Unspecified


Please describe the problem:
After building the latest release of gstreamer (0.10.14) on Ubuntu Feisty,
jokosher no longer records. I have no problem recording with the version of
gstreamer that ships with feisty (0.10.12). I get the same results with both
jokosher 0.9 and the latest svn.

This same problem also occurs in Ubuntu Gutsy which installs with gstreamer
0.10.14.

Steps to reproduce:
1. Load jokosher
2. Create a new project
3. Add an instrument
4. Press record
5. After a few seconds press stop


Actual results:
A tiny white box appears in the instrument lane with no waveforms and the red
line  doesn't progress. When the stop button is pressed an error message is
presented saying:

Error loading file: None

Please make sure the file exists, and the appropriate plugin is installed.

Could not determine type of stream.

gsttypefindelement.c(735): gst_type_find_element_activate ():
/pipeline0/decodebin1/typefind


Expected results:
Waveforms should appear and the red line should start moving. When stop is
recording should stop without an error.

Does this happen every time?
Yes

Other information:
The recordingbin should be writing to a file. When stop is pressed then that
file is read back. However recordingbin never actually gets out of PAUSED state
and so the file remains empty which explains the error reported when stop is
pressed. That's by the by. The bug here is the failure of the recordingbin to
change to PLAYING.


-- 
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=471372.