Mod wheel is CC#1
haha, doh. cheers
…still it could be nice to have modwheel parameter also, because it tend to use cc#1 as default for other things
Do you imply that music with synth leads is outdated or something? 
I’m not at all interested in making, or listening to, anything that resembles so-called “IDM” music. 
It depends on your individual preferences. Maybe it’s not “that bad” for you and your music. But for MIDI it’s definitely worse than for sample instruments. If I just wanted to use sample instruments only, I wouldn’t have needed to ask anything.
+1
Anyway. What comes to my alternative E, is it possible to route MIDI from one VST plugin to another, inside Renoise? I wouldn’t like to have to do all of that in Live via ReWire.
No I’m implying that you should give other options, like half a dozen of them, all user feedback driven evolutions of the 1992 paradigm, a chance.
Right, but what MIDI are we talking about? Gear that doesn’t respond to standard midi C0, C1, C2, C3 in the way you want (e.g. not standard)? So, not the fault of Renoise?
Anyway, interesting discussion.
In case it was missed the first time around.
Even if there is no standard for pitch for plugins, there is nothing stopping us from manually rerouting midi commands to standard tracker (sample commands) using for instance templates for each plugin?
In other words let you manually be able to set the correct range for each plugin.
I have used Cakewalk for DOS, Cakewalk for Windows, Cubase VST 5, Cubase SX 1 - 6, Reason, and Ableton Live, to name a few. And various trackers for 8, 16 and 32 bit machines. Each of them has their good sides. In the past few years I’ve been making tracker music for 8bit home computer sound chips (PSG and SID), and it’s felt like a breath of fresh air after all these fancy DAW-like behemoths with so many “features”. For example, Renoise’s automation envelopes feel like exactly the kind of stuff that I’m trying to avoid. By the way, in my post listing the alternatives A to E, I tried to explain what’s wrong with it. Not for every human being in every imaginable background and use-case, but for me right now.
I’m talking about (1) Renoise’s features for writing pitch changes for sample instruments vs. (2) Renoise’s features for writing pitch changes for MIDI instruments. Number 1 is much better (in my opinion).
For someone else’s needs, it might be OK to do pitch control with the mouse in a separate editor, separately from notes. But if graphical envelope mousing really was the greatest thing since sliced bread, why does Renoise have the whole notes-in-patterns thing at all? Why don’t you write all your beats and everything in the graphical envelopes?
But very nice discussion indeed. Lots of different opinions, ideas and paradigms.
That one doesn’t track pitch, does it?
But that chain could still be used for what I’m after, sort of. I could control the synth’s pitch by the volume of the second (sample instrument) track/channel. Very interesting idea, thanks! I wonder what it would sound like when controlled by a pumping beat or something.
Nopes, that you would need the key-tracking device, but this doesn’t track changing pitches either.
So you would then really need some wave analyser plugin that does pitch tracking of the audio feed and output the values to a parameter that you can use to control other parameters.
I do doubt about the speed and efficiency of such device though.
I think there’s some confusion. Namely, this thread is confusing MIDI with VST instruments.
Let’s define standard. A standard means if you have 100 vendors, they all do the same thing.
First, if you read the posts in this thread again, you will see that there is a standard for pitch bend in MIDI. Renoise supports it. It’s C1 in Renoise parlance. Renoise respects the standard. What you type is what you get. It doesn’t do what you want? That’s another story.
Secondly, sampled instruments are raw data. Renoise can do whatever it wants to that data without breaking any standard because XRNI instruments are Renoise only. So of course the features will be better.
Never mind that in this thread alone there have been 7 ways to do just what you asked. (C1 Increased Resolution, Resample, Envelopes, INST Midi Contol Device with commands in the pattern editor, One shot LFOs, LFO device chained to other device with commands in the pattern editor, Signal Follower tied to Instr. Automaton device…) If we keep discussing, I’m sure there will be more.
What you are asking for is a way to pitch bend a VST instrument using MIDI pitch bend which is a single command. In other words you want a way to “batch send” MIDI pitch bend commands with a single custom Renoise command in the effect column.
Ok, cool idea! But, this is not an obvious feature. In fact, it doesn’t exist. Should it? Sure why not. Yet another way to accomplish the same thing. But, it’s a new idea.
Let’s forget I ever mentioned VST and stick to just plain MIDI. Whatever happens in the object that receives the MIDI, is up to me, and I’m completely fine with it.
I already said it: “all I want is to get (1) 1xx and 2xx commands to output pitch bend messages and (2) notes to send a pitch bend reset message.”
Here’s the feature in all its simplicity or complexity, whatever you like
- if the track has a MIDI instrument (and not a sample instrument) and there’s a new note on the track: on tick 0 of that row, reset variable PB to 0 and send it as a Pitch Bend MIDI message
- if there’s a command 1xx: on every tick > 0 of that row, add xx to PB (limit to 14 bit range), and send the new PB value as a Pitch Bend MIDI message
- if there’s a command 2xx: on every tick > 0 of that row, subtract xx from PB (limit to 14 bit range), and send the new PB value as a Pitch Bend MIDI message
I don’t think that’s very complicated, but to each his own.
just messing around to see what’s possible… something like this could work maybe?
Interesting, a good idea, but it would have to be a new “midi only” command. Specifically:
In Renoise, you can have hundreds of instruments on a track. It’s not the MIDI model of 1 track = 1 instrument. I can’t imagine a “look ahead / look behind” model that will work efficiently with the same command.
So yeah, repost as a separate feature suggestion with as many details ironed out to make the devs life easier, and it will surely be considered.
But, your original question “How Do You Write Lead Lines For Midi Instruments” has been answered with 8+ solutions now. So either the question was loaded, or this is a sincere discussion where you keep an open mind?
Cheers.
The thing is, the 10xx and 20xx commands are relative. They don’t set the pitch to a specific value, but rather change the pitch by the specified amount. So, it would be kinda hard to “reset” the pitch bend, like you are suggesting. If the idea is to simply make VST instruments behave the same as sample-based instruments, then the pitch-bend would have to be reset with each note. But this would mess up how pitch-bend should work, so this idea would have to be built “on top” of the existing pitch-bend implementation, adding the 10xx / 20xx generated pitch bend amount to the actual pitch bend.
And then there’s the problem of missing standards. No matter how this was implemented, the result would be different for each VST plugin: some plugins doesn’t support pitch bend at all, others might default to 3 or 12 semitones. We have no way of knowing this. Even if Renoise had a database containing the default pitch bend range of all plugins, this wouldn’t be good enough, as the pitch bend range can often be specified from within the plugin, in a non-standard way. So if you changed the range to an octave, but the database is telling Renoise that the plugin has a range of 3 semitones, the result would be incorrect pitch. In other words, you would have to set the pitch bend range in the VST instrument settings, as well as the VST plugin itself, before results would be trustworthy.
And then there’s the issue of changing the pitch-bend range after effect commands have been entered into a pattern - they would need to be changed as well…
Yes indeed. You’d need to add a variable for storing the state. Can’t just blindly output the command parameters and forget about what they were.
Hard? Set the state variable to zero and send that as a pitch bend message.
And adding two numbers together, in a computer program, is very difficult? What is this “actual” pitch bend, by the way: And how “should” pitch bend work in your opinion?
How and when is that a problem, for who? You don’t know what my MIDI notes are doing in the MIDI device either. They might be controlling my disco lights.
But luckily there is no need for you to know it. MIDI is really simple, because you mostly don’t really need to know how it will be interpreted by the receiver, in order to make a program that processes it.
Why is that an issue? The same thing applies for notes. If I decide to swap the note mapping of my snare and kick drum samples in the sampler, I need to change the MIDI notes as well.
Let’s be practical here. MIDI is a very old protocol, but it’s also very practical, and I’d even go as far as to say, it’s good enough. Also, ProTracker was made using non-theory-hygienic, but practical period numbers (pitch = master clock / period), even though it meant getting different different vibrato and slide speeds depending on the note pitch. In practice, nobody cared.
I don’t know if the creators of SoundTracker and ProTracker aimed at creating a very compact and easily editable alphanumeric “language” for specifying monophonic melody lines with a lot of expressive power for complex pitch modulations in a very tight spacing, but that’s what they managed to do. In its current state, Renoise can’t really carry that good legacy to MIDI music-making, but I feel that it’s not far from it.
Why am I so stubbornly trying to explain this to you? Because I got such a huge wow feeling when trying Renoise. This was the first thing I tried, and I wrote it in quite literally one minute after starting Renoise for the first time (not taking into account reading the manual)
I added a VST instrument (Native Instruments Pro-53), entered some notes and looked up in the manual, how you specify note lengths and how to show the needed column, and … bang, wow. Wow. I was like, this is what I’ve been wanting forever - a way to write stuff just like in a tracker, but even better! No mouse-clicking around in dozens of windows, just enter stuff on the keyboard blazingly fast. Maybe that mp3 sounds like yet another boring bassline, but for me, being able to write that from the computer keyboard, and specify velocities and note lengths like that, it’s just great. I play many different instruments and I have no problem improvising endless amounts of stuff for hours. But if I want to do that, I can go to Live. But it isn’t really the same as “writing music”. That’s something that I’m really proficient in only in trackers. Yes, that’s my deficiency. In a perfect world, I’d first write it down in proper musical notation on a piece of music paper…
Then I thought, let’s add a melody… nope, can’t really do that like in trackers.
However, just to say thanks for everyone who participated in this thread, I’m going to make a melody with the awful looking automation thingy that’s horizontal, in a separate place, not tied to notes, and is edited with the mouse etc.
I’m with yzi here.
In general it would be great to be able to map whatever you want in an instrument to any pattern command.
If I want 1xx to pitch up one group of sample zones, and at the same time pitch down another group of zones. I should be able to do so. Would love to see that one day.
I once made a feature request for a frequency demodulator: