Absolutely, and it’s really nice to see the enthusiam of all those projects. But at the same time, it seems to me loss of energy, not focussing on an actual tracker daw which can compete with modern daws. People should work together. A pity that Renoise is closed source completely.
I image some “chipset” plugin for Renoise instead, so you could install SID- or AY-emulation natively or so, using the same track commands as usual. Maybe that would be even possible with VST3- or CLAP-plugins, if MPE and per-voice modulation was supported. Such stuff, like joining retro architecture with the latest design patterns.
Renoise has long needed its own modular engine, so that everyone could assemble their own synthesizers. And at the same time a more adapted API for creating more experimental variations of waveforms. In general, we will see in the future what the Renoise team considered a priority in the next release and crossed our fingers.
Personally, I don’t expect the Renoise team to embark on something that can be accomplished with Plugin, and I don’t want the resources of a small team like Renoise devoted to something like that.
I have faith in the Renoise team. I trust the Renoise team because I feel they have been basically doing the right thing (and more importantly, not doing the wrong thing) so far.
Calling Renoise a DAW is one magic word, but the reality of them is that the concept is “a rich tracker that can also use plug-ins” and I’m basically perfectly fine with that.
I imagine that a large amount of API additions at lower layers, such as REAPER, would be good to go more in that outsourcing direction in the future, as third-party developers would work for free to create higher layer API groups and other large groups of features I imagine it will be good to go more in that direction in the future.
At the very least, we can see the following moves that will make RenoiseTools development more convenient. Personally I feel it is a perfectly valid strategy.
this is a different principle, a standard vst instrument and an instrument made with meta devices will be very different, plus you can control each node and create quite serious interactions within your timbre. devote more time to this and you may well discover renoise from a completely different side and see a lot of advantages and a different train of thought.
a small example of a synthesizer made from a delay
Arguru will be greatly missed, deadmau5 made a song for him and I didn’t catch it was an eulogy until I heard about him and his tragedy, he did great things in this world like contribute to this amazing software.
I’ve seen some screenshots of Noisetrekker and I just noticed the “developer comments” on the bottom lol
lol please no.
…i hate that you’re probably correct, but it will be for all the people who think trackers are too hard to learn so they can say they use trackers too
“ArGuru: I hate Cubase…” and “TakTik: Logic is cool…”.
Yes, I feel the same about Cubase, but I cannot agree what another TakTik said about Logic. Anyway…
Yo have to be realistic here.
There are only a few modular engines whcich are trully modular ( in sense that you can code your own dsp effects )
For that it requires z-1 feedback loops , the basis for all things dsp and especially filters , and even if it can do z-1 , this is not a garantee that it performs well ( that’s why reaktor has the core language introduced , realtime compiler ) )
Bitwig grid is imho not even full modular because you can’t even build a simple IIR filter with it ( because it requires z-1 feedback and bitwig relies on the audio bufer for feedback loops )
The programs that are capable of coding your own dsp
-reaktor
-Max /msp (only since the introduction of gen~ in 2012 )
-Pure data ,…
-Faust
-C sound
All of these have been in existence-fine tuned for decades , don’t expect Taktik to just code a full blown modular .
It’s naive to think that’s even possible , just the state of the current dsp offerings says enough
Renoise has very good features and is “pro”, but I had to stop using it and develop my own tracker, because the timing of MIDI events was all over the place when using the internal clock. Huge drift and jitter…drums out of sync by 0.5 secs at the end of the song was not acceptable. Someone else might have a different way of working so that this doesn’t matter. This was possible to “solve” by syncing to Jack, but should have been needless if the timing was implemented properly.
VCVRack also, its engine updates each port/cable 1 sample at a time so feedback of 1 sample delay is possible. You can write your own modules fairly easily and there are a large selection of modules to use and learn from. Cardinal is a free fork with plugin builds that can be used inside Renoise.
A homemade solution is always better, of course, but I would be interested in finding out what caused the problem in order to fix it. Would you mind sharing some more info here?
By default we use the ALSA MIDI sequencer to schedule MIDI events (snd_seq_event_output and friends). There’s actually an option to bypass it and use a custom Renoise built-in scheduler that can be enabled via a hidden option in the Renoise Config.xml file called <EnableAlsaMidiScheduler> setting it to false. It’s hard to test and automatically figure out which one does a better job, but maybe we should make that a user visible option.
I’m guessing you are using Jack’s MIDI IO along with an Jack audio stream to fix this for you?
I actually just chose “Jack” from the Sync menu on the top bar. I’m not using audio at all, only MIDI. I guess in that setup ALSA MIDI is still being used as the backend, but the internal clock is synchronized with Jack’s clock pulses. This fixed the issues with drift.
I don’t know how the internal timing works in Renoise, but my own solution calculates the precise absolute timestamps for each MIDI event beforehand and the player thread sleeps until the next timestamp. It is very accurate even with ALSA. No jitter or drifting practically at all. I popped into this issue when recording MIDI instruments track-by-track in an external application so that Renose is the sequencer.
Also, trying to make Renoise to sync with MIDI clock didn’t work at all as the player accelerated and decelerated while it tried to “lock”. I would have expected this to work similarly to the Jack sync.
