mrhrdr

joined 1 year ago
[–] mrhrdr@lemmy.world 1 points 1 year ago (1 children)

(I don't see comments below the post - only saw this in my inbox right now?)

Aha, I did the change manually, forgetting that sed would substitute the var. Would be great if Pipewire was aware of environment variables, but that's not an issue to complain about here I guess :)

[–] mrhrdr@lemmy.world 1 points 1 year ago* (last edited 1 year ago) (3 children)

The config file doesn't seem to support environment variables: for me it throws an error in the logs when i use the ${HOME} variable.

I can't find any docs on if it supports any environment vars - does it work for you?

[–] mrhrdr@lemmy.world 0 points 1 year ago (5 children)

Thanks, the PIPEWIRE_DEBUG=3 thing showed what's wrong: it uses a relative path to find the atmos.wav, so when I changed to use an absolute path it worked.

It might have something to do with my .config/pipewire directory being a symlink to my dotfiles, but now I know that it works! Thanks again :)

[–] mrhrdr@lemmy.world 1 points 1 year ago (7 children)

Hey, thank you so much for this!

I seem to be misunderstanding some step though: I have copy-pasted the steps above and put the atmos.wav file in the hrir directory, but I don't get any sound in my headphones when I select the Virtual Surround sink with connected headphones? I get sound when I select the regular Headphone device.

Is this meant to work out of the box when I connect my headphones in the regular jack on my laptop, or does it only work with a USB DAC?

[–] mrhrdr@lemmy.world 1 points 1 year ago

Great, thanks! Subscribing

[–] mrhrdr@lemmy.world 1 points 1 year ago (2 children)

This looks great! Is there some issue tracker to follow, or is it too early for that? I'm personally really interested in the 'Remember layout from previous session/screen setup' feature, but I realize that might be something for later :)