All notable changes to this project will be documented in this file. This change log follows the conventions of keepachangelog.com.
Nothing so far.
1.2.0 - 2024-07-07
- Updated Ableton Link to release 3.1.2.
- Continuous Integration has been updated to move away from a deprecated Apple notarization tool.
1.1.6 - 2021-02-20
- The macOS binary is now compiled as a universal binary to include code for both x86_64 (Intel) and arm64 (Apple Silicon). This means that Xcode 12 is required for building, and therefore Catalina (macOS 10.15) is the minimum macOS version on which it can be built. The binary will still run on macOS versions back to Sierra (10.12).
1.1.5 - 2020-12-28
- Updated Ableton Link to release 3.0.3.
- Updated gflags to release 2.2.2.
- Fixed Github Actions build script.
1.1.4 - 2020-07-01
- The macOS build process now creates HFS+ (MacOS Extended) disk images rather than the default APFS filesystem that it was previously using. This allows them to be opened on High Sierra (10.12) and earlier.
- The build configuration now specifies that the macOS version should be compiled in a way that is backwards-compatible as far back as macOS 10.12, which should hopefully fix linker errors people were seeing on macOS 10.13 (issue #18).
- Updated the Ableton Link and gflags libraries.
1.1.3 - 2020-01-16
- Now automatically build and release the Mac and Windows executables whenever changes are pushed to this repository, thanks to the power of GitHub Actions.
- Mac executables are released as code-signed, notarized disk images for ease of use on Catalina.
- Updated to Link 3.0.2 and gflags 2.2.2.
1.1.2 - 2019-12-17
- A
--daemon
boolean option to shut off the status line output, since that does nothing but flood the system log when Carabiner is running as an operating system background process. - A Raspberry Pi build, since I now own one.
- Also now reports the version number in the startup message, which is helpful when scanning the system log.
1.1.1 - 2019-04-24
- It turns out that C++
long
types in 64-bit Windows are half the size of the Javalong
type used by Beat Link Trigger, so values BLT is sending as time stamps need to be declared aslong long
values in C++ to be properly received in Windows. This change fixes parse errors people were running into. (It should also make it safe to compile and run in a 32-bit OS.)
- More detailed error information is printed in the window in which
Carabiner is running when there is a problem parsing a value it has
received. Hopefully this can help figure out a problem people are
running into in Windows sometimes when the beat numbers for the
beat-at-time
command are being unusable.
1.1.0 - 2018-08-27
- A way for clients to check the Carabiner version, so Beat Link Trigger can know whether the multi-message packets issue has been fixed and warn the user to upgrade Carabiner if needed.
- If multiple messages were sent rapidly to or from Carabiner they might get grouped into a single network packet, and the later ones would be ignored. This release, along with a newer Beat Link Trigger release, process even later messages grouped in the same packet.
1.0.0 - 2018-05-24
- Implemented the
enable-start-stop-sync
,disable-start-stop-sync
,start-playing
, andstop-playing
commands, to support the new transport control features in Link 3.0. - A Windows binary, and a tip linking to instructions for building it in that environment.
- Updated the embedded Link library to version 3.0.1 to be able to support start/stop sync.
0.1.3 - 2017-07-23
- Implemented the
phase-at-time
,time-at-beat
, andrequest-beat-at-time
commands, to provide access to the rest of the Link API. - Explained the nature of Link timestamps in the documentation.
- Improved some details in the documentation.
- Updated the embedded Link library to incorporate fixes.
0.1.2 - 2017-04-22
- Updated the embedded Link library to incorporate recent improvements, such as supporting Carabiner on the Raspberry Pi.
0.1.1 - 2016-11-20
- Beat position information in status updates, for Afterglow.
- Support the actual tempo range that Link itself supports, from 20 to 999 BPM.
- Set up initial project structure.
- Figured out how to embed and work with the Link library.
- Chose communication and configuration frameworks.
- Built an implementation which meets the needs of beat-link-trigger.