| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
extended to the other libs)
Stage 1 of 3 (more to follow)
|
|
(Mixbus itself will probably need extra changes)
|
|
using different versions of the SESSION_FILE format
|
|
libtemporal
This is mostly to see if there'll be any problems when merging these changes into Mixbus. I'm guessing there'll be some conflicts in these projects (and a lot more to follow...)
|
|
|
|
It is slightly questionable whether type specific methods like
velocity() belong on Event at all, these may be better off as free
functions. However the code currently uses them as methods in many
places, and it seems like a step in the right direction, since, for
example, we might some day have events that have a velocity but aren't
stored as MIDI messages (e.g. if Ardour uses an internal musical model
that is more expressive).
In any case, the former inheritance and plethora of sloppy casts is
definitely not the right thing.
|
|
file format (ver 5) rather than the older v3 format
|
|
|
|
|
|
libevoral itself doesn't seem to need libpthread - but by some mechanism it #includes <pbd/event_loop.h> (which now does #include <pthread.h>). So let's make sure it can be found.
|
|
(just to be on the safe side)
|
|
This change is 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.
|
|
Note that class 'MusicalTime' needn't be exportable (with a little work, this could be reverted if it affects the other builds)
|
|
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.
|
|
|
|
|
|
Note that there's no 'VS Solution' file at present and some targets haven't been built yet (e.g. 'fst')
|
