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

Follow-up: Workaround for libmp4v2 2.0.0 #969

Merged
merged 3 commits into from Jun 23, 2016
Merged

Follow-up: Workaround for libmp4v2 2.0.0 #969

merged 3 commits into from Jun 23, 2016

Conversation

uklotzde
Copy link
Contributor

Some improvements and additional documentation as a follow up for Daniel's bug report and fix:
https://bugs.launchpad.net/mixxx/+bug/1594169

@uklotzde uklotzde changed the title Workaround for libmp4v2 2.0.0 Follow-up: Workaround for libmp4v2 2.0.0 Jun 23, 2016
@@ -40,6 +40,16 @@ const SINT kNumberOfPrefetchFrames = 2112;
// The TrackId is a 1-based index of the tracks in an MP4 file
const u_int32_t kMinTrackId = 1;

// According to various references DecoderConfigDescriptor.bufferSizeDB
// is a 24-bit unsigned integer value.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, the yes data field is able to store 24 bit. That means up to 16 MB buffer for one SampleBlock.
That sounds incredible high. The SampleBlock size from real files is always below 1 KB.
I was hoping we where able to reduce the maximum buffer even more.
How could one design a portable mp4 player if it need to provide up to 16 MB RAM.
But why is the field 24 bit though ... :-/

@daschuer
Copy link
Member

Thank you, for the real good improvements. LGTM
(Waiting for Travis)

@daschuer daschuer merged commit 1ffa46b into mixxxdj:master Jun 23, 2016
@uklotzde uklotzde deleted the mp4v2_workaround branch June 23, 2016 22:48
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

Successfully merging this pull request may close these issues.

None yet

2 participants