Age | Commit message (Collapse) | Author |
|
|
|
fix problem with using AudioBackend::<property-value>() functions before anything has been set.
|
|
NOTE: users will lose the sample rate/latency display in the status bar display. Not yet sure what to do about this
|
|
|
|
as intended
So far only tested with JACK backend, but expected to be more correct for other backends too
|
|
happens now)
|
|
public so that we can use these when doing intentional disconnects without popping up the "HALTED" dialog
|
|
|
|
|
|
|
|
|
|
|
|
|
|
press in a window that has called relay_key_press(), so that normal key handling works there (e.g. audio/MIDI setup)
|
|
|
|
some non-functioning changes to try to get spinbutton text entry to work
|
|
|
|
n_physical_{inputs,outputs} members which were (a) not initialized early enough (b) not used anywhere except monitor bus connection.
Things almost make sense now.
|
|
state
|
|
during quit-without-finished-session
|
|
driver/device name combos
|
|
|
|
pkg-config file
|
|
both work
|
|
|
|
|
|
|
|
|
|
access to the backend
|
|
|
|
change into windows branch
|
|
|
|
This allows a derived (concrete) implementation to share information (e.g. sample rate, buffer size)
between the audio backend side of things and the port management side of things.
|
|
|
|
|
|
|
|
into its own method. sorry, ardour build-from-source folk :)
|
|
|
|
|
|
measurements, and continuing work on the session construction/engine configuration flow
|
|
in reorganization work
|
|
because there is no editor window to forward key presses to
|
|
EngineControl::State*
|
|
|
|
THIS IS A HACK. LONG TERM GOAL: understand why ardour gets zombified on the way up.
|
|
|
|
port latency to compute extra delay
|
|
no longer relevant
|
|
different devices for input+output)
|
|
|