Age | Commit message (Collapse) | Author |
|
|
|
Set the AEffect* plugin pointer before calling effOpen.
effOpen may call back into the host (masterCallback) and invoke
actions which depend on _plugin (eg. to call back into the plugin again)
|
|
|
|
|
|
|
|
ScopedConnection and label,bar went out of scope.
|
|
|
|
- freeze the correct playlists on fiorst move.
- only update the start offset of linked regions once the drag
has finished.
|
|
|
|
This mechanism re-uses internal abstraction (plugin-enable).
Other plugin-specs designate a control-port, for VST we 'emulate'
a control-port.
There is still debug-output to stderr, here while testing.
|
|
|
|
|
|
|
|
This reverts commit 04ed05ecc4629d85d8f1fd3d6756669a42fb762b.
|
|
|
|
debug-prints indicat it was at least possible for the same Window to
receive FloatingTextEntry::entry_focus_out twice (without idle)
|
|
|
|
- should fix 7260
|
|
- this diffs all playlists that use the same source.
- the secons part hould be a no-op, but needs testing
(trim drag undo on audio and midi regions)
|
|
|
|
|
|
|
|
- a tempo marker may now be set to always continue (clamped)
this means that the end tempo of the previous section will
track the start tempo during tempo ops.
it mimics the behaviour in 5.8, with the gui indicating
the curves to be changed.
|
|
|
|
- GMPC does not use it directly
- when GMPC was enabled Stateful::loading_state_version was set to 1000
(the protocol is at 1.0.0)
- it messes up session-loading, particularly various plugin states and
templates (e.g Processor::set_state_2X was used)
|
|
|
|
- the spray is limited to the first entered note.
- all new notes are selected (requires a selection change to
MRV::create_note_at()
|
|
- should fix 7134
|
|
|
|
|
|
- should fix 7105
|
|
|
|
|
|
Work around logic-flow in EngineDialog which should already have
done that, but may no longer heed this special-case if sample-rate
dropdown is refreshed to only devices supported ones.
|
|
This partially reverts commit ac40945ff96f27606ff5d3600cf06b0ba663a5e1.
re-add system_config, but not instant.xml
|
|
Hotfix work around:
1) Launch without existing user-config and no system_config
2) Load or create session. save/quit.
3) re-load session. save. user-config file is corrupted in <Extra>
|
|
on key release, and vice versa
This should really be split in separate semantics for key and button events.
Fixes a subtle but nasty bug in the EngineDialog where the change of the default focus
widget from a Gtk::Button (acts on press) to an ArdourButton (acts on release) caused
events occuring after a dialog has grabbed focus to trigger button clicks
|
|
The re-order is queued to be performed click-free in realtime-context.
Meanwhile adding plugins will result in a race-condition.
|
|
|
|
If a plugin has 0 audio-outputs, and has the meta-data "InstrumentPlugin",
Ardour would interpret is as "variable number of output synth.
|
|
When a monitor-section is added, the auditioner automatically connects to
its input. However on session-reload, the connection is explicit
(by saved port-name) and Auditioner::needs_monitor() was not set.
Session::process_audition() didn't run the monitor-route. Silence.
|
|
Stop event propagation. Otherwise, on release the event is passed
up and handled by the TAV which scrolls the editor viewpoint
and the button is no longer under the mouse.
|
|
|
|
The audioMasterAutomate callback from plugin to host does include
the parameter-value.
Previously there was a redundant call
Plugin::parameter_changed_externally() -> get_parameter
-> VSTPlugin::get_parameter() back into the plugin to query the value.
calling back into the plugin from the callback, may explain
oddities and/or crashes with some VSTs.
|
|
(such as those held in a MidiPlaylist's RegionTrackers
|
|
|
|
|
|
- this is the opposite of 'Ramp to Next'.
it removes discontinuities between the
last end tempo and the current by altering the current one.
|
|
|
|
controllable->set_value() from GUI context will eventually queue
a session-rt command. By the time the realtime command runs, the
controllable needs to be in "touch" mode.
The AutomationController "toggle" UI worked around this by directly using
the underlying API (ignoring slaved-controls and ignoring groups).
The RouteUI's GUI wasn't able to write mute-automation at all.
This commit is a compromise: press + hold (touch) + release button.
(it may need further special-casing for _desc.toggled in
AutomationControl::actually_set_value(), also undoing automation-writes
is currently not working correctly)
|