No, OP was pretty clear that this started happening well before the patch came out.

Yup, you've locked yourself out of the computer authorization route. If you do any kind of operation on the OS to be on the safe side de-authorize the computer first. Then when you are done with messing with the OS it is a simple job of re-authorizing. I've done this myself before, after a public b...

Thanks for the data point, ravisoni. Looks like more confirmation that Win10 users should be pretty much fine, at least. Would love to hear from more Win7/8.1 users about how they're doing with the patch!

For god's sake, yes, there needs to at least be some visual indication of the fact that not all controls are being displayed. They could show just the edge of the first hidden control, fading off after a few pixels, or something like that. Otherwise you get very confused users, as in this thread and...

Perfectly coherent, good to have that cleared up. Thanks!

Yeah, absolutely. This is one of the better threads on this subject I've seen anywhere, thanks!

It's a bit of a pain to resort to a whole separate VST with the pop-out window and all when a super-simple unobtrusive native rack device will do the job just as well, though. (Thanks for the tip on that VST though, I didn't know about that and it looks great!)

Any ideas? No need to go painstakingly through all of my questions, I'd be happy enough to get even just one or two of them answered. I know you're out there, IR experts!

Thanks for clarifying that, drloop! Almost everyone with a pre-haswell chip, especially those with a Clarkdale or even Lynnfield, is reporting 'some' loss of performance with the patch, ranging from 5 to 15% depending on the hardware (it seems the type/brand of audio interface also matters, as are t...

I only wish it took a bit more of a "hybrid" approach to IR - e.g. some sort of internal modulation of the IR to make it less static. Some algorithmic wizardry, pre-convolution EQ or anything exciting. Another thing you should check out is Overloud REmatrix (https://overloud.com/products/rematrix),...

Damn, that's unfortunate, though not surprising, as it's consistent with what was mentioned upthread about Win8.1. Thanks for sharing that info--if anyone else who's on Win7 or Win8.1 has the patch (released yesterday I think?), please do share your experiences. It seems that's where the greatest di...

I have patched and benchmarked with my own projects. W10 i5 3570K Reason 10 Tracktion 8 Also tried on my old laptop with i3 330m, W10 and Reason 10 The results... Works like a charm, I get no obvious performance hit at all. I knew if this thread went on long enough someone would eventually give som...

See, I knew if I said that it'd get fixed the next day so I'd have egg on my face. That's why I said it. You can all thank me later.

It's a known bug introduced with the 10.0.1 update (Mac only). Discussed at length here: https://forum.reasontalk.com/viewtopic.php?t=7504841&start=25 PH is aware of it, but they sure seem to be taking their sweet time about fixing it. I'd roll back to 10.0 in the meantime if I were you, there might...

I've got some old Multi-FX units lying around and would like to record some IRs for them. I know the basics of how to do it, but am a bit unclear on what the limitations are for what can be done successfully with IRs. Given that I'll be using them with the RV7000MkII, and since some of the best IR d...

Quite so. As always, it will depend on the individual use case.

Ah I see, by "pure processing power" you specifically meant per-core processing power. At a certain point it boils down to semantics, of course (i.e. if I had more per-core processing power I'd have less of a need to resort to features that parallelize the workload, etc.) but that does make sense. A...

Taking it back to the subject of this thread: I do find that turning HyperThreading on in Reason often buys me an increase of ~50% or sometimes even more in the number of identical (and, of course, non-interconnected) mix channels I can run before I hit my DSP limit. Which presumably suggests that, ...

Okay... good food for thought. Thanks

If the CPU is 33% of the buffer time and the rest is 66% then doubling your CPU power you can only lower the DSP load by 16%. And yes, with low buffer sizes these ratios can really shift that far. Only a third of the time used for actually computing stuff! The answer to the last question is a bit m...

Sure, but if the CPU weren't a bottleneck, upgrading the CPU while leaving everything else the same wouldn't help, right? ;) I get what you're saying--there are other things that matter too, and more performance can often be extracted from the CPU by optimizing other things. So you're quite right to...

And again, it will only give you less DSP load if the raw processing power of the CPU was the bottleneck in the first place - which it almost never is these days. I would love to see a bit of clarification/elaboration on this. If the "raw processing power of the CPU" isn't usually the bottleneck, t...

Which meter do you mean by "peak meter"? There's no way to add detail to the labeling of Reason's meters unfortunately, but if you're not already using the "Big Meter" on the hardware interface, check that out and see if it helps at all. Despite the labeling, you can pretty easily read it down to 1 ...

Hello. Househoppin - I suspect you're not going to get the data you crave. You can keep refreshing this and the other thread, but probably your best bet will be to start reading the less specific music production forums like Gearslutz and KVR. Try searching forums for Ableton and Pro Tools for this...

This is turning into an incredibly informative thread! Thanks to selig and everyone else for these invaluable tips.