I have Reason 11 too. The Suite Version. I wait for next Renoise Update to use Complex-1 in Renoise as a Reason Rack.
Reason Rack is a VSTi3 but the Reason 11 standalone dont Support other VST3 Instruments, thats fact.
And it cant send midi out to use the Players inside another daws Instruments
2 Likes
taktik actually did reply to that, VST3 is tentatively planned AFAIK, but you won’t get to that info by spamming the same post 3 times, you get to that by reading.
And you speak like you know anything about the costs in man hours or the Renoise sales, but it’s a very a low priced niche tool, in a niche market. I wouldn’t even be surprised if it was a net investment, rather than a financial gain. Talking about “companies showing they are dedicated to listening to customers” is totally off-base marketing speak. Renoise devs actually do respond, they just don’t make a song and dance about it.
6 Likes
I’m actively using dozens of VST3s in Reason 11 right now. VST3 in Reason 11 is a reality. No idea about the specific issues you’re hitting, but VST3 absolutely works. I’m literally using it.
Using Reason with any other DAW for midi is generally just using Rewire - that’s what it’s for. There are Midi tools in Reason for interacting with external hardware, that work fine if you have midi networks for local functionality as well. VST support means many other tools to accomplish the same thing as well. Tools like midiox or copperwire, both free, can get you anything you want, if you even need them at all. None of which is VST3 related, but tack on as many problems as you want, there is a solution … any of which can be easily googled and solved.
Maybe it’s the page not loading the entire thread at once, or maybe taktik doesn’t explicitly use “VST3” in his reply, but I actually did search this thread for responses - both through the browser and through the Renoise search functionality.
There are responses on the Trackers group in Facebook as well, and it sounds like it’s a beastly overhaul to even come close to making this happen, based on the way the code is written.
You might be talking about more recent activity, but tell me exactly how long it’s been between updates? Yeah, I don’t know of any other DAW or most tools of any scale less responsive to their community. Regardless, as I clearly stated, there are solutions to this problem that could greatly benefit the community that Renoise development has chosen not to pursue, leaving, again, not only VST3 support, but a great many other feature requests long unresolved.
I’m a developer. I’ve worked across the industry, from Microsoft, to companies with 3 developers. I know what it means to code, I know what it means to be responsive to customers. I know exaxtly what it means, and I know when it’s not being done. And as stated, the developers themselves stated clearly they have other responsibilities that put Renoise on the back-burner.
But you don’t get to those posts while you’re busy trying to shoot down long-standing users over real issues that maybe you just don’t care about as much as others.
Can’t you just write your own tracker program that is built to your own specification?
5 Likes
I’m actively using dozens of VST3s in Reason 11 right now. VST3 in Reason 11 is a reality. No idea about the specific issues you’re hitting, but VST3 absolutely works. I’m literally using it.
@EnergyCrush You miss something, Reason 11 currently doesn’t support VST3:
The Rack plugin is a VST3 plugin. And you can use VST3’s in Renoise, when you use a wrapper:
I’ve used this wrapper with Renoise 3.2 on my windows 10 maschine. Works fine with some smaller quirks. Its a workaround, till Renoise support it natively.
2 Likes
No vst 3 in reason my friend,I smell bullshit.
2 Likes
I use it myself and can assure that vst3 is not supported by reason 11 itself.
You are confusing something
3 Likes
If I made it my job to write a tracker program and then support my customers using it, absolutely.
But better yet, as I mentioned, would be to open source Renoise so any active developer could add onto the existing platform, as well as any other additions that have been wanted. People keep mentioning Renoise Dev doesn’t make enough money to support it properly, and the devs have indicated themselves they’ve moved in to other projects primarily. Seems pretty reasonable.
1 Like
See https://forum.renoise.com/search?q=vst3%20category%3A11 and
https://forum.renoise.com/t/never-a-better-time-than-now-to-add-vst3-support/58030/2?u=taktik
please.
4 Likes
Why not make it a hobby? You’ll be your own boss. You can decide what goes in into your program and how much time you want to spend coding on it. You can decide how much time you want to spend on maybe a forum you’ve set up (or github) reply (or ignore) your customers asking/demanding for updates/features that you can accept/reject.
1 Like
taktik, I greatly appreciate all your time and effort and everything that you’ve done to help and respond to questions. You’ve been awesome on the forums, and immensely dedicated to Renoise and users needs.
There’s been one single choice for VST-based trackers for years now for writing music, and hundreds of songs marking my history with Renoise.
But as functional synths and effects have grown, as Steinberg has long-past deprecated the VST2 standard, and as I’ve had time to test several dozen plug-ins that have both VST2 and VST3 versions across full versions of most majors DAWS while additionally running into VST performance limitations in Renoise while producing music, it’s become incredibly painful.
VSTs in a tracker, I feel, has been the specific power and legacy of Renoise, in part because there are plenty of other trackers that do much of the other pieces (though admittedly I’ve never felt most of them have done it nearly so cleanly).
While I’ve started to feel the pull of contention in responses to my posts, the root and only point I was making, and wanted to, is that after 15+ years, I just … I’m burnt waiting. I really don’t expect anything to change, and really, I’m not angry at Renoise or the devs at all … I only wish open-sourcing it or elevating that core element could have happened. I can understand why it didn’t, I’m not beyond logic about this, I’m just … done.
Thanks taktik, for everything.
Lol …
It’s an honest possibility. The last year has seen a transition to a job where I develop remotely full-time, which has allowed me to marry my wife in Mexico and live in both places simultaneously, two weeks at a time in each, in Mexico with her, then back here with my two children.
It means refamilirizing myself with C++ most like, as I’m sure the performance is needed. I don’t mind asynchronous multi-threaded programming, or learning new APIs. Possibly the loss of actually writing music to develop a program allowing VST3 tracker-based music would be worth the time and effort given where I’m at.
All things in time. All things in time.
All the best, EnergyCrush, with Reason and everything. Hope you will someday find (og make) a tracker with VST3 support.
Here’s the fact. Reason 11 doesn’t support VST3.
Screenshot from the Reason 11 operation manual:
You can read it at page 370.
1 Like
You’re absolutely right, and I am absolutely wrong on that front - I was certain I had specified my VST3 path. I keep all of my VST2 dlls in a custom folder, and everything very organized. After seeing a couple responses to this, I dug more online, and went back and validated those settings, and yes, it turns out I was flat out wrong about VST3 support already being there in Reason. Some of the plug-ins I installed I thought I had installed only as VST3, but either I missed a setting, or they installed the VST2 versions under the covers and I didn’t know they were there. Regardless, you’re absolutely right, VST3 is not there in Reason yet.
Guess it’s a race at this point. Working primarily in Windows, but like cross-compatibility. Ableton no VST3. BitWig still has weird random issues. Samplitude and other Magix DAWs (Music Maker, Sequoia, etc.) have problems with many VST3s that other DAWs don’t (like Dmitry Sches Thorn), even when just reloading them or resetting patches. I’m not certain that applies to the new ACID and subsequent VST3 implementation yet, haven’t had time to load and validate everything since they added, but they’re owned by Magix now too. MuLab, Mixcraft, Tracktion, Stagecraft, Multitrack Studio, Digital Performer, NTrack, Audition, Audio Mulch, Cantibile, and many others either also have problems with VST3 or don’t support it. Maschine still isn’t full featured and also no VST3 support. Pro Tools … yeah.
There are several DAWs that do work well with VST3 … but first, aren’t trackers, and second, have other limitations that make portability or usability painful. Steinberg Sequel doesn’t support 64-bit, Cubase still requires a dongle. Reaper is well-loved by many, but is complicated to setup for efficient workflows, and it shows all plugins at once, of all types and bitness, making it a bit of a navigational nightmare. FL Studio has made an incredible number of advancements, but I haven’t been able to get into the workflow … beings it supports video, though, it has serious potential when I’m making music for movies or video. Studio One has also been incredibly functional, but again the workflow feels … weird, like when adding different effects processors.
Reason has been the only other DAW that has felt relatively clean and in-tune compared to the otherwise very different workflow of Renoise. I’m kicking myself now for mistaking the VST3 implementation, but pound for pound am finding it a reasonably performant alternative, and they’re certainly actively moving the code base and functionality along on a consistent basis.
Maybe I want too much? I don’t know. Maybe the new i9 mobile laptop will provide the performance I need to keep rolling wherever, especially traveling back and forth to Mexico to spend time with either my wife or children between everything else.
Either way … yeah, it’s been a lot of searching, testing, waiting, bashing along, trying to get to a solid portable completely electronic VST instrument and effect based system. I thought the track freeze add-on for Renoise would help that some, but it’s wonky and unreliable for as frequently as I need to unfreeze and mod tracks.
Someday man … someday. Someday.
1 Like
Yes, a lot DAWs have problems with VST3. Even inside Cubase. Funny enough, because Steinberg is the inventor of the VST format.
VST3 also lacks a lot functions which are possible/available in VST2. Like e.g. MIDI input/triggering for effect VSTs. It’s frustrating (for me as a VST developer) while working on a new VST plugin, but you can’t realize the feature you ever wanted to implement because of limitations of the VST3 format. VST3 also still is very buggy. This can be a problem for new VST companies who were founded after October 2018. Because of the new licence agreement for VST developers. After October 2018 founded companies are forced by these agreements to develop only VST3 , because VST2 licences were dropped by steinberg since Oct 2018 for new developers who missed to sign the licence agreement before that date. So new companies are forced to develop buggy shitty VST3 plugins…
…and i think this is also the case, why the Reason VST rack is just available in VST3 because the (ex) Propellerheads missed to sign this agreement. The Europa VST is VST2, but it was released before Oct 2018…
2 Likes
I remember reading a recently about the license transition, yeah - I can appreciate the frustration, especially given the challenges of implementation with VST3 that are frequently mentioned. That makes sense about the Reason VST rack as well.
I haven’t run into the MIDI input/triggering issues specifically yet, I’m curious … I use and much love iZotope’s Stutter Edit from BT, which has a VST3 version, and is a MIDI triggered FX processor (I had to go and look to be sure I wasn’t managing to talk out of my @$$ again …). Since DDMF’s Metaplugin hosts and makes MIDI available to VST3s (and I believe Blue Cat’s tool as well), I’m wondering if there is some work around these companies have implemented themselves to work around that limitation or something else. I haven’t done any VST2 or VST3 programming yet (though I’m highly interested in getting started, I think with a VST3 host, so if you have any pointers or links that might be a good place to get started, I’d be highly interested … most of my programming is in Python or C# these days, but I’m not bothered about jumping back into C++ or another language if there’s something newer and still performant enough for such work … looking around, seems like the GUI language landscape for something like a DAW or plugins has shifted quite a bit, will have to dig more on that front as well).
It’s good info, thanks 
Ah - I missed that Ableton has actually now added VST3 support as of the v10 release:
https://www.ableton.com/en/live/
Plug-in Support
New in Live 10.1:
- Introduced support for VST3.
- All plugin settings now appear in a dedicated “Plug-Ins” tab in the Preferences.
- Introduced system folders for VST3 plug-in scanning. Also added a button to the “Plug-Ins” Preferences tab to enable and disable system folders.
- Introduced sidechain support for all plug-in architectures, and added a sidechain view to the left of the X/Y control in the plug-in device view.
- Additional audio input and output buses from VST3 plug-ins can be used from track “Audio To” and “Audio From” routing choosers, as with VST2 and AU plug-ins.
- For VST3 plug-ins with less than 65 parameters, the parameters are now auto-assigned after instantiation. Also, when copying a VST3 plug-in or loading a Set with VST3 plug-ins, the parameter assignment (and value) is retained. Furthermore, VST3 parameter automation is now available.
- VST3 plug-ins are now scanned via a separate background process. Plug-ins that crash during the scanning process no longer cause Live to crash. In addition, Live will not wait during startup for the plug-in scan to finish, which means having a large number of installed plug-ins will not slow down Live anymore (this is only implemented for VST3 for now). The background scanning can be disabled with the debug option “-DisableBackgroundPluginScanner”.
Yeah, it really is making traction, and challenging as it sounds, it’s for a good reason.
Mickey
Renoise = 68€
Reason 11 = 349€
“Arms race” in music producing is a bit hard to understand for me , what makes good music is not VST3 support or 80GB sounbanks recorded with 1billion dollar microphones but work and creativity.
As long as i’m having fun and enthusiasm making music I dont care about being able to using the latest technologies.
I read the same complaints on the Native Instruments forum about the lack of VST3 support with Maschine, come on guys you all have gears and software that we never dared to dream about 20 years ago.
The permanent “we want more” tire me out…
5 Likes