[pulseaudio-tickets] [PulseAudio] #897: include vumeter samples in the remote protocol

[PulseAudio]

#897: include vumeter samples in the remote protocol
--------------------------+-------------------------------------------------
  Reporter:  brian        |       Owner:  lennart
      Type:  enhancement  |      Status:  new    
 Milestone:               |   Component:  daemon 
Resolution:               |    Keywords:         
--------------------------+-------------------------------------------------

Comment(by brian):

 Replying to [comment:1 coling]:
 > There is:
 >
 >     PA_STREAM_PEAK_DETECT = 0x0800U,
 >     /**< Find peaks instead of resampling. \since 0.9.11 */
 >
 > This is a flag used when connecting your record stream.
 >
 > That said, I'm not sure this cuts down on the data much.

 This does not make any sense to me.  You are trying to tell me that
 measuring and reporting the peak levels of an audio stream will be just as
 much data as actually receiving the audio stream?

 Can you humour me and do the math with me?  If we answer these questions I
 think we can see what the difference is between the bandwidth needed for
 an audio stream and the bandwidth needed to transmit peak measurements of
 such an audio stream.

 What is the bandwidth of a typical audio stream as sent from one PA to
 another?

 What is a reasonable sample rate for the purposes of vumeter display?

 > I'm also not sure if it's something you'd want as you may still want to
 make a spectrum analyser rather than just the simple vumeters in
 pavucontrol.

 Perhaps, but in such a case, there will be no choice but to receive the
 stream.

 Does that invalidate the use-case of wanting peak measurements for simple
 vumeter display?  I don't think so.  I think the vumeter case is quite
 common (as pavucontrol displays) and the spectrum analyser not so much.

 > I suspect that this is unlikely to happen to be honest.

 That's a pity.

 > I think it would be better to just implement a GUI or command line
 option to enable/disable the vumeters as needed.

 Seriously?  The whole vumeter-as-samples thing seems like it's almost
 there already but that there is a bug or something in the implementation.
 Should it really be discarded at this point?

 Why disable the vumeters when they can be implemented efficiently?  That
 seems like throwing the baby out with the bathwater.

-- 
Ticket URL: <http://pulseaudio.org/ticket/897#comment:2>
PulseAudio <http://pulseaudio.org/>
The PulseAudio Sound Server