You have no idea what we developers have to do to keep basic compatibility going these days. And it's definitely not 'the least a developer can do'.
#AUDULUS VS REAKTOR SOFTWARE#
If you start using new tech, you better make sure the software you want to use is compatible. I assure you, hiDPI support is *not* in the top 10 of most requested features for our products and thus it is not something you prioritize over all else. 'Upgrades' have new features or new functionality, whatever has been prioritized on the backlog or is important according to either management or customer feedback. If you choose a tech to support, that's another set allotment of total development time to be dedicated not only to the development of a feature, but to the maintenance of it.
You can't just pick a tech and say "yeah, it's your job to support this because I think it's important to this group of people". High dpi screens may be useful for people with bad eyesight, but until it existed the older tech sure did the trick. Do you even realize how many new technologies or revisions to old technologies get brought to the table every year? You can't keep *all of them* in sight. To me, at least.Ĭlick to expand.Not really. I'm sure the maths and physics will eventually translate to other gear. Reaktor as a product makes me excited and happy so it's what I'll be using for now. If development finishing up on a piece of kit bothers you, avoid Reaktor and go for VCV or something else that is actively being developed. But if you're doing it because the 'tech industry' is telling you it's the right move, I asure you it's lying.Įdit: Look, do whatever you like. Unless chasing that stuff makes you happy, in which case, by all means. Choosing tech based on 'ascendancy' is spanning the cart before the horse. It doesn't matter what tech you invest in, as long as it suits your needs. I use MVC because it makes sense to me and at this point I've become damned good at it. I chose C# way back when because I liked how it worked and it functioned exactly as I liked. If you choose technology based on what's evolving fastest you'll never master what you're working with and you'll always be chasing a unicorn. I don't give a rat's ass if Angular is the bestest most rapidly advancing thing, I'm not going to be using it because I don't gel with it. In fact, it's going to do you no good at all. If nothing you're going to use or write requires Python, there's no point in learning it when Perl will do. But if you need to work with something that requires Perl or Pascal or even Kobol, that's what you learn. If you want to work in Ren'py, of course you're going to learn Python. I see it happening all around me and it's so absurd. The signal can then be manipulated further by "Effects" such as distortions, filters, delays, and mastering plugins.Click to expand.Yeah, I don't get it.
#AUDULUS VS REAKTOR GENERATOR#
Signal synthesis is performed by "Generators" such as synthesizers, noise generator functions, samplers, and trackers. JSTOR ( December 2009) ( Learn how and when to remove this template message)Ī modular software music studio consists of a plugin architecture that allows the audio to be routed from one plugin to another in many ways, similar to how cables carry an audio signal between physical pieces of hardware.Īll aspects of signal synthesis and manipulation are handled entirely by the plugin system.Unsourced material may be challenged and removed.įind sources: "Modular software music studio" – news Please help improve this article by adding citations to reliable sources.
0 kommentar(er)
