Multiple Outputs Routing For The Internal Renoise Sampler ?

Sorry, I don’t get what you are saying there. But to re-explain my point: In any other sequencer I can record a whole e-drumset into one single midi track, but still have the actual audio output routing on single tracks for each of the drums in there, such that I can put a reverb on the snare, but not on the kick, although they are all in the same midi track. That is what we want from Renoise as well, record everything into one track (this actually is a limitation of Renoise! If I could decide which midi notes go into which track and could record them simultaneously into several tracks, that would be just fine as well!) and then route the sound from the sampler which is played by the note information in that track to different output channels (or other tracks), depending on which note value/sample they are (or whatever criterion).

Hope that makes it more clear.

fladd

arranging track = drummer’s seat and body :)

receiving audio signal tracks = microphones on toms, snare, etc

It took me a while bu tI see why this makes perfect sense. In the meantime I’m gonna try using keytrack on send destination. Should be tolerable so long as nna is cut and there’s only one hit at a time :lol:
I wonder if scripting will allow one to modify this? Probably not, looking at lua, but what so I know…

Frustration? with renoise!!!??? :yeah: :drummer:

never!!!

just a suggestion :) i just’d really find this feature usefull… i often miss it when i’m lost jumping between tracks when there is only one sample every 2 patterns…
don’t know if (hope) you understand more now…

because it can be done with too much manipulations and it soon becomes boring…

It’s pretty much an extension of this idea, but rather than tieing whole instruments you can tie notes (samples) within an instrument.

I can see how it would be useful, especially for those that play their drum parts in live or have been using a keyboard split but I don’t think it’s something I would personally use.

And it can’t currently be done. Sure you could write something to edit the offline xrns data and then reload the song and once scripting comes in you should be able to do it (almost) live but I can see why people might like Renoise to do it automatically, if asked to do so.

Oh come on, now your are just trolling! You know exactly that it is not possible in Renoise to input into several tracks simultaneously! I actually said it before, the problem could be either fixed by the input OR the output routing (so don’t tell me I confuse them with each other). So what do you think serious DAW-users and producers do? Do you think they first play and record the kick drum, then in the next take they record only the low tom, then the mid tom and so on? Because if this is the case, then you are right, I wasn’t aware at all that this is how the pros do it and I apologize! But in that case, I just don’t want to do it like the pros :slight_smile:

But on a more serious note: You do understand the issue at hand, right? (I am not sure you do, especially when you start talking about the limitations of MIDI…) I mean I appreciate that you don’t care for that functionality, but you should at least be able to see the usage (and you should also be aware that this is the way practically all other DAWs work).

fladd

Ah, separating the pattern editor’s tracks, from the dsp routing and a tracks input method.

In many ways I would like to see the dsp routing join with the actual instrument also, be it vst or sampler instrument.
Association of many effects commands in the pattern editor could also be instrument specific, instead of the current track only specific implementation.
While having the instrument tied to the dsp routing directly, we would still need the track effects along with this, as some effects commands are track specific.

This is pretty big, as the current pattern input method for the pattern editor is track specific, it’s why we can’t record multiple MIDI-IN’s in real-time.

+1 I enjoy OP’s idea, I don’t know if it could be as simple as previously stated, but I see the merit.

thank you :)

btw, i’ve never sayed that it’s a “problem” placing my kiks, hats, chords etc on their respective tracks, … (that’s what i do since my first e-mu with cubase on atari, i was discovering the “more than 4 traks limitation of the amiga”, and later in logic… ) so once again, thank you :)

i just suggest. so please keep your “user problem” for you…

i think you consider my request like some kind of critic about renoise… not at all, but i still can’t understand why refusing a simple “added feature suggestion”

If this feature ever happen one day, and if you don’t like it, JUST LEAVE THIS OPTION OFF and continue your way, nothing will change for you!

complicate? as i allready sayed, if you don’t like it, if ever it’s added one day, just leave it off… that won’t change anything…
just an additional feature… on or off, free or fix…

I am talking about recording midi inputs live. Something that is done in probably every studio production nowadays. Think of any hardware synth, drummachine or whatever. No one is recording only the audio of those things. At least not in the beginning. You play your synth, sampler, drummachine, whatever and record midi first, just in case you need to fix something afterwards. You know, a “sequencer”, be it in hard or software, is a piece of gear that is only made for exactly that thing, namely sequencing and controlling other electronic instruments via MIDI which will then produce sound that is then recorded into a multitrack recorder for mixing.

Anyway, I think you know exactly what I am talking about :slight_smile:

fladd

that’s exactly what i’m saying… so where’s the problem? just leave the original structure in its own track and split the audio results…

:lol:

for sure, now we have to admit that every electronic musician in the world works in the same way! ORGANISATION! :w00t:

Whatever :)

Okay, one last time: What I mean can be achieved in both ways, either by changing the input routing OR by changing the output routing. If the input routing stays like it is, then we have to record a whole drumset into one track. However, if we could then route the samples that are triggered by the notes in that track to different outputs/tracks, such that they can be processed individually (effect and mixing wise), then this would solve the problem as well as changing the input routing.

fladd

fladd TALKS ABOUT MIDI ONLY TO TRIG THE SOUND THAT IS GOING TO GO OUT ON MORE THAN THE TRACK CONTAINING THE NOTES OF THESE SOUNDS!

so forget midi and just say a KEYBOARD COMPUTER (azerty or querty or quertzanyway) wich will be able to trig multisamples going on many other tracks or sends than the one where you type on your keyboard…

SO YOU CAN RECORD A RICH AND VARIOUS STUFF (RYTHM OR ANY OTHER STUFF LIKE PADS OR SCREAMING DOGS OR EXPLODING FRYER) PASSING THROUGH LOTS OF AUDIO TRACKS IN REAL TIME!! ALL IN ONE

MIDI IS NOT THE PROBLEM, IT’s AN EXAMPLE ABOUT ONE WAY OF HOW TO TRIG

THIS IS ANOTHER WAY OF “ORGANISATION” and “DISCIPLINE” :w00t: :lol:

easiest way… or another? yep, that should also work, but i don’t really understand what’s easier than a new tiny box placed near the NNA, INTERPOLATION, etc, this little box lets you decide between free (as usual) or fixed… but surely your suggestion is more flexible if automation of the destination track is include so you can switch between differnt traks with a sample in the song… sure this is a good idea :) but means the whole xrni instead of the samples (ex multisample) no?

k i see… so, anyway, this option, (your idea) as i say should be cool ;) and, wherever, however and whenever it is created one day , i’ll use it :)
so, you still think it’s another weird topic?? ;)

k, i just precised this topic in my first post to avoid confusion
hope it’s clearer now…

let’s use protracker…