[PATCH] gnu: Add wildmidi.

[PATCH] gnu: Add wildmidi.

[宋文武]

* gnu/packages/midi.scm: New file.
* gnu-system.am (GNU_SYSTEM_MODULES): Add it.
---
 gnu-system.am         |  1 +
 gnu/packages/midi.scm | 46 ++++++++++++++++++++++++++++++++++++++++++++++
 2 files changed, 47 insertions(+)
 create mode 100644 gnu/packages/midi.scm

diff --git a/gnu-system.am b/gnu-system.am
index 04e9345..86ba028 100644
--- a/gnu-system.am
+++ b/gnu-system.am
@@ -189,6 +189,7 @@ GNU_SYSTEM_MODULES =				\
   gnu/packages/mcrypt.scm			\
   gnu/packages/messaging.scm			\
   gnu/packages/mg.scm				\
+  gnu/packages/midi.scm				\
   gnu/packages/miscfiles.scm			\
   gnu/packages/mit-krb5.scm			\
   gnu/packages/moe.scm				\
diff --git a/gnu/packages/midi.scm b/gnu/packages/midi.scm
new file mode 100644
index 0000000..4ea6f06
--- /dev/null
+++ b/gnu/packages/midi.scm
@@ -0,0 +1,46 @@
+;;; GNU Guix --- Functional package management for GNU
+;;; Copyright © 2015 Sou Bunnbu <iyzsong@gmail.com>
+;;;
+;;; This file is part of GNU Guix.
+;;;
+;;; GNU Guix is free software; you can redistribute it and/or modify it
+;;; under the terms of the GNU General Public License as published by
+;;; the Free Software Foundation; either version 3 of the License, or (at
+;;; your option) any later version.
+;;;
+;;; GNU Guix is distributed in the hope that it will be useful, but
+;;; WITHOUT ANY WARRANTY; without even the implied warranty of
+;;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+;;; GNU General Public License for more details.
+;;;
+;;; You should have received a copy of the GNU General Public License
+;;; along with GNU Guix.  If not, see <http://www.gnu.org/licenses/>.
+
+(define-module (gnu packages midi)
+  #:use-module (guix licenses)
+  #:use-module (guix packages)
+  #:use-module (guix download)
+  #:use-module (guix build-system cmake)
+  #:use-module (gnu packages linux))
+
+(define-public wildmidi
+  (package
+    (name "wildmidi")
+    (version "0.3.8")
+    (source (origin
+              (method url-fetch)
+              (uri (string-append "https://github.com/Mindwerks/wildmidi/"
+                                  "archive/" name "-" version ".tar.gz"))
+              (sha256
+               (base32
+                "1z324wkmkf0lapfammviiyclhc7i8in2x2gvgc2r6sq69lcwbn7g"))))
+    (build-system cmake-build-system)
+    (arguments '(#:tests? #f)) ; no tests
+    (inputs `(("alsa-lib" ,alsa-lib)))
+    (home-page "http://www.mindwerks.net/projects/wildmidi/")
+    (synopsis "MIDI Synthesizer")
+    (description
+     "WildMIDI is a simple software midi player which has a core software
+synthesizer (softsynth) library that can be use with other applications.")
+    ;; The player is under GPLv3+, the library is under LGPLv3+.
+    (license (list lgpl3+ gpl3+))))
-- 
2.1.2

Re: [PATCH] gnu: Add wildmidi.

[Mark H Weaver]

宋文武 <iyzsong@gmail.com> writes:
> * gnu/packages/midi.scm: New file.
> * gnu-system.am (GNU_SYSTEM_MODULES): Add it.

The package looks good to me, with two caveats:

* It might be better to put this in audio.scm for now.
  What do you think?

* You mentioned in another thread (subject "Midi") that you hadn't
  tested it, and then Andreas reported that it didn't work.  We should
  get it working before adding it.

     Thanks!
       Mark

Re: [PATCH] gnu: Add wildmidi.

[Ricardo Wurmus]

Mark H Weaver writes:

> * You mentioned in another thread (subject "Midi") that you hadn't
>   tested it, and then Andreas reported that it didn't work.  We should
>   get it working before adding it.

It doesn't work out of the box because (just like timidity++) it needs
to be passed a configuration file that specifies what soundfont to use.
We have not yet packaged a soundfont that covers general MIDI
instruments.

Arguably, it *might* work but it comes without a sane configuration.
The question is whether we should add a particular soundfont as an
input and pre-configure wildmidi/timidity to use it by default, or if we
should leave this decision up to the user.

~~ Ricardo

Re: [PATCH] gnu: Add wildmidi.

[Andreas Enge]

On Tue, Feb 17, 2015 at 11:11:39PM +0100, Ricardo Wurmus wrote:
> Arguably, it *might* work but it comes without a sane configuration.
> The question is whether we should add a particular soundfont as an
> input and pre-configure wildmidi/timidity to use it by default, or if we
> should leave this decision up to the user.

I think we should do the former. Something that works out of the box would
be nice for the casual user. Also, after building, one cannot modify the
configuration files of wildmidi or timidity. So we would need the soundfont
first, use it as an input to the midi synthesiser and put an absolute path
into the configuration file. If you are not in a hurry, I could package
freepats over the weekend.

Andreas