From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin-announce@cygwin.com
Subject: wildmidi 0.4.2-1
Date: Tue, 10 Apr 2018 19:26:00 -0000 [thread overview]
Message-ID: <20180410142438.14480-1-yselkowitz@cygwin.com> (raw)
The following packages have been uploaded to the Cygwin distribution:
* wildmidi-0.4.2-1
* libWildMidi2-0.4.2-1
* libWildMidi-devel-0.4.2-1
* mingw64-i686-wildmidi-0.4.2-1
* mingw64-x86_64-wildmidi-0.4.2-1
WildMidi is a wave table player that uses gus pat sound sets to play midi
file. The WildMidi player is the frontend, and is only designed to pass
information to the core library and output any audio data the library
returns. The core of the project, libWildMidi, is the work horse behind the
player. Designed to be used in future and existing projects, its capable of
multithreading and multiprocessing of midi files, allowing for the mixing
of multiple midi file at any one time if someone had a desire to do so.
This library is what turns the midi files into audio data using the gus pat
sets.
This is an update to the latest upstream release, which includes fixes for
several CVEs:
https://github.com/Mindwerks/wildmidi/releases/tag/wildmidi-0.4.2
--
Yaakov
reply other threads:[~2018-04-10 19:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180410142438.14480-1-yselkowitz@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).