FWIW I can't seem to find anyone else with this problem atm. Good news for you all. Bad news for me lolArpeg wrote: ↑11 Oct 2022Oh the Pain of unwanted glitches in visual and sound are now gone. Like Selig and others, I am reaching 64 buffer size, sample rate 48,000 and Max Threads just on Default on a track that had weird glitch problems before this update.
Using a i7 3770 3.4Ghz Win10 - Behringer UMC404HD - It seems flawless at the moment and now I can say it is the best it has been since I jumped back on the Reason ship in version 10.
No weird browser search behaviour, all seems fine atm. Hope folks get their problems sorted and get to experience a very up to par Reason 12.
It's highly unlikely for them to drop M1 support.LittleBoy wrote: ↑12 Oct 2022Well, if this update is concerned with improving performance over Rosetta, I'm afraid that support for M1 is still missing. Why improve performance over Rosetta if in 1 or 2 months they were going to introduce native support for M1?
What I'm starting to fear is that Reason Studios is going to drop support for M1 and VST3 for Reason 13, and they're going to spend all of Reason 12 without fulfilling their roadmap. If by spring 2023 there is no support for M1 and VST3, I am sure that I will sell my license.
It's funny that the one thing many of us thought years ago would transition easiest to scaling (the transport) is one of the few things having graphical issues. Back when R8 introduced the flat transport, some users were missing the hardware look of the old transport, and came to terms with it based on the idea of it being easier to scale and the excitement of a scalable Reason...
Literally zero chance of this stuff happeningLittleBoy wrote: ↑12 Oct 2022Well, if this update is concerned with improving performance over Rosetta, I'm afraid that support for M1 is still missing. Why improve performance over Rosetta if in 1 or 2 months they were going to introduce native support for M1?
What I'm starting to fear is that Reason Studios is going to drop support for M1 and VST3 for Reason 13, and they're going to spend all of Reason 12 without fulfilling their roadmap. If by spring 2023 there is no support for M1 and VST3, I am sure that I will sell my license.
You're right - one would think that drawing a grey rectangle would be simple enough.joeyluck wrote: ↑12 Oct 2022It's funny that the one thing many of us thought years ago would transition easiest to scaling (the transport) is one of the few things having graphical issues. Back when R8 introduced the flat transport, some users were missing the hardware look of the old transport, and came to terms with it based on the idea of it being easier to scale and the excitement of a scalable Reason...
I haven't noticed those issues here.
yep. well, I hadn't tried all of them until you said that (thanks for the suggestion), but I did try a few, and those didn't work. just went back and tried them all and yeah, still a glitchy mess even with the DSP meter hovering just above halfway. 🥲
Maybe I shouldn't post so soon lol. So far Ive noticed a significant performance improvement.selig wrote: ↑11 Oct 2022On a more positive note, the same song that would crawl to almost a halt plays PERFECTLY at a buffer of 64 samples at the default CPU setting on my new M1 Studio Max. The previous version needed 1024 sample buffers and turning off Multi-Core Rendering to play without glitches. Impressive performance indeed.
I should note that I’ve never been able to get 64 samples to play complex songs on any previous systems I’ve owned or worked on!
[there is some minor glitching with fast scrolling @ 64 samples, but none at higher buffer settings]
First time I fired up the newest build I also had the DSP sitting at half way. Restarted it and now I’m flying.
Yes, you're wrong. Again, Reason Studios have very publicly stated that they are working on VST3 right now, at this very moment, and it will (very likely) appear in Reason (12) before the end of this year (as recent as June 2022, their VST3 hosting could already load instruments and effects). And official M1 support is coming after - again - in Reason 12. Nothing to worry about. Actually, what you see in 12.2.9 is part of the M1 support that will come...
What you see in 12.2.9 is exactly that. ^^Reason M1 native support development will start off with threading optimisations we believe will affect performance and battery life positively for all platforms including non M1-macs.
Hey man - I just checked my Windows machine (that infamously had search indexing broken for several Reason 12 updates many moons ago). 12.2.9 d40 search/indexing seems to work fine for me. Sorry! Looks like you've got a unique issue.chimp_spanner wrote: ↑11 Oct 2022Hey just wondering if anyone is getting weird browser search behaviour? Specifically, mine has stopped working haha. Even searching Drum Supply for 'kick' nothing comes up. It just sits there. I'll try a restart maybe. Anyone else getting this?
I did not share your optimistic timetable thoughts since it was known at the time that this tidy little update required a top down (or is it bottom up) re-writing of the entire graphics engine of over 20 year old code. While it has taken longer than I had hoped, I am not surprised.Jackjackdaw wrote: ↑12 Oct 2022Well I dunno… I thought hd graphics would be a tidy little 11.5 update but it turned out 12 is just a big old beta test for it. The longer they take , the more the update cycle coffers are emptied.
On that I fully agree with youselig wrote: ↑12 Oct 2022I did not share your optimistic timetable thoughts since it was known at the time that this tidy little update required a top down (or is it bottom up) re-writing of the entire graphics engine of over 20 year old code. While it has taken longer than I had hoped, I am not surprised.
Similar to how a home renovation of an older home always reveals issues that were not obvious (or knowable) before ripping into the structure.
...All good! Deleting the index v4 and 5 on the advice of support helped. Although v4 still isn't rebuilt. Not sure if it's needed for something else that I'm not aware of at this point. But v5 was, and once it did, search worked again. Fast as anything too. Like really fast.EnochLight wrote: ↑12 Oct 2022Hey man - I just checked my Windows machine (that infamously had search indexing broken for several Reason 12 updates many moons ago). 12.2.9 d40 search/indexing seems to work fine for me. Sorry! Looks like you've got a unique issue.chimp_spanner wrote: ↑11 Oct 2022Hey just wondering if anyone is getting weird browser search behaviour? Specifically, mine has stopped working haha. Even searching Drum Supply for 'kick' nothing comes up. It just sits there. I'll try a restart maybe. Anyone else getting this?
Should be settled for the next 15 years now. 
Oh man - that sucks! Yeah I'd never EVER update my software in the middle of a project. Burned too many times in the past before. Hopefully you can get things sorted.MarkTarlton wrote: ↑12 Oct 2022I have had a couple crashes, and have only opened up a few songs to test and make sure my older tunes are still working fine, I am a little nervous since I am in the middle of a project that is on a break til I get back from my tour.
Thanks, I know I usually never update either, but I was hoping it would fix another bug I have been having, unfortunately it didn't. The good news is I haven't had any other crashes today when I briefly played around with some ideas. It's been pretty stable other than those crashes yesterday.EnochLight wrote: ↑12 Oct 2022Oh man - that sucks! Yeah I'd never EVER update my software in the middle of a project. Burned too many times in the past before. Hopefully you can get things sorted.MarkTarlton wrote: ↑12 Oct 2022I have had a couple crashes, and have only opened up a few songs to test and make sure my older tunes are still working fine, I am a little nervous since I am in the middle of a project that is on a break til I get back from my tour.
It's not a little update.Jackjackdaw wrote: ↑12 Oct 2022Well I dunno… I thought hd graphics would be a tidy little 11.5 update but it turned out 12 is just a big old beta test for it. The longer they take , the more the update cycle coffers are emptied.
getting used to disappointment.