Sample rate changed

I nearly had a MI a few minutes ago. I am starting a new piano work and have some sketches in Reason. So I have both Reason and Dorico 6.2.10.6140 open. As a result, if I click a note on my old Ensoniq synth, the note will sound in both Reason and Dorico once I have Dorico as my active window (Reason is set to stay active in the background). Hitting the key produced a clear dissonance, and it was clear that Dorico was off by microtones in a big way. I recently had released a work on Bandcamp and the streaming services and fortunately, that was in tune, but opening that recent Dorico file also had the tuning off. I looked at Playback Options and A=440. But on a whim I opened up Device Setup and the sample rate was set to 44100, whereas it was 48000 for Reason. Changing Dorico to 48000 restored the correct tuning.

Just posting this in case anyone has a similar finding. I had not previously changed the sample rate of Dorico but I strongly suspect the recent 6.2.1 update changed the sample rate on my end. I just changed both Reason and Dorico back to 44100, and comparing it to a standard A=440 tone on the Web, all is good. I guess one’s DAW needs to be at the same sample rate as Dorico for both to sound in tune, even though changing the sample rate in Reason does not change the frequency in that app. Strange, for sure.

Long ago I found my copy of Dorico switching from 44.1 to 48K. I believe other programs (possibly Cubase, which always used 48K) could cause the switch. So I set Dorico at 48K and have had no problem since.

48 is the new 44. :grinning_face:

Jesper

Thanks. Very odd. I know higher bitrates are better in terms of audio so I might set both back to 48k. Only risk is if whatever gremlins that downsampled things in Dorico decide to do it again.

48 or 44.1 kHz doesn’t really matter, the difference in sound is so small. So either you choose is fine, just make sure to use the same sample frequency on all your audio apps in order to avoid such detuning issues.

Yup. That’s why I typically have left things at 44.1k. Glad it wasn’t a bigger problem.