Neither do I think this should be closed. I've experienced the exact
same problems but I'm getting a "Polling is already enabled on the given
drive" when issuing the hal-disable-polling command.
When starting e.g. GRIP I immediately get a listening of what's on my
audio disk inserted.
sound-juice
Why is this bug closed? Disabling polling should seem to do just that,
stop the frequent polling. I don't see why it should stop things
working when the user initiates the action; surely a one-off poll
should be done then. And the "WARNING **: Error getting media type"
diagnostic is very confus
I just had the same problem, also because of powertop. For those who
need it, here is how to re-enable polling:
sudo hal-disable-polling --device /dev/scd0 --enable-polling
--
[gutsy] sound-juicer can not see audio CD in drive
https://bugs.launchpad.net/bugs/137830
You received this bug notifica
Ripping works ok in gutsy, but what are these messages I get every time
from terminal? Are they normal?
** (sound-juicer:13300): WARNING **: Could not lock drive: Kopioidaan
musiikkia CD-levyltä
** (sound-juicer:13058): WARNING **: Could not lock drive: Kopioidaan
musiikkia CD-levyltä
** (sound-
thank you for updating the bug, that's not the right place to discuss
powertop changes though
--
[gutsy] sound-juicer can not see audio CD in drive
https://bugs.launchpad.net/bugs/137830
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for
closing.
** Changed in: sound-juicer (Ubuntu)
Status: New => Invalid
--
[gutsy] sound-juicer can not see audio CD in drive
https://bugs.launchpad.net/bugs/137830
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug contact for sound-juicer in
Fixed. My fault, I disabled hal cd polling (as suggested by powertop),
leading to completely useless CD drive. Maybe this setting should be
disabled in powertop?
--
[gutsy] sound-juicer can not see audio CD in drive
https://bugs.launchpad.net/bugs/137830
You received this bug notification because
gst-launch can correctly open the following pipeline:
[EMAIL PROTECTED]:~$ gst-launch 'cdparanoiasrc ! alsasink'
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
Pipeline is PREROLLED ...
Setting pipeline to PLAYING ...
New clock: GstAudioSinkClock
Caught interrupt -- handling interrupt.
I can confirm that cdparanoia can extract tracks from the disc (so it is
not a hardware problem). How can I test that the gstreamer plugins are
working correctly (I suspect these are the culprits)?
(disclaimer: I was the maintainer of ripperX for 2 years, I know how to
rip audio CDs)
--
[gutsy]
