[mythtv-users] Unexpected interaction between Mythfrontend and K3b

Michael T. Dean mtdean at thirdcontact.com
Wed Oct 26 17:37:14 UTC 2011

On 10/26/2011 12:36 PM, John Pilkington wrote:
> On 26/10/11 16:34, Michael T. Dean wrote:
>> On 10/26/2011 06:52 AM, John Pilkington wrote:
>>> On 26/10/11 10:55, John Pilkington wrote:
>>>> On 26/10/11 09:54, John Veness wrote:
>>>>> On 25/10/2011 13:27, John Pilkington wrote:
>>>>>> Hi:  This is probably not directly related to Mythtv but maybe someone
>>>>>> here will recognise what is going on.
>>>>>> I often burn-and-verify DVD iso images using K3b.  Recently I have found
>>>>>> that if I am watching a recording at the end of either phase of this
>>>>>> process, I lose sound.  I haven't been able to restore it without
>>>>>> restarting playback.
>>>>> I'm just wondering if it's to do with the notification sounds that K3b
>>>>> plays. It might be worth, in K3b, going into Settings, Configure K3b,
>>>>> Notifications, and untick all "Play a sound" boxes.
>>>> Could be. Of late I haven't heard any such sounds, and at first I
>>>> misinterpreted the display.  It seems that I had Notifications enabled
>>>> but with no sound files identified.   Doing things in the top window
>>>> inserted 'ogg' file names below, which I could then enable or not.  Will
>>>> experiment further.   Thanks for the suggestion.
>>> K3b used with no Notifications active, sound playback continued without
>>> interruption. K3b defaults need revising; will add this to KDE bug report.
>> System set up to use PulseAudio but MythTV configured to use ALSA (and,
>> therefore, disabling Pulse), so that when K3b plays a sound using Pulse,
>> it re-enables Pulse?
> Well, I certainly see reports of Pulse Audio resume OK and Pulse Audio
> suspend OK scattered liberally around the frontend log - usually in that
> order and often 200 ms apart.  TBH as long as I can hear something
> acceptable I had given up paying it much attention.  Maybe I'll try
> enabling K3b Notification with file names defined and see what happens;
>    but maybe not - if I'm watching I don't want triumphant fanfares as well.
> It looks as if the undefined file name problem may have been a result of
> upgrading Fedora distributions in-place, with preupgrade wrongly leaving
> an obsolete configuration.  But it still shouldn't have had the effect
> it did.  And there's another coming up soon...

What happens if you change MythTV to use PulseAudio directly instead of 
ALSA?  (And, if that "works"--prevents audio failure during burning, you 
can either use it like that--and likely get those beeps and blings and 
... during playback--or just get rid of PulseAudio completely.)


More information about the mythtv-users mailing list