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 
what the python script has implemented for bsewave files is now also done (even 
somewhat more correctly as far as I remember) by

* https://github.com/swesterfeld/liquidsfz/blob/master/lib/hydrogenimport.cc

So as soon as Anklang has liquidsfz support, we also have most of what this bug 
report is about supported in Anklang.

What this doesn't do is
* looking for drumkits in well known folders
* downloading additional h2drumkits
* extracting h2drumkits
* displaying author and/or license infos

(which all could be done by Anklang)

It is also somewhat limited in terms of what hydrogen features are supported, 
but if we need more, we could improve the liquidsfz importer. In cases where 
there is no corresponding sfz opcode, we could invent our own private opcodes 
(i.e. liquidsfz_foo_bar=bazz for a hydrogen foo_bar=bazz feature). In these 
cases liquidsfz bugs could be filed.

Finally one problem here is that we don't split each drum into its own stereo 
bus. So you cannot for instance place a reverb on the base drum, but a 
different effect on the snare, as you only get a mixdown from liquidsfz which 
contains all drums. This is ok for a start, but suboptimal, but in theory we 
can implement it by extending the importer and adding new either public or 
private API to liquidsfz to support splitting its output in more stereo 
channels. Its a somewhat advanced feature though, and we probably can ignore it 
for now.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/tim-janik/beast/pull/41#issuecomment-1200041001
You are receiving this because you are subscribed to this thread.

Message ID: <tim-janik/beast/pull/41/c1200041...@github.com>
_______________________________________________
beast mailing list
beast@gnome.org
https://mail.gnome.org/mailman/listinfo/beast

Reply via email to