Date: Tue, 01 Apr 2008 20:02:22 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Scott Nicholson <atomicplayboy@socal.rr.com> Cc: freebsd-gnome@freebsd.org Subject: Re: Sound Juicer and audio CD problems after 2.22 Message-ID: <1207094542.23098.8.camel@shumai.marcuscom.com> In-Reply-To: <4AFF647E-E70D-4FD7-B0C3-5673B28DA2AC@socal.rr.com> References: <8F1DD519-309C-4DCA-AEEE-FFC417EFA11F@socal.rr.com> <1207030407.38611.26.camel@shumai.marcuscom.com> <4AFF647E-E70D-4FD7-B0C3-5673B28DA2AC@socal.rr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-Fto7UHCgFt6/Tr3Ke5Ar Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2008-04-01 at 15:19 -0700, Scott Nicholson wrote: >=20 > I went through the HAL FAQ before I came here. Great info, by the way. =20 > I created a new account on my system and tried reproducing the =20 > problem. It worked without flaw. Turns out that, by default, it uses a =20 > blank value in the 'device' string under gconf. Put that under my own =20 > user profile and, success. Would it be wise to remove my current gconf =20 > profile and start from scratch, or should it not matter that much? Any =20 > other configuration info that might be stale from previous versions? =20 > I've been using gnome on this machine for some time. I only had a problem with accessibility after the 2.22 upgrade, so you may not see other problems. On the other hand, mezz starts from scratch after each release. >=20 > Not satisfied with mere success, I tried to figure out what went =20 > wrong. After some tinkering, I discovered that my original problem was =20 > likely caused by changing which CD device I was trying to rip with. I =20 > have two and, I believe, I was attempting to get a cleaner rip on a =20 > scratched CD by trying the other. Doing so caused the 'device' string =20 > in gconf to become the scsi address. It looks like, when the default =20 > device is changed, breakage occurs. Both devices work by passing the '-=20 > d /dev/cdX' flag at the command prompt. I suppose I can just avoid =20 > using the alternate device for now, but it seems like a possible bug? =20 > Has anyone had success in changing the default device in sound juicer? What options do you see in sound-juicer for CD devices? s-j uses nautilus-cd-burner to get its drive info, but the SCSI address path should noly be used by apps that need to call cdrecord. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-Fto7UHCgFt6/Tr3Ke5Ar Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkfyzQ4ACgkQb2iPiv4Uz4f0ewCeMNzj1oGKKwnWRFTZlalxOW55 3xkAnRlcgGe/DHiri9Zh+UK7efktEfPR =1Cey -----END PGP SIGNATURE----- --=-Fto7UHCgFt6/Tr3Ke5Ar--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1207094542.23098.8.camel>