Re: [LMMS-devel] 1.2 feature definition/feature freeze

On 01/28/2015 08:35 AM, Amadeus Folego wrote: > On Wed, Jan 28, 2015 at 07:45:47AM +0200, Vesa wrote: >> As for the freeze, I think we talked of February before? Maybe a week or >> two from now? Is anyone working on any big features right now? > Well, I am not asking too much

Re: [LMMS-devel] 1.2 feature definition/feature freeze

his is because rather than a rock rolling back to > its place (Sisyphus), we're more of a snowball gaining size and > momentum. I'll let Vesa, Lukas and Dave chime in here too because > proper milestone management was more of a nice-to-have and less of a > line-in-the-san

Re: [LMMS-devel] Building package on Ubuntu (for vivid) [issue]

Should already be fixed in the stable-1.1 branch. -- New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high perfor

Re: [LMMS-devel] LSP browser inside LMMS

A reminder: before we add any online features to LMMS, we need to remember that any time something is connected online, it brings with it a whole bunch of new issues to worry about. As long as LMMS is a purely local application, we don't need to worry about such things. The moment we allow LMMS to

Re: [LMMS-devel] Blender example?

On 01/16/2015 10:27 PM, Spekular R wrote: > > @vesa I'm not sure about removing it. If we could offer it as a > separate download that'd be a good solution imo, > How is that a good solution? We'd still have to maintain the code, only now it'd be even less useful (

Re: [LMMS-devel] Blender example?

On 01/16/2015 04:05 PM, Tres Finocchiaro wrote: > 4. CC0 Pat files. (etc, etc) Oh, that takes me back... My first x86 computer had a Gravis Ultrasound, when I was a kid. That was in the 90s. It is now 2015... is GUS patch support really useful to anyone anymore? I can't imagine new ones being pro

[LMMS-devel] What happened to song editor?

Due to some recent change, you can no longer drag an instrument/preset/etc. into the toolbar of the song editor. This used to be an easy way to prevent overwriting existing instruments. We should put this functionality back. Who's tweaked the song editor window recently? -

Re: [LMMS-devel] Preparing for stable-1.2

On 01/13/2015 06:04 AM, Tres Finocchiaro wrote: > *Features:* > > * New parametric graphic EQ FX plugin > * Quick FX mixer assignment from instrument > * FX mixer "remove unused channels" feature > * Quick Piano roll/pattern switching using ALT + Lelft, Alt + Right > * Automation Pattern

Re: [LMMS-devel] Preparing for stable-1.2

On 01/13/2015 06:04 AM, Tres Finocchiaro wrote: > But looking forward, we'll soon be branching off for a stable-1.2 branch. How about we'll wait at the end of the month, then it's feature freeze time. (As before, plugins can be excused if they do not touch core code.) --

Re: [LMMS-devel] Computer Music magazine question

On 01/09/2015 07:18 PM, I'm Umcaruje wrote: > Why should I consider using a Linux-based system for music making? That really depends on your particular use case. >From a technical perspective, there really isn't any advantage in using Linux for the average user. Most people probably benefit more

[LMMS-devel] Delays...

So I already told this to Tres on GitHub, but I thought it'd be polite to inform the mailing list as well. I'm currently going through some real life issues - nothing serious, no worries, just stuff that takes a lot of my time. So I have even less time for LMMS development right now. This situatio

Re: [LMMS-devel] Paid Dev Fundraising - Pitivi Style?

On 01/07/2015 06:28 PM, Tres Finocchiaro wrote: > > > Not sure exactly how Indiegogo operates, probably we can set > some kind of upper limit on the funding. Or just tell people not > to donate anymore or something, if it comes to that... > > Or just hire the developer for a longer

Re: [LMMS-devel] Paid Dev Fundraising - Pitivi Style?

On 01/07/2015 03:21 PM, Tres Finocchiaro wrote: > > the developer can receive the funds from the campaign directly and > pays any income tax etc. on their side. > > > Sure, that covers the income taxes that get spent on a human that is > responsible for paying income taxes, but what happens

Re: [LMMS-devel] Paid Dev Fundraising - Pitivi Style?

On 01/07/2015 05:32 AM, Tres Finocchiaro wrote: > If someone wants to organize a fund raiser, please do. I actually talked about this with Harry recently and it seems that organizing the funding isn't all that complicated as we've maybe been assuming. Basically, the idea is that if we do an Indie

Re: [LMMS-devel] LMMS 1.0.1 falsely marekd 1.1.0 in KX Studio repos?

On 01/06/2015 03:35 PM, Tres Finocchiaro wrote: > @musikBear, > > Same symptom, different OS. Unfa's talking about KXStudio, which in > contrast to openSUSE, DOES have a maintainer actively part of our > project and which we do recommend most Ubuntu derivatives to install > from for the latest ver

[LMMS-devel] FYI

I've deleted all the old pages imported from the SF-Wiki from our GitHub Wiki. Those pages were completely outdated and served no purpose other than to possibly confuse new developers. These included old compile instructions (we have better, newer ones), and old roadmaps made before 1.0... On tha

Re: [LMMS-devel] LMMS 2.0 progress so far

On 01/03/2015 01:14 AM, Stian Jørgensrud wrote: > Were Pattern (Editor) also in use in other DAWs? Step sequencer is what it's usually called. "Pattern editor" I think is mostly a FL studio thing. -- Dive into the World o

Re: [LMMS-devel] Mac version uses SDL.

On 01/02/2015 05:39 PM, Tres Finocchiaro wrote: > We do use CoreAudio on Mac. Yeah, but not directly... Again, if someone wants to code a direct CoreAudio backend, I see no reason to not include it. -- Dive into the Worl

Re: [LMMS-devel] Mac version uses SDL.

On 01/02/2015 11:49 AM, Jonathan Aquilina wrote: > I am curious how come for the mac version we arent using mac own core > audio. I compiled stable 1.1 with source from the github repository > and everythign worked beautifully. On first load it prompted me which > audio back end to use be it jack p

Re: [LMMS-devel] mmp's xml syntax

We use Qt's xml parsing tools and formatting is decided by Qt. Feel free to dive in to Qt docs to find out if there's any possibility to modify the formatting. Otherwise nothing can be done. -- Dive into the World of Paral

Re: [LMMS-devel] LMMS 2.0 progress so far

On 12/31/2014 08:54 PM, Tres Finocchiaro wrote: > @Vesa, > > Should we consider either of these as part of 2.0? Eh, I don't know. Name changes are hard, we never reached any kind of consensus on any of the name change issues... personally, I'd be fine with renaming Song Edito

Re: [LMMS-devel] Shortcut changes

On 12/26/2014 01:40 AM, Stian Jørgensrud wrote: > So maybe Ctrl + > right click for the context menu throughout the software would be better? No, it wouldn't. -- Dive into the World of Parallel Programming! The Go Paralle

Re: [LMMS-devel] LMMS 2.0 progress so far

On 12/28/2014 11:03 AM, David Gerard wrote: > Is there anything that can be done to avert the future where none of > our files work any more? Certainly. Start organizing the campaign to hire a paid developer for the LMMS team. We had everything planned out for this, the only thing missing is someo

Re: [LMMS-devel] LMMS 2.0 progress so far

On 12/28/2014 11:43 AM, I'm Umcaruje wrote: > > Next, I'm going to focus on dBV-scale controls, > > > Shouldn't LMMS use dBFS for its loudness measurement? dBFS is used by > a lot of DAWs, and seems like a standard. We're not doing loudness measurement anywhere (loudness != volume), and dBFS

Re: [LMMS-devel] Looking for things to do?

On 12/26/2014 05:27 PM, Amadeus Folego wrote: > On Fri, Dec 26, 2014 at 03:39:43PM +0200, Vesa wrote: >> #1 - track muting doesn't work >> Probably caused by recent changes in NotePlayHandles and AudioPorts. I >> think this can be fixed in AudioPort, where all the NPH&#

[LMMS-devel] LMMS 2.0 progress so far

So I feel like I have to document the changes so that other developers will know what's what and can possibly also contribute at some point towards the 2.0 effort. Currently, tempo track has been implemented. The way it works is, that tempo track inherits automation track, and tempo pattern inheri

Re: [LMMS-devel] Looking for things to do?

On 12/27/2014 01:03 PM, Amadeus Folego wrote: > On Fri, Dec 26, 2014 at 03:39:43PM +0200, Vesa wrote: >> Couple of bugs in master branch which should be easy to fix. I'd fix >> them myself, but I thought this would be a good opportunity for our >> newer developers to ge

Re: [LMMS-devel] Looking for things to do?

Since #2 is being looked at by Dave I suggest you look into what you can do to #3... -- Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Me

Re: [LMMS-devel] Looking for things to do?

On 12/26/2014 06:38 PM, Tres Finocchiaro wrote: > Stable and master? We should definitely file these. > > - tres.finocchi...@gmail.com <mailto:tres.finocchi...@gmail.com> > > On Fri, Dec 26, 2014 at 8:39 AM, Vesa <mailto:dii@nbl.fi>> wrote: > >

[LMMS-devel] Looking for things to do?

Couple of bugs in master branch which should be easy to fix. I'd fix them myself, but I thought this would be a good opportunity for our newer developers to get a bit more familiar with our codebase - especially the core part of it, not just the GUI. #1 - track muting doesn't work Probably caused

Re: [LMMS-devel] Let's release 1.1

On 12/23/2014 04:24 PM, Tres Finocchiaro wrote: > I've bumped all non-critical bugs that were flagged for 1.1 to 1.2. > > Unless there are objections, I think we're ready to release 1.1. Go for it -- Dive into the World o

Re: [LMMS-devel] Shortcut changes

On 12/21/2014 09:41 PM, Stian Jørgensrud wrote: > I will make an attempt to change some shortcut keys I don't think we should change any shortcuts until we can make them configurable. -- Download BIRT iHub F-Type - The F

Re: [LMMS-devel] Better JACK support

On 12/19/2014 11:49 AM, Raine M. Ekman wrote: > No comment on in/outputs. Transport support is probably not a huge > thing to add when the single tempo track changes are done, locating to > an absolute time should be possible. Yep. > Locating to bar/beat/tick might > be a bit trickier wit

Re: [LMMS-devel] Better JACK support

On 12/19/2014 04:10 AM, Tres Finocchiaro wrote: > "Better JACK support" seems to be a common theme historically for > LMMS, yet we have several specific open bug reports around it which > have gotten very little attention. > > Does anyone object to me wrapping the open bugs into a single bug > repo

Re: [LMMS-devel] Valgrind

On 12/17/2014 08:48 PM, Dave French wrote: > Vesa, I have been grinding on the gameboy instrument, can you remember > or is there a bug report as to what im looking for. valgrind is > reporting numerous uninitialized values, and one memcopy where the src > and destinations overlap, bu

Re: [LMMS-devel] Valgrind

On 12/17/2014 01:04 AM, Lukas W. wrote: > Only if a QObject has a parent Qt automatically deletes all children > on parent deconstruction. Yes, our widgets are initialized with the parent widget (ie. the dialog/window) as parent, so the widgets get destroyed whenever the parent window is destroyed

Re: [LMMS-devel] Valgrind

On 12/17/2014 12:49 AM, Dave French wrote: > I decided to learn how to use Valgrind on code i knew, so decided a > good place to start was to analyse my Eq plugin as that is fresh in my > mind. Im learning quick :) and can see this to be very useful. Think i > may be turning into "Dave the bug hunt

Re: [LMMS-devel] Growl Instrument Idea (Ian Sannar)

On 12/16/2014 07:50 PM, Tres Finocchiaro wrote: > Wishful thinking, but if we get Ian's source code and cross-compile > the DLL using Mingw (or Winegcc or Mono) and clean-room VST headers (I > believe we have some of these in our code, right?) could we offer to > the world the first GPL 2.0 VST? T

Re: [LMMS-devel] Valgrind

On 12/16/2014 07:32 PM, Dave French wrote: > Today was my first time of using Valgrind to detect memory leaks. Its > awsome, and Im planning on spending a bit of time getting to know it. > As a command line tool the output is very verbose, but I ran it in Qt > Creator, and it made viewing the log s

Re: [LMMS-devel] Weird Master channel with some clicks

On 12/13/2014 03:55 PM, Stian Jørgensrud wrote: > Both I and DeRobyJ am using RC10 = > LMMS 1.0.99 which is the latest beta for windows, 12 days old. > Yes that's why I said to update -- Download BIRT iHub F-Type - The F

Re: [LMMS-devel] Weird Master channel with some clicks

Whoever has had problems with clicks, please update to the latest stable-1.1 and see if the problem still persists. I've made some changes that might fix this problem, possibly. -- Download BIRT iHub F-Type - The Free Ente

Re: [LMMS-devel] ... does *this* looks a little (too) familiar?

On 12/08/2014 06:01 PM, Tres Finocchiaro wrote: > That appears to be a nice DAW and although it bares some visual > similarities to LMMS, More likely, it bears visual similarities to FL Studio... just like LMMS. Our tabbed instrument windows, song editor, bb-editor, Fx-mixer, are all just renamed

Re: [LMMS-devel] Weird bug in master branch - can anyone reproduce

Ok I think I've found the bug and fixed it... seems like some kind of race condition in the channel dependency counting routine. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly

Re: [LMMS-devel] Weird bug in master branch - can anyone reproduce

Let me remind you I'm talking about master branch here. It's good if it doesn't show up in 1.1. But I need someone to confirm if they can reproduce this in master. -- Download BIRT iHub F-Type - The Free Enterprise-Grade

[LMMS-devel] Weird bug in master branch - can anyone reproduce

I'm hoping this doesn't turn up in 1.1 as well... if it does, it's pretty serious. The FX mixer seems to randomly turn off channel sends - it seems to mostly happen to a channel that I use for sidechaining, ie. one that has multiple inputs and sends to master. The channel send just gets muted rand

Re: [LMMS-devel] which branch of the git repo to pull.

Like, if you're on master branch / a branch forked from master, you'd sync it up with the main LMMS repo with: git pull --rebase git://github.com/LMMS/lmms.git master -- Download BIRT iHub F-Type - The Free Enterprise-Gr

Re: [LMMS-devel] which branch of the git repo to pull.

On 12/07/2014 08:07 AM, Jonathan Aquilina wrote: > Call me crazy, but is there a page on the wiki which explains how to > setup your forked repo so you can pull any changes of that particular > repo on it? You can do that with git pull --rebase

Re: [LMMS-devel] Questions about LMMS and how it works

On 12/06/2014 11:23 PM, Stian Jørgensrud wrote: > Here are some questions which I don't know the answer to, mostly about the > instruments. > > 1. What does the "Dead" knob do for LB302? Kills the filter envelope. > 2. Do the reverb and chorus for soundfonts activate the effect specifically > for

Re: [LMMS-devel] which branch of the git repo to pull.

As for which branch to target, it's simple, as always: bugfixes for 1.1, everything else for master -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Rep

Re: [LMMS-devel] which branch of the git repo to pull.

On 12/06/2014 11:07 AM, Jonathan Aquilina wrote: > Hi guys, > > I have all dependencies setup on my new mac, but I am wondering which > branch to fork. Should i fork master or in terms of mac related bugs > always the latest stable branch? You fork the entire repo, you can then switch branches on

Re: [LMMS-devel] Max frequency for internal knobs

On 12/04/2014 07:33 AM, Vesa wrote: > On 12/03/2014 10:35 PM, Stian Jørgensrud wrote: >> So I just discovered that the maximum frequency of cutoff frequency knobs in >> LMMS is 14000 Hz, that is quite low and definitively audible when you >> suddenly turn it on or off. Anyone

Re: [LMMS-devel] Max frequency for internal knobs

On 12/03/2014 10:35 PM, Stian Jørgensrud wrote: > So I just discovered that the maximum frequency of cutoff frequency knobs in > LMMS is 14000 Hz, that is quite low and definitively audible when you > suddenly turn it on or off. Anyone know what the reason for this is? Range > should probably be ex

Re: [LMMS-devel] Responsive UI Layout

On 12/01/2014 07:48 AM, Jonathan Aquilina wrote: > Correct me if I am wrong here. We use CSS for the UI layout? We don't. We use QSS (Qt's version of CSS) for theming widgets, and nothing else. Layout is defined in the software.

Re: [LMMS-devel] EQ plugin

On 11/30/2014 05:41 PM, Dave French wrote: > Give me a bit and i will post a screen shot of the ui im working on, > you will see that what you have described is what I am aiming for , + > a hp at the beginning, and low pass at the end. So you want to do peak filters, low/high shelves, and addition

Re: [LMMS-devel] EQ plugin

On 11/30/2014 03:41 PM, Dave French wrote: > My initial thoughts was to have selectable filter types per band so a > few different lp, bell, notch , shelf hp filters types, selectable by > the user, but im not sure that it benefits the user, as it can be more > of a distraction, I also feel using

Re: [LMMS-devel] EQ plugin

On 11/30/2014 12:39 AM, Vesa wrote: > On 11/30/2014 12:24 AM, Dave French wrote: >> You want me pull to code into a class? > No, I can do that... Ok, it is now done (in master branch). BasicFilters.h now contains the class BiQuad, where ch_cnt_t is a typedef for int that signifies c

Re: [LMMS-devel] Build fails on newly cloned master branch

On 11/30/2014 02:16 AM, Chrissy McManus wrote: > I have just done a new git clone of the Master branch and it fails > with this error :- > work in progress -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Serv

Re: [LMMS-devel] EQ plugin

On 11/30/2014 12:24 AM, Dave French wrote: > Parametric EQ would be cool. Especially if you develop a good UI for it. > I'm thinking maybe like a custom QWidget that lets you move the filter > points directly in the frequency response graph. > > You'll probably want to use biquads for the filters.

Re: [LMMS-devel] Planning on writing an eq plugin.

On 11/28/2014 08:49 PM, Dave French wrote: > > Looks like I have no work for 2 weeks, and am planning on spending > some time here. > > I am thinking of developing a parametric eq, simular in use to the > calf 8 band eq. With a spectrum analizer showing before and after > displays. > > Is this some

[LMMS-devel] Surprise Stuff

I needed a break from working on 2.0 so I made some stuff for you to play with in master branch: Each bar in those graphs represents a delay line, with the upper bar controlling volume, and the lower bar controlling lowpass frequency (6dB/oct onepole, might add stages later) Graphics are still

Re: [LMMS-devel] Moving on...

Roadmap, quick sketch: ( Not in chronological order ) - Per track automation (done, mostly) - Pattern overlap prevention (mostly done, some bugs left) - Tempo track (in progress) - Song playback parallelization & redesign (in progress, halfway done) - ProcessHandles for tracks (done) - Control

Re: [LMMS-devel] Moving on...

On 11/27/2014 11:52 AM, Raine M. Ekman wrote: > Cool, but... where's the roadmap you were going to write? I'll get to that when I get to that... I haven't forgotten about it, don't worry. -- Download BIRT iHub F-Type - Th

Re: [LMMS-devel] AFP sampling

On 11/26/2014 11:02 PM, DeRobyJ wrote: > At all xD > > For the attack, ok, this should fix the Start Point click. > But what about loop point? Adjusting loop points to get smooth looping is a forgotten art, remembered only by the ancient tracker wizards... Admittedly LMMS doesn't really provide v

Re: [LMMS-devel] Moving on...

On 11/26/2014 10:21 PM, DeRobyJ wrote: > Hurray! > What about Mixer channel support for sample tracks? Oh, that's a really simple thing. Trivial even. Just hasn't been much point to implement it before since sampletracks have been so broken anyway... ---

Re: [LMMS-devel] AFP sampling

On 11/26/2014 10:48 PM, DeRobyJ wrote: > With AudioFileProcessor the user is able to re-use old ogg/wav files > in their new compositions, but there is one little problem: clip. > > If the user doesn't want to use the whole file, but a small part, he > is able to do that, but it will mostly result

Re: [LMMS-devel] Moving on...

Making more progress with tempo track... Soon, proper sampletrack playback from any position should be a possibility. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Superch

Re: [LMMS-devel] Moving on...

On 11/26/2014 08:19 PM, Tres Finocchiaro wrote: > > Since you're pretty deep into the 2.0 rewrite, we'll need someone else > to look at the dual-filter plugin to move 1.1. along. I'll take a > look now. > Just a hunch, but try adding updateFilters() at the end of the loadSettings() function... -

Re: [LMMS-devel] Moving on...

On 11/26/2014 04:51 PM, Vesa wrote: > Tempo track. > > Not functional yet but the UI is there... I now also have pattern overlap prevention working. -- Download BIRT iHub F-Type - The Free Enterprise-Grade BI

Re: [LMMS-devel] Moving on...

Tempo track. Not functional yet but the UI is there... -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sh

Re: [LMMS-devel] like to mention a peculiarity..

On 11/26/2014 04:04 PM, musikbear wrote: > I do not understand this, and just want to mention it, if /someone else/ > would get a flash of genious, from it. > The thing is, that i have a isp that allow streaming tv in a plugin. > With the release of 1.0, a strage thing happens. > If i have lmms *op

Re: [LMMS-devel] sample-track -is it at all worthy to be included..?

On 11/24/2014 07:56 PM, musikbear wrote: > I wonder if sample-track should be included in the current implementation.. Pointless to remove them now, huge backwards compat backlash, blah blah... We'll be fixing sampletracks in 2.0, so there's no point doing anything to them now. -

Re: [LMMS-devel] Export to MIDI file

On 11/23/2014 11:58 PM, midi-pascal wrote: > Hi all, > > By reading the devel mailing list for a long time I clearly see some > interest for an "Export to MIDIfile" in lmms. > Since I have a very good knowledge of the low level MIDI file structure, > I would be willing to build either a stand alo

Re: [LMMS-devel] Let's release 1.1

On 11/23/2014 01:47 PM, Spekular R wrote: > > X and Y flip is done! All we need is 2 icons (I'm about to make them) > and it'll be ready, so don't release without me :P > Hm... Actually I think these actions would be better to be launched from the context menu of the pattern on the song editor. Th

Re: [LMMS-devel] Let's release 1.1

On 11/21/2014 10:26 PM, Stian Jørgensrud wrote: > :( > > Yes it is unfinished, and so is undo. Undo isn't supported in the Song > Editor at all now! Incorrect... some actions undo, not all. -- Download BIRT iHub F-Type -

Re: [LMMS-devel] Let's release 1.1

On 11/21/2014 05:18 PM, Stian Jørgensrud wrote: > Actually, if you are going to focus on LMMS 2.0 and not bother build official > LMMS 1.2 I don't see any point in waiting with introducing the function to > duplicate several TCO's in the Song Editor. To be honest, this is the most > wanted feature

Re: [LMMS-devel] Options

On 11/21/2014 03:58 PM, Stian Jørgensrud wrote: > Yeah, I agree that it will be more autotracks, and that could be a bad thing. > There is a solution, and that is grouped tracks, like a folder with tracks > inside, hopefully that will be implemented together with the new autotracks. Well probably

Re: [LMMS-devel] Options

On 11/21/2014 12:30 PM, Andreas Ecker wrote: > Restricting an autotrack (the whole track not the pattern) to only one > knob would be a big showstopper for most of my LMMS projects. > > I am using in most of my songs a single one automation track for the > song mixup/mastering - where I e.g. switch

Re: [LMMS-devel] Lowering the barrier of entry for would be developers

On 11/21/2014 07:05 AM, Spekular R wrote: > > Haha. I've commented for myself when doing stuff but I was gonna > remove it before committing anything since it's usually really basic > stuff. Should I keep my comments around, even ones that just explain > what really basic stuff is? > Yes

Re: [LMMS-devel] Lowering the barrier of entry for would be developers

Now, if we really want to lower the barrier of entry for would-be developers, there's one thing we could do... Comment the code. We should have a commenting marathon, where everyone takes some time to go through all of the code that they know how it works, and add commentation. Our code commentat

Re: [LMMS-devel] Lowering the barrier of entry for would be developers

On 11/20/2014 06:41 PM, Tres Finocchiaro wrote: > @Vesa, > > https://github.com/LMMS/lmms/issues/1249 I don't think it's related... -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT

Re: [LMMS-devel] Lowering the barrier of entry for would be developers

Ok, here's one very annoying bug that I'd really like solved - but don't have the time to work on myself... The bug where, when loading a project, window positions get loaded incorrectly. Usually it's the song editor, which goes to overlap with other windows. Possibly there's something wrong with

[LMMS-devel] Options

So. Automations. We have options. #0. Current situation: Each automation can control many knobs, range of automation is the range of the first connected knob #1. Each automation track only controls one knob, if you need it to control several, you'll have to daisy-chain the knobs together by linki

Re: [LMMS-devel] Uh... what?

On 11/20/2014 12:15 AM, Tres Finocchiaro wrote: > > Will you hunt down the subwindow where the knob is, drag the > window close enough to the song editor, then drag the knob to the > track, or will you clone the recorded pattern and then spend time > cleaning it up of dozens of auto

Re: [LMMS-devel] Uh... what?

On 11/19/2014 10:44 PM, Tres Finocchiaro wrote: > > You drag a control to the track. Now, the track is bound to the > control, and you'll NEVER need to ctrl-drag that knob ANYWHERE > during this project again. It's a single hole-in-one shot. Need to > add another pattern? Just click

Re: [LMMS-devel] Uh... what?

On 11/19/2014 11:14 PM, Spekular R wrote: > > It's obviously not one automation track per knob, since Vesa > mentioned automating multiple knobs with one track. So what is it? > One automation track per knob, but not necessarily one knob per

Re: [LMMS-devel] Uh... what?

On 11/19/2014 09:24 PM, Tres Finocchiaro wrote: > I tend to use automations sparingly. When I do, I tend to use a > single automation track and just put small events in it where they are > needed. Well, here's another perspective: My projects can sometimes have something like 20 automation tracks

Re: [LMMS-devel] Uh... what?

On 11/19/2014 08:13 PM, Raine M. Ekman wrote: > Quoting Vesa : >> #0. Current situation: Each automation can control many knobs, range of >> automation is the range of the first connected knob >> >> #1. Each automation track only controls one knob, if you need it to >

Re: [LMMS-devel] Uh... what?

Anyway here's my original message, let's see if this goes through this time... Automations: We have options. #0. Current situation: Each automation can control many knobs, range of automation is the range of the first connected knob #1. Each automation track only controls one knob, if you need i

Re: [LMMS-devel] Uh... what?

On 11/19/2014 07:33 PM, Raine M. Ekman wrote: > Was there anything in the message that could be interpreted as > commands to the mailing list software? I've had a list or two and they > could be admined through mail, no fancy web interfaces needed. > Majordomo and mailman are two names that come to

Re: [LMMS-devel] Uh... what?

On 11/19/2014 06:49 PM, Vesa wrote: >> Your mail to 'LMMS-devel' with the subject >> >> Options >> >> Is being held until the list moderator can review it for approval. >> >> The reason it is being held: >> >> Messa

[LMMS-devel] Uh... what?

> Your mail to 'LMMS-devel' with the subject > > Options > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Message may contain administrivia What the hell is "administrivia" Someone please tell me, this is not an actual word that

Re: [LMMS-devel] Moving on...

On 11/19/2014 05:01 PM, Tres Finocchiaro wrote: > If I have a say, it it will stay LMMS. We own lmms.io > , have an official youtube channel, an official > soundcloud group, official facebook page. > > Yesterday, our site received about 2,400 visitors and if the pattern > continues

Re: [LMMS-devel] Moving on...

On 11/19/2014 04:52 PM, Jonathan Aquilina wrote: > I am actually planning on contributing but with my very limited c/c++ > know how not sure where a good task would be to start. You could run the fundraising for hiring a developer -project. All you'd need to do is accept the legal responsibility o

Re: [LMMS-devel] Moving on...

On 11/19/2014 01:02 PM, Spekular R wrote: > > Vesa, how have you gone about finding compatibility hacks? Have you > searched something like "if (version <..." or have you manually gone > through files looking for that them? Do any compatibility hacks exist > that do

Re: [LMMS-devel] Moving on...

On 11/19/2014 06:21 AM, Tres Finocchiaro wrote: > > > > Perhaps it could be held as a carrot for enticing people to donate for > > the paid developer project... You know, as a perk? Stretch goal? Would > > that be a reasonable thing to do? > > Yes completely agreed. We will need help scabbing comp

Re: [LMMS-devel] Moving on...

On 11/19/2014 03:56 AM, Tres Finocchiaro wrote: > When we originally discussed this idea, we set forth a few > principals. We never voted on them, but I stated that if backwards > compatibly were broken, we would absolutely need to maintain the MIDI > data. Like I said, as long as we're talking a

Re: [LMMS-devel] Moving on...

Ok, so as far as providing backwards compat as a 3rd-party option... I think the actual note data (as it is saved in the project files) is not going to change much if at all - that's one area where we don't really need to do any drastic changes. This means that it should be perfectly possible for

Re: [LMMS-devel] Moving on...

On 11/19/2014 12:29 AM, David Gerard wrote: > But I do want to note: for us users, it's about our music. Users don't > actually care about the software, they care what they can do with it. We're all users here. I don't think anyone here is just in it for the coding, pretty much everyone on this m

Re: [LMMS-devel] Moving on...

On 11/19/2014 12:19 AM, Rob Kudla wrote: > On 11/18/2014 02:23 PM, Vesa wrote: >> Well, if you have old projects, you'll just have to finish them with 1.1 >> or 1.2 and render them to wavs. Then publish them, forget about it, and >> make new music with 2.0. > If th

Re: [LMMS-devel] Moving on...

On 11/19/2014 12:19 AM, Rob Kudla wrote: > On 11/18/2014 02:23 PM, Vesa wrote: >> Well, if you have old projects, you'll just have to finish them with 1.1 >> or 1.2 and render them to wavs. Then publish them, forget about it, and >> make new music with 2.0. > If th

  1   2   3   4   5   6   7   8   9   10   >