From: James S. <jst...@gm...> - 2003-04-14 15:00:15
|
Hi Miguel, > xine_fast_memcpy is probably being called from ffmpeg wrapper > or postprocessing code. i don't have libffmpeg/xine_decoder.c > in my data because it was less than 2.5%. Indeed, the postprocessing code uses xine_fast_memcpy. When postprocessing is disabled the ffmpeg wrapper goes back to using xine_fast_memcpy to copy from the ffmpeg buffers into xine frames. > but still the time spent in memcpy gives > an idea of what could be the gain with some kind of direct > rendering to xine frames. I actually have a partly finished patch for doing this very thing somewhere. I didn't get as far as copying in slices and ran into some problems that at the time I couldn't figure out how to solve. I can dig it up if you like? James. |