Can we file an issue on this please.
On Saturday 18 January 2014 23:39:34 Tobiasz Karoń wrote:
> If I use the plugin SC4 in Ardour, beside some control sliders I have a few
> meters that show me for example momenral input signal level and gain
> reduction. Thus is very helpful.
> However in LMMS t
I would put a mouse over with the full name so if you mouse over abs value it
shows absolute value.
Do we honestly expect everyone to remember the abbreviations?
On Sunday 19 January 2014 03:54:34 Vesa wrote:
> On 01/19/2014 02:32 AM, Johannes Lorenz wrote:
> >>> What does "Abs value" mean?
> >>
Dont know about the current SF website, but if we code something from scratch
we can embed them on the site very easily with html5 :D
On Sunday 19 January 2014 08:41:17 Gurjot Singh wrote:
> On 19 January 2014 04:16, Tobiasz Karoń wrote:
> > I think we could make an official YouTube channel fo
On 19 January 2014 04:16, Tobiasz Karoń wrote:
> I think we could make an official YouTube channel for LMMS (unless it
> already exists) to share the great news about LMMS development using a vlog.
> If done regularly it could attract a lot of users and make them more aware
> what is up.
> What ar
On 01/19/2014 02:32 AM, Johannes Lorenz wrote:
>>> What does "Abs value" mean?
>> That is short for the mathematical term absolute value.
> Okay, I think if you decide to put the checkboxes on top of each other, you
> could write that out. Also, I am not sure if the wheels names should all have
>
> > What does "Abs value" mean?
>
> That is short for the mathematical term absolute value.
Okay, I think if you decide to put the checkboxes on top of each other, you
could write that out. Also, I am not sure if the wheels names should all have
four letters? This would look more unique. What do
I think that should be also possible with Travis as it's completely
scriptable. It may even be possible to automatically deploy builds, but
I'll have to investigate this further.
Am 19.01.2014 01:07 schrieb "Jonathan Aquilina" :
> One perk though of having our own hosted build bots and other self
> FYI, I had to revert the commit for the time being
first of all, sorry for the confusion, I did not notice any bug when I tested
it. I'll try to find out on Monday and make more tests.
@Toby: For the loop speedup: I can do this, ofc.
IIRC someone asked why using a multiplicator instead of just
Agreed, also can use it for tutorials about particular features, new
incoming features etc.
On Sat, Jan 18, 2014 at 11:46 PM, Tobiasz Karoń wrote:
> I think we could make an official YouTube channel for LMMS (unless it
> already exists) to share the great news about LMMS development using a
> v
One perk though of having our own hosted build bots and other self hosted
stuff is that we can then have for instance the build bots send out emails
to those committers who submitted something which was merged and say hey
what you did broke the build can you please revisit and fix it.
On Sun, Jan
I could Lukas but again its up to @TOBY or @PGIB
On Sun, Jan 19, 2014 at 1:03 AM, Lukas W. wrote:
> I'd love to do it. But as soon as I understood id, this requires me to
> have admin rights on the repository.
> So if that's ok for you (cause I would completely understand if it's
> not), could
I think this workflow works well.
On 15 Jan 2014 22:17, "Paul Giblock" wrote:
> Agreed, I'd rather discussion stay on the mailing lists. If someone has a
> bug: sure, report it straight to the tracker. But, regarding developer
> discussion, issues shouldn't be created until the discussion has le
I'd love to do it. But as soon as I understood id, this requires me to
have admin rights on the repository.
So if that's ok for you (cause I would completely understand if it's
not), could someone who is an admin grant me those rights on GitHub?
2014/1/19 Jonathan Aquilina :
> Lukas go ahead and d
Lukas go ahead and do it. It is better to have continuous integration
seeing as we have no unit tests in place to catch any problems early.
On Sat, Jan 18, 2014 at 11:42 PM, Tobiasz Karoń wrote:
> I would really love it, as I'd be able to test the new features
> immediately without compiling LM
With right edge drag + Ctrl it is possible to have a single pattern track
clip 1.5 or 8 bars long. But one can't shrink the clip making it shorter
than one bar (muting a few last notes of the pattern), which is strange and
makes the life of a beatmaker a bit harder.
Another thing is that the funct
I see. But the basic functions of a Lv2 synth would work?
Per-note bends/pitch - I wish ZynAddSubFX could do it too...
On 19 Jan 2014 00:26, "Vesa" wrote:
> On 01/19/2014 01:05 AM, Tobiasz Karoń wrote:
> >
> > Does this mean that we could... say... use TripleOscilator with Ardour?
> >
>
> Ardour
This makes me want to hurry up with the knobs ;)
I never knew, how and why software is versioned in a way it is. I guessed
one must have a roadmap that shows what the program needs to reach to
become version 1.0, 1.5 etc. Does LMMS have one?
This new versioning could be explained in a video...
I
On 01/19/2014 01:05 AM, Tobiasz Karoń wrote:
>
> Does this mean that we could... say... use TripleOscilator with Ardour?
>
Ardour uses MIDI for all instruments, so you couldn't do things that
tripleosc currently supports, like per-note pitch bends, per-note
panning...
---
Does this mean that we could... say... use TripleOscilator with Ardour?
On 18 Jan 2014 16:27, "Tobias Doerffel" wrote:
> Sure we can but I'm thinking about Paul's proposal to convert all our
> existing plugins to LV2.
>
>
>
>
> -
I think we could make an official YouTube channel for LMMS (unless it
already exists) to share the great news about LMMS development using a
vlog. If done regularly it could attract a lot of users and make them more
aware what is up.
What are your thoughts?
-
I would really love it, as I'd be able to test the new features immediately
without compiling LMMS on my own.
On 18 Jan 2014 23:16, "Lukas W." wrote:
> As I mentioned in the "Nightbuilds" thread, I would like to suggest
> using a continuous integration service such as
> https://www.travis-ci.org.
If I use the plugin SC4 in Ardour, beside some control sliders I have a few
meters that show me for example momenral input signal level and gain
reduction. Thus is very helpful.
However in LMMS this feedback information provided by plugins is ignored
and not exposed to the user. Can we fix that?
--
As I mentioned in the "Nightbuilds" thread, I would like to suggest
using a continuous integration service such as
https://www.travis-ci.org.
Their service is free for open source projects and is particularly
made to integrate with GitHub. Using it, no own hardware is required.
A build gets trigge
I guess it would be better to make it a separate window accesible from the
Help menu.
On 18 Jan 2014 04:42, "Israel" wrote:
> Instead of Tip of the Day, how about the background be made to have ALL
> (or most) of the keyboard shortcuts. The user could keep the background
> with all the handy in
Also something like a changed window title or a watermarked background
could be used to denote the automatically built versions. Or a changed
splash window graphic saying: "This is not a stable LMMS release, but a
nightbuild. Some features might be broken.".
Anyway - would anyone who intentionally
Fabulous!
On 18 Jan 2014 19:14, "Tobias Doerffel" wrote:
> 2014/1/17 Tobiasz Karoń
>
>> I mean duplicating a stereo signal so it can be fed to more than one
>> mixer channels simultaneously.
>>
>
> So that's what we have in the new FX mixer :-)
>
>
---
It was forked from sourceforge. The migration to GitHub is very recent.
The most recent commit was 4 months ago. Toby already looked at it and
said it didn't have anything to add to the current development.
On 01/18/2014 11:22 AM, Jonathan Aquilina wrote:
You sure its not just a fork of the
2014/1/17 Tobiasz Karoń
> I mean duplicating a stereo signal so it can be fed to more than one mixer
> channels simultaneously.
>
So that's what we have in the new FX mixer :-)
--
CenturyLink Cloud: The Leader in Enterpr
You sure its not just a fork of the main repo? I wonder how one could tell
if its not a fork.
On Sat, Jan 18, 2014 at 2:29 PM, Israel wrote:
> https://github.com/ranft/lmms
> This might have some improvements worth looking at...
> Just something I came across..
>
> --
> Regards
>
>
>
>
LV2 can probably be made to support that by writing an extension -- if one
doesn't exist already.
2014/1/18 Vesa
> On 01/18/2014 05:26 PM, Tobias Doerffel wrote:
> > Sure we can but I'm thinking about Paul's proposal to convert all our
> > existing plugins to LV2.
>
> Hmm. Would it break any ex
On 01/18/2014 05:26 PM, Tobias Doerffel wrote:
> Sure we can but I'm thinking about Paul's proposal to convert all our
> existing plugins to LV2.
Hmm. Would it break any existing functionality? Does LV2 support eg.
per-note pitch bends? I know MIDI doesn't support those, and if LV2 is
(like VST) b
On 01/18/2014 05:16 PM, Tobias Doerffel wrote:
> Hi,
>
> next time please just merge the stable-0.4 branch because if doing
> lots of changes manually in different branches it can become
> complicated when merging back to stable-0.4 later (Git possibly can't
> recognize common commits)
>
> Toby
Ye
Sure we can but I'm thinking about Paul's proposal to convert all our
existing plugins to LV2.
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Crit
Hi,
next time please just merge the stable-0.4 branch because if doing lots of
changes manually in different branches it can become complicated when
merging back to stable-0.4 later (Git possibly can't recognize common
commits)
Toby
Done.
I didn't do it before because this bug had already been reported on the
old bug tracker:
https://sourceforge.net/p/lmms/bugs/520/
Il 18/01/2014 15:49, Gurjot Singh ha scritto:
> On 18 January 2014 20:13, giakk...@hotmail.it wrote:
>> The tracks behavior is good enough, so I'd love it on F
On 18 January 2014 20:13, giakk...@hotmail.it wrote:
> The tracks behavior is good enough, so I'd love it on FX channels too!
>
> The only issue with them is this:
> - Open a project with multiple tracks
> - "solo" one of them
> - save the project
> - restart lmms
> - open the project
> You get th
The tracks behavior is good enough, so I'd love it on FX channels too!
The only issue with them is this:
- Open a project with multiple tracks
- "solo" one of them
- save the project
- restart lmms
- open the project
You get the soloed track with the green led only, so to un-mute all the
other tra
On 01/18/2014 03:20 PM, Tobias Doerffel wrote:
> Hi Johannes,
>
> FYI, I had to revert the commit for the time being - reasons explained
> here:
I also reverted it in the UI branch to keep things from getting messy.
--
Ce
On 01/18/2014 01:44 PM, Tobias Doerffel wrote:
> Hi Paul,
>
> just had the time to read your docs regarding Unison design and I
> really like it. As an abstract description it's very similiar to how
> LMMS is supposed to work in the future (especially the resources
> section). I don't know whether
Hi,
I'm currently working on adding the feature of Solo buttons to the
FXMixer Channels.
I'd like to ask you all how this should be implemented?
Do we want it to behave just like tracks? In the case of tracks, when
we solo one track all other tracks are muted.
Or do we want it behave independent
Maybe the major releases could have a 'code name'
say version 14.0.0 could be "Blaster Boombox" or whatever
and version 15.0.0 could be "Clever Cacophony"
all the 14.X.X would simply retain the 'code name' until version 15.
This might make it simpler for users to identify what base version they
a
Quoting Tobiasz Karon :
> I wonder if we could have the latest code from Git built automatically
> every day (night).
>
> I can't even count today's pulled branches.
>
> I don't know much about such routines, so don't hesitate to tell me if I'm
> entirely wrong about this.
In the name of user-fri
Addition: a good test case is the demo song at
data/projects/Demos/Shovon-ProgressiveHousePluckDemo.mmpz
Render it to WAV files with and without patch and take a look at the
differences in Audacity. In the end, there shouldn't be any differences :-)
Toby
-
This is an external upload made several months ago and from what I can see
it only includes the note labels feature which has been merged already.
Anyways thanks for the hint!
Toby
--
CenturyLink Cloud: The Leader in Enter
IMHO this would make people overestimate the meaning of individual releases
(and also increases effort for each release a bit) because if we're going
to followthe "release early, release often" principle in the future we will
be through very quickly. Release names are fine for distributions/operati
https://github.com/ranft/lmms
This might have some improvements worth looking at...
Just something I came across..
--
Regards
--
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are
Hi,
one more note on the part where values are summed up. For better
performance and better code readability please make two loop variants: one
if absolute values are activated and one the way it always has been.
Toby
--
I could setup something to build automatically on launchpad, but I will
have to look into how to pull code from GitHub every night. You can
create a recipe from a branch, and simply set it to auto build and it
will automatically build it for all the architectures. I have never
built anything
Hi Johannes,
FYI, I had to revert the commit for the time being - reasons explained here:
https://github.com/LMMS/lmms/commit/9cb52ccf0d84b31945b86cbf419db854c0d91204
can you please take a look at it so maybe we get things fixed until the
next release?
Thanks! :-)
Toby
Hi Toby, how about using a "nickname" scheme similar to Ubuntu...
for example "2.10 Ubuntu 9.04 (Jaunty Jackalope)2.11 Ubuntu 9.10 (Karmic
Koala)2.12 Ubuntu 10.04 LTS (Lucid Lynx)2.13 Ubuntu 10.10 (Maverick
Meerkat)2.14 Ubuntu 11.04 (Natty Narwhal)2.15 Ubuntu 11.10 (Oneiric Ocelot)
where the rel
Hi,
2014/1/16 Tres Finocchiaro
> Coming from the windows side of composition, the VST performance on
> playback is something that suffers currently.
>
Has this been an issue since a specific version? Generally the current
approach (launching the VST plugin in a separate process) is very portab
Hi Paul,
just had the time to read your docs regarding Unison design and I really
like it. As an abstract description it's very similiar to how LMMS is
supposed to work in the future (especially the resources section). I don't
know whether to agree or disagree about the migration to LV2 as I don't
On 01/18/2014 01:24 PM, Tobias Doerffel wrote:
> Hi,
>
> I'd like to plan the next releases and also propose to change the
> versioning scheme:
>
> YY.QQ.RR
>
> YY=year
> QQ=quarter (start counting at 0)
> RR=release (start counting at 0)
I like the idea otherwise, except that I despise the bloate
On 18 January 2014 16:54, Tobias Doerffel wrote:
> Hi,
>
> I'd like to plan the next releases and also propose to change the versioning
> scheme:
>
> YY.QQ.RR
>
> YY=year
> QQ=quarter (start counting at 0)
> RR=release (start counting at 0)
>
> so if we manage to push out a release in January (whi
Hi,
I'd like to plan the next releases and also propose to change the
versioning scheme:
YY.QQ.RR
YY=year
QQ=quarter (start counting at 0)
RR=release (start counting at 0)
so if we manage to push out a release in January (which is my goal) it
would be 14.0.0. I know this would be a confusing ju
The point is that with a service like the two I have mentioned, we
don't need our own hardware. It completely runs on their servers.
And with the latter, pull requests on GitHub are tested automatically
*before* they get merged into the official repo.
2014/1/18 Jonathan Aquilina :
> Lukas I have a
vesa I think the migration to unison should be started on. It is going to
take a lot of work for Paul to migrate it so we will have time to work on
new releases while he works on the migration to the new core.
On Thu, Jan 16, 2014 at 8:40 AM, Vesa wrote:
> On 01/16/2014 09:22 AM, Johannes Loren
Seeing as you have a road map in mind. can you fill n that page on the
github dev wiki please. Currently that is blank and I think it would be
great to have filled up with the release cycle etc.
On Sun, Jan 12, 2014 at 3:19 PM, Tobias Doerffel
wrote:
> I fully agree. We should wait at least for
Lukas I have a solution on continuous integration testing but again
requires our own hardware.
Libreoffice use build bots http://trac.buildbot.net so as soon as anything
changes in the repo it then pulls the changes and initiates a compile.
If people are willing to run these bots for now on their
Just an idea I'd like to throw in:
Apart from nightly builds, we could also use a continuous integration
service to automatically test new code and see if it builds.
For example, those two offer this service for free for open source projects:
https://travis-ci.org/
https://drone.io/
E.g. the tagli
Reason I suggested our own hardware is i know what libreoffice use and it
would require some dedicated hardware.
On Sat, Jan 18, 2014 at 9:15 AM, Tobias Doerffel
wrote:
> I don't think that we need a dedicated server for it. Launchpad offers all
> we need (and even windows builds could be built
I don't think that we need a dedicated server for it. Launchpad offers all
we need (and even windows builds could be built there via cross compiling
(the way we build it for normal releases too)) - just need an automatism to
trigger the update-and-build process. Does anyone have experience on this?
2014/1/16 Jonathan Aquilina
> Sirmacik we would love to take advantage of your hosting offer, but I have
> a question what kind of guarantee can you give in terms of uptime? The main
> fear of project owner is that of down time.
>
Not about down time (even though that is important as well) but l
63 matches
Mail list logo
