Announcing Reason 13

[RobBarnett]

Think you guys might be crossing wires. You can still edit all notes midi in a clip from the arrange view (e.g.) transpose all but if you want to edit individual notes you have to do that in the edit window

[Re8et]

My RE folder is about 40Gig but it's SymLinked to another drive, as is the factory soundbank folder. Works well on Windows but I seem to recall reading that you can't do the same on a Mac. RS really should just add an RE location setting in the prefs menu. Putting huge data files on the OS drive is just rude in this day and age.

That!

I did symlink the Reason folders like crazy. To keep track of what I did I made some notes.

Code: Select all

(((1)))
- Factory Sound Banks
- Remote
C:\ProgramData\Propellerhead Software
D:\D\Audio-Libs\RS1\Propellerhead Software
(((2)))
- Optional Content like Klang, humana, Drum Supply, Loop Supply, etc.
C:\Users\XXX\Music\Propellerhead Content
D:\D\Audio-Libs\RS2\Propellerhead Content
(((3)))
- Template Songs
C:\Users\XXX\Music\Reason 12
D:\D\Audio-Libs\RS2\Reason 12
(((4)))
- Favorites
- Preferences
- RackExtensions
C:\Users\XXX\AppData\Roaming\Propellerhead Software
D:\D\Audio-Libs\RS2\Propellerhead Software
(((5)))
- Browser Fast-Search Index file
- Graphics Cache
- Thumbnails
C:\Users\XXX\AppData\Local\Propellerhead Software
D:\D\Audio-Libs\RS4\Propellerhead Software

For that exact reason I do not understand why Reason does not support FLAC lossless compression. I converted all my samples into FLAC to save half of my disk space. Only for use in Reason I have to convert a sample back because Reason is the only pro audio software in the whole universe that can't be bothered to handle FLAC. sigh.

This is related to Windows right?
bc I'm still figuring out how to do it on Mac...

[PhillipOrdonez]

Wondering something about Ripley. How do you stop the dry signal from passing through when all modules are off and the W/D is 100% wet?

[selig]

Wondering something about Ripley. How do you stop the dry signal from passing through when all modules are off and the W/D is 100% wet?

Using the “off” switch? What is the use case for this?
I’m really not sure why there is 100% dry with ALL modules off, but with Delay off you can use the Reverb (“Space”) module on it’s own, or the Noise section (when set to INPUT at the bottom of the module), or the Dist/Digital/EQ sections etc.
Feedback filter also works, even when Delay is muted - try using the Band filter with Offset on mono sources for instant “stereo” effect - lots to explore here with all the routing options between modules IMO…

[PhillipOrdonez]

Wondering something about Ripley. How do you stop the dry signal from passing through when all modules are off and the W/D is 100% wet?

Using the “off” switch? What is the use case for this?
I’m really not sure why there is 100% dry with ALL modules off, but with Delay off you can use the Reverb (“Space”) module on it’s own, or the Noise section (when set to INPUT at the bottom of the module), or the Dist/Digital/EQ sections etc.
Feedback filter also works, even when Delay is muted - try using the Band filter with Offset on mono sources for instant “stereo” effect - lots to explore here with all the routing options between modules IMO…

Yeah I was just wondering. Thought of killing two birds with one stone given the modules do work separately from the delay, I figured it could be a quick multi send effect to have on the template and take care of delay and reverb in one send instead of two and save some resources and time by having it all set up in a combinator/ableton effect rack with easily accessible controls for using both or either or parallel and / or the other effects. By exploring this I found out the dry signal passes through when it is 100% wet and that struck me as odd ‍♂️

[selig]

Yeah I was just wondering. Thought of killing two birds with one stone given the modules do work separately from the delay, I figured it could be a quick multi send effect to have on the template and take care of delay and reverb in one send instead of two and save some resources and time by having it all set up in a combinator/ableton effect rack with easily accessible controls for using both or either or parallel and / or the other effects. By exploring this I found out the dry signal passes through when it is 100% wet and that struck me as odd ‍♂️

My guess, from having similar discussions on past devices, would be this behavior is preferred over the alternative (lesser of two evils). For example, if turning off the delay section caused total silence, more folks would be affected/confused than with this current behavior. Not to mention, it would prevent using the other sections on their own!

The same was concluded (use the lesser of the two ‘evils’) about how to set the defaults for dry/wet controls, in that defaulting to full wet made more sense than defaulting to 50/50 because the worst case would be when used as a send where you never want to have 50/50 dry/wet. The alternative use, as an insert, would easily work with a default of 100% because you’d ‘catch’ it immediately unlike when using as a send/return and a 50/50 blend.
Writing this pre-coffee, so hopefully I got everything the right way around…

[PhillipOrdonez]

Yeah I was just wondering. Thought of killing two birds with one stone given the modules do work separately from the delay, I figured it could be a quick multi send effect to have on the template and take care of delay and reverb in one send instead of two and save some resources and time by having it all set up in a combinator/ableton effect rack with easily accessible controls for using both or either or parallel and / or the other effects. By exploring this I found out the dry signal passes through when it is 100% wet and that struck me as odd ‍♂️

My guess, from having similar discussions on past devices, would be this behavior is preferred over the alternative (lesser of two evils). For example, if turning off the delay section caused total silence, more folks would be affected/confused than with this current behavior. Not to mention, it would prevent using the other sections on their own!

The same was concluded (use the lesser of the two ‘evils’) about how to set the defaults for dry/wet controls, in that defaulting to full wet made more sense than defaulting to 50/50 because the worst case would be when used as a send where you never want to have 50/50 dry/wet. The alternative use, as an insert, would easily work with a default of 100% because you’d ‘catch’ it immediately unlike when using as a send/return and a 50/50 blend.
Writing this pre-coffee, so hopefully I got everything the right way around…

Sure, though i have to look at the reset patch on ripley to check which modules are on by default. Though I imagine the majority of inexperienced users have reason set to load a patch (which on ripley is the “Much needed spice” patch which does have quite a few modules on by default) and not the device on it’s reset state. And it’s those inexperienced users we are thinking of that would hypothetically be confused about no sound after switching the delay module off, right? ‍♂️

[selig]

Sure, though i have to look at the reset patch on ripley to check which modules are on by default. Though I imagine the majority of inexperienced users have reason set to load a patch (which on ripley is the “Much needed spice” patch which does have quite a few modules on by default) and not the device on it’s reset state. And it’s those inexperienced users we are thinking of that would hypothetically be confused about no sound after switching the delay module off, right? ‍♂️

I don’t know about any of that.
But assuming there are two options here, silence, or hearing the dry signal, it seems like a no brainer to choose the former over the latter. Unless there are other options?

[tobypearce]

I can't quite see the right place to post this, but after several months of really, really trying to use R13 and its new browser, it's just not feeling natural.
It's always getting in the way, doesn't give me access to the things I need the most (e.g. quick way to load an EQ or sidechain), sits right on top of what I'm trying to look at, and looks disjointed from the rest of Reason. Reason has always had such a playful tone, but this new browser is black and white and to my eyes unpleasing.
Also, it's very purpose (I think) is to help uncover the wealth of patches in the Reason factory banks. Reason's synths are fantastic and easy to programme so with those I normally start from scratch. If I'm wanting to use a sound somebody else has made, I will almost always reach for a 3rd party synth (like Dune).

The new devices are nice but this afternoon I realised that overall, R13 has resulted in me making less music, and enjoying the process of doing it less.

It doesn't please me to say this, but I think I'm better off sticking with Reason 12 until this new browser becomes more mature. If I'm honest, it feels like a bit of a beta on top of an otherwise excellent DAW - one that I've loved for so many years.