Closed #41.
--
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/41#event-7092793346
You are receiving this because you are subscribed to this thread.
Message ID: ___
beast mailing list
beast@gnome.org
Great, thanks a lot for this summary!
--
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/41#issuecomment-1200044587
You are receiving this because you are subscribed to this thread.
Message ID: ___
beast
Basically, liquidsfz tries to transparently load hydrogens xml format, and
turns its xml content into .sfz opcodes. For instance if you use
```
$ liquidsfz /usr/share/hydrogen/data/drumkits/GMRockKit/drumkit.xml
```
you can use the hydrogen GMRockKit in liquidsfz. This works because a lot of
@swesterfeld is this something that can be turned into a LiquidSFZ or Anklang
bug?
I don't want the work that went into this go to waste, but I wonder what the
best way forward is with Anklang taking over from Beast...
--
Reply to this email directly or view it on GitHub:
We discussed that beast should be able to download pre-converted drumkits at
some point. Here is an example tarball, containing two drumkits (the ones that
ship with hydrogen itself).
The download URL is:
http://space.twc.de/~stefan/download/beast-drumkits-pack.tar.xz
The tarball contains:
-
