Jump to content


Photo
- - - - -

How to best contribute towards Renoise's Development?


  • Please log in to reply
6 replies to this topic

#1 Zhu

Zhu

    New Member

  • Normal Members
  • Pip
  • 6 posts

Posted 28 March 2018 - 20:51

I might be picking up programming in LUA and I know a bit of C++ and will be reading books on audio engineering. I was wondering how possible it would be to learn how to make certain features added on to Renoise or to continue development on this wonderful DAW since Taktik may be taking and indefinite leave of absence for production on Renoise?

 

I want to make new tools, update some old ones that have become obsolete and make educational content on this program. I don't want to void my own license if I want to study this program further (I don't plan to open things up, and much more, I don't even know how.)

 

I'll be starting on XRNI tools of my own and see where else I can go with this, either making plugins of my own and see how much I fail or not, then see if I can replicate or solve features people ask for frequently on the forums.

 

So I guess to Danoise or anyone else reading, what do you think the best approach would be to help this program out?


  • ffx and Raul (ulneiz) like this

#2 danoise

danoise

    Probably More God or Borg Than Human Member

  • Renoise Team
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 6749 posts
  • Gender:Male
  • Location:Berlin
  • Interests:wildlife + urban trekking

Posted 29 March 2018 - 09:52

I want to make new tools, update some old ones that have become obsolete and make educational content on this program. 

 

Great! One tip: reach out to the author and get permission before updating a tool.

Just like you would, if you were to remix someone else's song, etc. :)  

 

Other than that, it sounds like everyone could benefit from this. 


Tracking with Stuff. API wishlist | Soundcloud


#3 Raul (ulneiz)

Raul (ulneiz)

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1290 posts
  • Gender:Male
  • Location:Spain

Posted 29 March 2018 - 11:28

I might be picking up programming in LUA and I know a bit of C++ and will be reading books on audio engineering. I was wondering how possible it would be to learn how to make certain features added on to Renoise or to continue development on this wonderful DAW since Taktik may be taking and indefinite leave of absence for production on Renoise?

 

I want to make new tools, update some old ones that have become obsolete and make educational content on this program. I don't want to void my own license if I want to study this program further (I don't plan to open things up, and much more, I don't even know how.)

 

I'll be starting on XRNI tools of my own and see where else I can go with this, either making plugins of my own and see how much I fail or not, then see if I can replicate or solve features people ask for frequently on the forums.

 

So I guess to Danoise or anyone else reading, what do you think the best approach would be to help this program out?

 

I'm glad to see that someone is so encouraged with the issue of creating tools. I suggest some steps to follow (from a humble point of view):

  1. Examine Renoise thoroughly, to know their most striking deficiencies. There are many improvable details, in the sense of improving the speed of the work flow, especially in repeated operations. Here is "a technique" that I have used to proceed: I call it "anti-clockwise": Imagine that Renoise is a clock rods. You can start with the pattern editor, then with the matrix editor, then with the dsp chains, then with the automation editor, then with the instrument box and then with the instrument editor and all its parts. You can proceed in this way, by sweeping all Renoise in this orderly fashion, following the opposite direction to the hands of a clock.
  2. Examine the Renoise API to know its limitations (the available documentation). There are certain things that can not be done. This will save you time. You can use the previous technique "anti-clockwise" too.
  3. Once you have a general idea of what you can program and what you can not program, try to build your own tools, with what you think is useful. You can be inspired by the requests of many users. But most are small things here and there.
  4. Share code in the scripting forums. Tricks, things that you think interesting. On many occasions we fall into the error of commenting on code without writing it. In many scripting questions you will see solutions without writing code. I think the best way to enrich the scripting forums is to discuss with written code.
  5. I would not try to improve or update others' tools. Each person should be responsible for the maintenance of their tool. If a tool becomes obsolete, simply forget it or create your own. This will save you headaches and time.
  6. Creating interesting tools can take a long time, and in my opinion, is very little valued by the community, possibly due to ignorance. Try to invest it in what is really useful.
  7. One very interesting thing is to publish LUA code videos. How to build a basic tool? The video does not have to be correct with the code. It would be very interesting to do something else, move forward when it comes to building tools for Renoise. But I recognize that this is a huge job.
  8. Finally, you ask anything concerning scripting that you have not previously been able to locate in the forums advanced search. Surely someone can help you...
  9. Do not expect multiple tools to improve Renoise. Renoise can only be improved under the hood, with new versions. Consider the tools as small add-ons and be very careful with operating errors. This will allow you to focus on your tools and forget that Renoise "seems abandoned".

Courage! See you in the forums ...  :lol:

 

Edit: It's never too late. When I started in these forums I thought I arrived too late. Even so, you will find hours and more hours of fun. If you love the code, it is as rewarding as composing music. You are creating new things!!!


Edited by Raul (ulneiz), 29 March 2018 - 11:48.

:excl: Development of my tool: GT16-Colors

 

:excl: My API wishlist R3.1 (updated 24 July 2017):

Spoiler

 

:excl: My Renoise 3.1 wishlist (updated 26 September 2017):

Spoiler

#4 Raul (ulneiz)

Raul (ulneiz)

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 1290 posts
  • Gender:Male
  • Location:Spain

Posted 29 March 2018 - 11:44

By the way, I forgot to answer your thread question: Buy a license. Have others buy a license. Advertise Renoise! It is so logical. If there is no money, there are no updates. As simple as that.


  • Achenar and Neurogami like this

:excl: Development of my tool: GT16-Colors

 

:excl: My API wishlist R3.1 (updated 24 July 2017):

Spoiler

 

:excl: My Renoise 3.1 wishlist (updated 26 September 2017):

Spoiler

#5 Zhu

Zhu

    New Member

  • Normal Members
  • Pip
  • 6 posts

Posted 29 March 2018 - 18:47

I've bought a license for myself and bought a license for my friend because I love Renoise so much. I advocate it on Twitter and rave about how fast the work flow is paired with Reaper.

 

I would love to create tools or use other DAWs, such as FL Studio, Ableton Live, Bitwig, Cubase, Logic Pro, Reason, and have Caustic and Sunvox on my iPhone / iPad.

 

I want to see if I could find a way to create portable versions for Renoise, or eventually develop my own DAW with a similar philosophy to Reaper where people should pay but will not be stripped away from their options to slap them on the wrist.

 

I feel like increasing access to users only empowers them and improves the music making community.

 

Thanks Danoise for your encouragement, it means a great deal to me and when I reach that phase where I've delved into my own scripting and built confidence in myself this year, I'll try to message Taktik and see where I can go from there.

 

To Raul:

 

1. I would like infinite nested groups, the ability to select multiple tracks, to be able to create a horizontal moving track list where the notes show up vertical. I'd also like more features like being able to turn the tracking part more into the whole Ableton Live looking scheme which probably would require insane amounts of work. I'd also like to make LFO shaping and Automation Shaping with curves more adjustable like how Serum does it, or other programs. It'd be fun to make drawing tools possible so people with pen tablets like the Intuous can create really interesting effects. There's some issues with the Modulation tab from what I've read on the forums with inaccuracies or discrepencies. Native pitch shifting tools, a saturator, and other wave table shenanigans like Frequency Modulations or Detuners would be really nice for me. There's a lot of great Renoise tools that I think could benefit by becoming native. I don't know to what degree I'd be able to do all of this. I also think rebrushing up on calculus would give possibilities to make 3D wave tables similar to the ones in Serum. Adding the scream filter from Redux to Renoise too would be lovely.

 

There's a numerous amount of possibilities to open up once I learn more out of programming, but the main issue I have is time and energy. I know the labors of programming from working with one who is making an indie platformer game of dis design in C++. A lot of it is grueling work and testing, having others figure out bugs. For me I would want to learn or teach others how to delegate or break up these tasks to the users so if they wanted to help they could integrate it in my process if I have an off day or a season where I have to dip and work on something else to get money or finish a big project.

 

2. I'll look at your API  wishlist and try to figure out what's doable. Programming is black magic, it costs a lot to do a lot, and there are certain things as you said that are beyond the scope of doing at all.

 

3. I definitely will start small and build my way up.

 

4. I tend to leave comments for myself in code and having pretty code is an art form in and of itself. My programmer and I talk a lot about his systematic approach to making tools like an editor mode in my platformer game, or even a cutscene editor and hitbox editor. The gist that he does is he does a lot of recursive work making scripts readable via number systems in .bin files to load his code fast that can be accessed from a more complex interface, then reduced again.

 

5. I intend to start my ideas from the ground up. I agree that working on someone's own writing would be hell especially if I don't know what every interaction does in the code itself. Not knowing why something works in code spells out disaster for debugging and understanding why something breaks.

 

6. I will try to do what works for me. This will be so I can make Renoise the best DAW for me, not for others, as selfish as that is, and hope for those that get me, will enjoy it.

 

7. I will be publishing videos on Youtube to explain my process with illustrations and ask help from the community.

 

8. I'll ask around if so! Sometimes it's tough to figure out an answer, I've known some projects end prematurely because no one can figure out how to hurdle a nasty debug.

 

9. Renoise is a massive DAW I think. In the end it's not the parts that make the car, the car is a body in and of itself.

 

 

Music is fun, and developing games is my passion. I want to make good for myself and others. I hope that makes sense! I find it better to do that, than to be querulous and mean-spirited.



#6 esaruoho

esaruoho

    Guruh Motha Fakka is Levitating and Knows Everything About Renoise Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2670 posts
  • Gender:Male
  • Location:Kontula, Helsinki, Finland
  • Interests://Varying Interests//

Posted 31 March 2018 - 23:25

so far i've only seen the renoise documentation be updateable via PRs on the github. obviously the renoise code itself is proprietary and accessible only to those within the dev-team, as otherwise we run the risk of it being leaked and we start bumping into dozens and dozens of variations that all suck and have no cohesion amongst themselves.

and then suddenly no-one actually buys the license.

 

would be cool to be able to pay a premium price for access to the codebase - but i'm sure the vetting process would have to be extremely harsh, to get rid of timewasters (i count myself in that group).

 

+ if there's no time to update the app, there's no time for the strenuous on-boarding required to teach a person to move around the codebase without wrecking everything.

 

would be interesting to see how many PRs are awaiting review in the Renoise codebase, though, and if someone doing manual QA testing on the PRs could somehow help it, even under NDA.


http://lackluster.org | on Bandcamp | on YouTube | on Facebook | on Spotify | on iTunes | on TiDAL | on Soundcloud | 

http://twitter.com/esaruoho | http://esaruoho.tumblr.com | GitHubesaruoho@gmail.com | 

| macOS 10.13 High Sierra | MacBook Pro 2.8 GHz Intel Core i7 / 16 Gb 1600 MHz DDR 3 |

| http://renoise.com/tools/paketti | BTC: 1BoZ9rvb8wT7dFNyVPwSX7DLj3stNo7844 | http://paypal.me/esaruoho |

| Latent Impulse Tracker/Scream Tracker 3/Schism Tracker <-> Renoise fanatic |

More API functions, please! ;) http://forum.renoise.com/index.php/topic/26329-the-api-wishlist-thread/page-3#entry240266

#7 lettuce

lettuce

    Big Masta Member

  • Normal Members
  • PipPipPipPipPipPipPipPipPip
  • 523 posts
  • Gender:Male

Posted 01 April 2018 - 23:37

Invest in the renoise developers.

$76,704 per year each.

Total creative control.

Hire some people to work for them on tasks that are relatively simple but involve a lot of repetition and take a long time so that developers time is spent on audiotracks and fixing vibrato, tremelo and autopan so they cycle in time with song settings.

Pay for yearly renoise boat party. Pay for celebrity star trek actor to advertise renoise at NAMM and MusicMesse.

Making more music videos including shots of people using renoise.

 

06.jpg


Edited by lettuce, 01 April 2018 - 23:45.