Re: No more NDA!
Posted: 31 Jan 2020
Kontakt is like comparing apples to oranges.Enlightenspeed wrote: ↑30 Jan 2020In which case I need to repeat this:
How are Reaktor and Kontakt getting on, in this regard?
When did the first free, or cheap VST compatible host come out that you could test with?
The plugin version of VCV Rack (to be released alongside 2.0) will cost around $99, i e slightly higher than Reason Intro.
You can't dev for them without owning the full versions of the program, though.
Hasn't always been the case though, and it used to be that you WOULD need a license for either Cubase or Logic to be able to dev. Apologies if it isn't clear here that I'm concerned mostly with the developer perspective in my post.
Yeah, tell me about it However this suits me down to the ground because it allows me to be faster about what I'm doing if all I have to worry about is my devices and not the hassles and expenditure of money and, more importantly lost time, that I would incur should I have to develop web, shop and security services.
No need to apologize. I'm thinking about the developer/business perspective too, thats why I want a free Reason Rack Player Plugin (still going through shop, etc) that would be bundled with REs. I've made that request in another forum too.Enlightenspeed wrote: ↑31 Jan 2020Apologies if it isn't clear here that I'm concerned mostly with the developer perspective in my post.
Maybe it could be a bit more limited, so ppl are "forced" to buy Reason. Maybe only 3 devices or something like this.eXode wrote: ↑31 Jan 2020No need to apologize. I'm thinking about the developer/business perspective too, thats why I want a free Reason Rack Player Plugin (still going through shop, etc) that would be bundled with REs. I've made that request in another forum too.Enlightenspeed wrote: ↑31 Jan 2020Apologies if it isn't clear here that I'm concerned mostly with the developer perspective in my post.
Starting to understand the whole properties thing and i see where ownership is an issue with pattern devices.artotaku wrote: ↑30 Jan 2020I think there may be way to improve remote support for pattern based players/devices that are mostly custom display based. For the custom display use string properties as described above. For the remote codec it may be sufficient to use runtime properties that are the "view" subset of the string properties because a midi controller can only show e. g. one pattern or a certain step length at once. The thing is that midi controller typically has much fewer elements it can display (LED buttons etc) and does not need to know about the persistent state. We also have to take into account that remote codec input/output properties cannot be string properties. There is a restriction when you try to use them in the codec. So you can only use number properties.buddard wrote: ↑29 Jan 2020
It’s because the motherboard is limited to 1024 properties, and those slots fill up fast if you implement a multi pattern device. For Step, I chose to forego multiple pattern support in favor of maximizing Remote and automation support.
For Sequences, we definitely wanted multiple patterns, so we decided to encode the pattern data into long string properties, which of course makes Remote/automation support impossible.
But there’s also a usability aspect to this, since each parameter+pattern combination would have to have separate Remote objects. So you couldn’t for example toggle mute on step 3 in two different patterns using the same button without a really advanced Remote codec.
Redrum can do this, but it’s not an RE and doesn’t adhere to the same limitations.
This is how I do it with a RE I´m working on currently. So big document owner string properties that are modified by the custom display but runtime number properties to pass the state to the remote codec. The runtime (C++ part) supplies the remote codec with the necessary state it needs.
I think it would have been completely possible to make e. g. ReasonStudios Dual Arp fullly remotable for e. g. Launchpad like controllers.
But it is increased development effort since you have provide a specific Remote codec that works for midi controllers by different brands.
Like almost everyone else here, I too made the request for a free player (before realizing I was not the first!). But I went further and even suggested it would only host ONE Rack Extension at a time, to avoid any of the possible negatives mentioned by others (and many disagreed with this idea, IIRC).
The paywall also exist with Kontakt, where some extensions nee full Kontakt.selig wrote: ↑31 Jan 2020Like almost everyone else here, I too made the request for a free player (before realizing I was not the first!). But I went further and even suggested it would only host ONE Rack Extension at a time, to avoid any of the possible negatives mentioned by others (and many disagreed with this idea, IIRC).
I say this because I believe there is a market for "non Reason" users to use Rack Extensions, which IMO is a different market than Reason users. And these folks likely don't want a $99 paywall in front of using Rack Extensions - no other plugin format has one.
Yes, the beauty of Reason is the interconnectivity of the rack, and yes, the limitation of only loading one RE at a time means no "Reason experience".
But IMO, it would act as a way to dip your toes in the shallow end of the Reason pool: buy an RE, get the free player, which leads to getting more REs, and which may or may not lead to a Reason purchase (but that's not the point - it's a bonus).
Reason Studios gets $$ for every RE sold, so this is a win/win and a way to open the market to a wider audience than if you limit access to those who own a version of Reason.
Good suggestion, sounds win-win to me.selig wrote: ↑31 Jan 2020Like almost everyone else here, I too made the request for a free player (before realizing I was not the first!). But I went further and even suggested it would only host ONE Rack Extension at a time, to avoid any of the possible negatives mentioned by others (and many disagreed with this idea, IIRC).
I say this because I believe there is a market for "non Reason" users to use Rack Extensions, which IMO is a different market than Reason users. And these folks likely don't want a $99 paywall in front of using Rack Extensions - no other plugin format has one.
Yes, the beauty of Reason is the interconnectivity of the rack, and yes, the limitation of only loading one RE at a time means no "Reason experience".
But IMO, it would act as a way to dip your toes in the shallow end of the Reason pool: buy an RE, get the free player, which leads to getting more REs, and which may or may not lead to a Reason purchase (but that's not the point - it's a bonus).
Reason Studios gets $$ for every RE sold, so this is a win/win and a way to open the market to a wider audience than if you limit access to those who own a version of Reason.
Thanks Martin.Martin Fridegren wrote: ↑31 Jan 2020Good to see! Please note that you are required to include the RE License agreement in your project. Please add it, you may find the agreement here:Koshdukai wrote: ↑30 Jan 2020Now it's possible to publicly share things like this without breaking the NDA:
https://github.com/fredwillmore/SI2/blo ... README.txt
https://developer.reasonstudios.com/agr ... _agreement
It is also included in the SDK as a txt-file under /SDK/Licences
From the license file:
"With the exception of Rack Extension products distributed via Reason Studios' Shop, this license agreement and the copyright notice included herein must be distributed together with all copies of any results from your use of the Rack Extension SDK."
Best Regards,
Martin
Reason Studios
I was thinking the same thing. A single-device rack plugin wouldn't compete with Reason at all, even if you bought the Synapse bundle. An RE-only customer would still get full use of all the individual instruments and effects in their DAW, but chaining, CV, Combinators, and mixers would all require a Reason license. I really think this would hit a sweet spot where there's value for non-Reason users in having these REs by themselves in a DAW, but there's also an implicit teaser that you could do a lot more with them if you bought Reason.selig wrote: ↑31 Jan 2020Like almost everyone else here, I too made the request for a free player (before realizing I was not the first!). But I went further and even suggested it would only host ONE Rack Extension at a time, to avoid any of the possible negatives mentioned by others (and many disagreed with this idea, IIRC).
I say this because I believe there is a market for "non Reason" users to use Rack Extensions, which IMO is a different market than Reason users. And these folks likely don't want a $99 paywall in front of using Rack Extensions - no other plugin format has one.
Yes, the beauty of Reason is the interconnectivity of the rack, and yes, the limitation of only loading one RE at a time means no "Reason experience".
But IMO, it would act as a way to dip your toes in the shallow end of the Reason pool: buy an RE, get the free player, which leads to getting more REs, and which may or may not lead to a Reason purchase (but that's not the point - it's a bonus).
Reason Studios gets $$ for every RE sold, so this is a win/win and a way to open the market to a wider audience than if you limit access to those who own a version of Reason.
Well put, I agree completely.selig wrote: ↑31 Jan 2020Yes, the beauty of Reason is the interconnectivity of the rack, and yes, the limitation of only loading one RE at a time means no "Reason experience".
But IMO, it would act as a way to dip your toes in the shallow end of the Reason pool: buy an RE, get the free player, which leads to getting more REs, and which may or may not lead to a Reason purchase (but that's not the point - it's a bonus).
Reason Studios gets $$ for every RE sold, so this is a win/win and a way to open the market to a wider audience than if you limit access to those who own a version of Reason.
I dabbled with the idea (inside my head) of a wrapper that only allows one RE but that comes with i.e. one fixed Pulsar for some basic modulation routing goodness (for an example).challism wrote: ↑01 Feb 2020I agree with the idea of a free RE wrapper. That is really the only way I see this attract new developers, new REs and new buyers. The RE market has not been a good one the last year or so. I also agree that it should be extremely limited, but one device seems too limiting to me. To truly give the user a taste (tease) of Reason, they should be able to use at least two devices. Twos is enough to let them hook up a player to a synth, or an LFO to some effect, and really play around with the back side of the rack. It might also encourage them to buy more REs to use together or entice them to buy, at the very least, the $99 version.
The 30% they earn from each RE sale isn't money?pongasoft wrote: ↑01 Feb 2020I am not convinced that a free RE wrapper which can host only one RE is right. The true power of Reason is how you can connect each other in truly unique fashion. You have to remember that Reason Studios take a cut of every single RE they sell... so even if they were to provide a free RE hosting platform that can host as many RE as Reason, it's not like they would not make any money of of it.
That is what I am saying (just reread the sentenceeXode wrote: ↑01 Feb 2020The 30% they earn from each RE sale isn't money?pongasoft wrote: ↑01 Feb 2020I am not convinced that a free RE wrapper which can host only one RE is right. The true power of Reason is how you can connect each other in truly unique fashion. You have to remember that Reason Studios take a cut of every single RE they sell... so even if they were to provide a free RE hosting platform that can host as many RE as Reason, it's not like they would not make any money of of it.
I guess rewriting the built-in devices as REs would be a difficult task, and even impossible for some of them on the current SDK.Boombastix wrote: ↑01 Feb 2020A limited RRP is surely the wrong move, just gives users a bad taste. Better to arrange with in app purchases like most modern apps. Thor $29, Maelström $19, Subtractor $9, REs att current shop price, etc.