|
|
image.png (35,902 bytes) |
|
|
Maybe related, or idea : Allow custom panners by map strip panner to "standardized" plugin controls. Eg : I have a custom panner in my strip, i can say to the strip "the panner is this plugin", and the L/R or XYZ Width controls are sent to the plugin. Ambisonic everywhere ! ;) |
|
|
@wargreen that has been the initial idea. Panners in ardour are plugins (dynamically loaded shared libs: https://github.com/Ardour/ardour/tree/master/libs/panners). Ardour offers five controls available for each panner: * Azimuth * Elevation * Width * Front/Back * LFE This would allow for N.m, and also ambisonics. However so far nobody volunteered to add more panner plugins beyond the basic ones. VBAP is also only half baked (automation is not implemented). For ambionics however, you can simply use a LV2 or VST3 plugin instead ... |
|
|
PS. There is another proposal to only use meta-data for panning, until the signal reaches the graph boundary. This would be required for Atmos. So far Ardour directly pans the audio signal on each track. This allows to have direct outs, and use JACK for connections. The alternative would be that the audio output of each track remains unpanned and the pan-information is sent along with it until the final stage where summing and panning happens. |
|
|
I do use a lv2 for ambisonic :) But it would be wonderful to use the ardour's UI / OSC control for spat. I've made this lv2 from my faust code but C is really out of my knowledge. is it imaginable to get a kind of panner "load plugin" ? |
|
|
Interesting... |
|
|
What if Ardour has an option to replace the Default Panner in the mixer with an External Panner Plugin that works across the entire project for multiple audio tracks? Say you can implement an industry standard panner (Whether its LV2, VST2, or VST3) as an alternative to the default with the features to add multiple speaker outputs and position them and link them through Ardour's Input/Output nodes? |
- Anonymous
