What do 3.3 really needs…

i know a dude that still uses playerpro and is one of my main influences when i started making music :slight_smile:

1 Like

so is this version being finalised or could suggestions still make there way in ?

There exists allready a build Version.

2 Likes

@NPC1 Here you have a specific tool for this. I know it’s not under Renoise’s hood. But you can try it…

By the way, it has not been easy to program!

1 Like

Thanks Raul, but i not use any 3 Party Tools. And it should very easy to code from Renoise direct. All what needed is there in the block play function!!! You have a startposition, you have a stop position. Where should be the Problem!?

Well you could start some day. You’re missing a lot.

Ask the person in charge. I guess there is no time for everything…

This thread sometimes sounds like ‘hey everybody, let’s get together and each have a stab at the one developer we have’.
There are no easy things to program - what one thinks will take few minutes usually takes few hours and let’s not forget the testing that all works well after. If all that was proposed in here (and other threads) was to be implemented we’d need 5 full time developers.
So… that being said… :slight_smile: Possibly in one of the future versions samples used by the ‘Convolver’ as impulse can be made to save within the RNSX file - I don’t have the impression this is happening at the moment? (likely this would be also an option under ‘Preferences’ - ‘Files’ - ‘Song/Instr./sfx Export’)
And, since ideas are easy… add an option in the Convolver so it can be made to resamples the impulse according to the midi note input - if that makes any sense. Likely the re-sampling would need to happen once (on loading of the impulse) and then the Convolver would read out the correct sample from the pre-resampled memory - or better way might be to simply permit audio routing to be used as the impulse (so resampling would be done on a different track… one could use vst’s for the impulse,…). As I said, ideas are easy. Thank you for all the good work!

3 Likes

a proper note grab move up with the arrow press a certain button and grab it and move it where u like

@Inhoused You talking nonsense. What i read out of your Post ist. Realize not the need and ideas of the other posters here, use mine…

If there is no time for anything then the entire Thread is useless. I am self a Developer. (Delphi, C++, C#, Java, MMASM) and when i say it should be easy to integrate (because all of needed functions already exist and are using in actual program Version) you could accept it.

PS: Crying of only 1 Developer… I only can assume that the Lead Developer want to be the only DEV on the Project and not want to give it out of his Hands. Im sure in other Case it would give many Support to this Project. I Would Support too. For Coding and/or Testing. But for Help, its need of an Sourcecodemanagement Tool and Collaboration Ways/Tools. Just my opinion.

happy Tracking

1 Like

I want a battle royal feature.

2 Likes

Only an advanced AI can say what Renoise 3.3 really needs.
But a human can identify the 10 more asked features and then create a poll.

2 Likes

While it is too big to implement in a simple update, I think adding some way of viewing sample wave forms in the timeline (with the editing features of the sampler added) would open up Renoise, making it easier to manipulate individual samples, work with long samples (for example vocal recordings) and also lowering the barrier of entry for people not well versed with tracker systems. It’s the one aspect that I still prefer in other DAWs compared to Renoise.
Ideas for implementation would be a simple horizontal timeline view, wav form overlays in the advanced pattern editor or a per-track sample/wave form view/editing tab at the bottom (next to the DSP/Automation tabs). Imo this would blow all other DAWs out of the water as it would make Renoise a true hybrid DAW retaining the tracker workflow while allowing for in-depth sample processing and visual editing without switching to the sampler.

I‘d like Ableton live style Audio Warping within the Sampler itself with SXX Markers behaving just like Ableton Warp Markers and a new effect command to move them of course =D

Automatic Key detection of samples would be great as well.

Also I‘d like a pony

4 Likes

+1 for a pony. I mean, come on…

2 Likes

Another thing that I’d really like is automation lanes that are not linked to a pattern, to be able to adjust a parameter further than the current pattern that is playing. Maybe there is a way to do it that I haven’t discovered yet.

1 Like

@NPC1, we seem to have said the opposite. There will not be time for everything, as is normal, but yes for important things, supposedly. The strange thing is, if you are a programmer with so much experience, why don’t you make your tools with LUA?

LUA looks a lot like C++ (it’s a derivative). Many user requests can be covered well with LUA tools.

If Renoise had all the ideas from the forums implemented it would be very fat and heavy, difficult to maintain / modify / improve.

Nonetheless, I think the looping ability of the selection should be under the hood (seems like a no-brainer), even though there is already a tool that does that (and with more options).

Using Renoise doesn’t just mean composing music. You can also program with LUA and expand it. Both things. Many people who know English forget this.

1 Like

Simply thing Raul, because i hate scriptet shit! Never scripted things are so straight, direct and efficient to implement as in native project code. Api’s or Interfaces are ever a limiting factor. An open moderated Git Repo would be the better way in my opinion. Users can code their own functions and send it to dev for inspecting. If he is fine with the code he could it integrate.

I think one of the best features of Renoise is precisely that it has an API to expand capabilities. It’s wonderful to be able to add features without a supervisor to expand your Renoise. The API has limits (and should have them), like anything else.

What I don’t understand is your hatred for scripts. Most are little lines of code that “do something new”, if well written. The only real limitation is time and the desire to learn how to use it. If you switch to another program or DAW with expandability, the same thing happens. You have to relearn specific things for that program (the API… LUA…). For the rest, there is no excuse. The LUA code works just as well as the built-in code under the hood as long as it is well written, unless it is a heavy tool with hundreds of functions as a spaghetti plate.

On the matter of someone monitoring the code of others, I would not know what to think. Certainly, even people who know how to code hardly contribute anything here in these forums. There are only “4 cats” staring at the moon, and each person programs very differently. Maintaining that would be a headache.

2 Likes

i’d add the ability to zoom in sequencer/lines like in radium tracker - so we wouldn’t need to stress about lpb and wether we are going to have enough detail in terms of sequencing or not. (but i think this is a complicated if possible at all - thing to do).
Cheers

3 Likes

How does this work in radium ? do you like zoom in place a 128th note and zoom out and it gives that note the delay / gate values ?