Absolutely!!! That is so right on Vesa!
I'm so glad you are around to think of things like that! Keep up your
awesome work!
On 03/06/2014 10:36 PM, Vesa wrote:
> On 03/07/2014 02:44 AM, Tres Finocchiaro wrote:
>> I personally am spilt 50/50 in terms of a non-intrusive upgrade
>> indicator, but
On 03/07/2014 02:44 AM, Tres Finocchiaro wrote:
> I personally am spilt 50/50 in terms of a non-intrusive upgrade
> indicator, but it would have to get coded and Vesa seems mostly
> against it.
>
>
Well, I'm not the only coder here (I'm not much of a coder anyway), and
my word isn't the law on the
On 03/07/2014 12:33 AM, Stian Jørgensrud wrote:
> Agreed. Thit is the best option apart from option 4: Simulating 200% by
> boosting above 100 with an amp.
>
>
> diiz wrote
>> Thinking about this again, I'm starting to think it'd be best to just
>> keep native instrument volume as it is (0-200), ke
I personally am spilt 50/50 in terms of a non-intrusive upgrade indicator,
but it would have to get coded and Vesa seems mostly against it.
-Tres
- tres.finocchi...@gmail.com
On Thu, Mar 6, 2014 at 6:55 PM, Bill Y. wrote:
> How about a little LED graphic in a corner that lights up when there
How about a little LED graphic in a corner that lights up when there is an
update, and the user has the option to set it's brightness level? It could
have a user definable dimmer so it can be as unintrusive as a user wants.
On Thu, Mar 6, 2014 at 6:08 PM, Tres Finocchiaro wrote:
>
> On Mar 6, 2
Here is the thing. Midi is a two way street.. If some one uses LMMS as
their sequencer, and makes volume changes in LMMS then sends that sequence
data back out over midi, the music volume will clip. This would be highly
undesirable. Instead it would be better to have the option to normalize the
mid
sorry, that should read 1-200% volume scale*
On Thu, Mar 6, 2014 at 6:38 PM, Bill Y. wrote:
> Here is the thing. Midi is a two way street.. If some one uses LMMS as
> their sequencer, and makes volume changes in LMMS then sends that sequence
> data back out over midi, the music volume will clip
On Mar 6, 2014 5:07 PM, "Stian Jørgensrud" wrote:
>
> Use HTML iframe tag?
>
Yes, sort of but making the content more appropriate. iFrame would just
put the mess of information that's already mostly irrelevant to installing
onto our page.
Simply putting the ppa dropdown with command line I woul
Agreed. Thit is the best option apart from option 4: Simulating 200% by
boosting above 100 with an amp.
diiz wrote
> Thinking about this again, I'm starting to think it'd be best to just
> keep native instrument volume as it is (0-200), keep the MIDI velocity
> mapping at 100=127, and cap the vel
Haha. I saw that link, and this one is even more amazing. I don't think I
would ever need any strange BPM, really... never.
http://en.wikipedia.org/wiki/List_of_musical_works_in_unusual_time_signatures#1.2F.E2.88.9A.CF.80.2F.E2.88.9A.E2.85.94
Raine M. Ekman wrote
> It's the cutting edge of modern
Use HTML iframe tag?
Tres Finocchiaro wrote
> I would be a fan of providing something like this on our downloads
> section.
>
> The way launchpad displays this (scrolling way down, clicking the
> triangle,
> clicking the version) sort of hides it away.
>
> Is anyone aware if launchpad has a way
Hmm. I find pop ups very useful most times. What if you made it "a new
version is available" like an alert message (hoovering box in a corner) you
didn't have to click ok? It just fades out itself. That would be fine for
everyone, at least if it only popped up once, and then didn't bother you
again
Couldn't we offer something like a normalize toggle that when checked
scales midi input to fit the 200% range, but when uncheck scales only to
100%? That way people can choose how they want to deal with the problem on
a per instrument basis.
On Thu, Mar 6, 2014 at 2:06 AM, Vesa wrote:
> Thinkin
Dont forget that we will have random bug fix releases in between
On 4 Mar 2014 16:59, "Israel" wrote:
> On 03/04/2014 09:58 AM, Jonathan Aquilina wrote:
>
> Not even providing a notification and link to where to download the new
> version's installer?
>
>
> On Tue, Mar 4, 2014 at 4:53 PM, Vesa
On 03/06/2014 01:53 PM, Raine M. Ekman wrote:
> Beat patterns should really be upgraded to have both a length and a
> denominator. 36 48ths for a drum fill? 16 quarter notes for a long,
> stiff beat where you don't need those smaller notes? No problem! (But
> it might be a lot easier said than don
On 03/06/2014 01:53 PM, Raine M. Ekman wrote:
> Beat patterns should really be upgraded to have both a length and a
> denominator. 36 48ths for a drum fill? 16 quarter notes for a long,
> stiff beat where you don't need those smaller notes? No problem! (But
> it might be a lot easier said than don
On 03/06/2014 11:49 AM, Raine M. Ekman wrote:
> Citerar Vesa :
>> You have to also remember that time sig in LMMS doesn't work exactly the
>> same way as time sig in sheet music. In traditional notation, the lower
>> part signifies which note length corresponds to one beat, for example:
>> in 4/8 t
Citerar Vesa :
> You have to also remember that time sig in LMMS doesn't work exactly the
> same way as time sig in sheet music. In traditional notation, the lower
> part signifies which note length corresponds to one beat, for example:
> in 4/8 time, an 8th note would be one beat, meaning that one
18 matches
Mail list logo
