kim-vde
commented
4 years ago It is not clear to me why you would have a custom extractor.
You could instead have a custom data source that would wrap another data source and read from the second byte of the file. Something like:
public final class CustomDataSource implements DataSource {
private final DefaultDataSource defaultDataSource;
public CustomDataSource(Context context) {
defaultDataSource = new DefaultDataSource(context, Util.getUserAgent(context, "myapp"), false);
}
@Override
public void addTransferListener(TransferListener transferListener) {
defaultDataSource.addTransferListener(transferListener);
}
@Override
public long open(DataSpec dataSpec) throws IOException {
DataSpec newDataSpec = dataSpec.buildUpon().setPosition(dataSpec.position + 2).build();
return defaultDataSource.open(newDataSpec);
}
@Nullable
@Override
public Uri getUri() {
return defaultDataSource.getUri();
}
@Override
public Map<String, List<String>> getResponseHeaders() {
return defaultDataSource.getResponseHeaders();
}
@Override
public void close() throws IOException {
defaultDataSource.close();
}
@Override
public int read(byte[] target, int offset, int length) throws IOException {
return defaultDataSource.read(target, offset, length);
}
}Would that work?
zengcanxiang
[REQUIRED] Searched documentation and issues
https://exoplayer.dev/doc/
implementation 'com.google.android.exoplayer:exoplayer-core:2.11.8'
[REQUIRED] Question
We added some extra bytes to the front of the mp4 file and renamed it.
When playing locally, I don’t want to decrypt the original file to the local first. Therefore, we intend to solve this problem by customizing Extractor and DataSource.
In the custom Extractor, I reused Mp4Extractor for actual reading.
In the sniff method, I skipped the correct number of bytes. The sniff of Mp4Extractor returned true.
But there was an exception of releaseCodec.
// code
A full bug report captured from the device