Re: [pulseaudio-tickets] [PulseAudio] #434: pa_context_subscribe causes memory leaks

[PulseAudio]

#434: pa_context_subscribe causes memory leaks
--+-
  Reporter:  enso...@hora-obscura.de  |   Owner:  lennart
  Type:  defect   |  Status:  closed 
  Priority:  normal   |   Milestone: 
 Component:  libpulse |Severity:  normal 
Resolution:  invalid  |Keywords: 
--+-
Comment (by enso...@hora-obscura.de):

 Confirmed & fixed in cvs. will be released as gst-plugins-good-0.10.12.
 thanks for help.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by brian_j_murrell):

 Replying to [comment:8 coling]:
 > Lennart. Brian seems to be using 0.9.10 now (in other tickets he was
 using 0.9.13).

 Yes, I flirted with 0.9.13 very briefly only to find it didn't solve my
 stuttering and was generally worse with ALSA underruns and so forth.

 > What you are describing here is glitch-free stuff AFAICT...

 Are you referring to Lennart's description in comment #6?

 > (it's a nice description tho', which I'll copy when people ask me :))

 I did think the description in comment #6 was pretty decent too.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by coling):

 Lennart. Brian seems to be using 0.9.10 now (in other tickets he was using
 0.9.13). What you are describing here is glitch-free stuff AFAICT... (it's
 a nice description tho', which I'll copy when people ask me :))

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by brian_j_murrell):

 Just to further update...

 It seems pretty good at the moment. I got rid of one application that was
 spiking the CPU for short periods and it seems much better. The
 application was "preload". I have been on the fence for a while about
 whether that application was worth it's cost.

 I can't even seem to force stuttering now with something fairly heavy on
 both disk i/o and CPU such as:

 {{{
 find /usr -type f | xargs md5sum
 }}}

 I'd hate to think this is just working because I am currently still in the
 "sweet spot".  Do you have any pet/particular torture tests you use to
 test for the sort of problem I am seeing here, even with the HDA
 controller?  My find/md5sum does not seem torturous enough.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by lennart):

 Replying to [comment:4 brian_j_murrell]:

 > I'm certainly not doubting you on this, but for the record of this
 ticket and anyone else who comes across it, why does it work so well with
 just plain ALSA driving it?

 We schedule audio with timer interrupts, not with sound card interrupts --
 which we disable as much as possible. That allows us to variably change
 the wakeup frequency to match what clients that come and go need. This
 kind of scheduling requires the sound driver to provide us with correct
 timing information so that we can properly estimate the wakeup times. This
 is broken in the emu10k driver which causes PA to miscalculate the wakeup
 times based on this wrong data and thus missing the deadlines which you
 can hear as dropouts.

 As long as you only play MP3 music directly on the device and use the
 traditional sound card interrupt based wakeups the bogus timing
 information the sound drivers export doesn't matter. That's why you won't
 notice this issue without PA but it becomes very visible (or audible...)
 when PA is used.

 > as my main audio sound card.  Will I have better luck with that device
 and PA?

 HDA is pretty well supported. Docs are open. A lot of hw has bugs but
 those can usually be worked around. Usually support for HDA should be
 pretty good, and if it isn't it is quickly fixed.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

[pulseaudio-tickets] [PulseAudio] #437: Repetitive error causes pulseaudio to take 50% of the CPU load

[PulseAudio]

#437: Repetitive error causes pulseaudio to take 50% of the CPU load
--+-
 Reporter:  greg0ire  |   Owner:  lennart
 Type:  defect|  Status:  new
 Priority:  normal|   Milestone: 
Component:  padsp |Severity:  normal 
 Keywords:|  
--+-
 Running the following command does not always work, and when it does not,
 I try to interrupt it like this : [[BR]]
 padsp winecfg
 ^Cerr:module:attach_process_dlls "winmm.dll" failed to initialize,
 aborting
 err:module:LdrInitializeThunk Main exe initialization for
 L"C:\\windows\\system32\\winecfg.exe" failed, status c13a[[BR]]
 Then pulseaudio takes half the CPU load and /var/log/messages is filled
 with this message :[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]
 Dec 17 23:34:23 liche pulseaudio[2873]: asyncq.c: q overrun, queuing
 locally[[BR]]

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by brian_j_murrell):

 Replying to [comment:4 brian_j_murrell]:
 > I guess in the meanwhile, I will swap my cards and relegate that EMU10k
 to being
 > my (viop) headset soundcard driven by ALSA directly and use the:
 >
 > {{{
 > 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio
 (rev a2)
 > }}}
 >
 > as my main audio sound card.  Will I have better luck with that device
 and PA?

 It seems not.  It stutters (almost?) as badly, again with nothing logged
 on the output of pulseaudio -.  The stuttering seems to correlate with
 periods of higher CPU activity.

 Also it has other problems.  Reducing the Output Device volume in the PA
 Volume Control to 50% or lower completely mutes the sound.  :-(

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by brian_j_murrell):

 Replying to [comment:3 lennart]:
 > Sorry, but Creative sund cards are unfortunately not well supported on
 Linux.

 Interesting.

 > Creative is very uncooperative and doesn't supply Free Software
 developers with documentation.

 I was not aware that Creative were amongst this crowd.  Unfortunate.

 > The result of this is that only the most basic support for emu10k is
 available and a lot
 > of more advanced stuff that PA needs (like accurate timing) is
 broken/incomplete.

 I'm certainly not doubting you on this, but for the record of this ticket
 and anyone else who comes across it, why does it work so well with just
 plain ALSA driving it?

 > Please blame Creative for that and don't make the mistake to buy
 Creative again.

 Well, I definitely make a point of not buying from companies that engage
 in these tactics and sound cards are cheap and plentiful, so that probably
 won't be difficult.

 I guess in the meanwhile, I will swap my cards and relegate that EMU10k to
 being my (viop) headset soundcard driven by ALSA directly and use the:

 {{{
 00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev
 a2)
 }}}

 as my main audio sound card.  Will I have better luck with that device and
 PA?

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by lennart):

 Sorry, but Creative sund cards are unfortunately not well supported on
 Linux. Creative is very uncooperative and doesn't supply Free Software
 developers with documentation. The result of this is that only the most
 basic support for emu10k is available and a lot of more advanced stuff
 that PA needs (like accurate timing) is broken/incomplete.

 It is well known that PA doesn't work that well on Creative cards. Please
 blame Creative for that and don't make the mistake to buy Creative again.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by brian_j_murrell):

 Replying to [comment:1 lennart]:
 > Which sound card is this? Which driver do you use? Which application are
 you experiencing
 > these problems with? What distribution are you using?

 Yes, indeed.  Some more googling today and it has become apparent to me
 that at minimum the sound card is relevant.  It's a

 {{{
 04:09.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev
 07)
 }}}

 Just about any sound application seems to be subject to the stutter, but
 of course, the most of them are quite transient in their nature (such as
 pidgin, which only chirps [NPI] for a brief moment when messages are
 sent/received) prevalent in use here is rhythmbox, which I have come to
 understand uses gstreamer.  So for your query, gstreamer is probably the
 relevant application.

 I did all kinds of twiddling with default-fragments and default-fragment-
 size-msec (which are configured in daemon.conf at 8 and 10 respectively on
 Ubuntu) but was unable to make things any better.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #398: Assertion 'PA_SINK_INPUT_IS_LINKED(st)' failed

[PulseAudio]

#398: Assertion 'PA_SINK_INPUT_IS_LINKED(st)' failed
---+
  Reporter:  pl4nkton  |   Owner:  lennart 
  Type:  defect|  Status:  closed  
  Priority:  high  |   Milestone:  
 Component:  daemon|Severity:  critical
Resolution:  fixed |Keywords:  
---+
Changes (by lennart):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Fixed in r82f09b6.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #435: severe and frequent stuttering

[PulseAudio]

#435: severe and frequent stuttering
--+-
  Reporter:  brian_j_murrell  |   Owner:  lennart
  Type:  defect   |  Status:  new
  Priority:  normal   |   Milestone: 
 Component:  daemon   |Severity:  major  
Resolution:   |Keywords: 
--+-
Comment (by lennart):

 Which sound card is this? Which driver do you use? Which application are
 you experiencing these problems with? What distribution are you using?

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #400: front-center should not be remixed into rear channels.

[PulseAudio]

#400: front-center should not be remixed into rear channels.
-+--
  Reporter:  Cimi|   Owner:  lennart
  Type:  defect  |  Status:  closed 
  Priority:  normal  |   Milestone:  0.9.14 
 Component:  daemon  |Severity:  normal 
Resolution:  fixed   |Keywords: 
-+--
Changes (by lennart):

  * status:  new => closed
  * resolution:  => fixed

Comment:

 Fixed in r209a8d7.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #343: bsnes does not play well with pulseaudio

[PulseAudio]

#343: bsnes does not play well with pulseaudio
---+
  Reporter:  belegdol  |   Owner:  lennart
  Type:  defect|  Status:  new
  Priority:  normal|   Milestone: 
 Component:  daemon|Severity:  normal 
Resolution:|Keywords: 
---+
Comment (by belegdol):

 byuu (the bsnes author) was kind enough to provide a simple test case. It
 needs some love before it compiles, though.

 {{{
 #include 
 #include 
 #include 

 //PulseAudio simple test -- no error handling
 int main() {
   pa_simple *handle;
   pa_sample_spec spec;
   uint32_t buffer[64];

   spec.format   = PA_SAMPLE_S16LE;
   spec.channels = 2;
   spec.rate = 32000;

   int error = 0;
   handle = pa_simple_new(
 0,   //default server
 "ruby::pulseaudio",  //application name
 PA_STREAM_PLAYBACK,  //direction
 0,   //default device
 "audio", //stream description
 &spec,   //sample format
 0,   //default channel map
 0,   //default buffering attributes
 &error   //error code
   );

   while(true) {
 for(unsigned i = 0; i < 64; i++) {
   int16_t sample = sin(i * 2 * M_PI / 64) * 0x2000;  //may need
 tweaking
   buffer[buffer.offset++] = (sample << 16) | sample;  //left and right
 }
 int error = 0;
 pa_simple_write(handle, (const void*)buffer, 64 * sizeof(uint32_t),
 &error);
   }

   pa_simple_flush(handle, &error);
   pa_simple_free(handle);
   return 0;
 }
 }}}

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #343: bsnes does not play well with pulseaudio

[PulseAudio]

#343: bsnes does not play well with pulseaudio
---+
  Reporter:  belegdol  |   Owner:  lennart
  Type:  defect|  Status:  new
  Priority:  normal|   Milestone: 
 Component:  daemon|Severity:  normal 
Resolution:|Keywords: 
---+
Comment (by belegdol):

 As on the latest version (0.038), bsnes got itself a native Pulseaudio
 driver. It works quite well, but it causes the emulation to stop for a
 moment every few moments. Such behavour is also present in case openal →
 sdl → pa path is used, but it is a little less visible then.
 Uptream claims that the PA driver is extremely simple, and should work
 well:

 {{{
 device.spec.format   = PA_SAMPLE_S16LE;
 device.spec.channels = 2;
 device.spec.rate = settings.frequency;
 device.handle = pa_simple_new(
   0,   //default server
   "ruby::pulseaudio",  //application name
   PA_STREAM_PLAYBACK,  //direction
   0,   //default device
   "audio", //stream description
   &device.spec,//sample format
   0,   //default channel map
   0,   //default buffering attributes
   &error   //error code
 );
 //...
 pa_simple_write(device.handle, (const void*)buffer.data, buffer.offset
 * sizeof(uint32_t), &error);
 }}}
 Any ideas what goes wrong here? This is with PA 0.9.13 on Fedora 10
 x86_64.

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #436: Default RTP Multicast Address

[PulseAudio]

#436: Default RTP Multicast Address
---+
  Reporter:  Sven  |   Owner:  lennart
  Type:  enhancement   |  Status:  new
  Priority:  normal|   Milestone: 
 Component:  module-rtp-*  |Severity:  normal 
Resolution:|Keywords:  multicast, igmp
---+
Changes (by coling):

  * reporter:  coling => Sven

Comment:

 NB Original comment from malaiwah reposted here:

 Configuration file snippet (/etc/pulse/default.pa)

 {{{
 ### On the SENDER side
 load-module module-rtp-send source=rtp.monitor destination=239.255.1.56

 ### On the RECEIVER side
 load-module module-rtp-recv sap_address=239.255.1.56
 }}}

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

[pulseaudio-tickets] [PulseAudio] #436: Default RTP Multicast Address

[PulseAudio]

#436: Default RTP Multicast Address
-+--
 Reporter:  coling   |   Owner:  lennart
 Type:  enhancement  |  Status:  new
 Priority:  normal   |   Milestone: 
Component:  module-rtp-* |Severity:  normal 
 Keywords:  multicast, igmp  |  
-+--
 Hello,

 We use pulseaudio in our LAN and we've noticed that the default Multicast
 IP Address (ie 224.0.0.56) used by the module-rtp-send and module-rtp-recv
 seems to be part of the "well-known" Multicast adresses. As a result, some
 switches (HP Procurve in our case) won't filter the igmp traffic, but will
 broadcast it to all ports. I attached a documentation from HP Procurve
 Networking with better explanations about this on page 100, (4-22).

 We had to change the multicast IP address to resolv that issue. It seems
 that the 239.255.x.x range is dedicated to local multicast diffusion. We
 use 239.255.1.56 and it now works perfectly. My request is to have the
 default multicast IP address changed so that multicast diffusion works in
 all case with all network materials.

 I would be glad to provide more information,[[br]]
 Best regards[[br]]
 Sven Marquilly

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #377: Default RTP Multicast Address

[PulseAudio]

#377: Default RTP Multicast Address
---+
  Reporter:  Sven  |   Owner:  lennart
  Type:  enhancement   |  Status:  new
  Priority:  normal|   Milestone: 
 Component:  module-rtp-*  |Severity:  normal 
Resolution:|Keywords:  multicast, igmp
---+
Changes (by coling):

  * reporter:  smarqui...@acipia.fr => Sven

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #377: Default RTP Multicast Address

[PulseAudio]

#377: Default RTP Multicast Address
---+
  Reporter:  Sven  |   Owner:  lennart
  Type:  enhancement   |  Status:  new
  Priority:  normal|   Milestone: 
 Component:  module-rtp-*  |Severity:  normal 
Resolution:|Keywords:  multicast, igmp
---+
Changes (by coling):

  * reporter:  smarqui...@acipia.fr => Sven

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets

Re: [pulseaudio-tickets] [PulseAudio] #377: Default RTP Multicast Address

[PulseAudio]

#377: Default RTP Multicast Address
---+
  Reporter:  smarqui...@acipia.fr  |   Owner:  lennart
  Type:  enhancement   |  Status:  new
  Priority:  normal|   Milestone: 
 Component:  module-rtp-*  |Severity:  normal 
Resolution:|Keywords:  multicast, igmp
---+
Comment (by Sven):

 Hi Coling,

 Here is my new account, without my email as a username ...
 Thanks for your help

 Sven

 Replying to [comment:4 coling]
 > Hi Sven,
 >
 > I've changed the description but please register for an account here and
 post a new comment with your username rather than your email and I'll use
 that as the value to replace the reported by.
 >
 > I may have to delete your comments to remove the email address from
 those listings.
 >
 > Note that even your comment asking for your email to be removed included
 your email address! Regsiter for a new account if you have to!

-- 
Ticket URL: 
PulseAudio 
The PulseAudio Sound Server
___
pulseaudio-tickets mailing list
pulseaudio-tickets@mail.0pointer.de
https://tango.0pointer.de/mailman/listinfo/pulseaudio-tickets