SDL2 Lands Native PipeWire Support

[tildearrow]

It's astonishing how many APIs we have to pass around some arrays of scalars.

It's astonishing how many transistors we have to pass around some currents to produce sound.

[Guest]

Well I mean we already have VNC, X11/ssh, RDP and countless others. We don't need to talk *or* code. It is already done

As for bandwidth, Pipewire achieves similar to VNC (similar technology actually). Which, in terms of performance is... basic.

??? VNC, RDP, SSH are about remote login/desktop experience.........

[oiaohm]

This graphic is wrong.

Jack Audio starts in 2002 that 2 years before pulseaudio.

Sound server starts in gnome in 1998 going back to 1997 with esound. http://0pointer.de/blog/projects/esound-free.html Sound servers predate ALSA as it only starts in 1998.

The history is OSS4 having it limitations worked around by sound servers before ALSA appears. We have gnome many others doing their own unique sound server solutions before ALSA appears. So ALSA partly comes out of OSS4 design limitations other than being proprietary.

Both pulseaudio and jackaudio are designed to deal with issues caused by the prior sound servers.

From http://stackoverflow.com/questions/2...io-sub-systems you can see a graphic how 2007 Linux audio stack looked.

Please note by 2007 quite a few sound servers have already disappeared but there is 5 different sound servers Artsd, ESD and NAS have basically disappeared.

Notice in the old map how Pulseaudio and all the sound servers are connecting to OSS this is because sound servers are working around the limitations of OSS as well. So both ALSA and OSS are unable to-do it all. Yes pulseaudio was designed to overcome the limitations of ALSA and OSS and FFADO.

jan.newmarch.name/LinuxSound/Sampled/Architecture/ From here we get a modern day map.


This is a modern day map to the audio stack. What pipewire does is fuse the Pulseaudio and Jackaudio into 1 item so finally down to 1 sound server yes pipewire does more than just being a sound server.

Really if you look at this map we have be getting rid of sound servers. So pipewire replacement would not wirecutter instead would have to be evolved Alsa and Direct Rendering Manager in kernel so no sound server is required. I don't see that change happening any time soon if at all.

[lyamc]

It wasn't meant to be taken that seriously. The joke was that due to a small action of making OSS4 proprietary, the Linux (and Unix) audio driver space got fragmented.

[oiaohm]

It wasn't meant to be taken that seriously. The joke was that due to a small action of making OSS4 proprietary, the Linux (and Unix) audio driver space got fragmented.

The problem is fragmentation was well and truly happening before OSS4 and ALSA in the Audio space. The sound server fragmentation on Unix starts in the 1980s before Linux exists.

http://sunsite.uakom.sk/sunworldonline/swol-02-1997/swol-02-connectivity.html

Network Audio 96 in X11 protocol was something started in 1996 yes another sound server solution that did not even make it to 1999.

https://wiki.archlinux.org/index.php/Open_Sound_System

Please note something the date OSS4 coming proprietary is 2002. ALSA starts in 1998 while OSS3 is out and is fully open source due to limitations of the OSS3 design is why the developer who creates ALSA starts coding it. So the Linux and Unix audio driver space started fragmenting in 1998 from the Linux side before OSS4 came proprietary.

Really lyamc the idea that OSS4 coming proprietary is a cause to the Linux and Unix audio space getting fragmented is not true. ALSA starts because OSS3 has some technical limitations while both are fully open source. 1998 when ALSA starts is when the fragmentation of Audio drivers between Linux and Unix start this is 4 years before OSS4 proprietary.

OSS4 coming proprietary speed up the change over to ALSA on Linux but was not the cause of the fragmentation starting. The reason the audio stack fragmented is technical defects of OSS in the first place. Some of the reasons why so many sound servers started in the 1990s was attempting to address the defects in OSS3 and before leading to sound server fragmentation.

Lack of cooperation to deal with OSS3 technical issues end up leading to one huge mess. That taken over 3 decades to somewhat get close to fix.

Just like the sound servers the fragmentation starts while OSS is open source heck before its even called OSS.

[60Hz]

It wasn't meant to be taken that seriously. The joke was that due to a small action of making OSS4 proprietary, the Linux (and Unix) audio driver space got fragmented.

It's barely "fragmented" and OSS is irrelevant, even w.r.t. to that. Stick to Gooming.

[lyamc]

gooming?

[60Hz]

gooming?