I just changed from Raspi 2 + OSMC (where everything was working perfectly) to Raspi 3 + OSMC. The latest update is installed (2016.02.04). My power supply is at 5V/2.5A and I thought it should be enough for the Pi 3. I already tried w/ and w/o overclocking.
Problem: When I try to play some 1080p videos I only see the video for about half a second, then the screen stutters to black and the audio stops playing, till after some seconds the video+audio continues for 0.5 seconds and then same thing happens again.
I tried to watch the video directly via the Kodi Vimeo-AddOn and also downloaded it on my PC and tried to play it from a plugged USB-stick on the Pi.
The following video is meant in particular (I didn’t try other 1080p clips so far because this video was working on my Pi 2 and I want to know why it isn’t any more): https://vimeo.com/108679294
Another similar video I downloaded and played via USB has the same issues: https://www.youtube.com/watch?v=4DjdJydl-ds
I made a logfile from the start of OSMC going directly to play the video from a plugged USB drive (http://paste.osmc.io/ifatomales) but didn’t know exactly which parts to log so it could be a little too big, sry.
I already tried searching around the forum+Google for this but I only found problems with video playback via network on the Raspberry Pi 3 and playing it via USB was always considered to work as a solution there.
I have downloaded the Vimeo file and played it without any stutter or glitch on my Pi3.
So if you have a problem it must be related to your setup or hardware.
When you transferred your install from the Pi 2 to Pi 3 did you get new codec licenses and install them ? The codec licenses from your Pi 2 won’t work on another Pi.
It’s unclear from the log whether you are trying to play a file that requires the codecs - for some reason the log does not say what codec the files have, so a Mediainfo of the file you’re trying to play would be helpful.
Sorry I forgot to mention that I purchased+entered the 2 codecs and when I check them via SSH the system says they are both enabled.
Here is a MediaInfo of the file I am trying to watch:
General
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/mp41/isom/avc1)
File size : 101 MiB
Duration : 3mn 19s
Overall bit rate mode : Variable
Overall bit rate : 4 246 Kbps
Encoded date : UTC 2014-10-16 12:14:04
Tagged date : UTC 2014-10-16 12:14:04
Well a clean install did it (same SD card, same Pi3, …).
I did nothing more than entering the codecs so far and it works. Now I’m going to set up everything (updates, menu, Samba, Hyperion, overclocking) to see whether it still works afterwards, but I have no free time this weekend so it will take till monday before I can tell more.
Thank you so far and sorry for wasting your time xD
Why the hell would you need overclocking on a Pi3?
I don’t know exactly, but I installed coolers on my Pi 3 and thought that overclocking is not dangerous or something at all - so why should a bit higher speed be bad?
But back to the original topic: I removed the “solution”-marker because my problem is back and now I can tell a little better what it is caused by. I did all the steps mentioned in my last post and in between I always tested the video playback from USB drive. Everything worked perfectly until I installed Hyperion by executing the following commands (SPI support is enabled in Pi-config)
After I restarted the Pi I had my old problem back as described in the first post. The Ambilight is behaving normal (blue xD) in OSMC menu and the playback works fine again if I stop the Hyperion-service and than start to watch the video, but I am really interested in getting it back to work as it did before on the Pi 2.
Maybe it is indeed just a problem of a too weak power supply, because everything is working as intended if I watch the video from Vimeo in 720p instead of 1080p from the same USB drive.
I changed the USB cable I used to power the Pi and that removed the undervoltage symbol regularly blinking in the top right corner even in OSMC menu, but the 1080p video problem still remains.
Because the maximum speed of a CPU is not infinite…
If you go too high the system will become unstable and crash randomly, this can also lead to data corruption which causes knock on problems as once your file system is corrupted you may have problems that can only be resolved by a re-install.
Overclocking is not dangerous on the Pi in terms of hardware damage as the CPU speed will be throttled back if it gets too hot to stop it going past 85 degrees, however that says nothing about the CPU not crashing.
But one more question (as I am total noob to hyperion): Can you please explain what this grabber-config does, why it didn’t work before and why it does work now on 64x64?
