Midi - trying to put it all together!

Author
wineshop
Max Output Level: -87 dBFS
  • Total Posts : 185
  • Joined: 2007/07/18 23:44:18
  • Status: offline
2012/07/16 20:07:32 (permalink)

Midi - trying to put it all together!

I'm getting more and more into working on symphonic music after years of mostly audio. I've purchased some orchestra libraries and I admit I'm having a lot of fun. And actually I'm pretty pleased with my progress. But I do have a few issues I'm trying to wrap my head around. The whole concept of velocity, volume and dynamics overall (with respect to midi) are still confusing. I have a session with about 30 tracks. Most of them I recorded one at a time (using mod wheel). Some I have copied and pasted from other tracks. And what happens is the dynamics get confused, I guess. It's like the velocity, CC 1, CC 11 (etc) all wind up telling the data to do something different. The result is the occasional note that will swing wildly in volume, or it will not crescendo like I want, etc. And then, if I use track view to edit, say, CC1 - it appears to be different than the data I see in PRV. And I realize that's kind of a big topic to answer in a thread. So - how much help would, say, one of the videos on the Cake store help me make sense of all of this? Can you recommend one in particular? Or - can you point me somewhere else that would help?

Hope I explained all of this well enough. Thanks!
#1

9 Replies Related Threads

    konradh
    Max Output Level: -42 dBFS
    • Total Posts : 3325
    • Joined: 2006/01/16 16:07:06
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/16 22:47:57 (permalink)
    Here is what many people do. 1-Use velocity to vary the loudness (and timbre) of individual notes, like a player playing more loudly or quietly. 2-Use expression (CC11) to crescendo and decrescendo—in other words, to bring the overall volume up and down, to swell and fade. 3-Use Volume (CC 7) to set the overall level at the first of the piece. In other words, after you have all your expression commands (CC 11) in place, if you find the whole thing needs to be louder or quieter, you can change the CC 7 value. What really complicates this is that some libraries—PARTICULARLY HOLLYWOOD STRINGS—do not use these values the same way for every patch. For some sounds, velocity does nothing, while for some it controls loudness, and for others it controls both loudness and vibrato. Although I love Hollywood and use it all the time, the lack of consistency drives me nuts. Vienna Symphonic is much much more consistent and easier to use, but it has a different sound.
    #2
    konradh
    Max Output Level: -42 dBFS
    • Total Posts : 3325
    • Joined: 2006/01/16 16:07:06
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/16 22:50:17 (permalink)
    Note to my comments above: I personally don't use CC 11 much unless it is required by certain patches (like certain ones in Hollywood). I just use Controller 7 and if I need to change the overall level, I use a Find/Change command to increase or decrease the values. But what I said above is what most people do and is much easier—I am just stuck in my old habits.
    #3
    wineshop
    Max Output Level: -87 dBFS
    • Total Posts : 185
    • Joined: 2007/07/18 23:44:18
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/16 23:13:54 (permalink)
    Thank you! Great answer. I'm going to work on it later tonight and will consider all of that as I study it. And see - what you said is what I think makes it so confusing. Sometimes I'll drag velocity all the way up or down and nothing happens. Then I'll drag cc 1 up or down - nothing. But still, I can hear the dynamics changing. I guess I just need to record some useless tracks that I can't mess up and spend time with all the automation values until it makes sense. But your reply gives me an excellent starting point. Thanks! Tim
    #4
    bmdaustin
    Max Output Level: -68 dBFS
    • Total Posts : 1114
    • Joined: 2004/01/11 21:56:51
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 00:37:34 (permalink)
    It's important to understand that different sample libraries respond to different controllers in different ways. Where Garritan uses mod wheel for volume, others use it for vibrato, for example. That may explain the discrepancies you're experiencing. Velocity refers to how hard the key is struck, literally how fast the key moves past a sensor that computes its actual velocity. This parameter is usually mapped to how loud the instrument appears to sound or which sample layer is triggered. Volume refers to the overall volume of whatever's going on with that particular MIDI channel. For example, it's possible to have a velocity of 127 (a drummer banging away at full force), but a volume of 10 (the volume is turned down to blend in with the mix). Does that explain things any better? Not all sample libraries are created equal, nor are they programmed the same way. You'll really have to delve into your documentation to get the most out of each library.

    Paul Baker
    Baker's Jazz And More
    http://www.bakersjazzandmore.com
    #5
    wineshop
    Max Output Level: -87 dBFS
    • Total Posts : 185
    • Joined: 2007/07/18 23:44:18
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 01:29:57 (permalink)
    Paul - yes, thank you that really helps. Between you and Konrad I think I kinda get something I wasn't getting before. And I guess i really do need to dive into the library manuals. I admit I'm one of those not so smart guys who dive in without reading first. But it's obvious I'm going to have to back up a bit.

    One thing that's currently confusing me. For example - in my current session, I have a string track. In track view there is data stemming up from the bottom of the track. It's darkened and I can't edit it. I can tell it is effecting the "volume" (maybe wrong word) because I can hear crescendos/ decrescendos as it gets bigger and smaller. But I can't find a way to edit it. I have selected every automation option available and also added CC 7 (so, CC 1, CC 11 and CC 7) and each option creates a new automation envelope, but none that allows me to edit whatever data that is. Plus - I can click the (+) sign at the bottom of PRV and add velocity, 1, 7 and 11 and none of them match whatever that mystery data is. I hope that all makes sense. I really need to go in and delete and re-draw some of that data.
    #6
    SToons
    Max Output Level: -81 dBFS
    • Total Posts : 478
    • Joined: 2012/05/14 15:21:14
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 02:12:16 (permalink)
    Select the track with the confusing data. Press Alt-4 to launch the Event List. In this list you will see all notes, controllers, volume changes, mod wheel data, CC's etc. so you can figure out what the mystery controllers/MIDI events are. 
      
    Note that controllers drawn in the PRV or recorded directly will not show up in automation envelopes just as data from automation envelopes doesn't show up in the PRV but they -all- show up in the Event list.
     
    As Konrad says, also note that velocity affects "dynamics" and timbre and volume doesn't. As you know a cello sounds different bowed softly (low velocity) versus bowed hard (high velocity). Different velocities will trigger different samples whereas volume simply affects volume. A loud velocity with a lower volume will sound completely different than a soft velocity with a loud volume even though both may register the same in dB on a meter. Use velocity to control the timbre and expression of an instrument and volume to control volume.
    #7
    wineshop
    Max Output Level: -87 dBFS
    • Total Posts : 185
    • Joined: 2007/07/18 23:44:18
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 02:30:16 (permalink)

    Note that controllers drawn in the PRV or recorded directly will not show up in automation envelopes just as data from automation envelopes doesn't show up in the PRV but they -all- show up in the Event list.



    That, my friend is very helpful. I can see now where there is a discrepancy among notes played, drawn, and copied from one track to another. I've really learned a lot tonight. Thank you.

    Also - I just kind of figured out "Convert Midi Controllers to Envelopes". Although I'm still trying to completely wrap my head around that, it is starting to help bring things into focus. 
    #8
    synkrotron
    Max Output Level: -22.5 dBFS
    • Total Posts : 5263
    • Joined: 2006/04/28 16:21:21
    • Location: Warrington, UK
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 03:02:35 (permalink)
    I'll chip in my two pence here, I think...

    Admittedly, I may not a "complete" expert with all things Sonar, but I do come from a MIDI background and have been creating MIDI music for over twenty years. Plus, my main area of expertise is in the use of non-sample based synthesizers. 

    In the old days, before Sonar, and before mixing consoles come into being, I would control everything via MIDI messages, either at the beginning of a track, or at any point through the track. So I am no stranger to MIDI.

    As has been mentioned here already, Velocity determines how hard an instrument is played, generally. And I say generally, because each instrument is different. Especially instruments that use multi-layered sample sets. I have always used Velocity to represent expression, although, with synths, the velocity messages act on the sound in a different way to sample based players.


    I rambling a bit there, and what I really wanted to add here is, that I no longer use the Volume MIDI controller any more, and I rely solely on the sliders in the mixing console to get each MIDI performance to fit into the mix. If I need to alter the volume during a performance I will then use an envelope on the track, rather than adding MIDI controller messages. I find it easier that way nowadays, and I rarely use Event List (which is where I would add such messages) any more.

    Anyway, that was just my opinion, and there is always more than one way to skin the proverbial cat...


    http://www.synkrotron.co.uk/
    Intel Core™i7-3820QM Quad Core Mobile Processor 2.70GHz 8MB cache | Intel HM77 Express Chipset | 16GB SAMSUNG 1600MHz SODIMM DDR3 RAM | NVIDIA GeForce GTX 675M - 2.0GB DDR5 Video RAM | 500GB Samsung 850 Pro SSD | 1TB Samsung 850 Pro SSD | Windows 10 Pro | Roland OCTA-CAPTURE | SONAR Platinum ∞ FFS| Too many VSTi's to list here | KRK KNS-8400 Headphones | Roland JP-8000 | Oberheim OB12 | Novation Nova | Gibson SG Special | PRS Studio
    #9
    SToons
    Max Output Level: -81 dBFS
    • Total Posts : 478
    • Joined: 2012/05/14 15:21:14
    • Status: offline
    Re:Midi - trying to put it all together! 2012/07/17 03:39:25 (permalink)
    synkrotron


    I'll chip in my two pence here, I think...

    Admittedly, I may not a "complete" expert with all things Sonar, but I do come from a MIDI background and have been creating MIDI music for over twenty years. Plus, my main area of expertise is in the use of non-sample based synthesizers. 

    In the old days, before Sonar, and before mixing consoles come into being, I would control everything via MIDI messages, either at the beginning of a track, or at any point through the track. So I am no stranger to MIDI.

    As has been mentioned here already, Velocity determines how hard an instrument is played, generally. And I say generally, because each instrument is different. Especially instruments that use multi-layered sample sets. I have always used Velocity to represent expression, although, with synths, the velocity messages act on the sound in a different way to sample based players.

    Not to confuse the issue, but... in many cases synths act similiarly to sampled instruments although sometimes synths do use velocity to control other elements of the sound. Take a synthesized snare. Usually a sound source like noise is combined with a sine/saw/square etc. wave thru an ADSR envelope to get a snare sound. Velocity could be set to control the signal so that softer velocities will produce a softer sounding hit and higher velocities will produce a harder hit by modulating the ADSR envelope. So in effect the synthesizer is programmed to mimick real snare samples. Another simple example would be to have velocity control the cutoff of a low pass filter so that notes with lower velocities sound "darker" and have less high frequency content than notes with higher velocities, again mimicking real instruments. Many synth sounds use the real-world model of sounding brighter and having more attack as the velocity increases.
     
    The vast majority of multi-sample sets use velocity as the prime method of switching between samples. There can be multi-samples within a single velocity region that are either switched randomly (often drums and percussion) or with controllers (such as switching between pedal and non-pedal sounds on a piano) but they are still primarily based on velocity-switching.
    #10
    Jump to:
    © 2025 APG vNext Commercial Version 5.1