We're happy to announce the release of Reason 11.3.6, Reason 11.3.6 Suite, Reason 11.3.6 Intro and Reason 11.3.6 Lite.
Here's what's new:
- Fixed a bug where Reason would not receive audio input on some versions of macOS in certain situations.
- Fixed a bug where it was not possible to run pattern devices inside a Combinator in Reason Rack Plugin.
Reason/Suite/Intro/Lite 11.3.6 released!
- Reasonistas
- RE Developer
- Posts: 875
- Joined: 15 Jan 2015
- Location: Morristown, NJ USA
- Contact:
https://help.reasonstudios.com/hc/en-us ... -released-
- Creativemind
- Posts: 4876
- Joined: 17 Jan 2015
- Location: Stoke-On-Trent, England, UK
Gonna go make a coffee, can't take the excitement.
Reason Studio's 11.3 / Cockos Reaper 6.82 / Cakewalk By Bandlab / Orion 8.6
http://soundcloud.com/creativemind75/iv ... soul-mix-3
smaller, more frequent updates to address bugs is a good thing. better than them leaving bugs in there until they put out a splashier update. not every release needs to be exciting.
-
- Posts: 3756
- Joined: 20 Oct 2017
- Location: Norway
- Contact:
Keep the updates coming, you're working hard and i for one love it
- Boombastix
- Competition Winner
- Posts: 1929
- Joined: 18 May 2018
- Location: Bay Area, CA
They broke VST graphics for some plugins on Mac, in 11.3.5. No plan to fix?
10% off at Waves with link: https://www.waves.com/r/6gh2b0
Disclaimer - I get 10% as well.
Disclaimer - I get 10% as well.
Nope. I reported that bug to them and they replied something along the lines of "we expect the plugin developers to fix it on their end..."Boombastix wrote: ↑01 Dec 2020They broke VST graphics for some plugins on Mac, in 11.3.5. No plan to fix?
I was quite taken aback by that answer too... Then I realized that most VSTs worked after I updated them to the latest version... Outliers are some older Waves plugins (that are not on 11 or 12), with Sibilance crashing Reason 11.3.6 now...
D.
To check if broken graphics for some plugins on Mac are responsability of third party developpers, a simple way is to load them (as AU, but it is relevant) in last GarageBand. If they are not working as expected in GarageBand, then the answer is probably something that should be fixed by third party VST developper. New SDK in MacOS broke some VSTs (for example WaveArts V5 or Photosounder Spiral). Many VST have been fixed already by their developper (Waves and McDsp are amongst them). Double check if you have last versions.Boombastix wrote: ↑01 Dec 2020They broke VST graphics for some plugins on Mac, in 11.3.5. No plan to fix?
- hamsterfactor
- Posts: 100
- Joined: 22 Nov 2020
Ta, updated!
Suite 11 | 12 perpetual license | | | macOS Ventura | Mac Studio M1 Max
- Boombastix
- Competition Winner
- Posts: 1929
- Joined: 18 May 2018
- Location: Bay Area, CA
Bad policy in my opinion, to break VST comparability in a minor update. They should have waited until v12 if they had managed this correctly. Doesn't affect me since I'm on Windows, but I still think it is poorly managed since they were not forced to update their SDK and other developers seems to have not.eusti wrote: ↑01 Dec 2020Nope. I reported that bug to them and they replied something along the lines of "we expect the plugin developers to fix it on their end..."Boombastix wrote: ↑01 Dec 2020They broke VST graphics for some plugins on Mac, in 11.3.5. No plan to fix?
I was quite taken aback by that answer too... Then I realized that most VSTs worked after I updated them to the latest version... Outliers are some older Waves plugins (that are not on 11 or 12), with Sibilance crashing Reason 11.3.6 now...
D.
10% off at Waves with link: https://www.waves.com/r/6gh2b0
Disclaimer - I get 10% as well.
Disclaimer - I get 10% as well.
I'm guessing that they updated to the latest SDK so they can start building Reason natively for Apple Silicon. (Note, this is pure speculation on my part!)Boombastix wrote: ↑08 Dec 2020Bad policy in my opinion, to break VST comparability in a minor update. They should have waited until v12 if they had managed this correctly. Doesn't affect me since I'm on Windows, but I still think it is poorly managed since they were not forced to update their SDK and other developers seems to have not.eusti wrote: ↑01 Dec 2020
Nope. I reported that bug to them and they replied something along the lines of "we expect the plugin developers to fix it on their end..."
I was quite taken aback by that answer too... Then I realized that most VSTs worked after I updated them to the latest version... Outliers are some older Waves plugins (that are not on 11 or 12), with Sibilance crashing Reason 11.3.6 now...
D.
I don't think that RS can be held responsible for other VST manufacturers not implementing their GUI scaling correctly.
It's not like every VST broke, it was just the ones that had this underlying flaw that happened to be exposed under the new SDK.
They would have to fix the problem sooner or later anyway, and this might have helped speed that process up.
-
- Information
-
Who is online
Users browsing this forum: No registered users and 36 guests