Re: [ubuntu-studio-devel] Upgrade Notifications for Kubuntu and Ubuntu Studio
On Thu, 8 Sep 2022, Erich Eickmeyer wrote: It doesn't, however, solve the problem with the package autoremoval feature that Discover lacks and Update Manager gives. I guess this would be a feature request in the upstream KDE Discover bugzilla. It's a "nice-to-have" and not quite as high priority as a whole Ubuntu/Distro Release Notification. Since /boot has become it's own small partition, I am not sure it is only nice to have as it could lead to unexpected failure of security upgrades. However, blanket autoremove has it's own problems. A dedicated kernel and friends cleanup would be even nicer. Another problem I have found is that none of the current tools I am aware of, remove old /lib/modules/* directories as they often have files in them that have been created after install and so the module package remove will not remove these old unused directories and files. Perhaps this is really a problem with the module packages .remove script. -- 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] Ubuntu Studio: We're out of space
On Thu, 24 Mar 2022, Jonathan Aquilina wrote: Hi Guys, More a long time lurker here and I used to use studio in the past. Wouldnt it be easier to strip everything to bare bones and allow the user to choose what apps to install on first login by popping up the package manager GUI? We already have that option as a one package install that can work with any Ubuntu flavour. This package installs the bare minimum Studio packages and then allows adding various workflow metas to that. However, the reason for providing an image with everything, is to provide: A) An install that does not require network access B) A live image that allows a user to try out just what UbuntuStudio is with all SW. C) A complete install with Studio specific theming and menus D) A live image that can be used stand alone to do actual work. (yes this is a subset of B above) So rather than stripping things to "bare bones", it would make much more sense (if we wanted to abandon having a working live image, I don't think so) would be to provide a "PPA" on a stick... plug in the stick from any flavour, open it in a file manager and run an installer. The image could even be stacked as a second partition on the same stick as the desired flavour image. I guess an image with two paritions would work even easier. However, at that point, just providing a full size image with everything in one partition would be less work and less error prone not only in creating the image but also in creating the USB stick, using it and installing it. Len -- 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] Ubuntu Studio: We're out of space
On Thu, 24 Mar 2022, Erich Eickmeyer wrote: If it's going to only be usable on a USB stick, then let's fix how we build it and avoid all the indirection that exists ONLY so that it can be used on optical media. As 32bit systems are no longer supported anyway, I am not sure there are any 64bit systems that can not load from a USB stick. The only reason I have a DVD player/writer is because I have a PCIe PATA card and the DVD is used for playing media just because of the pain in find blank DVD/CDs and formating data to put it on there in the first place is also a pain. The new full size case my son bought doesn't even have a cd/dvd bay. So anyway, A bootable USB install media format limited only by the USB stick size makes sense to me too. The only problem I see with that (I really don't know if it would even be a problem) is, would current windows/mac based USB stick writing tools still be able to create a bootable USB stick? I am assuming dd would still be able to write the whole image to the stick. I more advanced utility could format the whole stick, making it persistant too, though making it persistant after the fact might be a better route. (I personally have no need for this but the question does pop up from time to time) Len PS this is being written from a 32 bit machine that is no longer Ubuntu but mainline debian... -- 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] Future of Jamin
On Tue, 5 Jan 2021, Ross Gammon wrote: Should we preemptively remove Jamin from our seeds? I assume it's typical use case of taking over mastering from Ardour is no longer important? I have some comments to make: A) I have been told that the DSP in Jamin is substandard, specifically that the eq has large phase errors. B) I have read lists of the tools used in recent projects and found Jamin is still one of those tools in many projects. So the code may be falling apart but people still use it. C) There is not (that I am aware of) a tool or set of tools that can replace Jamin or at least there is not a tool chain that is a well documented for this purpose. So I expect that Jamin will be removed and that is ok. It would be nice if we could come up with a Carla Project File that would include a new tool chain for this use. A tutorial would be wonderful as well (with or without Carla). A quick example but quite old: https://discourse.ardour.org/t/jamin-replacement/85046/3 But really, it would probably be better to have a list of generic mastering tutorials tha talk about processors by their generic name rather than specific plugins. -- 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] Updates from me
On Sun, 22 Nov 2020, Ross Gammon wrote: So far all of my Ubuntu Studio machines are desktop units as I have never had the need to do music on the run (all of my instruments are too big to carry, and I rarely get a project to the mixing stage that can't wait a few weeks anyway). :-) But I would probably use the US installer anyway to overlay Ubuntu Studio so that the possibility was there. I kind of thought so too until someone walked in with their shiny new windows box with a USB 2.0 that would not work cause he didn't have the driver disk... I was able to get the session recorded with his audio device on Ardour in my old 32bit whatever this thing is that I was given as being to old to use. Good to have a backup. -- 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] Virtual Instrument Gap
else's playing. Again my apologies if this is old news. I'm sure musicians have been Not news, just a rant. just feels like Ubuntu Studio is going obsolete vis-a-vis current not-terribly-expensive yet mind-blowing software, especially for keyboard players and music producers. mind blowing? surely you jest. What you mean by "music producers" is companies that wish to spend almost no money by having one anonomous person create a midi track that their chosen singer of the month that sounds just like all the other singers of the month can sing karaoke to. The kind of music I would call a "channel changer". Hobbyists and non-musicians can do a lot on their phones and you can even run a DAW on a tablet. on an iOS based phone or tablet maybe... anything I have tried on any android tablet is so laggy as to be useless. Pro and semi-pro musicians and engineers are going with ProTools or similar without giving Linux a moment's consideration. If incorrect information. I can assure you that almost any movie you have seen in the past 10 years has used linux video software and linux audio software (Probably a version of Ardour in fact). Anyone who uses a digital mixer is using Linux too. There is a difference between PR (protools is the name someone spending money looks for so we have to use this junk to keep the money rolling in) and good software. I will note that Mixbus (Ardour inside) is seeing use by people who normally use reaper or protools as their mixdown software. you can afford a computer, you can almost certainly afford a commercial DAW without the need to change OS. Who is Ubuntu Studio for? There is a problem with that statement. you have mentioned windows many times... yet if you look at the computers on stage and in many studios they are not PCs but a Mac. There is a reason for this. While Mr. Jobs was alive, there was a focus at Apple of making the hardware work better for the art comunity that anythingn else. I can afford a computer, I cannot afford a mac. Nor can I afford to upgrade my audiop interface as often as windows makes the drivers for my audio inteface no longer work (my audio interface cost more than my computer). The "PC" (computer made for windows) is designed to be "low latency" which intel says is 30ms latency. For audio work less than 10 ms is a must which means running the computer beyond it's design spec. With windows, tweaking the OS is difficult at best, impossible in many cases. With Linux this is more straight forward though a degree of knowledge is still required. Is there the remotest hope that more software will come out in three flavors? My guess is the software companies can't justify supporting Linux. Has anyone approached them? Have you? Is there anything on the horizon to solve the problem of running recent Windows/Mac applications, maybe without a bridge? See comment above. If you want to run Mac/windows software, run the OS that it is made for. Do note that things like Ardour and Mixbus which are developed on Linux, come in both windows and Mac binaries as well. The reality is that the desktop computer is dying. The "Chromebook", Android, apple tablets, etc are the future. Apple has stated they are moving away from the intel CPU to an in house ARM based setup... a Chrome book like device with iOS on it. I am sure windows will follow. The cost of doing music on a computer is going to go up no matter the OS of choice, as the number of "computers" being sold goes down and becomes a niche market (is already in many ways). Linux may become the only OS still running on we we call a computer today. I have watched the quality of audio interfaces decline as they moved from PCI and firewire to USB. The harware available to run the software on has also delined... not a bright future. -- 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] Pre-Installed Application Review
On Tue, 12 May 2020, Jacek Konieczny wrote: On 11.05.2020 14:15, Peter Reppert wrote: Len and I have discussed removing the Calf plugins from the default install since lsp-plugins covers the things that Calf can do (and then some), and Calf has a tendency to be prone to crashing when used in Ardour. I don't think that is still true. There were a few problems with Calf and Ardour, but AFAIK all have been fixed. I have not seen such a crash in a long time. And Calf plugins are really nice, especially the 'look and feel'. Worth to keep that. I would think the audio that comes out the back end is more important that "look and feel". The math issues still remain such as phasing in eq, zippering still prevents automating values. So far as I know the reverb can still put out +1000dB signals once in a while. The values on the controls do not reflect what the plugins actually do. However, because of their wonderful look and feel, they seem to be the first plugins mentioned to new users rather than higher quality plugins available. It seems so long as we ship these plugins, they become a "go to" for anyone helping people getting going only to find out later they are not so great really. I would rather answer a few more times why studio doesn't include Calf, that see them continuously recomended as first choice. I see Calf as a "well you can of course install them from the repos but we will not give support if you have trouble with them". -- 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] Pre-Installed Application Review (effective for 20.10)
On Mon, 11 May 2020, Ross Gammon wrote: I thought we had fixed that Ardour crash problem by removing the old version of calf-ladsp that was bundled with lmms? Do we still get bug reports of these crashes? That fixed the crash every time problem :) Calf plugins are built using system gui libs and as such have a shared namespace with other gui libs which sometimes confict and some times don't... when they do they create odd crashes that may not seem connected to the plugin. The devs at calf are switching the gui to their own (static build) gui (all plugins should be static built) which should fix that problem. Anyway, I can't comment if the lsp-plugins offer the same functionality/quality as the calf ones (as I have not used either of them enough). I sure hope not! Quality != Calf. The general comment by professional audio engineers is that the DSP in Calf is some of the lowest quality available. The controls do not do what they are supposed to do, The EQ causes phasing problems, the controls can not be automated because they are not dezippered. The reverb may return a signal that is +1000 dB on occasion. The only people I know who use Calf a lot, do so because they like the sound and are using that artistically. (Unfa for example) However, for straight mixdown use they are the poorest choice available. Ardour already comes with the a-series plugins that includes much of the same functionality. LSP is quite good, x42 is very good, eq10q is a good set, zam is quite good (these are the a-plugins with extras). The dragonfly reverb is very good and being actively developed with the help of clasical recording engineers (who are quite picky I might add). Every time I see someone suggesting calf plugins to a new user, I cringe. -- 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] About video editor - reg.
On Sat, 25 Apr 2020, KR Jesudoss wrote: Hello, I'm Jesudoss. I just asked about video editing software placed in Ubuntu studio. The "Openshot" software which is added to that firmware isn't good enough to do video editing. So i suggest change the editing software which is good and sufficient one. Thank you For some uses Openshot works well enough, Kdelive and Blender are also included for those who need better tools. It is up to the user to choose the best tool for their own use. -- 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] Ubuntu Studio 19.10 and Xubuntu 19.04 and dual quad core Xeon E5335 CPUs
On Wed, 2 Oct 2019, Mike Squires wrote: The short answer here is that if I can use a generic kernel then Ubuntu Studio works across all of the PCs on which I need to run it; the low latency kernel, however, makes using versions 18 and 19 too slow for my needs. The real question is what you wish to achieve with your system. The goals of lowlatency and throughput are not the same. In fact high throughput in general probably makes for poor lowlatency performance. If low latency is not a hard requirement for your use, then install a generic kernel and be happy. Yes it will be faster in some cases with some systems. Or to put it another way, the lowlatency kernel will always be at least a little bit slower than the generic kernel... on some systems it will be much more noticable. So, end of story? No not really. On a single core atom processor running at 0.8Ghz (800 Mhz) the speed difference between generic and lowlatency is really not noticable. It can only deal with rather small packets anyway with only 2G Ram and a smaller data bus etc. One of the ways that a high powered server cpu with lots of cores can be "faster" or have greater throughput (how speed is normally measured) is to use really large packets and more the whole packet at once... however, if you have a high priority audio process that is stopping that file transfer every 128 samples so it can do a very small file transfer before that big transfer starts agian, then that large packet is effectively broken down into a large number of small packets being transfered. Each of those small packet portions may take as long as several packet portions would _if_ they were all sent as one packet because of the overhead of context change etc. "Oh but I wasn't doing audio at the same time as the file transfer". Is that true? is Jack running silently? Even if no client is hooked to jack, if it is running and the packet size is 128 samples, then the device irq is firing every 128 samples without fail anyway. So one way to test this is to A) shut jack off while doing high speed file transfers (does that make it faster?) B) set jack to 1024 sample buffers or higher when it is only being used for listening to youtube. You will notice if you play with it much that hdmi audio has very large buffers as a minimum size. They will not accept 256 sample buffers, they are too small. That is he reason computers are not designed for audio... esspecially lowlatency audio. I have read some of the Intel specs for latency. In those specs "low latency" is 30ms... normal latency is higher. making a PC do low latency audio is hard and in some cases it is not really possible with some hardware. Having many cores should in theory help, but in the end does not as they all have to access the same memory. In a file transfer situation, it is main memory use that counts. Audio too uses that main memory and it has to access it on schedule whithin the time limits the buffersize puts on it. Having said that... thankyou for reminding me... my machine was feeling slow and I am realizing I have the buffer size set quite slow when I don't need it to be. I have been far too long winded on this, but this is not a bug that I can see. I do suspect there are ways of doing things better for high memory, high core count machines but I am not well versed with them. I know setting aside a core or two just for Audio is one of them. I am even aware that some people run a generic kernel on most of their system with a second real time kernel on a few cores. I have never done this and don't know where to look for it. -- 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] New Live Music Control Application
On Mon, 9 Sep 2019, Elias Kesh wrote: In term of licensing I was thinking LGPL, but, open to suggestions. I think that would be ok. For a small Pedal board, I have the source and schematics on github using an Arduino: https://github.com/EliasKesh/SmallMidiExpressioWithButtons The LED's on the stompbox (like tempo) are controller from the app. Cool. I may look into that in a bit as I have some of the small Arduino boards. In terms of setup, I think keyboard players are used to a certain amount of programming before playing. At least this method uses a large screen, real keyboard and is consistent. However, for the less techie group I would think it's a non starter. still probably easier than PD I guess. It would not be too difficult to set up the information (Patches, Tempo) by clicking on buttons and then having the code write into the HTML file. There is already a parser with reads songs files, extracts the meta data and can rewrite them (Comes for changing my mind on formats too much). Ah, well thats not so bad then. I guess I didn't pay close enough attention to the video... it does have rather a lot of information in it. In terms of packing. I already have the debian make system and can build a .deb . However, beyond that I would need some guidance on what is required. I was also wondering if it where packaged as a container, that might make it easier to use. To be included as a debian package you have to be able to first make a src package (unless it is totally scripts and needs no compile steps). This is because it needs to be buildable for various archetectures... and maybe to allow code review more easily as well. If you happen to use autoconf and friends (.configure, make, make - /usr install) that step should be easy. I think cmake is not to hard either. ./waf is much harder I think. -- 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] New Live Music Control Application
On Mon, 9 Sep 2019, Elias Kesh wrote: I've been writing and using this over the last few years and was wondering if there is any interest in open sourcing it . It's written using GTK and WebKit and can control guitarix, sooperlooper, fluidsynth, hydrogen and a few others. I'm looking for feedback and interest levels. Here is a quick overview video. https://youtu.be/Y8flGCnV-j0 Intreresting. What kind of open source licence were you thinking of? Some are more compatable with debian/ubuntu than other. This seems to be a mix of session manager and control application. I have seen people who use such things but I am not one of them because I get confused doing complex real time things beyond playing the instrument itself ;) But for people who do one man band with looping and backing this could be quite useful. I guess it could easily work for taking a MIDI controller foot switch and making a stomp box (a la Mod duo) wth a pi4 or nuc as well. How hard is it to program? some people would have no trouble with HTML programing, others would want some sort fo GUI. I guess we have to ask the hard questions too. What GUI does it use? and will it be maintained? People tend to look is askance at things where there has been no commits for ages (years). How would you host the code? (github, launchpad, etc.) Anyway, I do think it looks like a useful application. I think before we look at packaging it, we would want to see the how the code fits together for ease of packaging... not the make a package that works kind of packaging but rather the making the package acceptable for publishing part (means passes lint at least) It would be too late to have appear in 19.10 at this point, but plenty of time to hit 20.04. -- 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] Package Tracker
On Thu, 8 Aug 2019, eeickme...@ubuntu.com wrote: As I'm having trouble getting RaySession accepted, I might be trying to get Non-Session-Manager in instead. It might take a little more work, but it looks like it would be favored over RaySession. It appears NSM can be edited to use fltk instead of ntk for the gui. While NTK is an extesion of fltk, it appears nsm does not use any of the extensions. Judging from the conversation on #LAD a few weeks ago there was someone who popped in long enough to say they had done it and it was trivial. Writing up a patch to add to upstream may be more difficult... maybe USSM? (ubuntustudio session manger) as a fork... Anyway, I am no good at packaging so maybe that is why I feel patching the upstream is hard. Though it may be that technically changing the gui tool kit is a fork anyway. -- 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] Solution to my problem
On Wed, 17 Jul 2019, Mike Squires wrote: I did notice the following things about "grub": If there is only a 18.04 Studio partition on the disk "grub" does not seem to be automatically installed, and the grub menu does not appear. I tried this twice with two different DVDs, same result. Grub is still installed, but if there is only one OS installed it does not bother to show the menu but rather boots the default kernel. This should be the same with any ubuntu flavour. When "grub" is installing it finds two LINUX kernels to boot but both are labeled as "low latency" when being installed by "grub". Is the second one really a version without the "low latency" mods? The top two kernel entries should be explained (and there is work to change this). There was a problem with installing the lowlatency kernel but it was not A) listed as such and B) if there was also a generic kernel installed, the one with the latest date/time would be the default. At the time, the generic kernel often came out a day or two before the lowlatency so that one was never sure of the boot was generic or lowlatency. Editing system files from another package is concidered bad form and so the way around it was to insert a new file that searched for the latest lowlatency kernel and then put it first. After this the normal code would look for the overall newest kernel and display it in the default fashion... with no idea of what it may be. So the first kernel is correctly labeled as lowlatency. The second one is not labeled at all and is the default latest kernel which may be lowlatency or generic. It is (in a stock Studio install) the same as the first entry. Hopefully, for 19.10 there will be a latest lowlatency listed as default and only if a generic kernel exists will there be a second entry wich will be labeled as generic. Should the user decide to remove the lowlatency kernel then the only entry should be the generic entry... (I know clear as mud, but hopefully clear to the user as implemented) -- 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] Studio 19.04 vs XUBUNTU 19.04 vs dual quad Xeon
On Wed, 10 Jul 2019, Len Ovens wrote: On Mon, 8 Jul 2019, Mike Squires wrote: My desktop is a Supermicro X7DAE dual quad core Xeon (2Ghz), with a 1TB RAID 1 boot device and a single 4 TB archive device running off a 3ware 9750 PCI-E card. A second RAID 5 array running off an older 3ware 9550 PCI-X card is currently off line (drives pulled). Video is a ATI/AMD 5500 PCI-E card. History: Ubuntu Studio (using "Studio) afterwards) 16 ran fine; v 18 was extremely slow once installed, taking many minutes to complete simple tasks. I ran 19.04 but although faster than 18 it was still much slower than 16. I have since switched to XUBUNTU 19 on the same hardware, speed is OK. I do not know the Xeons well. I do know that much of the RT patches that have I forgot to mention: The big difference between what I have and your setup is that I am using an Intel GPU. I would not think that is a problem in this case... but one never knows. I know there are multi processor boards for Xeons... I wonder about a board with an i* and a xeon with the i* doing the desktop and the Xeon doing "interesting" stuff. -- 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] Studio 19.04 vs XUBUNTU 19.04 vs dual quad Xeon
On Mon, 8 Jul 2019, Mike Squires wrote: My desktop is a Supermicro X7DAE dual quad core Xeon (2Ghz), with a 1TB RAID 1 boot device and a single 4 TB archive device running off a 3ware 9750 PCI-E card. A second RAID 5 array running off an older 3ware 9550 PCI-X card is currently off line (drives pulled). Video is a ATI/AMD 5500 PCI-E card. History: Ubuntu Studio (using "Studio) afterwards) 16 ran fine; v 18 was extremely slow once installed, taking many minutes to complete simple tasks. I ran 19.04 but although faster than 18 it was still much slower than 16. I have since switched to XUBUNTU 19 on the same hardware, speed is OK. I do not know the Xeons well. I do know that much of the RT patches that have been added to main line kernel were developed on the Xeon as well as i3-7 processors. And the lowlatency kernel is only slightly different from generic. Still, I would at least try running the generic kernel. Note that the way GRUB works in Studio is the latest lowlatency kernel is listed first followed by the latest kernel (which may be the same lowlatency kernel above it) the only way to ensure the generic kernel is selected is to use the third option which gives a sub menu of all the kernels to choose from. This is a packaging oddity but does insure the lowlatency kernel is default. The other package I would look at is rtirq which may be raising the priority of your mouse and keyboard above your storage system. The settings in rtirq should always be set for the system the package is used with the default tries to be reasonable but I certainly have to change things for no xruns at low latency even with PCI audio cards. With USB audio I need to specify that the physical port the audio device uses has higher priority than any other USB ports. So try disabling /etc/init.d/rtirq by: sudo mv /etc/rc5.d/S01rtirq /etc/rc5.d/K01rtirq Should this prove to be the problem, it should be possible use the same tool to raise the priority of the storage bits to just below the audio device. There is work to replace or suplement rtirq with a more dynamic setup. Our default-settings has been split up in the last cycle so that performance type settings have there own package... I don't know what the package is called but perhaps not using that will also help. The first packages added tend to be installer and controls. Installer only runs when the user runs it. Controls does have a daemon (autojack) that runs from session start to end, but it doesn't ever show in top and normally sits in a wait state until some DBUS event tells it to do something. Jackdbus does use some cpu if it is running and certainly more with lowlatency setting, with latency set to 1024 I see .3%cpu for jack which means about .6% for pulse if it is bridged. I certainly will be interested in your findings. -- 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] Web design/theme contribution
On Sun, July 7, 2019 7:45 am, Shinta Carolinasari wrote: > Hi all, > > > I apologize for the late progress. > We are keep working on it, and here's the latest progress: > http://ubuntustudio.playmain.com/ I am not a visual based person, at least not to the extent most others are here. So take my comments with that context. I personally think this would be great for the next LTS launch with it's fresh new look. The only thing I would change, is to not have "open source" as the first feature. I think linux, ubuntu, and the creative tools we include are beyond that. Now Open source OS, support, and applications are good to use for their own merits beyond just open source. For example Linux is one of the most stable and secure OS available. Ubuntu probably has the broadest support. Certainly one of the largest user bases. Gimp has seem much of it's development in the film industry and has been used in almost every major animated film seen on the big screen for a number of years. Blender is the choice of independent film artists. The same can be said about Ardour which is used as the recording software inside of Harrison's flagship digital consoles used for both large budget film score/sound stage, as well as some top name music artists. Oh and by the way, it is open source too. So open source is great but the tools are also some of the best and that is a reason to use Studio already. Before you make any changes... wait for other comments though. As I said, visual and advertising are not my top abilities for sure. Also note, that my view of the above web page is outside, sitting on a picknick table, in the rain... but under a shelter :) using an "i8" tablet (not apple despite the i in front) That keeps telling me that chrome, google and youtube have stopped... even though I am using none of them. It seems I can no longer use or upgrade playstore either so not the latest or the geatest but barely adequate for email, web pages, and watching youtube... using firefox :) o for what it' worth, Great job so far. -- 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
[ubuntu-studio-devel] A new utility
Some of you may have had "fun" with libremenu or alacart in the past. Both of them are not really usable. Perhaps they try to do too much... But we have spent much time helping people fix what they have done with either of these two utilities. Enter ubuntustudio-menu-add. ( available from https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild ) This can be used to add a missing menu item, change a menu item including its possition in the menu, or even hide it so it doesn't show on the menu. This does not make system wide changes, but only for the user running the utility. From the top: There are two drop downs that allow starting from either a system item or an item you have allready created. Below that is a tex box where the user can type in the name they wish to use for the file. this should be unique. If after typing in the filename and going to the edit screen shows an already filled out screen, that file name is already in use. The name of the file does not have to be the same as the name of the manu item, but likely should be close enough to make sense. There is no need to include the extension of the file (*.desktop). Depending on what state the file named is in, various options will become sensitive (available). If the file is a new one, the only option available will be edit. Pressing edit will open another dialog whitch will ask what name you wish the item to have in the menu, a comment that will show up as a tool tip, the command line to execute, an icon chooser, and other ods and ends. there are only two values that are required: Name and command, but it is nice to fill out the rest as well. If the program is a command line program like top or nano, then check the run in terminal box. When you have filled in enough, the save button will become sensitive. By default, the resulting item will be inactive, normally not what is desired, check the active checkbox to change that, if this is a system item you don't want to appear on the menu (like the gnome software application), uncheck the visible box. By default, a new item will have no categories and may end up in the "Other" folder. However, if you have started with a system file, it should remain where it is unless you change it. The are two dropdowns where you can choose the menu folder and sub menu if that folder has any. It is not possible to add new folders or subfolders and the folders shown are specific to the ubuntustudio menu configuration though they may still work reasonablly well in other situations as well. in the xfce DE as found in ubuntustudio's ISO, using the "settings" folder will make the item appear in the settings applet at the bottom in the other section... perhaps that should be the first bug :) ubuntustudio-menu should probably be upgraded to the new from the PPA as there are changes in there that make folders work a bit better, for example the audio subfolder "Effects" will not work without it. Please file bug reports for anything that does not work or anything that seems missing or anything that works in an unexpected way. Please let me know if you wish to be added to the contributers list if you find bugs etc. so I don't leave anyone out. Let me know how you wish to be reconized as well (name, or nick or whatever). Feature requests are added with a bug report as well. This is very much a work in progress and should be considered Alpha. All file writes are to ~/.config/ (temp file) and ~/.local/share/applications/ where the desktop files are kept... they are renamed *.inactive until they are activated. Removing desktop and inactive files from this directory will return a system item to the way it was before this applet was run. In fact, loading one of these new items and unchecking active will return that item to stock as well. While I am at it, ubuntustudio-controls has changed a lot since 19.04 was released as well, to try out the version that should be coming with 19.10, use the PPA above. all of the same things apply... bug reports please. -- 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
[ubuntu-studio-devel] -controls tweaks
Rather than mucking up the bug comments... Ross, I think that you were the one who has only a USB device. In any case, that should also be fixed as a part of correcting defaults. please check for this. Removing ~/.config/autojackrc should show if th9is is so. you should not have to set up USB as master expicitely it should do that on it's own. The jack master box should sho USB and the USB master box should show your device. In a new install, jack is disabled at boot and in order to start jack the user has to open -controls and select start jack. Start jack will save the configuration and use it to start jack. This should default to using your USB device without you having to select it. I can't test this without taking my machine apart and removing cards and later reinstalling them. Doing this repeatedly will cause problems sooner rather than later as the PCI slots are not high use plugs. -- 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] ISO Tests
On Fri, 26 Apr 2019, Ross Gammon wrote: Hi Len, I have uploaded a new ubuntustudio-controls (v1.8) that fixes things so us-controls starts with the settings from the last saved config file. Your changes in git (mentioned below) did not seem to have been pushed, so unless you were working in a branch, you might have trouble rebasing on my changes. Sorry about that in advance. Over the weekend, I will start on an SRU for disco. Cool, rebase will not be a problem, maybe some work but not a problem. -- 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] Ubuntu Studio Installer on Gnome
On Wed, 17 Apr 2019, Ross Gammon wrote: The second was on Cosmic, and this time ubuntustudio-installer stalled. I see there is a bug (with fix released) to give more feedback of what apt is doing: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/1309536 But without this, I suppose I should be able to dig out some apt logs. I do not think that bug is the same one you are having. Depending on which version you do have, There is at least one version that would hang on the jackd2 install when apt asks for input. I am pretty sure we fixed that also by having -installer pre-fix the file jackd2 is trying to install. So need more info, I guess. -- 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] Ubuntu Studio Installer on Gnome
On Wed, 17 Apr 2019, Ross Gammon wrote: Before I was interrupted by another ISO Release Candidate to test, I had been testing turning the bog-standard Ubuntu install (Ubuntu 18.04, 18.10) into Ubuntu Studio. That is the senerio that has the most testing I think. I have not tested it myself for a long time (cause the gnome desktop does not meet my needs) SO it should work The first freeze happened with Firefox, hexter and qjackctl open on Bionic. Everything froze (mouse unusable), and the only way out was a kill with RELSUB. It is possible I should have done a reboot before starting to play. Possible. -controls does ask for at least a logout and in, but I think there are other settings that are reboot only. The second was on Cosmic, and this time ubuntustudio-installer stalled. What version of installer? (it should be the one from backports) I will look through things a bit later. Wish List - Gnome doesn't have a menu. Yes I know - I don't want to start a flame war and comparison of Desktops :-) Ya thats on my wishlist too. But what is the name of that wierd synthesizer or plugin? Plugins can be partially solved by pinning carla I suppose. But... Wouldn't it be great if you could start the Ubuntu Studio menu from some panel in gnome. Or have some other category based app launcher. I did a search and there are some extensions out there, but nothing conclusive. Meow looked promising, but didn't seem to have a way of loading a configuration for users at install time. Any ideas? I have tried various things on both unity and gnome including adding an xfce4-pannel, which works but does not stay on top and using the addon menu, which we can't ship installed and is broken anyway (doesn't do multilevel menuing correctly, has a broken menu spec file, etc). So far as I can tell, we need A) an gnome panel item that has a menu, B) and indicator (systray) item with a menu. Both of these are beyond my coding ability at this time and (to be honest) not something I am interested in doing anyway as I concider the gnome shell broken for it's lack of menu while the gnome team concider this a feature. This means I don't use gnome shell. I concider people who do should use it as is or switch if it is not suitable. Not trying to be overly blunt or put down anyone, many people do use very few applications and will find gnomeshell a great way to go. -- 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] ISO Tests
On Tue, 16 Apr 2019, Thomas Pfundt wrote: Most of the test cases worked fine, but in my live system and the first boot on the full install, I wasn't able to get any sound with Controls alone. I should ask what kind of Which sound card first off. Assuming the system uses pulse for something before controls is started, Pulse will turn the audio card up... if it knows which controls do this. So my old Delta 66 has never come up on a new install with sound coming out unless I turn it up using mudita24, alsa mixer or qasmixer. It may be reasonable to allow qasmixer to be opened from within controls for this reason. I don't know what exactly the issue was, but I had to reboot once for it to work (it was set to load on startup). Is this something to be expected or should I investigate this further? (I still have the test system installed the way it was.) On first startup, jackd should not be running but pulse should be. Once controls is used start jack, it should be running on the next boot if it was running at shutdown. While my personal opinion, is that the most stable way to run audio is to always run jack as the backend for pulse, there may be those who's main focus is graphics, animation or video and would like to have every bit of cpu possible available for rendering. These people may want just pulse on their system and probably do want hyperthreading and Boost enabled, both of which are bad for low latency audio. (USB is bad for low latency audio as well, but that is what we are generally left with that most of us can afford) So there need to be choices and sane defaults. In the case of jcak starting at session start, My feeling is that in most cases the user needs to set latency and device the first time they run the system anyway (the default device on my system has no speakers hooked to it as it is only used for it's MIDI port) Otherwise, great UI. Very clear and easy to understand. I'd suggest though that it could be helpful to see the current Jack status (running or off), else there isn't a clear response from the start/restart button. Already been changed in git. Controls is under active development (along with installer and soon to be menu_wrecker) -- 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] xfce4-screensaver
On Mon, 11 Mar 2019, Janne Jokitalo wrote: On Sun, Mar 10, 2019 at 04:17:57PM +0100, Ross Gammon wrote: There was some discussion about the use of screensavers in general and it was decided that in the days of flatscreens the original purpose has disappeared, and the fact that in audio and video we might want to watch some rendering/mastering chuntering along for quite a while, that screensavers did not make much sense. I think the power management settings would need to be fiddled with to get the screensaver to work instead of blanking. From my perspective, the point isn't so much in saving the screen, but rather the possibility to lock the session with it. I understand that not everybody have their machines in locations where other people frequently share the space, but I think it's quite a strong usecase to consider, nonetheless. I do realize that every additional piece of software running causes some unneeded overhead, so I'm of course willing to see it opt-in by default. I think any discussion was of the light hearted kind. I do like just having things blank, I do not ever put my machine to sleep but If I did so it would be by user action not time. I also don't expect or ever want some action to happen just because another drive or disk apears. However, all of those things are configurable. Certainly if litelocker is suffering bit rot and/or Xubuntu is moving away from it and there is actually an xfce-variant, we should use it. The DE should be as close to what Xubuntu ships as possible without interfering with audio/video stabillity. The UbuntuStudio iso should install the same way as Xubuntu with a Studio install on top. The only gripe I have with xfce is that /etc/xdg/menus/xfce-applications.menu is "won't fix" (along with gnome and lxde) KDE has it right. The user should be able to change the whole menu layout without admin priv. just for that user. Anyway, rant over ;) it is what it is. (And besides menus are on their way out cause people only use two applications on a computer, the browser and I forget the other one) -- 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] Audio Handbook
On Tue, 19 Feb 2019, Erich Eickmeyer wrote: On Tue, 2019-02-19 at 10:31 -0800, Len Ovens wrote: aside, these plugins even when properly packaged, do sometimes cause crashes in combination with other plugins which use the same GUI lib but different version (gtk2 vs gtk3). My understanding is that the Calf team is working on a GUI toolkit to replace GTK. (GTK or QT should never be used as a plugin toolkit and any toolkit used should be compiled in static) Can confirm: https://github.com/calf-studio-gear/CTK Seems as though Markus has been quite busy lately. Good. There's really quite a combination of problems here, and it is a very touchy subject on both sides. Either way, I feel as though remove Calf altogether and removing it from the Audio Handbook is throwing out the baby with the bathwater. No, don't remove it, As I said their are people who like the way it sounds even if it is not the best sounding stuff out there. I would just not put it down in the manual as my first choice or a preferable choice even. Better to give a list of packages in reverse aphabetical order ;) and let the user choose. -- 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] Audio Handbook
On Tue, 19 Feb 2019, Erich Eickmeyer wrote: The entire problem with the calf plugins stems from bad packaging of the calf-ladspa plugins, which comes in the lmms package and was never meant to be exposed to the rest of th esystem. bacically, Ardour will Not true. Only one of the problems comes from bad packaging. There are others. Some people find the DSP problems artistic though I can't imagine anyone finding 1000db outputs artisitic (or helpful to ones speakers). So DSP aside, these plugins even when properly packaged, do sometimes cause crashes in combination with other plugins which use the same GUI lib but different version (gtk2 vs gtk3). My understanding is that the Calf team is working on a GUI toolkit to replace GTK. (GTK or QT should never be used as a plugin toolkit and any toolkit used should be compiled in static) -- 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] LMMS & Calf: The Ongoing Saga
On Sat, 2 Feb 2019, Ross Gammon wrote: Hi All, The problem with the calf plugin is fixed in Debian! lmms now only recommends calf-ladspa or whatever it was called, instead of Depending on it, which was wrong! So, does LMMS actually work without the calf LV1 package? As in can the user do what they expect to be able to do? If the user has a project that includes the calf plugins, I would assume that project will now be broken and to fix it they will want to install the calf LV1 package, What packages will have to be removed (or will be autoremoved) for that package to install and what other Applications will be broken by this? -- 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] LMMS & Calf: The Ongoing Saga
On Thu, 31 Jan 2019, er...@ericheickmeyer.com wrote: Specifically to Ross: where are we at with this bane-of-our-existence conflict (LP: 1810534)? ISO builds are still failing and will probably fail until we can get lmms from Debian to build properly. Wait for LMMS to stop using depricated plugins? Then include it. -- 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] Possible explanation of my problems with Ubuntu Studio 18.10 and video may require more than 768MB in some cases
On Wed, 5 Dec 2018, Mike Squires wrote: First, it seems that I need at least 768MB and very likely 1GB of memory on the video board to avoid the problems I had with the 256MB All-In-Wonder Radeon board I used previously. Displays are two HD displays; I couldn't display some windows, such as "Terminal Emulator", over the right-hand two-thirds of the second monitor. With a 1GB card, no problem. Ok. That does sound odd. I haven't had that problem with only an i5 using default video (intel on chip) with dual monitors. However, the system was incredibly slow. After login all functions were very slow; for example, burning a DVD ran at less than 1X where the same hardware runs at more than 7x using 16.04. The system was unable to keep the buffers filled, with 16.04 that is not a problem. Yikes! have you tried ctl-alt-F1 from the login screen and do SW upgrade from there? is it any faster? A clue, I think, is that the "wa" (processes in wait state) percentage in "top" stood at more than 30% all of the time; currently running 16.04 on the same hardware it is 0.0 to 0.2%. OK. Running the version of XUBUNTU which is the base for 18.04 didn't show this issue (running from the DVD). Hmm, then maybe try installing the generic linux kernel alongside and run that to see what happens. You may wish to chmod -x /etc/grub.d/09_lowlatency first though so that you don't default to lowlatency. Of course I would really like to know if adding lowlatency kernel to Xubuntu kills that too. It may be something else we do that Xubuntu has found and fixed that we haven't that has caused that... or one of the tweaks we have added besides the extra kernel. My guess is that there is something about the low-latency kernel that causes my dual Xeon quad core to slow down dramatically. I wonder if it That _should_ be faster than my i5 for sure. The fact that you are running an ice1712 audio card suggests that you do audio work where the lowlatency may be important. I should ask anyway, how you use the machine. If you are doing recording with external monitoring and can run with a higher latency the generic kernel may work fine for you. I have purposely stayed with the intel video because I know that the drivers are "open" and just work with most kernels (or get fixed pretty quick). I understand though that the xeon chips just don't have that option. (last I looked) I have next to no experience dealing with other video types. BTW have you tried 18.04? The differences from generic to lowlatency is very small (one switch that can actually be turned on in generic at boot time I am told). -- 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] problems with 19.04
On Sun, 25 Nov 2018, charlie wrote: Hey guys. I started testing 19.04 today and when I began the list of tasks to do, I ran into an error with the audio driver for my laptop. And it looks like jack isn't running because it says [default]stopped, so none of the other tests like creating a beat in hydrogen and listening for the audio playback doesn't work. I'm very rusty in getting everything connected and running so I'm having to relearn as I go. lol Silly me. I'll file a bug report asap. Um, right. We need to change the tests I think. I am assuming you are starting jack with qjackctl. Can you try using ubuntustudio-controls instead? To test if it is running or not use either patchage or jack-lsp (from the cli) Also, if you have have a USB audio device, please start with that unplugged and try running jack on the internal device and then with jack running plug that device in and it should then just show up in jack-lsp/patchage or whatever. I am not saying this is the best way to run a USB device, but it needs testing as much as possible. It should, of course, be possible to run the usb device as the main jack device instead. I haven't D/L or tried 19.04 at all yet, so I guess I should try too. -- 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] New version of Calf plugins (and a failed ISO build)
On Sun, 25 Nov 2018, Ralf Mardorf wrote: On Sat, 24 Nov 2018 13:15:36 -0800 (PST), Len Ovens wrote: I have found that the only problem with Ubuntu is that it is the easiest Linux to access and so gets more newy users than Arch (for example). I have found that more than 50% of all ubuntu user problems are using Ardour/Jack with a USB mic and internal playback. I follow the Linux audio related mailing lists and this month I didn't read anything about USB microphones, there was just a Calf discussion, but there were also other threads, e.g. somebody experienced the same I Certainly there is a difference between mailing lists and irc. The number of people that appear on IRC say "hello" or "help" and then shortly there after vanish is high. There are some who actually ask a question before vanishing but normally within 5 min before anyone might have a chance to say anything. The new generation of computer user does not have the expectation of using email to mailing list and would rather use a facebook like chat interface to talk with someone "right now" when they are hav9ing the problem. So you don't see these people on mailing lists. Of the people who have had problems with more than one audio interface at a time, none of them anounced their problem in those terms. I generally found out that was the problem by remote trouble shooting what looked like another problem. It seems people expect to just plug in another audio interface and use it along with what they already have (something that is now possible since the 18.10 version of controls was released). In general, pro-audio doesn't work that way (with any OS) due to sync problems. macos does handle it (if not in "pro" manner) in much the same way as the new controls does, with SRC on the USB device. I'm an Ardour user and most issues I experience with Ardour aren't caused by plugins. As probably most musicians I'm neither using an USB They should not be if you are using Ardour as comes from a distro and so uses the system libs. mic, nor an integrated audio device. Most issues I experience are saying "as probably most musicians" aren't using USB mics may be true... most new starting audio users are and many more want to use the speakers they already have hooked up to their computer, not hook up something they don't have to the new 2x2 USB audio device they have. One can no longer buy a plain stereo amp of good quality for about $100. Instead they want to sell you a "receiver" for $500 that has no analog inputs anymore of course the new generation doesn't understand audio plugs/lines/levels etc anyway. What most musicians used even 5 years ago does not at all give a good idea of what is normal today. This is even more the case those of limited budget (teens?) who are just starting out. caused by Ardour, it's not nearly as good programmed as claimed. For example, the only reason for dropping my CRTs and buying a LCD display was, that Ardour is unable to provide readable font sizes and at the same time windows that fit into the screen resolution. First I bought an inexpensive LCD display, but soon I noticed that I need an expensive LCD display, so I bought an expensive one. I use $88CAD walmart specials on Ardour with no problem. In general I don't even need my glasses like I do for reading. YMMV... The real problem with Ardour aren't Calf plugins and USB mic users. The Certainly not, I agree. That is why we worked hard to make the use of USB mics easy and almost automatic (plug it in and it just shows up on the jack graph). Linux audio does not handle these situations well (ALSA, pulse, jack, pipewire all included). The new -controls was our attempt at making the audio infrastructure much more PNP. Ardour is not the best tool for all uses but it is one of the top applications in audio. We do want it to work. It would be nice to see zynaddsubfx with it's new gui as well. -- 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] New version of Calf plugins (and a failed ISO build)
On Sat, 24 Nov 2018, Ross Gammon wrote: On 11/24/18 8:32 PM, Len Ovens wrote: On Sat, 24 Nov 2018, Erich Eickmeyer wrote: You all might have notice the "fail mail" we just got for our ISO. This is due to the new version of calf deprecating calf-ladspa per the developer. Ross or Len: Would you mind removing the calf-ladspa package from the seed? I would except, uh... I've never done it. XD That said, I'm very happy to see this progress. 0.90.0 dropped a year ago and was a major change for that package, and 0.90.1 dropped in July as a bugfix. Hopefully this will make the Ardour people happy as well since the old version was messing with compatibility. The ardour people would be happy if this was released to 16.04 - 18.19... don't hold your breath. Getting calf backported to Xenial is not likely. I have had backports waiting for sponsorship for years. Nobody seems interested in backports anymore. Exactly, however, from RG's perspective, he should never have to tell a ubuntu user to remove this or that package or put up with sw where there is an available upgrade upstream. so keeping Ardour devs happy is pretty much an impossible dream. It is best to be aware that RG (at least) does not like ubuntu and assumes any trouble he has with a ubuntu user is ubuntu's fault. I have found that the only problem with Ubuntu is that it is the easiest Linux to access and so gets more newy users than Arch (for example). I have found that more than 50% of all ubuntu user problems are using Ardour/Jack with a USB mic and internal playback. We could provide it in a ppa, (probably also with a new metapackage), and advise those interested in using the ppa that lmms will be removed. The PPA route would probably be best. Alternatively, we could go for an SRU (Stable Release Update) with the Those are more trouble than they are worth and might break someones important project :P best not to. Ubuntu is not a rolling release and people choose it for that reason. I was not sugesting we change things, just trying to explain (badly) that pleasing Ardour devs is not likely so don't worry to much about that. (They would have you remove all Calf plugins anyway) Sorry for the confusion. -- 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] New version of Calf plugins (and a failed ISO build)
On Sat, 24 Nov 2018, Ross Gammon wrote: I was just going to look into that. Thank you. Germinate output shows that it is lmms that is pulling calf-ladspa in: http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.disco/all We will have to temporarily drop lmms. Looking at the Debian lmms bugs, it is possible that a newer lmms doesn't do this (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870473). Need to confirm. It is about time LMMS caught up with the world anyway. ladspa and vst2 are both officially depricated. (Stienberg is even sending takedown notices to devs making new vst2 plugins) LMMS without Calf will look broken to a lot of people. csladspa should also either get updated or dropped aparently the problem was fixed upstream in csound on December 15, 2017. I will drop lmms temporarily from the seed. It is pretty easy to do for We should leave then dropped till they add lv2 hosting support. Anyway, thankyou. I would have had trouble figuring this stuff out. I am not very good with packaging. -- 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] New version of Calf plugins (and a failed ISO build)
On Sat, 24 Nov 2018, Erich Eickmeyer wrote: You all might have notice the "fail mail" we just got for our ISO. This is due to the new version of calf deprecating calf-ladspa per the developer. Ross or Len: Would you mind removing the calf-ladspa package from the seed? I would except, uh... I've never done it. XD That said, I'm very happy to see this progress. 0.90.0 dropped a year ago and was a major change for that package, and 0.90.1 dropped in July as a bugfix. Hopefully this will make the Ardour people happy as well since the old version was messing with compatibility. The ardour people would be happy if this was released to 16.04 - 18.19... don't hold your breath. -- 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] Git seeds (was - jack-mixer)
On Sun, 28 Oct 2018, Ross Gammon wrote: For information, the seeds have been converted to git. The archive and cd-image have now been switched to use git instead of bzr. I am just waiting for the the new "D" name for 19.04, and then we can create the new git branch for "D", and then I will do an ubuntustudio-meta update which is the final place to switch away from bzr. Thanks Ross. Can you confirm (or not) my guesses below: So all changes go into master first? Then cycle branches are rebased from master till release? The cycle branches can be directly changed after release for bug fix? Rebasing current cycle branches would be manual or auto? -- 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
[ubuntu-studio-devel] jack-mixer
As we are doing th9is meetingless... I would suggest adding jack-meter to the iso for 19.04. We currently do not have anything that does this. It is sort of like a simple version of non-mixer (which we also don't have) with no plugins. but it allows a user to mix channels of audio together in jack with individual level control.. -- 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] [ubuntu-studio-users] Fwd: Non-final, but very testable (hint, hint) Cosmic RC builds
On Wed, 17 Oct 2018, Ross Gammon wrote: I noticed that if you click on "Start Jack" or "Stop Jack", the check box for "Autostart Jack for session" is checked and unchecked without me clicking there. Is this deliberate, or should I file a bug? It is not serious. It is that way on purpose with the idea that the next startup should take off where the last one ended. So if jack was running when you shutdown, it shold be running when you login again. -- 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] Fwd: Non-final, but very testable (hint, hint) Cosmic RC builds
On Sun, 14 Oct 2018, Ross Gammon wrote: As you can see below, final testing has started for Ubuntu Studio 18.10 (Cosmic Cuttlefish). http://iso.qa.ubuntu.com/qatracker I you have an interest in helping a good release, then please get testing. Instructions are on the tracker (link above). There will be other builds with fixes, so please plan to test several (or all) nights this week until Thursday (18th October). In particular, ubuntustudio-controls has had the most changes. Please test it to death. -- 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] Vision for 19.04 and beyond
On Sun, 14 Oct 2018, Ross Gammon wrote: With all these changes to seeds, I would recommend converting from bazaar to git before we start. We are the last flavour to do it I believe. I am happy to take that on if required. That would be wonderful. It seems that for the history to be right a number of seeds would have to be added as branches. Or do we start fresh for d*? That is the main thing keeping me from trying. Most of our packages are just master linearly with tags (though branches will appear for bug fixes). They were easy :) (well maybe we did them wrong too). -- 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] Vision for 19.04 and beyond
On Sat, 13 Oct 2018, Erich Eickmeyer wrote: == Meetings == It was brought to my attention that our bi-weekly IRC meetings were hard to make, and I have to agree. Saturdays are a time where I need so spend time with my family, and it's hard do to that when I'm in an IRC meeting for 90 minutes and then have to head to work that afternoon/evening. It was recommended we do a bi-weekly check-in via email, and that seemed to be the most viable option. So, going forward, I will be sending emails to check-in on how we're doing with our projects. OK Since we ran into issues that really need a lot more resources than we have currently, I recommended halting the additional DE iso spins. Instead, I think we should come at this from a multiple-phased approach. === Phase 1 (GOAL: 19.04) === Make ubuntustudio-installer the only package people need to install to bolt-on Ubuntu Studio's tools to their existing Ubuntu (or flavor thereof) install, thereby enabling people to use Ubuntu Studio inside of whatever is their favorite DE. Are we changing the GUI lib? * Modify ubuntustudio-installer to depend on ubuntustudio-controls * Split the lowlatency kernel grub selection settings from ubuntustudio-default-settings into its own package (ubuntustudio-lowlatency-kernel) that depends on linux-lowlatency. I've already done this and will get this synced soon. There are two more settings I would include in that move, swapiness and timer permisions. Swappiness could be something that is useful for graphics/video too (comments?). * Add the ubuntustudio-lowlatency-kernel to the ubuntustudio-audio metapackage, since people who need audio optimization are the only ones that need the lowlatency package. If we do this, I would suggest fixing the grub file so that it gives lowlatency as default like now, but also have generic as the second option and default if there is no lowlatency. Also generic should be labeled as such. Basically the grub hack should get fixed really this should be an upstream thing. If there is more than one kind of kernel they should all be listed and there should be a user parameter that chooses a type for default with fallback should that type not be available. === Phase 2 (GOAL: 19.10) === Too far ahead for me to think about :) but reasonable anyway. -- 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] availability of alternate DEs
On Sun, 7 Oct 2018, Ralf Mardorf wrote: On Sun, 07 Oct 2018 15:27:25 -0400, lukefro...@hushmail.com wrote: Most DE's are designed not to conflict with any other DE Yesno :D, for some more or less exceptional cases, regarding so called major DEs, you and I know better :p. A "conflict" might not be the right term for some issues, users could experience. I would reduce it to switching between window mangers, never does cause an issue, but switching between desktop environments not necessarily does, but always could come with a pitfall. The main thing is user config files which may be the same filename from DE to DE or worse, one DE might expand a user config file in a way another might not understand. Also, if there is a studio specific login and a DE login for the same DE, whichever login you use first will set user configs in the way that login sets up. Most DEs have a DE specific sub directory of .config, but in the case where the DE is just a modified version of another DE... who knows. In general most people pick the DE they want and always use it. -- 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] availability of alternate DEs
On Sun, 7 Oct 2018, jaquil...@eagleeyet.net wrote: I do like this direction things are going to be fair with the below suggestion. Just some food for thought. Let us say i install normal ubuntu. if i install the meta package for kde version of studio obviously the gnome stuff will be removed and then the new KDE stuff will be installed right? Actually no, one can run as many DEs as they would like to. KDA (Plasma) can live along side gnome just fine. There are relatively few conflicts between Studio and vanilla. The kernel while not strictly a conflict does need tweaking to make sure the right one runs if there is more than one. Some of the Codex we install do require the simpler codex package be removed, though that doesn't affect regular desktop use but rather extends it. If we were to try allowing the user to DL and install a different DE at install time, the user would also be able to choose not to install the DE the ISO comes with. -- 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] availability of alternate DEs
On Fri, 5 Oct 2018, Ross Gammon wrote: Is it not possible to install the kubuntu metapackage (or one of them) on a Ubuntu Studio install and then chose the DE when logging in? If that was possible, then we could add a new metapackage to our ubuntustudio seeds that could be optionally installed, and then switch the seeds to that metapackage once we are happy. Probably some of us are just hard of thinking :) That would increase the ISO size by the size of the plasma meta, though the resulting ISO would probably still fit on a DVD (if those are still a thing). DL time would go up yet a again. It would, at this point, be a next cycle thing of course. We would need at least an optional -plasma-desktop package, but more realistically we would need to split -default-settings into -default-setting and -xfce-desktop (replace "desktop" with "settings" if needed). I guess it is possible for the plasma part to be dl and install during ISO install rather than included on the ISO. So there might be a default DE on the ISO, but at install time a different DE could be selected. I do not know how to do that, but the installer already DL and installes non-free packages so there must be a way. -- 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] availability of alternate DEs
On Wed, 3 Oct 2018, Charlie wrote: Erich: understood. would the metapackages include the low latency headers as well? in synaptic search for ubuntustudio-* packages install the ones you want (audio, graphics whatever) but probably not the desktop. Also install linux-lowlatency if you are doing audio work. And install ubuntustudio-controls. Do run -controls at least once to set memory limits and real time priorities and logout and in. I would warn against the the gnome software installer, but the plasma moan (I think it is) is fine. I don't know what -default-settings will do for plasma, but it makes sure that if you have both generic and lowlatency kernels that lowlatency is default. It adds some other audio specific setting (like swappiness) as well. We have been thinking of making Studio an add on rather than it's own iso... Maybe a choice to add Studio or make Studio So install any ubuntu flavour then make it into Studio with that DE: - adds Studio's boot screen - adds Studio's startup graphic - maybe remove generic kernel - make DM Studio specific - make default backdrop Studio specific Or, add Studio - boot screen, startup graphics, backdrops and DE left as is - lowlatency kernel added as default (or user choice via setup?) - audio tweaks added - Studio metas added (as chosen) This would really require an updated -install package I think as well as some extensions to -controls... though swappiness 60 is not really good for any desktop use anyway. Maybe some of the other tweaks we make can be just left in. I don't know how easy it would be to make an install iso where the user DL an iso of the flavour of their choice and the studio install iso... installs the flavour and then installs the studio iso on top choosing option A or B as above (or some variant). This would replace our live ISO and xfce would no longer be "the Studio DE". It would be based on the net iso instead of desktop and would ensure proper install order, proper install user groups, proper jackd install, etc. In the case of installing over a fresh install, the Make this into Studio choice would be default. If the user has logged in at least once since install (~/.config exists) then the Add studio to this flavour would be default. Just an idea... it would be some work to get there... but it would be some work to go anywhere from here. -- 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] Some thoughts, frustrations, and considerations.
On Wed, 26 Sep 2018, ttoine wrote: > After all, the point is to be able to install an optimised system without spending a lot of time searching for all the software, plugins and configurations You can do that with some metapackages, scripts, or even a tutorial. Does that justify the work and energy to maintain a distribution? Maybe this energy could be more useful to help AVLinux or KXStudio? Just questions, please don't see any attack here. avlinux and kxstudio are both good sets of SW. Both are audio only though. However, with graphics/video, adding sw is relatively sane. Audio, where live use is not needed is also quite straight forward, install and go kinds of stuff. There are some places where avlinux, kxstudio and some other ideas just fall down. Tutorials would be a great help for many things such as figuring out how to best use the hardware you already have, be it finding a suitable USB plug or using a USB mic for input while monitoring with onboard audio (neither avl or kx even try to deal with theses things). Studio at least deals with the second, but it would be nice to have some better tools for dealing with the first. Even something that goes through audio devices looking for irq conflicts. I think linux audio still has a ways to go. -- 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] Some thoughts, frustrations, and considerations.
On Wed, 26 Sep 2018, Alexandru Băluț wrote: People from Jack, PulseAudio, GStreamer, GNOME, KDE will meet at the end of October for a hackfest about improving the Linux audio situation. If successful, it seems this will make distributions focused on audio less relevant. There is only one project in those listed that have anything to do with (semi)pro audio. That is jack, I have not heard from the jack developer any meantion of this and so would expect he has not even been contacted at this point. Generally missing from this list are ALSA, Kernel or even pipewire (which is still at the pipedream stage... ie. not yet doing audio) "The idea that we can have a shared infrastructure for consumer level audio and pro-audio under Linux really excites me and I do believe that if we do this right, Linux will take a huge step forward as a natural home for pro-audio desktop users." (Christian's opinion) https://blogs.gnome.org/uraeus/2018/09/24/getting-the-team-together-to-revolutio nize-linux-audio/ Steal coreaudio. Right now it is the best going for pro audio... probably desktop as well. Note that the HW design is part of it. PCs don't have that. What the average user does not seem to understand, is that the average "PC" hardware is not designed for proaudio. The proaudio path starts with motherboard selection... even in a laptop. Lowlatency anything (let alone audio) is not on the cpu/MB developer's mind at all. Any mention they give of low latency is deceiving... low latency = 30ms in their books. Managing to get lowlatency on a PC system (as low as .6ms) requires careful system massage from the kernel to irq priorities to choosing which slot a sound card uses or which USB plug it is plugged into (or adding a dedicated USB card). This is why there are so many chewed apple logos on stage, the hardware really is better. There are more PCs in the studio... because in the studio latency is less important. So changing software alone will not make much of a difference, if treated correctly alsa and/or jack already does what is needed. From past experience, gnome will do whatever they want no matter what anyone says. KDE will listen to their own users (gnome doesn't even do that much). Pulse will continue to work well for desktop audio as making it usable for even basic semipro work would require a complete rewrite... and jack will be ignored. The fact is that the (semi)pro audio community is a very small part of the linux desktop use... and desktop linux is not a large part of the desktop world. Oh, I forgot to mention. Lowlatency or realtime kernels are "slower" or have slower data throughput than generic kernels... and who wants to give up computing speed on their graphics render... in their browser even. So using a normal desktop as is for pro audio is not impossible, but it is problematic. -- 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] Some thoughts, frustrations, and considerations.
On Sun, 23 Sep 2018, ttoine wrote: involved (MOTU and other people like that for Ubuntu). More, in some open source projects, only committers can vote on strategic decisions, and it's bad when they ignore theirs users or don't understand a specific emerging use of their project. That's why many open source project have bad UI/UX, and often, bad communication. I can't remember how much time someone answered to me in IRC "learn how to code and do it"... Yes and no. As an Ardour dev, I have added a lot of stuff that is not useful to me. On the other hand, there are users or just people who like to comment, that have ideas that really don't make sense or that would be bad for the project or really can't be done without rewriting the whole project. When one of these people is insistant that their pet want gets added and won't leave you alone. There is a point of "no I won't add that, build a copy and add it yourself". even as someone who commits to Ardour frequently I still don't have a lot fo vote in it's direction ;) Engineers and technicians don't care that much about their operating system look and feel: they have the head in their applications. They are just looking for a very stable operating system and good devices drivers. Providing a slick dark theme and some nice backgrounds, a setup assistant, and too much pre-installed applications is not anymore what people want. The current need is a lightweight, clean install, and then they just add the few applications they use in their workflow. This is where AVLinux, KXStudio, or even a vanilla Ubuntu with a few modifications (my current choice) are good enough for those who can follow a howto :-) While vanilla is much better than it was... well, it's not my favourite still. However, point taken. By the way, let's speak a bit about the beginnings of the Ubuntu Studio journey. At the origin (I was there...) Ubuntu Studio was a wiki page for vanilla Ubuntu, I came along well after that. (there was a text based installed when I showed up) Regarding the project name, sometimes, I have the feeling that the name "Ubuntu Studio" was a good idea and a bad idea at the same time. In the past, it gave a I remember, but I honestly don't remember how I felt at the time. Working with Ubuntu has not been easy. releases are based on other things than audio and as such we have ended up with releases just before major audio app releases or just before a significant bug fix (jackd comes to mind). This has made Studio instantly out of date. Running a PPA with just metas, an install applet and updates would allow keeping up with such thing much easier. So why not use kx ppa? Some his utilities (cadence) make trouble shooting very hard on IRC or email. (controls current state is because of that) I stepped down from the project after Ubuntu 10.04 for two reasons: I became a father (and it means less time available), and I disagreed with the direction of the project at the time (particularly, the will to add as much packages as possible and focus energy on changing the desktop environment, instead of improving drivers and overall stability). That has (or had) changed. Many packages were removed and the installer had a module added that allowed choosing which apps to actually install. So it was possible to have an audio only (no graphics/video apps) and not include non-used apps even in audio. In my humble opinion, an active website, with a dedicated forum, with section like "Audio", "Video", or "3D", welcoming any users of any Debian/Ubuntu derivative, would have been a key to create an active community. But because of There are linux audio users email lists and formums and they are not doing so well these days either. The linux audio website is suffering from the same dev/maintainer burnout. There is something we must not forget: nowadays it has never been so easy to install a Debian based Linux distribution like Ubuntu, and then add/change a few things to use it as a very good audio or video workstation. Most people actually There some good parts to this too. Having people asking for help about OS related things would automatically go to the flavour they installed rather than our almost empty IRC channel. Whatever is the decision of the current team, to continue or to stop the project, be sure there is no bad decision. Projects start, live, and die. Even if you would choose to stop Ubuntu Studio, parts of it will be used each time someone record music with a Debian based Linux distribution. This is a big legacy :-) I think I will distribute ubuntustudio-controls under another name as well. Just to keep it alive if all else fails... and to make it more usable to those who are not using ubuntu. -- 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
[ubuntu-studio-devel] [LAD] DrumGizmo 0.9.16 Release (fwd)
We should ask for a sync in both debian and then Ubuntu. AVLdrums would be nice to have as well: https://x42-plugins.com/x42/x42-avldrums DG is probably the best drum kit out there, but requires large drum sample package downloads which we do not include (I am not sure they are even packaged) AVLDrums is actually patch on fluidsynth to load one or the other of the AVLdrums kits. It is much lighter to use that DG while still being quite good. DG is for those who must have the best, AVLdrums is for everyone else. -- Len Ovens www.ovenwerks.net -- Forwarded message -- Date: Sun, 12 Aug 2018 12:46:06 +0200 From: Bent Bisballe Nyeng To: Linux Audio Developers , linux-audio-annou...@lists.linuxaudio.org Subject: [LAD] DrumGizmo 0.9.16 Release DrumGizmo 0.9.16 Released! DrumGizmo is an open source, multichannel, multilayered, cross-platform drum plugin and stand-alone application. It enables you to compose drums in midi and mix them with a multichannel approach. It is comparable to that of mixing a real drumkit that has been recorded with a multimic setup. This is mainly a bugfix release. If you encountered timing issues when using the humanizer features of 0.9.15, this is the release to get. It also optimizes the resampling and a bunch of other stuff. For the full list of changes, check the roadmap for 0.9.16 [1]. And now, without further ado, go grab 0.9.16 [2]!!! [1]: https://www.drumgizmo.org/wiki/doku.php?id=roadmap:features_roadmap#version_0916 [2]: http://www.drumgizmo.org/wiki/doku.php?id=getting_drumgizmo ___ Linux-audio-dev mailing list linux-audio-...@lists.linuxaudio.org https://lists.linuxaudio.org/listinfo/linux-audio-dev -- 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] Meeting Agenda 2018-08-11 [cancelled]
On Sun, 12 Aug 2018, eylul wrote: I'd say mypaint and the pikopixel are 2 separate programs for very separate usecases. MyPaint (despite the name) has nothing to do with pixelart, and is a more lightweight and sketching oriented alternative to Krita. :) As I said on chat I think it is a great idea to add it to ubuntustudio. As for mypaint, not sure there is much we can do on short term except removing it and keeping an eye on when it gets updated on debian repos. OK, mypaint is already removed, I think, just so the iso continues to build. We can add pixelart easy enough though. -- 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] Fwd: Updates
On Sun, 5 Aug 2018, Ross Gammon wrote: On 08/05/2018 03:58 AM, Len Ovens wrote: https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1785418 * There are quite a few old bugs. I suspect some of them can be closed. I could do with Len's opinion on some of them first though. https://launchpad.net/ubuntustudio-controls shows 5 bugs. ckicking on "All bugs" gives: "There are currently no open bugs." and when I checked all were invalid, fixed or won't fix already. So I am not sure which bugs these are. That link is to the upstream bugs (project). You need the bugs for the ubuntu archive (source): https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls I see 7 bugs there (including my one for sponsorship). Thank you, there should only be the sponsorship bug left. Those were all old and did not really affect even the current version except for the wayland su bug which this release fixes. I actually had to move the GUI out of su in any case to expand the functionallity as most audio settings are done in userland anyway. -- 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] Fwd: Updates
On Sat, 4 Aug 2018, Ross Gammon wrote: On 08/04/2018 06:29 PM, Ross Gammon wrote: ubuntustudio-controls Also done. Wow - Len has been busy, and Simon did a good job of tidying Thank you. https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1785418 * There are quite a few old bugs. I suspect some of them can be closed. I could do with Len's opinion on some of them first though. https://launchpad.net/ubuntustudio-controls shows 5 bugs. ckicking on "All bugs" gives: "There are currently no open bugs." and when I checked all were invalid, fixed or won't fix already. So I am not sure which bugs these are. -- 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] Fwd: Updates
On Sat, 4 Aug 2018, Ross Gammon wrote: I have taken a look at ubuntustudio-look. It's lookin' good (pun intended). Thank you. -- 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
[ubuntu-studio-devel] web page
Someone left a comment on: http://ubuntustudio.org/2018/06/introducing-the-ubuntu-studio-audio-handbook/ They are not happy that their email appears in the message rather than a nick. If someone could remove their comment They would be grateful. This is something that should be changed in any case. -- 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] hello
On Fri, 15 Jun 2018, Jonathan Aquilina wrote: irc nick on freenode is eagles0513875 now this summer i have a bit of an issue on the 30th of june im getting married and then july im mostly away on honeymoon and wont be back towards the end of july then away for a few days in august. No worry about that. Congratulations instead! This is not a full time gig (and certainly not paying) so show up when you can, but take care of family first. The things I love most about my wife... are also the things I like the least... so it is easy to remind myself when I am upset with something she does that this is probably something I liked too... it's a whole package. So right now meetings are a bit hard for me to be fair. Next saturday i will try and attend. Are you on irc now? yes, am I watching it? no, I am writing email ;) The best way to think about irc is to write whatever you have to say and leave irc running, so long as whoever you are talking to has their irc online, they will write back when they happen to glance at their irc screen which may be in minutes or hours or days. They will answer when they can. If you happen to be watching when they writew you will have some back and forth time. If you can't leave your irc on line, the ubuntustudio-devel irc is logged. So you can see activity when you are not connected: https://irclogs.ubuntu.com/2018/06/14/%23ubuntustudio-devel.html is yesterday's log... you start at https://irclogs.ubuntu.com/ choose your year (latest looks good but leaves you with just today log which may be blank) then choose the month ( https://irclogs.ubuntu.com/2018/06/ for this month). Then you have a list of days. You probably would want to look at yesterdays date first (or further back if you haven't been on for a while and really want to know where things have been). Be aware that the logs are only updated once an hour. This is also a good way to see meetings you have missed. There is nothing you have to do real time... but for some things realtime helps. -- 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] hello
On Fri, 15 Jun 2018, Jonathan Aquilina wrote: I am interested but a bit rusty on python. i would need to setup a VM with studio on it. Already have launch pad account sorted :) as well. I have found that so long as you are running ubuntu or debian with reasonably recent python and systemd, development can be done in whatever your main os is. I wrote most of -controls in 16.04 and am finishing it off in 18.04 and testing in 18.10 only when needed. I would think developing in a vm would be less than ideal because of the extra packages needed just to set up a reasonable dev environment. Having said that, if you are used to working in a VM, you likely have taken care of all those needs already... and I am just full of fluff :) -- 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] plasma desktop
On Wed, 13 Jun 2018, Erich Eickmeyer wrote: On Jun 13, 2018, at 3:10 PM, Len Ovens wrote: I installed Studio 18.10 today and then dropped kubuntu-desktop in on Good info, but why couldn’t we have ubuntustudio-desktop-xfce pull lightdm and have ubuntustudio-desktop-plasma pull sddm? That said, sddm is extremely theme-able and wouldn’t be a bad replacement if we have to go that route. I am assuming that a good percentage of people will choose both DEs. In that case we want the one that works for both. Having said that, I am quite sure I could create a lightdm configuration that would not show the Wayland entry or the plain xfce/plasma entries. It would be similar word to do the same thing on sddm, but if we leave things alone... then if someone installs studio and then installs gnome on top then the login gnome style will just work. Quite honestly, I think we could provide plasma as a DE by changing kubuntu-desktop a very little to give our backdrop and the one tweak for window stacking. I would also suggest removing the Wayland-related package to fix the problem described above. I think until Wayland becomes mainstream, it’s a no-go for us. It would be nice to know where they are. I grabbed the file list for kubuntu-desktop (depends and suggests) and there are no wayland files in there. I think we would have to try blacklisting them one at a time. I do not even know that Studio is free from Wayland related files. dpkg -l | grep 'wayland' when run on Studio 18.04 already gives a long list of wayland stuff. So I think it is stuff we pull in from core. If someone has more time than I do, they are welcome to create a Studio core... but moving away from the ubuntu core would aside from taking a lot of time mean we can't really say "Studio is Ubuntu, try asking that on #ubuntu". Unless we were going to seed two ISOs as previously discussed, because then it would just be a matter of whichever ISO the user picks. Also, an I will create a ubuntustudio-plasma-seed. When I feel reasonably confident about it, someone can find out how to get that to be built :) idea could be to pull a Kubuntu & Lubuntu and switch to Clamares (sp?) instead of Ubiquity. From what Simon has told me, it’s a bit easier to work with. It would be starting over... I think the thing to do is to create two desktop metas, add them to a standard desktop. then if the user chooses to not install either, force install the default or smaller of the two. (or fvwm :) -- 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
[ubuntu-studio-devel] plasma desktop
I installed Studio 18.10 today and then dropped kubuntu-desktop in on top. This pretty much just worked with one exception. After logout I found there were two "Plasma" sessions (as well as ubuntustudio and xfce). On selecting the first of the two and logging in, I found that I had no mouse and no keyboard... I ended up using the reset button. The second "plasma" worked fine when I had rebooted. As happened, while installing kubuntu-desktop I was asked to choose the display manager and because that is what we have been using, that was what I chose. So I went through the packages that get loaded and found sddm was part of it. I found the config screen and switched the DM to sddm. Now there were still two Plasma entries, but one of them was clearly labeled (Wayland)... so ya, Wayland doesn't work. If we are going to add different DEs to studio, we may wish to look into sddm as a replacement for lightdm as it provides a little more info about the session. Quite honestly, I think we could provide plasma as a DE by changing kubuntu-desktop a very little to give our backdrop and the one tweak for window stacking. The bigger thing will be changing the chooser plugin for ubiquity. -- 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] Confirmed! Microsoft Has Bought GitHub for $7.5 Billion | It's FOSS
On Thu, 7 Jun 2018, Charlie wrote: I'm against this deal. I don't like a corporate giant jumping into our open source community and exerting its influence with money. We of the free and open source software community need to be alarmed by this and if any of you have code on github, I'd suggest you put it somewhere else. Linux is about being open github itself was never open source. github has always been a for profit company. As such it could have been bought by anyone. perhaps it has never been a good place to keep open code and this sale has just brought that fact home. -- 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] wacom tablet - was: Meeting Notes 2018-05-26
On Sat, 26 May 2018, er...@ericheickmeyer.com wrote: === Wacom Tablet === The discussion about "Wacom Tablet" started at 20:05. * ''LINK:'' https://github.com/KDE/wacomtablet :) * Erich noted Kubuntu team is working on this package, will collaborate. The package at: https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/experimental Does load and run in cosmic (though it says its for bionic) though I have no tablet to test with... -- 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] The problem with gnome
On Fri, 11 May 2018, Erich Eickmeyer wrote: If we choose to make it default, I propose we go a similar direction that Lubuntu went in for the transition to LXQt by making an "UbuntuStudio-Next" for the additional DE. If not, we could simply make a "ubuntustudio-plasma" and "ubuntustudio-plasma- settings" package and have it available as one of the install options at install time similar to how we do it now with the metapackages. I envision a radio button option between Xfce and Plasma. I think the extra ISO would be a great idea. at least for testing. (yes it has taken me since may 11 to figure this out) having a second seed will help finding which packages (like -settings) need to be split or forked for this to work. I think maybe something other than -next for a name because -next makes whatever is there sound like the cut in stone direction we are taking rather than a trial direction. My thinking is that when we have plasma working well it will either be default or an install choice and we can then use the trial iso to work on MATE and then gnome. It would be nice if all DE things could be in one package per DE. I think we already try to do this, but I am not sure. -- 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] uh oh
On Sun, 20 May 2018, charlie wrote: ok, i've realized that the .iso image i got says DVD and i'm thinking i've got to burn this to a DVD disk instead of putting it on a USB thumbdrive. is this correct? i haven't had this question in a lng time. lol reason i ask is that when i start the process of creating my startup thumbdrive, the program i use, which is startup disk creator, doesn't see the image. that's what got me to look at the file again. That will work fine on a usb stick. dmesg after you insert the USB stick and it should tell what it has decided to call it. ([768617.609134] sd 8:0:0:0: [sdc] Attached SCSI removable disk) As you can see mine turns out to be sdc. then in the directory where my iso is: sudo dd if=cosmic-dvd-amd64.iso of=/dev/sdc this takes a while and does not show activity unless your USB stick has a light on it, so be patient. I can't remember how long my last one took as I don't time it, I ignore it and do other things. Anyway, reboot, I have to hit F8 while booting to get boot device prompt.. I select my USB stick and boot. Note: It is important to make sure you have the right drive as dd will happily print the iso to your system drive over writing whatever is on the first 4 G. -- 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] hey
On Fri, 18 May 2018, charlie wrote: i wanted to let you guys know that i'm in the process of downloading 18.10 to test out. i've got to head over to launchpad and link up with you good folks. what should i look for on launchpad to connect with all of you? and also, is there a website or list of items that need checked on reported on for QA? If testing dailies: http://iso.qa.ubuntu.com/qatracker/milestones/390/builds/172611/testcases gives the three test cases (click on each for a list). If you are logged in to can pass or fail the test and add bugreports on what failed. For post installation: qjackctl should show jack has started in realtime: from the qjackctl main window select "messages/status" and look at the status tab. You should be able to find "Realtime Mode: Yes". Of course checking as many main applications as you can would be nice too. It is particularly nice to check applications you know really well. Any others may well be of a "starts, can draw sqiggle, can save" or can join two videos together or whatever. -- 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
[ubuntu-studio-devel] Font list
Our current font list can be found here: https://bazaar.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/ubuntustudio.cosmic/view/head:/fonts There are some that are included because some application needs them (I suspect t1-xfree86-nonfree is one of them). However, I think all the fonts needed for the DE are included somewhere else. One should not have to install this package for Studio to run. -- 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] Considerations from a video and photo editing perspective.
On Wed, 16 May 2018, argumento wrote: (in case ubuntu studio sticks to GTK). Equilux is a material design based neutral gray theme, it might sound unimportant, but for ppl that do photo or video color correction, having a neutral gray theme is a great help. (idc about 'material design' guidelines, but they work). https://github.com/ddnexus/equilux-theme I know that theme colour is important artwork. However, I am not an artist myself. We have in the past always shipped more than one theme for this reason. Thank you for pointing this out. There are some more artists here maybe they can check this theme for such use. Also, I hate how ubuntu studio comes with a bunch of low quality free fonts, it makes it awkward to browse your font catalog. Maybe having less, but better fonts could help Ubuntu Studio be a better tool (anyway, anyone can get as many fonts as they want from dafont or -better- sites like Squirrel Font or Open Font, so less fonts might be a good way to go). This I agree with even though I rarely do art or even formal text projects which need fonts. However, the few times I have used different fonts, I have fount it difficult to find anything. I have also stumbled on a lot that didn't look very nice. The idea of including lots of fonts was 12.*-ish as I recall. I'd like to share with you a well curated, free font collection, that could be used as a guideline: http://usemodify.com/ If you have time to go through our fonts list in ubuntustudio-fonts and tell me which ones to bump. I would be happy to do so. Also if you know of any others that have a ubuntu packge that should have been added this would be the time. Eric is working on an installer I don't know if installing extra fonts would work from there. An extra fonts button that at least opens a browser at the right place could be done though. Any thoughts? I don't personally have time to vet our fonts. -- 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] gnome vs kde (regarding: The problem with gnome)
On Tue, 15 May 2018, Alexandru Băluț wrote: On 15 May 2018 at 18:51, Len Ovens <l...@ovenwerks.net> wrote: I will say kde does try to make as many things possible as can be imaginable. gnome tends to tell you "this is whats good for you eat it." GNOME is responsible for the products it makes—When one option works and your resources are limited, it's simply wasteful to implement two options. It's not fair to interpret this as "this is what's good for you eat it." That's called good management. Gnome3 from the outset would not run on my resource constrained computer that every other DE would run on (even unity). So not good management, not great use of resources. The above in my opinion is just not true. The team discussed and chose a path and everybody interested at the time had the option to take part. Now the direction is set, and their exceptional focus can be seen in how efficient, clean and elegant GNOME looks. And low possibility of getting any wark done. I fail to see how that can be "elegant" unless I am using my computer for a door stop. I suppose if removing things that help one do work is clean that at least is true. I'm sorry, but I find gnome session next to useless unless I do lots of mods, look for extra modules that do things that any desktop should have built in... even openbox with no DE does a better job at least for getting work done. Now for using a browser and a mail editor gnome is fine... maybe even wonderful. You always have the option to use whatever works for you, if you really need Motif window decorations or whatever. You need to reread what I wrote apparently. I did not suggest we should use motif decorations so much as that some DEs (gnome among them) could learn something from them. When someone works on particular code it is easy to get focused on what that code does. In the case of DE code, it is easy to spend so much effort on making the desktop look nice that the use for the desktop in the first place gets forgotten. That is as a place to run applications and it is the applications that matter. It is true that gnome is fine for the average person that uses their computer for entertainment where they use firefox or chrome and nothing else. To be fair this may even be what most computer users do. However, for content creation where a number of tools are being used to create one product all at the same time Gnome is painful. Studio is not catering to browser users, but content creators. My first impression of gnome session was when is this thing going to load, followed by the realization it was already loaded and the tools I needed had been removed. From what I have seen the way gnome has been fixed from that time is by adding functionallity back in that should have never left. My desktop does not need to be an elegant looking picture that is merely nice to look at. I am not sure what happened to "the user is right" in gnome's mind, but it sure gone. Sorry for ranting, but elegant? Good for limited resources? Ah, no. In the end, I think personal POV has a lot to do with what is nice and what is not nice. The key to these things is configurability. Any DE we have set aside has been set aside for that reason, it is hard to configure to some use other than the DE author's idea of the world. -- 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] gnome vs kde (regarding: The problem with gnome)
On Tue, 15 May 2018, Aleksander Pusz wrote: Forgot to add, for ubuntu-studio one would need colord-kde and wacomtablet however I don't know where to get second one... I wasn't aware they were missing. I did see more tools in settings for monitor colour setup in KDE than in xfce as happens, as well as settings for tablets (the drawing kind). That was one of the pluses of KDE over xfce that I forgot to mention. The trouble we have had in the past is that no one had a monitor colorimeter to test these things with, though I am pretty sure we have people with tablets (and I need to get one for my son). Flat monitors don't change colour as fast or as much as crts (which change with the weather) but they do chnage over time and for that matter are not factory calibrated. (at least not the $90 Walmart specials I use) In any case, I think finding and adding these packages might be something we would have to deal with in any DE. Colord was not in XFCE either and there seems to be no wacomtablet in the ubuntu repos period. There are a number of libs etc. under wacom though. We do include xsetwacom and there is a kcm-wacomtablet somewhere (maybe that is what I saw in kde settings) -- 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] gnome vs kde (regarding: The problem with gnome)
On Tue, 15 May 2018, Aleksander Pusz wrote: I'd like to share my thoughts regarding your post about gnome CSD area development. Please take a look at my bugreport (feature req) here: https://bugzilla.gnome.org/show_bug.cgi?id=791262#c8 However KDE is not saint also, take a look at those two, IMO really important topics secondary being task switcher inconsistency: https://bugs.kde.org/show_bug.cgi?id=378200#c6 https://bugs.kde.org/show_bug.cgi?id=377722 Thank you for pointing these things out. I know that I have blind spots because of my personal workflow. I do not use shortcuts that much except in the terminal I use for remote login where I use screen and any local shortcut means I can't run screen/irssi correctly. However, many (most?) people who use an application for very long find shortcuts the fastest way to work. I was surprised by the comment that gimp "should be run full screen". I never run it that way. In my opinion, an application is allowed to run either full screen or not because people find both useful. Having tool boxes use part of my work area when they could be on a separate screen shows a lack of understanding. Maybe it's possible to push KDE into fixing those two issues, I wasn't able to do this myself... With those two fixed it would be possible to set KDE into very simple and non-interfering interface perfectly suited for Or maybe we can preset some of the settings. I have not found _any_ DE developers willing to fix things even when presented with a pr or diff. Even if they are one line solutions. The open source world is full of religious zealots... I probably can't prove I am not one myself :) productive workflow. I only somehow miss overview screen from gnome... but hey you can't have it all. I will say kde does try to make as many things possible as can be imaginable. gnome tends to tell you "this is whats good for you eat it." As side note I'd like to add, that KDE allows both full-screen switch and this neat option: https://bugs.kde.org/show_bug.cgi?id=383833 It also allows such extreme settings: https://forum.kde.org/viewtopic.php?f=14=141479 The last in interesting, but for me it would break my workflow as I depend on the Tilebars of my apps to tell me which window is in focus: I use focus follows mouse (having had trouble getting focus follows mind working) I do not use raise on focus, I frequently enter text without being able to see the whole window so I can see what the result is on another window I don't want blocked. it is not unusual for me to have as many as ten windows in front of me on two screens In the end I want a DE that is focused on the applications it runs first. I want to get work done, not play with the desktop. I understand (as a developer) how one's own corner of influence tends to become the most important thing. I personally like the window decorations from Motif, fvwm, etc where the whole frame/border of the window changes colour for the window that has focus, each border handle is well deliniated so I can see where a corner handle ends and a side handle begins. These window decorations may not be pretty, but they are designed to show function for good workflow rather than hide the bits that hold things together. While I am not suggesting we go backwards, I am suggesting that desktop design seems to have "lost it's way" in some places. Gnome would be good for kiosk use where the user should only press this part of the screen to get directions to the washrooms and not be able to play with the system. However, as happens, I already know my way to the washroom, thank you. Hopefully this is useful! Please feel free to share this info. Yes it is. It has felt very much like I have been picking a DE. I like to get responses even if they are to the effect that my head must be full of rocks. I do want to add that I can see how KDE/plasma could very easily be configured into a desktop where I would be lost. Gnome tends to start there and is hard to get to a place where work can be done. It is not a bad thing that I could be lost so long as the user feels that things fit. Speaking of window borders, I am not suggesting we set Studio up this way, but does anyone know how to change the border colours depending on focus? -- 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
[ubuntu-studio-devel] De testing
So budgie will probably not work for us. Cinamon also has issues That would be hard to overcome. I have pretty much decided that while tilix has some nice features... I don't find myself using them and the way it deals with the window decoration doesn't allow the theme to do it's work. In general it seems cinnamon does not deal well with themes other than it's own. I found mate easier to use and set up. I also find MATE is better at using standards. I think in the end we will be choosing between MATE, plasma and xfce (or replacing whatever panel with xfce's ;) I will look at lxqt, but expect that at this point it is not yet mature enough for our use. Applications that do away with system theming should die in my opinion, Theming is not just a looks thing, it is a part of the workflow too. Being able to change the theme is important. Having all applications use the theme is important, at least for such things at window decorations. Aside from that, even in the looks department, having one application do it's own thing makes the desktop look disjointed and unprofessional. -- 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] Agenda for 2018-05-05
On Sun, 6 May 2018, Thomas Pfundt wrote: However, the most important consideration is that a majority of users find dark text on bright backgrounds easier to read. A bright background forces the eye to focus and makes edge recognition easier, some people even have serious trouble reading bright text on dark backgrounds, because they experience a glow effect, making the letters fade into each other. There are some studies on this somewhere, but I'm too lazy to look them up right now, they should be relatively easy to find, though. For the most part that is correct. The one glaring exception is terminals that use ansi colours. No one seems to have taken the time to theme every ansi colour to make sure it works against the BG. So in my romp through available themes I would get a light theme and my terminal (I am writing this in a terminal running alpine) the background would go light and the text dark. this is fine... though the letters seem thinner to my older eyes and harder to read, but it is acceptable. However, I then type "ls" at the command prompt and am lucky if I can read half the files in the directory because they are all coloured by type. Ansi colour is from the days of CRTs when VGA was king... but is still in very high use. The we come to graphic manipulation. For someone who is creating graphics colour is very important. Having a big white tool box sitting close to or on top of a graphic does make the colours one is using to paint with harder to visualize properly. A portait studio that uses their camera teathered to their computer would want a mostly dark screen that does not interfere or add colour to their subjects. So whatever the default theme, there needs to included alternatives to cover the workflows Studio includes. Someone doing publishig would probably agree that light bg was best. (though I think such applications tend to force their own theme anyway) In any case, the theme is something that needs testing with a variety of applications in a variety uses (I have had some themes that make it impossible to enter a password in firefox) -- 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
[ubuntu-studio-devel] Thoughts on enabling DEs
This is probably obvious to some of you... but if we were going to install DEs at install time... we had already thought we would need a package for each DE. We also need to be ready for those who install _all_of_them_ This means that probably all our DE metas (even the default) need to have some other name than just ubuntustudio. Ubuntustudio-xfce for example. In some ways it would be nice to do: Install your flavour first then install ubuntustudio loader and run it. -- 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
[ubuntu-studio-devel] testing other DEs
I downloaded and installed Ubuntu Desktop (Vanilla even) and installed it. After mucking about in it, adding some bits... I was able to get something that is quite workable. Aside from the way everything seems to have been gelded and have less options and functionality, if we wanted to make Studio on top of vanilla we could: http://www.ovenwerks.net/paste/screens/Screenshot%20from%202018-04-12%2016-44-13.png There are a few things we would need to add: gno-menu gnome-tweak-tool artwork (but we add that anyway) our menu and config file tweaks the lowlatency kernel and of course our metas. Really this is way better than the last vanilla I tried (unity based) or the last gnome shell install for that matter. However, I have got a newer i5 since then when I had a P4 with 2.5 G and gnome shell would not even run and unity was sllooww as could be. And honestly, when I installed ubuntustudio 17.10 on the same machine it barely runs too. So if we want the biggest support base for our DE, that is probably it. I was told there was a way I could run plain gnome shell from vanilla, but I could not find it and there does not seem to be a Ubuntu flavour that runs gnome shell anymore. If someone knows how I can do that... I will try that also, but in all honesty, if there is not a flavour there to borrow from I do not know that is a good idea anyway. So there are more to test: Kubuntu - as plasma has trouble with some of our applications I am less sure of it. Lubuntu - I was not going to bother as it has always felt unfinished to me but, I hear that they will be switching to lxqt for 18.10 so it will be worth a try for older machines. Ubuntu Budgie - ??? ok, I'll at least try it. Hmm this seems to be a gnome 3 based DE... for the moment. They seem to wish to follow the same path as Lxqt and will be switching over to qt as their GUI code. I don't know if the roots will remain gnome3-ish or not. However, with three people doing most of the dev work and a major change like switching toolkits. Stability may be less than we want. ubuntu MATE - this seems to be top of the list for a number of people xubuntu - we are already there and we know it works. -- 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] Release Cycle for 18.04
On Wed, 11 Apr 2018, Erich Eickmeyer wrote: I’ve been speaking with Simon Quigley and he suggested that, due to manpower, we drop 18.04 from being LTS and just go with a 9-month release for this cycle. Thoughts? This is OK with me. I don't know that it changes anything, wouldn't the packages still end up getting maintained in an LTS manner? It would mean there was no 18.04.3 etc. but that just means a bigger update if someone wanted 18.04 a bit later. In other words whatever packages xubuntu uses would still get updates. The kernel might not as we are the only ones using lowlatency... -- 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] GIMP vs MyPaint - Dependency conflicts
On Wed, 11 Apr 2018, Ross Gammon wrote: I think it would be a good idea to create snaps for our priority packages, and encourage upstream to maintain them. And then if someone wants the latest and Upstream? in most cases won't happen. greatest, they can install it. Adding relevant snaps to our seeds )instead of the Debian package) would be a good test/goal for 18.10. Snaps have some issues for some of our packages. I am not sure how many graphics programs have plugins and how those plugins work, in Audio programs that use ladspa, dssi, LV2 or lxvst plugins, snap instalation will simply not work. Right now we have reasonable support for plugins because we compile the hosts with the same libs as the plugins, snaps would require each application to have it's own copy of all the plugins someone might use. If the person wanted to add a plugin not included with an application they would either have to build both the host and all plugins they use or at least find out what build environment the host uses so they can use the same. I know both gimp and blender also have plugins. At least in those cases the plugins are application specific and can become a part of that application's snap environment. Running jackd in one snap with jackd applications from other snaps may also be a problem. There is already a problem with audio plugins that have been incorrectly built... even if upstream does it correctly, debian tends to break it :P Audio plugins should be built static for the most part. (can't imagine how big a binary that makes when the plugin dev decides to use gtk or qt for their GUI) Two of the offenders in this are Calf plugins and Guitarix. Crashes (and other troubles) are common with both. Many devs have started creating their own GUI toolkits to combat this. -- 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] Release Cycle for 18.04
On Wed, 11 Apr 2018, Erich Eickmeyer wrote: On the other hand, it would be good to have an LTS always available. Many users prefer not to have to constantly update. Our 16.04 LTS will not be supported after April 2019. Ross Yeah, that’s the sucky part. It means taking steps backward as far as being an LTS flavor, but if we simply don’t have the manpower, then that’s where we’re at. Hopefully we can take the next two years to give UbuStu new life and attract help. In the meantime, I think that’s just how it is. :( Erich Does an LTS have to sync with other LTS? Can we have 18.10 be LTS? I am guessing not as support for all 18.10 packages would become our problem :P -- 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
[ubuntu-studio-devel] -controls
Systemd is somewhat of a headache. I have been testing -controls in 1804 and ondemand has been moved to systemd. Not only that, some of the kernel modules don't seem to be loaded before cpufreq runs. I can fix all this stuff but if I do, -controls will be something that works for 1804 but not for 1604. (where the exact cutoff would be I don't know) Any opinions as to supporting older versions in -controls, or should we just go forward? My thoughts are to move forward as we don't seem to do back ports anyway, so Ardour for 16.04 is still 4.* even though active development is on 6.0. I'm sure other applications are similar. -- 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] ubuntustudio-controls
On Thu, 5 Apr 2018, Erich Eickmeyer wrote: This is indeed great news. I think I would favor this over Cadence. What really sets Cadence apart is the Catia component (graphical patchbay), but I guess one could use Patchage for the same interface, even though it is out of development. Maybe it’s time to fork Patchage? I dunno… The answer is Carla I think. It also includes a patch bay. On the other hand, a patch bay on it's own or as a part of -controls would make an ok feature request. in other news with -controls, I have noticed that udev sometimes "resets" even pci/internal audio interfaces sometimes with the result that every interface available gets connected as a client if possible. :) This is really part of the same thing as being able to connect more than one USB device. It is all about keeping track of all audio devices. But hey, baby steps. Things work quite well as they are. I also need to add autojack as a dbus service so that if it happens to not be running, -controls can kick it. -controls should be considered alpha just now. But it works quite well as a proof of concept and probably well enough for someone who has a USB mic they want to use. -- 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] 18.04 & Beta
On Thu, 5 Apr 2018, Thomas Pfundt wrote: On April 4, 2018 8:10 PM, Ross Gammon <ro...@ubuntustudio.org> wrote: The release date is still tomorrow (Thurs 5th April) however. So everyone get testing! I downloaded the 64-bit ISO yesterday and gave it a spin. So far, I've had no major issues, but I noticed that the application-selection screen was missing from the installer. So far as I know that would be a bug... however, the dev who created the chooser is gone and so far with a quick look through our seeds and ubiquity's logs/code I have not seen anything that has changed. Quite honestly I don't know where to start looking. I am not even sure if it was there in 17.10 (I have been quite inactive for some time). Hmm, this looks like the code, not sure how this fits in though: https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-live/trunk -- 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] Saturday Meetings (Was: Sunday Meetings)
On Wed, 4 Apr 2018, Thomas Pfundt wrote: So far, the most promising time for this is every Saturday at 19:00 UTC on the official IRC (freenode / #ubuntustudio-devel). If noone is completely unavailable on Saturdays at that time, we'll schedule the first meet-up this Saturday, the 7th. So that is 1200 PDT not 1000 PDT after all, 1000 would be easier, but we will try 1200 and see. -- 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] Sunday Meetings (was: US still alive !)
On Tue, 3 Apr 2018, Erich Eickmeyer wrote: For the Record: Thomas kindly suggested the following time: I'll just suggest now that we schedule a meeting every Sunday at 19:00 UTC. (21:00 CEST in Stockholm, Berlin, Paris, Madrid; 20:00 BST in London; 13:00 EDT in New York, Toronto; 10:00 PDT in Los Angeles, Vancouver.) Len: if you'd be interested in joining, I hope it's not early for you? Unfortunately. 10:00 (PDT) is a horrible time for me. I work for a church (specifically, audio & video production) and am eyeballs deep in services at that time. If there is another day at the same time, I’m pretty open for that. I am in a similar position, I need to be out the door 15-20 mins before that time and won't be back till 3 hours later at the earliest, 6 if my wife is working and needs to be picked up. -- 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] US still alive !
On Mon, 2 Apr 2018, Erich Eickmeyer wrote: I had started to mangle ubuntustudio-controls in a way that I thought would work best for beginners. It allowed using a USB mic (one of the most common causes of problems these days) by just plugging it in. It handles hot plugged USB audio devices as well as using the internal MB audio along with PCI(e) interfaces. It also allows using the pulse-jack bridge even when jack is set to freerunning. However, I have been too busy to finish it. This would be amazing. I’m not much of a coder, but if you can find someone to hand that off to, or if you could find the time to finish it (at lest to an alpha stage) that would be great. Looking at the what has been uploaded so far will give some idea, there is a build at: https://launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild But I notice no one has updated it to put out 18.04 builds as well. The GUI is pretty close to where I was going, but I have done a lot locally since then. I should probably do a workaround for where I was stuck at for now so it runs :) right now the daemon runs, but the GUI can't talk to it on my local version. (my knowlage of dbus in python is just not there) My proposal would be to move from Xfce to MATE, or even to KDE Plasma now that Plasma 5 has reduced resources compared to the way it was historically. Ideally, we’d present the user with the option at install, but I’m not sure how technically feasible that would be. Either way, it’s worthy of discussion, and perhaps even a survey. gnome3 or mate do not at bother me at this point. KDE however, is broken (won't be fixed) for multi-window applications such as Gimp or Ardour. KDE does not follow standards in the area of window stacking with the result that a window that should be on top may be hidden behind something else. As Studio is a working platform with applications that tend to more windows rather than fewer, such things are important. If someone really wishes to use KDE they can install Studio's metas... at least that way if complaints are made, it is not officially supported and such a user can be refered back to the KDE devs. Maybe if they get enough complaints about not supporting standards they will change. -- 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] Candace
On Tue, 3 Apr 2018, Ralf Mardorf wrote: If a user gets the setup right in the first place, there seldom is the need for cheap workarounds such as a bridge to pulseaudio. Which one is the "cheap workaround" is a matter of opinion. Note, it doesn't matter what distro I prefer to use myself, since I report issues to upstream (real upstream of software, not Ubuntu's upstream called Debian) and I help users using Ubuntu flavours. I don't see posts from Erich Eickmeyer on Ubuntu flavour user mailing lists helping users. This comment is out of place. Please keep your putdowns to yourself. -- 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] US still alive !
On Mon, 2 Apr 2018, Thomas Pfundt wrote: On April 2, 2018 1:15 PM, Set Hallstrom <s...@ubuntustudio.org> wrote: if you feel you want to set-up a meeting you should feel free to go ahead and do so by inviting everyone to attend on a given date in a given chat room. :) I have no problem with setting up a meeting, but I don't really feel qualified enough to curate it. I suppose it would be beneficial to have someone with a clear vision on where to pick things up, in a sense. Just think like you are starting over. Don't be afraid of stepping on people's toes. While I also don't like Cadence that much (last time I tried it was a long time ago), I am picky and don't use qjackctl for anything other the connections window. I have my own script that does what I happen to want. I had started to mangle ubuntustudio-controls in a way that I thought would work best for beginners. It allowed using a USB mic (one of the most common causes of problems these days) by just plugging it in. It handles hot plugged USB audio devices as well as using the internal MB audio along with PCI(e) interfaces. It also allows using the pulse-jack bridge even when jack is set to freerunning. However, I have been too busy to finish it. In short, the things that (so far as I know) keep cadence from being better are: - it does not unload module-udev-detect and module-alsa-card from pulse (required for reliable pulse-jack bridging) - does not deal with hotpluged USB audio - it does not deal with two or more audio devices Another project that would be great to see added to US is https://github.com/jhernberg/udev-rtirq to replace the standard rtirq. The standard rtirq only works at startup and only with devices that are ready before it runs. udev-rtirq gives hot plugged audio interfaces raised priority as well. To add to all that there is something new that will be facing us called pipewire. How well that will work remains to be seen, but the auther at least seems to be talking to the right people and it seems it will not be another pulseaudio replacement that doesn't meet pro-audio needs. (one hopes) Some people have asked about DE. We have since Gnome2 was depricated, used xfce as being the best replacement so far as usablility, stability, light on CPU. Unity has come and gone \o/ and Gnome session has settled down and will likely become the next ubuntu de (? anyone know?) Also, the average used computer has changed in this time as well (the P$ is not common any more) and ubuntu is even thinking of dropping 32bit CPU support. The purpose for sticking to xfce is perhaps no longer there (though it is stil my personal favourite) and moving to something more standard my be something to look at for the next lts (in two more years). Please remember US is a working flavour, not a casual desktop that needs to work the same as a phone. It has many more applications than an email client and a browser and needs easy ways of discovering them all. I personally have not yet found anything as good the old win95 style dropdown menu (which was designed for the work environment). However, also remember that with only a few people helping out, being able to use somebody else to do most of the DE stuff and only add the applications and tweaks on top (in the same way we have been building on xubuntu) is an easy way to go. The DE stuff gets tested by someone else so US can concentrate on the audio/video/graphic parts. Anyway, lots of ideas, not sure which are good or bad... -- 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] Coming Ubuntu Studio Releases
On Thu, 22 Feb 2018, Ross Gammon wrote: Ubuntu Studio 18.04 Final Beta: April 5th. I should be around for that. Ubuntu Studio 18.04 Final Release: April 19th - 26th. I will not be available for that (due to work). Who is around to help testing for the first 3? I will try to be. Should we release 18.04 at all? I would say yes. There is enough with just application upgrades to make it worthwhile I think. The other end of it is that if 18.04 is not released, it is probably not worth keeping Studio around at all. 16.04 is already too old in many ways... the big thing is that developers of some of applications Studio ships are getting bug reports on issues they have fixed years ago. Unless someone has the time to step up and steer this beast, I think it is finished. -- 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] Fwd: Bug#888657: ladish: should this package be removed?
On Sun, 28 Jan 2018, Ross Gammon wrote: It is very likely that ladish/gladish will be removed from the Debian archive soon, as it is not maintained upstream, and needs to be ported away from GTK2. Whilst we can probably keep it a little longer in Ubuntu, unless someone steps up to take over maintenance (and do the porting work), it will be lost eventually. Best to let it go. The current maintainer has suggested that it will not be updated and deserves retirement. The New thing in session managers is NSM... also not being taken care of and not in the debian repos anyway. -- 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] ubuntu-studio-devel Digest, Vol 127, Issue 5
On Fri, 17 Nov 2017, Ross Gammon wrote: If you are interested in understanding the build process for the Live CDs/DVDs, you can try building them locally. There is some information here (with further links): https://wiki.ubuntu.com/UbuntuStudio/SetupLocalIsoBuildServer Maybe I will ask on Ubuntu Devel for help to get some simple instructions? Your link above actually seems pretty simple and straight forward. It looks like things have changed since I last tried. I could get chroot directory with all the sw on it, but getting it to the ISO stage seemed to take a number of steps that didn't work for me. That link shows one script. To be honest, I would rather spend my time getting -controls ready but have been busy... -- 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] ubuntu-studio-devel Digest, Vol 127, Issue 5
On Thu, 16 Nov 2017, Ross Gammon wrote: If you are interested in understanding the build process for the Live CDs/DVDs, you can try building them locally. There is some information here (with further links): https://wiki.ubuntu.com/UbuntuStudio/SetupLocalIsoBuildServer I have tried... but I have never gotten an ISO out of the deal. There does not seem to be a script that just does it all... well there must be because the ISO are built automatically, but the script does not seem to be available. Be nice to cd ~/some_directory; make configure --$arc; make Or something like that. I should try again though, that looks easier than whatever I tried last time. -- 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] Carla
On Mon, 2 Oct 2017, Ross Gammon wrote: Over the weekend, I started to look at packaging Carla. It has a LONG way to go to comply with Debian policy, is missing some functionality due to missing dependencies, and it also fails to build on 32bit, but you are welcome to install and test my WIP (Work In Progress) here: https://launchpad.net/~rosco2/+archive/ubuntu/new Cool. How does it mess up debian policy? Does it just depend on the wrong things or is it deeper than that? It is very acceptable not to include Linux Sampler either as a dep or anything else. In fact if all we get is the rack that loads plugins and the plugin that loads other plugins, it is well worth it. Being able to load win-VSTs while nice, is not required for a first go if we can get it into the repos without. I haven't actually tested it myself yet, so don't try it on a machine that you depend on. It is only built for Artful and so while I could boot that up, I can't test it my normal workflow on 1604. Not that I use Carla or plugins that require it on a regular basis... :) -- 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] Ubuntu Studio Artful - Debian & Feature Freeze
On Tue, 29 Aug 2017, Ross Gammon wrote: On 08/29/2017 09:30 PM, Ross Gammon wrote: In fact, I was playing with it on Sunday, but it looks like I have no cpuFreq driver installed, so it didn't work for me (the governor in performance bit). But reading a wiki just now, I see that the driver is supposed to be loaded by cpufrequtils. So either the init script is not working for me, or I need to do a reboot. I will play some more in a minute. A reboot does not fix it. I may have run into something like this bug: https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/1084262 More investigation required. Unfortunately I have to sleep now. I am not sure, does -controls have a dep for cpufrequtils? It has worked fine for me so far... I guess I need to try it on 17.10 as well. Make sure you have cpufrequtils installed (it is not by default). -- 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] Legacy Support
On Sun, 30 Jul 2017, Helios Martinez Dominguez wrote: There should be a way to provide x86 support natively while providing x64 upgrading on the go as detected, as needed or as stated. It would allow to remain We already do provide both 32 and 64 bit ISOs. Putting both on one ISO would pretty much double the size of an ISO that is the biggest ISO of all the Ubuntu ISOs. Last I checked, UbuntuSTudio did still load and work on well over 10 years old computers so long as they have at least 1 Gig ram (though more is needed to make the best use) There are enough people who rely on a machine not connected to tyhe internet to make on the go installs not practical. lighter ISO's, support legacy hardware with lower performance than commercially available and upgrade to a more recent configuration as required. I would like to configure such code myself as i consider i am a great developer and could (and should) provide myself with such requirements as needed, yet my knowledge on the procedure is poor at the time and it would take longer to study and practice all the way through the learning process than to proceed to ask for someone else who does knows, works and relies on the procedure on a periodic basis. As such, i formally ask the development team to address my request into such matter, as possible. Thanks in advance. Good day. Please make yourself available to take on this task. Asking a few people with hardly any time to take on yet another task just means most people will just hit the delete key on this mail and get on with life. Really you should at least make yourself familiar enough with the process to know how much work you are asking "someone" else to do for your system and maybe not many others in their spare time. The Ubuntu kernel and repository maintainers are already asking us to drop support for 32bit systems... and some of our main applications are no longer 32bit compatable upstream by the application developers either. -- 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] Ubuntu Studio Controls
On Sun, 23 Jul 2017, Len Ovens wrote: Two different things completely. The RT setting in -controls only shows up if jackd2 has not been properly installed. So it would not show up on a UbuntuStudio install (unless it is broken). it is there for people who install jackd2 or the Studio metas into another flavour and it ends up not installed correctly. clicking on the button corrects the install so that audio applications have RT access. The button in qjackctl only tells jackd if I should point out that there is probably never any reason to reverse this process. It will have no effect on any non-audio application. There is the slight possibility that with a true RT kernel (which we don't provide) a bad application could use _all_ cpu time available locking the computer up as far as the user is concerned. However, our lowlatency kernel saves at least a little time for the system to work. I don't know of any packages with a bug like that. It also fixes the use of some audio packages that use alsa directly such as Ardour with the alsa backend should anyone try to do that. That is, installing Ardour without installing jackd will not work even if the user never intends to use it with jack. Using -controls to fix rt will allow Ardour to run without jack installed. (I suspect Ardour lists jackd as a depnds anyway, but it can be downloaded from ardour.org too if the user wishes to keep up the latest version ... 5.10 these days) -- 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] Ubuntu Studio Controls
On Sun, 23 Jul 2017, Ross Gammon wrote: Hi Len, I just successfully installed an Artful 1704 VirtualBox VM this afternoon, and installed the daily build of ubuntustudio-controls (https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/12643119) to test out the graphical bits. It is all looking great! Some comments: 1. In the "help", I am not sure of the "if requested" wording for the realtime setting. I have not yet redone the help dialogs. I have removed someout of date things and that is about it. 2. To test out what might be meant by that, I thought I would fiddle with the realtime setting. But it is no longer there! us-controls tells me that RealTime is enabled. If I fire up QJackCtl, and untick RT there, Two different things completely. The RT setting in -controls only shows up if jackd2 has not been properly installed. So it would not show up on a UbuntuStudio install (unless it is broken). it is there for people who install jackd2 or the Studio metas into another flavour and it ends up not installed correctly. clicking on the button corrects the install so that audio applications have RT access. The button in qjackctl only tells jackd if it should try to use RT mode when it runs. You should not have to use qjackctl to start jack if you use -controls. However qjackctl when started will show jack as already running and will allow connecting jack clients together. and closing QJackCtl & us-controls). I see from the README that I probably should have logged out. Should the help dialogue mention this? If you need to log out and back in, -controls should have a red message suggesting this. Note: all of this is done without Jack actually started (as I was too lazy to choose higher later latency settings in the VM & to test a reboot). unless you changed some -controls settings it is possible jack was running... not sure how VMs deal with reboots. The default is to use jack as the audio server with pulse as a frontend. On my system (and my wife's) this is invisible to the user. ie. it just works. It does not seem to use extra CPU, pulse uses a bit less in some cases. 3. As you can tell, after all this time I am still a bit of a Linux Audio noob. Which brings me to documentation. I assume the README & documentation, aside from being one of my weak points, has not been started. (packaging is also a weak point for me, but I should learn at least enough to package my own SW) So yes: ROADMAP files need updating. You should probably add yourself to the AUTHORS too! https://help.ubuntu.com/community/UbuntuStudioControls has needed an update for a long time. There used to be a manpage (http://manpages.ubuntu.com/manpages/trusty/en/man1/ubuntustudio-controls.1.html) which references https://wiki.ubuntu.com/UbuntuStudio/SettingsApp which is wildly out of date. I suppose the manpage is only really needed if users might try and run the scripts from the terminal. The us-controls launchpad page has a link to a wiki which doesn't exist (http://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioControls). There is a useful links section at the bottom of https://wiki.ubuntu.com/UbuntuStudio/ControlsRedesign which probably contains some documentation to assist with producing a new wiki page. Are there any others? I don't know. Next I will upgrade the real hardware machine in the basement, and give it a proper spin. Cool -- 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] Fwd: Artful Aardvark Alpha 1?
On Thu, 22 Jun 2017, Ross Gammon wrote: Hi, As we are not yet ready with ubuntustudio-controls, probably Alpha 1 is not much use to us. Any thoughts? Has anyone tried -controls? (besides me) -- 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] https://
On Fri, 2 Jun 2017, Ralf Mardorf wrote: I attached a script to download 64 bit architecture Ubuntu desktop flavours, with an automatic check against signed checksums. After making the script executable running ./luamd64_1610.sh ubuntustudio 16.10 ./luamd64_1610.sh ubuntustudio 17.04 zsync also auto checks against the checksums, with the added benefit it will only download the chunks you don't already have. It does require the url of the zsync file though, so less easy to use. -- 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] Our website
On Wed, 31 May 2017, Jonathan Aquilina wrote: One thing that wasnt mentioned here. If you guys use google chrome, and im not sure if chromium supports this but have you all noticed the browser shows you if a site is secure and using https or not? It seems like they are cracking down on http based sites. Actually, https://ubuntustudio.org is there... just that http://ubuntustudio.org is not redirected there. -- 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] Our website
On Tue, 30 May 2017, Hank Stanglow wrote: use https. I just did a nmap of ubuntustudio.org and see that it's running Apache 2.4.7 on Ubuntu which I believe means 14.04 (Trusty). Setting up Let's Encrypt on 14.04 is a bit of a hassle. I tried it for a few days before As happens I have set up letsencript on 14.04 and found it easy. I use it for squirrelmail, but having read this, I will probably move the rest of my web pages into https as well. -- 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
[ubuntu-studio-devel] Our website
I had this conversation on IRC. Anyone know if this is a problem? My web understanding is old. - 06:11 < mchelen> any reason why ubuntustudio.org doesn't default to HTTPS? 07:56 < OvenWerks> mchelen: no idea. 09:15 < mchelen> OvenWerks: it's not great security practice, given that there are links to .iso downloads (which are also HTTP) 09:50 < OvenWerks> mchelen: that may be true, however, web page setup is not my thing. I am not sure who is doing web stuff right now. 09:59 < mchelen> OvenWerks: ok, yeah I wasn't sure where to create an issue or anything 09:59 < OvenWerks> mchelen: do you know if xubuntu's site is any different? I think the same person worked on both 10:01 < mchelen> OvenWerks: visiting http://xubuntu.org correctly redirects to https 10:04 < OvenWerks> mchelen: I will drop this coversation on the dev mailing list and see what comes from it. 10:36 < mchelen> OvenWerks: ok thanks! hopefully its just a matter of creating a redirect -- My understanding, is that https is useful when personal info is shared over the net. ubuntustudio.org is, so far as I can tell, one way. That is, we provide info/files and the user DL them, they do not sign in or give comments or anything. Am I missing something? -- 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] ubuntustudio-controls
On Thu, 25 May 2017, Ross Gammon wrote: I also see that Len has been busy and pushed his latest work: http://bazaar.launchpad.net/~ubuntustudio-dev/ubuntustudio-controls/trunk/revision/133 Actually up to 140 now... and ready for some testing. I have a few GUI tweaks but the functionality is where it will get to for now. If you want an easy way to try it it, debs can be found here: https://code.launchpad.net/~ubuntustudio-dev/+recipe/ubuntustudio-controls-daily ubuntustudio-controls pre1.5 (140) is available for testing. The audio section is mostly complete. Auto connecting hot plugged USB devices does not work at this time. (meens I have not yet started on it) The GUI is still getting tweaked... it will be 1/4 (or it is 1/3 bigger now) smaller tomorrow. Giving full names to the audio devices expanded the GUI width quite a bit. I am trying to make the GUI easier to understand :/ not my best thing. I have already added some text to add and remove (Add (Available) and Remove (Connected)) The Apply button can be either renamed to "Save settings" or it can also do a jack restart. Things to try: create a new user and make sure you get a big red warning when starting -controls as the new user. click the fix button and the message should change to tell you to logout/in. Logout/in and the red message should be gone. This should work on another flavour even if jackd is not installed. The USB auto connect will be interesting, but I need to do some work on autojack first so it responds to: autojack start/restart/stop/reconfigure -- 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 Sat, 20 May 2017, eylul wrote: out of curiosity through, is there a way to automount without starting a window regardless, because it is a bit annoying. The options are: Mount Removable Drives when hot-plugged Mount removable media when inserted Browse removable media when inserted Auto-run programs on new drives and media Auto-open files on new drives and media I thihnk I need a manual to figgure out what they all mean. I am not sure what the difference is between "drives" and "media", unless drives are media with a known mount point in /etc/fstab or internal drives. Anyway, I think browse is the "avoid me" in this lot. Auto-run and Auto-open also look bad. I can't remember which enabled at install though. -- 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 Sat, 20 May 2017, eylul wrote: cron based updates where you can set up the time, and reminders about system being out of date. All of these are good ideas. The reminders are already there. Turn off your updates for a week (less?) and you will see that there are reminders. (I wonder how I knew that ;) -- 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, 19 May 2017, Ross Gammon wrote: On 05/17/2017 12:38 AM, eylul wrote: Disabling auto-updates should NEVER be the default, period. It would leave users system vulnerable to attacks. Strongly dissagree on that one. Auto updates are performed on no real time schedule and often happen while the user is trying to do something. If auto updating _must_ be done then it should be moved to cron and the user should be asked to choose the time. If autoupdates are turned off, there _is_ a warning Icon that shows up in the top bar that says "hey you haven't updated for a while would you like to check for updates." That is good enough. The user can choose when that happens. This also avoids the "hey I need Chromium so a can join a meeting on hangouts but I can't download it because some other process is up dating my system for some unknown amount of time." Fair enough (considering there are other use cases for US than audio work). Auto update can be anoying no matter what kind of work is being done. It slows compile times, graphic render times (so video too) and introduces those "it works most of the time but every once in a while" kinds of bugs. Users can turn off the auto-updates if they want to.(Go to "software" -> "Updates". You can change how often the system checks for updates, it currently only downloads and installs automatically security updates, and displays the rest.) Advanced users can make that choice. It is not ours to make. It is very much our choice to make. High disk/network/cpu load activities should _never_ be run without user request on a work machine. The user should have to work hard to screw up their system, it should not be done for them (automatically). Well - I prefer to check what the updates are before installing them. Sometimes, they can be quite disruptive (e.g. temporarily disabling something). It might be better to pull the internet cable out instead ;-) Yup, one more reason for no auto updating. --- In thinking about auto mounting of media I realize that we probably don't need it. Automounted or not, the devices icon shows up in the file browser anyway... so what does automount gain besides opening a new window in the middle of things? Does it improve a workflow? -- 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
