Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #196949 > unrolled thread

Re: Audio - Dummy Output, except for root

Back to article view | Back to linux.debian.user

Contents

  Re: Audio - Dummy Output, except for root Borden Rhodes <jrvp@bordenrhodes.com> - 2018-06-26 16:00 +0200
    Re: Audio - Dummy Output, except for root Kent West <westk@acu.edu> - 2018-06-26 16:10 +0200
      Re: Audio - Dummy Output, except for root Brad Rogers <brad@fineby.me.uk> - 2018-06-26 16:20 +0200
      Re: Audio - Dummy Output, except for root Johann Spies <johann.spies@gmail.com> - 2018-06-26 16:30 +0200
        Re: Audio - Dummy Output, except for root deloptes <deloptes@gmail.com> - 2018-06-26 22:00 +0200
      Re: Audio - Dummy Output, except for root Curt <curty@free.fr> - 2018-06-26 17:00 +0200
      Re: Audio - Dummy Output, except for root Charlie Gibbs <cgibbs@surfnaked.ca> - 2018-06-26 17:40 +0200

#196949 — Re: Audio - Dummy Output, except for root

> In my case. "timidity" was causing my problem. Within X, I did a "sudo kill
> timidity", and immediately my Volume control on the pane of KDE's Plasma
> desktop changed, and the volume control slider produced test clicks. I
> tried purging timidity, but it seems to want to take half of KDE with it,
> so I'm gonna hold off until tomorrow to tinker any more with it.
>
> Whew!

Yessir. The timidity update on 19 June messed up my sound, too. After
a frustrating few hours of troubleshooting I discovered that timidity
is hogging the sound server.

Which brings us to the obvious question of how do you get Pulse to
play nicely with Timidity?

[toc] | [next] | [standalone]

#196950

[Multipart message — attachments visible in raw view] — view raw

On Tue, Jun 26, 2018 at 8:39 AM, Borden Rhodes <jrvp@bordenrhodes.com>
wrote:

> > In my case. "timidity" was causing my problem. Within X, I did a "sudo
> kill
> > timidity", and immediately my Volume control on the pane of KDE's Plasma
> > desktop changed, and the volume control slider produced test clicks. I
> > tried purging timidity, but it seems to want to take half of KDE with it,
> > so I'm gonna hold off until tomorrow to tinker any more with it.
> >
> > Whew!
>
> Yessir. The timidity update on 19 June messed up my sound, too. After
> a frustrating few hours of troubleshooting I discovered that timidity
> is hogging the sound server.
>
> Which brings us to the obvious question of how do you get Pulse to
> play nicely with Timidity?
>
>
This morning I removed "timidity" from the "audio" group, and rebooted. All
seems well for me, but then, I don't use Timidity (to my knowledge - don't
really know what it is). I do notice that a "ps ax | grep timidity" does
not return anything.


-- 
Kent West                    <")))><
Westing Peacefully - http://kentwest.blogspot.com

[toc] | [prev] | [next] | [standalone]

#196951

[Multipart message — attachments visible in raw view] — view raw

On Tue, 26 Jun 2018 09:00:16 -0500
Kent West <westk@acu.edu> wrote:

Hello Kent,

>seems well for me, but then, I don't use Timidity (to my knowledge -
>don't really know what it is). 

A MIDI/MOD file player.

-- 
 Regards  _
         / )           "The blindingly obvious is
        / _)rad        never immediately apparent"
You're not so safe in the safety of your room
Nasty - The Damned

[toc] | [prev] | [next] | [standalone]

#196952

On 26 June 2018 at 16:00, Kent West <westk@acu.edu> wrote:
> On Tue, Jun 26, 2018 at 8:39 AM, Borden Rhodes <jrvp@bordenrhodes.com>
> wrote:
>>
>> > In my case. "timidity" was causing my problem. Within X, I did a "sudo
>> > kill

>>
>> Yessir. The timidity update on 19 June messed up my sound, too. After
>> a frustrating few hours of troubleshooting I discovered that timidity
>> is hogging the sound server.
>>
>> Which brings us to the obvious question of how do you get Pulse to
>> play nicely with Timidity?
>>
>
> This morning I removed "timidity" from the "audio" group, and rebooted. All
> seems well for me, but then, I don't use Timidity (to my knowledge - don't
> really know what it is). I do notice that a "ps ax | grep timidity" does not
> return anything.

I had the same experience.  What solved it for me was to edit
/etc/default/timidity so that timidity does not run as daemon.

That freed my audio-devices.

Regards
Johann
-- 
Because experiencing your loyal love is better than life itself,
my lips will praise you.  (Psalm 63:3)

[toc] | [prev] | [next] | [standalone]

#196961

Johann Spies wrote:

> I had the same experience.  What solved it for me was to edit
> /etc/default/timidity so that timidity does not run as daemon.
> 
> That freed my audio-devices.

Me too, but the question is how we make timidity work with alsa or pulse,
without blocking alsa.

I would like to know this as I use timidity from time to time.

regards

[toc] | [prev] | [next] | [standalone]

#196953

On 2018-06-26, Kent West <westk@acu.edu> wrote:
>>
> This morning I removed "timidity" from the "audio" group, and rebooted. All
> seems well for me, but then, I don't use Timidity (to my knowledge - don't
> really know what it is). I do notice that a "ps ax | grep timidity" does
> not return anything.
>

Seems like a lingering bug.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745373

[toc] | [prev] | [next] | [standalone]

#196956

On 26/06/18 07:00 AM, Kent West wrote:

> This morning I removed "timidity" from the "audio" group, and rebooted.
> All seems well for me, but then, I don't use Timidity (to my knowledge -
> don't really know what it is). I do notice that a "ps ax | grep
> timidity" does not return anything.

Try grep -i - it's officially spelled TiMidity++ because it was designed 
to play MIDI files.  (I see you're using BSD parameters to ps - that 
should work, although since I was raised on SysV I say "ps -ef".)

-- 
cgibbs@surfnaked.ca (Charlie Gibbs)

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web