dead space at beginning of bounce

[xl999]

Hey guys,

I'm sure this has been answered before but I can't seem to find it on the forum.

When bouncing to an audiofile, there seems to be a piece of dead space at the very beginning that is bounced along with it. when I look at the result (after importing the bounce into the session) there is approx. 0.020 secs of nothing.
When bouncing regions that ought to be looped, this obviously is a problem.

Also, when pressing play, I can see the cursor start right before the insert point (a few ms). Pre- and post-roll is off, so that can't be it. Any ideas?
I can't seem to find anything about this in the manual or preferences. Help is greatly appreciated.

regards,

XL

[caruso7r]

Highlight one of the regions in the song exactly where you want it to start and end. Question, when you start bouncing do you hear a slight delay in audio?

[xl999]

Yeah, I know I should highlight the exact region i want bounced, and I do.

The problem is that I get an unwanted bit of space at the beginning when looking at the bounced file.

And yes, there is a very very slight delay between pressing space and hearing audio.
As said above, I can actually see the cursor beginning before the highlighted region (and yes, preroll is off ;-))

[caruso7r]

Sounds like you're in grid mode. Make sure you're not and I know this is basic stuff but make sure you're also in slip mode.

[xl999]

no man, its nothing like that.

I'm in slip mode, but I tried every other mode and the problem remains.

[HDK_Ent]

do you have any plugs on the master track, if so this causes a delay, ive noticed this when playing back tracks after adding ozone to the master fader.

also, if you see the bar moving faster then your computer registers the audio and/or plays the audio back, your computer just might not be powerful enough for that session,

try inactive-ing, some audio tracks, that your not using, or slimming up your session see if that fixes the problem...

obviously, playing a 40 track song on bounce, or anything for that matter, on an old 2 ghz single core or dual core proc will cause issues...

im pretty sure if no one can give you a pro tools based answer, someones going to ask for a sandra, mite as well have it ready....

[xl999]

Got it bro, thanx for the advice. I'm going to try all of the above and I'll keep you posted.

eehm..whats a Sandra? (i'm new here).

instant edit: nope, none of that stuff works....aarghl.

[caruso7r]

"Google" Si software Pro Tools and you will find it. It gives a report of your computer specs performance etc.

[HDK_Ent]

well what your describing sounds like a dverb test nearing its end point. its when pro tools is processing faster then your computer can...

kinda like how the human SEES lighting, before it HEARS the thunder.

lighting travels faster then sound, seeing as how all your computer is, is a bunch of numbers that correspond to images, hence forth light,

obviously you'll SEE it, before you HEAR it.

it probably is your computer.


are you bouncing to disk? and what is it your trying to do with the audio your bouncing? loop it?

[xl999]

yup, I'm bouncing to disk.

I am looping series of gunshot sounds that, when inserted into a game engine, can be looped seamlessly.

Obviously I need the end and start points to be exactly the lentgh I want them to be, not a bit more or less :)