It will die, and that means ultimately the hardcore users lose as well. This is where pride in my conversations telling other musicians how I write ends, and why I haven’t convinced anyone else to pick it up now in years. This is where I feel responsibility lies, and where I feel Renoise has actually failed myself and others. Tracking is how I cut my teeth and how I prefer to write, and at the end of the day, Renoise is and has been the only serious option for modern Trackers. I depend on my plugin developers to keep relatively up to date, and I depend on my DAW developers to do the same. Now I rely on the functionality built into VST plug-ins because I need my core toolset to work everywhere. This got me off the ground for years, when Renoise was literally the only thing I could afford. It’s noted on several respectable ‘top x plugins’ lists that the best place to start for entry level musicians are the often very decent tools already built in to your DAW. I love that Renoise has built-in several core effects, as well as extensible utilities that in many ways goes beyond other DAWs. It’s awesome to have that path, and it probably solves the issue for several Renoise users. I can totally appreciate what you are saying. Hi interesting post i use to think the same as you …but ive noticed that producers every day are using more ducking (basically what we made in renoise signal follower+hydra+gainer) Staggering thought for the day: It’s going to be a seriously telling day when, given the context of history, Propellerheads implements VST3 support in Reason before Renoise developers make it happen. The hokery involved in connecting it all this way is phenomenal, not in a good way. Digging around, it seems other people have noticed that Neutron seems to be much less CPU intensive when run as a VST3 plugin, and Metaplugin makes this possible in both Renoise and Reason, both being only VST2 capable at present. I’m in the process of trying to use Metaplugin for Neutron, as I discovered that when running Neutron in Reason 9.5, the CPU is completely overwhelmed with 2 or more instances.
![sidechaining reason 9.5 sidechaining reason 9.5](https://ars.els-cdn.com/content/image/1-s2.0-S0008621521000239-sc1.jpg)
While DDMF Metaplugin enables side-chaining functionality between VST3 plugins, hosted plugins like Neutron are still impacted by that setting, which is…irritating. What I figured out was that if the option to run plugins in their own sandbox is on, Neutron (and likely other plugins) can’t see each other. I seem to be able to use Neutron either directly or within Metaplugin, but was having trouble where the drop-down in the Masking feature wouldn’t show any other instances of Neutron. Anyone else have this problem?Ĭurious if you’ve played with this more.
![sidechaining reason 9.5 sidechaining reason 9.5](https://d1aeri3ty3izns.cloudfront.net/media/19/191317/1200/preview.jpg)
However, it doesn’t seem to work with Izotope Neutron unfortunately.