BUG? Sample rate shown does NOT update after change

Report · Jan 17, 2020

Hi,

I think I found a bug in 13.0.2.

In multitrack session, when I change the sample rate from 44 to 48, it successfully changes it in my audio interface's panel (Focusrite Control) and it also displays properly in Audio Hardware Preferences inside Audition. Perfect.

However, when you look at the project view (bottom right), you will see that the display does NOT update to show the new 48 sample rate. I even tried quitting and reloading the template I created. Same issue.

Sample rate changed but not updated in display

Report · Jan 17, 2020

Changing the Sample Rate in Audition's Preferences dosen't change the Session Sample Rate.

Close your Session. Open the assocciated .sesx file in a text editor. Up top - make the following edit, and Save. Reopen Session ...

-paul.

@produceNewMedia

Report · Jan 17, 2020

Thanks Paul - your solution is good for me to fix an existing multisession template that I don't want to rebuild from scratch.

But I realize now that my mistake was choosing the wrong sample rate when creating my template. I was thinking I could create a session from a 48kHz template and still have the ability to change it to 44 afterwards on a case by case basis. And I guess in that sense, I saw the Preferences-->Audio Hardware as a "Session/Project Setup" similar to what is found in Cubase.

I am a bit surprised that Audition does not have such a Session/Project Setup window and that everything needs to be "locked in" during file/template creation.

And so if I understand correctly then, it is possible and normal for there to be a mismatch between the sample rate in Audio Hardware preference and what is displayed (as per my screenshot) in this circumstance. Perhaps I should enable the box that says Attempt to force hardware to document sample rate in order to make sure my Focusrite always changes its sample rate accordingly so that there is no mismatch?

(PS> In the case of the previous screenshot, what sample rate would have been the recording at? The one displayed, or the one that my audio card was locked to?)

Report · Jan 23, 2020

**bump**