Hi muzzol,
first of all, welcome to this list!
Am 25.04.2020 19:37, schrieb muzzol:
1- Integrate patterns correctly with Hydrogen as a downloadable repo
or directly with the package. Maybe starting next version a basic set
(the one in github) could be integrated in the package or suggest
distro packagers to create an additional package (hydrogen-patterns)
The repo is already there (the one which also includes all our
drumkits),
it just needs to be synced with the github pattern repo (the feed is
located
at http://www.hydrogen-music.org/feeds/drumkit_list.php). We did that
before
with a simple script, but this has not been migrated since we have moved
with our website to github pages. So currently this feed is completely
static,
the source is also at github:
https://github.com/hydrogen-music/hydrogen-music/tree/master/feeds.
I think most of the puzzle parts are there, they just need to put again
together, maybe via
a github action? I haven't looked into those automation things at github
yet. The only
open question would be the hosting of the patterns, i'm not sure if the
patterns can be
downloaded directly from github via permalinks.
The patterns could also be distributed by additional packages, but then
this list
seems to be the wrong place for discussion, since we do not supply those
packages.
Apart from that, everyone can already setup an own server. Users which
want to use
that server can just add the URL to the server list and use it.
2- Improve pattern workflow. Clicking on a pattern should give the
option to listen to it even if not loaded so you can see if it fits
your needs. Also double clicking should load the pattern and focus on
it. Pattern library could be near pattern list instead of the opposite
corner with a quick show/hide button so you can load them quickly.
The pattern preview feature is a nice idea! I would support that. But
the
implementation is not trivial, but also not impossible.
3- Patterns should be kit agnostics. Sometimes I discard a pattern
because it sound bad and later I found is because it was created with
another kit so elements get mixed. This shouldn't happen. Also it
would be great to be able to import midi directly. I know this have
been discussed in the past and maybe is a good time to start.
Yes, this has been discussed in the past. But without any result. Do
you have any good idea how to implement this? We discussed a tag-based
system, but this was years ago and nobody had since an interest in
implementing
this.
4- Autoload patterns on new song. When you create a song ask if you
want an empty pattern or if you want to start with some genre specific
pattern: rock, blues, samba...
I'm not sure if thats a thing every Hydrogen user would find useful. If
people really need that, they could prepare some example songs which
include
those patterns and use that as start points for new songs. That would be
much more powerful, at least in my opinion.
5- More patterns! We need tons of patterns here. Maybe we could show
some hint to encourage people to share their patterns. Maybe some
anual contest with actual prizes. Also, could be great to be able to
upload patterns to a public repo directly from the app.
Sure! Thijz has organised such a contest for drumkits years ago, which
was
a nice thing in my opinion. But as i remember, it was quite
time-intensive
to carry out the contest, organize the prizes and send everything out.
Overall, I think we need to improve that area and even make it more
prominent with the final goal of having a nice song with just some
clicks. Take this video is a lousy inspiration
(https://www.youtube.com/watch?v=YEJH3WM6Oz8)
I can offer some help. My background comes from linux administration
but I've participated in some projects and I can offer a server to
host a free repo and I can do some other work on the server side. I'm
not a developer but I can do some bash magic
(https://gist.github.com/muzzol/5f5d27c155d6113069445c7d3b6910f2) and
mantain domains and services.
Great, every help is welcome!
I understant that this could be a lot of work so as Olivier suggested,
this could be divided in several FR so we can start working on some
things while pausing some others.
You could create single feature request tickets on Github for things
which
have to implemented in Hydrogen (like the pattern preview). This enables
other
people to chime in and add their feedback, as well to get the attraction
of developers
who might find interest in working on that feature.
Best regards,
Sebastian
_______________________________________________
Hydrogen-devel mailing list
Hydrogen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
