<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 16/02/16 10:34, Kingsley Turner
wrote:<br>
</div>
<blockquote cite="mid:56C26095.1040302@krt.com.au" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">On 12/02/16 13:44, Phill Edwards
wrote:<br>
</div>
<blockquote
cite="mid:CAE2RtTMApJLvaX82AfYA7CPhrT04rCL4uwCOZfeNJuh1ncrM4A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">> I
purchased a new receiver in November, an Onkyo TX-NR646.<br>
> I send the signal over HDMI from the nVidia card
through the amp to<br>
> the TV. So the amp handles all the audio, passes
through the video.<br>
> So far that's all sweet.<br>
><br>
> However...<br>
><br>
> Whenever I playback something via mythtv, video
appears immediately on<br>
> the TV, and then there's a 3 to 4 second delay
before sound starts<br>
> up. So if you're watching a music clip, or a TV
show with dialogue at<br>
> the start, you have to rewind to hear the whole
thing.<br>
</blockquote>
<div><br>
</div>
<div>I have the same receiver and I have the exact same
experience. I thought it was just "normal" and the way
it is. If you hear back from Onkyo Support I'd live to
hear what they say.<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Ok, here's what I've found today ...<br>
<br>
Configure pulse audio for your HDMI settings. You might already
have it so, but mine was still pointing at SPDIF.<br>
<br>
And In your /etc/pulse/default.pa comment-out the module that
suspends it on idle:<br>
e.g.:<br>
# load-module module-suspend-on-idle<br>
<br>
Reboot or restart pulse audio. Whatever ensures the new settings
are read.<br>
You can check it with:<br>
# pacmd list-modules | grep -i suspend<br>
There should be no output.<br>
<br>
What seems to be happening (for me), is that even though MythTV is
configured to use alsa:HDMI, it's still doing <something>
with Pulse Audio, and it looks as if Pulse Audio is the thing
sleeping the HDMI connection. So we've configured PA *not* to do
that.<br>
<br>
With this configuration, I now have it down to a ~ 1 second delay
on start.<br>
The HDMI light is always on in the receiver, except when a new
video starts, where it flashes for a second. This is the ~1
second delay.<br>
I guess that something is quickly dropping the HDMI link on
start. Not sure yet. Maybe the interaction between Alsa and PA?<br>
<br>
I did set my MythTV audio output to alsa:default - which uses
pulse audio. This gave me zero delays, but when I tried to play
something with DTS-HD audio, there was no sound, playback was very
jerky, and if I stopped playback, mythtv locked at a black-screen.<br>
<br>
I might do a bit more research on Pulse Audio and DTS, DTS-HD
etc. as this gave a better result.<br>
<br>
I tried killing Pulse Audio, but mythTV frontend shows an error
dialogue and restarts it (even if not configured to use it).<br>
I am kind-of tempted to remove pulse audio totally.<br>
<br>
So, some progress.<br>
<br>
</blockquote>
<br>
After a bit more testing, it seems the start-up delay changes with
respect to the media as well.<br>
But with the above it's better. Some of my media start with only a
split-second delay, but then<br>
stuff like: <a class="moz-txt-link-freetext" href="https://www.youtube.com/watch?v=lkaIoH6Um60">https://www.youtube.com/watch?v=lkaIoH6Um60</a> (3 second
fried prawns) from the local<br>
file-system still has a few seconds delay.<br>
<br>
With audio output set to alsa:default, even using the audio test (in
setup) causes mythfrontend.real to lockup.<br>
Maybe I should start a separate thread on this.<br>
<br>
-kt<br>
<br>
<br>
<br>
<br>
</body>
</html>