FFe justification:
Probably one of the most popular questions I see new users ask about gnomeradio is along the lines of the following:
"It looks like gnomeradio is working (showing me gui), but for some reason I am not hearing any audio. What is wrong with my tuner?"
Unfortunately, in the vast majority of cases, there is nothing wrong with the tuner. The problem is that gnomeradio was originally designed to be used with older tuner cards that have a dedicated audio output cable, which you are expected to connect to speakers. Most newer tuner products deliver their audio via an ALSA device, for which gnomeradio has no mechanism to route the audio to soundcard.
As a result, users end to run sox or arecord/aplay in a separate terminal window (which always seemed like a rather ridiculous workaround).
One of this ridiculous workaround example : https://bugs.launchpad.net/ubuntu/+source/gnomeradio/+bug/613809/comments/21
original description:
Gnomeradio seems to use the old OSS interface we have obsoleted in raring.
I can't get Gnomeradio to output audio. I accesed the soundcard config with "alsamixer -c0" and turned the line-in all the way up. But i still can't get audio from my Gnomeradio.
Gnomeradio needs to be ported to ALSA.
The contents of my /proc/asound/pcm is:
00-00: Intel ICH : Intel ICH5 : playback 1 : capture 1
00-01: Intel ICH - MIC ADC : Intel ICH5 - MIC ADC : capture 1
00-02: Intel ICH - MIC2 ADC : Intel ICH5 - MIC2 ADC : capture 1
00-03: Intel ICH - ADC2 : Intel ICH5 - ADC2 : capture 1
00-04: Intel ICH - IEC958 : Intel ICH5 - IEC958 : playback 1
02-00: Bt87x Digital : Bt87x Digital : capture 1
02-01: Bt87x Analog : Bt87x Analog : capture 1
Bt87x Digital/Analog i think are there cause of my TVcard but they never seemed to do anything.
The card shipped with a loop cable to connect the card to the line-in and dind't mention it beeing possible another way.
And i did go to the alsamixer -c0 and turned line-in all the way up and still didn't get any audio.
But if there's a way to use my tvcard directly, would of course bee even better than that halfe baked line-in solution.
Status changed to 'Confirmed' because the bug affects multiple users.