Before, an export format with an invalid enum value (for example in the Encoding id) would crash Ardour with: unhandled exception (type std::exception) in signal handler: what: unknown enumerator FOO in PBD::EnumWriter That kind of error can happen if a new type is introduced and users switch back to versions without it. Instead, catch such exceptions while loading a format, log an error, and skip the format - similar to how other format loading errors are handled. |
||
---|---|---|
doc | ||
gtk2_ardour | ||
headless | ||
libs | ||
luasession | ||
msvc_extra_headers | ||
MSVCardour3 | ||
MSVCMixbus3 | ||
MSVCvst_scan | ||
session_utils | ||
share | ||
tools | ||
.dir-locals.el | ||
.gitattributes | ||
.gitignore | ||
ardour.1 | ||
COPYING | ||
nutempo-todo | ||
PACKAGER_README | ||
README | ||
README-GITHUB.txt | ||
system_config | ||
TRANSLATORS | ||
waf | ||
wscript |
Please see the Ardour web site at https://ardour.org/ for all documentation.. For information on building ardour: https://ardour.org/development.html