# Changelog

## 1.0.53

* Support receiving truncated `SysEx` messages

  This can happen when a MIDI device sends a large amount of data using a `SysEx` message, which is then delivered in multiple batches - now such messages can be received and reconstituted into a single `SysEx` message.

## 1.0.52

* Added Linux support - thanks [abirke](https://github.com/abirke)

## 1.0.51

* Added missing System Common Messages:
  * MIDI Time Code Quarter Frame
  * Song Position Pointer
  * Song Select
  * Tune Request

## 1.0.50

* Pulled updates for `rtmidi` from [upstream](https://github.com/thestk/rtmidi)

## 1.0.49

* Pulled updates for `rtmidi` from [upstream](https://github.com/thestk/rtmidi) and compiled new unmanaged binaries for macOS (*x64*) and Windows (*x64, x86*)
  * Changed the `rtmidi_get_compiled_api` to take an additional `unsigned int apis_size` indicating the size of the array for `RtMidiApi` enums
* No changes in public-facing code, so will not break existing code

## 1.0.48.1

* Bug fix for receiving **SysEx** messages - thanks [mat1jaczyyy](https://github.com/mat1jaczyyy)

## 1.0.48

* Support for sending and receiving **SysEx** messages - thanks [mat1jaczyyy](https://github.com/mat1jaczyyy)

## 1.0.47

First documented release with initial features and C# 7 `readonly struct` and `in` features to improve performance by making messages *immutable structs* and passing them by reference, thus reducing copy operations and allowing the compiler to optimize the code.

Supported MIDI messages:

* Channel Pressure
* Control Change
* Note On / Off
* Pitch Bend
* Polyphonic Key Pressure
* Program Change
* Non-Registered Parameter Number (*NRPN*)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://rtmidicore.micdah.dk/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.