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
Crash on export video function on some devices #9
Comments
I am also getting error on export. Attaching the whole error code here: Device: Redmi Note 7S I/flutter (31813): null |
I know which is the problem. I added "preset" and"cr" arguments. In the next update I going to remove the "preset" argument and the API will be test on "min-gpl" package. |
by when will we have the next update? |
Please ping me here once you update the issue, will be waiting. |
I just released the 1.0.3 version. Please use it with the "min-gpl-lts" package |
I am still facing same issues with updated version |
Here is the issue mentioned in another issue: What I think as mentioned in above issue, this is due to the path being modified by ffmpeg execute function. In most devices, especially in Android, there would be many folders containing spaces to their names, then this would be a major issue. Do you think if we can come to any conclusion on this issue or is it beyond your reach as I think it is flutter-ffmpeg issue? |
Yes, It is a flutter-ffmpeg issue. I only created a UI to the FFMPEG commands |
Okay thanks for you efforts though. |
Crashes on export video function on some devices not in particular Android or iOS. In some android devices, it works fine but crashes or gives export error on some android devices. I have only tested in iPad and it works fine so far but not sure if same issue occurs in other iOS devices.
Is there anything to do with package name while installing the pub? I have tried with "full", "full-lts", "video" but no success. Currently with "full" package, I am facing above issue in few devices. So, I understand that there is nothing related to package name as it works well in some devices.
The text was updated successfully, but these errors were encountered: