Firstly, a belated Merry Christmas to all of you I guess we are all busy with family and possibly quite a few who might be away from their dear ones as well, so best wishes to all and everyone. I love you all.
@noisemonkey wow, your last post was 12 years ago, amazing, so you dropped in just for Christmas I guess where were you during 2017 when I first joined?
To your point, I had this whole project preparation and even wrote the TOC, sent emails back and forth to the publisher (major one) and submitted it for review. Their editorial team gave back some helpful feedback regarding target market, sales potential, author experience and content mapping and selection. To be fair, the original TOC needs much rewrites as I probably then tried to masquerade Renoise in a generic music production book in an innocent effort to appeal to a wider audience in terms of readership who are not already familiar with tracker culture or tracker music software. That approach somewhat diluted the focus element when it comes down to projecting sales figures for a final book. Also, I was a fresh Renoise user and while I know my way around to get results, the innards of Renoise and its scripting was then very new for me as well. Additionally, more relevant workflows and academic music software processes and concepts that can be very well addressed while keeping Renoise as a focus was completely ignored from my end. In retrospect, I think now is the best time to reevaluate a better TOC and incorporate popular music production methods as well as combine academic music frameworks (such as Csound, CDP, PD etc), in a manner that brings the best of both worlds without being left wanting atleast in terms of the direction or intended audience(s). It is tricky and will need to be either 2 books or 1 with a well consolidated manuscript.
Then comes the question of do we even need such a book to which I would say an absolute YES. It brings merit to the entire culture and community of musicians and programmers and the Demoscene element which already has a few books extolling and exploring the history of the culture and its key elements, which is now recognized as a cultural heritage in Germany. Renoise is the culmination of how technology itself adapted to the culture of free music making and sharing around it, like Open Source music so any one can see the .mod files. The user manual does the job along with a plethora of trending and well made Youtube videos and the web blogs which are certainly doing their part in the evangelizing aspect of things. A book is a different feel though, even as a PDF download on Kindle/Nook/Pocketbook etc. I have quite a few tomes such as The Csound Book for instance and that it being present on my desk brings an entirely different and more authentic aspect to learning and reading about it.
Every Renoise user has their own production workflow, the more senior ones have a genuinely good grasp of how to work in Renoise, build scripts etc. Taktik possibly would be interested to contribute as well, but I think its best to try to come up with something more template based which can also not go over the head of the readers at least for a first offering. Just like MilkyTrackerX incorporates Csound, I think what we already have with the CDP Tool can be also done for Csound to get the best of literally everything one would need to make music on their computers, as we already have a million VSTs on each and every instrument and sample pack we can shake a stick at, so more options basically, like Csound for Live. Renoise can really benefit from this approach. Makes for good text material as well, as academic software has been around for 40+ years already, so its like two cultures meeting at a point in future. The average music listener on iTunes or a basic DJ producer (unlike BT who uses Csound extensively or folks of his brain/star power:)) won’t be too keen on using all these arcane code based music design and processing tools. But we are a leg up in this department as many of us do use such tools as well on a daily basis. I reckon at the end of the day its a matter of preserving legacy and responsibility to evangelize and educate others about something we all believe in as long term and long time users of a really good piece of music software.
Just a note, Blue by Steven Yi is a Csound IDE that also has a tracker note entry SoundObject, which is a timeline construct that takes tracker style inputs and converts to Csound score format. It is nowhere near the immediacy of Renoise or Schism tracker for instance and is very basic in its implementation as mostly a note entry abstraction but its there for those who can appreciate it. Cabbage converts Csound code to VSTs and its quite powerful and stands out with its premium offering. Especially if one can write their own opcodes in C/C++ and incorporate it inside the Csound framework as UGOs (User Generated Opcodes), the sky is the limit literally. Csound for Live already exists along with its Android port and WebIDE as well which does LiveCoding too; the rest of the academic softwares are somewhat behind in these departments. There is also something very timeless about textual programming inspite of having all these GUI widgets and VST export facilities on your table, it will stand the test of time. Similarly, I need to explore the Lua scripting for Renoise in detail which I am yet to see for myself in any detail to warrant my own feelings about it. So much to learn from all of you!