Re: [LMMS-devel] A suggestion for the demo tune

Hey guys! I release all my music under CC0, so no problem there. I can convert soundfonts to flacs, sure. I will try to do that and see what the result will be. Will keep you posted on that. "On an semi-related note, we just had a top songs competition for LMMS. Would you be interested in enter

Re: [LMMS-devel] A suggestion for the demo tune

On 03/30/2014 10:59 PM, Louigi Verona wrote: > Hello fellas! > > About 3 years ago I've written several tunes with LMMS that over the > years have gotten very favorable reviews from people. And I thought > that maybe these tunes can be candidates for including them in LMMS > demo set. Well, I'm no

Re: [LMMS-devel] A suggestion for the demo tune

This is a very generous offer and this music is great! You are a very talented musician! To properly distribute either track "TributeToScooter" or "TheTribe" with the next version of our LMMS software would require quite a few considerations... 1. We would ask that the MMPZ is tested with versi

Re: [LMMS-devel] Just a thought

On 03/30/2014 10:40 PM, David Gerard wrote: > > This reminds me of GNU Hello, a "hello world" application that is > fully instrumented with all the faff a proper GNU project should have. > > https://www.gnu.org/software/hello/ > > Yes, a version of "hello world!" that got to version 2.9 ... > > Ye

[LMMS-devel] A suggestion for the demo tune

Hello fellas! About 3 years ago I've written several tunes with LMMS that over the years have gotten very favorable reviews from people. And I thought that maybe these tunes can be candidates for including them in LMMS demo set. Here are the projects with samples in question: http://www.louigiver

Re: [LMMS-devel] Master Branch won't compile

Which wiki? I'm talking about the github one as that's where our compilation instructions reside now. Here's a bug I opened, which has the userid in it: https://github.com/LMMS/lmms/issues/509 -- _

Re: [LMMS-devel] Just a thought

On 30 March 2014 20:04, Vesa wrote: > A reference implementation might make sense though? > A simple instrument which doesn't do much - produces a sinewave, maybe? > - which would be extensively commented, and would get shipped with LMMS > but not built by default... > If this sounds like a good

Re: [LMMS-devel] Just a thought

On 03/30/2014 08:26 PM, Tobias Doerffel wrote: > An SDK usually only makes sense for proprietary platforms (where the > whole source code is not available) or large and complex systems. > However for LMMS all you have to do is to clone the repository, copy a > simple instrument, add it to plugins/C

Re: [LMMS-devel] ENV/LFO idea...

On 03/30/2014 08:33 PM, Tobias Doerffel wrote: > Hi, > > sounds like an innovative concept - and maybe ambitious at the same > time when it comes to achieving 100% backward compatibility. > Nevertheless this should be nothing we could not manage. > > More thoughts: > - the note effects should show

Re: [LMMS-devel] Mailing list broken? [Test]

Yes you have to subscribe - otherwise we would be bombed by spam and/or a moderator had to check moderator requests at least once a day. The current solution is pragmatic and has been working well for years :-) Regarding the specific issue: mail address correct? no big attachments? Toby

Re: [LMMS-devel] ENV/LFO idea...

Hi, sounds like an innovative concept - and maybe ambitious at the same time when it comes to achieving 100% backward compatibility. Nevertheless this should be nothing we could not manage. More thoughts: - the note effects should show all controls and UI elements inline i.e. no "control" button

Re: [LMMS-devel] Just a thought

An SDK usually only makes sense for proprietary platforms (where the whole source code is not available) or large and complex systems. However for LMMS all you have to do is to clone the repository, copy a simple instrument, add it to plugins/CMakeLists.txt and change everything according to your n

Re: [LMMS-devel] Master Branch won't compile

You need to install "fluid" which is related to FLTK. We no longer ship generated files but generate them cleanly upon build as it is intended by upstream ZASF. I agree that we have to update the Wiki @tres: what is your wiki name? I tried "tres" and "tresf" and both of them could not be found. T

Re: [LMMS-devel] Wiki: Submitting-a-patch

I thought all new features go to master On 30 Mar 2014 15:43, "Lukas W." wrote: > Yeah that's what I thought as well. Just wanted to be sure. > > 2014-03-30 15:37 GMT+02:00 Vesa : > > On 03/30/2014 03:36 PM, Lukas W. wrote: > >> Hi, > >> > >> Thanks for pointing this out, it still needs to be upd

Re: [LMMS-devel] Master Branch won't compile

On 30 March 2014 16:31, Lukas W. wrote: >> We need a buildbot :-) > We have: https://travis-ci.org/LMMS/lmms Yes, I thought we did! The problem appears solved by doing a fresh code pull, and only those of us updating an old copy of the tree through the push appear to have a problem. Thankful

Re: [LMMS-devel] Master Branch won't compile

> We need a buildbot :-) We have: https://travis-ci.org/LMMS/lmms 2014-03-30 17:27 GMT+02:00 David Gerard : > Better error now! > > make[2]: *** No rule to make target `/usr/bin/fluid', needed by > `plugins/zynaddsubfx/zynaddsubfx/src/UI/VirKeyboard.h'. Stop. > make[1]: *** > [plugins/zynaddsubfx

Re: [LMMS-devel] Master Branch won't compile

Better error now! make[2]: *** No rule to make target `/usr/bin/fluid', needed by `plugins/zynaddsubfx/zynaddsubfx/src/UI/VirKeyboard.h'. Stop. make[1]: *** [plugins/zynaddsubfx/zynaddsubfx/src/UI/CMakeFiles/zynaddsubfx_gui.dir/all] Error 2 make: *** [all] Error 2 We need a buildbot :-) - d.

Re: [LMMS-devel] Master Branch won't compile

> Please put it in the wiki. I would, but despite multiple requests, I don't > have access... ;) Done. I can't give you write access to the wiki, as I'm no admin. 2014-03-30 16:56 GMT+02:00 Tres Finocchiaro : > Please put it in the wiki. I would, but despite multiple requests, I don't > have acc

Re: [LMMS-devel] Master Branch won't compile

Please put it in the wiki. I would, but despite multiple requests, I don't have access... ;) >From my experience, the cmake hints that echo to the screen are particularly useful in situations like this too (i. e delete cache etc). --

Re: [LMMS-devel] Master Branch won't compile

On 30 March 2014 15:22, David Gerard wrote: > On 30 March 2014 09:13, Lukas W. wrote: >> ZynAddSubFx is now included using a git submodule. And what you are >> experiencing is one of the main reasons against using submodules. >> Sadly, any good advice has been broadly ignored, and now we have it

Re: [LMMS-devel] Master Branch won't compile

Have these steps been added to the wiki? :) -- ___ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel

Re: [LMMS-devel] Master Branch won't compile

On 30 March 2014 09:13, Lukas W. wrote: > ZynAddSubFx is now included using a git submodule. And what you are > experiencing is one of the main reasons against using submodules. > Sadly, any good advice has been broadly ignored, and now we have it, > breaking for example dobey's daily builds from

Re: [LMMS-devel] Master Branch won't compile

> Besides this there's nothing stopping us from adding the git submodules > commands to the global CMakeLists.txt so it get executed automatically. Not a bad idea, but this would imply connecting to the internet during building, which should be avoided. (Has already been discussed in the first lin

Re: [LMMS-devel] Wiki: Submitting-a-patch

Yeah that's what I thought as well. Just wanted to be sure. 2014-03-30 15:37 GMT+02:00 Vesa : > On 03/30/2014 03:36 PM, Lukas W. wrote: >> Hi, >> >> Thanks for pointing this out, it still needs to be updated. >> Before I correct this, I'm still unsure what the planned workflow is: >> Should devs b

Re: [LMMS-devel] Wiki: Submitting-a-patch

On 03/30/2014 03:36 PM, Lukas W. wrote: > Hi, > > Thanks for pointing this out, it still needs to be updated. > Before I correct this, I'm still unsure what the planned workflow is: > Should devs base the work on the unstable master branch or the > stable-1.0 branch (for bug fixes)? > I think we'r

Re: [LMMS-devel] Just a thought

On 03/30/2014 03:33 PM, Jonathan Aquilina wrote: > Hey guys I am wondering, after readying Toby's response to issue #537. > Do we have an SDK in place for > > 1) creating synths etc native to lmms > 2) porting synths easily to LMMS, like a base GUI that then is adapted > according to the synth that

Re: [LMMS-devel] Mailing list broken? [Test]

On 03/30/2014 03:27 PM, Lukas W. wrote: > This mail is partly for testing purposes. > > Louigi on IRC reported that he's not able to post to the mailing list, > that's why I try it myself with this mail. > He gets this message: "You are not allowed to post to this mailing > list, and your message h

[LMMS-devel] ENV/LFO idea...

I suddenly had an idea. The basic idea comes in two parts: 1. Introduce a new type of native plugin: note effect. These are effects which work the same as effect plugins, but they get applied for the note-specific audiostreams. Of course this means they only function on non-MIDI-based, native mul

Re: [LMMS-devel] Wiki: Submitting-a-patch

Lukas it depends on the issue. if they are working on enhancements and new features the master branch is used. if its a bug fix for 1.0 then the stable branch should be used. On Sun, Mar 30, 2014 at 2:36 PM, Lukas W. wrote: > Hi, > > Thanks for pointing this out, it still needs to be updated. >

Re: [LMMS-devel] Mailing list broken? [Test]

Well the correct one ;) 2014-03-30 14:35 GMT+02:00 Jonathan Aquilina : > What email address is he using to send to the list? > > The developer one is LMMS-devel > > > On Sun, Mar 30, 2014 at 2:32 PM, Lukas W. wrote: >> >> He is, and even if he was not he should be able to post, should he not? >>

Re: [LMMS-devel] Wiki: Submitting-a-patch

Hi, Thanks for pointing this out, it still needs to be updated. Before I correct this, I'm still unsure what the planned workflow is: Should devs base the work on the unstable master branch or the stable-1.0 branch (for bug fixes)? 2014-03-30 14:28 GMT+02:00 midi-pascal : > Hi, > > I just noticed

Re: [LMMS-devel] Mailing list broken? [Test]

What email address is he using to send to the list? The developer one is LMMS-devel On Sun, Mar 30, 2014 at 2:32 PM, Lukas W. wrote: > He is, and even if he was not he should be able to post, should he not? > > 2014-03-30 14:29 GMT+02:00 Jonathan Aquilina : > > That sounds like he isnt subscr

[LMMS-devel] Just a thought

Hey guys I am wondering, after readying Toby's response to issue #537. Do we have an SDK in place for 1) creating synths etc native to lmms 2) porting synths easily to LMMS, like a base GUI that then is adapted according to the synth that one would like to add. These are just some thoughts at thi

Re: [LMMS-devel] Mailing list broken? [Test]

He is, and even if he was not he should be able to post, should he not? 2014-03-30 14:29 GMT+02:00 Jonathan Aquilina : > That sounds like he isnt subscribed to the list. > > > On Sun, Mar 30, 2014 at 2:27 PM, Lukas W. wrote: >> >> This mail is partly for testing purposes. >> >> Louigi on IRC repo

Re: [LMMS-devel] Mailing list broken? [Test]

That sounds like he isnt subscribed to the list. On Sun, Mar 30, 2014 at 2:27 PM, Lukas W. wrote: > This mail is partly for testing purposes. > > Louigi on IRC reported that he's not able to post to the mailing list, > that's why I try it myself with this mail. > He gets this message: "You are

[LMMS-devel] Wiki: Submitting-a-patch

Hi, I just noticed in the Wiki page "Submitting-a-patch": 4. Pull in upstream changes $git fetch upstream# Fetches new changes without modifying your files $git rebase upstream/stable-0.4 Ithink it sould now state: $git rebase upstream/stable-1.0 I thought doing the change myself

[LMMS-devel] Mailing list broken? [Test]

This mail is partly for testing purposes. Louigi on IRC reported that he's not able to post to the mailing list, that's why I try it myself with this mail. He gets this message: "You are not allowed to post to this mailing list, and your message has been automatically rejected" If this mail arriv

Re: [LMMS-devel] How do you manage bugs?

@toby they would need to still file the pull request against the right branch though. On Sun, Mar 30, 2014 at 10:47 AM, Tobias Doerffel wrote: > 2014-03-30 10:00 GMT+02:00 Jonathan Aquilina : > > Yes its really up to you what you want to work on :) Key thing to > remember > > we have gone into

Re: [LMMS-devel] How do you manage bugs?

2014-03-30 10:00 GMT+02:00 Jonathan Aquilina : > Yes its really up to you what you want to work on :) Key thing to remember > we have gone into a two branch version control. Currently there is the > master branch which is all new features etc. and the 1.0 is for bug fixes > and further stabilzation

Re: [LMMS-devel] So...

Ok, sounds good :-) -- ___ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel

Re: [LMMS-devel] So...

The LSP2 rewrite is coming along slowly but surly. I am working on my own fork of the branch On Sun, Mar 30, 2014 at 10:30 AM, Tobias Doerffel wrote: > And why the hell do we not keep the current approach and simply > include the plugins which get installed either ways? Again, as long as > the

Re: [LMMS-devel] Master Branch won't compile

I think the submodules command should be added to the CMakeLists.txt file to make it easier for those wishing to compile lmms and not well versed in how git works. I admit those submodule commands this project is the first time im seeing them used. On Sun, Mar 30, 2014 at 10:25 AM, Tobias Doerffe

Re: [LMMS-devel] So...

And why the hell do we not keep the current approach and simply include the plugins which get installed either ways? Again, as long as the plugins are regular OS-dependent binaries (which always will be the case) it adds an horrible amount of maintainance work with no benefit at all. It's a comple

Re: [LMMS-devel] Master Branch won't compile

What's the alternative if we always want to be able to easily integrate the latest upstream changes? It's been lots of work to manually apply the LMMS-specific patches to the current ZASF master branch. What we can do now is to simply merge upstream/master without losing our changes. If we have an

Re: [LMMS-devel] So...

Technically another way we could do it is provide an interface where we can download the new instruments etc from a remote server and have lmms install them behind the scenes for the user and all the user has to do is restart lmms. On Sun, Mar 30, 2014 at 10:20 AM, Tobias Doerffel wrote: > 2014

Re: [LMMS-devel] So...

2014-03-29 22:41 GMT+01:00 Vesa : > Well LADSPA is right out, as it doesn't support instruments at all Oh, it does but they're simply not supported as such in LMMS ;-) Besides this I strongly vote for keeping the current all-in-one concept - everything else helps nobody and is just pain in the as

Re: [LMMS-devel] Master Branch won't compile

ZynAddSubFx is now included using a git submodule. And what you are experiencing is one of the main reasons against using submodules. Sadly, any good advice has been broadly ignored, and now we have it, breaking for example dobey's daily builds from his PPA, and introducing a new weird step for eve

Re: [LMMS-devel] Master Branch won't compile

On 03/30/2014 04:04 AM, Jonathan Aquilina wrote: I think the biggest question to ask here at this point what OS are you trying to compile on? On Sun, Mar 30, 2014 at 9:55 AM, Popsip > wrote: I have all the dependencies installed and I can compile the stable-1.

Re: [LMMS-devel] Master Branch won't compile

Please run "git submodule init" and "git submodule update" to pull in the external ZynAddSubFX repository. Toby -- ___ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net h

Re: [LMMS-devel] Master Branch won't compile

I think the biggest question to ask here at this point what OS are you trying to compile on? On Sun, Mar 30, 2014 at 9:55 AM, Popsip wrote: > I have all the dependencies installed and I can compile the stable-1.0 > branch just fine; however, when I try to compile the master branch, I > get this

Re: [LMMS-devel] Release notes LMMS 1.0.0

I think that would be the best toby unless we can remove the link to the 0.4.15 download directory and leave it showing in SF On Sun, Mar 30, 2014 at 10:01 AM, Tobias Doerffel wrote: > +4000 downloads of 0.4.15 - it's probably still linked at many > external sites. We could try to temporarily r

Re: [LMMS-devel] Release notes LMMS 1.0.0

+4000 downloads of 0.4.15 - it's probably still linked at many external sites. We could try to temporarily rename the files so people get a 404 and download 1.0.0 instead. Toby -- _

Re: [LMMS-devel] How do you manage bugs?

Yes its really up to you what you want to work on :) Key thing to remember we have gone into a two branch version control. Currently there is the master branch which is all new features etc. and the 1.0 is for bug fixes and further stabilzation On Sun, Mar 30, 2014 at 12:48 AM, midi-pascal wrote:

[LMMS-devel] Master Branch won't compile

I have all the dependencies installed and I can compile the stable-1.0 branch just fine; however, when I try to compile the master branch, I get this CMake error: /Desktop/lmms-master$ cmake ./ -- The C compiler identification is GNU 4.7.3 -- The CXX compiler identification is GNU 4.7.3 -- Check