Hi, what can't work? Chromium? or playing youtube full screen through Epiphany?gkreidl wrote:This cannot work, at least not without a workaround, which has never been tried.
While the video is decoded by the GPU, it has to be copied back into the frame buffer in real time to appear inside the window. This does work for medium image sizes, but not for a whole screen.
There are other solutions (but not with epiphany).
I tried "sudo apt-get install chromium-browser" but got a message saying the package was missing, has been obsoleted or is only available from another source. Any ideas where I can get it?Nickcn wrote:...
Because I am using Chromium on my pi3 w/Rasbian-Jessie, to watch youtube videos full screen.
I'm talking about Epiphany. Chromium is not in the repository and I did not want to try install the Ubuntu version.Nickcn wrote:So you are saying you cant watch youtube videos on the pi in Chrome (Chromium)? or are you saying something else?
Because I am using Chromium on my pi3 w/Rasbian-Jessie, to watch youtube videos full screen.
Thanks. I'll give that a try.GTR2Fan wrote:viewtopic.php?f=63&t=121195&hilit=chromium+48
Thank you!Nickcn wrote: Here is chrome (chromium), and it works perfect with the pi3
Overclocking the RPi3 is dangerous and useless. Even without overclocking it starts throttling dramatically if all 4 cores are used (down to 900 MHz in my tests). A heat sink might help a bit (if not boxed in).Nickcn wrote:Overclock pi3 sdram and cpu, and assign more sdram to gpu is my suggestion (that is what I am doing).OK. I gave it a try. Here's the result:
Playing inside the browser window: Video OK, audio out of sync.
Going to full screen (Full HD 1920x1080):
Video lagging and shaky, perhaps 5 - 10 FPS. audio out of sync.
I have no idea why anybody should enjoy watching this.
And I'm running this on a RPi 3!
Code: Select all
sudo nano /boot/config.txtCode: Select all
# uncomment to overclock the arm. 1200 MHz is the default. arm_freq=1350 core_freq=500 over_voltage=4 # uncomment to overclock memory. 400 Mhz is standard. sdram_freq=560 sdram_schmoo=0x02000020 over_voltage_sdram_p=6 over_voltage_sdram_i=4 over_voltage_sdram_c=4 # Memory allocation of 1024MB for graphics processor ("gpu_mem=" should be very last line in config.txt) gpu_mem=256
I does throttle by itself. I have run a test with HandBrake which fully uses all four cores, converting a video. I have been watching temperature and frequency from a terminal all the time (almost an hour). After a very short time, temp. reached 80 C and the system starts throttling down. After a few minutes the freq. was aways between 922 and 960 MHz. The Pi3 is not in a box and receives good air flow.Nickcn wrote:I have maxed out all 4 cores for hours at 1350mhz, without throttling, without heat sinks or fan, using the official pi3 case, and temps never went higher than 65 CEven without overclocking it starts throttling dramatically if all 4 cores are used (down to 900 MHz in my tests).
Slap another 15°C on top of that if you plan on overclocking that GPU and spanking it at the same time and you'll nearly be there. Bear in mind that the internal temperature sensor has been reported as under-reading at the hot end on at least some Pi3B. The proof of the pudding will be if you can run Quake 3 Arena at 1920x1080 without throttling back. I'd like to think it could.Nickcn wrote:I have maxed out all 4 cores for hours at 1350mhz, without throttling, without heat sinks or fan, using the official pi3 case, and temps never went higher than 65 C