[14:47] <sakrecoer_> OvenWerks: interesting thoughts. i think it would be awsome if ubuntustudio could become an add on for any falvour. But it is good to ship a DE that is a bit customized. Telling a noob, to install a new OS and then install an add on to get started being creative, is much more complicated then telling the n00b to install the OS and get started creating...
[14:48] <OvenWerks> sakrecoer_: Ah, I this stuff is more complex than it seems. :)
[14:51] <OvenWerks> sakrecoer_: Installing and go can happen too. The install of a flavour + Studio need not be any harder than just installing a flavour. We have already proved that.
[14:52] <sakrecoer_> that is excellent! and int that case, i agree, emphasis on PR will be required...
[14:52] <OvenWerks> The difference between xubuntu + Studio metas and ubuntustudio install is actually very small.
[14:55] <OvenWerks> sakrecoer_: the differences of opinion you have seen are how much the DE should be customized to make creation easier. The result of our exploration of people's opinions just in the small number of people who have been "vocal" has been that different people find different uses.
[14:56] <OvenWerks> sakrecoer_: the PR thing is different again. It is a problem regardless of how we set the DE up.
[14:57] <OvenWerks> sakrecoer_: we do need to deal with the perception that Studio is just a buntu with extra packages.
[14:58] <OvenWerks> sakrecoer_: I think we could also go farther semi-automatically setting more of the system setting for people.
[15:01] <OvenWerks> sakrecoer_: In general, I do not like USB as a transport for low latency audio. It is full of pit falls that OSx avoids with proper HW design and M$ hides by not telling you how bad the latency is. (or when you have xruns)
[15:01] <OvenWerks> sakrecoer_: but... it is what most audio interfaces are right now.
[15:04] <OvenWerks> sakrecoer_: It would be worth while keeping track of which irqs are being used for audio devices... how many USB devices are on each USB bus... and having user feedback suggesting that moving a USB interface to another usb plug, not using a hub, moving the mouse... etc. etc. would improve things.
[15:06] <sakrecoer_> OvenWerks: the PR teams needs to be synchronised and briefed about these topics...
[15:06] <OvenWerks> sakrecoer_: if we are starting jack at session start, we know which interface is the main one and can set rtirq's priorities line up to favour that interface... as an example
[15:06] <OvenWerks> sakrecoer_: yes.
[15:07] <OvenWerks> sakrecoer_: and we should be keeping a list of system settings we do to optimize things so pr can include them every time.
[15:19] <OvenWerks> sakrecoer_: just as an interesting side topic... it is interesting that the odroid chooses ubuntumate to pre install. http://www.hardkernel.com/main/products/prdt_info.php?g_code=G143703355573 They just call it "Ubuntu", but on a screen shot: http://dn.odroid.com/homebackup/201511/VU7inchwXU4.jpg
[15:20] <OvenWerks> sakrecoer_: nope one of the other screen shots looks Lubuntu: http://dn.odroid.com/homebackup/201511/7inchMTdisplaym.jpg
[15:21] <OvenWerks> sakrecoer_: my point being that both are very conservative DEs. Mate is the old gnome DE.
[15:26] <sakrecoer_> it looks like one is xfce and the other lxe
[15:26] <sakrecoer_> lxde even
[15:27] <sakrecoer_> I think conservative is good, ok, it will not look amazing to fancy artist, but it will be intuitive enough for beginner.
[15:27] <OvenWerks> xfce was modeled after gnome2, Mate is a fork of gnome2.
[15:27] <OvenWerks> so they both look the same
[15:27] <sakrecoer_> mate, is that the same as LXDE?
[15:28] <OvenWerks> no
[15:28] <sakrecoer_> ok.. i see now
[15:28] <sakrecoer_> is it what mint uses?
[15:28] <OvenWerks> lxde is based on openbox with a lower cpu/memory footprint.
[15:29] <sakrecoer_> it looks very much like a merge of XFCE and unity, but simplified
[15:29] <OvenWerks> Mint is a different animal again.
[15:29] <OvenWerks> mint was based on gnome 2 moved to mate and then to a modified gnome3.
[15:30] <sakrecoer_> ok. sorry, help me focus.... are we still thinking about using something else than XFCE?
[15:31] <sakrecoer_> i have a hard time understanding why it is important to do more customization to the DE than wallpaper and the icon-set...
[15:31] <sakrecoer_> and color code
[15:31] <OvenWerks> sakrecoer_: I think that because we have interested parties that work on both xubuntu as well as Studio and because xfce gives a polished yet understandable interface we will stay there
[15:32] <sakrecoer_> i think XFCE is the perfect compromise between modern and old
[15:32] <OvenWerks> sakrecoer_: also we know that xfce works well with audio stuff... that is it doesn't interfere as much as some other DEs do.
[15:32] <sakrecoer_> i'd rather see ubuntustduio have a customized theme, than having a custom DE...
[15:32] <sakrecoer_> sorry OvenWerks , i'm reading :)
[15:33] <OvenWerks> sakrecoer_: we don't have the personel for a custom DE
[15:33] <sakrecoer_> exactly!
[15:33] <sakrecoer_> eventualy, helping the XFCE, LXDE, or mate devs push the envelope of their product will be more productive for us, than taking on the task to maintain our own...
[15:34] <OvenWerks> sakrecoer_: it will be interest to see where the qt version od lxde goes (qxde?)
[15:34] <sakrecoer_> yeah... i have a good feeling about qt...
[16:48] <OvenWerks> No, I have pulse set up so it sees no alsa devices at all. pulse can only see what jack sees.
[16:48] <OvenWerks> sakrecoer_: so with the same setup in 16.04 you would see 6 sets of ports at boot instead of only 4.
[16:50] <sakrecoer_> ok... thats sounds excellent!
[16:50] <OvenWerks> That seems like a waste of resources if they could be shown if they are connected to jack or not then that would be better. In the AoIP world, this kind of thinking is already there.
[16:51] <OvenWerks> sakrecoer_: in the AoIP world, all possible audio connections on the local network would show up in the connection dialog, but the actual network connect only takes place if the user wants to use it.
[16:52] <OvenWerks> sakrecoer_: this does not have a need for changing jack, but rather creating a new connection application.
[16:52] <sakrecoer_> AoIP... audio over IP right?
[16:52] <OvenWerks> sakrecoer_: yes
[16:52] <OvenWerks> sakrecoer_: AVB, AES67, etc.
[16:53] <OvenWerks> sakrecoer_: even AoIP that is at the other end of a sound card (PCIe or USB)
[16:55] <sakrecoer_> hm... you are approaching the limits of my ignorant savant audio knowledge base :D
[16:55] <OvenWerks> sakrecoer_: both OSx and Win have that... though it is unique to the transport not generic... there is such a thing for AVB on Linux, but it is CLI (and experimental)
[16:55] <sakrecoer_> ok... 
[16:55] <OvenWerks> sakrecoer_: it should be transpart=ent to the user anyway.
[16:56]  * OvenWerks wanders off to spend time with Yf.
[16:56] <sakrecoer_> enjoy OvenWerks read you later!
[16:57] <OvenWerks> zequence: I think you missed this image of my system after boot with auto jack as it sits so far: http://picpaste.com/pics/qjackctl-multicards-tiw1pKQd.1449073497.png
[17:55] <NoklaM> Is there a virtualbox image of the 16.04 or do i have to install it manualy on to vbox?
[18:00] <flocculant> install it onto vbox 
[18:01] <NoklaM> Lost all files, was working on one, decided to install ATI drivers to get rid of flicker/screen tearing /fail