I really don't see why should we the new guys go though all the pain of learning bit by bit what took you years to develop and figure out.
Happy you see it that way. Because, yes, apart from making a tool that I use myself, that was indeed the intention.
@danoise: Can you put some extra work into the RAS feature set? Seems with what you have already achieved with XStream, writing a style 2 bar pattern mapping script will be at most a day or twos work for you.
As stated in the xStream topic, I hardly have time to finish the new release ATM, so I can't fully participate on this project. But what I can offer - and what you'll need anyway - is guidance.
Because, it's really about getting familiar with a trinity of things:
1. intimate knowledge of Renoise itself (FX commands, note columns and group tracks, you name it...),
2. the Renoise API - what can it do, what it can't do. You don't have to know each and every detail, but it helps.
3. and finally, the xStream API itself - technically, powered by xLib, a library of classes that I've written to provide my own tools with higher-level functionality.
Of course you can jump right in and start using it (user scenario), but once you start writing new models from scratch (developer scenario), things will obviously get a lot more tricky
You will have moments where you think "WTF, why can't I do this?". And so, this is basically where I see myself as being most useful. Trying to help out, solve problems and making sure that xStream is a good platform for prototyping something like RAS.
The core PSR Styles logic and the Chord Analyzer can be two individual models in XStream. You can simply pipe Model A (Chord Analyzer) to Model B (Styles Mapper).
Good that you mention this. Because, precisely thing kind of thing (multiple models, multiple tracks) is what the next version of xStream will offer.
And due to various changes underneath the hood, it will even be more performant than the current one. I've spent a lot of time finetuning things, and there's still more work to be done there.
So, while I don't think xStream will be able to live up to FSus4' example of 64 concurrently streaming tracks unless you have a high-powered PC, it's already more than adequate for most performance situations where you are controlling a handful of elements simultaneously.
(as a sidenote: I regularly test my tools on a humble 8 year old netbook to be sure that CPU usage is reasonable)
Edited by danoise, 28 July 2017 - 11:10.