[kisas]

Thank you! You mean all the files in the folder "target"? such as KERNEL, KERNEL.md5, SYSTEM, SYSTEM.md5?

Install a stable version like 5.0.8 then transfer the testbuild tar file to /storage/.update/ and reboot.

[kisas]

@kisas: These test builds are not disk images. Use an OpenELEC disk image downloaded from the OpenELEC site (5.0.8 or 5.95.1), then once your Pi1/Pi2 is booted copy the latest test build tar file into your Update folder and reboot.

I'm sorry. How to copy the files? Turning on the ssh service and ftp the files? I inserted the microSD card into my macbook, it does not show the folders "Update". Thanks!

[nickr]

No I mean the whole tar file

[parcel]

@kisas: These test builds are not disk images. Use an OpenELEC disk image downloaded from the OpenELEC site (5.0.8 or 5.95.1), then once your Pi1/Pi2 is booted copy the latest test build tar file into your Update folder and reboot.

I'm sorry. How to copy the files? Turning on the ssh service and ftp the files? I inserted the microSD card into my macbook, it does not show the folders "Update". Thanks!

You don't direct work on SDCard. Turn on Pi and access Pi with computer.

[kisas]

No I mean the whole tar file

I unzipped and copied this file to the Update folder on Kodi through FTP: milhouse.build.0523b.tar
However, on startup, it says, Found new tar. but didn't find KERNEL or SYSTEM file. So the system is still 5.0.8. My current system is OpenELEC 5.08

Did I miss any thing? Thanks!

[kisas]

@kisas: These test builds are not disk images. Use an OpenELEC disk image downloaded from the OpenELEC site (5.0.8 or 5.95.1), then once your Pi1/Pi2 is booted copy the latest test build tar file into your Update folder and reboot.

I'm sorry. How to copy the files? Turning on the ssh service and ftp the files? I inserted the microSD card into my macbook, it does not show the folders "Update". Thanks!

You don't direct work on SDCard. Turn on Pi and access Pi with computer.

Thanks! I just learned today to use ssh and SFTP to access Pi.

[kisas]

@kisas: These test builds are not disk images. Use an OpenELEC disk image downloaded from the OpenELEC site (5.0.8 or 5.95.1), then once your Pi1/Pi2 is booted copy the latest test build tar file into your Update folder and reboot.

Thanks for the instructions. I have successfully updated to the new version. However, my problem is still there. I can't use Rapsberry Kodi as an airplay target. I have tried many ways. but still won't work. Is Raspberry Pi2 capable of airplay?

[maratonomak]

I'm not able to download the latest build #0523b, 23-May-2015. Getting 404 Not Found

[Milhouse]

Yes, there will be a new build shortly (uploading now).

[Elky]

[*]MVC and 3D support updates

Latest build should automatically detect 3D MVC files (in mkv and probably mp4 containers) as 3D without having to name the file with 3D.SBS/3D.TAB.
Please test if that behaves correctly for you.

Auto detect works fine, but from build #0522 it is dropping frames all over the place, go back to build #0521 and add the tags back to the file, it will play fine!!

http://sprunge.us/MCZH
(from a clean install)

[maratonomak]

Yes, there will be a new build shortly (uploading now).

Thank you !

[kisas]

anyone can use Raspberry Pi2 as an airplay target?

[nickr]

anyone can use Raspberry Pi2 as an airplay target?

Please, you only asked your question a couple of hours ago.

[wchick132]

anyone can use Raspberry Pi2 as an airplay target?

Yes, test only with iPad 3 with iOS 6, YouTube App is not working despite it shows AirPlay device is available. Also screen mirroring is not possible.

[Milhouse]

Latest build updated to #0523c.

@popcornmix: I'd definitely say there is an improvement with #0523c and HEVC playback, however I'm also seeing a major problem with "Sintel_1080p_27qp_24fps_1aud_9subs.mkv" - with #0522 this would stutter quite noticeably, and although it's now smoother with #0523c, when playing this file repeatedly (play-stop-play-stop etc.) the GPU memory reported by "vcgencmd get_mem reloc" can go haywire.

See bcmstat results - this is a Pi2 with gpu_mem=320. On the first play of Sintel_1080p_27qp_24fps_1aud_9subs.mkv the GPU mem drops to 191MB but returns to 249MB when playback is stopped. When playback is started a second time, GPU mem now drops to 180MB. When playback is stopped a second time at 02:38:34, the reloc memory is reported as 661MB... This isn't reproducible 100% of the time, but I have seen it happen 3 or 4 times so far while testing #0523c.

I've also seen very significant artefact/pixellation when playing the Sintel 1080p mkv with #0523c, again not always but often. However on the plus side, #0523c is definitely smoother than with build #0522 (although #0522 didn't have the artefacts or whacky GPU memory!: )