Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

5.0.0 #3

Merged
merged 7 commits into from
Jun 1, 2016
Merged

5.0.0 #3

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
147f569
accept buffer_size in reader nif
Jun 1, 2016
ed9e3bb
make reader nif return list of messages, with timestamp
Jun 1, 2016
d202f7a
make writer nif accept list of messages, with timestamps
Jun 1, 2016
b69b8b4
update README
Jun 1, 2016
6899049
bump version to 4.0
Jun 1, 2016
4bc46a4
bump version to 5.0.0
Jun 1, 2016
f1e50b8
update CHANGELOG
Jun 1, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
update CHANGELOG
  • Loading branch information
Andrea Rossi committed Jun 1, 2016
commit f1e50b8025add365197d6aac4c071c6fbaded01e
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,10 @@
# Changelog

## 5.0.0
* `@ 147f569` - `PortMidi.Reader` now passes a `buffer_size` to the underlying nif, saving MIDI messages from being lost. This `buffer_size` is set to 256 by default, and can be configured at application level: `config :portmidi, buffer_size: 1024`
* `@ ed9e3bb` - `PortMidi.Reader` now emits messages as lists, no more as simple tuples. Sometimes there could be only one message, but a list is always returned. The tuples have also changed structure, to include timestamps, that were previously ignored: `[{{status, note1, note2}, timestamp}, ...]`
* `@ d202f7a` - `PortMidi.Writer` now accepts good old message tuples (`{status, note1, note2}`), event tuples, with timestamp (`{{status, note1, note2}, timestamp}`) or lists of event tuples (`[{{status, note1, note2}, timestamp}, ...]`). This is the preferred way for high throughput, and can be safely used as a pipe from an input device.

## 4.1.0
* `@ 614a27e` - Opening inputs and outputs now return `{:error, reason}` if Portmidi can't open the given device. Previously, the Portmidid NIFs would just throw a bad argument error, without context. `reason` is an atom representing an error from the C library. Have a look at `src/portmidi_shared.c#makePmErrorAtom` for all possible errors.

Expand Down