Skip to main content

importing into Sonar 2.2XL

Submitted by anonymous on Thu, 07/31/2003 - 17:16

Ive been using FL Studio to create beats for my songs and importing them into songs in Sonar 2.2XL. But after importing a few waves, Sonar will start to speed up the wave while importing. if I try the same beat in mp3 format instead it will import at the right tempo but will add loud "pops". I tried playing the same files in winamp with no problems. they were the right tempo and had no pops, so it has something to do with sonar. does anyone know the cause or solution? or has had experiance with this in other DAW's?

Tags

Comments

anonymous

no, theres no pitch change. and it seems it doesnt always work on the first import.
it seems to speed up at the end of the imported file. if its small than it will get real fast real quick, but if I pourposly make it 15x the sizt it should be then slice it down to size the beats match up. it a pain in the ass, I have to go beat by beat instead of just bringing in all the drums at once.

Sat, 08/23/2003 - 14:02 Permalink
anonymous

A tip: When creating your loops remember that cutting the loop will do just that. It will cut the sound at the end of the beat(i.e. any cymbol crash/splashes, effects trails, etc.). Wrapping them will take the remaining sound(past the beat) and "wrap" it around to the begining of the loop. I will often create 2 loops. The first, which is cut, will begin the song(usually 1 repetition). This way it won't start out with an unwanted splash or trail. The second, which is wrapped, will be used for the rest of the song. Because the second loop is wrapped, it will sound as if a slash or effect trail is carried into the next rep of the loop. HTH and G'luck. :D

Tue, 08/26/2003 - 20:24 Permalink
falkon2

Opus and friends: (Hey whaddya know, I'm beginning to talk like Alecio :D )

Originally posted by Trendkill:
But after importing a few waves, sonar will start to speed up the wave while importing.

Hence his original attempt to use MP3.

I've never had that speeding up problem while importing. However, sometimes SONAR has gone completely bonkers an played everything back at like 4x speed everytime I hit play, and the only way to fix is a reboot. I suspect it's a driver conflict/problem at work in my case.

The file lengths and such are correct, though. It's just playback that's screwed.

Wed, 08/27/2003 - 07:37 Permalink
anonymous

Hi All,

As Blutone has said "A picture is worth a thousand words"

And what I see in the picture above is that Trendkill is saving his file as an "Acidized" file. In doing so, When that file is imported into SONAR it will stretch or shrink to match the current project tempo. So if the loop was created in FL at say 80bpm and then saved with the parameters in the picture above, then imported into SONAR and the current SONAR project tempo is say 100bpm then yes that loop will stretch to match the current project tempo which is 100bpm and sound faster. So from what I see, the key here is either to not save the file as an "Acidized" file or make sure that the SONAR Project that you're importing to is set at the same tempo as your newly saved "Acidized" file.

Damn.....I just noticed the dates of these posts. I sure hope you haven't been going this long without a solution to your plight. And if you have...I hope this post helps.

JHC :p:

Fri, 10/03/2003 - 22:38 Permalink