2eaa0183ef0b051dac40ab61e3a23716fd2f56a3
When bouncing Region or Range, Session::write_one_track() blocks processing, but takes no process-lock. It is possible that a latency-callback arrives at the same time while Route::bounce_process is active and calls ::run. This can trigger a delayline.cc Assertion `lm.locked ()' failed in either thread. Now latency-callbacks are postponed until the session can process normally again
Please see the Ardour web site at https://ardour.org/ for all documentation..
For information on building ardour:
https://ardour.org/development.html
Description
Languages
C++
56.5%
C
39.6%
JavaScript
1.3%
Lua
0.9%
Python
0.6%
Other
0.9%