|
Subject:Hideous Audible Clicks on Samples.
Posted by: flowbee
Date:8/21/2004 3:01:11 AM
Okay, I spend AGES trimming a WAV sample so it will Loop perfectly. I render it. Then I open a project & bring the sample in as a ONE-SHOT. Now I copy & paste the 1-shot over & over. SOMETIMES it will play seamlessly, but about 1/2 the time I get obnoxious audible CLICKS at the end of the sample, right before it repeats. -- Why's it happen, how can I stop it, why's it happen sometimes and not others...? * * *ALSO: All my samples default in as BEATMAP & I have to go thru each one & change to ONE-SHOT. Is there a way to re-default so they come in as ONE-SHOTs? Thanks to anyone who can offer info on this. |
|
Subject:RE: Hideous Audible Clicks on Samples.
Reply by: MyST
Date:8/21/2004 4:23:51 AM
"Okay, I spend AGES trimming a WAV sample so it will Loop perfectly. I render it. Then I open a project & bring the sample in as a ONE-SHOT." Why would you do this? If you spent AGES making a perfect loop, then why wouldn't you use it as a loop? Try this... Bring in your sample, except set it's properties to LOOP instead of ONE-SHOT. Right clic on the track icon that has the track number on it. Select PROPERTIES. Under TRACK TYPE, select LOOP instead of one-shot. One-shots aren't meant to loop. They're used primarily for things like explosions, cymbal hits, doors closing, stuff like that. 2nd part... OPTIONS>PROPERTIES>AUDIO Open files as loops if between(seconds) What is yours set to? Mine is set to 0,5 to 30,0. You don't want your samples to default as One-shots. Ideally they should default as loops. Mario |
|
Subject:RE: Hideous Audible Clicks on Samples.
Reply by: Iacobus
Date:8/21/2004 10:55:02 AM
Adding to what MyST said, One-shots are the only ACIDized form of track that is not timestretched by ACID. What you hear is what you get no matter what the tempo. Not sure what's causing the clicking to occur. Might want to check the quick fade edges by zooming in. Try adjusting your soundcard's latency or updating your video drivers if newer drivers are available. (Try other troubleshooting steps like reducing video acceleration as well.) Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page Guitars 4 Kids |
|
Subject:loops/beatmaps vs. 1-shots
Reply by: flowbee
Date:8/22/2004 3:24:06 AM
Hey guys, I really must not be getting this. -- This is why I tend to prefer 1-shots over loops / beatmaps at least as a default to begin with. Please explain to me what's wrong with this thinking, or what I don't understand about Acid. 1) I figure I can always change a sample to loop / beatmap if the need arises. 2) All my loops / beatmaps get assigned BPM tempo information. This means that if I'm trying to preview a sample at 94.873 in a project that has a BPM of 120, I'm stuck with it sounding off-tempo during preview. I can only fix this by changing the BPM of my current project to the tempo of each sample I want to preview -- or saving the sample as a 1-shot. 3) I edit what sounds good as a repeated 1-shot, but if I bring it in as a beatmap / loop, it ends up re-edited somehow, and I lose part of the sample. This sounds terrible. (Not all my samples start on the precise first downbeat of a measure of 4/4; it may start a little after the 2nd beat let's say, maybe this is the reason.) A repeated 1-shot sounds beautiful if I've edited it properly, & cut & paste it, but a loop / beatmap slices that sample for some reason, usually at the end. I can "rescue" the sample by erasing it, configuring the sample as a 1-shot, & bringing it back in as a 1-shot. 4) I have a sample I like. As a loop / beatmap, it's BPM is 94.873. So, when I bring it into a project, it sounds off-tempo unless I change my project tempo to 94.873, or bring it in as a 1-shot. I don't always set up the tempo for every project I work on right off, choosing to experiment a little first. (& even If I HAVE set a tempo, I'd rather hear an accurate 1-shot, not all sped up or slowed down, because I may want to bring in a section of the sample in edited bits as repeating 1-shots: for ex, a small series of sliced, repeating sax blasts before a drum beat. I don't want to hear "Chipmunks" saxophone, and I may be stuck with that if Acid saves the sample as a loop) - - - Also: Is there a DOWNSIDE to working with a 1-shot that I have cut & pasted? -- outside of losing the time-stretching thing. |
|
Subject:RE: loops/beatmaps vs. 1-shots
Reply by: Iacobus
Date:8/22/2004 9:47:59 AM
1) Nothing wrong with that. Only the app used can read the ACIDized info and playback accordingly. An app like Sound Forge can read the ACIDized info but does not timestretch on the fly like ACID does. 2) Nothing wrong with this either, depending on your needs. Sometimes, you may get something you like out of a Loop or Beatmapped track. Note how I said before, however, that with One-shots, what you hear is what you get and will not change tempo or key should you change the overall project's tempo or key. 3) You could actually render the One-shot sample as a Loop (or Beatmapped) by soloing the track, setting the Loop Region over the arranged sample and using CTRL+M with the "render loop region only" option checked. Depending on different factors (I can explain if needed), your perfectly-arranged One-shot sample should turn into a perfectly-arranged Loop. Note that when you render to a new track, the newly rendered track takes on the project's tempo and key. Be careful when bouncing percussion tracks down. More than likely you don't want to assign key info to such tracks. Make sure that if you render to a new track, solo the track (or tracks) and get the track to be at least near unity (0.0 dB) before bouncing. Worry about mixing the newly rendered track with the rest of your mix afterward. 4) If this is the way you work, I'd keep any custom material as a One-shot so that you can decide what to do with it. Remember that ACID only guessitmates what an un-ACIDized sample is; just because ACID says your sample is 94.873 doesn't mean it could be that tempo. It's probably worth nothing you should have a good idea what your sample fits into as far as tempo goes. For example, a typical 4/4 measure of audio that's two seconds long will fit exactly within a tempo of 120.000 BPM. Two measures of the same would also fit within a tempo of 120.000 BPM but would be four seconds long. (We're merely doubling the amount of measures and therefore the time; it's all relative.) ACID is usually pretty good at identifying the right tempo, but not always. You may intend a sample to be 24 beats long, but ACID would identify it as 32 beats, therefore throwing off the intended tempo. This might be because ACID is looking to "balance out" the measures. 32 beats would evenly be arranged into 8 measures, which would feel more "complete" musically than 24 beats (or 6 measures). - - - There is no downside to what you're doing. My workflow follows a very similar pattern. For example, I always record a take as a One-shot so I hear exactly as I played. Later on, I'll bounce my takes down into one Loop. Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page Guitars 4 Kids |
|
Subject:RE: loops/beatmaps vs. 1-shots
Reply by: Snappy
Date:9/18/2004 6:42:40 PM
I often find that files with lower than CD-quality sampling rate or bitrate (i.e. <44.1KHz, <16-Bit) play with unexpected results in Acid. Check this? |