Reason 13.1 - prompting to save without changes / Send MIDI Clock toggling issue

This forum is for discussing Reason. Questions, answers, ideas, and opinions... all apply.
nytjadens
Posts: 3
Joined: 19 May 2018

Post 24 Jan 2025

I have just recently updated from Reason 11 / MacBook Pro 2017 to Reason 13 / MacBook Pro 2025. The transition has gone smoothly except for a few issues.

Issue 1

Songs with VST’s always ask to be saved when closing even if there haven’t been any changes. When changing a preset on a VST it doesn’t change in the Patch Load/Save section of the Plugin Rack Device. The saved file opens with the correct plugin presets but they still show Init Patch in the Patch Load/Save section of the Plugin Rack Device. Closing the file prompts the save window. Checking the edit control shows Undo Change Patch.

Issue 2

If I open a file and select Send MIDI Clock it doesn’t work. If I close the file and reopen it starts working. In Reason 11 I could toggle between Send MIDI Clock / no MIDI Clock.

Thanks in advance for your help!

Stephen
Screenshot 2025-01-24 at 6.00.27 AM.png
Screenshot 2025-01-24 at 6.02.10 AM.png
Screenshot 2025-01-24 at 6.03.17 AM.png
You do not have the required permissions to view the files attached to this post.

User avatar
huggermugger
Posts: 1547
Joined: 16 Jul 2021

Post 24 Jan 2025

Re Issue 1 - The patch name from a VST3 device is no longer reported to Reason, and will not show up in the VST shell anymore. And in fact, even with VST2, it rarely did. The majority of my VST2's don't report their patch names to Reason either. Blame it on the developer, not on Reason.

User avatar
joeyluck
Moderator
Posts: 11484
Joined: 15 Jan 2015

Post 24 Jan 2025

As for the prompt to save without making changes, it might be the plugins you are using? For instance, when I use plugins like iZotope RX and use features like "adaptive" it seems to cause a ton of undo steps by just running it, I guess because it's constantly changing and reporting those changes, which I would guess might also affect the prompt that changes have been made when closing the project.

Next time, when you open the project and make no changes, before you quit, try looking in the menu to see if there is an undo step there. If so, it should point to the plugin that is the culprit.

User avatar
Pepin
Posts: 680
Joined: 16 Jan 2015

Post 24 Jan 2025

I noticed a while ago that some VSTs write to the undo history when loaded from an existing song file. In my case, NUGEN Audio SigMod and Korg opsix native were the culprits. In these cases, the undo history shows "Undo Change Patch" as soon as the song file is loaded. Unfortunately, it's not so clear what device that applies to without a bunch of trial and error. I'm not sure if the actual issue is with these plugins or Reason's VST3 implementation. opsix also crashes sporadically when loading, possibly related.

nytjadens
Posts: 3
Joined: 19 May 2018

Post 24 Jan 2025

Yes, that's what happens!

Stephen
Screenshot 2025-01-24 at 6.03.39 AM.png
You do not have the required permissions to view the files attached to this post.

User avatar
Pepin
Posts: 680
Joined: 16 Jan 2015

Post 24 Jan 2025

Kontakt is the other one I forgot to mention that does this.
In general, I don't think there's a solution except for avoiding such plugins altogether. It's a bit annoying, but you'll already encounter "unsaved" changes like this any time there's a Reason update or a plugin is updated. The main thing to avoid is using these plugins in your startup template since that will prevent Reason from automatically closing the document when you open another song or choose a different template from the menu.

The patch name display you observe is unrelated. It will only show properly if the patch is being loaded from a directory of .fxp (vst2) or .vstpreset (vst3) files. Most plugins--especially with VST3--use their own proprietary formats so won't expose patch names in this way.

User avatar
chimp_spanner
Posts: 3086
Joined: 06 Mar 2015

Post 27 Jan 2025

Yeah some plugins do this - Logic has an option to exclude plugins from the undo history on a per plugin basis. So yeah, might be a good feature in a future version.

nytjadens
Posts: 3
Joined: 19 May 2018

Post 28 Jan 2025

Interesting... thanks for the thoughts :-) I have removed VSTs from my startup template and hope this gets sorted at some point.

Stephen

User avatar
mcatalao
Competition Winner
Posts: 1940
Joined: 17 Jan 2015

Post 28 Jan 2025

nytjadens wrote:
28 Jan 2025
Interesting... thanks for the thoughts :-) I have removed VSTs from my startup template and hope this gets sorted at some point.

Stephen
As an alternative you can keep the plugins on the template but have the vst's off in the vst container and activate them when needed:
Screenshot 2025-01-28 120954.png
You do not have the required permissions to view the files attached to this post.

  • Information
  • Who is online

    Users browsing this forum: CommonCrawl [Bot], MikeTheMan990 and 3 guests