<div dir="ltr">Why are you concerned with the time for encding a single frame? šIt's probably just the API initializing various data structures on the chip. šIf you're encoding single frames just use jpeg.<div> </div><div>We use libva for real-time encoding at 60fps at 1280x720, with about a 10ms delay on the libva part. šIt does a good job.</div><div> </div><div>The simplest piece of sample code I've seen is the h264encode.c file included in the library. šThere's also the gstreamer-vaapi code, but it's much more spread out over many files:</div> <div> </div><div><a href="http://www.freedesktop.org/software/vaapi/releases/gstreamer-vaapi/">http://www.freedesktop.org/software/vaapi/releases/gstreamer-vaapi/</a> </div><div> </div>What are you planning to output your encoded video to? šYou may want to look into using gstreamer. šFair warning: moost of this stuff is not at the "plug and play" stage.</div> <div class="gmail_extra"> <div class="gmail_quote">On Thu, Mar 27, 2014 at 11:43 AM, Nik Orlov <<a href="mailto:nikitos1550@yandex.ru" target="_blank">nikitos1550@yandex.ru</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello! Thanks for you answer! Do you mean 3840x1080 (yuv420p) size of frame? Real time for me, is all that takes less than 1/25s for encoding one frame (with sending data to gpu and sending it back). In my test I have started two 3840x1080 encodings at on time: <div class="">/h264encode -w 3840 -h 1080 -framecount 2500 -f 25 /h264encode -w 3840 -h 1080 -framecount 2500 -f 25 </div>Ubuntu 13.04 has desktop env, and graphics during encoding was slow, but cpu was less 10%. And I still have about 10ms for 1 frame for each encoding. But, as you see when I encodes 1 frame (or 60 frames, less than 1000 or more) time for 1 frame is very big. Why is it so? And I think it will be a problem with real time encoding :-( Another problem is that it is much diffulty to use encoding via libva (at the moment I have expirience only with liavcodec (ffmpeg lib). Could you advice me some tutorials or c/c++ program examples about h.264 libva encoding? 27.03.2014, 20:11, "Matt Pekar" <<a href="mailto:mpekar@raineyelectronics.com">mpekar@raineyelectronics.com</a>>: <div class="HOEnZb"><div class="h5">> For that size of frame, 20ms is a pretty darn good time IMO. šWe see 10ms (ish) on things in the 1280x720 range. > > Since your input stream is only 25fps, the encoder will be able to provide near real-time output, with just a 20ms delay before writing each frame. > > If you were trying to do 60fps then you wouldn't be able to do "real time" at all since you'd be falling behind 5ms every frame. > > On Thu, Mar 27, 2014 at 5:57 AM, Nik Orlov <<a href="mailto:nikitos1550@yandex.ru">nikitos1550@yandex.ru</a>> wrote: >> Hello! >> >> I have ubuntu-desktop 13.10 amd64 on core i7 4770 (Haswell, HD graphics 4600). >> I have installed vaapi (libva from sources 1.3.0). >> >> There is h264encode test. I have started it: >> >> user@video-ubuntu:~/VAAPI/libva-1.3.0/test/encode$ ./h264encode -w 3840 -h 1080 -framecount 1 -f 25 >> Source frame is 3840x1080 and will code clip to 3840x1088 with crop >> >> INPUT:Try to encode H264... >> INPUT: RateControl š: VBR >> INPUT: Resolution š : 3840x1080, 1 frames >> INPUT: FrameRate š š: 25 >> INPUT: Bitrate š š š: 24883200 >> INPUT: Slieces š š š: 1 >> INPUT: IntraPeriod š: 30 >> INPUT: IDRPeriod š š: 60 >> INPUT: IpPeriod š š : 1 >> INPUT: Initial QP š : 26 >> INPUT: Min QP š š š : 0 >> INPUT: Source YUV š : AUTO generated >> INPUT: Coded Clip š : /tmp/test.264 >> INPUT: Rec š Clip š : Not save reconstructed frame >> >> libva info: VA-API version 0.35.0 >> libva info: va_getDriverName() returns 0 >> libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so >> libva info: Found init function __vaDriverInit_0_35 >> libva info: va_openDriver() returns 0 >> Use profile VAProfileH264High >> Support rate control mode (0x12):CBR CQP >> Support VAConfigAttribEncPackedHeaders >> Support packed sequence headers >> Support packed picture headers >> Support packed misc headers >> Support 1 RefPicList0 and 1 RefPicList1 >> Loading data into surface 15.....Complete surface loading >> š š š |00000000(485835 bytes coded) >> >> PERFORMANCE: š Frame Rate š š š š š : 0.06 fps (1 frames, 16500 ms (16500.00 ms per frame)) >> PERFORMANCE: š Compression ratio š š: 12:1 >> PERFORMANCE: š š UploadPicture š š š: 16444 ms (16444.00, 99.66% percent) >> PERFORMANCE: š š vaBeginPicture š š : 0 ms (0.00, 0.00% percent) >> PERFORMANCE: š š vaRenderHeader š š : 0 ms (0.00, 0.00% percent) >> PERFORMANCE: š š vaEndPicture š š š : 3 ms (3.00, 0.02% percent) >> PERFORMANCE: š š vaSyncSurface š š š: 32 ms (32.00, 0.19% percent) >> PERFORMANCE: š š SavePicture š š š š: 0 ms (0.00, 0.00% percent) >> PERFORMANCE: š š Others š š š š š š : 21 ms (21.00, 0.13% percent) >> (Multithread enabled, the timing is only for reference) >> >> And other way >> >> user@video-ubuntu:~/VAAPI/libva-1.3.0/test/encode$ ./h264encode -w 3840 -h 1080 -framecount 2500 -f 25 >> Source frame is 3840x1080 and will code clip to 3840x1088 with crop >> >> INPUT:Try to encode H264... >> INPUT: RateControl š: VBR >> INPUT: Resolution š : 3840x1080, 2500 frames >> INPUT: FrameRate š š: 25 >> INPUT: Bitrate š š š: 24883200 >> INPUT: Slieces š š š: 1 >> INPUT: IntraPeriod š: 30 >> INPUT: IDRPeriod š š: 60 >> INPUT: IpPeriod š š : 1 >> INPUT: Initial QP š : 26 >> INPUT: Min QP š š š : 0 >> INPUT: Source YUV š : AUTO generated >> INPUT: Coded Clip š : /tmp/test.264 >> INPUT: Rec š Clip š : Not save reconstructed frame >> >> libva info: VA-API version 0.35.0 >> libva info: va_getDriverName() returns 0 >> libva info: Trying to open /usr/local/lib/dri/i965_drv_video.so >> libva info: Found init function __vaDriverInit_0_35 >> libva info: va_openDriver() returns 0 >> Use profile VAProfileH264High >> Support rate control mode (0x12):CBR CQP >> Support VAConfigAttribEncPackedHeaders >> Support packed sequence headers >> Support packed picture headers >> Support packed misc headers >> Support 1 RefPicList0 and 1 RefPicList1 >> Loading data into surface 15.....Complete surface loading >> š š š \00002499(719089 bytes coded) >> >> PERFORMANCE: š Frame Rate š š š š š : 53.70 fps (2500 frames, 46555 ms (18.62 ms per frame)) >> PERFORMANCE: š Compression ratio š š: 11:1 >> PERFORMANCE: š š UploadPicture š š š: 16364 ms (6.55, 35.15% percent) >> PERFORMANCE: š š vaBeginPicture š š : 2 ms (0.00, 0.00% percent) >> PERFORMANCE: š š vaRenderHeader š š : 18 ms (0.01, 0.04% percent) >> PERFORMANCE: š š vaEndPicture š š š : 1098 ms (0.44, 2.36% percent) >> PERFORMANCE: š š vaSyncSurface š š š: 21385 ms (8.55, 45.93% percent) >> PERFORMANCE: š š SavePicture š š š š: 8759 ms (3.50, 18.81% percent) >> PERFORMANCE: š š Others š š š š š š : -1071 ms (1717986.49, 9225574.54% percent) >> (Multithread enabled, the timing is only for reference) >> >> So, when test encodes more frames time for encoding 1 frame is about 20ms. >> Why it is so? >> >> My primary question, if I want to encode video in real time (It means camera sends me frame each 40ms), what time for encoding 1 frame I will get? >> As I understand programm sends some data to GPU, GPU encodes video and then send me encoded data back. >> How much time takes sending data to GPU and back? >> >> Maybe it will possible to encode each frame in real time, or maybe it isn`t possible, but It is possible to keep some buffer (for example for 25 frames - 1 sec of video) and than encode ot very fast. >> >> -- >> îÉË ďŇĚĎ× mailto:<a href="mailto:nikitos1550@yandex.ru">nikitos1550@yandex.ru</a> >> _______________________________________________ >> Libva mailing list >> <a href="mailto:Libva@lists.freedesktop.org">Libva@lists.freedesktop.org</a> >> <a href="http://lists.freedesktop.org/mailman/listinfo/libva" target="_blank">http://lists.freedesktop.org/mailman/listinfo/libva</a> -- îÉË ďŇĚĎ× mailto:<a href="mailto:nikitos1550@yandex.ru">nikitos1550@yandex.ru</a> </div></div></blockquote></div> </div>