Hi,
I'm trying to split pipes and can't figure out the pipeline syntax.
In the example (see attachment) there is a single 2-channel pipe which i want to split into two parallel 1-channel pipes. Assuming it's possible I can't seem to figure out how to specify it in the pipeline section.
Any Help?
Attempt at config file:
[at least in the post preview all the leading spaces get removed. In case that's how it goes out I've attached the file below (adding .txt to the name as it won't let me attach a .yml file - sigh)
--------------------------------------
devices:
adjust_period: 3
capture:
channels: 2
device: CamillaLivingRoomSource
format: FLOAT32LE
type: CoreAudio
capture_samplerate: 48000
chunksize: 1024
enable_rate_adjust: true
playback:
channels: 2
device: CamillaLivingRoomSink
exclusive: true
format: FLOAT32LE
type: CoreAudio
queuelimit: 4
rate_measure_interval: 1
samplerate: 48000
silence_threshold: -85
silence_timeout: 10
stop_on_rate_change: false
target_level: 0
filters:
filter_a:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_b:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_1:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_2:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
mixers:
mixer_ab:
channels:
in: 2
out: 2
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -12
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -12
inverted: false
mute: false
mixer_1:
channels:
in: 2
out: 1
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -12
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -6
inverted: false
mute: false
mixer_2:
channels:
in: 2
out: 1
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -6
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -12
inverted: false
mute: false
pipeline:
- name: mixer_ab
type: Mixer
- channel: 0
names:
- filter_a
type: Filter
- channel: 1
names:
-filter_b
type: Filter
#out of desperation I tried indenting the below one space - flailing!
- name: mixer_1
type: Mixer
- channel: 0
names:
- filter_1
type: Filter
- name: mixer_2
type: Mixer
- channel: 0
names:
- filter_2
type: Filter
I'm trying to split pipes and can't figure out the pipeline syntax.
In the example (see attachment) there is a single 2-channel pipe which i want to split into two parallel 1-channel pipes. Assuming it's possible I can't seem to figure out how to specify it in the pipeline section.
Any Help?
Attempt at config file:
[at least in the post preview all the leading spaces get removed. In case that's how it goes out I've attached the file below (adding .txt to the name as it won't let me attach a .yml file - sigh)
--------------------------------------
devices:
adjust_period: 3
capture:
channels: 2
device: CamillaLivingRoomSource
format: FLOAT32LE
type: CoreAudio
capture_samplerate: 48000
chunksize: 1024
enable_rate_adjust: true
playback:
channels: 2
device: CamillaLivingRoomSink
exclusive: true
format: FLOAT32LE
type: CoreAudio
queuelimit: 4
rate_measure_interval: 1
samplerate: 48000
silence_threshold: -85
silence_timeout: 10
stop_on_rate_change: false
target_level: 0
filters:
filter_a:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_b:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_1:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
filter_2:
parameters:
freq: 300
gain: .01
q: 0.4
type: Peaking
type: Biquad
mixers:
mixer_ab:
channels:
in: 2
out: 2
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -12
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -12
inverted: false
mute: false
mixer_1:
channels:
in: 2
out: 1
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -12
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -6
inverted: false
mute: false
mixer_2:
channels:
in: 2
out: 1
mapping:
- dest: 0
mute: false
sources:
- channel: 0
gain: -6
inverted: false
mute: false
- dest: 1
mute: false
sources:
- channel: 1
gain: -12
inverted: false
mute: false
pipeline:
- name: mixer_ab
type: Mixer
- channel: 0
names:
- filter_a
type: Filter
- channel: 1
names:
-filter_b
type: Filter
#out of desperation I tried indenting the below one space - flailing!
- name: mixer_1
type: Mixer
- channel: 0
names:
- filter_1
type: Filter
- name: mixer_2
type: Mixer
- channel: 0
names:
- filter_2
type: Filter
Attachments
Last edited:
You can't put several mixers in parallel. Do you want to build some sort of crossfeed? Then use a single 2-to-2 mixer and add both input channels (with suitable gain) as sources for both of the output (destination) channels.
Hi Henrik,
This came from my compressor as driver protection thread and looking for an alternative to putting 17 compressors in series to get single channel compression (really limiting with attack and release settings) on each of 17 outputs (5.4 with 3-way L,C,R satellites, 2-way side satellites and four 1.2 ft^3 subs placed for smoothest room response).
Turns out the DAC I just got (used MOTU 24ao) has that functionality with its internal DSP - probably a better place to have it anyway.
What I really want is a single channel limiter whose control chain models driver voicecoil temperature. Unfortunately the required modeling data would be hard to come by without burning up a bunch of drivers - not on my budget.
I continue to be impressed by and grateful for your work. Thank you!!
Cheers, Louis
This came from my compressor as driver protection thread and looking for an alternative to putting 17 compressors in series to get single channel compression (really limiting with attack and release settings) on each of 17 outputs (5.4 with 3-way L,C,R satellites, 2-way side satellites and four 1.2 ft^3 subs placed for smoothest room response).
Turns out the DAC I just got (used MOTU 24ao) has that functionality with its internal DSP - probably a better place to have it anyway.
What I really want is a single channel limiter whose control chain models driver voicecoil temperature. Unfortunately the required modeling data would be hard to come by without burning up a bunch of drivers - not on my budget.
I continue to be impressed by and grateful for your work. Thank you!!
Cheers, Louis
Last edited:
Ok got it! The current compressor is primarily made for working on several channels. It can be used for single channels but as you say it gets a bit clunky when there are many channels. For that use case it would be better with a compressor filter instead of a processor. That would be easy to add in a future version. 3.0 is nearly ready, this could go in a 3.1.