It's because you're running as root. Run it as a normal user.quarkjuggler wrote:When I ran your instructions, the last thing it said was:
A simpleThis still requires >64M GPU memory for most video but the amount has
been reduced. SD or smaller video streams may work in 64M, but HD
won't. I recommend 80M (gpu_mem=80 in boot/config.txt) to be on the
safe side. Having said that that will only allow for 1 stream. If you
are playing >1 stream (even transienntly) then you will need more (say
gpu_mem=128). The code should give up cleanly if it cannot allocate a
h/w video decoder and give the stream to old-stle ffmpeg decode, but as
it stands in many cases it thinks it has allocated a decoder cleanly
only to find that it fails when it tries to use it.
There are a few command-line switches - in general you shoudln't use
--mmal-zero-copy By default the decoder copies frames out of
h/w buffers into s/w buffers before giving them to the main part of
chrome. This helps keep the gpu-mem requirement down. If you have
allocated a lot of gpu-mem (say gpu_mem=192) then this will allocate
more gpu frame buffers and use them instead. This is normally faster
but does require quite a lot more gpu mem than the default
--mmal-frame-buffers=<n> Set the number of gpu frame buffers (8M each).
Defaults to 2 or 6 if zero-copy is set. Probably shouldn't be changed.
--mmal-red-pixel Puts a red square in the top left of a frame
decoded by mmal so you can tell that it is active. Doesn't work if
zero-copy is set.
Code: Select all
sudo apt-get update sudo apt-get dist-upgrade sudo rpi-update #For sandboxing, only temporary
Yes. Right in the browser with HW acceleration.gkreidl wrote:Will it work without rpi-update (I just don't want to do this right now)?
My understanding is that without rpi-update the browser will work but only with software video decode.kusti8 wrote:Edit: I thought you said rpi-youtube. It may if you add --no-sandbox but I haven't tried it.
Yeah that's what I thought. I just didn't know if there was any code depending on the newer firmware that wouldn't work anymore with no sandbox and the older, but I guess not.dom wrote:My understanding is that without rpi-update the browser will work but only with software video decode.kusti8 wrote:Edit: I thought you said rpi-youtube. It may if you add --no-sandbox but I haven't tried it.
--no-sandbox should allow hardware video decode to work.
Make sure the RPi-youtube package is installed. The whole point of this is not to require rpi-youtube at all, have it right in the browser will all the speed of rpi-youtubeTrixster wrote:Ok, I've been using your chromium + rpi-YouTube extension for ages and it's been brilliant, so I thought I'd give this update a whirl on my rpi3. All went well following adding dev to the source, an apt-get update and apt-get dist-upgrade and then finally a run_omxplayer.py -U, but now clicking Extract Video on the rpi-YouTube icon does not load up the omxplayer window for full-window video playing. Does this update diasable the rpi-YouTube extension?
This is updated with this version? What does:Trixster wrote:Sorry but you've lost me. I thought your rpi-YouTube was just an extension to get full screen video working through omxplayer. I have that installed and up until updating to this hardware enabled version of chromium that's what I've been using to get full screen video working smoothly. What is this rpi-YouTube package you're talking about? Is that something different?
With everything updated, full screen YouTube videos are still not smooth. There is frequent buffering and stuttering. Gpu mem is 256 (I need that for RetroPie). Is this too little? Too much?
Code: Select all
apt-cache policy chromium-browser apt-cache policy rpi-youtube
What does it say when you run it from the terminal?Trixster wrote:Hi, yes i installed h264ify. I ran apt-get update then apt-get dist-upgrade then rpi-update. I then rebooted and did run_omxplayer.py-U (this is what I've been doing to update rpi-YouTube).
I'm now on version 51.0.2704.91 of chromium.
Rpi-YouTube is 5.1.0-1
Code: Select all
Installed: 51.0.2704.91-0ubuntu0.14.04.1.6000 Candidate: 51.0.2704.91-0ubuntu0.14.04.1.6000 Version table: *** 51.0.2704.91-0ubuntu0.14.04.1.6000 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/dev armhf Packages 100 /var/lib/dpkg/status 51.0.2704.79-0ubuntu0.14.04.1.1121 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/dev armhf Packages 50.0.2661.102-0ubuntu0.14.04.1.1118 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 50.0.2661.102-0ubuntu0.14.04.1.1117 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/dev armhf Packages 49.0.2623.108-0ubuntu0.14.04.1.1113 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 48.0.2564.82-0ubuntu0.15.04.1.1193 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 500 http://dl.bintray.com/pipplware/dists/jessie/main/binary/ ./ Packages 47.0.2526.73-0ubuntu0.15.04.1.1190 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 45.0.2454.85-0ubuntu0.15.04.1.1181 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 500 http://dl.bintray.com/pipplware/dists/jessie/main/binary/ ./ Packages [email protected] ~ $
Code: Select all
rpi-youtube: Installed: 5.1.0-1 Candidate: 5.1.0-1 Version table: *** 5.1.0-1 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 100 /var/lib/dpkg/status 5.0.1-2 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 5.0.0-1 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages 4.0.2-1 0 500 http://dl.bintray.com/kusti8/chromium-rpi/ jessie/main armhf Packages
What's the output of :Trixster wrote:Hi!
omxplayergui ytdl [url] correctly loads omxplayergui and runs videos full screen, however playing a video in youtube and then clicking the rpi-youtube icon at the top right of the window no longer works to bring up the omxplaygui. it's as if the updates to the HW video accelerated version of chromium v51 has disabled this shortcut from working.
Code: Select all
#!/usr/bin/env python import struct import sys import json import subprocess import urllib2 import os VERSION="0.5" def check_update(): new_py = urllib2.urlopen("https://raw.githubusercontent.com/kusti8/RPi-chromium/master/native/run_omxplayer.py").read() old_py = open("/usr/bin/run_omxplayer.py", 'r').read() if new_py != old_py: open("run_omxplayer.py", 'w').write(new_py) subprocess.call("sudo mv run_omxplayer.py /usr/bin/run_omxplayer.py && sudo chmod +x /usr/bin/run_omxplayer.py", shell=True) new_man = urllib2.urlopen("https://raw.githubusercontent.com/kusti8/RPi-chromium/master/native/run_omx.json").read() old_man = open("/etc/chromium-browser/native-messaging-hosts/run_omx.json", 'r') if new_man != old_man: open("run_omx.json", "w").write(new_man) subprocess.call("sudo mv run_omx.json /etc/chromium-browser/native-messaging-hosts/run_omx.json", shell=True) subprocess.call("update-ytdl", shell=True) #open('/home/pi/test', 'w').write(''.join(sys.argv)) if len(sys.argv) > 1: if sys.argv == '-U': check_update() sys.exit(0) else: print "Invalid command line option!\nTo update: run_omxplayer.py -U" sys.exit(0) def read_thread_func(): message_number = 0 # Read the message length (first 4 bytes). text_length_bytes = sys.stdin.read(4) # Unpack message length as 4 byte integer. text_length = struct.unpack('i', text_length_bytes) # Read the text (JSON object) of the message. text = sys.stdin.read(text_length).decode('utf-8') return text url = json.loads(read_thread_func())['text'] FNULL = open(os.devnull, 'w') print 'OK' try: urllib2.urlopen('http://localhost:9192') except: subprocess.Popen(['nohup', 'start_ytdl_server.sh', '&'], stdout=FNULL) subprocess.call("omxplayergui ytdl " + url, shell=True)
Chromium is WebKit based (Blink is a fork of WebKit ) and this patch does pretty much what the patch for WebKit did, although with a more stable browser. I'll try it, but fullscreen should work and there are still a few more improvements planned.DavidS wrote:At least on the RPi 2 the accelerated WebKit browsers have no trouble playing 1080i youtube videos full screen on a screen resolution of [email protected] And that is using the HTML5 player in WebKit (accelerated for the RPi)..