![]() *apparently you need to build the apps off of the PipeWire Jack libs and not the regular Jack libs which kind of sucks but nothing major, we don't have to wait for the devs to get around to fixing anything at least.All of our software is available as a free download, right from our web site. I know little to nothing about PortAudio, I believe it is a crossplatform library capable of talking to many different audio services. So now I am recompiling PD to see if it speaks to PipeWire through its Jack interface. ![]() Just fired up PipeWire for the first time ever and it seems to work quite well without issues but I have yet to give it a good test.Īn application needs to be built with support for Jack, Pulse, ALSA and OSS if it wants to use them, PipeWire understands the languages of all of those and an app built with Jack or Pulse support will* work with PipeWire and unlike Pulse and Jack can also expose ALSA/OSS ports so applications can access them directly without the middle man which is one of the huge issues with Jack and Pulse, they both take over all available ports so no one else can get in. Enter PipeWire which brings video into the mix and seems to solve many of the user/administration issues of the rest. Jack and Pulse flesh out the features of ALSA but Pulse got adopted before it was ready and that first year or two was not fun and few seem to really like it, Jack is great when it works but can be a nightmare when it does not. Essentially linux used OSS back in the day than OSS changed its licence so linux had to find something new in a hurry, enter ALSA which was not at all ready but pretty good, not as mature as OSS or as featureful but it did a good job within its limits, which is where Jack and Pulse come in. All of these have overlap but they are not quite the same thing. PipeWire, Jack and PulseAudio are more user level and communicate with ALSA or OSS. Still happy to be schooled ALSA and OSS are low level/tied into the kernel. TLDR: I'm not sure why anyone would want to use Jack on a Mac. If that's not your cup of tea, don't install it! Finally, it's worth noting that Jack doesn't come with an uninstaller, so to get rid of it you have to manually remove files from /usr/local and below, and the list of files can be found on one of the windows of the installation package if you scroll down. RE that first point, I'm tentatively concluding that an audio app has to be Jack-aware (like Pd) in order for it to be routed by Jack, which isn't a requirement of other loopback drivers like Soundflower or Blackhole. I've seen 2 tutorial videos on Mac audio loopback where you can see that the presenter has Soundflower installed in addition to whatever loopback software they were demonstrating, so that makes me scratch my head. Soundflower is obsolete Jack is currentĮdit: I can confirm the 2nd through 4th bullet point but not the first and last.For Pd to send/receive from a Jack channel, Jack has to be running and you have to select Jack in the audio settings before you can select which particular Jack channel you want for input or output.The Qjackctl.app that is bundled with the Jack MacOS download runs on Monterrey without any additional runtime frameworks installed.Jack can serve as audio loopback software between MacOS audio apps such as Pd.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |