Update database format to cover gain and frame timings #94
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds documentation for the gain and peak format in mixer params, and new info on the frame & MPEG frame timings for cues.
for more information, see https://pre-commit.ci
|
@dylanljones Is there a manual action that needs triggering to update readthedocs? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds documentation for the gain and peak format in mixer params, and new info on the frame & MPEG frame timings for cues.
Quick summary: a "frame" means 1/150th of a second (6.666ms) and is always filled out. This is the timing in "real" audio. However, when rekordbox comes across a VBR or ABR encoded MP3 (or, rather, MPEG file in general, since MP4 can also be variable bit rate) it adds some additional data to help with seeking, since getting exactly the same audio to play when you seek to a timestamp isn't quite as simple in VBR/ABR. The "MPEG frame" isn't the frame index within the MP3 file, but rather a different timing scheme that's roughly 1/75th of a second (13.333ms) per frame. It also stores a byte offset, which isn't the exact offset of the frame internally but is probably the location where it starts scanning for the correct frame inside the file.