Page 2 of 2

Re: hw-encode opengl output without glReadPixels in 2018 ("fastpath")?

Posted: Tue Oct 02, 2018 4:56 pm
by 6by9
dickon wrote:
Tue Oct 02, 2018 3:44 pm
It's quite astonishing. The work you lot at Pi Towers have done is incredible.

12b 8k p60 H.265 (encode and decode) is all I want from a new Pi. Please :-)
:D :D :D :D :o

Re: hw-encode opengl output without glReadPixels in 2018 ("fastpath")?

Posted: Wed Oct 03, 2018 8:18 am
by tvjon
" I hope my example project on github can help others on that matter...."

It certainly does, thank you. Your README contains helpful info' too.

This entire thread is useful.

Incidentally, only one example,

connection_decode_encode

fails using

-O3 (or2)

-01 works

It builds without errors, but runs thus:

$ ./connection_decode_encode
fourcc: I420, variant; width: 1280, height: 720, (0,0,1280,720)
start transcoding
stop transcoding

so generates an empty out.h264

All the others build & run fine using -O3


$ gcc -v

Using built-in specs.
...
gcc version 6.3.0 20170516 (Raspbian 6.3.0-18+rpi1+deb9u1)

Re: hw-encode opengl output without glReadPixels in 2018 ("fastpath")?

Posted: Wed Oct 03, 2018 8:28 am
by 6by9
Probably the same issue I hit - eos_received isnt initialised so it will randomly immediately abort.