|Anonymous | Login | Signup for a new account||2017-06-28 08:39 PDT|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0002562||ardour||bugs||public||2009-02-22 13:44||2010-04-24 03:31|
|Target Version||Fixed in Version|
|Summary||0002562: After the ARDOUR_UI::engine_halted dialog appears, saving the session results in all track + bus output connections being lost|
|Description||Steps to reproduce:|
1. The "Ardour was not fast enough" dialog appears
2. User saves session
3. User restarts ardour
4. All track + bus outputs are disconnected
I've classed this as major because on a project with lots of tracks and buses it can take a long time to setup all the outputs again :(
Workaround: don't save the session. Close ardour and choose not to save. You lose any work done in the session but it's probably less work than setting up all the outputs again.
This is on Ubuntu Hardy with jackd 0.109.2-1ubuntu1 and 2.7.1 compiled from source.
|Tags||No tags attached.|
|Users sponsoring this issue|
Total Sponsorship = US$ 30
2009-02-22 13:48: nickm (US$ 25)
2009-02-22 15:20: wicked_boy (US$ 5)
hmm, Session::save_state() should refuse to work if ardour is no longer connected to JACK. can you confirm absolutely that its possible to save state when disconnected from JACK? this disabling was intended precisely to stop this behaviour (at the cost of possibly losing edits).
we do actually have all the info required to save state in the right way, but it lives in the AudioEngine object, not each port. tricky to fix, but far from impossible.
|i see now that the code in AudioEngine is wrong. the shutdown handler does not mark jack as inactive, so state saving will still be permitted. fixing that is part 1 of solving this particular bug; part two will be to make ports always save their connection state from data owned by the audio engine.|
Yes it definitely allows you to save.
I don't think re-connecting to JACK helps either but I'm not 100% sure of this.
|I experienced this same problem several times before and when reconnecting Jack I got and error about the Jack ports not existing. Connections were lost anyways.|
|I believe that this is now fixed in 2.0-ongoing (confirmation would be helpful) and will be in 2.8.1|
I'll keep an eye out for it happening again.
I sent you a paypal.
I've reproduced this and the fix looks good.
To reproduce I started a compilation of ardour in parallel with making a copy of an ardour session on my audio disk.
Then I loaded up ardour and moved the playhead around a lot during playback.
ardour copes surprisingly well, but eventually the "your computer was not fast enough" dialog appears.
ardour no longer disconnects all the jack ports! yay!
In fact, after a brief pause, ardour will continue playback.
Therefore, would it be possible to get rid of this dialog altogether, and maybe display a warning somewhere in the UI? eg in the top right status area.
|2009-02-22 13:44||nickm||New Issue|
|2009-02-22 13:48||nickm||Sponsorship Added||nickm: US$ 25|
|2009-02-22 13:48||nickm||Sponsorship Total||0 => 25|
|2009-02-22 15:20||wicked_boy||Sponsorship Added||wicked_boy: US$ 5|
|2009-02-22 15:20||wicked_boy||Sponsorship Total||25 => 30|
|2009-03-12 14:19||paul||Note Added: 0005807|
|2009-03-12 14:19||paul||Status||new => feedback|
|2009-03-13 05:21||paul||Note Added: 0005817|
|2009-03-15 11:43||nickm||Note Added: 0005821|
|2009-03-31 21:26||hectro||Note Added: 0005852|
|2009-07-03 21:53||seablade||Status||feedback => confirmed|
|2009-07-04 11:44||paul||Note Added: 0006254|
|2009-07-13 07:31||nickm||Note Added: 0006428|
|2009-07-13 09:06||nickm||Note Added: 0006429|
|2010-04-24 03:28||cth103||Category||bugs => bugs2|
|2010-04-24 03:31||cth103||Category||bugs2 => bugs|
|Copyright © 2000 - 2017 MantisBT Team|