[mythtv-users] .24 Audio results: mixed

[Douglas Peale]

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

On 06/18/2010 07:27 PM, Jean-Yves Avenard wrote:
> Hi
> 
> On 19 June 2010 10:35, Douglas Peale <Douglas_Peale at comcast.net> wrote:
>> If Pulse is stereo only, please stop putting "by default" after it when you try and tell me that. To me "by default" implies I
>> can change it to operate as something other than stereo. "by default" to me means "this is what it will do if you don't do
> 
> This is to do with the pulseaudio server.. The configuration and
> running of pulseaudio is completely outside the scope of mythtv..
> 
> the default configuration file of pulseaudio is done in /etc/pulse

Does this mean that PulseAudio is capable of surround output but MythTV can't send surround to PulseAudio? Or can I change the
PulseAudio configuration to support surround?

> 
> 
>> It is not clear what this option does in the menu. So far the only affect I have been able to determine is that changing it away
>> from stereo enables the selection of dolby digital and dts, and enables digital pass through. I haven't noticed any difference
>> between the 5.1 or 7.1 setting otherwise.
>> Since you tell me I should, I will set it to 5.1.
> 
> I have explained what it does before...
Obviously I did not understand your explanation.

> But you are obviously only reading what you want, and it seems to be a
> very selective filter.

Certainly not by intent.

> 
>>
>> I was mostly just trying to tell you what I as a user did while generating those log file, but ok.
> 
> I haven't looked at your log, because it became clear to me that the
> issues you were seeing were due to you using pulseaudio, and setting
> it for AC3 passthrough, which it can't do

That log file was not generated with PulseAudio, it was generated with ALSA:default since that is the only thing that works for
AC3 passthrough.
PulseAudio was just one of the many things that I tried that did not work.

> 
>> I just tried this setup again, and got the same results I had before
>> I set "Audio output device:" to ALSA:iec958:CARD=Intel,DEV=0
>> "Speaker configuration:" to 5.1
>> Dolby digital checked, DTS checked, PCM/Analog unchecked because I still have no idea what this means.
> 
> That's the right thing to do.

And yet it does not work.

> If you can come with a better explanation than what I put there, I'm all ears..

I'd have to understand it myself before I could come up with an explanation. I'm not there yet.

> 
> As I explained earlier, we are limited to what the software framework
> let you do... Myth can makes some choice, but ultimately it relies on
> the user to enter the proper configuration..
> PCM/Analog as the description said (did you read it?) is there to
> tells myth what the output medium supports: discrete multi-channel PCM
> audio...

I read it but was not enlightened.

> SPDIF only support stereo PCM.

And stereo IS multi-channel. In English, "multi" is a prefix meaning more than one. Stereo is two channels, therefore it is
multi channel.
Perhaps "PCM Surround", or "more than 2 channels of PCM" might be a better way of wording it.


> 
>>
>> The results of this setup are that for channels not sending Dolby digital, it works, for channels sending Dolby digital, I get
>> digital noise.
> 
> Ok... now that's interesting.. and I would like to see the full log of
> mythfrontend running with -v audio and trying to play a 5.1 audio
> stream.
> 
> Also the output of
> aplay -L
> and aplay -l
> 

See attached zip file.
The sequence of events while generating the log file:
run mythfrontend
select liveTV
A channel that was attempting to send AC3 was selected, I got noise.
I changed the channel to one that was not sending AC3, I got sound.
I exited LiveTV
I exited mythfrontend.

>>
>> This is why I keep setting it back to ALSA:default, it is the only setting I have tried that does Dolby digital pass through!
> 
> 
> then use ALSA:default :)
> 
> 
> Do you have to sign all your messages with pgp?
> I doubt anyone would try to pretend they are you when they post to
> mythtv-users :)

If encryption were the default and all e-mails were signed like they should be, I bet that most e-mail reading programs would
hide the signature and complain when it was not there.
I'd rather have the signature there when I don't need it then not have it there when I do.



-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwcQaUACgkQe5tReOauESoRDQCfabGim3vkE5Y3Uga/f9xUR5+2
p9QAn18AcpDPgS7T13VR0MHpsecEzCtN
=JwIq
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Logfiles.zip
Type: application/zip
Size: 9236 bytes
Desc: not available
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100618/33598450/attachment-0001.zip>