Re: [ubuntu-studio-devel] HiDPI (previously: Re: Next cycle)
On Fri, 14 Apr 2017, eylul wrote: *nods* GTK2 and java are the 2 major desktop env. independent culprits, from what I can tell, which unfortunately are still around in many applications. It is possible to do HIDPI in GTK2. I know Ardour dealt with it when Mac defaulted to hidpi. (maybe try running Ardour on your hidpi monitor and see) It does take developer attention though. Ardour is _not_ switching to gtk3 BTW, but have been slowly reducing the use of gtk2 by replacing calls with built in functions that deal with cairo. -- Len Ovens www.ovenwerks.net -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
Re: [ubuntu-studio-devel] Next cycle
On Fri, 14 Apr 2017, eylul wrote: Len thanks for this. A lot of interesting thoughts here. Opinions, etc ahead. :) I have tried to make sure that people know many tings I say here are either opinion or based on my very specific work flow. Auto mounting - we used to make sure there was no auto mounting of USB Yes, it is best for design/art people to have automount (its already hard to bring design/art people to unfamiliar ground, more intuitive behavior, the better), turning it off could be a good addition to the -controls through if it is feasible? If not I think it is worth discussing pros and cons and more details on what the problem is. If it is seriously hindering audio creators, I'll take not hindering one side in price of being a bit less intuitive to other side. Hmm, I looked at settings. It is possible to have a selection of panel (menubar) setups, or saved sessions. Neither seem to include totally different window manager settings. Also, I don't think desktop settings should be something we try and micro manage anyway. These are user preferences where we try to set sane defaults but the user sets them exact. Documentation of which desktop settings may be helpful to different workflows may be a better solution. Auto updating - same as above. But to add to it, I noticed that considering autoupdates fixes security issues among other things I would go with they need to stay. In terms of the kernel issue, I do use efi, I never ran out of space in that manner until now, but still filing a bug about this could be useful? Can you check how big and how full this is? how many kernels are in there? whisker menu - I still hate it :) But if we are going to keep it (I always go back to the system menu on my systems) can we at least resize it so that the menu categories are all visible by default... My personal disagreement with this aside (I actually use the search bar to launch a program often) :D I would caution against hover in particular as it is a gesture that is inaccessible to touchscreens (which are becoming more and more common on laptops). I assume this is why whisker went with this approach actually. I think my first point still stands. The user should be able to see all the categories without having to scroll down. The current whisker window size means System and the Ubuntu Studio submenu are not visible (maybe office too) The user adding new sw (a web page editor for example or wine) will add yet more categories. The point is, I was looking for system and couldn't find it. Also scroll bars as narrow as what we have are not easy to deal with on a tablet anyway. Can we change the default theme to Moheli or similar? There are two things I like in a theme: The window with focus stands out - menu bar is a different colour The border needs to be wide enough to be easy to grab More than one workpace by default - I understand that I may work a bit I understand that xubuntu is aimed at mainstream either browsing or one other app fullscreen use and so the desktop we end up with reflects that. As content creators, how do the rest of us set up their desktops? Should changes be made? or am I really the odd one out? for me as an artists its usually only one, or two windows (e.g. drawing + reference image), and often 2 windows means 2 screens if possible. (at Even with two large apps in two windows, I personally, would like to know at a glance which window is active (has focus). Studio is not a mainstream distro, it is aimed at profesional use, it is really a development flow. The look may be "old fashioned" to some, but that is because "fashion" in DEs has followed use. In the 90s, computers were used to do work. They were designed for the office, either clerk or engineer, and the design reflects that. We have moved since then towards the computer as an entertainment centre where the screen may be the TV (only one window please with no border) or a tablet... I'm so small I can't afford to have anything but one app(let) at a time on my screen. However, Studio is not made for that use, it is made to get work done. We do not need a "beautiful desktop" (to quote one top Ubuntu head), we need a work horse with obvious marking where needed even if it makes things less pleasing to the eye. BTW I am not knocking Mark's statement about making a beautiful desktop. I think he knows his audience, lets know ours too. window etc. :) Usually through if I have 20 windows up, it is because I have been getting distracted and doing 3 things at once (for which now I Yes I often do three or four things at once... I have one workspace dedicated to conunication (like this and browsing). Then I have the main development workspace... but to run Ardour I need a full workspace. That makes two for one project. Then I often need to merge someone elses PR and it is nice to have space to do that without stopping everything I am doing. Working on -controls
[ubuntu-studio-devel] HiDPI (previously: Re: Next cycle)
*nods* GTK2 and java are the 2 major desktop env. independent culprits, from what I can tell, which unfortunately are still around in many applications. Eylul On 04/14/2017 12:32 AM, lukefro...@hushmail.com wrote: > GTK3 itself brings hidpi support to its widgets. That means GTK3 desktops > should support it. I only have 1920x1080 as my largest monitor, but > GtkInspector > allows testing hidpi scaling, with 1.0 and 2.0 times default size options. I > can > verify that this works in MATE for mate-panel and Caja (desktop/folder icons) > though double-sizing everything runs out of space fast on my monitor. > > GNOME (Ubuntu default), Cinnamon, and now MATE all use Gtk3 and should > all offer at least partial hidpi support. Not sure if this works for > everything, and > Gtk2 apps will remain problematic no matter what the desktop environment. > > On 4/13/2017 at 5:10 PM, "eylul"wrote: >> Len thanks for this. A lot of interesting thoughts here. Opinions, >> etc >> ahead. :) >> >>> Auto mounting - we used to make sure there was no auto mounting >> of USB >>> drives, cds or dvds. But since we have started borrowing >> xubuntu's >>> desktop, that has come back in. IMO this is bad for audio use at >> least >>> (anything auto is). However, I realize I am audio centric. How >> does >>> this align with graphics/video use which are in general not real >> time >>> or low latency tasks. >> Yes, it is best for design/art people to have automount (its >> already >> hard to bring design/art people to unfamiliar ground, more >> intuitive >> behavior, the better), turning it off could be a good addition to >> the >> -controls through if it is feasible? If not I think it is worth >> discussing pros and cons and more details on what the problem is. >> If it >> is seriously hindering audio creators, I'll take not hindering one >> side >> in price of being a bit less intuitive to other side. >>> Auto updating - same as above. But to add to it, I noticed that >>> autoupdating installs new kernels in background. However, there >> seems >>> to be no background old kernel clean up. I don't use efi myself, >> but I >>> understand that efi uses a separate boot partition of minimal >> size and >>> could become full with no warning... perhaps making updates or >> booting >>> broken. I would guess this not just a Studio problem... though >> if it >>> is then the solution must be hanging around already. Needs study >> in >>> any case. >> considering autoupdates fixes security issues among other things I >> would >> go with they need to stay. In terms of the kernel issue, I do use >> efi, I >> never ran out of space in that manner until now, but still filing >> a bug >> about this could be useful? >>> whisker menu - I still hate it :) But if we are going to keep it >> (I >>> always go back to the system menu on my systems) can we at least >>> resize it so that the menu categories are all visible by >> default... >>> and enable hover so that click on category is not needed. I >> understand >>> that having the search window there is nice for some people... >> but I >>> just don't seem to come up with valuable search terms ever... my >> brain >>> and whoever sets seach data just don't match. (probably means I'm >>> abnormal) >> My personal disagreement with this aside (I actually use the >> search bar >> to launch a program often) :D I would caution against hover in >> particular as it is a gesture that is inaccessible to touchscreens >> (which are becoming more and more common on laptops). I assume >> this is >> why whisker went with this approach actually. >>> Can we change the default theme to Moheli or similar? There are >> two >>> things I like in a theme: >>> The window with focus stands out - menu bar is a different >> colour >>> The border needs to be wide enough to be easy to grab >>> >>> More than one workpace by default - I understand that I may work >> a bit >>> different than others doing development on more than one project >> at a >>> time. It is not unusual for me to have 30 or more windows open >> at one >>> time. IDEs do try to make things so this is not needed... but my >>> workflow is just that way. This is why being able to resize >> windows >>> and see which is focused are important. >>> >>> I understand that xubuntu is aimed at mainstream either browsing >> or >>> one other app fullscreen use and so the desktop we end up with >>> reflects that. As content creators, how do the rest of us set up >> their >>> desktops? Should changes be made? or am I really the odd one out? >> for me as an artists its usually only one, or two windows (e.g. >> drawing >> + reference image), and often 2 windows means 2 screens if >> possible. (at >> least that has been my experience so far). I need the screen >> estate to >> see what I am doing, more often than not. When doing creative >> coding it >> ends up more of a mess with language references, and code and
Re: [ubuntu-studio-devel] Next cycle
GTK3 itself brings hidpi support to its widgets. That means GTK3 desktops should support it. I only have 1920x1080 as my largest monitor, but GtkInspector allows testing hidpi scaling, with 1.0 and 2.0 times default size options. I can verify that this works in MATE for mate-panel and Caja (desktop/folder icons) though double-sizing everything runs out of space fast on my monitor. GNOME (Ubuntu default), Cinnamon, and now MATE all use Gtk3 and should all offer at least partial hidpi support. Not sure if this works for everything, and Gtk2 apps will remain problematic no matter what the desktop environment. On 4/13/2017 at 5:10 PM, "eylul"wrote: > >Len thanks for this. A lot of interesting thoughts here. Opinions, >etc >ahead. :) > >> Auto mounting - we used to make sure there was no auto mounting >of USB >> drives, cds or dvds. But since we have started borrowing >xubuntu's >> desktop, that has come back in. IMO this is bad for audio use at >least >> (anything auto is). However, I realize I am audio centric. How >does >> this align with graphics/video use which are in general not real >time >> or low latency tasks. >Yes, it is best for design/art people to have automount (its >already >hard to bring design/art people to unfamiliar ground, more >intuitive >behavior, the better), turning it off could be a good addition to >the >-controls through if it is feasible? If not I think it is worth >discussing pros and cons and more details on what the problem is. >If it >is seriously hindering audio creators, I'll take not hindering one >side >in price of being a bit less intuitive to other side. >> >> Auto updating - same as above. But to add to it, I noticed that >> autoupdating installs new kernels in background. However, there >seems >> to be no background old kernel clean up. I don't use efi myself, >but I >> understand that efi uses a separate boot partition of minimal >size and >> could become full with no warning... perhaps making updates or >booting >> broken. I would guess this not just a Studio problem... though >if it >> is then the solution must be hanging around already. Needs study >in >> any case. >considering autoupdates fixes security issues among other things I >would >go with they need to stay. In terms of the kernel issue, I do use >efi, I >never ran out of space in that manner until now, but still filing >a bug >about this could be useful? >> >> whisker menu - I still hate it :) But if we are going to keep it >(I >> always go back to the system menu on my systems) can we at least >> resize it so that the menu categories are all visible by >default... >> and enable hover so that click on category is not needed. I >understand >> that having the search window there is nice for some people... >but I >> just don't seem to come up with valuable search terms ever... my >brain >> and whoever sets seach data just don't match. (probably means I'm >> abnormal) >My personal disagreement with this aside (I actually use the >search bar >to launch a program often) :D I would caution against hover in >particular as it is a gesture that is inaccessible to touchscreens >(which are becoming more and more common on laptops). I assume >this is >why whisker went with this approach actually. >> >> Can we change the default theme to Moheli or similar? There are >two >> things I like in a theme: >> The window with focus stands out - menu bar is a different >colour >> The border needs to be wide enough to be easy to grab >> >> More than one workpace by default - I understand that I may work >a bit >> different than others doing development on more than one project >at a >> time. It is not unusual for me to have 30 or more windows open >at one >> time. IDEs do try to make things so this is not needed... but my >> workflow is just that way. This is why being able to resize >windows >> and see which is focused are important. >> >> I understand that xubuntu is aimed at mainstream either browsing >or >> one other app fullscreen use and so the desktop we end up with >> reflects that. As content creators, how do the rest of us set up >their >> desktops? Should changes be made? or am I really the odd one out? >for me as an artists its usually only one, or two windows (e.g. >drawing >+ reference image), and often 2 windows means 2 screens if >possible. (at >least that has been my experience so far). I need the screen >estate to >see what I am doing, more often than not. When doing creative >coding it >ends up more of a mess with language references, and code and >preview >window etc. :) Usually through if I have 20 windows up, it is >because I >have been getting distracted and doing 3 things at once (for which >now I >am trying to use workspaces and KDE activities) Window focus/menu >bar >aspect is not critical for me in either direction but hard to grab >borders are an issue regardless of how many windows one work with >tbh. >(I have been using
Re: [ubuntu-studio-devel] Next cycle
Len thanks for this. A lot of interesting thoughts here. Opinions, etc ahead. :) > Auto mounting - we used to make sure there was no auto mounting of USB > drives, cds or dvds. But since we have started borrowing xubuntu's > desktop, that has come back in. IMO this is bad for audio use at least > (anything auto is). However, I realize I am audio centric. How does > this align with graphics/video use which are in general not real time > or low latency tasks. Yes, it is best for design/art people to have automount (its already hard to bring design/art people to unfamiliar ground, more intuitive behavior, the better), turning it off could be a good addition to the -controls through if it is feasible? If not I think it is worth discussing pros and cons and more details on what the problem is. If it is seriously hindering audio creators, I'll take not hindering one side in price of being a bit less intuitive to other side. > > Auto updating - same as above. But to add to it, I noticed that > autoupdating installs new kernels in background. However, there seems > to be no background old kernel clean up. I don't use efi myself, but I > understand that efi uses a separate boot partition of minimal size and > could become full with no warning... perhaps making updates or booting > broken. I would guess this not just a Studio problem... though if it > is then the solution must be hanging around already. Needs study in > any case. considering autoupdates fixes security issues among other things I would go with they need to stay. In terms of the kernel issue, I do use efi, I never ran out of space in that manner until now, but still filing a bug about this could be useful? > > whisker menu - I still hate it :) But if we are going to keep it (I > always go back to the system menu on my systems) can we at least > resize it so that the menu categories are all visible by default... > and enable hover so that click on category is not needed. I understand > that having the search window there is nice for some people... but I > just don't seem to come up with valuable search terms ever... my brain > and whoever sets seach data just don't match. (probably means I'm > abnormal) My personal disagreement with this aside (I actually use the search bar to launch a program often) :D I would caution against hover in particular as it is a gesture that is inaccessible to touchscreens (which are becoming more and more common on laptops). I assume this is why whisker went with this approach actually. > > Can we change the default theme to Moheli or similar? There are two > things I like in a theme: > The window with focus stands out - menu bar is a different colour > The border needs to be wide enough to be easy to grab > > More than one workpace by default - I understand that I may work a bit > different than others doing development on more than one project at a > time. It is not unusual for me to have 30 or more windows open at one > time. IDEs do try to make things so this is not needed... but my > workflow is just that way. This is why being able to resize windows > and see which is focused are important. > > I understand that xubuntu is aimed at mainstream either browsing or > one other app fullscreen use and so the desktop we end up with > reflects that. As content creators, how do the rest of us set up their > desktops? Should changes be made? or am I really the odd one out? for me as an artists its usually only one, or two windows (e.g. drawing + reference image), and often 2 windows means 2 screens if possible. (at least that has been my experience so far). I need the screen estate to see what I am doing, more often than not. When doing creative coding it ends up more of a mess with language references, and code and preview window etc. :) Usually through if I have 20 windows up, it is because I have been getting distracted and doing 3 things at once (for which now I am trying to use workspaces and KDE activities) Window focus/menu bar aspect is not critical for me in either direction but hard to grab borders are an issue regardless of how many windows one work with tbh. (I have been using my own window styling in XFCE for a while now so I didn't realize this was still a problem) TLDR, wouldn't oppose switching themes if it will improve usability. I am going to side track here, and say, combined with the previous point, it might be a good idea for us to discuss how EXACTLY we use our desktop and share experiences at some point and even reach out to our users if we get the chance. That way we can hopefully find out what are bottlenecks for a lot of people in terms of efficiency and what are diverging personal choices. :) > > Also in the world of themes. Are there any high DPI or better variable > DPI centric themes available? While I do not use a high DPI monitor > (mine are only 1600X900), I would expect both graphics and video > creators to use them... actually it would be very nice for mixbus-32c > too. SO at least
[ubuntu-studio-devel] Next cycle
Aside from having a new -controls (I hope) there are a few things I would like to hear about. Auto mounting - we used to make sure there was no auto mounting of USB drives, cds or dvds. But since we have started borrowing xubuntu's desktop, that has come back in. IMO this is bad for audio use at least (anything auto is). However, I realize I am audio centric. How does this align with graphics/video use which are in general not real time or low latency tasks. Auto updating - same as above. But to add to it, I noticed that autoupdating installs new kernels in background. However, there seems to be no background old kernel clean up. I don't use efi myself, but I understand that efi uses a separate boot partition of minimal size and could become full with no warning... perhaps making updates or booting broken. I would guess this not just a Studio problem... though if it is then the solution must be hanging around already. Needs study in any case. whisker menu - I still hate it :) But if we are going to keep it (I always go back to the system menu on my systems) can we at least resize it so that the menu categories are all visible by default... and enable hover so that click on category is not needed. I understand that having the search window there is nice for some people... but I just don't seem to come up with valuable search terms ever... my brain and whoever sets seach data just don't match. (probably means I'm abnormal) Can we change the default theme to Moheli or similar? There are two things I like in a theme: The window with focus stands out - menu bar is a different colour The border needs to be wide enough to be easy to grab More than one workpace by default - I understand that I may work a bit different than others doing development on more than one project at a time. It is not unusual for me to have 30 or more windows open at one time. IDEs do try to make things so this is not needed... but my workflow is just that way. This is why being able to resize windows and see which is focused are important. I understand that xubuntu is aimed at mainstream either browsing or one other app fullscreen use and so the desktop we end up with reflects that. As content creators, how do the rest of us set up their desktops? Should changes be made? or am I really the odd one out? Also in the world of themes. Are there any high DPI or better variable DPI centric themes available? While I do not use a high DPI monitor (mine are only 1600X900), I would expect both graphics and video creators to use them... actually it would be very nice for mixbus-32c too. SO at least two themes one for low and one for high, but better one that can deal with making fonts visible at any dpi. Normally artwork changes for LTS releases (next year) but as things move slow here... maybe now is a good time to start thinking about a new backdrop. It would be nice if there could be one that is extensible where a generic version could be used on the right monitor in a dual monitor configuration. I am sure that I have not been plain here :) I am thinking of a left monitor BG that is complete in itself for single monitor users. Then a second BG that looks like an extension of the left but with no logo etc. It may even seem blank or just continue the right edge colours or something like that. Then build the ISO install for a dual monitor setup with those two BGs as default (I don't thnk this would be too hard). If started up in single monitor mode, the system will reconfigure using the left monitor's BG and look right in that configuration as well. -controls will make some changes beyond what it does now and I want it complete and well tested for 17.10 so that we have time to make changes in it and the rest of the system for 18.04LTS. One of those changes will be to upgrade the pulse-jack bridge. The main thing being to allow pulse to run at a higher latency than jack so that the bridge will take less cpu and things like skype will continue to run even with jackd at 16/2. Basically, I want jackd to look like a sound card to pulse. I would like it to show up in pulse's configuration tab for example so people can set it up as more than stereo if they want. But the main thing is that the pa-jack bridge should never cause jack xruns... pa xruns are ok :P pa hides it's xruns already (but not their artifacts) so go with the flow. A PA replacement would be ever so nice, but we don't have a team of coders and 10 years to do that. My goal for -controls is to replace most of the aging qjackctl except the connections window (I may even be able to get -controls to open the qjackctl connections window) and to make it more like Cadence. I would use cadence if it was packaged and I totally agreed with the way it does things. (I am not saying cadence does things wrong... just that I can do better ;) ) -- Len Ovens www.ovenwerks.net -- ubuntu-studio-devel
Re: [ubuntu-studio-devel] check-in and reminder release candidate on April 6th
Thanks Eylul & Len. Just back from my travels and I see the tests are marked ready, and the release notes prepared! I will probably still give the ISOs a spin - probably be a while before the release is official. Will also go over the Release Notes. Cheers, Ross On 04/13/2017 01:26 AM, eylul wrote: > Quick update: behind testing, but the release notes are up. > > https://wiki.ubuntu.com/ZestyZapus/ReleaseNotes/UbuntuStudio feel free > to add, remove, edit, etc to make sure we didn't miss any other changes. > > Also, got in touch with Set about the website, both Krytarik and I have > administrator access, so we should be able to post tomorrow or when needed. > > Thanks. > > Best > > Eylul > > > On 04/02/2017 11:52 AM, Ross Gammon wrote: >> On 03/31/2017 10:36 AM, eylul wrote: >>> I will be around for testing April 11,12,13th, and will be available in >>> chatroom the (european) evenings during that time. Will probably try to >>> do some more tests before that too if I can. >>> >>> I'll also start the notes so that we can all add items on it. (nag me if >>> it is not done by next tuesday). (unfortunately probably not much help >>> on development side tasks). >> Thanks for volunteering for that. It can easily be forgotten in the rush >> of testing the ISO images. >> >>> we should probably also email users ML to see if there is anybody who >>> can help us test there as well. :) >> Done - just now >> >>> On 03/30/2017 01:56 PM, Ross Gammon wrote: Thanks Eylul - you must have read my mind! On 29/03/17 20:43, eylul wrote: > Hi! > > Zesty release is right around the corner and we will have release > candidates out starting April 6th. Where are we with things? Who do we > have available to test the week of April 6th/13th? > > Best > > Eylul I am afraid I have availability problems for this particular release week. I might have some time on the 6th to test the first Release Candidate. And I should be back on the 13th to try and help with the release, but with no guarantee that I will have much time to spare. So it would be great to have some volunteers for testing one or two of the days during that week. Please reply to this message if you can, otherwise we might need to inform the Ubuntu Release Team that we would like to defer our release until after the Easter Holidays. There are also some tasks that I am aware of that we could be doing this week to help prepare for a good release. >> [...] >> Development: 1. Len did some excellent work on ubuntustudio-controls this cycle, but we needed to revert back to something like the state it was at Revision 128. I tried to do this, but may have made some mistakes (r130). It crashed when I tested it, and I haven't had time to get back on it. It may be too late to get a freeze exception for this, but if someone was keen to try. >> Prepared & waiting for the Release Team to confirm the Freeze Exception. >> We should maybe ping them on IRC next week. >> 2. There has been a mass rebuild of the archive, and there are a few build failures of our packages that someone could look into: http://qa.ubuntuwire.org/ftbfs/rebuilds/test-rebuild-20170322.1-zesty.html#ubuntustudio http://qa.ubuntuwire.com/ftbfs/#ubuntustudio Testing: 1. No-one from the team (that I am aware of) did any real testing of the Final Beta, so the Ubuntu Release Team asked that we give the daily ISOs a good bash between now and the release: http://iso.qa.ubuntu.com/qatracker/milestones/369/builds 2. We could do with a smoke test of our important applications. There are test cases that can be used here: http://packages.qa.ubuntu.com/qatracker/milestones/370/builds Testing Please submit a bug if you find something bad, and let us know. Please also record your results if you found no problems, then others can decide to concentrate on untested ones if they are short of time. Bugs: Lots of people have already reported bugs against our packages: https://bugs.launchpad.net/~ubuntustudio-bugs/+packagebugs Feel free to triage some of these bugs to see if any of our packages contain serious bugs, and let us know. There is some advice here for triaging bugs in Launchpad: https://wiki.ubuntu.com/Bugs/Triage/ I hope we can all "muck in" and make it a good release! >> Do we have someone to man the website & blog about the release? >> >> Also, our support for the Ubuntu Studio Trusty 14.04 (LTS) release ends >> with the release of 17.04 (3 years). We should announce this here, the >> users list and on the website ahead of time. >> >> Cheers, >> >> Ross >> > > -- ubuntu-studio-devel mailing list ubuntu-studio-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel