Closed GoogleCodeExporter closed 8 years ago
this has got to consume about 500% of your cpu. I can't support this behavior.
Anyway, with other changes to comskip (marking on the fly via RecordingStarted),
this shouldn't be a problem any more.
Original comment by jon.chri...@gmail.com
on 19 Apr 2010 at 9:00
OK. Your response is reasonable & more sane than creating the cpu killing
process I described. I will evaluate the
changes you indicated. I have submitted this request to elgato in order to try
to make the over use of CPU issue
less likely --> http://forums.elgato.com/viewtopic.php?f=122&t=7542
The data of that request in the elgato forum URL is:
Request to intentionally postpose encoding of recordings?
by ab… » 31 Mar 2010, 01:25
Original comment by moh...@gmail.com
on 19 Apr 2010 at 9:06
Original issue reported on code.google.com by
moh...@gmail.com
on 14 Oct 2009 at 8:43