{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifj33zlj3e42zrd7vbckkvsdzjppofmnmoxxcmob2dzp4ifyl5dwm",
    "uri": "at://did:plc:yrn4rbgwenb6lfhhzjegbtnc/app.bsky.feed.post/3motb344zlag2"
  },
  "path": "/t/virtual-surround-manager-please-help-with-setting-pipewire-metadata/12336#post_2",
  "publishedAt": "2026-06-21T16:36:01.000Z",
  "site": "https://discourse.flathub.org",
  "tags": [
    "https://shaz.app"
  ],
  "textContent": "it’s crickets around here isn’t it - I don’t get why that is ???\n\nI’m able to use pipewire with my pianocheetah flatpak (in the next release I’m working on - not in the current release).\n\nMy finish args are:\n\n\n    “finish-args”: [\n    “–filesystem=host”,\n    “–filesystem=xdg-run/pipewire-0”,\n    “–share=ipc”,\n    “–share=network”,\n    “–device=dri”,\n    “–socket=wayland”,\n    “–socket=fallback-x11”,\n    “–socket=pulseaudio”\n    ],\n\n\nSo looks like the diffs between us is my --filesystem=host (probably not necessary for you - I just don’t like the weird paths that show up when you don’t use it)\n\nand share=network (I think that’s necessary to use usb midi devices? as with many flatpak things i’m unsure)\n\nand socket=pulseaudio - I think this is all you’ll need it’s the ONE flatpak flag telling the system that you’re using audio and not particularly pulseaudio just any audio.\n\nThis is not well doc’d (flatpak dev docs are voluminous but not very comprehensive as with all things linux) and getting help is rough (again - as with all things linux sigh)\n\nI mean ole claude may make some crappy code (if you don’t clean it up) but I’ve found it verrrrry helpful in getting past the very limited docs of linux/kde/flatpak/etc etc.\n\ngood luck to ya\n\n…Steve https://shaz.app",
  "title": "Virtual Surround Manager: Please help with setting PipeWire metadata"
}