Sonarworks in Reason

[TheNY]

Hi. I have a problem using sonarworks in reason. The thing is that the reason browser bypasses sonarworks and the samples in the browser sound different (like without sonarworks) than in the sequencer. Which is very annoying when looking for the right sample. Is there any option to prevent the browser from bypassing sonarworks?

[Loque]

No. No effects are applied when playing a sound in the browser.

[TheNY]

No. No effects are applied when playing a sound in the browser.

I thought so. Reason needs to fix this in future versions

[Loque]

No. No effects are applied when playing a sound in the browser.

I thought so. Reason needs to fix this in future versions

Nothing to fix,because nothing is broken.

You can make a request at Reasonstudios...

[crimsonwarlock]

If you update your SonarWorks to SoundID, you get system-wide ASIO-support so you won't need the VST-plugin. This offers the additional benefit of not having to disable SonarWorks before rendering your tracks. Upgrading is not exactly cheap, though. I use SonarWorks 4 myself, but I don't have this issue because I have a rather well treated room and SonarWorks does only minor corrections here.

[tanni]

as Loque said, there is nothing to fix.
If you want to browse samples with your effects chain, use an NNXT and browse the samples over it. That's the route I always take

[TheNY]

If you update your SonarWorks to SoundID, you get system-wide ASIO-support so you won't need the VST-plugin. This offers the additional benefit of not having to disable SonarWorks before rendering your tracks. Upgrading is not exactly cheap, though. I use SonarWorks 4 myself, but I don't have this issue because I have a rather well treated room and SonarWorks does only minor corrections here.

Thanks for this!