How To Get Help

[tanersener]

0. You're free to open issues about anything you want in any format you want. Below are our suggestions to get the best help for your issues, plus to receive a response from the maintainer(s) of this project.

FFmpeg

2. If you have questions about ffmpeg commands, filters, devices, etc. the fastest way to get an answer is to ask google. ffmpeg is a universal, platform independent tool. There are a lot of resources on the web about it. Put the correct search keywords and try the solutions shared by other people.

3. If you can't find the answers using google then try asking them on ffmpeg-user mailing list. There are many ffmpeg developers that are members of that list. They maintain ffmpeg. So, they know a lot more about ffmpeg than we do here. Therefore, we (maintainers) generally don't respond to questions about ffmpeg itself.

4. This project does not modify the original ffmpeg source code. If an ffmpeg feature or component is not working as expected, most probably that problem comes from ffmpeg. Unfortunately, we (maintainers) can't help you with those bugs. If you encounter that kind of errors, our suggestion is to install the desktop version of ffmpeg and validate that the feature/component you use works on desktop. If you create an issue after doing that and tell us that it works on desktop then we can provide a solution. If an ffmpeg issue doesn't include that information (tested on desktop), then we most probably will ignore that report. You can still get a response from other users but now from us (maintainers).

5. If you need more professional help then refer to ffmpeg developers. They are available for contracting work. They know a lot more about ffmpeg than we (maintainers) do here.

FFmpeg-Kit

6. If your issue is specific to ffmpeg-kit then use the Search button at the top first. If there are similar issues reported before or if there is a wiki page about your question it will be listed in the search results.

7. If you can't find the answers using Search then go to Wiki and look at relevant sections about your issue. There are a lot of pages that cover different aspects of the project. Check if your issue is already explained there.

8. ffmpeg-kit releases are tested using the test applications under the ffmpeg-kit-test repository. If an API method, class or package doesn't work in your application, have a look at the test applications for that platform, see how it was used there, run the test applications locally if possible.

9. When none of the above works, then create an issue and select one of the templates provided there. It is crucial to fill out one of those templates. Because we (maintainers) don't have time to ask the standard questions (what did you do, how did you do, where did you do, etc.) in every issue. If we don't see enough information inside an issue, we will not respond to it.

Thanks

[arteevraina]

@tanersener Is there any discord or IRC channel where I can seek help related to FFMPEG Flutter?

[tanersener]

@arteevraina No, everything is here under the github project page.