Age | Commit message (Collapse) | Author |
|
|
|
(although I'm not sure if it's actually used yet in the Windows build).
|
|
I'm not entirely sure why it's needed in 'smf_source.cc' but MSVC fails to link the compiled module if I don't #include it ?!?
|
|
|
|
|
|
(libardour)
|
|
file format (ver 5) rather than the older v3 format
|
|
(haven't built any fluidsynth plugins yet)
|
|
(libardour)
|
|
|
|
|
|
|
|
the static libraries)
|
|
|
|
|
|
|
|
|
|
|
|
MSVC)
|
|
|
|
|
|
adapted from John Emmas' lua branch
|
|
|
|
|
|
|
|
|
|
|
|
|
|
(mostly these got moved out of the PortAudio backend and into libpbd)
|
|
building with MSVC)
|
|
|
|
|
|
(just to be on the safe side)
|
|
|
|
When building with MSVC, some libraries had PROGRAM_NAME set to "Mixbus" and PROGRAM_VERSION set to "3". Whereas other libraries had PROGRAM_NAME set to "Mixbus3" while PROGRAM_VERSION was an empty string.
I've a horrible feeling there must have been a reason for this but I can't quite think what it was. Hopefully though, this change will standardize everything.
|
|
|
|
|
|
These changes are MSVC specific and shouldn't affect the other builds.
|
|
|
|
|
|
|
|
Among other things, this means that automation controls/lists have the actual
min/max/normal/toggled of parameters, and not those inferred from the Parameter
ID, which is not correct for things like plugin parameters.
Pushing things down to the Evoral::ParmeterDescriptor may be useful in the
future to have lists do smarter things based on parameter range, but currently
I have just pushed down the above-mentioned currently used attributes.
|
|
This is not used anywhere in Evoral and is just a wrapper around the PBD
RingBuffer anyway. Towards a (once again?) independently buildable/testable
Evoral and fewer cross-dependencies.
|
|
|
|
debuggable versions if we need to
|
|
|
|
(new preprocessor directive - greatly improves CPU loading)
|
|
(after updating to the latest versions of serd, sord, sratom and lilv)
|
|
opposed to just 'Mixbus')
It'd be nice if we could use 'ARDOUR::config_dir_name' for this purpose (or perhaps 'PROGRAM_VERSION'). However, neither is implemented widely enough at present to make this practical. Keep an eye on them though, as possible future strategies.
|
|
|