Great update. As a Tauist I'd love to see the (actual) circle constant tau=6.2831853071... (which happens to be 2 Pi) added in case you're adding some other new features. Using "tau" instead of "2*pi" would also save a few characters in some formulas.

For chop FX you can also use Alligator or a Matrix controlling the output volume or filter frequency of the device.

Disabling hardware acceleration isn’t a great solution, because it shifts more of the rendering load to the CPU, which can noticeably affect performance depending on the system. I’ve got the same issue, by the way, and I’m using this workaround too. Reason Studios should consider dropping OpenGL fo...

If you don't need live conversion of your voice you can also record it as an audio track and use the internal monophonic audio to MIDI conversion in Reason.

Mapping the controls of one complete mix channel and then two additional controls to increase/decrease the mix channel base should work just fine. Maybe stripping down or editing the BCR codec from Mixer Jaëxx could be a good option: https://www.jaexx.com/blog/reason-using-a-bcr2000-to-fully-control...

I think the Remote SDK has those questions covered. You can find it here: https://developer.reasonstudios.com/dow ... r-products

"We got both kinds of music: We've got country and western."

Simply put a dual arp player on top of Thor and activate only arp 1 and the hold function.

Best workaround so far (sadly) is to open up the fader value to DB mapping table that selig shared some time ago and do a lookup.

I love the mix of different musical styles in combination with the quirky lyrics and video.

I think in most oft those cases it was either a broken OpenGL implementation in the graphics card driver that caused graphics glitches or bad power saving settings that caused audio dropouts. There should be some threads about this in the forum here.

The only quick way that I know of: Restore from your local or online backup.

Passive splitters usually just connect both outputs to the input. In unbalanced consumer systems with RCA its the voltage that's usually then coupled to HighZ inputs at the active speaker. This way of spliting the signal should not really affect the levels. And even if it did you could simply add a ...

There should be an automatable control for the pattern (number). Of course it will not show the names of the patterns in your DAW but instead it will most likely be just a float value between 0.0 and 1.0.

Reason still does not support MIDI output from VST(3). But you can use drag and drop to get the generated MIDI from it into the sequencer iirc.

It might be better to opt for the safe option than killing studio equipment or the hearing of a user as some added delay at least allows for a little reaction time to possible feedback build-up.

Here is some possible inspiration on how a voting system could be implemented: https://remix64.com/articles/voting-system.html

Maybe they did it this way so you can't easily run into feedback loops by accident.

Sure, native support for NKS would be very welcome, but I highly doubt to see it in Reason unless RS is bought up by NI. Also in general the whole MIDI implementation inside of Reason could use some overhaul (also for MIDI 2.0), but I doubt to see this in the next few years as RS is still struggling...

You can simply write a sensible remote map for the combinator with a sensible layout once and then use the combinator to map the controls to the VST(i) controls.

Instead of introducing an additional system RS should imho rather make it easy to create remote maps from within Reason.

The combinator is the Reason way of doing macro controls. I don't think there will be any parallel structure implemented to this.

I think those are recorded drums. Thus some mic bleed might just be part of the samples. You could ask ujam about this.

To my eyes these meters definitely sound much more pro. I bet they even taste sweeter.

The only alternative is to use individual instances of the Kontakt VST each with only one instrument. The performance overhead for this should be rather small when using Reason 13.

Insert "why can't we have both?" meme here.