Anyway… I also pictured this “plug-in within plug-in” feature and could see some advantage with it, the plug-in grabber tool for instance. But when I think of it… It perhaps is not as easy as one would imagine. But I have no clue… Is there any other plug-ins which have “VST/AU within VST/AU”- kind of feature?!
Moreover, I think they just should release it as it is now as there will always be things to improve.
Anyway… I also pictured this “plug-in within plug-in” feature and could see some advantage with it, the plug-in grabber tool for instance. But when I think of it… It perhaps is not as easy as one would imagine. But I have no clue… Is there any other plug-ins which have “VST/AU within VST/AU”- kind of feature?!
No idea how hard it would be buthereare a few examples (edit: a few morehere,hereandherewhile we’re at it). I’m thinking the harder it is, the better it might be to wait if they plan to extend .xrni’s to utilize plug-in instruments more in Renoise. The most obvious maybe being several mappable ones going through plug-in effects. They could then focus on porting it all to Redux, knowing they had something really substantial on their hands. Maybe warranting a paid upgrade (2.0?). If extending .xrni’s is the harder part, just having what’s in Renoise now, i.e.samples-only through effect plug-ins, a single plug-in instrument,would be great in the meantime. Or just make the plug-in grabber model plug-in instruments 1:1 with all controls, etc.
No idea how hard it would be but here are a few examples. I’m thinking the harder it is, the better it might be to wait if they plan to extend .xrni’s to utilize plug-in instruments more in Renoise. The most obvious maybe being several mappable ones going through plug-in effects. They could then focus on porting it all to Redux, knowing they had something really substantial on their hands. Maybe warranting a paid upgrade (2.0?). If extending .xrni’s is the harder part, just having what’s in Renoise now, i.e. samples-only through effect plug-ins, a single plug-in instrument, would be great in the meantime. Or just make the plug-in grabber model plug-in instruments 1:1 with all controls, etc.
Another plugin within plugin example is Image Lines Minihost modular.
No idea how hard it would be buthereare a few examples (edit: a few morehere,hereandherewhile we’re at it). I’m thinking the harder it is, the better it might be to wait if they plan to extend .xrni’s to utilize plug-in instruments more in Renoise. The most obvious maybe being several mappable ones going through plug-in effects. They could then focus on porting it all to Redux, knowing they had something really substantial on their hands. Maybe warranting a paid upgrade (2.0?). If extending .xrni’s is the harder part, just having what’s in Renoise now, i.e.samples-only through effect plug-ins, a single plug-in instrument,would be great in the meantime. Or just make the plug-in grabber model plug-in instruments 1:1 with all controls, etc.
All right. But is it already known that Redux will not have VST/AU-import compatibility? I thought I read somewhere that it will have the plug-in grabber, that would satisfy me personally for a while!
All right. But is it already known that Redux will not have VST/AU-import compatibility? I thought I read somewhere that it will have the plug-in grabber, that would satisfy me personally for a while!
Someone from the team can answer decisively but from what I understand, it won’t. Guessing what was meant is that you can use the plug-in grabber in Renoise?
Someone from the team can answer decisively but from what I understand, it won’t. Guessing what was meant is that you can use the plug-in grabber in Renoise?
Not sure I understood what you meant, but yes I can always use Renoise for plug-in grabbing purposes. It was just that - in matters of Redux - the job would be done quicker in most cases if Redux also had this feature.