Reason 12 quality issues.

[kitekrazy]

As if it could be done any better... People are working hard, doing their best

I am sure they do, but don't release stuff BEFORE it is ready. That's a sure way to alienate your customers.

Holding off a release date a couple times will do that.

[kitekrazy]

...That's a sure way to alienate your customers.

From my POV there is a scale. The good stuff on the one side, the bad stuff on the other and bugs, especially simple ones which could easily be catched or fixed or are not fixed within reasnable time, are on the bad stuff side.
If a dev or company gets too mich weight on the the bad side, i ignore and never buy again. They need to do quite a lot to get my trust back.

Here are a few companies i already left:
* Rob Papen
* Melda
* Waves
* IK Multimedia
* Softube
* And probably a big bunch of companies the names are already eliminated, badly associated or never got any good points in the positive scale in my brain...

Reasonstudios is currently in the balance...that is not a pretty good state IMO...and they just live from the good old times atm.

It's worse when you have to pay for an upgrade if they fix something.

[avasopht]

I disagree. Requirements alone speak that.

Not quite sure what you mean here ‍♂️

Do you mean the hardware requirements of games?

[Karim]

Mac here..

Buggy and as operating slowness is pretty unusable to me and then I have a little issue: It LITERALLY TAKES 120 minutes to boot (in fact I always use R11 for the professional work of the case) despite having an Imac with an i7 and 16 gigabytes of Ram on board .
And today I also made an update to Mac OS Catalina .... nothing, but the MacOs is really fast !
I am in contact with support to review my log files.
It's a dilemma and I think I'll start using Reason 12 when V13 is probably already out

Hi, is anyone else finding Reason 12 buggy? It feels like a pre-release version.

My PC is a 6 months old, Windows 10, Ryzen 9 5900, 32G of ram from a reputable supplier. Up to date and absolutely rock solid no issues.

[orthodox]

There's definitely a hell of a lot of bloat nowadays.

Most of it is just because they aren't concerned and might have misunderstood the caution against premature optimisation and as a result habitually hold our CPUs and ram hostage.

There are lots of leaky abstractions out there. It might be rendering a graphic using the CPU because the library being used lacks and GPU acceleration, and then sending the loaded graphic to the GPU (so now you're maintaining at least 2-3 times the storage).

Or integrating a bunch of frameworks that each have their own ad-hoc, bug riddled list processing functions littered around their modules that lead to deeply nested call stacks to do what could have been achieved in a single loop (a little hyperbole, ... but maybe not).

Of course there is a tendency to bloatware and I don't like it. I for one try to optimize my stuff where I can. Yet nobody is capable of regulating the whole industry, it will go on the way it is with incompetent specialists, wrong decisions and everything there is, and no one is to blame and nothing can be done about it.

[Vincent Vitellius]

I would suggest people join the beta and report any issues you are experiencing and include log files.

In July 2021 I reported a bug in R11. Included clear step by step instructions and a video demonstrating the problem.
It took until April 2022 before they even read the ticket. The bug was still reproducible in R12, and acknowledged.

That’s almost 9 months response time, just to read the ticket. How long it’ll take to fix the bug, is still unknown.

Why would I spend hours narrowing down the specific conditions triggering a bug, recording video and documenting the specific steps to reproduce, when this is my experience?

I regularly report bugs in other software, and usually hear back a day or two later, with a fix released one or two updates down the line.

Ever since the R12 release, I’ve had a feeling that I bet my money on the wrong horse. The bug reporting experience did not help.

[DNGmaestro]

Reason 12 still terribly full of bugs. Even today a new bug happened to me. I would click on the VST's device to appear and they would appear behind the main reason windows and wouldn't come to the front, like they always do. Had to restart.
I bought R12 on release. Still haven't used it to do serious work, simply because i can't. Terrible release, terrible costumer service. It's a shame. Can only hope they are aware of all of this, with efforts being made to be a better company in the future.

[avasopht]

In July 2021 I reported a bug in R11. Included clear step by step instructions and a video demonstrating the problem.
It took until April 2022 before they even read the ticket. The bug was still reproducible in R12, and acknowledged.

That’s almost 9 months response time, just to read the ticket. How long it’ll take to fix the bug, is still unknown.

Why would I spend hours narrowing down the specific conditions triggering a bug, recording video and documenting the specific steps to reproduce, when this is my experience?

I regularly report bugs in other software, and usually hear back a day or two later, with a fix released one or two updates down the line.

Ever since the R12 release, I’ve had a feeling that I bet my money on the wrong horse. The bug reporting experience did not help.

You won't know when they've read a ticket because they are also received by email.

What exactly was the bug? Did you mention it here?

[joeyluck]

I would suggest people join the beta and report any issues you are experiencing and include log files.

In July 2021 I reported a bug in R11. Included clear step by step instructions and a video demonstrating the problem.
It took until April 2022 before they even read the ticket. The bug was still reproducible in R12, and acknowledged.

That’s almost 9 months response time, just to read the ticket. How long it’ll take to fix the bug, is still unknown.

Why would I spend hours narrowing down the specific conditions triggering a bug, recording video and documenting the specific steps to reproduce, when this is my experience?

I regularly report bugs in other software, and usually hear back a day or two later, with a fix released one or two updates down the line.

Ever since the R12 release, I’ve had a feeling that I bet my money on the wrong horse. The bug reporting experience did not help.

The point is that you've done what you can. You can always bump the ticket and provide new info if you can and want to do that. My comment wasn't to say that a bug report will result in an immediate fix or even immediate action necessarily. Although you should hear something back after not too long.

But a bug you report with specifics about your experience, including log files, stands a better chance of being addressed and resolving a bug as it relates to your system more so than someone who doesn't report a bug. That's all I'm saying.

[Vincent Vitellius]

You won't know when they've read a ticket because they are also received by email.

What exactly was the bug? Did you mention it here?

When the response starts with "I'm going through some old tickets" and the view count on the linked video stays at zero for at least seven months, I think it’s fair to say that they didn’t read it. Technically they could have skimmed through it and forgot about it for 9 months, but I don’t consider that as actual reading.

Bug description:
When you export a song as audio at greater than 44.1kHz, while another app is in the foreground, and "play in background" in Reason audio settings is deselected, the rendered audio sounds wrong.

Since I deleted the original zero-views video about a month ago thinking they’d never respond, I had to make a new one demonstrating the problem:

I did not mention it here, since every time someone complains about a bug, it seems they are instructed to file a ticket instead. So that’s what I did.

I have no complaints about the actual conversation with the support person, nice and pleasant. It’s just the 9 months initial response time.

For any insiders wanting to verify that I’m not making this up: 99464

[Vincent Vitellius]

But a bug you report with specifics about your experience, including log files, stands a better chance of being addressed and resolving a bug as it relates to your system more so than someone who doesn't report a bug. That's all I'm saying.

I agree with you in principle. In practice I lose interest in helping out when there is no response.

[plaamook]

I think they’re just overwhelmed.
In the past they’ve always been pretty quick to reply to me about bugs.
I agree it’s disheartening but as someone said...when you’re going through hell, keep going.
Someone also said...we’re not retreating, we’re advancing in a different direction!
But I’m saving the latter for when/if things get really bad.

[helmutson]

After month of waiting that these guys making Reason stable and useful as I know it from the very first days (R1), I thought, OK I'll give RS another chance and purchased the R12 upgrade. It's simply a desaster ... there is not more to say

[Loque]

After month of waiting that these guys making Reason stable and useful as I know it from the very first days (R1), I thought, OK I'll give RS another chance and purchased the R12 upgrade. It's simply a desaster ... there is not more to say

Any points what is such desaster?

[helmutson]

After month of waiting that these guys making Reason stable and useful as I know it from the very first days (R1), I thought, OK I'll give RS another chance and purchased the R12 upgrade. It's simply a desaster ... there is not more to say

Any points what is such desaster?

Really ? I pay 199.- € for a buggy software, that's the desaster ! I can't understand that some people accept this . Compare that with hardware, you purchase for example a brandnew Boss DS-1 (or a similar thing). Would you accept some scratches, a broken knob or that the on/off LED not work? Yeah, nothing big and the pedal working so far, but you payed for a NEW one and excpect that everything is perfect (so, I do that).Thats my point !

[avasopht]

Really ? I pay 199.- € for a buggy software, that's the desaster ! I can't understand that some people accept this . Compare that with hardware, you purchase for example a brandnew Boss DS-1 (or a similar thing). Would you accept some scratches, a broken knob or that the on/off LED not work? Yeah, nothing big and the pedal working so far, but you payed for a NEW one and excpect that everything is perfect (so, I do that).Thats my point !

NOBODY has said they find buggy software or bugs in R12 acceptable.

Loque simply asked what is a disaster for you?

Bear in mind most people aren't experiencing those issues, and at the same time there are other issues raised about R12 such as the subscription service, nobody can really read your mind to know what exactly is a disaster to you.

It could be simply that you think it's a disaster because it had few features you cared about, or didn't support vst3 and Apple m1, or that it lacked content you saw in other daws.

And so, Loque, instead of trying to mind read, merely asked for you to clarify

[helmutson]

Really ? I pay 199.- € for a buggy software, that's the desaster ! I can't understand that some people accept this . Compare that with hardware, you purchase for example a brandnew Boss DS-1 (or a similar thing). Would you accept some scratches, a broken knob or that the on/off LED not work? Yeah, nothing big and the pedal working so far, but you payed for a NEW one and excpect that everything is perfect (so, I do that).Thats my point !

NOBODY has said they find buggy software or bugs in R12 acceptable.

Loque simply asked what is a disaster for you?

Bear in mind most people aren't experiencing those issues, and at the same time there are other issues raised about R12 such as the subscription service, nobody can really read your mind to know what exactly is a disaster to you.

It could be simply that you think it's a disaster because it had few features you cared about, or didn't support vst3 and Apple m1, or that it lacked content you saw in other daws.

And so, Loque, instead of trying to mind read, merely asked for you to clarify

Mmh, OK then sorry for that. English is not my native language. It felt for me like "whats your problem" or "oh not that again".
Whatever, as I said - these GUI problems are so annoying for me that I have no fun working with R12, maybe other people can live with that, I can't and I don't want it. I paid the full price for a fully functional R12. Now, not somewhere in the future ...


here is my other post from today :

I have strange horizontal and vertical lines in many devices, appearing sometimes, sometimes not. The upper border of the new vocoder RE is not a straight line/border, it's interrupted somehow. Around the transport "buttons" are lines , always when I use them, after some actions later they dissapearing. That's not the case in full screen mode. Whatever, there are more of so many stupid GUI problems, I can't accept this ... the whole DAW seems still so unfinished. I updated to R12 not long ago with the hope in mind RS will solve that very soon, I was wrong ...

PS : Beside that I have audio problems too, I never had before or have with other DAWs on the same system.

[Arrant]

I agree with the above assessment that it's a disaster.

It's so bad it should be taught in schools as an example of how to destroy an impeccable reputation for quality with a single release.

I take no enjoyment from using Reason anymore, so I have pretty much stopped making music.