Like Tres said, the repo is the place for the dicussion about these.
Link to the samples repo: https://github.com/LMMS/Samples
-Uroš|Umcaruje
On 4 October 2014 15:25, Tres Finocchiaro
wrote:
> Probably best suited for the sample pack discussions, which apparently we
> need our own repo for. :
Probably best suited for the sample pack discussions, which apparently we
need our own repo for. :)
We should already have a team working on this stuff, so perhaps open and
assign a bug report so we can track the progress of this (and also get it
into our repo so people can clone and work with it?
On 4 October 2014 09:01, Vesa wrote:
> With per-track automations, it would be as easy as just connecting the
> track and bam, all patterns connected. One more entry on the pros-list.
>From a usability standpoint, this is a no-brainer IMO...
+1
Could we have multiple independent automations p
Hey, I've recorded and partially edited an acoustic drumkit (the toms suck,
but the rest sounds fine, even great). Read the read me.txt file for
details.
I've found myself out of free time and I thought it'd be cool to maybe
include some samples in LMMS 1.1.
I hereby release this archive and all
..Guys -i wrote this.. From the debate and argumentation, i have realized,
that this will be a bad idea. Modularzation-wise, ram/cpu-wise, and
other-wise..
Please let this die now.
-the end-
--
View this message in context:
http://linux-multimedia-studio-lmms.996328.n3.nabble.com/mixer-EQ-defau
Well, I just again ran into this bug where you open a project and some
automation patterns get randomly disconnected from their models...
This time, I had 5 automation tracks, each with more than 10 patterns,
get disconnected, forcing me to connect each of those patterns again
individually...
And