-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log callbacks for FFprobe includes the executionId of a previous async FFmpeg execution #1
Labels
android
Affect Android platform
apple
Affect Apple platforms
bug
Something isn't working
development-branch
Affects development branch
fixed-in-v4.4
Fixed in release v4.4
library
Affects the library
mobile-ffmpeg
Originates from MobileFFmpeg
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Fixed in |
tanersener
added
development-branch
Affects development branch
bug
Something isn't working
mobile-ffmpeg
Originates from MobileFFmpeg
android
Affect Android platform
apple
Affect Apple platforms
library
Affects the library
and removed
bug
Something isn't working
labels
Apr 30, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
android
Affect Android platform
apple
Affect Apple platforms
bug
Something isn't working
development-branch
Affects development branch
fixed-in-v4.4
Fixed in release v4.4
library
Affects the library
mobile-ffmpeg
Originates from MobileFFmpeg
Current Behaviour
When the same thread calls
Config.ffmpegExecute()
first andFFprobe.execute()
later, log callbacks received forFFprobe
includes the executionId of the ffmpeg execution.Expected Behaviour
FFprobe
does not support async operations. So, log callbacks forFFprobe
should always have executionId = 0.Environment
This issue originates from
MobileFFmpeg v4.4
andv4.4.LTS
, affects all platforms includingreact-native
andflutter
plugins based onMobileFFmpeg
.The text was updated successfully, but these errors were encountered: