PSA: do not beta test RE's on your only production machine
- Marco Raaphorst
- Posts: 2504
- Joined: 22 Jan 2015
- Location: The Hague, The Netherlands
- Contact:
It's even more disastrous:
A developer can automatically send beta version to end-users, for example when wanting to test an update.
So, when you have beta tested a RE in the past, the developer might automatically give you a beta version (you won't notice this!!!)
OR by mistake, when a developer types in the wrong name, you get the beta RE.
I have had locked up files and many combinators which were broken during development.
I hope the Props takes action. This is broken.
A developer can automatically send beta version to end-users, for example when wanting to test an update.
So, when you have beta tested a RE in the past, the developer might automatically give you a beta version (you won't notice this!!!)
OR by mistake, when a developer types in the wrong name, you get the beta RE.
I have had locked up files and many combinators which were broken during development.
I hope the Props takes action. This is broken.
Props should implement an "allow beta" checkbox for every RE in our account so you have the ability to choose wether you want a beta when available or the latest stable version. Right now the control over this is in the hands of the dev, we should be able to override this.
V9 | i7 5930 | Motu 828 MK3 | Win 10
- Marco Raaphorst
- Posts: 2504
- Joined: 22 Jan 2015
- Location: The Hague, The Netherlands
- Contact:
At least the Props should fix Reason so that a 3rd party RE never ever would lockup Reason. Like VST and AU.
-
- Information
-
Who is online
Users browsing this forum: No registered users and 33 guests