Red Hat Bugzilla – Bug 197059
"Could not link pipeline" error with WAV output
Last modified: 2007-11-30 17:11:36 EST
Description of problem:
With the output setting set to 'Voice, lossless (WAV)', I can't extract any CD
tracks. I get this error:
Sound Juicer could not extract this CD.
Reason: Could not link pipeline
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Select 'Voice, lossless (WAV)' for the output setting
2. Try to extract an audio track
Selecting 'CD quality, lossless (FLAC)' works fine (but I wanted WAV files..).
Same problem here. Is someone working on it?
Almost surely this upstream bug--
Scroll down a bit. Also note the link to a Ubuntu bug:
"Ubuntu https://launchpad.net/distros/ubuntu/+source/sound-juicer/+bug/38428 is
about that too:
"Using dapper, Notebook Panasonic Cf-Y4 (sound : intel ICH6)
Trying ripping CD, the following error is displayed.
Sound Juicer could not extract this CD
Reason: Failed to link pipeline.
This problem happens only if I select wav in the preferences,
Ogg and Flac seem working.
Strangely works if launch
select wav item
audio/x-raw-int,rate=22050,channels=1 ! wavenc name=enc
audio/x-raw-int,rate=44100,channels=1 ! wavenc name=enc"
Should be fixed upstream as of 2.16.1, which is in Rawhide but not FC6 yet.
There's a patch in the upstream bug.
Note that the default "lossless WAV" profile is technically mono 22khz audio,
not lossless CD quality stereo 44.1khz audio.
Created attachment 139378 [details]
Fixes extraction to default WAV profile (already in 2.16.1)
So if you want lossless CD quality WAVs (instead of voice quality WAVs), you'll
need to edit the audio profile or create a new one.
Anyway, it's not working because the default profile wants 22kHz samples, so
sound-juicer needs to add resampling to the pipeline in order to get it to work.
I'll attach the patch which is in 2.16.1 that fixes it, but the real answer is
to simply upgrade to 2.16.1 like in RawHide.
Reassigning to email@example.com since (as far as I can tell), he's the one
that actually seems to own the component and make updates to the package.
The problem was fixed in sound-juicer 2.16.1 upstream, which is older than the
current version in FC6, or rawhide.
Closing as a stable release has the fix already.