Closed manast closed 11 years ago
Any progress on this? :)
It is on the top of my priority list for navcodec, and it is very important for the product that I am developing also so it will be fixed soon, but I cannot give a date yet.
On 2012-09-13 04:54, Peter Rekdal wrote:
Any progress on this? :)
-- Reply to this email directly or view it on GitHub [1].
Links:
[1] https://github.com/OptimalBits/navcodec/issues/2#issuecomment-8516920
@manast i dont know what are you doing regarding that but for a work project i implemented an async transcoder using node.js The idea was having "process" events , and transcoding n seconds of playback at a time [ where n was 1 in my case ].. The solution was pretty efficient , I am wondering how do you plan to do it ?
Hello,
well I'm just going to use threads, nothing fancy :).
This is fixed in version 0.2.0
Currently the transcode function is synchronous, which does not work properly in an event driven architecture. Besides, making decoding and encoding asynchronous may improve performance since while one thread is decoding other is encoding, possibly using multiple cores if available.