Hi Trevor,

I agree with you that VC4 is easier to work with - and can be patched if there 
are issues.
But normally you lose the H.264 and MPEG2 HW decoders, and a bunch of audio 
codecs, provided by the userland/omx.
Depending on what you're doing, you may or may not notice the difference. But 
I'm not sure how well you can handle 1080p30 or 1080p60 in H.264 using only 
ffmpeg - if you're using chromium, that's what you should be using I guess.
My personal preference would be to use VC4, and that's what I do most of the 
time, but there is still a limitation for the moment, that I just wanted to 
point out.
And that's why I think we can't do only VC4, and probably have to keep userland 
a while longer.

Cheers,
Herve

-----Original Message-----
From: Trevor Woerner [mailto:twoer...@gmail.com] 
Sent: jeudi 20 avril 2017 09:13
To: Herve Jourdain <herve.jourd...@neuf.fr>
Cc: 'Andreas Müller' <schnitzelt...@googlemail.com>; 'Yocto Project' 
<yocto@yoctoproject.org>
Subject: Re: [yocto] [meta-raspberrypi] gles2 on raspi3

On Thu 2017-04-20 @ 05:41:44 AM, Herve Jourdain wrote:
> Yes, VC4 indeed works for both 32bits and 64bits. It was first introduced  .
> for 32bits, actually Regarding why still using userland: at this point in  .
> time, we have accelerated HW codec (H.264, MPEG2, some audio) only if using.
> userland If one doesn't need that, then VC4 is, in my opinion, the way to  .
> go. Otherwise, userland still needs to be used                             .

What decoder is needed to play youtube videos?

Using Andreas' meta-raspi-light (which removes userland and only uses vc4) I've 
spent the last hour or so watching youtube videos from my raspberrypi3 (32-bit 
build) in chromium, accelerated, with sound (both via the HDMI and the jack), 
both on the big monitor and the 7" waveshare touchscreen. Not to mention I can 
now run openGL and GLESx apps accelerated.

I wasn't able to do that with userland. In fact, it was quite a struggle just 
to get it to build!

Maybe I did something wrong with userland, but vc4 is successful, and certainly 
easier to work with.

-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to