You can subscribe to this list here.
2005 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(5) |
Aug
(8) |
Sep
(107) |
Oct
(5) |
Nov
(55) |
Dec
(90) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2006 |
Jan
(75) |
Feb
(68) |
Mar
(56) |
Apr
(33) |
May
(47) |
Jun
(57) |
Jul
(109) |
Aug
(81) |
Sep
(79) |
Oct
(21) |
Nov
(30) |
Dec
(65) |
2007 |
Jan
(30) |
Feb
(54) |
Mar
(34) |
Apr
(71) |
May
(50) |
Jun
(21) |
Jul
(67) |
Aug
(56) |
Sep
(75) |
Oct
(47) |
Nov
(130) |
Dec
(36) |
2008 |
Jan
(8) |
Feb
(8) |
Mar
(25) |
Apr
(16) |
May
(32) |
Jun
(18) |
Jul
(74) |
Aug
(75) |
Sep
(52) |
Oct
(26) |
Nov
(27) |
Dec
(50) |
2009 |
Jan
(36) |
Feb
(45) |
Mar
(23) |
Apr
(34) |
May
(158) |
Jun
(110) |
Jul
(42) |
Aug
(24) |
Sep
(51) |
Oct
(73) |
Nov
(83) |
Dec
(33) |
2010 |
Jan
(16) |
Feb
(11) |
Mar
(41) |
Apr
(29) |
May
(19) |
Jun
(30) |
Jul
(22) |
Aug
(143) |
Sep
(45) |
Oct
(42) |
Nov
(1) |
Dec
(5) |
2011 |
Jan
(25) |
Feb
(12) |
Mar
(35) |
Apr
(36) |
May
(12) |
Jun
(25) |
Jul
(32) |
Aug
(16) |
Sep
(7) |
Oct
(12) |
Nov
(13) |
Dec
(5) |
2012 |
Jan
(26) |
Feb
(23) |
Mar
(34) |
Apr
(17) |
May
(31) |
Jun
(3) |
Jul
(3) |
Aug
(1) |
Sep
(39) |
Oct
(50) |
Nov
(46) |
Dec
(21) |
2013 |
Jan
(85) |
Feb
(54) |
Mar
(6) |
Apr
(9) |
May
(35) |
Jun
(58) |
Jul
(18) |
Aug
(14) |
Sep
(17) |
Oct
(1) |
Nov
(10) |
Dec
(18) |
2014 |
Jan
(1783) |
Feb
(875) |
Mar
(913) |
Apr
(909) |
May
(575) |
Jun
(345) |
Jul
(410) |
Aug
(417) |
Sep
(209) |
Oct
(216) |
Nov
(366) |
Dec
(276) |
2015 |
Jan
(223) |
Feb
(84) |
Mar
(33) |
Apr
(33) |
May
(70) |
Jun
(41) |
Jul
(8) |
Aug
(14) |
Sep
(40) |
Oct
(27) |
Nov
(6) |
Dec
(3) |
2016 |
Jan
(10) |
Feb
(15) |
Mar
(19) |
Apr
(19) |
May
(6) |
Jun
(7) |
Jul
(8) |
Aug
(7) |
Sep
(8) |
Oct
(12) |
Nov
(3) |
Dec
(10) |
2017 |
Jan
(6) |
Feb
(2) |
Mar
(6) |
Apr
|
May
(6) |
Jun
|
Jul
(1) |
Aug
(3) |
Sep
|
Oct
(9) |
Nov
(5) |
Dec
|
2018 |
Jan
(3) |
Feb
(11) |
Mar
(2) |
Apr
(5) |
May
(2) |
Jun
(1) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
2019 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(4) |
Oct
(8) |
Nov
(1) |
Dec
(1) |
2020 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(5) |
Dec
|
2021 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jonathan A. <eag...@gm...> - 2014-01-23 18:39:30
|
Yes a recent commit enabled Werror. This was done by a commit by Andrew Kelly @Andrew Kelly Can you tweak Werror to solve this problem. On Thursday 23 January 2014 20:16:44 Vesa wrote: > Something wrong, LMMS doesn't build. > > /home/vesa/tmp/lmms-ui/plugins/midi_import/portsmf/allegro.h: In member > function ‘double Alg_time_map::beat_to_time(double)’: > /home/vesa/tmp/lmms-ui/plugins/midi_import/portsmf/allegro.h:424:34: > error: assuming signed overflow does not occur when assuming that (X - > c) > X is always false [-Werror=strict-overflow] > cc1plus: all warnings being treated as errors > make[2]: *** > [plugins/midi_import/CMakeFiles/midiimport.dir/portsmf/allegro.o] Error 1 > make[1]: *** [plugins/midi_import/CMakeFiles/midiimport.dir/all] Error 2 > make[1]: *** Waiting for unfinished jobs.... > > Why are all warnings treated as errors now? Is this a codebase cleanup > measure or something? If so that's nice, but it prevents me from > compiling LMMS... is there a cmake flag that I can use to override this > setting? > > ---------------------------------------------------------------------------- > -- CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel |
From: Vesa <di...@nb...> - 2014-01-23 18:16:52
|
Something wrong, LMMS doesn't build. /home/vesa/tmp/lmms-ui/plugins/midi_import/portsmf/allegro.h: In member function ‘double Alg_time_map::beat_to_time(double)’: /home/vesa/tmp/lmms-ui/plugins/midi_import/portsmf/allegro.h:424:34: error: assuming signed overflow does not occur when assuming that (X - c) > X is always false [-Werror=strict-overflow] cc1plus: all warnings being treated as errors make[2]: *** [plugins/midi_import/CMakeFiles/midiimport.dir/portsmf/allegro.o] Error 1 make[1]: *** [plugins/midi_import/CMakeFiles/midiimport.dir/all] Error 2 make[1]: *** Waiting for unfinished jobs.... Why are all warnings treated as errors now? Is this a codebase cleanup measure or something? If so that's nice, but it prevents me from compiling LMMS... is there a cmake flag that I can use to override this setting? |
From: Gurjot S. <bha...@gm...> - 2014-01-23 18:04:57
|
On 23 January 2014 23:30, Vesa <di...@nb...> wrote: > No need, there's a colour blindness filter in GIMP. Okay. -- Gurjot Singh Blog: http://bhattigurjot.wordpress.com |
From: Vesa <di...@nb...> - 2014-01-23 18:00:23
|
On 01/23/2014 07:58 PM, Gurjot Singh wrote: > On 23 January 2014 23:18, Vesa <di...@nb...> wrote: >>> BTW, has the new color scheme been checked for color blindness >>> accessibility? >> It has, at least for the most common forms of colour blindness. >> >> All of the elements should be visible for colour blind people, although >> it's of course impossible to say for 100% certainty without an actual >> colour blind person taking a look at it. >> >> We don't have any UI elements where the state/meaning of an element >> could only be discerned by its colour, anyway. And that's a good thing. > On this note we can use some simulator to test it. > Seems like a nice one: > http://colororacle.org/ > > No need, there's a colour blindness filter in GIMP. |
From: Vesa <di...@nb...> - 2014-01-23 17:48:27
|
On 01/23/2014 07:38 PM, Raine M. Ekman wrote: > BTW, has the new color scheme been checked for color blindness > accessibility? It has, at least for the most common forms of colour blindness. All of the elements should be visible for colour blind people, although it's of course impossible to say for 100% certainty without an actual colour blind person taking a look at it. We don't have any UI elements where the state/meaning of an element could only be discerned by its colour, anyway. And that's a good thing. |
From: Raine M. E. <ra...@ik...> - 2014-01-23 17:39:10
|
Quoting Vesa <di...@nb...>: > On 01/23/2014 04:05 PM, Tres Finocchiaro wrote: >> >> >> Is there anything that can be done to more effectively use the screen >> real-estate at the top of the software? >> Inline image 2 >> >> - > > Yes, there is anything that can be done. But I don't think it will be > done for this release. Possibly for a future release though. > > It would however require to make the oscilloscope smaller, and to make > the sliders horizontal, and it would also stretch the horizontal > dimension of the toolbar up to around 1000 pixels - meaning that LMMS > couldn't be used on 800x600 monitors. I don't think it's usable in that > small size anyway, but apparently that is a concern to some... so maybe > it'd need to be a configuration option. > Let's see, it's not like all that stuff has to be visible. The top row of buttons (new project...export project) are duplicated in the menu. Unless the menu is thrown away those buttons could be hidden without causing much pain. The second row shows the different windows, could be hidden with their functions added to a "view" menu in addition to the F-buttons. Those visibilities would of course be configurable. Turn the time signature horizontal, sliders as well, maybe move the scope to a window of its own (i don't know if it's useful in a smaller size)? When everything is the same height it could just flow to the next row in narrow windows, and fit on one row in wider windows. I've used 1024x600 quite a bit, and it's OK as long as you don't use VSTs or Zyn (it's not like my old Eeepc has the horsepower for that anyway...) 800x600 is a bit worse, but not yet unusable. BTW, has the new color scheme been checked for color blindness accessibility? -- ra...@ik... http://www.mikseri.net/radioproject |
From: Tres F. <tre...@gm...> - 2014-01-23 15:11:23
|
Whoops... click send too soon... As for boosted saturation for icons, here's my opinion on it: I don't > think it's necessarily a good idea. That's exactly what was problematic > with the old style, everything being so colorful and garish, which just > makes the UI look too busy, messy and confusing. Completely agreed. The new theme is in the right direction. I was skeptical at first, but the more I stare at it, the more I see this argument coming to life. -Tres - Tre...@gm... On Thu, Jan 23, 2014 at 10:10 AM, Tres Finocchiaro < tre...@gm...> wrote: > As for boosted saturation for icons, here's my opinion on it: I don't > think it's necessarily a good idea. That's exactly what was problematic > with the old style, everything being so colorful and garish, which just > makes the UI look too busy, messy and confusing. > > - Tre...@gm... > > > On Thu, Jan 23, 2014 at 9:38 AM, Jonathan Aquilina <eag...@gm... > > wrote: > >> Correct me if im wrong. But what I see since im on a bigger screen is >> lots of >> wasted space with the bars stacked under each other. >> >> FL has two bars on the left then everythign stretched the rest of the >> length >> of the screen. >> >> Is this something that could be done to solve this issue? >> >> On Thursday 23 January 2014 16:36:25 Vesa wrote: >> > On 01/23/2014 04:05 PM, Tres Finocchiaro wrote: >> > > Is there anything that can be done to more effectively use the screen >> > > real-estate at the top of the software? >> > > Inline image 2 >> > > >> > > - >> > >> > Yes, there is anything that can be done. But I don't think it will be >> > done for this release. Possibly for a future release though. >> > >> > It would however require to make the oscilloscope smaller, and to make >> > the sliders horizontal, and it would also stretch the horizontal >> > dimension of the toolbar up to around 1000 pixels - meaning that LMMS >> > couldn't be used on 800x600 monitors. I don't think it's usable in that >> > small size anyway, but apparently that is a concern to some... so maybe >> > it'd need to be a configuration option. >> >> >> >> ------------------------------------------------------------------------------ >> CenturyLink Cloud: The Leader in Enterprise Cloud Services. >> Learn Why More Businesses Are Choosing CenturyLink Cloud For >> Critical Workloads, Development Environments & Everything In Between. >> Get a Quote or Start a Free Trial Today. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk >> _______________________________________________ >> LMMS-devel mailing list >> LMM...@li... >> https://lists.sourceforge.net/lists/listinfo/lmms-devel >> > > |
From: Tres F. <tre...@gm...> - 2014-01-23 15:10:28
|
As for boosted saturation for icons, here's my opinion on it: I don't think it's necessarily a good idea. That's exactly what was problematic with the old style, everything being so colorful and garish, which just makes the UI look too busy, messy and confusing. - Tre...@gm... On Thu, Jan 23, 2014 at 9:38 AM, Jonathan Aquilina <eag...@gm...>wrote: > Correct me if im wrong. But what I see since im on a bigger screen is lots > of > wasted space with the bars stacked under each other. > > FL has two bars on the left then everythign stretched the rest of the > length > of the screen. > > Is this something that could be done to solve this issue? > > On Thursday 23 January 2014 16:36:25 Vesa wrote: > > On 01/23/2014 04:05 PM, Tres Finocchiaro wrote: > > > Is there anything that can be done to more effectively use the screen > > > real-estate at the top of the software? > > > Inline image 2 > > > > > > - > > > > Yes, there is anything that can be done. But I don't think it will be > > done for this release. Possibly for a future release though. > > > > It would however require to make the oscilloscope smaller, and to make > > the sliders horizontal, and it would also stretch the horizontal > > dimension of the toolbar up to around 1000 pixels - meaning that LMMS > > couldn't be used on 800x600 monitors. I don't think it's usable in that > > small size anyway, but apparently that is a concern to some... so maybe > > it'd need to be a configuration option. > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > |
From: Second F. <qbg...@gm...> - 2014-01-23 14:49:30
|
There is ONE crash sample that's external, but I'm sure we can find a replacement c: -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/I-want-to-give-my-most-polished-tracks-source-for-LMMS-demo-projects-tp5212p5263.html Sent from the lmms-devel mailing list archive at Nabble.com. |
From: Jonathan A. <eag...@gm...> - 2014-01-23 14:38:17
|
Correct me if im wrong. But what I see since im on a bigger screen is lots of wasted space with the bars stacked under each other. FL has two bars on the left then everythign stretched the rest of the length of the screen. Is this something that could be done to solve this issue? On Thursday 23 January 2014 16:36:25 Vesa wrote: > On 01/23/2014 04:05 PM, Tres Finocchiaro wrote: > > Is there anything that can be done to more effectively use the screen > > real-estate at the top of the software? > > Inline image 2 > > > > - > > Yes, there is anything that can be done. But I don't think it will be > done for this release. Possibly for a future release though. > > It would however require to make the oscilloscope smaller, and to make > the sliders horizontal, and it would also stretch the horizontal > dimension of the toolbar up to around 1000 pixels - meaning that LMMS > couldn't be used on 800x600 monitors. I don't think it's usable in that > small size anyway, but apparently that is a concern to some... so maybe > it'd need to be a configuration option. |
From: Vesa <di...@nb...> - 2014-01-23 14:36:35
|
On 01/23/2014 04:05 PM, Tres Finocchiaro wrote: > > > Is there anything that can be done to more effectively use the screen > real-estate at the top of the software? > Inline image 2 > > - Yes, there is anything that can be done. But I don't think it will be done for this release. Possibly for a future release though. It would however require to make the oscilloscope smaller, and to make the sliders horizontal, and it would also stretch the horizontal dimension of the toolbar up to around 1000 pixels - meaning that LMMS couldn't be used on 800x600 monitors. I don't think it's usable in that small size anyway, but apparently that is a concern to some... so maybe it'd need to be a configuration option. |
From: Vesa <di...@nb...> - 2014-01-23 14:27:22
|
On 01/23/2014 02:35 PM, Tobias Doerffel wrote: > Sure we can drop this image. It's a relict from our beginnings almost > 10 years ago... ;-) > > I agree that the new theme is very nice but indeed a little bit too > pale. Some icons like automation patterns could really benefit from > boosted saturation. Vesa, what's your opinion on this? > > I have a replacement image for the crappy looking drum in the bb-editor, which I think many people will like. If not, we'll just remove it entirely. As for boosted saturation for icons, here's my opinion on it: I don't think it's necessarily a good idea. That's exactly what was problematic with the old style, everything being so colorful and garish, which just makes the UI look too busy, messy and confusing. The same problem is with the KDE default theme, for example. UI icons shouldn't be colourful, because in modern software, UI is expected to stay out of the way and not compete for attention with the actual content. To this end, I've strived to limit the colours used in icons, and the UI in general - and to use a consistent palette all around. Now coming to think of it, the bb-editor icons should probably be the same colour as instrument tracks, not the same as sample tracks, so that's probably something I'll have to fix. The colour of the automation track icons is also the same colour that is used for the automation tracks themselves. I think it's a good colour, since it gives a good contrast with the dark background of the tracks - a more saturated blue would by necessity be darker, and this would lower the contrast in the tracks which would not be a good idea at all. |
From: LocoMatt <sam...@gm...> - 2014-01-23 14:18:19
|
There is txt file where everything is described. For drums I used Synth 1 and some free compresors. For fx I used Tyrell N6. Some sounds are from ready presets but very edited. Sounds can be similar to sounds icluded in LMMS because some of them are based on 808, 909 samples and other old samplers. Basicly I added bpm info for me because (before I released it) it was very helpful in making my songs. P.S I never used lmms samples so i didn't noticed it before ;P -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Additional-samples-tp5252p5259.html Sent from the lmms-devel mailing list archive at Nabble.com. |
From: Rob K. <sou...@ku...> - 2014-01-23 13:43:14
|
On 01/23/2014 08:17 AM, Tres Finocchiaro wrote: > I feel "Owl City - Fireflies" is a fantastic candidate for > consideration to LMMS sample projects and I feel I've made the case that > it falls under the "fair use" clause. - Do others agree that it should > be included? - If so, should we move forward and get permission from the > 3 authors? 1. I don't think it should be included with LMMS because I would hope anything included with LMMS would be under a free license. Inclusion of Fireflies certainly violates the Debian Free Software Guidelines, for example, and may get LMMS removed (or maybe they would just include a patch that omits Fireflies from the package). Further, if someone gets LMMS, doesn't realize Fireflies was a hit song (I would never have known it existed, myself, if I didn't sit next to someone at a client site who runs a radio all day on a top 40 station; I've literally heard it nowhere else), uses the sample project as a base and comes up with something else that became a hit, they could be sued for making a derivative commercial work. I don't think you want (or should want) to put your users in that position, so I think only stuff that can be licensed under CC-BY or similar, if not dedicated to the public domain, should be included. 2. Why would you feel you need to get permission from the 3 people who arranged the song in LMMS if you don't feel you need to get permission from the original copyright holder? Does copyright only count if it's held by some guy using a one-word pseudonym on the Internet? If lifting the entire melody and arrangement from a hit song is "fair use", wouldn't lifting someone else's arrangement be as well? For the record, I think the US copyright system in its current state sucks ass. When people are still getting sued for performing "Happy Birthday", a melody written literally 121 years ago with words published 102 years ago, it's clearly abusive. But it exists, and free software needs to work within it. Rob |
From: Tres F. <tre...@gm...> - 2014-01-23 13:17:43
|
@Vesa, Thank you for the recommendation. I feel "Owl City - Fireflies" is a fantastic candidate for consideration to LMMS sample projects and I feel I've made the case that it falls under the "fair use" clause. Back on point: - Do others agree that it should be included? - If so, should we move forward and get permission from the 3 authors? -Tres - Tre...@gm... On Thu, Jan 23, 2014 at 1:26 AM, Vesa <di...@nb...> wrote: > On 01/23/2014 04:57 AM, John Serafino wrote: > > I'd like to nitpick your assertion that the track not using the > > recorded vocals makes a difference. The melodies are also copyrighted. > > > > I think any reasonable judge/jury would call fair use in this > > situation. IMO though, a top dollar lawyer's whole life is persuading > > the judge/jury to interpret the law their way. This means that you > > need to have a sufficiently untouchable case in your favor or not give > > the companies any incentive to attack. > > > > And just to clarify something, number 4 is about the economical effect > > of the market. Think laws of supply and demand. If you give away a > > better version of the original for free, the market for the original > > dwindles. This isn't what's happening here, but that sort of thing is > > what that fourth point is for. > > > > > You could always get a compulsory license. > > http://en.wikipedia.org/wiki/Compulsory_license#United_States > > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > LMMS-devel mailing list > LMM...@li... > https://lists.sourceforge.net/lists/listinfo/lmms-devel > |
From: Gurjot S. <bha...@gm...> - 2014-01-23 13:05:13
|
On 22 January 2014 21:35, John Serafino <lzr...@gm...> wrote: > Perhaps we should post bug/feature requests to the github tracker first, and > try to stick primarily to discussion of development direction, work > organization, or major program changes on this mailing list? Actually that's how it should be done. -- Gurjot Singh Blog: http://bhattigurjot.wordpress.com |
From: LocoMatt <sam...@gm...> - 2014-01-23 12:47:09
|
How about new samples included into LMMS Here's my own sample pack. Everything is done by me. https://drive.google.com/file/d/0B_LYvSmEjdiBSXBuOTBXZFJOckk/edit?usp=sharing -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/Additional-samples-tp5252.html Sent from the lmms-devel mailing list archive at Nabble.com. |
From: Tobias D. <tob...@gm...> - 2014-01-23 12:35:49
|
Sure we can drop this image. It's a relict from our beginnings almost 10 years ago... ;-) I agree that the new theme is very nice but indeed a little bit too pale. Some icons like automation patterns could really benefit from boosted saturation. Vesa, what's your opinion on this? Toby |
From: Stian J. <sti...@gm...> - 2014-01-23 12:15:59
|
Two more things :-p 1. Do one really need to have an image top right corner in the B&B editor? No other window has this and why have two different icons for the B&B editor? 2. Use whatever you like from my themes. https://drive.google.com/folderview?id=0B-1kciTMrTBZTmlGMU5ad1JGVm8&usp=sharing -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/UI-graphical-rehaul-project-tp4165p5250.html Sent from the lmms-devel mailing list archive at Nabble.com. |
From: Stian J. <sti...@gm...> - 2014-01-23 11:54:36
|
So I have looked at some pictures Greippi sent me of the new GUI, which I know is unfinished, and mostly like what I have seen so far! The B&B editor looks neat. The new automation track icon is what I dislike the most, it is a totally new colour? The theme itself I would describe as pale, low contrast and faded (not necessarily bad) but still a very cool theme. I think the colour of the automation track should be stronger blue, for example the same blue colour as TripleOsc (Mix, PM, waveforms) in this window. One could consider boosting the saturation of the other blue colours as well, or use the same blue as TripleOsc everywhere, however it might be counterproductive against the style I have mentioned. Hope to see the old colour go. My first impression when seeing the GUI was that the new grey and the old blue don't fit together. It is improvements every way I look at it :) <http://linux-multimedia-studio-lmms.996328.n3.nabble.com/file/n5249/Kuvakaappaus_2014-01-23_13_30_15.png> -- View this message in context: http://linux-multimedia-studio-lmms.996328.n3.nabble.com/UI-graphical-rehaul-project-tp4165p5249.html Sent from the lmms-devel mailing list archive at Nabble.com. |
From: Jonathan A. <eag...@gm...> - 2014-01-23 10:33:00
|
Suggestion which might involve some fancy mathematics here. Is there a way we can have the logo scale up to the max size of 800x800 and scale down depending on the size of the screen? On Thursday 23 January 2014 00:36:49 Tobiasz Karoń wrote: > Are you serious? I'd like that, but it would be good if it scaled down to > half of that while running on a small screen. Sometimes I have such a > screen when I use a projector to tech students LMMScraft. > > On 22 Jan 2014 23:24, "Vesa" <di...@nb...> wrote: > > On 01/23/2014 12:12 AM, Tres Finocchiaro wrote: > > > > *Do we have a selected a uniform output resolution for the splash screen > > > >> graphics.* > >> > > Here's what I've gathered: > > > > Splash Resolutions: > >> *LMMS: *400x400 > >> *GIMP: *560x350 > >> *Hydrogen:* 400x300 > >> *NetBeans:* 475x300 > >> *FL Studio: *250x400 > > > > So the median size between those 5 would be 400x350. That would be the > > safe choice. > > > > But I say, let's be bold and stand out from the crowd. Let's make our > > splash screen bigger than all of them. Let's make it 800 x 800. |
From: Jonathan A. <eag...@gm...> - 2014-01-23 10:31:44
|
I think the best thing to do would be to have 4 ppa's one for linux ( ubuntu) another for rpm package another for windows and mac osx. If we provide these we can easily get testing coverage across all platforms. On Thursday 23 January 2014 11:29:19 Tobias Doerffel wrote: > At least the Win32/Win64 cross compilation should work as all you need is > installing various packages from the MinGW PPA and run the > "build_mingw32"/"build_mingw64" script and "make" afterwards. |
From: Tobias D. <tob...@gm...> - 2014-01-23 10:29:26
|
At least the Win32/Win64 cross compilation should work as all you need is installing various packages from the MinGW PPA and run the "build_mingw32"/"build_mingw64" script and "make" afterwards. |
From: Jonathan A. <eag...@gm...> - 2014-01-23 10:27:32
|
No problem :) its a great asset that we can further have enhance things through the uploads. @lukas can travis build for non linux platforms? Or is that something the LMMS code would need to have tweaked somethings in regards to cmake? On Thursday 23 January 2014 11:22:27 Tobias Doerffel wrote: > BTW thanks for your work on the CI system!! I think this greatly helps to > improve overall software quality. |
From: Tobias D. <tob...@gm...> - 2014-01-23 10:22:34
|
BTW thanks for your work on the CI system!! I think this greatly helps to improve overall software quality. |