The pkgconfig directory is no longer marked for creation assuming that
the system directory is specified in libmt32emu_PKGCONFIG_INSTALL_PREFIX
property so to avoid conflicts
- More of the package metadata fields are now filled from the CMake script
thus reducing duplications
- When the library is build with external sample rate conversion,
field Requires.private is now filled with the related dependency
(either soxr or samplerate) thus fixing build of user applications
that link against statically built libmt32emu in such cases
- Along the way, variable MT32EMU_EXT_LIBS is now unset when building
a shared library to avoid pollution of variable MT32EMU_LIBRARIES
with unnecessary dependencies
- In TVP::process, UB was possible due to right shifts with counter values
exceeding the maximum permitted limit of 31 (similarly to the original
hardware); we now attempt to emulate that in the same way as in
calcVeloMult implemented in 41980704d2
- In TVP::setupPitchChange spotted by clang static analyzer, a negative
value could be shifted left
- mt32emu_get_machine_ids enables to retrieve a list of all supported
hardware configurations as opposed to individual ROM images
- mt32emu_get_rom_ids to retrieve a list of identifiers of all supported
ROMs, optionally for a specific machine
- A couple of convenience functions to identify a given ROM image
without applying any changes to the emulation context
- New function mt32emu_add_machine_rom_file facilitates implementation
of a ROM scanner that traverses files in a given directory and adds
to the emulation context those compatible with a specific machine
That is currently concerns of a set of relevant ROMs only, thus making it
possible to find all ROMs for a desired machine configuration that are
mutually compatible and can be used in the emulation engine.
that now merely wraps <mt32emu/mt32emu.h> for convenience.
This file is autogenerated by the build system.
Although, a reorganisation of public headers is rather imminent,
but it will only happen on next major release.
When users of the library compile code with -Weffc++, this class
triggers warning:
‘class MT32Emu::Service’ has pointer data members
but does not declare ‘MT32Emu::Service(const MT32Emu::Service&)’
or ‘operator=(const MT32Emu::Service&)’
Class Service aggregates an owning raw pointer (mt32emu_context), which
is being taken over via constructor and freed in destructor - this might
lead user to accidentally double free the pointed object if a Service
object was accidentally copied through default copy c-tor or default
assignment operator.
Declare copy c-tor and operator= private to prevent creation of
accidental copy (this fixes the warning).
When upgrading this code to C++11, these declarations should be
marked with '= delete' (and won't need to be private any more).
- New functions mt32emu_merge_and_add_rom_data and
mt32emu_merge_and_add_rom_files accept a pair of ROMs to be merged
and added to the emulation context upon success
- Improved descriptions of functions mt32emu_add_rom_data and
mt32emu_add_rom_file to mention the fact that they only handle full
ROM images yet to highlight the requirement wrt. memory allocation
of the ROM data array
- Added method ROMImage::isFileUserProvided to make memory cleanup easier
wrt. freeing the File of a ROMImage which may not be created internally
as with ROMImages merged from partial ones
- Minor formatting fix in ROMImage
- Mentioned that full ROMImages are required in description of Synth::open
that apparently advertised wrong directory, making all the public
headers global. This is never the intended way and the consumer application
is instead supposed to include headers from the library directory, likewise:
#include <mt32emu/mt32emu.h>
- Added metadata describing raw bitwise ROM dumps from supported hardware
models
- New overloaded methods enable finding a ROMInfo and creating a ROMImage
for a given File and a subset of known ROMInfos, e.g. filtered by type
and/or pairType
- New methods facilitate creation of a full ROM image from a couple
of the respective partial ones
Added support for documenting easily the exact library version
when a particular exported symbol was introduced. This will help
an application developer to quickly find the version requirements
yet adds a possibility to generate version map files automatically
for platforms that support symbol versioning.
- Introduced configuration option libmt32emu_PKGCONFIG_INSTALL_PREFIX.
Because pkgconfig files reside outside the library directory on some
systems, we have to allow the packager to specify pkgconfig prefix
separately.
- The pkgconfig file is no longer included in Runtime packages with shared
library, as is commonly adopted by popular Linux distros.
When creating a Devel package for shared library in DEB and RPM formats,
the package name and resulting package file name are now adjusted
automatically (still, not splitting stuff into several cmake components).
The advanced option libmt32emu_PACKAGE_TYPE is now possible to select
regardless whether a static or shared library is built. For static builds,
values Complete and Devel are identical but for Runtime, documentation
files are only added to the package.
This permits somewhat better build experience when using the top-level
CMakeLists.txt script. Specifically, it is now easy to omit development
files and build both components mt32emu_qt and mt32emu_smf2wav statically
linked with the library with just a single cmake command like
cmake -Dlibmt32emu_PACKAGE_TYPE=Runtime .
JACK MIDI sessions
- Disabled audio recording when the synth is stopped; stopping a synth
that is recording audio now terminates the audio recording and closes
the audio file
- Temporarily disabled unsupported audio recording for JACK
with more than one MIDI session attached
- Fixed presumably broken cleanup in case write to the audio file fails
- Improved names of related methods, added a couple of comments
This method is now used in majority of audio drivers that simplifies
rendering loops or the callbacks yet ensures that all drivers invoke
the related operations in the right order.
- It now allows recording from several MIDI sources simultaneously.
When more than one MIDI session is attached to a Synth being recording
MIDI, a standard MIDI file type 1 is created subsequently that contains
recorded MIDI events of each session in a separate MIDI track, which may
be helpful while editing the MIDI file further.
- It no longer blocks the MIDI driver thread for buffer reallocations.
- Along the way, fixed writing broken MIDI files when an unsupported
MIDI message appeared. Also, fixed recording out-of-order MIDI messages
with bogus timestamps.
