Announcement

Collapse
No announcement yet.

Ubuntu 22.10 Switching To PipeWire For Linux Audio Handling

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • WannaBeOCer
    replied
    Originally posted by F.Ultra View Post

    Your link suggests that this is more to do with XWayland (since the application you are linking is X11 native and not Wayland native) than Wayland itself.
    As mentioned previously Wayland is missing functionality for this use: https://gitlab.freedesktop.org/wayla...ge_requests/45

    https://psychtoolbox.discourse.group...en-window/4277

    Running non-fullscreen always incurs a performance hit on any operating system (may change if and when PTB uses Wayland instead of X11 as display system at some point in the future, and the specific Wayland display server supports use of direct scanout from secondary planes/overlay planes), but current Wayland is by far not ready for PTB’s general needs). Also on non-Linux, visual timing and timestamps are not to be trusted at all.

    Leave a comment:


  • F.Ultra
    replied
    Originally posted by WannaBeOCer View Post

    I've been following this issue: https://gitlab.freedesktop.org/pipew...re/-/issues/93 My DAC does detect DSD playback but just like reported I get static noise when it's playing.



    Seems like you didn't read what I wrote. Wayland doesn't work on AMD, Intel and Nvidia when trying to run vision/neuroscience experiments that require precision timing. If it worked fine it would already be the default backend for Psychtoolbox: https://github.com/Psychtoolbox-3/Ps...box-3/pull/765
    Your link suggests that this is more to do with XWayland (since the application you are linking is X11 native and not Wayland native) than Wayland itself.

    Leave a comment:


  • F.Ultra
    replied
    Originally posted by user1 View Post

    The same can be said about any common piece of software. It also got more and more bloated (in terms of resource usage), but did we really get new significant features?
    Perhaps, but not generally IMHO. E.g Word Processors and Spreadsheets are far more advanced today than what they where back in 1986. Same with 3d renders (Blender) and graphics programs (PS and GIMP) even if I there (as a graphic illiterate) miss the more simple programs such as Deluxe Paint , sound editors and DAW:s are also way more advanced today.

    Also I must say that they new calculator in Gnome 41 is a big step up from their older version, just hate that they removed the auto removal of spaces since copy+pasting numbers now means that I have to do manual cleanup for it to accept them. And I also wish that they would increase it beyond 64-bit integers.

    Leave a comment:


  • Old Grouch
    replied
    Originally posted by cl333r View Post
    Meanwhile KDE Spectacle offering to save screenshots as .cur or .ico files, but not .webp (Ubuntu 22.04)!

    Both sides work hard to keep the Linux desktop share at 1%.
    Umm - I hope JPEG XL is offered.

    Leave a comment:


  • WannaBeOCer
    replied
    Originally posted by user1 View Post

    I was actually wondering if it's even possible to have native DSD playback on Linux (without converting to PCM) because AFAIK even on Windows you need an ASIO driver for that.
    I've been following this issue: https://gitlab.freedesktop.org/pipew...re/-/issues/93 My DAC does detect DSD playback but just like reported I get static noise when it's playing.

    Originally posted by mppix View Post

    Very outrageous: just run your display off the iGPU and use the Nvidia GPUs for compute. Wayland works, CUDA works, best of both worlds and works like a charm =)
    Seems like you didn't read what I wrote. Wayland doesn't work on AMD, Intel and Nvidia when trying to run vision/neuroscience experiments that require precision timing. If it worked fine it would already be the default backend for Psychtoolbox: https://github.com/Psychtoolbox-3/Ps...box-3/pull/765

    Leave a comment:


  • mppix
    replied
    Originally posted by WannaBeOCer View Post
    This thread has gone way off topic.



    Yes that is outrageous since it doesn’t even meet feature parity of x11.

    It’s perfectly fine for 99% of Intel/AMD normal desktop usage/gaming. Left out Nvidia since they’re still working on their support: https://forums.developer.nvidia.com/...release/214275

    It’s currently completely useless for vision and neuroscience research. Which I’m certain have more workstations deployed than the number of Linux gamers due to broken timing in Wayland.

    https://gitlab.freedesktop.org/wayla...ge_requests/45
    Very outrageous: just run your display off the iGPU and use the Nvidia GPUs for compute. Wayland works, CUDA works, best of both worlds and works like a charm =)

    Leave a comment:


  • mppix
    replied
    Originally posted by Almindor View Post

    This makes no sense to me. Why should pulseaudio or app settings influence recording when using pipewire? If those settings worked with pulse, why not pipewire. It's supposed to be compatible. Also the broken recording wasn't app specific, any recording app (skype, the gnome record app etc.) just produced what I'd guess as wrongly sampled data.
    In general, it is. Yours seems not to be. I would start by purging the app settings (I had success with that on one machine actually). Your debug procedure may vary...

    Leave a comment:


  • user1
    replied
    Originally posted by WannaBeOCer View Post
    I’ve been using PipeWire for a few weeks now on Solus with a SMSL M8A v3 DAC. Only issue I’ve run into is DSD playback. Aside from that it has been stable. Here’s a useful guide: https://discovery.endeavouros.com/au...#--sample-rate
    I was actually wondering if it's even possible to have native DSD playback on Linux (without converting to PCM) because AFAIK even on Windows you need an ASIO driver for that.

    Leave a comment:


  • Almindor
    replied
    Originally posted by mppix View Post

    Pipewire recording works, generally speaking.
    It may be helpful to purge pulseaudio and/or delete all hidden config files in the user directory.
    This makes no sense to me. Why should pulseaudio or app settings influence recording when using pipewire? If those settings worked with pulse, why not pipewire. It's supposed to be compatible. Also the broken recording wasn't app specific, any recording app (skype, the gnome record app etc.) just produced what I'd guess as wrongly sampled data.

    Leave a comment:


  • Vermilion
    replied
    Originally posted by polarathene View Post
    You can't minimize apps? At least when I was testing some software out like Unigine Heaven I could not hide the launcher window. I'm a bit confused why that's the case and what you're meant to do (shift it to a different workspace?). There wasn't anything in the windows titlebar with right-click context, nor in the top panel interaction for the app regarding minimizing. I believe more native apps like Nautilus supported such via those menus at least, but it seems it's not consistently supported?
    Yes, the workflow in GNOME requires a bit of getting used to, and it starts making sense once you're familiar with it.

    You're supposed to launch apps in their own workspaces. From the overview you can either drag-and-drop app icons into different workspaces, or if you prefer keyboard-based workflows, use Ctrl+Alt+Right/Left to switch workspaces and type app names in the overview. Window management then happens through workspaces, either from the overview, keyboard shortcuts, or touchpad gestures (Wayland only).
    That's why in the default experience, there's no minimize buttons, and no panel to restore minimized apps from.

    I'm personally too used to this workflow that I have a bad time when forced to use Windows occasionally, with muscle memory getting in the way.
    Last edited by Vermilion; 22 May 2022, 10:08 AM.

    Leave a comment:

Working...
X