Changes between Initial Version and Version 1 of Ticket #757, comment 2


Ignore:
Timestamp:
Aug 30, 2013, 6:42:19 AM (11 years ago)
Author:
saul

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #757, comment 2

    initial v1  
    11What I suspect may be happening is that the usage of ''videoscale'' in the Gstreamer pipeline causes every accessed frame to be resized while seeking the thumbnail position in the video stream. On slow CPUs (I'm using a 1GHz 686), this processing is taking too much time and triggers a timeout.
    22
    3 I may be completely off-base in this, but I was able to get past this problem in two separate ways. One was by decreasing '''wadsworth_position_callback'''[=#point1 (1)] duration from 30% to 5%. The other was by increasing the '''gobject.timeout_add'''[=#point1 (2)] value from 3000ms to 20000ms.
     3I may be completely off-base in this, but I was able to get past this problem in two separate ways. One was by decreasing the '''wadsworth_position_callback'''[=#point1 (1)] duration from 30% to 5%. The other was by increasing the '''gobject.timeout_add'''[=#point1 (2)] value from 3000ms to 20000ms.
    44
    55The second method resulted in the generation of a socket response error and so I have chosen to go with reducing the wadsworth position value.
    66
    7 If my hypothesis about ''videoscale'' is correct, a potential remedy might be to remove that operation from the Gstreamer pipeline and perform the thumbnail generation on the returned, full-sized frame.
     7If my hypothesis about ''videoscale'' is correct, a potential remedy might be to remove that operation from the Gstreamer pipeline and perform the thumbnail scaling on the returned, full-sized frame.
    88
    99\\