You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all transcodeVideo methods in MediaTranscoder are async methods. However, there are many situations where a synchronous method might be preferable. IntentServices and Handlers with their own HanderThread are two that quickly come to mind. Would you be open to a PR to add a synchronous method? I was thinking of pretty much copying/pasting the current work that transcodeVideo does, like so:
I figure that if you are running this synchronously you know what you are doing and you can handle your own Exceptions/failures. You'll know it was successful when it returned. The only listener call that you might be interested in is for progress?
The text was updated successfully, but these errors were encountered:
I have same issue on app which uses this library. Currently doing patch work with CountDownLatch...
I think it is good idea to provide sync version of methods.
Note that there are some reasons using async interface and thread pool:
Currently, all
transcodeVideo
methods inMediaTranscoder
are async methods. However, there are many situations where a synchronous method might be preferable. IntentServices and Handlers with their own HanderThread are two that quickly come to mind. Would you be open to a PR to add a synchronous method? I was thinking of pretty much copying/pasting the current work thattranscodeVideo
does, like so:I figure that if you are running this synchronously you know what you are doing and you can handle your own Exceptions/failures. You'll know it was successful when it returned. The only listener call that you might be interested in is for progress?
The text was updated successfully, but these errors were encountered: