From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package request: drumgizmo
Date: Fri, 14 Jun 2024 15:42:08 +0200 [thread overview]
Message-ID: <20240614134208.CB39822304@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14279@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
Closed issue by luzpaz on void-packages repository
https://github.com/void-linux/void-packages/issues/14279
Description:
Website: https://www.drumgizmo.org
git repo: http://git.drumgizmo.org/drumgizmo.git
Latest stable: 0.9.17
Changelog: https://drumgizmo.org/wiki/doku.php?id=changelog:drumgizmo-0.9.17
> DrumGizmo is an open source, multichannel, multilayered, cross-platform drum plugin and stand-alone application. It enables you to compose drums in midi and mix them with a multichannel approach. It is comparable to that of mixing a real drumkit that has been recorded with a multimic setup.
> Features include:
> Stand-alone, Lv2 and VSTi versions available
Open drumkit file format, allowing the community to create their own drumkits
Drum velocity, allowing for several different hit velocities for each drum
Multichannel output, making it possible to mix it just the way you would a real drumkit
Optional built-in humanizer, analyzing the midi notes, adjusting velocities on-the-fly
Stand-alone midi renderer, generating .wav files, 1 for each channel
Stand-alone midi input, making it possible to use DrumGizmo as a software sampler for an electronic drumkit
prev parent reply other threads:[~2024-06-14 13:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 5:35 [ISSUE] New Package: drumgizmo voidlinux-github
2019-12-29 13:52 ` Package request: drumgizmo voidlinux-github
2021-01-07 23:03 ` uzr123x
2021-07-19 11:56 ` biopsin
2021-07-19 11:57 ` biopsin
2021-07-19 17:47 ` biopsin
2022-01-13 17:15 ` timsofteng
2022-01-13 18:18 ` biopsin
2024-06-14 13:42 ` ahesford [this message]
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=20240614134208.CB39822304@inbox.vuxu.org \
--to=ahesford@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/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 NNTP newsgroup(s).