media icon indicating copy to clipboard operation
media copied to clipboard

README for extensions (FFMPEG) is not clear

Open JaroslavHerber opened this issue 1 year ago • 3 comments

The README shows how to build an extension like FFMPEG for some architectures. But what's next? After executing build_ffmpeg.sh it lets the developer in the rain... What are next steps?

Which of those generated files (.../jni/ffmpeg/android-libs/) should be used for the exoplayer? Looks like they are in .a format - but shouldn't it be .so format? So there was an error or some wrong params that aren't mentioned in the README? What to do with them?

I see many other questions from other users about this, but I don't see a (good) solution. It would be nice, if there was an official/clean way to do this.

I know, you don't want to describe basic dev knowledge, how to include modules the right way. But it also looks like "the basic way" is not really practicable with ExoPlayer/Media3. Can you help with this?

JaroslavHerber avatar Jan 10 '24 21:01 JaroslavHerber

Hi @JaroslavHerber,

Have you seen the link in the README page for trouble shooting?

rohitjoins avatar Jan 17 '24 11:01 rohitjoins

Yes. But none of my questions are answered on those page.

JaroslavHerber avatar Feb 05 '24 07:02 JaroslavHerber

The troubleshooting doc mentions about:

You should see .so files appear in the libs subdirectory of the library's path for each supported architecture after following the steps in the README.

Please add any specific question you have on following the README and what specifically you want to be included? Which step is not working or unclear to you?

We try to output errors if any parameters are not defined correctly. Can you add the error that you got when executing ./build_ffmpeg.sh?

rohitjoins avatar Feb 27 '24 14:02 rohitjoins

Hey @JaroslavHerber. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

google-oss-bot avatar Mar 18 '24 01:03 google-oss-bot

Since there haven't been any recent updates here, I am going to close this issue.

@JaroslavHerber if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

google-oss-bot avatar Mar 26 '24 01:03 google-oss-bot