Reason 13.1 Update feature discussion

[crimsonwarlock]

bla bla bla

Still only vague statements and your default 'I know better because I know better'

Your stance boils down to 'a non-modular system is the same as a modular system', which is total cowcrap and shouldn't even be debated. We all know and understand the difference, except you, obviously.

Just keep on trolling, it's the one thing you are obviously good at

You are back on my block list.

[crimsonwarlock]

Because Reason is a never ending promise by design

Going from the endless feature requests on literary every DAWs user-forum, that goes for every DAW

Besides that, getting something because there is some 'promise' it will have or do something in the future, is stupid. I get things for what they can do right now, and for me Reason is in that category.

[SebAV]

But if you stay at a « Reason » pace when buying vst (one new every year average) you chose the right plugin manufacturer, it’s the same.

Of course it is not the same, and buying pace has nothing to do with it. I own over 500 rack extensions, and they will all work in any future Reason version without exception.

I Hope you’ve received a « Reason shop medal » for owning so many RE

NI, u-he, Arturia, Sonicharge (!) : they all keep their plugins running since their releases.

Until they don't, many well known plugin developers have simply disappeared for one or another reason. And besides that, big developers abandon stuff as well, like NI does regularly.

Hence chosing the « right » manufacturers. Regarding NI : regularly (not so) they update their VST. Something often asked by users at RT (Why don’t RS upgrade Subtractor, etc.)

This is the big difference: it is not the RE developers who secure their REs for future Reason versions, it is Reason Studios who secure this feat. The moment that Reason was updated to run on new Apple silicon, EVERY rack extension existing was as well. While other DAWs were updated to that OS, many people found out that a big portion of their plugins still weren't updated (and many won't), and they had to resort to running compatibility modes on their Mac to keep things working.

RS « sécurisation » is the same as every software editor

Same with DAW : the « big » ones are still able to open « old » projects

They can load the projects, but they can't load the plugins inside those projects if hose are no longer supported or even available.

Same as main argument

(I still wonder why Reason fans, which always update to the last version of Reason keep « pushing » the fact that Reason xx can open Reason 1.0 songs.

Because that Reason 1.0 instruments are still there and working. And every rack extension from the first one ever made, will also still load and work regardless.

How many people are really considering a DAW 20 years later with the idea of being able to open an old track ?)

Probably most people who were making music 20 years ago

When you update regularly, as Reason fans do, it’s a non subject. When you stopped using Reason during 20 years, it’s a non subject.

[yoursoul]

///

[bjm4tt]

a non-modular system is the same as a modular system

His problem might be that you single handedly decided what modularity means. Maybe others care less about the ability to use the mixer channels as inserts. Can you save them as a single patch and recall in other projects? No? Then it's not modular.

You see, it's easy to come up with arbitrary definitions. Can you nest combinators? No? Not modular! CV is not audio rate? Haha, not real modular! Poly CV without using 3rd party extensions relying on delayed signals? Nope? No MIDI out from VST's?

[crimsonwarlock]

I Hope you’ve received a « Reason shop medal » for owning so many RE

There are many Reason users who own hundreds of REs. And why should that be special, as KVR is full of comments from users boasting they have THOUSANDS of VST plugins. There are currently two active threads about sizing down huge plugin collections. So let's stop the cheap comebacks.

Regarding NI : regularly (not so) they update their VST. Something often asked by users at RT (Why don’t RS upgrade Subtractor, etc.)

NI has abandoned many plugins over the years, instead of updating them. On the other hand, Subtractor is still here and usable because Reason Studios keeps it working in its original state. Something I would have appreciated from NI if they had done the same with all the plugins I've bought from them and cannot use anymore.

[crimsonwarlock]

His problem might be that you single handedly decided what modularity means.

Nope, I pointed to the dictionary definition. People who argue that modularity means something else than the collectively agreed upon definition, are the ones who are "single handedly deciding what modularity means".

You see, it's easy to come up with arbitrary definitions. Can you nest combinators? No? Not modular! CV is not audio rate? Haha, not real modular! Poly CV without using 3rd party extensions relying on delayed signals? Nope? No MIDI out from VST's?

A Moog System 55 does not have MIDI, Poly CV, it can't nest modules inside modules, it cannot save a module's settings to use in another project, and yet nobody will argue that it is not a modular system. Obviously, because it adheres to the commonly accepted definition of modularity.

Opinions are not facts.

[jens]

bla bla bla

Still only vague statements and your default 'I know better because I know better'

well, I didn't explain it in detail because it is so bloody obvious and you claimed you were pretty familiar with Reaper - but I'll gladly lay it out for you in detail if that helps you to get your stuff sorted:

- On the track left-click the "ROUTE" -button.
(- if you don't want to send to the main out, untick "Master send channels from/to")
- open the "Audio Hardware Outputs" pulldown-menu (that says "Add new hardware output" by default) by clicking on it.
- select the hardware out(s) you want to route the channel to by clicking on it in the menu.

Done.

Your stance boils down to 'a non-modular system is the same as a modular system', which is total cowcrap and shouldn't even be debated. We all know and understand the difference, except you, obviously.

No, my stance boils down to >>what is and what is not a modular-system is debatable and a matter of definition and if you had half as much of a clue as you obviously think you do you would be well aware of this<< . It certainly isn't the cables - that's just a GUI-gimmick in Reason which - asd I mentioned before - the user can get rid of completely.

Just keep on trolling, it's the one thing you are obviously good at

You are back on my block list.

Again: why would I care? I'll gladly keep calling you clueless in your absence.

[bjm4tt]

So how's the new 'favourites' now they put it in (not the same as old though?)
I'm still on 12, haven't tried 13

In the device browser predefined categories can be assigned to devices, or tagged with user created tags and you can filter by these categories/tags, even combine them. Not the same as favorite lists, but gets the job done.

In the patch browser it's similar, but the categories and tags are not the same as the ones in the device browser and they apply only to patches.

[hotmitts]

So how's the new 'favourites' now they put it in (not the same as old though?)
I'm still on 12, haven't tried 13

In the device browser predefined categories can be assigned to devices, or tagged with user created tags and you can filter by these categories/tags, even combine them. Not the same as favorite lists, but gets the job done.

In the patch browser it's similar, but the categories and tags are not the same as the ones in the device browser and they apply only to patches.

Thanks. I wonder if you can save those over to future updates though.
Still nor really clear why they ditched the old method, which was great

[bjm4tt]

So how's the new 'favourites' now they put it in (not the same as old though?)
I'm still on 12, haven't tried 13

In the device browser predefined categories can be assigned to devices, or tagged with user created tags and you can filter by these categories/tags, even combine them. Not the same as favorite lists, but gets the job done.

In the patch browser it's similar, but the categories and tags are not the same as the ones in the device browser and they apply only to patches.

Thanks. I wonder if you can save those over to future updates though.
Still nor really clear why they ditched the old method, which was great

I'm on Windows, but I guess it's similar on Mac:

• The device tags and category associations are saved in a text file under Reason Studios\Metadata\rs_user_device_metadata.json. That's a plain json text file.
• The patch/sound browser favorite lists are stored in files under Reason Studios\Favorites\<EXAMPLE_FAV_LIST_NAME>.favo. This is a Reason specific format, not plain text.
• The patch/sound browser tag associations are under Reason Studios\Favorites\Metadata\rs_user_metadata.dat-wal. This again is Reason specific, not just a plain text file, but I could find it easily, the tag names and the patch names are not encoded.

This folder is located under my user home directory, for example Users\bjm4tt\Music\Reason Studios. The new User Library folder is located here too, it is the default path suggestion when saving a new patch.

[VOODOO U]

You are back on my block list.

See that folks? Reason users like to use blocks.

[hotmitts]

So how's the new 'favourites' now they put it in (not the same as old though?)
I'm still on 12, haven't tried 13

In the device browser predefined categories can be assigned to devices, or tagged with user created tags and you can filter by these categories/tags, even combine them. Not the same as favorite lists, but gets the job done.

In the patch browser it's similar, but the categories and tags are not the same as the ones in the device browser and they apply only to patches.

Thanks. I wonder if you can save those over to future updates though.
Still nor really clear why they ditched the old method, which was great

I'm on Windows, but I guess it's similar on Mac:

• The device tags and category associations are saved in a text file under Reason Studios\Metadata\rs_user_device_metadata.json. That's a plain json text file.
• The patch/sound browser favorite lists are stored in files under Reason Studios\Favorites\<EXAMPLE_FAV_LIST_NAME>.favo. This is a Reason specific format, not plain text.
• The patch/sound browser tag associations are under Reason Studios\Favorites\Metadata\rs_user_metadata.dat-wal. This again is Reason specific, not just a plain text file, but I could find it easily, the tag names and the patch names are not encoded.

This folder is located under my user home directory, for example Users\bjm4tt\Music\Reason Studios. The new User Library folder is located here too, it is the default path suggestion when saving a new patch.

Good to know, thank you

[SLiC]

Why are people here who don't want to discuss the new features in 13.1?

[SebAV]

Because there’s nothing to say about it ! It’s far more fun to talk about the same things as in every Reason thread !