1bd15bef6c
Add methods in EngineControl for blocking and unblocking signals
...
Only intended to be used with the nested SignalBlocker class
2015-08-11 09:24:52 +10:00
324b5ffbac
Refactor part of EngineDialog ctor into connect_changed_signals method
2015-08-11 09:24:52 +10:00
f428cb4bf1
Refactor part of EngineControl::set_state into new set_current_state method
2015-08-11 09:24:52 +10:00
a9c149216d
Remove unused method in EngineControl dialog
2015-08-11 09:24:52 +10:00
2437bbbe23
Fix state restoration in Engine dialog for Backends with driver selection
...
Connect to the backend_combo changed signal after setting state as calling
backend_combo.set_active_text() in set_state was triggering backend_changed(),
which would then see the driver_combo had not been set and set it to the
incorrect value.
The value/name of the backend needs to be restored first then we can populate
the driver combo and set the correct active entry from the saved state. After
which backend_changed() will populate the device combo's etc so they can then
be set to the correct active values from the saved state.
2015-07-31 09:59:53 +10:00
d9f24a46aa
Allow selection of input and output devices in EngineDialog for backends that support it
...
Some refactoring was necessary to avoid code duplication
Restoring of device state for input and output devices still doesn't work
correctly. I'm not quite sure what the issue is at this stage.
2015-05-31 20:02:07 +02:00
dd6ee69ef8
engine dialog, update device is changed.
2015-03-07 14:35:33 +01:00
818ed5fe12
update Engine Dialog when devices are dis/connected.
2015-03-06 06:24:56 +01:00
031f68fb9d
add a simple status indicator to the Engine Dialog
2015-01-25 10:19:46 +01:00
d2cbb28f79
Engine Dialog: fix various signal connections
...
connect/disconnect button was connected multiple times
Also the button allowed to start a backend with
invalid settings (after changing backend).
Q: does “Connect to” make sense? It’s redundant with
“Apply”.
2015-01-17 21:03:56 +01:00
001e4ca684
Engine Dialog: focus OK button (press enter to cont w/previous settings)
2014-09-01 22:06:45 +02:00
371bf59a94
for backends w/o control, save a fake state with only the "active" attribute.
...
This makes ardour start directly with external jack without asking if jack
was previously used. It also retains jackd settings if jackd was previously
started by ardour.
2014-06-23 05:12:08 +02:00
33ea2d25f1
hide "turn down volume" label for midi-latency measurement
2014-06-16 23:36:29 +02:00
61ab4f0fb0
be smart, use boost::shared_ptr
2014-06-15 13:24:41 +02:00
f312113163
enable ArdourButton focus in EngineDialog
2014-06-14 00:22:32 +02:00
2e88935bbf
add GUI for midi-device settings (and properly indent the code)
2014-06-13 12:01:55 +02:00
eb289a76af
basic Midi latency measurement GUI (re-use Audio latency notebook)
2014-06-08 14:48:10 +02:00
4c0a274b43
do not push new state to backend from audio/MIDI setup until OK or Apply are clicked (i.e. do not do this when device is changed)
2013-11-27 17:41:22 -05:00
4404a38996
prevent button in latency measurement dialog from changing size when relabelled
2013-10-15 14:55:54 -04:00
6e0a3c4853
try to prevent crash if running latency calibration with JACK setup that is lacking input or output ports (re: #5721 and #5719 )
2013-10-15 13:15:03 -04:00
e0a3c3f4fa
rework things for Audio/MIDI setup dialog a bit: no tabs being the most noticeable change
2013-10-12 14:57:32 -04:00
b194c1ad88
more fixes and rationalizations for MIDI option handling in the audio MIDI setup
2013-10-10 16:18:27 -04:00
645e9caeee
basic use of new backend MIDI options
2013-10-10 12:59:33 -04:00
cff174b541
move rate_as_string() from EngineControl to utils.cc
2013-09-23 21:35:17 -04:00
57d24608e7
show a different audio/MIDI option screen if JACK is already running. try to fix problem with using AudioBackend::<property-value>() functions before anything has been set.
2013-09-19 15:03:20 -04:00
f51537b71d
substantive changes to allow the audio/MIDI setup dialog to change settings as intended
...
So far only tested with JACK backend, but expected to be more correct for other backends too
2013-09-17 21:09:13 -04:00
7381390565
add basic display of existing MIDI ports to audio/MIDI setup
2013-09-17 10:01:24 -04:00
cb31e34a5c
end latency detection if AMS window closed while running detection (plus some non-functioning changes to try to get spinbutton text entry to work
2013-09-16 18:47:30 -04:00
2a3dfb5e82
various bits of polish for the latency tab of audio/midi setup dialog
2013-09-16 15:21:32 -04:00
7c88670680
lots of changes to auto-start (and stop) the backend for latency measurements, and continuing work on the session construction/engine configuration flow
2013-09-12 16:28:51 -04:00
6b3907d57f
change names, add comment, improve return type to avoid extra call to get EngineControl::State*
2013-09-12 12:26:59 -04:00
91e2eab01a
make use of measured latency values to set dialog controls, and use actual port latency to compute extra delay
2013-09-11 13:02:32 -04:00
bede012727
remove unused members and code from EngineControl dialog (related to different devices for input+output)
2013-09-11 12:05:51 -04:00
676ff80697
basic functionality for hardware latency measurement
2013-09-10 22:58:33 -04:00
209e4bdcae
many changes relating to session construction and audioengine interaction
...
every session member is now initialized using C++ constructor syntax
session construction reordered to clarify the split(s) between work
where the engine is not relevant and work where is it is. this
split is still not 100% obvious, but is enormously clearer than
previously.
if engine/backend are not running as session is created, and the SR
of the sample rate is known, attempt to force backend to that value.
2013-09-10 15:41:19 -04:00
2a89234027
move control app launching back into audio backend to allow ASIO/CoreAudio model to work; push initial state of AMS dialog to backend
...
Issues remain with the basic model of the AMS dialog - when is
newly chosen state pushed into the backend (which can then
modify the control app button sensitivity. This is a special
problem for this button because APIs like ASIO and CoreAudio
probably don't allow us to launch a control app for an arbitrary
device, but only one actually in use. In this sense it is
different from properties like available buffer size etc, where
we can typically query without actually using the device.
2013-09-09 21:23:12 -04:00
3633892eaa
fix crash when unconditionally using null env var; tweak packing of control app button
2013-09-09 17:10:58 -04:00
f06187735d
initial work on adding access to h/w control apps when ardour starts JACK
2013-09-09 15:17:43 -04:00
56465fda10
move engine dialog from a widget to an actual dialog; emit Session::AudioEngineSetupRequired when loading a session if it is necessary
2013-09-09 15:17:42 -04:00
e435f22793
add input/output channel counts and reorganize table somewhat
2013-09-06 21:00:01 -04:00
0467231d6e
save/restore I/O latency values in audio/midi setup
2013-09-06 16:43:02 -04:00
bc1cc154dc
always save/keep audio/MIDI setup states so that they are available for use *after* instances where JACK was already running
2013-09-05 14:21:25 -04:00
5a3cf3363b
save and restore the selected engine state at startup
2013-09-04 22:58:56 -04:00
0cc4ee7b79
fix up restoration of saved state from disk, still incomplete
2013-09-04 22:22:18 -04:00
418f2ff20a
save and restore audio/MIDI setup states to disk (in ardour.rc)
...
Not finished because the buffer size value will not always stick during restore
2013-09-04 19:34:43 -04:00
58dd0198e6
save and restore settings for different backend/driver/device combinations
...
So far, this is only internal - never saved to disk
2013-09-04 15:45:54 -04:00
35cc3245db
rename interface_ stuff in the engine dialog to device_, since that feels a bit clearer terminology
2013-09-04 12:37:44 -04:00
f44e0f33af
a few more visual tweaks and simplifications for audio/midi setup
2013-08-09 00:50:41 -04:00
743bb5066e
some rearrangements and details for the engine dialog
2013-08-08 23:31:35 -04:00
a66e3859e1
can now start JACK based on config dialog
2013-08-05 12:51:51 -04:00
