Skip to main content
Known Participant
October 23, 2023

Interesting errors may be related to why Center Channel Extractor doesn't save settings

  • October 23, 2023
  • 1 reply
  • 121 views

I have a handfull of outstanding bugs that I've reported over the last year (non solved) and one of them is that the Center Channel Extractor, used in a track of a multitrack session, won't save your custom settings.  When you re-open your project, the settings to made are lost and it's back to defaults.  So, I used Notepad++ to open the "Audition Log.txt" file and set Notepad++'s View->Monitoring on.  This makes Notepad++ show any new lines that have been added to the file as they are added.  Normally, when I open my project I have to go to each of 8 tracks to open the Center Channel Exctracter effect and then apply Presets that I've made with my custom changes.  But as soon as I did that, I saw error logs generated.  In fact, you can set the effect back to default settings and make any adjustment to any of the controls and cause the error messages to be generated, below is an example:

 

Ticks = 2605016 <19556> <AdamEveAudioFilterEditorView::SyncParameters> <5> (from component) parameter out of range: index = 15, value = 4
Ticks = 2605016 <19556> <AdamEveAudioFilterEditorView::SyncParameters> <5> (from component) parameter out of range: index = 19, value = 3

 

These errors don't seem to have any negative affect on the usefulness of the effort (your changes do work) but I'm suspecting that they are the cause of why the effect won't save any settings.  Like whatever detects that these values are out of range is incorrect about that but since it flag them as out of range it won't save them.  

 

Please don't bother asking what my settings to this effect are.  It don't matter what settings you try, it ALWAYS generates these error logs for any/all changes.  Even selecting "(Default)" will cause it.

1 reply

SteveG_AudioMasters_
Community Expert
Community Expert
October 23, 2023

Now I know it shouldn't really be like this, but if I follow your steps, change the values and save them as a preset, that works fine. If I close the session (and Audition) and then reopen it then yes, it comes up as saying that my test preset has been returned to its default settings (with a star besides its name). Only it hasn't - if you select Default and then reselect my test preset, it comes back exactly as I saved it.

 

So yes it's broken, but it's not a case of it not saving the settings - clearly it does. What it doesn't do is read the parameters back in correctly. Still needs fixing though.