Trouble Ripping CDs Made with SF/CDA -Sound Forge - PC

Subject:Trouble Ripping CDs Made with SF/CDA Posted by: Brooke Date:1/22/2009 1:41:40 AM I've been getting complaints from people having difficulty ripping .mp3 files from CDs I've mastered in SF9.0e with CDA5.2d (DOA, Redbook compatible, 16/44.1, burned at 16x on a Sony DW-Q120a with Taiyo Yuden 52x Inkjet Printable media). The CDs play fine, but I had the same problem ripping these back on the source machine using M$ Media Center, so I had to go back and burn and mail separate .mp3s for them. My primary editing machine was stolen when my editing suite was robbed a couple months ago (over $10,000 of uninsured equipment, along with most of my work, except for a year old backup), but it only had SF8 with Win2k, which worked flawlessly. Could I have missed changing a preset to allow copying on this system, or done something equally stupid that I'm overlooking? I'm not sure if the problem is in one of these programs or the latest M$ updates everyone is using, but I'd appreciate any insight.
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: jackn2mpu Date:1/22/2009 4:59:53 AM Did you by any chance set the protect/non-copy option in CDA? Jack
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: musicvid10 Date:1/22/2009 7:03:02 PM "having difficulty ripping .mp3 files from CDs" Does your CD contain .mp3 files or .cda files? Message last edited on1/22/2009 7:05:30 PM bymusicvid10.
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: drbam Date:1/23/2009 8:05:12 AM "Does your CD contain .mp3 files or .cda files?" Or are they audio CDs? Your description is not really clear. The term ripping usually refers extracting audio from a standard audio CD. If they are other types of files (mp3, etc), the term I would use would be "copying" the file to other media.
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: Chienworks Date:1/23/2009 10:49:30 AM Sound Forge and CDA aren't capable of burning anything other than Audio CDs.
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: Brooke Date:1/23/2009 9:44:01 PM "Did you by any chance set the protect/non-copy option in CDA?" Jack, That was the stupid mistake I was looking for! I looked for a protect enable switch in General Preferences, and thought I was covered when I didn't see it there. I didn't realize 5.2 defaulted to protect, and had to be turned off in track view because I was apparently working from my old preferences until I loaded CDA onto this new computer (without my old file preferences as a default). I just thought it would be more conspicuous than this, and I didn't see it in the midst of working back to back 140 hour weeks, trying to make up for my losses. Thanks so much for your help! By the way, am I missing an easy way to turn off protect in the preferences somewhere? Oh, and like Cheinworks clarified, I was talking about "ripping" standard near-Redbook audio CDs, that my people were trying to convert to .mp3s on their own computers. Message last edited on1/23/2009 9:51:05 PM byBrooke.
Subject:RE: Trouble Ripping CDs Made with SF/CDA Reply by: musicvid10 Date:1/24/2009 7:12:27 AM Glad you fixed the problem, and thanks for clarifying your original post!

Subject:Trouble Ripping CDs Made with SF/CDA

Posted by: Brooke

Date:1/22/2009 1:41:40 AM

I've been getting complaints from people having difficulty ripping .mp3 files from CDs I've mastered in SF9.0e with CDA5.2d (DOA, Redbook compatible, 16/44.1, burned at 16x on a Sony DW-Q120a with Taiyo Yuden 52x Inkjet Printable media). The CDs play fine, but I had the same problem ripping these back on the source machine using M$ Media Center, so I had to go back and burn and mail separate .mp3s for them.

My primary editing machine was stolen when my editing suite was robbed a couple months ago (over $10,000 of uninsured equipment, along with most of my work, except for a year old backup), but it only had SF8 with Win2k, which worked flawlessly. Could I have missed changing a preset to allow copying on this system, or done something equally stupid that I'm overlooking? I'm not sure if the problem is in one of these programs or the latest M$ updates everyone is using, but I'd appreciate any insight.