![]() ![]() That means that until Resolve finishes using it, I can't use my microphone! I could use that to record my voice over, but ADR on Resolve doesn't bother with either Pulse or Jack, and uses something called "ALSA". ![]() Resolve has this function called "ADR", or "Automated dialogue replacement" - it's a feature they use in film to record the actors on the computer. Last, when I use DaVinci Resolve to edit and upload my stream to Youtube, I want to record some voice over. Again I will have trouble, because the many moving parts in streaming, including video, make it very difficult to output a high quality stream. Now lets say I want to stream my playing on Twitch. Well, bad luck, some software do not support jack, and you can't use it together with PulseAudio. Imagine you wanted to play along with some music. Jack was not simple to use, but even if you were good at it, there were problems. I had to install a special software called "jack", because PulseAudio would have me wait before I could hear a note I played. There are some things PipeWire makes a lot easier to do.įor example, I have an electric piano that I can connect to my computer and play. Support is a bit sparse for now, but there's a LD_PRELOAD workaround for v4l2 interfaces.Įdit: also, pipewire gained support for nicer bluetooth codecs faster than pulseaudio did. looking at zoom).Īnd lastly, pipewire should hopefully become one of the best APIs for accessing webcams and other video streaming devices in the future (allowing stuff like sharing a camera between multiple apps, simple sandboxing, middleware for compositing or video effects - think background removal tools). Pipewire is also used in most places where wayland is, to provide screen sharing capabilities (now, if proprietary software could catch up. Also, support for sandboxing (flatpak portals) is first-class, as one of the early design goals was to provide this for video. Pipewire has become more usable for audio during the last year.Īctual advantages of pipewire vs pulseaudio are not that obvious, but it should mostly be lower-latency, hopefully more stable, and more flexible (provide something like the old `jack` API where any stream can be plugged anywhere). ![]() In some ways I guess that's a recommendation if I managed to get the hibernation bug fixed then this would be a totally transparent switch from my perspective. Again, I think this is mostly just the fact that I never really dug into Linux audio too deeply before so I'm not always completely sure what's going on with it, and I'm not doing anything complicated enough for me to immediately tell a difference. I'm sure if I took the time I'd understand them, but I find PulseAudio's sinks really annoying to work with and to manipulate. One thing I'd love is for a cleaner command-line interface to handle sinks, particularly when scripting. I'd love to do more with it, but truthfully I didn't really dig into Pulse/Alsa/Jack enough initially to really notice what the benefits are, so I can't tell a difference. Otherwise, it seems to basically just work. I'm certain this has something to do with me doing a bad install and not cleaning up old config files or something, possibly with either me either using PulseWire or not using PulseWire to manage the session, but it's pretty annoying (although apparently not annoying enough to get me to debug the issue). My switch to PipeWire on Arch has been mostly painless except for one particularly annoying bug that I haven't been able to track down yet - when the computer is hibernated, something in the config goes wrong and I need to rerun `alsactl init` to get sound playing again. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |