View Issue Details

IDProjectCategoryView StatusLast Update
0008245ardourfeaturespublic2020-08-20 15:59
Reportersapista Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformArchOSLinuxOS Version(any)
Product Version6.0 
Summary0008245: OSC feature request: better automation control for pan and trim gain
DescriptionThe current Ardour OSC implementation allows controlling most Ardour mixer features. However, some automation messages are not available for some Ardour mixer controls.

More precisely I'm missing the following OSC commands:

1. Touch commands for panner and trim gain. Since I'm mapping touch-sensitive motorized faders to these controls it will be nice to allow the "touch mode" to work properly on them:
    /select/pan_stereo_position/touch
    /select/pan_stereo_width/touch
    /select/trimdB/touch

2. It is very convenient to have the automation mode of a fader (manual, play, write, touch or latch) mapped to a button in the osc control surface. This way it is really fast to set the appropriate mode for a strip and start mixing with automation. Otherwise, using the Ardour GUI to set the automation mode with mouse clicks... well it works but is not a fast workflow. So, I suggest implementing the following osc commands to set the automation mode of panners and trim gain directly from my control surface as I'm currently doing with faders.
    /select/pan_stereo_width/automation
    /select/pan_stereo_position/automation
    /select/trimdB/automation

This list could be expanded to allow a complete osc automation support to any possible Ardour control: sends, plugins, etc...
TagsNo tags attached.

Activities

ovenwerks

2020-08-20 15:59

reporter   ~0024947

Automation added for pan azimuth and width as well as trim and mute. Automation for plugin parameters may be some time coming and won't be a part of this fix. Plugins might have well over 100 parameters that could be automated and the best way of dealing with that so far is to allow them to be looked at in banks or pages. This would make automating two parameters on two different pages not possible. So before I think about adding automation, I may look at allowing a single custom page.

Issue History

Date Modified Username Field Change
2020-06-15 16:42 sapista New Issue
2020-08-20 15:59 ovenwerks Status new => closed
2020-08-20 15:59 ovenwerks Resolution open => fixed
2020-08-20 15:59 ovenwerks Note Added: 0024947