https://github.com/supercollider/sup...er/issues/6076 OK, supercollider people aren't sure. Did something change in pipewire between 0.3.77 and 0.3.78? (Like how pw-jack is supposed to be configured, etc?)

1 members found this post helpful.

Removed, since the post I was responding to was removed. Should I bug report this with the pipewire people? I don't think it's a supercollider bug. Rather, the supercollider people aren't sure what's going on. Or wait until 0.3.79 to see if it's still an issue?

https://gitlab.freedesktop.org/pipew.../-/issues/3465 Not just me. If any of y'all are having problems with pipewire and jack, please add your data.

4 members found this post helpful.

pipewire 0.3.80 FTB on slackware 15.0 using slackbuild from -current. Anyone else see the same error?

I haven't investigated further yet.

edit:
Need to apply the attached patch and it will build.

Attached Files

vulkan-compute-utils.c.patch.txt (2.0 KB, 18 views)

1 members found this post helpful.

PipeWire 1.0 Planned For Release Later This Year

https://www.phoronix.com/news/PipeWire-1.0-Release-Plan

2 members found this post helpful.

I'm going to be honest, I had pipewire working on an Arch based distribution and finely setup. It was not bad, that distribution also used systemd. On Slackware stable and current, I know they include support for it but if you are running any kind of production environment for music I would not be toying with this stuff. I had it working pretty decent on that Arch based distribution but I did not feel confident in it. I would stick with pulseaudio/jack for a while. There will be a point where they have stuff ironed out with pipewire/slackware in terms of things being fairly seamless, however, that's a ways off.

Alien Bob has one of the best howto's out there for setting up your system base configuration for a DAW and is great for studio production, if you have your system set up with the older software tech I would not toy or fool with what you have, it's already excellent and not broke.

I have been using the older proven DAW setup for years and it's great. If you are running a music production environment the more boring the better, I actually use Mixbus32c so hopefully that gives some of you an indication of how serious I take this stuff. That said if you absolutely must 'pipewire' you probably want to be on a rolling release arch based distribution with fat fat fat software repos and systemd. It's not going to work the same on Slackware.

I have both Slackware stable and Slackware current setup for DAW work, neither use pipewire. A valid point to raise about pipewire is that it is just now reaching version 1, hold off on pipewire for a while that's my recommendation for DAWs only. I know I am new here but have been using all of this stuff four a couple decades, I'm not an idiot.

2 members found this post helpful.

ping slackdruid - While I'm retired so not as serious into DAW as I once was, I have recorded, edited and posted more than a dozen sessions in the last 2 months. I started using Slackware around 1999 and compiled Ardour when it was pre-alpha. I completely agree with you that pipewire on Slackware, as much as I hate having to say it, is not quite there yet, even on Current, but it is very workable and preferable to pulseaudio on some other distros. I am quite excited about the 1.0 release and hope ALL Slackware versions move to it when it is released.

Precisely on that point, slackduid, I want to ask you if I understand one other point on your #531 post. Why do you mention systemd? Do you think the init system has anything to do with some of those distro's success with pipewire? ... or is it just the newer version of pipewire that's responsible? IOW is this causation or unrelated correlation in your view?

I'm not 100% certain but systemd seems to be able to be more tightly integrated with pipewire allowing for an easier setup. I'm not a fan of systemd though, it's not just an init system it's a modern suite of things that are tightly coupled to the operating system. I don't like its process supervision. For those that like it, I'm not turning my nose up at their choice of using it, it's just not for me.

Pipewire is not default in Slackware, but is required by Wayland/Plasma5 and isn't only about audio, but also about video.

And finally, this thread is for those who want to experiment with Pipewire.

I don't understand why you came here if you don't like Pipewire. Just to crash the party?

I actually do like pipewire, I think it's an awesome project. I merely mentioned that you don't want to be toying with it on a DAW setup, I am just making the point that the last thing you want while you are working on a music project is to be messing with the stuff.

Nothing I said is keeping anyone from enjoying it, I just wanted to add a caveat for a particular use scenario. It's getting there and I am sure it's going to be great in the future for DAW's. I am actually looking forward to it, it's just that right now if your DAW is already working? You might want to hold off. At least set it up on a different install or system.

If you are not running a DAW on Slackware have at it and tons of fun in the process. I have no control over what you decide to do with your system, don't let my opinion get in your way. The only reason I bothered to interject in this thread was due to the mention of someone having issues with supercollider, you really can't blame me for trying to save someone from a headache on their DAW setup.

I was not trying to lead anyone astray from their hearts desires with pipewire, use it!

I don't understand why you assume slackdruid is even attempting to "crash the party". How is it a bad thing to note limitations, especially at this pre 1.0 stage? It seems to me noting such limitations identifies areas in which experimentation and improvements are needed. It also is a wise warning that presently pipewire is still a bit problematic on Slackware for serious DAW work. Serious users should be warned they have a slight uphill battle in such efforts at least pre 1.0 and certainly with pipewire-0.3.44, default on Slackware 15.0, and even with pipewire-0.3.80 now default on Current.

It is my sincere and somewhat urgent wish that Patrick moves to 1.0 even on v15.0 Slackware as soon as it is possible. I recognize that Pulseaudio was a major boon to basic audio users but for me, Pulsaudio, caused me a huge amount of grief with semi-professional audio work with high end audio. Pipewire has the ability to maintain and even improve BOTH basic and professional audio work and from my POV it's about damned time!

I think I understand why it has taken so long for Linux to have a solid audio system considering that Linus, himself, prefers silence while he works. Audio is, at best, a nagging afterthought for devs like Linus. Coming to Linux from OS/2 even as much as IBM disliked even the idea of multimedia having the possibility of distracting workplace efforts, even they recognized that multimedia is important to advertising so OS/2 did a passably decent job for the era. Linux has never done a solid job with audio. The ability is certainly there but neither OSS nor ALSA was basic for the average user, and it is still a bit dense and clunky for pros which is why any need for anything remotely like pulse was perceived.

Thankfully, Pipewire has a nearly realized format in which to check that box off once and for all. I think slackdruid's posts have been valid and useful and by no means anti-pipewire. I imagine since Alien Bob seems to be a music lover Current will not hesitate to get Pipewire 1.0 working in his DAW as well as default Current systems. I hope Patrick does this for 15.0, too.

3 members found this post helpful.

What does systemd do more than start pipewire daemons (pipewire, pipewire-pulse, pipewire-media-session or wireplumber) compared to the "Raforg daemon" we use?

I think you answered your own question. But to cut like a razor blade when pipewire was rolled out running by default on distributions it ran out of the box said daemons. I know, I watched it happen and I was like "What the hell." and to be honest it was
not welcome but! I worked around it and copied over a configuration and edited it and it was fine until I found out below.

The reason I don't use pipewire is cause of xruns and lots of them at very low CPU usage and conservative settings not asking too much of the audio interface. I have found other instances of people with the same issues testing it out with DAW work.
Eventually I think the pipewire project will elucidate why it's happening and solve it but for now and I could be quite behind on the subject, so far as I know it has not been fixed.

For everything else pipewire is awesome, it truly is. Just....until you get to the music production part.

So the most salient point about pipewire concerning DAW work is xruns and boat loads of them. Hence me originally stating I did not feel confident in it, at least for now. For everybody else? Rock some pipewire.

I am absolutely all for pipewire as a project, it may eventually put GNU Linux on the map with sound quality right up there with Mac OS by default and believe me that's greatly needed.

That's not been my experience, slackdruid, and on very old hardware. I recorded a live session almost non-stop for 2 hours with a Scarlett Focusrite into an ancient T61P Core 2 Duo Thinkpad at 48,000 with 256 buffer and had not one xrun. Granted it was a single source microphone recording. I had experienced some difficulties running the Slackware DAW so I tried a few distros with newest Pipewire and also the OpenSuse Tumbleweed packages pipewire-jack, pipewire-alsa, and pipewire-pulse. I'd much rather have been able to use Slackware but I wanted to be able to edit and "punch in" and did not want to deal with Pulse latency.

This is why I think Pipewire is very close to being able to deliver the much needed coup de gras to Pulse and very soon and that is a day I will celebrate. I despise Pulse.

2 members found this post helpful.

Slackdruid, were you using jack2 or pipewire's jack? I had no end of problems with jack (really jack2) and pipewire, but when I switched over to pipewire-jack, the problems disappeared. Not one xrun, though, but I wasn't doing anything complicated with supercollider.

2 members found this post helpful.