Skip to main content
N
Nina_T22910861
Participant
January 30, 2022
Answered

Center Channel Extractor Frequency Range is all wrong after closing the program

  • January 30, 2022
  • 1 reply
  • 299 views

Hi,

 

I'm using Center Channel Extractor in one of my tracks. I have split my track into several clips, and I want to use different Frequency Range in each clip, or in some clips I don't want to use this effect at all. Unfortunately, when I close the program and open it again, all the Frequency Ranges have changed to Start: 20 Hz and End: 22050 Hz, which results in the track sounding awful. 

 

I have made presets for this effect for each different clip that I want and set my own custom Frequency Ranges. Yet when I open the program, open the file and edit the effect, it shows that I have the correct preset chosen, but the frequencies are completely wrong. I need to choose the preset for each clip every time I open the program again and I find it laborious.

 

How can I make the frequencies to stay as I want them to stay?

 

Thanks

Nina

This topic has been closed for replies.
Correct answer SteveG_AudioMasters_

I think that this may be due to a limitation of what you can do with clip effects in a rack. But before I go any further, I have to point out that this is not an effect that you should be deploying in Multitrack anyway, really - it's very processor-intensive (which is why it shows up as red as a warning when you insert it) and having multiple instances of it running is really asking for trouble. Really it's best to do all this sort of processing to the files before you put them in the session, so that the mixdown will run more smoothly.

 

One thing you could try though is to put all of the clips you want to apply this to on a single track, and apply the extractor as a track effect. When you do this, you can use the automation system to alter the effect settings at different points along the track. You'd only need a single instance running then, and you could also pre-render the track. That I think should run relatively smoothly, and not require any presets at all - just some automation changes.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
January 31, 2022

Could we establish initially that you are trying to do this in Multitrack view?

N
Nina_T22910861Author
Participant
January 31, 2022

Hi Steve,

 

yes, I'm trying to do this in Multitrack view.

 

Nina

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community ExpertCorrect answer
Community Expert
January 31, 2022

I think that this may be due to a limitation of what you can do with clip effects in a rack. But before I go any further, I have to point out that this is not an effect that you should be deploying in Multitrack anyway, really - it's very processor-intensive (which is why it shows up as red as a warning when you insert it) and having multiple instances of it running is really asking for trouble. Really it's best to do all this sort of processing to the files before you put them in the session, so that the mixdown will run more smoothly.

 

One thing you could try though is to put all of the clips you want to apply this to on a single track, and apply the extractor as a track effect. When you do this, you can use the automation system to alter the effect settings at different points along the track. You'd only need a single instance running then, and you could also pre-render the track. That I think should run relatively smoothly, and not require any presets at all - just some automation changes.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices