The new sample selectin features (Velocity/Round Robin/Random) is not very straight forward from the GUI to know exactly what they mean.

See:

• hydrogen-music/hydrogen#763
• hydrogen-music/hydrogen#1000

describe changed note on/off (shift)click behavior
has note length been completely removed ??

Please document copyright holders in this git repository. It is also necessary to document the license for these files to be redistributed. Next, a full-text copy of that license will most likely need to be included in the repository (depends on the license).

Finally, it would be nice to see a beta1 tag!

Kind regards,
Nicholas

Hihat pressure groups enable users using v-drums to have different instruments depending on the pressure on the hihat pedal.

The hihat groups itself is for v-drum with different trigger for the hihat (edge, rim, etc.) so that a completely different group of different instruments can be setup per hihat trigger.

The manual needs to be updated to reflect all these functionalities.

• add note about behavior of custom note lengths in the presence of tempo changes
• update image showing stop note
• review stop note parts of the doc -> maybe start Pattern Editor section with introduction of all different types of notes that can be used (regular, custom length, stop note)
• in section for custom note length -> info that Instrument Editor > Release controls the length of the fade out
• better ADSR coverage. (Release only applied on custom note lengths, maybe a figure highlighting changes in the
  sample)
• Add Changelog
• Add pictures of tutorial to shotlist -> 1.3.0
• Rework tutorial -> 1.3.0
• Update CMake setup to allow creating artifacts within build pipelines
• Add new workflow to README.md

We already have quite a number of commands/endpoints (and I intend to add even more). Right now they are just presented as a bulk with no structure at all. How about grouping them into different topics?

In addition, most of the commands require an argument of a specific type. I would suggest to put the commands into tables with the rows: command itself | expected type | short explanantion

i assume that the documentation is moving in sync with the releases of hydrogen itself.

so: would it be possible to create a tag in the documentation repository, whenever you tag a release in the main repo as well (ideally: using the same name)?

this is related to: hydrogen-music/hydrogen#926

distributions like Debian really enforce using source code of everything (obviously binaries; but also documentation if it is generated from some abstract representation like docbook) during the packaging process.
while i appreciate your efforts in creating a separate tarball in the main repository (apart from the github-autogenerated one) that also contains the documentation.
however, as @trebmuh pointed out, it lacks the sources for the documentation.

so: in order to comply with a Debian packaging rules, we (the Debian packagers) need a way to get the source of everything to build a complete package from scratch. (you might think that this is anal; but really it's just the prize we pay for creating a free (as in speech) distribution)

i think that if you created matching tags here in the documentation repository, we would be able to come up with something that pulls in the sources for all artifacts (binary and docs) while importing a new upstream release. in an automated way ;-)

currently there is no section in the manual that describes the CLI options of H2

Is there a way of changing the velocity of the green note?
I am able to change only the velocity of the red one.
A solution is to select and move the green note in a temporary different position, change velocity and then moving to the initial position, but it's a bit long.
If one could select the desired note and then change its velocity in the bottom panel...

See here on the online doc.

The one currently displayed is:

while a current screenshot is:

Note that the URL is slightly different (re the "www") and this led to an user thinking that a bug was going on (See here in French).

Now that hydrogen support multi-banks per instruments (Close, Overhead, etc) it would be good to update the manual to reflect this.

describe this function in the manual
Instrument-->Layers-->Load Layer-->Set automatic velocity

see http://hydrogen.popez.org/hcms/node/10806#comment-59683

Thanks to this DRQ hydrogen-music/hydrogen#310 and pull request hydrogen-music/hydrogen#313 Hydrogen will soon be able to export drumkit to older version of Hydrogen.

The manual will need to be updated as in the updated functionality, when a user chose to export to 0.9.6 and older, she first needs to decide what component to export.

I just realize we do not support updating translation files *.po yet. There is only the manual.pot file generated from the current manual.docbook and the README.md states this should be copied to a manual_*.po and translated afterwards. But there is no way to update the latter.

The xml2pot package provides a program called split2po with which one could write a custom script. But the gettext system is so old there are full fledged solution in the official repos for sure. I'll have a look.

Right now, http://hydrogen-music.org/doc/ lists a couple of translations of the manual that are desperately out of sync. By scrolling through them it seems none of them reaches 30% translated content.

With the reworked version of the manual this percentage will decrease drastically. So, I think we have no choice but to drop them. But we should to still point out that translations of the manuals are both supported and highly welcome.

See here:

• http://www.hydrogen-music.org/hcms/node/17152
• http://hydrogen.popez.org/hcms/node/17214
• http://hydrogen.popez.org/hcms/node/14178
• http://hydrogen.popez.org/hcms/node/12585

@mauser or @thijz : could you guys please add a "manual" tag here?

add a dedicated section about the peculiaries of the NSM support/usage.

See

• hydrogen-music/hydrogen#999

Hello,

I've finally found some time to work on the Debian package as well as to add the new documentation. What I've found is that "manual_en.html tutorial_en.html tutorial_fr.html tutorial_it.html" are new, but nothing else appears to be built from the source of this repository.

Should tutorial_*.html still be installed to /usr/share/hydrogen/data/new_tutorial ?
Should manual_en.html still be installed to /usr/share/hydrogen/data/doc ?
Should the other html files that aren't built from localised source just be ignored and/or removed at this time?

Finally, is there any reason why the clean target doesn't remove the generated html files?

Thank again!
Nicholas