| AppAraat[m] | <OvenWerks "pipewire still has a long way to"> Anything in particular that is missing from PipeWire for that purpose? | 07:01 |
|---|---|---|
| rgh | AppAraat: it was freewheeling but they implemented that just recenctly | 09:33 |
| AppAraat[m] | <rgh "AppAraat: it was freewheeling bu"> Not sure what you're referring to, but it was [OvenWerks](https://matrix.to/#/%40freenode_OvenWerks%3Amatrix.org) that claimed that PW wasn't ready for (semi)pro audio use. | 09:34 |
| rgh | freewheeling is that when you export a song, you can export it in faster (or slower) than realtime | 09:35 |
| AppAraat[m] | <rgh "freewheeling is that when you ex"> Oh I see! Didn't know what that was, pretty cool! | 11:23 |
| AppAraat[m] | Though why would someone want to export it slower than realtime 🤔 | 11:24 |
| AppAraat[m] | Resource usage savings? | 11:24 |
| rgh | Offline/ freewheeling takes just all the time it needs. | 11:25 |
| rgh | Let's pretend you have to disable some tracks during producing because your pc can't handle it. | 11:25 |
| rgh | On export you'd be able to just switch everything on. | 11:26 |
| rgh | Just like rendering video takes longer than the actual end product video. | 11:26 |
| rgh | It's not that common in audio I'd guess. | 11:26 |
| rgh | _vitalium entered the chat_ | 11:27 |
| rgh | But, I've seen a number of users on the various messaging platforms I'm in that went back to plain jack / pulse bridge after some time with pipewire. Too many bugs without a obvious reason. | 11:29 |
| rgh | I stayed away. | 11:29 |
| * OvenWerks would add that firewire is not supported (using ffado) and bridging to a running jack is not supported | 13:42 | |
| OvenWerks | rgh: The biggest problem is that debian/ubuntu have old versions of PW so it is difficult test properly without going full fedora and all the rest of the mess that includes with flatpack, wacom, etc. | 13:59 |
| rgh | Sigh | 14:25 |
| rgh | Pain | 14:25 |
| rgh | Suffering | 14:25 |
| OvenWerks | meanwhile, jack just keeps working | 14:58 |
| rgh | this ^ | 15:27 |
| AppAraat[m] | <OvenWerks "rgh: The biggest problem is that"> can't that PPA be used for testing the latest PW version though? | 22:22 |
| OvenWerks | AppAraat[m]: which PPA? do you have a url? | 22:33 |
| * OvenWerks can add it to his list | 22:33 | |
| AppAraat[m] | OvenWerks: I posted it earlier as a Reddit thread: https://old.reddit.com/r/linux/comments/n6qt3d/pipewire_0327_released_launchpad_ppa/ | 22:35 |
| AppAraat[m] | Direct link to PPA: https://launchpad.net/~pipewire-debian/+archive/ubuntu/pipewire-upstream | 22:35 |
| AppAraat[m] | > This Launchpad PPA will be actively maintained to keep in sync with Upstream. | 22:36 |
| AppAraat[m] | even supports 18.04 apparently lol | 22:40 |
| OvenWerks | I will have to see where my spare partiton is at. might be 21.04 or 21.10. | 22:40 |
| * OvenWerks is not on his work machine right now | 22:41 | |
| OvenWerks | one of my problems is that with an alsa device, starting jack will ask pw for that device which PW will release. After jack starts, then PW will make a bridge to that jack with the no of i/o that device has. | 22:44 |
| OvenWerks | The problem is that if I need a bridge it probably because I want to use a backend that PW doesn't have, dummy, ffado, netjack, etc. | 22:45 |
| OvenWerks | and therefore PW does not know jack is there, does not know how many i/o the backend supports and therefore does not make a bridge at all. | 22:46 |
| OvenWerks | Actually it could find out easy enough | 22:46 |
| OvenWerks | Pulse already does this... or used to at one time. | 22:47 |
| OvenWerks | Anyway. PW does not (did not?) have any way of manually creating a bridge of n i/o or n in and m out. | 22:48 |
| OvenWerks | For my use this is a showstopper. | 22:49 |
| Ginalo | Hi! Regarding the Ubuntu Studio Installer that installs packages to other Ubuntu flavors, I'm curious as to what it does other than installing packages. Also, does it only use Apt? | 23:02 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!