** RC1 AV Sync Issue ** -> Read me before upgrade

DDDamian Wrote:RC2 is getting ready to roll out - a quick release to cover some of the overall sync issues this thread covers as well as some specific to ATV1,

wow thats quick indeed waiting with baited breath!

Mike Pisano Wrote:Not completely fixed for me

I've added the Video latency delay and now the videos start in sync, but if I skip forward or back the audio is out of sync again.

While they devs look into this, how do I wget Beta 3 again?

UPDATE:
Never mind Found it - anybpdy else want to roll back, Paste below SSH (Download,install,remove download image,reboot)

Code:

wget http://mirrors.xbmc.org/apt/atv2/deb/org.xbmc.xbmc-atv2_11.0-0~b3_iphoneos-arm.deb
dpkg -i org.xbmc.xbmc-atv2_11.0-0~b3_iphoneos-arm.deb
rm org.xbmc.xbmc-atv2_11.0-0~b3_iphoneos-arm.deb
reboot

HTH - Mike

Another update for any of the devs looking into this.
I believe there is a second issue here.

When this issue surfaced in RC1 I tried using the delay slider in the GUI, but failed to get sync since the value needed was > -15 sec.
After I put the Delay value in the XML file, the video did start correctly, but then went out of sync after skipping forward or back.
I then rolled back to b3 and removed the XML setting and the videos I was testing with worked again, but I noticed last night that after skipping in b3, I was still out of sync again.
What I didn't realize is that the delay slider in the GUI is saved in the database. So I think the second bug is that when XBMC begins playing it dosen't use the prior saved delay, and after a skip it uses it. That explains why both B3 and RC1 with XML start correctly and then mess up after skipping. Reality is, both versions should still start playing out of sync with a -15 saved delay from the GUI.

Im gonna try rolling forward again on one ATV2 and confirm.

bigdogeh Wrote:yes, ssh into your atv2 using root and alpine,

then copy and paste each line individually and hit enter after pasting each line. make sure you give each line time to finish what it's doing before pasting the next line and hitting enter. don't paste all 4 lines together at once.

thanks you, one more question when rc2 comes out do i have to delete the xml file before doing so.

If all you have is the advancedsettings.xml file as described in this thread, then no, you don't need to delete it. It won't matter if you do, however. All it does is sets up the default value that XBMC would use if the file isn't there (the bug was that the default value wasn't initialised in RC1 - RC2 initialises it to zero, same as the XML in this thread).

jmarshall Wrote:If all you have is the advancedsettings.xml file as described in this thread, then no, you don't need to delete it. It won't matter if you do, however. All it does is sets up the default value that XBMC would use if the file isn't there (the bug was that the default value wasn't initialised in RC1 - RC2 initialises it to zero, same as the XML in this thread).

thank you

I copied the text, didn't have an advancedsettings.xml file, so created it and pasted the text in there...

Didn't work...

If you don't already have an advancedsettings.xml file, then the "fix" doesn't work unless you add and enclose it inside the <advancedsettings> tags.

Below is the correct code for people who don't have an existing advancedsettings.xml file.


nm... looks like triple-D's fixed the original post for those of us who can click and try, faster than we can read.

Thanx. Quick fix worked no problem. the playback issue caught me by surprise as well. You guys are overworked and under appreciated.

Please read the first post carefully - there is a link there to just download a ready-made file if you don't have any existing settings, and it works out of the box.

The advancedsettings.xml fixed worked fine on RC1, on RC2 however it seems like I have the same problem again. Less so than on stock RC1, but still there

errornumber419 Wrote:The advancedsettings.xml fixed worked fine on RC1, on RC2 however it seems like I have the same problem again. Less so than on stock RC1, but still there

Now you have the option to actually use the patch that caused the glitch - search forum for a large thread using [Patch] Global AV Delay for details on how to use it!