Sample problem -ACID Product Family - MAGIX Community Forums Archive

Subject:Sample problem Posted by: matter Date:6/9/2003 11:43:47 AM I have 3.0 and when I chop a sample in Cool Edit and save it as a .wav, then try to add it to a session in AP3, it plays back very poorly. The sample sounds almost like it was "timstretched", playback is almost slowed down or whatnot, kinda poppy. I've checked the properties of the sample and as well as other samples I use, and there doesn't seem to be a difference. The sample opens and plays fine in Cool Edit. This is driving me crazy!! Is there a project setting I am not aware of that I could have possibly changed?I have also noticed it has touble previewing some samples, anyone else have this problem? I have never had any problems with acid since I bought it, until now. Any help would be very appreciated. Thanks all!!
Subject:RE: Sample problem Reply by: Iacobus Date:6/9/2003 12:09:59 PM Sounds like ACID is trying to apply ACIDization to a file that doesn't have those properties. Cool Edit doesn't have the ability to add ACIDized properties to a file, does it? I know Sound Forge does. In any case, if the sample is short enough to become a Loop type track, ACID will always apply its tempo and key stretching capability to such a track. That's probably why it's important to be able to apply that info externally before you bring it into ACID. You can get around this problem in several ways. One is to change the track type to One-shot, which will never be stretched; ACID leaves that track type alone. Another is to use something like Sound Forge with its ACID loop creation tools. Still another is to use the Chopper in ACID Pro 3.0. Just chop the sample up and apply it to the timeline, and then bounce the result down. Change the file to a One-shot before working on it. ACID should take the key and tempo info for the overall project and apply it to the bounced down sample. (Be aware about keys and pitch; for instance, you could easily apply the key of D (Major) to a file that has an actual (or overall) pitch of C. That obviously wouldn't sound too good if the sample was paired with samples that were pitched correctly—unless that's your intention.) HTH, Iacobus

Subject:Sample problem

Posted by: matter

Date:6/9/2003 11:43:47 AM

I have 3.0 and when I chop a sample in Cool Edit and save it as a .wav, then try to add it to a session in AP3, it plays back very poorly. The sample sounds almost like it was "timstretched", playback is almost slowed down or whatnot, kinda poppy. I've checked the properties of the sample and as well as other samples I use, and there doesn't seem to be a difference. The sample opens and plays fine in Cool Edit. This is driving me crazy!! Is there a project setting I am not aware of that I could have possibly changed?I have also noticed it has touble previewing some samples, anyone else have this problem? I have never had any problems with acid since I bought it, until now. Any help would be very appreciated. Thanks all!!

Subject:RE: Sample problem

Reply by: Iacobus

Date:6/9/2003 12:09:59 PM

Sounds like ACID is trying to apply ACIDization to a file that doesn't have those properties. Cool Edit doesn't have the ability to add ACIDized properties to a file, does it? I know Sound Forge does.

In any case, if the sample is short enough to become a Loop type track, ACID will always apply its tempo and key stretching capability to such a track. That's probably why it's important to be able to apply that info externally before you bring it into ACID.

You can get around this problem in several ways. One is to change the track type to One-shot, which will never be stretched; ACID leaves that track type alone. Another is to use something like Sound Forge with its ACID loop creation tools.

Still another is to use the Chopper in ACID Pro 3.0. Just chop the sample up and apply it to the timeline, and then bounce the result down. Change the file to a One-shot before working on it. ACID should take the key and tempo info for the overall project and apply it to the bounced down sample. (Be aware about keys and pitch; for instance, you could easily apply the key of D (Major) to a file that has an actual (or overall) pitch of C. That obviously wouldn't sound too good if the sample was paired with samples that were pitched correctly—unless that's your intention.)

HTH,
Iacobus