After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 471372 - Jokosher: bin state change issue
Jokosher: bin state change issue
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
0.10.14
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-29 00:37 UTC by John Green
Modified: 2009-09-10 08:18 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Attachments
gst debug log (22.15 KB, application/x-gzip)
2007-08-29 00:40 UTC, John Green
Details

Description John Green 2007-08-29 00:37:53 UTC
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.
Comment 1 John Green 2007-08-29 00:40:51 UTC
Created attachment 94534 [details]
gst debug log

Attached gzipped debug log
Comment 2 Tim-Philipp Müller 2009-04-16 00:27:39 UTC
I hate to ask after all this time, but: is this still an issue with recent versions of things, or can we close this as OBSOLETE for the time being?