Redux? Others functions of Renoise?There are so many things!
Think it will be a matter of time.I’m sure!Little by little they will perfecting native tools. Renoise is impressiveand grows.Always it is going to improvebecause it is obligatory in itself. But there you go on leaden feet. There are many ideas, some not suitable, others do. We must discuss them.You have to justify much!
This is what we have the good stuff.However, sometimes I think that some third-party tools for Renoise, what they achieve is to halt its development.“When I seean external toolI think, something is missingunder the hood ofRenoise”.
If you’re done, why implement native? But I would prefer that everything was under the hood of Renoise. That is the way I think, and forget the external tools (On the other hand, they make their service and costs a lot to develop them).The large number of external tools is great, but too a “drag” for Renoise(functions already supplied = not native).It’s just a thought. Nothing else.It will not be in general,I suppose.
Personally, I am delighted with the new things of Renoise 3.1and it has its priorities,but too I miss others, like everybody else.It’s hard to please everyone. ToRenoiseTeam, we should hang a medal for his great work. It’s great!
But look, In this post I stumbled upon this:
So better to do nothing.This is like flying a two-seater racing car, and suddenly your partner activates the hand brake.
I use irony:
Step 1) A usersays an idea “X”.
Step 2) Another user comments: “there are tools for that” (external tools)
Step 3)Do nothing and use external tools.
Step 4) Idea"X"ignored. No development under the hood of Renoise.
@Legendary Taunt. Have I answered you?This happens in many developments, not only in Renoise.
Not comment more!
Out of all the features available in Renoise since I’ve used it, the automation section got the least treatment. Then “tools” came around and people started adding their own functionality.
So actually, and forgive my frankness, but if you’re not a developer of renoise then … well no you haven’t answered my question. Maybe you’ve probably attempted to explain why it isn’t native, and you could sum it up by “well maybe that’s not a priority” which is fair. But in that case all the tools are just items that aren’t a priority right now to implement native.
I digress.
Fact is, the automation system could be improved on, but maybe it won’t. Thus to get quick and complex automation curves you have to use a specific tool for it. Which is also fine.
But what happens when the developer move on to other things and your favorite tool won’t work in future versions of renoise? This has happened before. Look at the earlier tools that were available for renoise previous versions. You can see the number of available tools decrease more and more.
So yeah, why not just implement it native instead of relying on the support of another developer? That’s my question.
One could say “well learn how to code”. Which I have mixed feelings about.
Anyhoo. Done with this topic. Enjoy your day and let’s keep things positive everybody.