5 ms·

Audio has "just worked" for years now, thanks to PulseAudio. Video was a mess for a while, but now it will generally work great out of the box if you've got Int

Audio has "just worked" for years now, thanks to PulseAudio. Video was a mess for a while, but now it will generally work great out of the box if you've got Intel or AMD graphics. Nvidia is still a mess, but Nouveau will work fine for non-gaming stuff.

taurath 9y ago
I've got Nvidia - probably the core of my problems then.
- vetinari 9y ago
  Yes, it is. For example, there was an article recently, how Nvidia isn't going to support OpenGL acceleration in XWayland. The keyholder to solve the problems with NV cards in Linux is Nvidia itself. They have all the info, all the sources, and whatever roadmap they planned. Linux community can solve only Intel and AMD problems, and that's because Intel and AMD are cooperating. Nvidia isn't (Linus' middle finger says hello). Meanwhile, it is up to you as an consumer, to vote with your wallet and use that to show the vendors your preferences.
  - sd8dgf8ds8g8dsg 9y ago
    Not sure why NIVIDIA should even invest any time in XWayland. It is just a stepping stone towards Wayland, and the retirement of X11
    - vetinari 9y ago
      The reason are: games. All the games (which are of course binary-only, often 32-bit only) released for Linux are linked against SDL 1.2/SDL 2 and X11. It means, that if you are Nvidia owner, you cannot switch to Wayland, unless you are willing to give up gaming (in the current session, at least). On the other hand, who is buying Nvidia cards? Gamers. So by not having OpenGL support in XWayland, they have to choose what kind of session they want to run. Many are of course going to choose X11, thus slowing down the adoption of Wayland, delaying the retirement of X11 and of course losing some benefits of Flatpaks (namely isolation at GUI server).
  - josteink 9y ago
    > For example, there was an article recently, how Nvidia isn't going to support OpenGL acceleration in XWayland Note: Xwayland, not Wayland itself. Xwayland is the X11-emulation server running inside Wayland (which itself is HW accelerated). Not saying anything you claim is wrong, but it's easy to interpret wrong so posting for clarity.
ZenoArrow 9y ago
> "Audio has "just worked" for years now, thanks to PulseAudio." For your use cases perhaps, but it's not suitable for all use cases in the same way CoreAudio on OSX is. Music production is a key weak point, which is why JACK and PulseAudio are both required to have what CoreAudio offers out of the box.
- em3rgent0rdr 9y ago
  There are a few options to allow for Jack and PulseAudio to coexist: http://jackaudio.org/faq/pulseaudio_and_jack.html http://jackaudio.org/faq/pulseaudio_and_jack.html There is a reason why there is both Jack and Pulse...they meet different needs (pro-audio vs desktop), and it is not necessarily a bad thing to have separate tools to handle separate needs.
  - ZenoArrow 9y ago
    > "and it is not necessarily a bad thing to have separate tools to handle separate needs." It's not a bad thing to have different high-level tools for different needs, but in the case of lower level frameworks it's suboptimal unless interoperability is seamless. In the case of PulseAudio and JACK that interoperability is not seamless, and is fraught with problems, so in this regard Linux audio is worse than CoreAudio.
CaptSpify 9y ago
I'm going to strongly disagree with you. Audio still has a lot of problems experienced by a lot of people. These naive statements are why people get frustrated with Linux. I strongly support FOSS software and use it all day, everyday, but we need to stop saying that our shit doesn't stink.

taurath 9y ago

I've got Nvidia - probably the core of my problems then.

vetinari 9y ago
Yes, it is. For example, there was an article recently, how Nvidia isn't going to support OpenGL acceleration in XWayland. The keyholder to solve the problems with NV cards in Linux is Nvidia itself. They have all the info, all the sources, and whatever roadmap they planned. Linux community can solve only Intel and AMD problems, and that's because Intel and AMD are cooperating. Nvidia isn't (Linus' middle finger says hello). Meanwhile, it is up to you as an consumer, to vote with your wallet and use that to show the vendors your preferences.
- sd8dgf8ds8g8dsg 9y ago
  Not sure why NIVIDIA should even invest any time in XWayland. It is just a stepping stone towards Wayland, and the retirement of X11
  - vetinari 9y ago
    The reason are: games. All the games (which are of course binary-only, often 32-bit only) released for Linux are linked against SDL 1.2/SDL 2 and X11. It means, that if you are Nvidia owner, you cannot switch to Wayland, unless you are willing to give up gaming (in the current session, at least). On the other hand, who is buying Nvidia cards? Gamers. So by not having OpenGL support in XWayland, they have to choose what kind of session they want to run. Many are of course going to choose X11, thus slowing down the adoption of Wayland, delaying the retirement of X11 and of course losing some benefits of Flatpaks (namely isolation at GUI server).
- josteink 9y ago
  > For example, there was an article recently, how Nvidia isn't going to support OpenGL acceleration in XWayland Note: Xwayland, not Wayland itself. Xwayland is the X11-emulation server running inside Wayland (which itself is HW accelerated). Not saying anything you claim is wrong, but it's easy to interpret wrong so posting for clarity.

ZenoArrow 9y ago

> "Audio has "just worked" for years now, thanks to PulseAudio." For your use cases perhaps, but it's not suitable for all use cases in the same way CoreAudio on OSX is. Music production is a key weak point, which is why JACK and PulseAudio are both required to have what CoreAudio offers out of the box.

em3rgent0rdr 9y ago
There are a few options to allow for Jack and PulseAudio to coexist: http://jackaudio.org/faq/pulseaudio_and_jack.html http://jackaudio.org/faq/pulseaudio_and_jack.html There is a reason why there is both Jack and Pulse...they meet different needs (pro-audio vs desktop), and it is not necessarily a bad thing to have separate tools to handle separate needs.
- ZenoArrow 9y ago
  > "and it is not necessarily a bad thing to have separate tools to handle separate needs." It's not a bad thing to have different high-level tools for different needs, but in the case of lower level frameworks it's suboptimal unless interoperability is seamless. In the case of PulseAudio and JACK that interoperability is not seamless, and is fraught with problems, so in this regard Linux audio is worse than CoreAudio.

CaptSpify 9y ago

I'm going to strongly disagree with you. Audio still has a lot of problems experienced by a lot of people. These naive statements are why people get frustrated with Linux. I strongly support FOSS software and use it all day, everyday, but we need to stop saying that our shit doesn't stink.