24 Apr
2016
24 Apr
'16
3:13 a.m.
Hi all,
I have also posted this on the fluid-dev list, but maybe there is some
wisdom on LAU about it as well :)
What is the current status of synth.audio-channels and
synth.audio-groups on Linux with jack?
By starting fluidsynth with something like:
fluidsynth -a jack -o synth.audio-channels=4 -o synth.audio-groups=4 \
-o audio.jack.multi=no
I do get 4 pairs of jack audio outputs.
However the behaviour isn't as expected at least according to this (very
old post):
https://lists.nongnu.org/archive/html/fluid-dev/2004-02/msg00027.html
Ideally is there a way to have each channel routed to a separate audio
output on jack these days? Any help appreciated.
Lorenzo
24 Apr
24 Apr
2:22 p.m.
New subject: Fluidsynth: map each channel to individual jack audio output
On Sun, Apr 24, 2016 at 03:13:42AM +0200, Lorenzo Sutton wrote:
Hi all,
I have also posted this on the fluid-dev list, but maybe there is some
wisdom on LAU about it as well :)
What is the current status of synth.audio-channels and
synth.audio-groups on Linux with jack?
By starting fluidsynth with something like:
fluidsynth -a jack -o synth.audio-channels=4 -o synth.audio-groups=4 \
-o audio.jack.multi=no
I do get 4 pairs of jack audio outputs.
However the behaviour isn't as expected at least according to this (very
old post):
https://lists.nongnu.org/archive/html/fluid-dev/2004-02/msg00027.html
Ideally is there a way to have each channel routed to a separate audio
output on jack these days? Any help appreciated.
'-o synth.audio-groups=4' fails: `fluid_settings_getint' returns 1
after `process_o_cmd_line_option' (also tested with a printf).
sh> fluidsynth -a jack -o synth.audio-groups=4 <<< settings 2>/dev/null \
| grep audio-groups
synth.audio-groups 1
Idem with "-o synth.audio-channels=4 -o synth.audio-groups=4",
but "-G 4" works:
sh> fluidsynth -a jack -G 4 <<< settings 2>/dev/null | grep audio-groups
synth.audio-groups 4
There is a comment in `src/fluidsynth.c:594':
/* The 'groups' setting is only relevant for LADSPA operation
* If not given, set number groups to number of audio channels, because
* they are the same (there is nothing between synth output and 'sound card')
*/
tested with:
sh> fluidsynth -a jack -L 4 <<< settings 2>/dev/null | grep audio-groups
synth.audio-groups 4
The follow example works (audio.jack.multi=no by default):
sh> fluidsynth -a jack -L 4
load /usr/share/sounds/sf2/FluidR3_GM.sf2
select 0 1 0 0
select 1 1 0 20
select 2 1 0 30
select 3 1 0 40
5:02 p.m.
Hi Tito,
On 24/04/16 14:15, Tito Latini wrote:
Thanks for testing... However I'm not really sure what to make out of
that apart from assuming that the use case isn't directly covered by
fluidsynth?
I imagine the easiest workaround would be starting multiple fluidsynth
instances, maybe lowering poliphony (not sure what impact this has on
resource consumption), possibly scripting it...
Lorenzo.
On Sun, Apr 24, 2016 at 03:13:42AM +0200, Lorenzo
Sutton wrote:
[...]
However the behaviour isn't as expected at least according to this (very
old post):
https://lists.nongnu.org/archive/html/fluid-dev/2004-02/msg00027.html
Ideally is there a way to have each channel routed to a separate audio
output on jack these days? Any help appreciated.
'-o synth.audio-groups=4' fails: `fluid_settings_getint' returns 1
after `process_o_cmd_line_option' (also tested with a printf).
sh> fluidsynth -a jack -o synth.audio-groups=4 <<< settings 2>/dev/null \
| grep audio-groups
synth.audio-groups 1
Idem with "-o synth.audio-channels=4 -o synth.audio-groups=4",
but "-G 4" works:
sh> fluidsynth -a jack -G 4 <<< settings 2>/dev/null | grep audio-groups
synth.audio-groups 4
There is a comment in `src/fluidsynth.c:594':
/* The 'groups' setting is only relevant for LADSPA operation
* If not given, set number groups to number of audio channels, because
* they are the same (there is nothing between synth output and 'sound card')
*/
tested with:
sh> fluidsynth -a jack -L 4 <<< settings 2>/dev/null | grep audio-groups
synth.audio-groups 4
The follow example works (audio.jack.multi=no by default):
sh> fluidsynth -a jack -L 4
load /usr/share/sounds/sf2/FluidR3_GM.sf2
select 0 1 0 0
select 1 1 0 20
select 2 1 0 30
select 3 1 0 40
10:54 p.m.
New subject: Fluidsynth: map each channel to individual jack audio output
On Sun, Apr 24, 2016 at 05:01:55PM +0200, Lorenzo Sutton wrote:
Thanks for testing... However I'm not really sure
what to make out of
that apart from assuming that the use case isn't directly covered by
fluidsynth?
I imagine the easiest workaround would be starting multiple fluidsynth
instances, maybe lowering poliphony (not sure what impact this has on
resource consumption), possibly scripting it...
With stereo samples, "-L" seems what you want but I don't intend to
influence your choice.
Perhaps unclear but the follow options are the same (but '-o' is buggy):
a) -o synth.audio-channels=4 -o synth.audio-groups=4 -o audio.jack.multi=no
b) --audio-channels=4 --audio-groups=4
c) -L 4 -G 4
d) -L 4
Proof (src/fluidsynth.c):
case 'L':
audio_channels = atoi(optarg);
fluid_settings_setint(settings, "synth.audio-channels", audio_channels);
break;
[...]
if ((audio_groups == 0) && (audio_channels != 0)) {
audio_groups = audio_channels;
}
Note: some options (i.e. "audio.output-channels") are registered but
never used.
With "-a jack -L N", there is a single jack client with N*2 outputs.
In my previous example (-L 4):
output ports l_00 and r_00 for the samples used with midi chan 1
output ports l_01 and r_01 for the samples used with midi chan 2
output ports l_02 and r_02 for the samples used with midi chan 3
output ports l_03 and r_03 for the samples used with midi chan 4
26 Apr
26 Apr
9:50 a.m.
Tito,
Thanks again for the detailed explanation.
On 24/04/2016 22:47, Tito Latini wrote:
On Sun, Apr 24, 2016 at 05:01:55PM +0200, Lorenzo
Sutton wrote:
As I also wrote on the Fluidsynth dev list I'm essentially after two
possible use cases:
1. Record different instruments from a "general midi" soundfont (on
different midi channels) independently e.g. in Ardour on a track per
instrument.
2. Record drums from a drum soundfont independently to their own track
in the DAW (Ardour). In that case I would be sequencing each drum on its
own (MIDI) channel.
I'm not sure if / how -L might help on 2. as there still doesn't seem to
be a way to route a (midi) channel to an audio output.
Lorenzo.
Thanks for testing... However I'm not really
sure what to make out of
that apart from assuming that the use case isn't directly covered by
fluidsynth?
I imagine the easiest workaround would be starting multiple fluidsynth
instances, maybe lowering poliphony (not sure what impact this has on
resource consumption), possibly scripting it...
With stereo samples, "-L" seems what you want but I don't intend to
influence your choice.
12:29 p.m.
New subject: Fluidsynth: map each channel to individual jack audio output
On Tue, Apr 26, 2016 at 09:49:43AM +0200, Lorenzo Sutton wrote:
As I also wrote on the Fluidsynth dev list I'm
essentially after two
possible use cases:
1. Record different instruments from a "general midi" soundfont (on
different midi channels) independently e.g. in Ardour on a track per
instrument.
2. Record drums from a drum soundfont independently to their own track
in the DAW (Ardour). In that case I would be sequencing each drum on its
own (MIDI) channel.
I'm not sure if / how -L might help on 2. as there still doesn't seem to
be a way to route a (midi) channel to an audio output.
The follow example shows a possible preset. For simplicity, I use only
a drum kit but you can select multiple drum kits and/or other samples
(also from different soundfonts).
The drum kits in FluidR3_GM.sf2 are:
sh> echo -e "load /usr/share/sounds/sf2/FluidR3_GM.sf2\ninst 1" \
| fluidsynth 2>/dev/null | grep 128-
128-000 Standard
128-001 Standard 1
[...]
128-042 Brush 2
128-048 Orchestra Kit
The format of a line is "bank-prog name".
For example, with 10 stereo outputs (kick, snare, 3toms+floor, crash,
ride, closed and open hihat), you can create a simple config file:
sh> cat my.cfg
load /usr/share/sounds/sf2/FluidR3_GM.sf2
select 0 1 128 0
select 1 1 128 0
select 2 1 128 0
select 3 1 128 0
select 4 1 128 0
select 5 1 128 0
select 6 1 128 0
select 7 1 128 0
select 8 1 128 0
select 9 1 128 0
where the syntax of "select" (from "help event") is:
select chan sfont bank prog
Start fluidsynth with:
fluidsynth -a jack -L 10 -f my.cfg
Now the standard kit is used for the ten stereo outputs
and you can play, for example, the follow samples:
|--------------+--------+---------------|
| midi channel | sample | jack output |
|--------------+--------+---------------|
| 1 | kick | l_00 and r_00 |
| 2 | snare | l_01 and r_01 |
| 3 | hhc | l_02 and r_02 |
| 4 | hho | l_03 and r_03 |
| 5 | floor | l_04 and r_04 |
| 6 | toml | l_05 and r_05 |
| 7 | tomm | l_06 and r_06 |
| 8 | tomh | l_07 and r_07 |
| 9 | crash | l_08 and r_08 |
| 10 | ride | l_09 and r_09 |
|--------------+--------+---------------|
3:46 p.m.
On 26/04/2016 12:22, Tito Latini wrote:
On Tue, Apr 26, 2016 at 09:49:43AM +0200, Lorenzo
Sutton wrote:
Thanks Tlinux-audio-user(a)lists.linuxaudio.orgito. Will definitely try
this, looks really cool.
Lorenzo.
As I also wrote on the Fluidsynth dev list
I'm essentially after two
possible use cases:
1. Record different instruments from a "general midi" soundfont (on
different midi channels) independently e.g. in Ardour on a track per
instrument.
2. Record drums from a drum soundfont independently to their own track
in the DAW (Ardour). In that case I would be sequencing each drum on its
own (MIDI) channel.
I'm not sure if / how -L might help on 2. as there still doesn't seem to
be a way to route a (midi) channel to an audio output.
The follow example shows a possible preset. For simplicity, I use only
a drum kit but you can select multiple drum kits and/or other samples
(also from different soundfonts).
The drum kits in FluidR3_GM.sf2 are:
sh> echo -e "load /usr/share/sounds/sf2/FluidR3_GM.sf2\ninst 1" \
| fluidsynth 2>/dev/null | grep 128-
128-000 Standard
128-001 Standard 1
[...]
128-042 Brush 2
128-048 Orchestra Kit
The format of a line is "bank-prog name".
For example, with 10 stereo outputs (kick, snare, 3toms+floor, crash,
ride, closed and open hihat), you can create a simple config file:
sh> cat my.cfg
load /usr/share/sounds/sf2/FluidR3_GM.sf2
select 0 1 128 0
select 1 1 128 0
select 2 1 128 0
select 3 1 128 0
select 4 1 128 0
select 5 1 128 0
select 6 1 128 0
select 7 1 128 0
select 8 1 128 0
select 9 1 128 0
where the syntax of "select" (from "help event") is:
select chan sfont bank prog
Start fluidsynth with:
fluidsynth -a jack -L 10 -f my.cfg
Now the standard kit is used for the ten stereo outputs
and you can play, for example, the follow samples:
|--------------+--------+---------------|
| midi channel | sample | jack output |
|--------------+--------+---------------|
| 1 | kick | l_00 and r_00 |
| 2 | snare | l_01 and r_01 |
| 3 | hhc | l_02 and r_02 |
| 4 | hho | l_03 and r_03 |
| 5 | floor | l_04 and r_04 |
| 6 | toml | l_05 and r_05 |
| 7 | tomm | l_06 and r_06 |
| 8 | tomh | l_07 and r_07 |
| 9 | crash | l_08 and r_08 |
| 10 | ride | l_09 and r_09 |
|--------------+--------+---------------|
11:08 p.m.
On 26/04/16 15:46, Lorenzo Sutton wrote:
On 26/04/2016 12:22, Tito Latini wrote:
> On Tue, Apr 26, 2016 at 09:49:43AM +0200, Lorenzo Sutton wrote:
>> As I also wrote on the Fluidsynth dev list I'm essentially after two
>> possible use cases:
>> 1. Record different instruments from a "general midi" soundfont (on
>> different midi channels) independently e.g. in Ardour on a track per
>> instrument.
>> 2. Record drums from a drum soundfont independently to their own track
>> in the DAW (Ardour). In that case I would be sequencing each drum on its
>> own (MIDI) channel.
>>
>> I'm not sure if / how -L might help on 2. as there still doesn't seem to
>> be a way to route a (midi) channel to an audio output.
[...]
Well I tested this and it definitely works!
Essentially it all boils down to using the -L switch.
Indeed the mapping is fixed (chan 1 -> output 1) and will wrap around if
you have N < 16 (e.g. with 10 audio outputs chan 11 will start again on
output l_00 / r_00), but I guess one can live with that once you know
the logic.
Thanks again Tito for the detailed explanations and great tip ;)
Lorenzo.
2:52 p.m.
New subject: Fluidsynth: map each channel to individual jack audio output
Lorenzo Sutton <lorenzofsutton(a)gmail.com> writes:
2. Record drums from a drum soundfont independently to
their own track
in the DAW (Ardour). In that case I would be sequencing each drum on
its own (MIDI) channel.
I'm often wanting to do something like this also. I often want to send
each drum out my interface to a physical mixer, to process each drum
separately in different channels on the mixer, and then bring them back
to re-record on new tracks.
I had hoped that maybe drumkv1 would get the ability to send to separate
Jack outputs at some point, but it looks like for now, the only
convenient way to do something like this is to use Hydrogen's multiple
output feature, and use the patchbay in QJackCtl to setup an automatic
mapping of Hydrogen outputs to audio interface outputs (so you don't
need to set this up yourself each time). This ends up basically
marrying you to Hydrogen for this sort of thing, but like you, I haven't
found a way to expediently send individual drums from a soundfont to
different outputs, and drumkv1 won't do that either, so there may not
really be another way. You may have to just use Hydrogen whenever you
want individual drum tracks.
--
- Brent Busby + ===============================================
+ "With the rise of social networking
-- Keycorner -- + sites, computers are making people
-- Recording -- + easier to use every day."
----------------+ ===============================================
3 p.m.
New subject: Fluidsynth: map each channel to individual jack audio output
On Tue, Apr 26, 2016 at 8:52 AM, Brent Busby <brent(a)keycorner.org> wrote:
Lorenzo Sutton <lorenzofsutton(a)gmail.com>
writes:
Nightly builds (and thus the next release) of Ardour will let you do all
this.
Watch this:
https://www.youtube.com/watch?v=XCTGs2p3P74
major kudos to robin gareus for his incredible work on this functionality.
2. Record drums from a drum soundfont
independently to their own track
in the DAW (Ardour). In that case I would be sequencing each drum on
its own (MIDI) channel.
I'm often wanting to do something like this also. I often want to send
each drum out my interface to a physical mixer, to process each drum
separately in different channels on the mixer, and then bring them back
to re-record on new tracks.
3:46 p.m.
On 26/04/2016 15:00, Paul Davis wrote:
On Tue, Apr 26, 2016 at 8:52 AM, Brent Busby <brent(a)keycorner.org
<mailto:brent@keycorner.org>> wrote:
Lorenzo Sutton <lorenzofsutton(a)gmail.com
<mailto:lorenzofsutton@gmail.com>> writes:
Thanks for highlighting this, it's really cool (and +1 on kudos to
Robin) looking forward to trying it.
Lorenzo.
2. Record drums from a drum soundfont
independently to their own
track
in the DAW (Ardour). In that case I would be
sequencing each drum on
its own (MIDI) channel.
I'm often wanting to do something like this also. I often want to send
each drum out my interface to a physical mixer, to process each drum
separately in different channels on the mixer, and then bring them back
to re-record on new tracks.
Nightly builds (and thus the next release) of Ardour will let you do all
this.
Watch this:
https://www.youtube.com/watch?v=XCTGs2p3P74
major kudos to robin gareus for his incredible work on this functionality.
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
3:24 p.m.
On Tue, 26 Apr 2016, Brent Busby wrote:
Lorenzo Sutton <lorenzofsutton(a)gmail.com>
writes:
Not fluid or a sound font, but nicer sound anyway :)
Open Ardour
Add a midi track
Put DrumGizmo in the processor box
jack_lsp output shows:
...
ardour:MIDI/audio_out 3
ardour:MIDI/audio_out 4
ardour:MIDI/audio_out 5
ardour:MIDI/audio_out 6
ardour:MIDI/audio_out 7
ardour:MIDI/audio_out 8
ardour:MIDI/audio_out 9
ardour:MIDI/audio_out 10
ardour:MIDI/audio_out 11
ardour:MIDI/audio_out 12
ardour:MIDI/audio_out 13
ardour:MIDI/audio_out 14
ardour:MIDI/audio_out 15
ardour:MIDI/audio_out 16
...
You can either process them externally or send them to their own tracks
and process internally.
--
Len Ovens
www.ovenwerks.net
2. Record drums from a drum soundfont
independently to their own track
in the DAW (Ardour). In that case I would be sequencing each drum on
its own (MIDI) channel.
I'm often wanting to do something like this also. I often want to send
each drum out my interface to a physical mixer, to process each drum
separately in different channels on the mixer, and then bring them back
to re-record on new tracks.
3207
days inactive
3209
days old
linux-audio-user@lists.linuxaudio.org
11 comments
5 participants
participants (5)
-
Brent Busby -
Len Ovens -
Lorenzo Sutton -
Paul Davis -
Tito Latini