
seven at seven
May 7, 2012, 5:30 PM
Post #5 of 11
(1010 views)
Permalink
|
|
Re: Is mythfrontend's AirPlay support supposed to be audio-only or audio-and-video?
[In reply to]
|
|
On 8 May 2012 09:32, Jean-Yves Avenard <jyavenard [at] gmail> wrote: > Hi > > On Tuesday, 8 May 2012, Scott Alfter wrote: > > > > > > 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. > > > > 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. > > > then you aren't running the new code. > > > > 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. > > I suggest you upgrade your copy of mythtv then, because significant > work was done on this matter, and A/V sync should be pretty much spot > on. > > Note that's there's a bug with iOS right now. Whenever you pause or > seek; the audio move forward about 50ms. So if you > pause/play/pause/play 20 times, you'll be 1s ahead of the video. > The bug shows up with an airport express too. I spent several days > tracking that issue thinking that the problem was in our code, when in > fact it's iOS getting their timestamp wrong > > > > > 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. > > I agree. But what one can find useful, another may not. > JY > Possibly this bug was fixed in 5.1.1? http://www.theregister.co.uk/2012/05/07/ios_five_dot_one_dot_one/ Cheers, Anthony
|