[ubuntu-studio-devel] Feature Spec Discussion: Artwork - community wallpapers
We need to establish a way for the community to contribute wallpapers to our releases. How do we do this? Any ideas? -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, May 21, 2014, at 12:49 PM, Kaj Ailomaa wrote: Out of the current packages available, I'm thinking: # audio plumbing and tools jackd a2jmidid alsa tools and utils (alsa-tools, alsa-tools-gui, alsa-utils) ffado (ffado-tools, ffado-dbus-server, ffado-mixer-qt4) pulseaudio-module-jack gladish # ubuntu studio kernel linux-lowlatency (already depends on rtirq-init) rtirq-init # midi essentials vkeybd midi tools (gmidimonitor, qmidiarp, qmidinet, qmidiroute) jack zita-ajbridge Possibly also jack-rack and a small selection of great plugins? I forgot to add ubuntustudio-controls, which when it is rewritten and made functional will be one of our core components. -- 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] Ubuntu Studio Release Schedule - Google Calendar
Here are the three address links to the Ubuntu Studio Release Schedule I've set up at Google Calendar: XML - https://www.google.com/calendar/feeds/official.ubuntustudio%40gmail.com/public/basic iCal - https://www.google.com/calendar/ical/official.ubuntustudio%40gmail.com/public/basic.ics html - https://www.google.com/calendar/embed?src=official.ubuntustudio%40gmail.comctz=Etc/GMT I will try to remember to put in anything relevant to any Ubuntu Studio release in this calendar, so not only the current development release, but also our stable point releases. All dates for Utopic are set. They are not written in stone however - not all of them, anyway. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, 2014-05-21 at 14:43 +0200, Jimmy Sjölund wrote: So what would you do after installation? In my world I need an application to record something, otherwise I don't know what the use of the iso is? For what usage? To record audio only, to record MIDI only, to record audio and MIDI? Etc. pp.. A core editor should be something like vi, nano or similar, that doesn't mean that for some tasks Sublime Text might be a much better editor. Core is for something that is needed as a base and that it's something that maintainers should keep stable whatever happens. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, May 21, 2014 at 3:03 PM, Ralf Mardorf ralf.mard...@alice-dsl.netwrote: On Wed, 2014-05-21 at 14:43 +0200, Jimmy Sjölund wrote: So what would you do after installation? In my world I need an application to record something, otherwise I don't know what the use of the iso is? For what usage? To record audio only, to record MIDI only, to record audio and MIDI? Etc. pp.. A core editor should be something like vi, nano or similar, that doesn't mean that for some tasks Sublime Text might be a much better editor. Core is for something that is needed as a base and that it's something that maintainers should keep stable whatever happens. Maybe I'm missing something, but why would then plugins be included? -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, 2014-05-21 at 15:06 +0200, Jimmy Sjölund wrote: On Wed, May 21, 2014 at 3:03 PM, Ralf Mardorf ralf.mard...@alice-dsl.net wrote: On Wed, 2014-05-21 at 14:43 +0200, Jimmy Sjölund wrote: So what would you do after installation? In my world I need an application to record something, otherwise I don't know what the use of the iso is? For what usage? To record audio only, to record MIDI only, to record audio and MIDI? Etc. pp.. A core editor should be something like vi, nano or similar, that doesn't mean that for some tasks Sublime Text might be a much better editor. Core is for something that is needed as a base and that it's something that maintainers should keep stable whatever happens. Maybe I'm missing something, but why would then plugins be included? The more you include to core, the harder is to ensure that it's stable. In FreeBSD, the term “world” includes the kernel, core system binaries, libraries, programming files, and built-in compiler. User space for BSD and Linux based systems is another issue. Core components are basal stuff. For audio the interpretation of core components is something like alsa and jackd, but regarding to a core *nix install even those aren't core components. As an analogy I mentioned rudimentary editors to maintain a broken install, compared to bloated GUI editors, that provide much comfort, but that easily could break. Core, is for core, is for core. A DAW is very complex thingy. -- 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] Ferature Spec Discussion: Testing
Are package uploaders properly testing their own packages? When I wrote a one passphrase/multi volume cryptsetup interface simply to use it myself in systemd and dracut, I had to set up a dummy partition with a keyfile so I could test that option, as otherwise I could not write it into the program and know if it worked or not. I assume package devs are testing every option they include, or are they writing code they hope will work and packing it up into .debs untested? On 5/21/2014 at 1:07 PM, Elfy ub.u...@btinternet.com wrote: Some comments in line ... It's likely to get a bit long, sorry about that ;) On 19/05/14 10:32, Kaj Ailomaa wrote: If anyone is interested in helping out with writing and performing tests during this cycle, please answer this mail (and do read on). This is the most important bit here to be honest, if there are only a /few/ people that would be willing to run package tests then anything else is rather, struggling to find a word here that isn't *pointless* When we (and for anyone reading this for the purposes of this mail - *we* is Xubuntu QA) started to write our testcases, there wasn't a huge crowd of people doing that - it took us a cycle to get the testcases written for us. We were then in a position to use those properly during the LTS cycle - and it went really well for us. Now, our applications are less complicated than many of yours. Consequently, I'm not going to be able to do much in the way of helping to write testcases for you - what I could do - is start setting up the barebones of testcases for you, which someone with more experience of an application can flesh out. They aren't complicated to write - it just gets time consuming and rather repetitive - certainly not a very glamorous job - but it is one that pays dividends in the end. We hardly do any testing at all during our cycle, currently. This needs to be changed. Naturally, we do required tests for our releases, the Beta releases and the final release, but other than that, there's no structured testing. There are two kinds of testing that we would like to do: * Quality Assurance Testing - to make sure there are no bugs for a wide range of applications * performance testing (which is rather a big topic) The most urgent type of testing we need to deal with is the first of those. (So far, what we have in testing documentation can be found here https://wiki.ubuntu.com/UbuntuStudio/TestingDocumentation) # QA testing I suggest we establish a plan for testing, write test cases, and such, until Debian Import Freeze (https://wiki.ubuntu.com/DebianImportFreeze), which is scheduled to happen Aug 7th this cycle. Debian Import Freeze is a great time to do testing on Debian imported packages, since those packages won't be changing before release. It also gives us some time to find bugs, report them and fix them (Testing can of course be done from day one of our development cycle. The more time we have to spot bugs and fix them, the better, but we should begin no later than Debian Import Freeze). So: * Test writing may starts any time * Testing of applications should begin no later than at Debian Import Freeze, Aug 7th I have a suggestion here, why not pick a handful of applications, get them landed in the manual testcase branch - then we can set up the tracker and people can start testing. Doing this - people get practice at writing them, people can start testing as soon as the tracker is up, you start to get results sooner - I would think it better to get reported bugs slowly to start with than to suddenly have 20 or 30 tests - all being run, all producing results at the same time. Elfy has offered to give us a hand on this. If he likes, he could take the role of QA lead for Ubuntu Studio during the next cycle, and mentor us into set up testing. What do you think elfy? I am more than happy to help you with this goal, there are probably some infrastructure issues with the trackers that need to be sorted out Launchpad wise, if you want me to do that I can talk to Nick Skaggs about what needs to be done. Let me know if you want me to do that please. As I alluded to earlier - 'we' took longer than a cycle - so I'm happy to help you all while you need the help, if that's longer than a cycle - so be it. The people who write the tests should know the applications they write the tests for. The test should be as simple as possible, but still designed to spot as many typical problems as possible for that application. If anyone wants a look at how testcases are written for the majority of cases, then bzr branch lp:ubuntu-manual-tests and have a look in /testcases/packages/ So, those are my thoughts at the moment - feel free to ask me questions about how we have worked our system. I tend to be about early morning for a while (06:00UTC ish) and later in the day 17:00UTC onward for 5 or so
[ubuntu-studio-devel] WM/DE
On Arch and Debian I use JWM. I used Xfce4 before I switched to JWM. I still have the option to use Xfce4, but I don't want to do this. Soon I'll switch from Xfce4 to JWM for *buntu installs too. Ubuntu Studio developers, you should test JWM for a while. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, 21 May 2014, Kaj Ailomaa wrote: An ubuntustudio-audio-minimal package would make it easier for users to install only the core audio applications for the audio workflows. Also, it could be used in our suggested smaller ISO. What should it include? Out of the current packages available, I'm thinking: # audio plumbing and tools jackd I am assuming this is the jackd we have now that includes jackdbus. a2jmidid alsa tools and utils (alsa-tools, alsa-tools-gui, alsa-utils) ffado (ffado-tools, ffado-dbus-server, ffado-mixer-qt4) pulseaudio-module-jack gladish The only thing I can think that is missing is some kind of patch bay for jack. I would suggest jack.tools too. (in fact, even though it is CLI only I would suggest adding it to the main ISO as well.) I am thinking in terms of tools that can be used for automated testing from scripts. # ubuntu studio kernel linux-lowlatency (already depends on rtirq-init) rtirq-init # midi essentials vkeybd midi tools (gmidimonitor, qmidiarp, qmidinet, qmidiroute) jack zita-ajbridge Possibly also jack-rack and a small selection of great plugins? Many of these assume X. I don't have a comment one way or the other really. I am guessing the small iso already presupposes X and gtk so ubiquity can run. I would suggest trying to keep the lib set needed as small as we can. That is try to fill this with meta with tools that are all based on the same toolkit. For example, you have not included qjackctl, but it would pull in all the qt libs. The starting and stopping of jackd(bus) does not require much, but the patchbay for many people needs to be there. I know -controls is meant to be able to set up and run jackd(bus) but is it also intended to allow connecting jack ports? Speaking of patchbays. A qjackctl like patchbay for PA would be nice too, I have seen a lot of people asking how to route audio from application to application with pulse. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, 21 May 2014, Jimmy Sjölund wrote: Shouldn't there be a DAW of some kind? Ardour is the main that comes to mind, but I suppose is rather big? No. Not in the audio-minimal. There are a number of daws around, but what we do want to include is enough so that any DAW will work. I am personally not sure about including plugins. A reasonably complete synth (hopefully GM based) so sound can be made, But not a beat box or sequencer as that is a user choice. We are moving out of the huge meta thing and into choosing applications that the user wants for their workflow. There are some people who might be happy with no MIDI stuff at all. My own reality is that all of my recording to this point has used no Synth sounds or MIDI control. So I could be very happy with guitarix and ardour plus a good set of effects plugins. On the other hand, the SW/OS I have on my drive takes up a very small percentage of drive space even with all of studio on it plus other SW on top of that. Our custom menu keeps all these applications managable. Once we add an application, it can be removed but, that application may have brought in depends that would not be removed with the removal of that app. It would be best just to install those things that are wanted/needed in the first place as much as possible. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Wed, 2014-05-21 at 13:54 -0700, Len Ovens wrote: On Wed, 21 May 2014, Kaj Ailomaa wrote: pulseaudio-module-jack gladish I wouldn't include pulseaudio and especially not gladish. The only thing I can think that is missing is some kind of patch bay for jack. I would include aj-snapshot. Not a patchbay, but a good tool to store and restore connections. -- 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] Feature Spec Discussion: introduce ubuntustudio-audio-minimal meta package
On Thu, 22 May 2014, Ralf Mardorf wrote: On Wed, 2014-05-21 at 13:54 -0700, Len Ovens wrote: On Wed, 21 May 2014, Kaj Ailomaa wrote: pulseaudio-module-jack gladish I wouldn't include pulseaudio and especially not gladish. Hard to take your idea about pulse seriously as your hate for both pulse and it's author have been well expressed. I knpw there are ways to get around using pulse and still having desktop sound, but they all require hacking the desktop packages to make it happen. This would require more maintenance than we are ever likely to have manpower for. I personally don't use gladish either, but it may make test setup more reproducable in some cases. The only thing I can think that is missing is some kind of patch bay for jack. I would include aj-snapshot. Not a patchbay, but a good tool to store and restore connections. Anything that can show what is connected, what ports are available and allows connecting ports in some easier way than typing out the whole port names. -- 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] WM/DE
Wouldnt it be better to go with something with high performance and super light weight in terms of either a window manager or DE. I have tried enlightenment and its rather light weight and rather zippy. reason being is its coded in native c/c++. is this something advantageous for a suite geared at multimedia, in otherwords keeping ram usage low in terms of the WM/DE so the rest of the ram can be used by apps? On Wed, May 21, 2014 at 9:17 PM, Ralf Mardorf ralf.mard...@alice-dsl.netwrote: On Arch and Debian I use JWM. I used Xfce4 before I switched to JWM. I still have the option to use Xfce4, but I don't want to do this. Soon I'll switch from Xfce4 to JWM for *buntu installs too. Ubuntu Studio developers, you should test JWM for a while. -- 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 -- Jonathan Aquilina -- 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
