Topic: Wavelab gain application problem..

[Ray76]

Ok...I have a wav file that is unbalanced...one channel is 4db off from the other. I decided to bring them both up to zero..they were way underrecorded...well I can easily apply gain to one channel..highlight..Process>apply gain..and it changes..after i analyzed it...it expressed that the new file was indeed approaching 0db..

this other channel..no matter how much I select it and add gain(or try to add gain) I still get the same readout of the analyzation every time. I dont know the exact number but i get -6.34 db is the average peak of the selection...so I added 4db...i get the same message...basically the gain cant be added to that channel...no matter how I try to do it...

Why is this??

teddy

[F.O.Bean]

amke sure youre applying gain to your peaks NOT your average(RMS) gain

[Ray76]

amke sure youre applying gain to your peaks NOT your average(RMS) gain

what do you mean?

[momule]

yours look like this?
(notice one is Highlighted.)

[Ray76]

yours look like this?
(notice one is Highlighted.)

Yep.

[Gordon]

not exactly the same but I ran into a strange issue woth this last week.  I would highlight the channel I needed to check/raise the gain.  would hit the get peak level.  then when I set the gain and told it to raise it it would raise the channel that wasn't highlighted.  did it over and over.  so I then tried to highlight the wrong channel thinking it may raise the one I needed.  it then raised the one that was highlighted ie the worng channel.  no fucking idea why   

[Ray76]

not exactly the same but I ran into a strange issue woth this last week.  I would highlight the channel I needed to check/raise the gain.  would hit the get peak level.  then when I set the gain and told it to raise it it would raise the channel that wasn't highlighted.  did it over and over.  so I then tried to highlight the wrong channel thinking it may raise the one I needed.  it then raised the one that was highlighted ie the worng channel.  no fucking idea why   

I ran into that too John..that exact problem...weird.

[Gordon]

this has only happened with one file.  I even tried others that night and they worked fine.  it wasn't something I tpaed but something I ripped from a audio cd to use as a spice source.

[kskreider]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

But I digress, Teddy's original problem sounds awfully suspicious.  Almost like a step is being forgotten, or maybe you are even highlighting the wrong channel?     Dang, I don't know. 

What I usually do is close everything down, sleep on it, and wake up to find everything normal after a cup of strong coffee.

BTW, just highlight the file and hit "ctrl+G" to get to the gain window.  That way you don't accidentally click in your project wondow and [un]highlight something.

[Gordon]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

[kskreider]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

What version of the app are you two running anyway?

[Ray76]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

What version of the app are you two running anyway?

wavelab 5

[kskreider]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

What version of the app are you two running anyway?

wavelab 5

Sorry, I should have been more clear Teddy.  5.what?  5.0?  5.01a?  5.01b?  Maybe all you need is the newest version?

[Ray76]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

What version of the app are you two running anyway?

wavelab 5

Sorry, I should have been more clear Teddy.  5.what?  5.0?  5.01a?  5.01b?  Maybe all you need is the newest version?

oh sorry man. 5.0

[kskreider]

My guess is that you both [coincidentally] thought that you had a channel highlighted and it was not, but the other one was.  I know sometimes it is hard to tell as teh color is just the inverse of what it was.  Just a guess.

nope.  my wavs are light blue (default?) and it is very easy to see which channel is highlighted. 

What version of the app are you two running anyway?

wavelab 5

Sorry, I should have been more clear Teddy.  5.what?  5.0?  5.01a?  5.01b?  Maybe all you need is the newest version?

oh sorry man. 5.0

An upgrade may fix your problem.  I use 5.01a and I think that there is even a 5.01b out now.