Re: [LMMS-devel] What compression does .mmpz use?

@David, According to this link , this explains it... Basically zlib compressed, but without the first 4 bytes (documented a bit also at LMMS/lmms.io#59

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

> > > I mean, how do we differentiate whether the user ctrl-drag-copies > (already a cumbersome operation requiring at least two hands) a pattern > because they want a copy of the pattern, or because they just want a > pattern connected to the same knob to modify? So the argument is that the aver

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

[LMMS-devel] What compression does .mmpz use?

Getting LMMS files added to the Archive Team File Formats wiki. .mmp is just XML, I'm presuming .mmpz is the same thing compressed ... but what compression is it? It doesn't seem to be ordinary gzip. - d. -- Download BIR

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

> > 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 > automation points - those are the current options, and either way is

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

Ah, right, one automation per *automation track*. I think #1 is the best out of of those choices. There's no reason at all to automate a knob from many different tracks, and having only one type of automation per automation track is good practice. If we were to allow one track driving multiple knob

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 automation track... --

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

> > The idea is to have one automation track per what? > Knob. Per: 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 > c

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

I'm getting very confused on the whole one automation track thing. The idea is to have one automation track per what? One automation per regular track (sample/bb/instrument) would be pretty horrible, since you could no longer automate more than one thing at a time (Aside from the very limited idea

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

> > 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 the track, there it is, initialized with the control's current

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?

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. Having multiple tracks using option #1 instead of the option #5 (keep it the way it is) could be a visual distraction from a usability perspective, but if

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

i would be perfectly ok with 2, but thats because i always has used aut. /that/ way.. So here someone with the habbit of using one or a few aut-tracks for /all/ automations, need to speak Again the most important thing is efficiency /cpu-leaness (imo) btw -topic need a new header now ( i think i

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 >> control several, you'll have

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

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 > control several, you'll have to daisy-chain the knobs together by linking > > #2.

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

Quoting Vesa : > 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

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?

Den 19 nov 2014 18:56 skrev Vesa : > > 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: > >> > >> Message may co

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] Diddent someone make a "how to use hydrogen in lmms" tut ??

And the hydrogen tut were never linked to, cause I have gone through all sites some times the last year, don't remember seeing any hydrogen tutorial. My guess is that you perhaps remember it from the forum. Tres Finocchiaro wrote >> I thought it maybe was "/lost in translation"/ from sourceforge

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

Heheh, Comic Sans... Many planning to get dirty with coding, Jonathan, you know some python right? Anyway, there's something to do even if you can't code, the hard part is to devote time. -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Moving-on-tp108

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

Target stable-1.1 for now. Well discuss the branch destination again on the pull request. There's too much I'm the air to know for sure which branch should be targeted. We should see the changes before making that call.

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

Do we define the categories for the mailing list or the groups on the mailing list? On Wed, Nov 19, 2014 at 5:56 PM, Tres Finocchiaro < tres.finocchi...@gmail.com> wrote: > Weird. > > Full Definition of ADMINISTRIVIA > > > > : routine paperwork and other administrative tasks that are regarded as

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

i will join you on the apple bugs :) What I am not totally clear on though. all the mac work does that get thrown into master? and then finds its way into a stable branch when we create the new stable branch? On Wed, Nov 19, 2014 at 5:52 PM, Tres Finocchiaro < tres.finocchi...@gmail.com> wrote: >

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

Weird. Full Definition of ADMINISTRIVIA : routine paperwork and other administrative tasks that are regarded as > trivial, uninteresting, and time-consuming spending patterns put too many dollars toward and too often place political > concerns ahead of real student needs. — Plain Dealer (Clev

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: >> >> Message may contain administrivia > > What the hell is "administrivia" > > Someon

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

> > > They have certain tasks which they like to call easy hacks. They > classify them according to difficulty and how much programming know how one > needs. I think if you've been following the discussion on our bug tracker and our mailing list you will notice we have many of these easy hacks an

[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...

> > can go start an angry blog written entirely in comic sans. I'm terribly sorry for taking the bait here... I'm not normally one to troll (image attached) -- Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Se

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] Diddent someone make a "how to use hydrogen in lmms" tut ??

> > I thought it maybe was "/lost in translation"/ from sourceforge to IO :) We shouldn't have anything "lost in translation". Please be more specific. This shouldn't be a black box. We ran both sites side-by-side for a while to get feedback prior to switching. We also have the old site avail

Re: [LMMS-devel] Diddent someone make a "how to use hydrogen in lmms" tut ??

> > *...* cant do that at this very moment -no linux machine I don't see how that is relevant? https://downloads.sourceforge.net/project/hydrogen/Hydrogen/0.9.6%20Binaries/hydrogen_0.9.6-alpha1.exe -Tres - tres.finocchi...@gmail.com On Wed, Nov 19, 2014 at 9:36 AM, musikbear wrote: > Tres F

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

> > I really want to get my hands dirty with programming I'd argue most of our community would rather be making music, but we all make personal sacrifices for the greater good. It's part of the culture. :) -Tres -- Down

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

I really want to get my hands dirty with programming On Wed, Nov 19, 2014 at 4:01 PM, Vesa wrote: > 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

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

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, it is likely to grow over time if we keep releasing updates and better way

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...

diiz wrote > think LMMS 2.x >> needs to be called something other than LMMS > > Again? Welp, time for another round of bikeshedding... :D *sigh* not ..again oki /Leisure music making studio/ == LMMS New meets old, Kisses are exchanged, and nothing is changed hooray -- View this message in

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

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. On Wed, Nov 19, 2014 at 3:17 PM, Lukas W. wrote: > Here's some probably even crazier food for thought. If you have ideas that > good… Why don't you actually do some of the

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

Jonathan Aquilina wrote > Do you guys think this would be a good thing to have and maybe list them > on > the website? I think it would be a tremendious idea! -But theres is a crevat. It would mean that some really strong develloper went through all the tickets, and marked the tickets in difficul

Re: [LMMS-devel] Wanted to introduce myself

Stian Jørgensrud wrote > Do you have your music online? Want to share? :) You can join the forum > for more casual music talk! Here: http://lmms.io/forum/ Great to have you onboard! -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Wanted-to-introduce

Re: [LMMS-devel] Diddent someone make a "how to use hydrogen in lmms" tut ??

Tres Finocchiaro wrote* > do some investigation on your own * > and have > Stian, Uros or Evan update the tutorial to reflect your findings. *...* cant do that at this very moment -no linux machine (ya i know WM + install .. its in the pipeline..) I think i saw /more/ on this once, not just that

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

Here's some probably even crazier food for thought. If you have ideas that good… Why don't you actually do some of the things you keep talking about, or just shut up? That 'or' is not exclusive. 2014-11-19 14:58 GMT+01:00 Jonathan Aquilina : > Here is some probably crazy food for though. If there

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

Technically couldnt copy the code from the other projects? On Wed, Nov 19, 2014 at 3:10 PM, David Gerard wrote: > 'Cos someone would have to sit down and write the exporters. > > (We still don't even have a direct MIDI export.) > > On 19 November 2014 13:58, Jonathan Aquilina > wrote: > > Here

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

'Cos someone would have to sit down and write the exporters. (We still don't even have a direct MIDI export.) On 19 November 2014 13:58, Jonathan Aquilina wrote: > Here is some probably crazy food for though. If there is potential for mmp > and mmpz being dropped. Why dont we allow users to expo

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

Here is some probably crazy food for though. If there is potential for mmp and mmpz being dropped. Why dont we allow users to export in other formats the other open source DAWS use such as hydrogen rosegarden etc? On Wed, Nov 19, 2014 at 2:54 PM, Tres Finocchiaro < tres.finocchi...@gmail.com> wrot

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

> > > why not if an old project is opened lmms2 that it upgrades the mmp with > data that it speaks and understand? That is EXACTLY what we are talking about. Vesa is removing old compat code (for good reason). We'll have an equivalent of it back in. We'll see where the 2.0 branch ends up thou

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

Stian and Tres both show and mention versioning. I dont know if it is as simple as this, but why not if an old project is opened lmms2 that it upgrades the mmp with data that it speaks and understand? Or would a converter of some sort be better here. On Wed, Nov 19, 2014 at 2:48 PM, Tres Finocchia

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 don't rely on checking for old vers

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

> > > How can you even check version on a project? https://github.com/LMMS/lmms/blob/master/src/core/project_version.cpp Or https://github.com/LMMS/lmms/blob/master/src/core/DataFile.cpp#L328 Etc. - tres.finocchi...@gmail.com On Wed, Nov 19, 2014 at 8:42 AM, Stian Jørgensrud wrote: > How

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

How can you even check version on a project? 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 > don't rely on c

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

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 don't rely on checking for old versions, and thus wouldn't be found by a search? --

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

On 19 November 2014 04:27, Vesa wrote: > If we're going to add any compat code for 1.x projects, that should be > done as an import plugin. That way we can confine any legacy code into a > neat little box that doesn't clutter the rest of the codebase. Yes, that's reasonable. It could even get