Compression in logic

[beerz]

safe my housemate uses logic and has the standard logic compressor on his kick track. The problem is that the first kick is a lot louder than the rest of the kicks and its definately something to do with the compressor.

the attack has been put at max and minimum and doesn't really solve anything.

i dont use logic so don't really have a clue how anything works at all was hoping someone could help. cheers.

[green plan]

Hmmm I'm not sure what your mates problem is. Maybe accidental bypass automation but probably not. So the first one hits loud then the rest are quieter? Are the rest quieter because his sub/bass comes in and covers up the kick frequencies maybe. Watch the compressor as the kicks run through it, is there the same amount of gain reduction on each one (the little blue bar at top of compressor)?

[beerz]

cheers 4 the reply.....its deffo not a mix down problem because it happens when the channel is solo'd.

the gain reduction is exactly the same for the loud kick than the quieter kicks.

alsooo, when we loop the first four kicks, it only happens the first time the kick is played and when the first kick comes around on the loop again its the same level as the others again. So basically it only happens when we press play...like there's a latency on the compressor to act or something.

its not just kicks its anything with a compressor on...the kicks are just the most noticable.

[green plan]

Hmm that's really weird. Does it happen across all projects or just this one? I know that sometimes when I start from a template in logic 8 the first hit of the first bar will be louder. But if you keep looping it that first hit isn't louder - exactly like you said. Think it might be a bug in logic, not sure. My work arounds are either to create a new project and drag everything across (lame and time consuming) or to move the start point of the project back half a bar, put in hits there that serve no purpose other than getting the loud bit out of the way, then start your tune proper on 1. Then when you bounce it out you can just slice off that first hit easy peasy. But it is a tax. Are you starting from a self made template? Anyone else any smart ideas?

[FORGETIT]

kick track being an AUDIO TRACK or an INSTRUMENT TRACK ?

[beerz]

the kicks are audio but it happens on synth tracks too

[beerz]

the guy who uses logic has gone to bed now but im sure it happens in every project as he said its a constant bug..

not sure about your other questions as i dont know much about logic :s

[mondays child]

Are you using a 'legit' version? if not, that might be your problem. I'd have a look at the buffer size in the logic preferences drop down menu. see what it's set to, try higher settings, this might be affecting your latency.
Other than that, it's not a problem i've heard of.

[beerz]

Are you using a 'legit' version? if not, that might be your problem. I'd have a look at the buffer size in the logic preferences drop down menu. see what it's set to, try higher settings, this might be affecting your latency.
Other than that, it's not a problem i've heard of.

ye its deffo legit he had it bundled with his macbook pro..cheers we'l look into those buffer size settings

[Wrigzilla]

I've had this problem with my copy of logic before (a legit one). It's possibly caused by the compression settings your using or it could be a bug. My solution to get around it is to bounce 8/16 bars of just the kick and then cut out the quiet one and replace it with one of the normal level ones.

[logic pro]

^^this or

newest version?

defo know this problems..

some non updated logics have strange problems,

logic 5.5. had similar issues....

one workaround i know:
start your tune some bars later...
(be careful with copying automation)

copy all the elements that hav said problems on bar 1

so first bar will be fucked but you dont have the problems while the real tune is running...
after bouncing out
chop the first empty/loud bars....

suckz but workz

[wirez]

It's probably because you accidentally have 2 midi notes layered on top of each other, or it sometimes randomly happens when you loop but I'm not too sure... If the selection isn't looped, do you still have the issue? If so I can almost guarantee it's a duplication.

EDIT: ok I read more and it said your compressor gain reduction doesn't change. Therefore it's not a 'real' issue and it's just a bug. It happens to me sometimes when I loop something, it's a looping bug lol. I bet it doesn't happen when that selection isn't looped!

[beerz]

It's probably because you accidentally have 2 midi notes layered on top of each other, or it sometimes randomly happens when you loop but I'm not too sure... If the selection isn't looped, do you still have the issue? If so I can almost guarantee it's a duplication.

EDIT: ok I read more and it said your compressor gain reduction doesn't change. Therefore it's not a 'real' issue and it's just a bug. It happens to me sometimes when I loop something, it's a looping bug lol. I bet it doesn't happen when that selection isn't looped!

ye it happens w.e you press play doesn't matter if it's looped but ye....we've just come tot the conclusion that its something that happens n gona just do that move things a bar forward technique