yes, i'm basically not sure what kind of information i need to send to
xbendin. and how do i send xbendout out.
is it int or flo or whatever?
do i need to midi format it before?
what's not going the way i expect (after various different tries)
is actually outputing the pitchbend.
(not through midi format not through midiout)
I copied this from somewhere... Also I made a demonstration patch for you.
"MSB and LSB Don't let this bit of technical jargon scare you off. MSB stands for Most significant byte and LSB stands for Least significant Byte. This data format is used when 127 values are not enough for the control. Think of it like a shortwave radio. The MSB sets the coarse tuning and the LSB is the fine tuning. Synths with very finely articulated knobs may send out an MSB and LSB, but most just send an LSB. You can tell by recording a knob tweak in your sequencer, then looking at the data in the event editor. If there are two sets of controllers, each with a range of 0-127, that's what's going on, it's sending a MSB and an LSB. Don't worry about learning hexidecimal code that the programmers have to deal with. Unless you are writing music software, all that stuff is a waste of time. Just remember, coarse and fine tuning."
o.k i think i got it. this divides the pitch bend into 128 pieces of 128 pieces?
(it took a little time but in the end i just placed an operator with the pitch bend up to 24 st and saw if i hear the changes the lsb is making)
one little question. why is it that the msb receives input>/ 128
and lsb % 128?
o.k so what's the basic differences between the two methods?
if i use msblsb version i get more accuracy and less smoothness and
if i use the other method i get more fluid action but it's less tone accurate?
thank the both for your help i don't think i would have figured this out on my own.
ok ok ... wait. Now *I'm* confused!!! Perhaps this was the blind leading the blind and an apology is necessary.
If I open up xbendout.maxhelp, There's an xbendout with a 127 step slider attached and it says, "Xbendout only changes the most significant byte of the pitch message." There's a comment pointing to 64 that says "center point"
Then, after that it says "However, using xbendout with midiout, you can send messages which change both bytes."
Those two statements appear to contradict each other.
Furthermore the help file's 128 step slider seems to be manipulating the least significant byte.
How does midiout tell if it's a high resolution or low resolution signal?