From: alberto a. g. <alb...@ho...> - 2011-09-19 17:29:53
|
Hello I'm opening a new thread with more questions. Your help has been invaluable so far. Regarding the display timing, yesterday's svn showed the video as fast as it was processed. I have come across a quick workaround which pretty much works for me. It is based on SDL_Delay function which forces the displayto wait 1/FPS. Given the dynamic fps nature of SVC I have thought using NAL indexes MaxTemporalId and TempToDisplay to compute the fraction of original fps (the max) that is used (linked to -tempId input). Roughly: fps_start_time=SDL_GetTicks(); SDL_Display(16, XDIM, YDIM, Y, U, V); current_fps=FPS>>(DqIdNextNal_Nal_o->MaxTemporalId-DqIdNextNal_Nal_o->TempToDisplay); SDL_Delay((unsigned int)1000.0/current_fps-(SDL_GetTicks()-fps_start_time)); However, I experienced two issues. 1- Can't find FPS of the sequence in any header of raw sequences ¿is it there yet? For now is an input parameter.2- With a fps reduction factor of 2 I should expect half the frames. However, it shows ¿repeated? all the framesDepending on decoder_svc_VideoParameter_ImgToDisplay value ([1,2]) there are two paths possible and in my example, theframes are displayed from those code sequences alternatively. I think the frames are repeated. What are the implications of that parameter? Am I getting it right? Any help would be appreciated. Best Regards, Alberto Alvarez |