SPDIF Audio Passthrough unreliable

Bug #538232 reported by DAP
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mythbuntu
Won't Fix
Undecided
Unassigned

Bug Description

Most times when I start MythTV front end, I get no audio. I have found that if I run "sudo /etc/init.d/alsa-utils restart" from a terminal, the audio will start working correctly. If I exit MythTV front end, do something else, then start MythTV front end again, the audio is gone again, and I must re-run "sudo /etc/init.d/alsa-utils restart".
When I get no audio, the receiver usually shows "Dolby D" even if the channel selected never provides Dolby digital. After running the restart, the receiver shows the correct audio signal type for the channel.

I am running the nightly builds of MythTV.
This is using the motherboard audio on an Asus P6T Deluxe motherboard.
Ubuntu 64 bit 9.10

Optical SPDIF
Gigabyte MA790XT-UD4P
Ubuntu 64 bit 9.10

Revision history for this message
Cablman (cablemanrevisited) wrote :

Same exact issue.

description: updated
Revision history for this message
DAP (akadap) wrote :

I just noticed that it is actually coax SPDIF (all the optical inputs were used by other devices on my receiver) I don't think that makes a difference though.

Revision history for this message
Thomas Mashos (tgm4883) wrote :

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that we have turned our efforts to a newer version. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.

Changed in mythbuntu:
status: New → Won't Fix
Revision history for this message
DAP (akadap) wrote : Re: [Bug 538232] Re: SPDIF Audio Passthrough unreliable

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/09/2015 07:09 PM, Thomas Mashos wrote:
> We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of
> reasons. The biggest one is that we have turned our efforts to a newer version. Could you please verify if this issue still
> exists in the latest version?
>
> Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs
> with the newer versions.
>
>
> ** Changed in: mythbuntu Status: New => Won't Fix
>
Ubuntu changed their login system, requiring an Ubuntu1 account (one of the many reasons I no longer use Ubuntu), so I can no
longer log in to launchpad.net.
In the 5 years since I reported this bug, I have since switched to Mint, so I can no longer attempt to reproduce this error.
The thing that discourages me from reporting bugs, is that 5 years after I reported this bug, no-one has even looked at it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iEYEARECAAYFAlSwm2cACgkQe5tReOauESrSXACfQv0L/syP0UPJB9vM8T6uaXd3
IiIAnR70aV9MqHxVdj3/lnMLVAMTgf9a
=lBTz
-----END PGP SIGNATURE-----

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.