<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Aug 20, 2015 at 4:49 PM, Len Ovens <span dir="ltr"><<a href="mailto:len@ovenwerks.net" target="_blank">len@ovenwerks.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, 20 Aug 2015, Mike Holstein wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
15:48 < zequence> holstein: I really urge you to put your thoughts down and write<br>
an email instead<br>
15:48 < holstein> well, its fashionable to not like ubuntu.. and, thats<br>
something larger than ubuntustudio.. but, when folks go to #ardour, for <br>
example, and the major piece of advice is "whatever you do,<br>
dont use ubuntustudio", i would like to think about why<br>
</blockquote>
<br></span>
That is not really true, "don't use Ubuntu" Yes I see that... and probably with good cause. It is possible to get good results with Unity, easy to get bad results. Certainly Studio sometimes just gets lumped in with Ubuntu. And when suggesting a distro made for Audio, generally kxstudio or avlinux are the two mentioned. However, I have heard UbuntuStudio recommended sometimes as well. (especially lately as kxstudio has had some issues related to KDE)<br></blockquote><div><br></div><div>i dont share that viewpoint, personally, that folks shouldnt use ubuntustudio. i feel like i had to make an effort, though, to sit in #ardour, and address each comment that i saw, for a time, and ask that folks try the more recent versions before making blanket statements..</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Studio has some good stuff:<br>
- xfce<br>
- a good set of applications<br>
- audio and RT allready works<br>
<br>
On the other side:<br>
- LTS releases with sometimes the buggiest release of some<br>
required audio utilities.<br>
- LTS releases mean that by the time the next one comes out<br>
the old one is hopelessly behind. Kubuntu may have<br>
the best way of dealing with this by trying to make<br>
each release LTS-able. Anything based on debian, tends<br>
to be release based.<br>
- It is not easy to update an LTS, the policys for adding a new<br>
version for anything besides bugs is not an easy road to<br>
take.<br>
<br>
It takes a lot of work to keep an LTS current and we just haven't been able to do that. Both kx and av add the latest versions to their repos within days (minutes sometimes)... they can do so because they own the repos and manage them.<br>
<br>
We could set up an upgrade repo ppa, but I do not know if that is what Ubuntu is all about. Ubuntu flavours are meant to use the Ubuntu repos.<br>
<br>
Directions we could go that remain Ubuntu-ish but still make a good distro for audio:<br>
<br>
remove module-udev-detect from pulseaudio and run jackd as the only back end. So jackdbus would start at session start and pulse would use either jack or dummy as it's only backends.<br>
<br>
Create a udev utility that replaces module-udev-detect for PA with something that adds a plugged in audio IF to jack on the fly. The user in -controls would be asked or allowed to determine if the new device became the jack maser device or if it was added via zita-a2j/j2a. If the (probably USB) new device was to be master, the internal would then get added via zita-a2j/j2a.<br>
<br>
These two things alone would make Studio unique in the Linux audio world and would solve more than 50% of support requests both in ubuntuStudio and in other places like #Ardour.<br>
<br>
Make performance mode default with the option when battery operation is detected to goto a slower speed or ondemand. (in general a slower _constant_ speed is better for low latency)<br>
<br>
Note on performance mode: I have found that performance mode runs cooler at high CPU use than ondemand. Ondemand is good for mostly idle use.<br>
<br>
Allow sw update stuff to be turned off while doing audio intensive stuff (stop cron works for me).<br>
<br>
Any place I have mentioned starting jack should include a2jmidid, using a2j_control seems to be more reliable for me than using a2jmidid directly.<br>
<br>
Note that this whole topic is audio only and does not address other workflows in Studio. It happens to be what I know :) Also, I have not mentioned the tweaks we already do for audio which should remain.<br>
<br>
--<br>
Len Ovens<br>
<a href="http://www.ovenwerks.net" rel="noreferrer" target="_blank">www.ovenwerks.net</a><br>
<br>--<br>
ubuntu-studio-devel mailing list<br>
<a href="mailto:ubuntu-studio-devel@lists.ubuntu.com">ubuntu-studio-devel@lists.ubuntu.com</a><br>
Modify settings or unsubscribe at: <a href="https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel" rel="noreferrer" target="_blank">https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">MH<div><br><a href="http://likethecow.com" target="_blank">likethecow.com</a></div><div><br></div></div></div>
</div></div>