2011-04-12 13:59:39 +02:00
|
|
|
/*
|
|
|
|
* xWMA demuxer
|
|
|
|
* Copyright (c) 2011 Max Horn
|
|
|
|
*
|
2011-04-15 04:37:17 +02:00
|
|
|
* This file is part of FFmpeg.
|
2011-04-12 13:59:39 +02:00
|
|
|
*
|
2011-04-15 04:37:17 +02:00
|
|
|
* FFmpeg is free software; you can redistribute it and/or
|
2011-04-12 13:59:39 +02:00
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2.1 of the License, or (at your option) any later version.
|
|
|
|
*
|
2011-04-15 04:37:17 +02:00
|
|
|
* FFmpeg is distributed in the hope that it will be useful,
|
2011-04-12 13:59:39 +02:00
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
2011-04-15 04:37:17 +02:00
|
|
|
* License along with FFmpeg; if not, write to the Free Software
|
2011-04-12 13:59:39 +02:00
|
|
|
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
|
|
|
|
*/
|
|
|
|
|
2011-04-15 13:28:04 +02:00
|
|
|
#include <inttypes.h>
|
2013-11-23 21:32:55 +01:00
|
|
|
#include <stdint.h>
|
2011-04-15 13:28:04 +02:00
|
|
|
|
2011-04-12 13:59:39 +02:00
|
|
|
#include "avformat.h"
|
2011-11-29 19:28:15 +01:00
|
|
|
#include "internal.h"
|
2011-04-12 13:59:39 +02:00
|
|
|
#include "riff.h"
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Demuxer for xWMA, a Microsoft audio container used by XAudio 2.
|
|
|
|
*/
|
|
|
|
|
2014-09-22 09:19:33 +02:00
|
|
|
typedef struct XWMAContext {
|
2011-04-12 13:59:39 +02:00
|
|
|
int64_t data_end;
|
|
|
|
} XWMAContext;
|
|
|
|
|
|
|
|
static int xwma_probe(AVProbeData *p)
|
|
|
|
{
|
|
|
|
if (!memcmp(p->buf, "RIFF", 4) && !memcmp(p->buf + 8, "XWMA", 4))
|
|
|
|
return AVPROBE_SCORE_MAX;
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2012-01-12 13:20:36 +01:00
|
|
|
static int xwma_read_header(AVFormatContext *s)
|
2011-04-12 13:59:39 +02:00
|
|
|
{
|
2012-08-01 01:29:37 +02:00
|
|
|
int64_t size;
|
2014-11-17 00:22:21 +01:00
|
|
|
int ret = 0;
|
2011-04-12 13:59:39 +02:00
|
|
|
uint32_t dpds_table_size = 0;
|
2014-04-29 20:41:58 +02:00
|
|
|
uint32_t *dpds_table = NULL;
|
2011-04-12 13:59:39 +02:00
|
|
|
unsigned int tag;
|
|
|
|
AVIOContext *pb = s->pb;
|
|
|
|
AVStream *st;
|
|
|
|
XWMAContext *xwma = s->priv_data;
|
|
|
|
int i;
|
|
|
|
|
|
|
|
/* The following code is mostly copied from wav.c, with some
|
|
|
|
* minor alterations.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* check RIFF header */
|
|
|
|
tag = avio_rl32(pb);
|
|
|
|
if (tag != MKTAG('R', 'I', 'F', 'F'))
|
|
|
|
return -1;
|
|
|
|
avio_rl32(pb); /* file size */
|
|
|
|
tag = avio_rl32(pb);
|
|
|
|
if (tag != MKTAG('X', 'W', 'M', 'A'))
|
|
|
|
return -1;
|
|
|
|
|
|
|
|
/* parse fmt header */
|
|
|
|
tag = avio_rl32(pb);
|
|
|
|
if (tag != MKTAG('f', 'm', 't', ' '))
|
|
|
|
return -1;
|
|
|
|
size = avio_rl32(pb);
|
2011-06-18 11:43:24 +02:00
|
|
|
st = avformat_new_stream(s, NULL);
|
2011-04-12 13:59:39 +02:00
|
|
|
if (!st)
|
|
|
|
return AVERROR(ENOMEM);
|
|
|
|
|
2016-04-10 21:58:15 +02:00
|
|
|
ret = ff_get_wav_header(s, pb, st->codecpar, size, 0);
|
2011-04-12 17:44:20 +02:00
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
2011-04-12 13:59:39 +02:00
|
|
|
st->need_parsing = AVSTREAM_PARSE_NONE;
|
|
|
|
|
|
|
|
/* All xWMA files I have seen contained WMAv2 data. If there are files
|
|
|
|
* using WMA Pro or some other codec, then we need to figure out the right
|
|
|
|
* extradata for that. Thus, ask the user for feedback, but try to go on
|
|
|
|
* anyway.
|
|
|
|
*/
|
2016-04-10 21:58:15 +02:00
|
|
|
if (st->codecpar->codec_id != AV_CODEC_ID_WMAV2 &&
|
|
|
|
st->codecpar->codec_id != AV_CODEC_ID_WMAPRO) {
|
2017-03-27 21:31:46 +02:00
|
|
|
avpriv_request_sample(s, "Unexpected codec (tag %s; id %d)",
|
|
|
|
av_fourcc2str(st->codecpar->codec_tag),
|
|
|
|
st->codecpar->codec_id);
|
2011-04-12 13:59:39 +02:00
|
|
|
} else {
|
|
|
|
/* In all xWMA files I have seen, there is no extradata. But the WMA
|
|
|
|
* codecs require extradata, so we provide our own fake extradata.
|
|
|
|
*
|
|
|
|
* First, check that there really was no extradata in the header. If
|
2011-04-15 09:43:15 +02:00
|
|
|
* there was, then try to use it, after asking the user to provide a
|
2011-04-12 13:59:39 +02:00
|
|
|
* sample of this unusual file.
|
|
|
|
*/
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
if (st->codecpar->extradata_size != 0) {
|
2011-04-12 13:59:39 +02:00
|
|
|
/* Surprise, surprise: We *did* get some extradata. No idea
|
|
|
|
* if it will work, but just go on and try it, after asking
|
|
|
|
* the user for a sample.
|
|
|
|
*/
|
2013-02-25 23:54:28 +01:00
|
|
|
avpriv_request_sample(s, "Unexpected extradata (%d bytes)",
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->codecpar->extradata_size);
|
2016-04-10 21:58:15 +02:00
|
|
|
} else if (st->codecpar->codec_id == AV_CODEC_ID_WMAPRO) {
|
|
|
|
if (ff_alloc_extradata(st->codecpar, 18))
|
2015-10-25 17:37:17 +01:00
|
|
|
return AVERROR(ENOMEM);
|
|
|
|
|
2016-04-10 21:58:15 +02:00
|
|
|
memset(st->codecpar->extradata, 0, st->codecpar->extradata_size);
|
|
|
|
st->codecpar->extradata[ 0] = st->codecpar->bits_per_coded_sample;
|
|
|
|
st->codecpar->extradata[14] = 224;
|
2011-04-12 13:59:39 +02:00
|
|
|
} else {
|
2016-04-10 21:58:15 +02:00
|
|
|
if (ff_alloc_extradata(st->codecpar, 6))
|
2011-04-12 13:59:39 +02:00
|
|
|
return AVERROR(ENOMEM);
|
|
|
|
|
2016-04-10 21:58:15 +02:00
|
|
|
memset(st->codecpar->extradata, 0, st->codecpar->extradata_size);
|
2011-04-12 13:59:39 +02:00
|
|
|
/* setup extradata with our experimentally obtained value */
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->codecpar->extradata[4] = 31;
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
if (!st->codecpar->channels) {
|
2012-03-21 18:58:07 +01:00
|
|
|
av_log(s, AV_LOG_WARNING, "Invalid channel count: %d\n",
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->codecpar->channels);
|
2012-03-21 18:58:07 +01:00
|
|
|
return AVERROR_INVALIDDATA;
|
|
|
|
}
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
if (!st->codecpar->bits_per_coded_sample) {
|
2012-03-21 18:58:07 +01:00
|
|
|
av_log(s, AV_LOG_WARNING, "Invalid bits_per_coded_sample: %d\n",
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->codecpar->bits_per_coded_sample);
|
2012-03-21 18:58:07 +01:00
|
|
|
return AVERROR_INVALIDDATA;
|
|
|
|
}
|
|
|
|
|
2011-04-12 13:59:39 +02:00
|
|
|
/* set the sample rate */
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
avpriv_set_pts_info(st, 64, 1, st->codecpar->sample_rate);
|
2011-04-12 13:59:39 +02:00
|
|
|
|
|
|
|
/* parse the remaining RIFF chunks */
|
|
|
|
for (;;) {
|
2014-04-29 20:48:03 +02:00
|
|
|
if (pb->eof_reached) {
|
|
|
|
ret = AVERROR_EOF;
|
2014-11-17 00:22:21 +01:00
|
|
|
goto fail;
|
2014-04-29 20:48:03 +02:00
|
|
|
}
|
2011-04-12 13:59:39 +02:00
|
|
|
/* read next chunk tag */
|
|
|
|
tag = avio_rl32(pb);
|
|
|
|
size = avio_rl32(pb);
|
|
|
|
if (tag == MKTAG('d', 'a', 't', 'a')) {
|
|
|
|
/* We assume that the data chunk comes last. */
|
|
|
|
break;
|
|
|
|
} else if (tag == MKTAG('d','p','d','s')) {
|
|
|
|
/* Quoting the MSDN xWMA docs on the dpds chunk: "Contains the
|
|
|
|
* decoded packet cumulative data size array, each element is the
|
|
|
|
* number of bytes accumulated after the corresponding xWMA packet
|
2011-04-15 09:43:15 +02:00
|
|
|
* is decoded in order."
|
2011-04-12 13:59:39 +02:00
|
|
|
*
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
* Each packet has size equal to st->codecpar->block_align, which in
|
2011-04-12 13:59:39 +02:00
|
|
|
* all cases I saw so far was always 2230. Thus, we can use the
|
|
|
|
* dpds data to compute a seeking index.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* Error out if there is more than one dpds chunk. */
|
|
|
|
if (dpds_table) {
|
|
|
|
av_log(s, AV_LOG_ERROR, "two dpds chunks present\n");
|
2014-04-29 20:48:03 +02:00
|
|
|
ret = AVERROR_INVALIDDATA;
|
2014-11-17 00:22:21 +01:00
|
|
|
goto fail;
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Compute the number of entries in the dpds chunk. */
|
|
|
|
if (size & 3) { /* Size should be divisible by four */
|
2011-04-15 13:28:04 +02:00
|
|
|
av_log(s, AV_LOG_WARNING,
|
|
|
|
"dpds chunk size %"PRId64" not divisible by 4\n", size);
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
dpds_table_size = size / 4;
|
|
|
|
if (dpds_table_size == 0 || dpds_table_size >= INT_MAX / 4) {
|
2011-04-15 13:28:04 +02:00
|
|
|
av_log(s, AV_LOG_ERROR,
|
|
|
|
"dpds chunk size %"PRId64" invalid\n", size);
|
2014-04-29 20:44:07 +02:00
|
|
|
return AVERROR_INVALIDDATA;
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Allocate some temporary storage to keep the dpds data around.
|
|
|
|
* for processing later on.
|
|
|
|
*/
|
2015-04-11 13:51:03 +02:00
|
|
|
dpds_table = av_malloc_array(dpds_table_size, sizeof(uint32_t));
|
2011-04-12 13:59:39 +02:00
|
|
|
if (!dpds_table) {
|
|
|
|
return AVERROR(ENOMEM);
|
|
|
|
}
|
|
|
|
|
|
|
|
for (i = 0; i < dpds_table_size; ++i) {
|
|
|
|
dpds_table[i] = avio_rl32(pb);
|
|
|
|
size -= 4;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
avio_skip(pb, size);
|
|
|
|
}
|
|
|
|
|
|
|
|
/* Determine overall data length */
|
2014-04-29 20:48:03 +02:00
|
|
|
if (size < 0) {
|
|
|
|
ret = AVERROR_INVALIDDATA;
|
2014-11-17 00:22:21 +01:00
|
|
|
goto fail;
|
2014-04-29 20:48:03 +02:00
|
|
|
}
|
2011-04-12 13:59:39 +02:00
|
|
|
if (!size) {
|
|
|
|
xwma->data_end = INT64_MAX;
|
|
|
|
} else
|
|
|
|
xwma->data_end = avio_tell(pb) + size;
|
|
|
|
|
|
|
|
|
|
|
|
if (dpds_table && dpds_table_size) {
|
|
|
|
int64_t cur_pos;
|
|
|
|
const uint32_t bytes_per_sample
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
= (st->codecpar->channels * st->codecpar->bits_per_coded_sample) >> 3;
|
2011-04-12 13:59:39 +02:00
|
|
|
|
|
|
|
/* Estimate the duration from the total number of output bytes. */
|
|
|
|
const uint64_t total_decoded_bytes = dpds_table[dpds_table_size - 1];
|
2012-11-15 00:56:33 +01:00
|
|
|
|
2013-09-28 22:13:26 +02:00
|
|
|
if (!bytes_per_sample) {
|
|
|
|
av_log(s, AV_LOG_ERROR,
|
|
|
|
"Invalid bits_per_coded_sample %d for %d channels\n",
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->codecpar->bits_per_coded_sample, st->codecpar->channels);
|
2014-04-29 20:48:03 +02:00
|
|
|
ret = AVERROR_INVALIDDATA;
|
2014-11-17 00:22:21 +01:00
|
|
|
goto fail;
|
2012-11-15 00:56:33 +01:00
|
|
|
}
|
|
|
|
|
2011-04-12 13:59:39 +02:00
|
|
|
st->duration = total_decoded_bytes / bytes_per_sample;
|
|
|
|
|
|
|
|
/* Use the dpds data to build a seek table. We can only do this after
|
|
|
|
* we know the offset to the data chunk, as we need that to determine
|
|
|
|
* the actual offset to each input block.
|
|
|
|
* Note: If we allowed ourselves to assume that the data chunk always
|
|
|
|
* follows immediately after the dpds block, we could of course guess
|
|
|
|
* the data block's start offset already while reading the dpds chunk.
|
|
|
|
* I decided against that, just in case other chunks ever are
|
|
|
|
* discovered.
|
|
|
|
*/
|
|
|
|
cur_pos = avio_tell(pb);
|
|
|
|
for (i = 0; i < dpds_table_size; ++i) {
|
|
|
|
/* From the number of output bytes that would accumulate in the
|
|
|
|
* output buffer after decoding the first (i+1) packets, we compute
|
|
|
|
* an offset / timestamp pair.
|
|
|
|
*/
|
|
|
|
av_add_index_entry(st,
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
cur_pos + (i+1) * st->codecpar->block_align, /* pos */
|
|
|
|
dpds_table[i] / bytes_per_sample, /* timestamp */
|
|
|
|
st->codecpar->block_align, /* size */
|
|
|
|
0, /* duration */
|
2011-04-12 13:59:39 +02:00
|
|
|
AVINDEX_KEYFRAME);
|
|
|
|
}
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
} else if (st->codecpar->bit_rate) {
|
2011-04-12 13:59:39 +02:00
|
|
|
/* No dpds chunk was present (or only an empty one), so estimate
|
|
|
|
* the total duration using the average bits per sample and the
|
|
|
|
* total data length.
|
|
|
|
*/
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
st->duration = (size<<3) * st->codecpar->sample_rate / st->codecpar->bit_rate;
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
|
2014-11-17 00:22:21 +01:00
|
|
|
fail:
|
2011-04-12 13:59:39 +02:00
|
|
|
av_free(dpds_table);
|
|
|
|
|
2014-04-29 20:48:03 +02:00
|
|
|
return ret;
|
2011-04-12 13:59:39 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
static int xwma_read_packet(AVFormatContext *s, AVPacket *pkt)
|
|
|
|
{
|
|
|
|
int ret, size;
|
|
|
|
int64_t left;
|
|
|
|
AVStream *st;
|
|
|
|
XWMAContext *xwma = s->priv_data;
|
|
|
|
|
|
|
|
st = s->streams[0];
|
|
|
|
|
|
|
|
left = xwma->data_end - avio_tell(s->pb);
|
|
|
|
if (left <= 0) {
|
|
|
|
return AVERROR_EOF;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* read a single block; the default block size is 2230. */
|
lavf: replace AVStream.codec with AVStream.codecpar
Currently, AVStream contains an embedded AVCodecContext instance, which
is used by demuxers to export stream parameters to the caller and by
muxers to receive stream parameters from the caller. It is also used
internally as the codec context that is passed to parsers.
In addition, it is also widely used by the callers as the decoding (when
demuxer) or encoding (when muxing) context, though this has been
officially discouraged since Libav 11.
There are multiple important problems with this approach:
- the fields in AVCodecContext are in general one of
* stream parameters
* codec options
* codec state
However, it's not clear which ones are which. It is consequently
unclear which fields are a demuxer allowed to set or a muxer allowed to
read. This leads to erratic behaviour depending on whether decoding or
encoding is being performed or not (and whether it uses the AVStream
embedded codec context).
- various synchronization issues arising from the fact that the same
context is used by several different APIs (muxers/demuxers,
parsers, bitstream filters and encoders/decoders) simultaneously, with
there being no clear rules for who can modify what and the different
processes being typically delayed with respect to each other.
- avformat_find_stream_info() making it necessary to support opening
and closing a single codec context multiple times, thus
complicating the semantics of freeing various allocated objects in the
codec context.
Those problems are resolved by replacing the AVStream embedded codec
context with a newly added AVCodecParameters instance, which stores only
the stream parameters exported by the demuxers or read by the muxers.
2014-06-18 20:42:52 +02:00
|
|
|
size = (st->codecpar->block_align > 1) ? st->codecpar->block_align : 2230;
|
2011-04-12 13:59:39 +02:00
|
|
|
size = FFMIN(size, left);
|
|
|
|
|
|
|
|
ret = av_get_packet(s->pb, pkt, size);
|
|
|
|
if (ret < 0)
|
|
|
|
return ret;
|
|
|
|
|
|
|
|
pkt->stream_index = 0;
|
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
|
|
|
AVInputFormat ff_xwma_demuxer = {
|
2011-07-16 22:18:12 +02:00
|
|
|
.name = "xwma",
|
|
|
|
.long_name = NULL_IF_CONFIG_SMALL("Microsoft xWMA"),
|
|
|
|
.priv_data_size = sizeof(XWMAContext),
|
|
|
|
.read_probe = xwma_probe,
|
|
|
|
.read_header = xwma_read_header,
|
|
|
|
.read_packet = xwma_read_packet,
|
2011-04-12 13:59:39 +02:00
|
|
|
};
|