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 471154 - [alsasrc] set_hwparams problem
[alsasrc] set_hwparams problem
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-base
0.10.13
Other All
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-08-28 14:49 UTC by EMoShunz
Modified: 2011-08-11 12:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
debug log jokosher (678.30 KB, text/plain)
2008-01-08 02:32 UTC, Joel Robinson
Details

Description EMoShunz 2007-08-28 14:49:22 UTC
Please describe the problem:
The following errors popup:
Argh! Something went wrong and a serious error occurred:

Internal GStreamer error: clock problem. Please file a bug at http://bugzilla.gnome.org/enter_bug.cgi?product=GStreamer .

gstpipeline.c(568): gst_pipeline_change_state (): /timeline:
Pipeline cannot operate with selected clock

It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/

-------------------------------------------

Argh! Something went wrong and a serious error occurred:

Could not get/set settings from/on resource.

gstalsasrc.c(649): gst_alsasrc_prepare (): /timeline/bin3/alsasrc1:
Setting of hwparams failed: Invalid argument

It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/

----------------------------------------------------

Argh! Something went wrong and a serious error occurred:

Could not get/set settings from/on resource.

gstalsasrc.c(428): set_hwparams (): /timeline/bin3/alsasrc1:
Rate doesn't match (requested 44100Hz, get 0Hz)

It is recommended that you report this to the Jokosher developers or get help at http://www.jokosher.org/forums/

------------------------------------------------

Error loading file: None

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

Could not determine type of stream.

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

------------------------------- 

Steps to reproduce:
1. Kubuntu 7.04
2. Jokosher 0.9
3. Press record, happens every time.


Actual results:
The above errors happen every time.

Expected results:
That the program would start to record

Does this happen every time?
Yes

Other information:
If I use the program in Dreamlinux 2.2, the issue does not occur.
Comment 1 EMoShunz 2007-08-28 17:46:14 UTC
Kubuntu 7.04. AMD 3000+. DFI Lanparty NForce4. 80GB SATA HDD. nVidia 6200. Pioneer 109D Burner. HP LiteScribe Burner. On Board Sound.
Comment 2 Tim-Philipp Müller 2007-09-23 10:47:02 UTC
The clock problem is bug #453650 and is fixed in CVS, I think. The 'could not determine type of file' problem is due to nothing being recorded and the file being empty (this is a jokosher bug when handling error messages, I think; it should only show the first error on the GStreamer bus and drop all others).


The set_hwparams failures I have seen before, but couldn't do anything about it because we didn't have a debug log.

Could you run the following in a terminal such as gnome-terminal or konsole or xterm please (the '$' is the shell prompt, don't type that):

 $ GST_DEBUG=*alsa*:5  jokosher  2>dbg.log


and then attach the dbg.log file to this bug report?

Comment 3 Tim-Philipp Müller 2007-09-23 16:19:26 UTC
bug #471154 is similar, but for alsasink instead of alsasrc.

Comment 4 Joel Robinson 2008-01-08 02:32:54 UTC
Created attachment 102362 [details]
debug log jokosher
Comment 5 Tobias Mueller 2009-01-23 23:38:07 UTC
Reopening as the log requested in comment #2 has been provided in comment #4.
Comment 6 Sebastian Dröge (slomo) 2011-05-18 20:35:59 UTC
Is this still a problem with the latest versions of everything?
Comment 7 Fabio Durán Verdugo 2011-06-28 23:41:57 UTC
EMoShunz, Joel the bug still exists?, can reply the comment 6 ?
Comment 8 Akhil Laddha 2011-08-11 12:48:07 UTC
Please feel free to reopen this bug if the problem still occurs with a newer version of GStreamer Core 0.10.35, Base Plugins 0.10.35, Good Plugins 0.10.30 stable release, tia.