add mutex/lock to all Evoral::SMF methods that use _smf/libsmf, to avoid inadvertent...
authorPaul Davis <paul@linuxaudiosystems.com>
Wed, 15 Oct 2014 19:12:02 +0000 (15:12 -0400)
committerPaul Davis <paul@linuxaudiosystems.com>
Wed, 15 Oct 2014 22:44:22 +0000 (18:44 -0400)
commitab658d7ca15ed24e073d85f43376c986c659b1cf
tree7a38bebe265d55d4d51da027c7051ad3100c03fa
parent7e764ea4051dce1f687cc9bdf92c67c110517600
add mutex/lock to all Evoral::SMF methods that use _smf/libsmf, to avoid inadvertent corruption via multithreaded access.

Serialization of Session::save_state() will already protect against most of this, but there is really no
good reason why Evoral::SMF's API should require single-threaded/explicit serialization.
libs/evoral/evoral/SMF.hpp
libs/evoral/src/SMF.cpp
libs/evoral/src/libsmf/smf_load.c
libs/evoral/src/libsmf/smf_save.c