Can't see why MFX_ERR_ABORTED happens

Can't see why MFX_ERR_ABORTED happens

I've been implementing the transcoding engine based on API 3.1 and the demo code of 'simple_5_transcode_opaque - async - vppresize' application.

By visual inspection so far, it looks to me that the recipe has been tightly followed in terms of what happens when. The value of asyncDepth has also been chosen to match the demo code (i.e. asyncDepth=4).

However, the execution encounters the problem. When the execution runs out of all the available 'Tasks', the attempt to synchronize the session results with MFX_ERR_ABORTED. Before that, the transcoding seems to run smooth (based on the return values). The attached log file illustrates the details.

Any hint/suggestion as to what might have been the cause of this problem is highly appreciated.

Downloadtext/plain mfx-err-aborted-log.txt1.2 KB
2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.


Can you try using the tracer.exe application (in the <install dir>\tools\mediasdk_tracer director) to capture a log of the MediaSDK API calls?  The log file may provide some insight.


Leave a Comment

Please sign in to add a comment. Not a member? Join today