You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I use DefaultMp4Builder.build on a movie with h264 video track with edits and aac audio track, the resulting mp4 file has its video reduced to a fraction and only the audio playing.
After some investigation, I noticed that the Movie class has this function defined:
public long getTimescale() {
long timescale = this.getTracks().iterator().next().getTrackMetaData().getTimescale();
for (Track track : this.getTracks()) {
timescale = gcd(track.getTrackMetaData().getTimescale(), timescale);
}
return timescale;
}
and the DefaultMp4Builder has this one:
public long getTimescale(Movie movie) {
long timescale = movie.getTracks().iterator().next().getTrackMetaData().getTimescale();
for (Track track : movie.getTracks()) {
timescale = lcm(timescale, track.getTrackMetaData().getTimescale());
}
return timescale;
}
While similar, they differ in logic as the first one uses gdc and the second lcm. DefaultMp4Builder uses in most cases the lcm version, but specifically uses the gcd version in function createEdts:
When I use
DefaultMp4Builder.build
on a movie with h264 video track with edits and aac audio track, the resulting mp4 file has its video reduced to a fraction and only the audio playing.After some investigation, I noticed that the
Movie
class has this function defined:and the
DefaultMp4Builder
has this one:While similar, they differ in logic as the first one uses gdc and the second lcm.
DefaultMp4Builder
uses in most cases the lcm version, but specifically uses the gcd version in functioncreateEdts
:If I override
createEdts
to use the lcm version like this:then I get the expected mp4 file that has the complete video.
Shouldn't
Movie.getTimescale
use lcm too? Or if gcd is the correct behavior there, perhapsDefaultMp4Builder
should use consistently the lcm function?The text was updated successfully, but these errors were encountered: