[miigotu]

Upgraded from #514 to #515 and video output is completely corrupted (with sound). White screen with a few green and pink random squares of different sizes scattered onscreen. All is good until I start the video, and also trying to stop it freezes the pi2, although I can still ssh to reboot. What debug components should I enable to provide a log?

[Milhouse]

Upgraded from #514 to #515 and video output is completely corrupted (with sound). White screen with a few green and pink random squares of different sizes scattered onscreen. All is good until I start the video, and also trying to stop it freezes the pi2, although I can still ssh to reboot.

So the same video plays with #0514, but doesn't play with #0515? Are you able to go back to #0514 and the video plays normally? What type of video is this, live tv or a movie etc.? Where is the video located, locally (on SD card, USB memory stick) or on the network (nfs://, smb:// etc.)?

What debug components should I enable to provide a log?

You don't need to enable any extra component logging at this stage, just upload your debug log when playing this video. Unfortunately sprunge.us (the paste site used by OpenELEC) is currently offline so uploading is a bit more involved than usual - manually upload your log to pastebin.com or xbmclogs.com.

[PhilE]

The mmc clock is locked to 250MHz. This makes it immune to variations in core frequency, but also means you can't get to other SD clock frequencies by varying core_freq.

[Milhouse]

The mmc clock is locked to 250MHz. This makes it immune to variations in core frequency, but also means you can't get to other SD clock frequencies by varying core_freq.

Aha, thanks.

[miigotu]

Upgraded from #514 to #515 and video output is completely corrupted (with sound). White screen with a few green and pink random squares of different sizes scattered onscreen. All is good until I start the video, and also trying to stop it freezes the pi2, although I can still ssh to reboot.

So the same video plays with #0514, but doesn't play with #0515? Are you able to go back to #0514 and the video plays normally? What type of video is this, live tv or a movie etc.? Where is the video located, locally (on SD card, USB memory stick) or on the network (nfs://, smb:// etc.)?

What debug components should I enable to provide a log?

You don't need to enable any extra component logging at this stage, just upload your debug log when playing this video. Unfortunately sprunge.us (the paste site used by OpenELEC) is currently offline so uploading is a bit more involved than usual - manually upload your log to pastebin.com or xbmclogs.com.

Yes, the same video works on #514, but not #515. It is a TV episode over an nfs source. Downgrading makes it work again. Here is the mediainfo output from the video: https://gist.github.com/miigotu/640def1f5345a63ac01a

I'll have to upgrade back to #515 to get a log when the tv is free again.

Edit: Is the 'OpenELEC Dev Updater' add-on usually run a day or two behind? I only see 0513 as latest there so it may have been upgrading from 0512->0513, I'm on a Chris Swan build now so I cant check kodi.old.log -.-

[User 209257]

Here are my results...I haven't had any time with the latest Kodi yet, so I can't speak for stability yet.

Code:

Results
=======
Standard driver:  Avg. Write 15.2 MB/s   Avg. Read 16.4 MB/s   Avg. hdparm 18.02 MB/s  (core_freq=525, force_turbo=1, devel-20150426210607-#0426-g160dc2d)
New SD driver:    Avg. Write 15.47 MB/s   Avg. Read 17.2 MB/s   Avg. hdparm 19.37 MB/s  (dtoverlay=sdhost, core_freq=525, force_turbo=1, devel-20150501221805-#0501-g774f426)

RPI 2 + Patriot 16GB Class 10 -> http://www.patriotmemory.com/product/det...28&type=15 (This may or may not be the same card I'm using, I bought it several years ago and this is the only one on Patriot's site that matches the specs)

Code:

Results
=======
New SD driver + O/C:    Avg. Write 15.87 MB/s   Avg. Read 18.1 MB/s   Avg. hdparm 19.51 MB/s  (dtoverlay=sdhost,overclock_50=63, core_freq=500, force_turbo=1, devel-20150515233111-#0515-g7193a10)
New SD driver + O/C:    Avg. Write 15.27 MB/s   Avg. Read 18.1 MB/s   Avg. hdparm 19.51 MB/s  (dtoverlay=sdhost,overclock_50=66, core_freq=525, force_turbo=1, devel-20150515233111-#0515-g7193a10)

This is what mine tests at with the latest build; any higher results in crashes. Haven't spent any time with it yet, so I can't vouch for stability at these settings other than Kodi started fine and the benchmarks ran Any idea why my core_freq=525 write was slower than 500?

[nikc0069]

If I had the existing a sdhost overlay enabled and am happy with perormance as is, can I just not change any settings in this new build and remain as is? Or do I need to change the overlay parameter to keep the existing setup?

[PhilE]

Good question, and the answer is that you don't need to do anything. The overclock is off by default, and your system will continue to work as before.

[PhilE]

@ahplk - are those numbers repeatable? If so, I don't have an easy answer for you, but it could be a subtle timing difference that ends up making the slower clock more efficient to use.

[slack3r]

About HEVC Pi2 optimizations: are you able to play this stream?

Torrent link:
http://pastebin.com/raw.php?i=yKTSqCu6

P.s.
It's not a piracy content.
Duration: 60 seconds - sorry, but my hardware is too old.
Encoded with:

Code:

ffmpeg -i ../1080p/hd_other_benq_green_island-DWEU.m2ts -f yuv4mpegpipe -an -vf scale=1280:720 -t 61 -v 0 -y - | x265 --preset faster --bframes 0 --merange 10 --crf 25 --y4m --input - -o hd_other_benq_green_island-DWEU.x265.bin

Thanks.

[popcornmix]

About HEVC Pi2 optimizations: are you able to play this stream?

Torrent link:
http://pastebin.com/faF4Ekq4

Struggling to download this. uTorrect gives unable to parse manget URI.[/quote]

[MONSTA]

#514 plays hevc a lot better than before, but still not smooth. 720p stutters if bitrate is above 1000 kbps . CPU 900 MHz (Pi2)

[slack3r]

Struggling to download this. uTorrect gives unable to parse manget URI.

Sorry, magnet was wrong.

Does this work?
http://pastebin.com/yKTSqCu6

[wrxtasy]

#514 plays hevc a lot better than before, but still not smooth. 720p stutters if bitrate is above 1000 kbps . CPU 900 MHz (Pi2)

Yes agreed, HEVC decoding is better than it was previously was but I see about a 1.2Mb/s limit if a clip has fast action scenes. (1Ghz Turbo Overclocked)
Just as a point of interest, all nightly Isengard releases for ARM SoC devices will have the ffmpeg HEVC optimisations as well.

As an example testing on a 1.8Ghz ARM A5 / ODROID-C1 using ffmpeg. HEVC clips that struggle on a 1Ghz Overclocked RPI2 play fine on the OC1. Those with 2Ghz or greater ARM SoC devices that support the NEON parallel processing instructions set will be happy.

[hdmkv]

Curious as to how the ISO support is coming along?

I hope it should be there within the next few days; I'm afraid I've been quite unwell this month, which has delayed it.

WoHoo..

Woo-hoo indeed! Hope you're feeling better deborah.