Re: [fluid-dev] Volume background and foreground

[Element Green]

If I remember correctly, the router_begin line sets what MIDI events
are to be modified.  So for example, if you wanted to change the
channel of all MIDI notes coming in to the MIDI driver from channel 0
to 4, you would:
router_begin note
router_chan 0 0 0 4
router_end

The router_par1 and router_par2 commands can be used to filter the
events by MIDI note number and MIDI velocity, respectively.  That
could be used to map different parts of the keyboard to different
channels, etc.  I think by default they are all inclusive, so you
don't need to specify them if you are routing all MIDI notes.

Likewise for pitch bend:
router_begin pbend
router_chan 0 0 0 4
router_end

The router_chan command takes min/max/mul/add, which basically says:
if channel is greater or equal to min and less than equal to max:
multiply by 'mul' and then add 'add'.  So the above will only modify
MIDI channel 0, multiply it by 0 (which is still 0) and then add 4
(essentially setting it to 4, which would work for any other MIDI
channel as well).

Best regards,

Element Green


On Tue, Jan 31, 2012 at 3:34 AM, James Ong <address@hidden> wrote:
> Kind of not working as expected.
> router_begin requires [note|cc|prog|pbend|cpress|kpress]
>
> I tried these commands:
> prog 0 3 <- Load honky soundset
> router_begin cc  <- Tried prog
> router_chan 0 0 15 0
> router_end
> channels
>
> chan 0, Honky-Tonk
> chan 1, Acoustic Piano(mono)
> chan 2, Acoustic Piano(mono)
> chan 3, Acoustic Piano(mono)
> chan 4, Acoustic Piano(mono)
> chan 5, Acoustic Piano(mono)
> chan 6, Acoustic Piano(mono)
> chan 7, Acoustic Piano(mono)
> chan 8, Acoustic Piano(mono)
> chan 9, Groove kit1
> chan 10, Acoustic Piano(mono)
> chan 11, Acoustic Piano(mono)
> chan 12, Acoustic Piano(mono)
> chan 13, Acoustic Piano(mono)
> chan 14, Acoustic Piano(mono)
> chan 15, Acoustic Piano(mono)
>
> The honky soundset is still on channel 0, didn't it moved to channel 15?
>
>
>
>
>
>
>
> On Tue, Jan 31, 2012 at 5:29 PM, David Henningsson <address@hidden> wrote:
>> On 01/31/2012 10:19 AM, James Ong wrote:
>>>
>>> I see, how do I load this script or do I have to pass the comman manually?
>>
>>
>> You can use the --load-config option to load a file with a script in, or you
>> can use FluidSynth's built-in shell.
>>
>>
>>> Sorry, I'm kind of noob when the tutorials are too vague.
>>
>>
>> Contributions are welcome, including those who add tutorials or other types
>> of documentation :-)
>>
>>
>>>
>>>
>>> On Tue, Jan 31, 2012 at 4:37 PM, David Henningsson<address@hidden>
>>>  wrote:
>>>>
>>>> On 01/31/2012 07:51 AM, James Ong wrote:
>>>>>
>>>>>
>>>>> An idea struck me, I like to understand what does "router" in FluidSynth
>>>>> do?
>>>>> I will appreciate to learn more on this area.
>>>>
>>>>
>>>>
>>>> Yeah, that's my thought as well, wouldn't the midi router in FluidSynth
>>>> be
>>>> able to handle this case? IIRC if you run the FluidSynth executable it
>>>> will
>>>> only affect the incoming messages from the midi driver(s), not the
>>>> internal
>>>> MIDI player. (And if you use the library directly you set these things up
>>>> the way you want.)
>>>>
>>>> Something like:
>>>>
>>>> router_begin
>>>> router_chan 0 0 15 0<- reroute channel 0 to channel 15
>>>> router_end
>>>>
>>>> It was a while since I used it, so I might have forgotten the exact
>>>> syntax.
>>>>
>>>> // David
>>>
>>>
>>
>
> _______________________________________________
> fluid-dev mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/fluid-dev