Re: [fluid-dev] Manipulating the 16,384 values of pitch bend

[David Bellows]

Hey Ben,

> The pitch bend controller simply moves between the upper and lower limits. 
> The pitch bend RANGE is what you need to set. I don't know what the default 
> is for FS, but from what you said it sounds like it is 4 semitones

I think I've found it now. By sending 0 to "control_change" 100 and
101 and then sending 1 to control_change 6 this gives me one semitone
up and down. I don't see a way to just just get one semitone up,
though. I am closer now, at least.

Thanks,
Dave

On Sun, Aug 14, 2016 at 4:20 PM, Ben Gonzales <address@hidden> wrote:
> Hi Dave.
>
> The pitch bend controller simply moves between the upper and lower limits.
> The pitch bend RANGE is what you need to set. I don't know what the default
> is for FS, but from what you said it sounds like it is 4 semitones
>
> Google "pitch bend range" and you'll get the required MIDI commands
>
> Ben
>
>
> On 15/08/16 04:09, David Bellows wrote:
>>
>> I'm working on a project that generates music using any tuning the
>> user selects. I had been using Timidity because it supports the MIDI
>> Tuning Standard. However, I just discovered that it supports it badly.
>>
>> So now I've switched to using pitch bend with Fluidsynth. The fact
>> that it allows for 256 channels instead of the MIDI standard 16 pretty
>> much solves most  of my problems that I was having with Timidity.
>>
>> Here's where things get interesting.
>>
>> When using Timidity and the MIDI Tuning Standard I was able to get
>> 16,384 pitches between each semitone. When using pitch bend, though,
>> that same number of values, 16,384 pitches is stretched between two
>> whole tones (four semitones). This is interesting because Timidity is
>> capable of the higher resolution.
>>
>> My question is, can Fluidsynth handle this higher resolution and I can
>> I tell it to use all 16,384 values between two semitones instead of
>> stretched across the two whole tones? It seems like a bit of magic but
>> if it can do this then my problems are truly solved.
>>
>> Thanks,
>> Dave
>>
>> _______________________________________________
>> fluid-dev mailing list
>> address@hidden
>> https://lists.nongnu.org/mailman/listinfo/fluid-dev
>
>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/fluid-dev