|
Subject:Loop Problem
Posted by: tibby
Date:10/24/2004 11:15:19 PM
I'll take part of a track & spend forever figuring out how to slice it so that it loops perfectly. PROBLEM: About half the loops I render are fine, but half sound awful as loops. It sounds like I have somehow accidentally rendered slightly too much or too little of what I intended to. Any ideas, guys? It's weird. I doubt it's a settings issue, since I'll do a dozen at one time, for ex, and about 1/2 will not sound right at all; 1/2 will be perfect. |
|
Subject:RE: Loop Problem
Reply by: Spirit
Date:10/24/2004 11:27:23 PM
There are many methods. Those wanting to really torture themselves with technical nuances will drone on about zero crossing points. Personally I prefer to make my loops in FL Studio and export with "wrap remainder" turned on. Result = perfect Acidised loop every time. |
|
Subject:RE: Loop Problem
Reply by: JohnnyRoy
Date:10/25/2004 5:23:19 AM
What is the source of the original tracks? Are they Loops, One Shots, or Beatmapped? Are you recording them yourself? It’s hard to know why your having this problem without know more about what it is your are doing. ~jr |
|
Subject:RE: Loop Problem
Reply by: tibby
Date:10/25/2004 6:22:52 PM
From within ACID, I extract something from an audio CD as a WAVE. In ACID, I bring in the entire song as a track and usually (not always) change it to a ONE SHOT, if it's beatmapped. I work to edit a chunk which will loop perfectly. I render out -- and then discover the loops sound wrong alot of times (the precision editing I did seems to've been lost -- the sample loop is slightly longer or shorter than it should be). I try re-editing my new loop, changing it to beatmapped or loop, but it's not possible to get it to sound right. Really frustrating -- why do some work perfectly & others not? |
|
Subject:RE: Loop Problem
Reply by: Iacobus
Date:10/25/2004 7:29:12 PM
Are you using the "tools>render to new track" command or the "file>render as" command? You should be using the former. Doing so will automatically ACIDize the sample based upon tempo and key (if applicable) in your present ACID project. Using the latter just renders out the file as you hear it. There's a little more to it, but I want to find out if you make any progress first. Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page Guitars 4 Kids |
|
Subject:RE: Loop Problem
Reply by: JohnnyRoy
Date:10/25/2004 10:44:18 PM
If you get the tempo right in the Beatmapper, you will get perfect loops when you use Render to New Track as Iacobus suggests. You definitely don’t want to use One Shots and try and loop them. Beatmapping defines the tempo of the wave. This will make looping almost foolproof. ~jr |
|
Subject:Now You Tell Me *sob*
Reply by: tibby
Date:10/27/2004 5:07:03 PM
Of course, I've been using the wrong one -- the FILE, RENDER AS I'll do a new batch as TOOLS, RENDER TO & see how it works. *** What's the difference, by the way? *** Strange how some samples loop perfectly & some don't, when I use FILE, RENDER AS Thanks for your info |
|
Subject:RE: Now You Tell Me *sob*
Reply by: JohnnyRoy
Date:10/27/2004 8:14:29 PM
> Strange how some samples loop perfectly & some don't Try right-clicking on the event that you want to turn into a loop and choose Select in Chopper. Then use the chopper to get your loop correct. If it doesn’t loop right in the chopper, it isn’t going to ever loop correctly. Once you are satisfied that you have the correct loop points set in the chopper. Right-click in the chopper view and select Chop to New Track... This will prompt you for a filename and that will be your new loop. Once again, if these are Beatmapped songs you need to get your beatmapping correct first. ~jr |
|
Subject:not getting this
Reply by: tibby
Date:10/28/2004 12:09:47 AM
Can I foul up a loop (meaning a seamlessly repeatable section of audio, not an Acid "Loop") by editing it as 1 shot vs. beatmap? * * * I tend to work a little more w/ 1-SHOTS cuz beatmapper doesn't always work right for me. When I isolate a good repeatable section of track, I can get it to loop perfectly in my project (by copying & pasting, or by moving the track bars). Now, from within my project I have a perfect loop. * * * Do I have this wrong? -- A good loop starts & ends at the precisely correct point. Therefore, I can use it as BEATMAPPED or LOOP and it should sound perfect. I CAN ALSO use it as a 1 SHOT, copied & pasted, and it should sound right too. RIGHT? I'm not playing any less or more of the sample, it's not being re-edited, so if it's the identical few seconds 4 beats of 4/4, it should repeat properly in loop, beatmap or 1-shot format. Thanks for bearing with me, I really am doing my best to understand this. |
|
Subject:RE: not getting this
Reply by: Iacobus
Date:10/28/2004 1:18:44 PM
tibby: Remember that time and tempo are related as far as ACID is concerned. If ACID encounters an un-ACIDized sample, it will try its best to determine the right tempo the sample fits into. However, ACID doesn't get it right every time. It may identify a four beat loop as an eight beat loop, which would halve the tempo. That's why it's best that you do the ACIDization work yourself. When you render to a new track in ACID (using the Tools>Render to New Track command), ACID automatically ACIDizes the sample based on its length. (*See below.) If a newly rendered track becomes a Loop, for example, tempo and key info (if applicable) of the ACID project is embedded within the newly rendered track. If you bounce down (render to a new track) a four beat sample in an ACID project that's 120 BPM in the key of G, the bounced down track will be ACIDized at 120 BPM with a root note of G as well. The One-shot track type is the only ACIDized track type that ACID does not timestretch, giving One-shots a "what you hear is what you get" approach similar to multitracking apps. You may be hitting a perfect combo if One-shots seem to loop perfectly for you. For example, a One-shot that has four beats and is exactly two seconds long will fit perfectly within a tempo of 120 BPM. Usually, what I do to make loops is record my project at the intended tempo as a One-shot, then take a part of that One-shot and bounce down to ACIDize that part of the recording properly as a loop. In your case, it sounds like you need to find out what tempo best fits your samples. There's a simple formula you can use: 240 / (length of sample in seconds) = (tempo sample best fits into) Note this formula works only for a four beat sample. If you have an eight beat sample, just take half of that sample's length. *A bounced down track will become a Loop, Beatmapped or One-shot track depending on its length in time. By default, anything shorter than a half a second turns into a One-shot, anything between half a second to 30 seconds becomes a Loop, and anything longer than 30 seconds becomes a Beatmapped track. Finally, when you use the File>Render As command, ACID simply renders out the project's tracks as it was heard during playback. This is the ideal function to use if you plan on doing other tasks such as mastering a final mix, rendering a media file for the Internet or using the render in other apps like a multitracker. It does not ACIDize the render. HTH, Iacobus ------- RodelWorks - Original Music for the Unafraid mD's ACIDplanet Page Guitars 4 Kids ***(ACID Pro 5.0! Woohoo!)*** |
|
Subject:RE: not getting this
Reply by: JohnnyRoy
Date:10/28/2004 1:32:34 PM
I’m not saying that you have to use the beatmapper. It’s just easier if you are going to chop the song up a lot because the tempo is already mapped. If you’re going to use a one shot, then: 1. Open the one shot in the Chopper 2. Listen to from before the part you want to loop 3. While it’s playing, press the ‘M’ key to mark the downbeat of the start of the loop 4. Continue listening and press the ‘M’ key again to mark the downbeat of the next measure 5. Double-click between the markers to select the area as a loop 6. Listen to the loop in the chopper to make sure it loops smoothly 7. If not, zoom in and adjust the in and out points until it loops smoothly 8. Use Chop to New Track... to create the permanent loop This should give you the results you are looking for. ~jr |