Skip to content
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

Non-baseline AVC video profile is not supported by Android OS (Android 9.0) #72

Open
ricamgar opened this issue Dec 18, 2018 · 9 comments

Comments

@ricamgar
Copy link

ricamgar commented Dec 18, 2018

Hi,

I am getting this error when trying to compress a video file with Android 9.0.

Fatal error while transcoding, this might be invalid format or bug in engine or Android.
net.ypresto.androidtranscoder.engine.InvalidOutputFormatException: Non-baseline AVC video profile is not supported by Android OS, actual profile_idc: 100

With other versions it works as expected. Any idea why is this happening?
Thanks

@tipa
Copy link

tipa commented Feb 17, 2019

Same issue here :(
Edit: I compiled the project myself, allowing the profile_idc 100 manually (instead of 66 only) and it seems to work. Would there be any sideeffects to this @ypresto or is this safe to use?

@ffMathy
Copy link

ffMathy commented Mar 12, 2019

@tipa can you share the .jar file or show me how to do that by myself? I'm not native to Java environments.

@tipa
Copy link

tipa commented Mar 12, 2019

Sure, you simply need to change this line:


to
if (profileIdc != PROFILE_IDC_BASELINE && profileIdc != 100) {

This is the resulting .jar
lib-release.zip

@ypresto
Copy link
Owner

ypresto commented Mar 23, 2019

#73 (comment)

(Main profile looks supported for now by Android itself, so we can remove restriction by checking Android version.)

@ffMathy
Copy link

ffMathy commented Apr 3, 2019

Thank you so much @ypresto for your time - sounds like you are quite busy.

Does that mean we can remove the if statement entirely?

@martinbertinat
Copy link

Hi there, any updates on this?

Thanks

@ricardoclipit
Copy link

any update on this?

@pengkobe
Copy link

any update?

@AlexTrotsenko
Copy link

The issue seems to be fixed in the latest version of the master.
While it's not perfect, you can get the latest build via JitPack as mentioned in #86.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants