Audio Stream metada only shows "Chrome" in PulseAudio applications list
Reported by
mrva...@gmail.com,
Dec 12
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: 1. Have multiple Chromes play audio streams 2. Open PulseAudio controller, show Applications 3. All Applications are called "Chrome" What is the expected behavior? It would be nice to know which stream is what so I connect it the sink I want. What went wrong? When multiple tabs have (potential) audio streams, even if they're not playing, I have multiple "Chrome" applications that I need to try before I have the right sound out of my BT sink. Did this work before? N/A Chrome version: 71.0.3578.80 Channel: stable OS Version: Flash Version:
,
Dec 12
,
Dec 13
Thanks for filing the issue! From comment#0, this seems to be a Feature request. Hence marking it as Untriaged.
,
Dec 13
We mix streams inside Chrome, so it's not possible to provide more detail at this level.
,
Dec 14
We don't mix stream from different tabs, do we?
,
Dec 14
We only mix streams from the same frame, so we could name the resulting stream from something like the origin of the frame (or rather a part of the origin I guess, so https://www.youtube.com/watch?v=oHg5SJYRHA0 would end up being called www.youtube.com or youtube.com). I don't think this is super difficult to implement, just one more argument to plumb through ALL the layers :). It's also a somewhat frequent feature request if I recall correctly.
,
Dec 14
Correct, we mix streams within a frame, so you might end up with > 1 stream with the same name and how the streams map won't be clear to a user. I.e., we might map N 44.1kHz streams to -> stream#1 and M 48kHz streams -> stream#2. So I don't see a point of mapping this.
,
Dec 15
With all due respect I think it would help tremendously to have context information of the stream(s). I understand that some frames might generate more streams that will be indistinguishable, but reality now is that all frames generate streams that are inherently indistinguishable. So worst case scenario we won't win clarity for multi-stream frames, but best case scenario we know what frame created the single individual stream. In my normal everyday use, the latter scenario is 100% of my usecases (youtube/soundcloud), so it would help me always? |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mrva...@gmail.com
, Dec 12