Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Documentation for mp3dec_ex_read_frame()?

Open
#103 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
c
Domain
documentation

Research direction

The request is to add the missing README.md documentation for mp3dec_ex_read_frame(). Start by reading the function's declaration and implementation (search the single header for mp3dec_ex_read_frame) and the commit d86f4cbc that added frame_info, focusing on whether frame_info must be reset after mp3dec_ex_seek. Then document the zero-initialization and seek behavior in README.md; done means a newcomer can tell from the README alone how to use frame_info.

Written by the indexing model from the issue text.

Description

It took me a while, but I'm finally updating my Rust bindings: https://github.com/mgeier/minimp3_ex-sys/pull/3

While doing that, I didn't find any documentation of mp3dec_ex_read_frame() in the README.md.

I think its usage is mostly clear from its similarity with mp3dec_ex_read(), but I'm wondering about the exact requirements for the frame_info parameter (which has been added in d86f4cbc9742c45b94cfb3e6cd86b951eeea7e5c).

I understand that it has to be zero-initialized in the beginning, but does it have to be reset at any later point in time?

Especially when seeking, should frame_info be reset after that or not?

Dominant language
C
Stars
2k
Forks
271
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lieff/minimp3

All issues in lieff/minimp3

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.