-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
Change original Playback Framerate #27
Comments
If you mean drop frame, try search skip_frame, skip_loop_filter. |
Thanks. So, there is no use with the ffp_set_max_fps(FFPlayer *ffp, int max_fps); to limit the max fps? |
Most h264 video I've seen, is about 24fps or 30fps. If your video compression parameters is predictable, go ahead to hardcode these options directly. |
Thanks, will give it a try. |
Thanks for your advice. Video playback is ok now. But i got another problem on playback ADPCM audio track. it keeps buffering after 30 to 40. Can i change a lower sample rate or just use mono for audio playback? |
Is it audio only resource? I haven't tested that situation. Search audio_open for sample rate and channel control. |
it's H264/ADPCM. Tried to lower the sample rate and mono audio but still got the same buffering problem. |
BTW, i have found the current display time is outsync with the playback video. Do you know which area should i look at. I have tried to modify the ijkmp_get_current_position() but seems not work. |
Sorry, overlook there is an ffp->av_sync_type options. |
Can you share the test stream? |
Will create an sample stream, can i share to your gmail? |
Just shared an sample stream to your gmail, really appreciate if you can check it out when you have time. The stream format is H264/ADPCM. I am building an android player. |
supported: 6ce6e14 |
feat: add loglevel for java code
Hello,
How I can change the original playback framerate? Do i need to modify the native code or just call a function in the app? Just want to play the high resolution video smoother on low-end devices.
thanks!
The text was updated successfully, but these errors were encountered: