search

gentoo-audio / audio-overlay

Gentoo overlay for music production
https://gentoo-audio.github.io/audio-overlay
GNU General Public License v2.0
41 stars 22 forks source link

Collect a list of ebuilds from proaudio #9

Open mrVanDalo opened 7 years ago

mrVanDalo commented 7 years ago

Suggested by maintainers

Requested

simonvanderveldt commented 7 years ago

I'd like to pull in the following in the short term:

In the somewhat longer term I'm looking at

And maybe the non stuff (non-mixer mainly, but that also means non-session-manager afaik)

domichel commented 7 years ago

I'd like to pull in the profiles from proaudio. It is 2 of them, desktop/proaudio and desktop/proaudio-kde. I use the first one into a systemd and *kit free system, but due to the actual state of gentoo/portage, I cannot test the second one (cannot install kde anymore with these USE flags).

In consequence, I will review the desktop/proaudio profile. For desktop/proaudio-kde, it is 2 solutions: 1) drop it. 2) drop the systemd, *kit and semantic USE flags from that profile, it should work but I cannot test it.

Anyway, I think the right solution is 2) because it will put in portage a lot of audio related USE flags by default, which is a good thing for an audio pro system.

simonvanderveldt commented 7 years ago

I'd like to pull in the profiles from proaudio. It is 2 of them, desktop/proaudio and desktop/proaudio-kde.

@domichel What do they actually do? I.e. why would someone need specific profile for audio?

domichel commented 7 years ago

For desktop/proaudio, someone using the rt-sources will usually not compile the cgroups into the kernel. The cgroups are needed by systemd. That imply such users will have "-systemd" in their USE flags, and as systemd and kit are tightly coupled, we can also put "-kit" and "-udisks" into such profiles. The result will be a systemd and kit free system (and as consequence a gnome and kde free system). In addition, that profile will put useful audio related USE flags like jack or dssi into the profile. Such a profile will work great with a rt kernel and all light desktops not depending on systemd or kit.

I just checked, desktop/proaudio-kde must be renamed into desktop/proaudio-gnome and desktop/proaudio-plasma. Due to the recent gnome and kde development, they will only add some useful audio flags like jack into the user profile.

mrVanDalo commented 7 years ago

Do we support systemd ?

simonvanderveldt commented 7 years ago

For desktop/proaudio, someone using the rt-sources will usually not compile the cgroups into the kernel. The cgroups are needed by systemd. That imply such users will have "-systemd" in their USE flags, and as systemd and kit are tightly coupled, we can also put "-kit" and "-udisks" into such profiles.

@domichel Hmmm, this sounds like a lot of assumptions. Also, technically there's no reason to disable cgroups if you want to use the RT PREEMPT patches. Same goes for systemd, one can run systemd fine without cgroups. And same goes for *kits, they can work fine without systemd.

This sounds more like a personal choice how you prefer your system. This overlay is for gentoo, users themselves can and should make their own choices of the combinations of items they want in their system.

Do we support systemd ?

I don't think that's a thing that's relevant to the work we're doing in this overlay?

mrVanDalo commented 7 years ago

I have no experience with systemd in gentoo, only when I'm using centos or ubuntu. I prefer openrc.

domichel commented 7 years ago

Hmmm, this sounds like a lot of assumptions. Also, technically there's no reason to disable cgroups if you want to use the RT PREEMPT patches.

It is no need to have 2 concurrent systems doing the same. The test I made shows me that when cgroup is in the kernel and configured for audio pro, a lot of system stuffs not related to audio are polluting the rt cgroup.

This overlay is for gentoo, users themselves can and should make their own choices of the combinations of items they want in their system.

Such a profile will only give them a possibility to use a profile that add a few audio related flags to the existing portage profile (for desktop/gnome and desktop/plasma), which I think is a good thing for an audio overlay. For desktop/proaudio, it will add the same audio flags to the desktop portage profile, and if you don't want the -systemd and -*kit flags, we can skip them and keep only the audio related flags.

For now, these audio related flags are: USE="audiofile cddb cdparanoia dssi ffmpeg fftw fluidsynth jack jackmidi ladspa lame lash libsamplerate lv2 midi mikmod mms mmx modplug musepack osc raw sndfile sse taglib theora threads timidity twolame vcd wavpack xft"

and the other flags are: -consolekit -policykit -udisks -udisks2 -upower

marcan commented 7 years ago

How does kit depend on systemd? I run a Plasma system without systemd and with kit and things work just fine.

Honestly I don't see why proaudio profiles should have anything to do with init system or desktop environment choice. Just enable audio-related flags and that's it. Going into init systems and desktops is making a lot of unnecessary assumptions. Desktop-specific variants should just inherit from the standard desktop profiles.

Those USE flags look like they could use some serious revision. What's xft doing in there? theora is a video codec, not audio (and a thoroughly obsolete one at that). If we're talking codecs there are a lot more that should be added, but honestly, choice is so vast I'm not even sure that's a good idea. E.g. why is wavpack in there and not flac? lame but not vorbis and opus? This isn't the place for mmx and sse (those aren't even regular USE flags any more, they're in CPU_FLAGS_X86 now). raw is about photos, not audio. vcd, seriously?

IMHO if we want an audio-specific profile, we need to start from scratch and consider what should be in there, starting with the basics like jack and lv2.

anemal commented 7 years ago

Here the list from the closed issue #22

simonvanderveldt commented 7 years ago

I've created #24 to discuss the profile. Then we can focus this issue on ebuilds.

simonvanderveldt commented 7 years ago

Updated the first post so it contains a list of all the ebuilds that have been suggested/requested. Added PR/issue numbers to them and marked the ones that are done.

domichel commented 3 years ago

I updated the wineasio ebuild in proaudio. It also install a python GUI to set its preferences.