13
0
Commit Graph

169 Commits

Author SHA1 Message Date
3d2f298fb2 Change message about JACK already running to be less scary 2015-06-03 13:48:43 -04:00
4d2bc612f2 engine dialog fixes for multiple devices 2015-06-01 01:01:42 +02: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
15bf19961f When running on Windows, hide the Engine dialog before calling 'push_state_to_backend()'
For some reason we don't understand 'push_state_to_backend()' can interfere with hiding the dialog (causing a partially hidden dialog to remain on screen). It's most likely a timing issue with the Windows version of GTK. Fortunately, reversing the calling order seems to fix it - BUT...

If there's no session loaded yet, the user can be left with a very long wait while nothing seems to be happening. The next thing the user would normally see would be the splash image. So let's display it slightly early (so the user can at least see that something's happening).

Sadly, it's all very kludgy - but a lot better than what we had before...  :)
2015-04-14 11:22:14 +01:00
40e3a01459 and 2c89ec5, keep backend running. 2015-04-07 15:23:24 +02:00
2c89ec5c0b Query backend’s setup_required() every time. fixes #6041 2015-04-04 02:39:30 +02:00
28730b4939 fancy plural form. 2015-03-31 04:16:24 +02:00
87e95e4bf1 add colon to match other labels 2015-03-26 21:43:33 -05:00
675444c7dd Engine: remember state only on “Apply” and “OK”
filed under “another scary engine dialog change”
2015-03-22 01:28:33 +01:00
7b1c7efc1c work-around engine dialog crashes.
Thanks to brilliant detective work by John E. we
can now reveal that the actual crash in
EngineControl::print_channel_count() is caused
by a seemingly unrelated exception.

The root cause however is waves/ASIO backend reporting a
buffersize that is not in list of available buffer-sizes
it reported earlier.
2015-03-16 15:09:59 +01:00
23a6526de7 remove unneeded debug output 2015-03-07 17:10:19 -06:00
dd6ee69ef8 engine dialog, update device is changed. 2015-03-07 14:35:33 +01:00
82e23ecd2a fix device changes..
backend_changed() stopped the backend.
2015-03-07 14:35:32 +01:00
818ed5fe12 update Engine Dialog when devices are dis/connected. 2015-03-06 06:24:56 +01:00
411c3ee70a possible fix for #6187 - assert(backend) 2015-03-01 16:48:14 +01:00
fbdf6a8151 recover the most recent audio setup settings from config 2015-02-24 14:29:02 -06:00
af174c0519 when the user changes devices, notify the backend 2015-02-06 13:55:00 -06:00
031f68fb9d add a simple status indicator to the Engine Dialog 2015-01-25 10:19:46 +01:00
37b8412aa3 fix latency measurement result display
If measurement is fast (<100ms), the GUI timeout function
never displayed the measured value.
2015-01-25 10:18:33 +01:00
611073790b move control app button adjacent to sample rate and bufsize settings 2015-01-22 15:00:13 -06:00
dcaf8d89c1 remove channelcount selectors for mixbus 2015-01-22 14:54:56 -06:00
49047e4dc9 consistent display of period-size. 2015-01-17 22:42:20 +01:00
cc221ea3c3 display current buffer size - hopefully w/o breaking ASIO 2015-01-17 21:29:14 +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
f77c923bee engine dialog fix buffersize sensitivity 2015-01-17 21:03:56 +01:00
7d88dc3202 update engine dialog UI state
fixes crash when jack is started externally
and the dialog is displayed later.
The current state e.g. avail buffer sizes is not
are queried from the backend, Apply,OK -> crash
because the dropdown is empty)
2015-01-17 21:03:56 +01:00
14a235ca8a fix 05a612b 2015-01-17 01:26:29 +01:00
c3847269c2 fix crash when changing the Audio System
When the i/o channel spinbox widgets are realized, they call
print_channel_count(). A "0" is formatted as "all available channels".
This causes the GTK::Entry inside the spinbox to emit a "changed"
signal which in turn triggers a parameter_changed(), [..], store_state(),
which calls into the spinbox again while it is being realized,
which makes gtkmm barf.

Start Ardour with JACK running (autoconnect to jack), Window ->
Audio/Midi settings -> initial no_control_notebook. Change
Audio System -> [control widgets are realized] -> glibmm std::exception
2014-10-03 15:32:12 +02:00
5e61c8ab12 fix engine control widget sensitivity 2014-10-03 15:08:06 +02:00
1d790355ca Fix warning from ./waf i18n about empty string
./waf i18n warns about passing an empty string to _(). Actually, the code
in question just wants to make a label not appear, so it might as well
just hide or show it as appropriate rather than attempting to set its
text to the empty string.
2014-10-02 18:03:19 +01:00
8b4eb07ab7 Fix restore of Jack driver setting
A small hack to ensure that the driver setting in the audio engine dialog
is restored when ardour starts up and when switching drivers.
2014-09-13 15:27:30 +01:00
001e4ca684 Engine Dialog: focus OK button (press enter to cont w/previous settings) 2014-09-01 22:06:45 +02:00
63d81d2419 purge states of Audio-backends that are N/A
fixes crashes/assert() when using different builds while
sharing ardour.rc with n/a engine backends marked active.
2014-07-04 15:52:14 +02:00
a3c378cf62 move utility functions into a dedicated namespace 2014-06-25 21:47:54 +02:00
1bd4e448de namespace libardour utils 2014-06-25 21:47:54 +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
3624d93001 fix latency-measurement dialog back-button. 2014-06-22 18:28:24 +02:00
edd9e730ef latency measurement dialog updates:
* distinguish errors: no ports and no engine.
* fix "No measurement results yet" message at successful end
* stop update callback
2014-06-19 19:44:15 +02:00
07759bbbf2 engine-dialog: properly restore previous active state 2014-06-19 19:44:15 +02:00
33ea2d25f1 hide "turn down volume" label for midi-latency measurement 2014-06-16 23:36:29 +02:00
fbe359e8c7 debug alsa midi latency measurement 2014-06-16 19:44:23 +02:00
f383f2b856 fix pango font style (prev commit) 2014-06-16 17:56:52 +02:00
5baa6ca5b4 no more red latency messages 2014-06-16 17:30:22 +02:00
80c7971f50 reset latency dialog every time. 2014-06-15 13:24:41 +02:00
61ab4f0fb0 be smart, use boost::shared_ptr 2014-06-15 13:24:41 +02:00
21ed2d6767 clear engine device combo when no devices are available 2014-06-15 13:24:40 +02:00
51b475467a if we don't have control over the device/backend, allow to proceed. 2014-06-14 16:26:14 +02:00
9268de566c fix initialization of audio-engine dialog 2014-06-14 16:01:46 +02:00
f312113163 enable ArdourButton focus in EngineDialog 2014-06-14 00:22:32 +02:00
f2404a522d Engine Dialog: Don't save duplicate states (and remove old dups) 2014-06-13 17:18:30 +02:00