<br><br><div class="gmail_quote">On 8 May 2012 09:32, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com" target="_blank">jyavenard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<div class="im"><br>
On Tuesday, 8 May 2012, Scott Alfter wrote:<br>
><br>
><br>
> I've gotten my problem sorted out. Setting MYTHTV_AIRPLAY in either (1) /etc/local.d/mythfrontend.start or (2) ~/.ratpoisonrc wasn't working. I ended up creating a short shell script that sets MYTHTV_AIRPLAY and then starts mythfrontend.<br>
><br>
> Once that was done, I could stream video podcasts and YouTube videos without issues. IIRC, the output selector shows two devices: one audio/video, the other audio-only.<br>
<br>
<br>
</div>then you aren't running the new code.<br>
<div class="im"><br>
<br>
> In my little bit of experimentation so far, audio and video aren't synchronized when the audio is streamed to the frontend and video remains on the iDevice. Unless that's solvable, I'd think that retaining audio-only output for video playback would be of limited utility.<br>
<br>
</div>I suggest you upgrade your copy of mythtv then, because significant<br>
work was done on this matter, and A/V sync should be pretty much spot<br>
on.<br>
<br>
Note that's there's a bug with iOS right now. Whenever you pause or<br>
seek; the audio move forward about 50ms. So if you<br>
pause/play/pause/play 20 times, you'll be 1s ahead of the video.<br>
The bug shows up with an airport express too. I spent several days<br>
tracking that issue thinking that the problem was in our code, when in<br>
fact it's iOS getting their timestamp wrong<br>
<div class="im"><br>
><br>
> Showing only one device per frontend would be more useful IMHO. The output selector could get crowded pretty quickly if you have multiple frontends each causing two devices to show up.<br>
<br>
</div>I agree. But what one can find useful, another may not.<br>
<span class="HOEnZb"><font color="#888888">JY</font></span><br></blockquote></div><br>Possibly this bug was fixed in 5.1.1?<br><br><a href="http://www.theregister.co.uk/2012/05/07/ios_five_dot_one_dot_one/">http://www.theregister.co.uk/2012/05/07/ios_five_dot_one_dot_one/</a><br>
<br>Cheers,<br><br>Anthony<br>