I might be wrong, but I thought the pitch bend values range from -8192 to 0 to 8192.

Not that it really maters

Bristol_Jonesey


I might be wrong, but I thought the pitch bend values range from -8192 to 0 to 8192.

Not that it really maters

That's what you effectively get, but the binary representation of the data has zero as the smallest value and 16383 as the max value.  Like you said, though, not that it really matters.

Actually, it does matter. When you enter a Pitch Event of 0, your pitch won't change, but if you enter a value of 8192, it will change upward drastically. Likewise, -8192 will lower the pitch drastically.

bmdaustin


Actually, it does matter. When you enter a Pitch Event of 0, your pitch won't change, but if you enter a value of 8192, it will change upward drastically. Likewise, -8192 will lower the pitch drastically.

--yes, but as Brundlefly said earlier on this thread:

I figured it wasn't really a big deal since no one types in pitch bend values... I hope.

If someone doesn't have a pitch bend wheel, the next-best thing to do is draw in the data in the PRV, as per the instructions on this thread.  Why would anyone type pitch bend data in via the Event List--? 

RB

The biggest problem I've had with editing control information in PRV is :  You Have to SELECT the CORRECT CHANNEL. Remember when you are driving a multi-timbral soft synth or when you have moved tracks around and or comped from other tracks  it's very easy to get note values that have different base channel information and subsequently have the track output to a different channel. The easiest fastest solve is to select the track and use the Event Inspector to change all event to a specific midi channel then make sure you select that same channel in the controller view in PRV. This is from my own frustrated experience. YMMV

rbowser


If someone doesn't have a pitch bend wheel, the next-best thing to do is draw in the data in the PRV, as per the instructions on this thread.  Why would anyone type pitch bend data in via the Event List--? 

They wouldn't, of course.  But it does help to know what the data is supposed to look like.  Sometimes you need to examine the contents of the event list to diagnose strange behavior.  So, knowing that the pitch bend data value (or any MIDI controoler data value for that matter) is always zero or positive can be useful.

rbowser

bmdaustin


Actually, it does matter. When you enter a Pitch Event of 0, your pitch won't change, but if you enter a value of 8192, it will change upward drastically. Likewise, -8192 will lower the pitch drastically.

--yes, but as Brundlefly said earlier on this thread:

I figured it wasn't really a big deal since no one types in pitch bend values... I hope.

If someone doesn't have a pitch bend wheel, the next-best thing to do is draw in the data in the PRV, as per the instructions on this thread.  Why would anyone type pitch bend data in via the Event List--? 

RB

Randy, if a particular sample or instrument is out of tune, typing a single pitch bend event in the Event List can remedy that without having to ride the pitch wheel throughout the entire piece. I agree though that you wouldn't be typing in a moving pitch wheel series of events unless perhaps you had a certain stairstep technique in mind or something to that effect where a single event would define the desired change.

Dmbaer and Bmdaustin - Good stuff, thanks for the posts.  I get it now.  I so rarely go into the Event List anymore, I tend to forget about its uses.  When I need that kind of pitch correction, I've used the PRV where I can insert data and keep whittling away or adding to it until I have the value I want.  Once that's locked in, the bend stays in effect until a "zero," center node is added.  But if it's an entire track with an instrument that needs fixing, there are usually handy tuning controls on a synth to use instead of bend.

RB

Many thanks to all concerned - especially rbowser.  Sat down 20 mins ago and was determined once and for all to find out how to bend MIDI notes.  This post did it for me! 
I'm just about 100% on screen - ALL my synths are SONAR's!  So no problems that you others might have with outboard kit.  So my suggestion to those having problems... test stuff WITHIN Sonar before going out alone at night.

I found this thread through a Google search and I'm totally confused as to how to replicate this process in Music Creator 6.
 
I would like to use pitch bend, but I cannot for the life of me figure out how to implement it. Also, does the process vary between my General MIDI, Cakewalk TTS and Cakewalk SoundCenter synths?
 
Can anyone assist? Please walk me through this. Thanks in advance.