2009-10-15 12:45:16 +03:00
|
|
|
/*
|
|
|
|
* AIFF/AIFF-C muxer
|
|
|
|
* Copyright (c) 2006 Patrick Guimond
|
|
|
|
*
|
2011-03-18 19:35:10 +02:00
|
|
|
* This file is part of Libav.
|
2009-10-15 12:45:16 +03:00
|
|
|
*
|
2011-03-18 19:35:10 +02:00
|
|
|
* Libav is free software; you can redistribute it and/or
|
2009-10-15 12:45:16 +03: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-03-18 19:35:10 +02:00
|
|
|
* Libav is distributed in the hope that it will be useful,
|
2009-10-15 12:45:16 +03: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-03-18 19:35:10 +02:00
|
|
|
* License along with Libav; if not, write to the Free Software
|
2009-10-15 12:45:16 +03:00
|
|
|
* Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
|
|
|
|
*/
|
|
|
|
|
2013-11-23 23:32:55 +03:00
|
|
|
#include <stdint.h>
|
|
|
|
|
2011-11-27 17:04:16 +03:00
|
|
|
#include "libavutil/intfloat.h"
|
2009-10-15 12:45:16 +03:00
|
|
|
#include "avformat.h"
|
2011-11-29 21:28:15 +03:00
|
|
|
#include "internal.h"
|
2009-10-15 12:45:16 +03:00
|
|
|
#include "aiff.h"
|
2011-02-24 08:36:02 +02:00
|
|
|
#include "avio_internal.h"
|
2009-10-15 12:45:16 +03:00
|
|
|
|
2014-09-22 10:19:33 +03:00
|
|
|
typedef struct AIFFOutputContext {
|
2009-10-15 12:45:16 +03:00
|
|
|
int64_t form;
|
|
|
|
int64_t frames;
|
|
|
|
int64_t ssnd;
|
|
|
|
} AIFFOutputContext;
|
|
|
|
|
|
|
|
static int aiff_write_header(AVFormatContext *s)
|
|
|
|
{
|
|
|
|
AIFFOutputContext *aiff = s->priv_data;
|
2011-02-20 12:04:12 +02:00
|
|
|
AVIOContext *pb = s->pb;
|
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 21:42:52 +03:00
|
|
|
AVCodecParameters *par = s->streams[0]->codecpar;
|
2011-11-27 17:04:16 +03:00
|
|
|
uint64_t sample_rate;
|
2009-10-15 12:45:16 +03:00
|
|
|
int aifc = 0;
|
|
|
|
|
|
|
|
/* First verify if format is ok */
|
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 21:42:52 +03:00
|
|
|
if (!par->codec_tag)
|
2009-10-15 12:45:16 +03:00
|
|
|
return -1;
|
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 21:42:52 +03:00
|
|
|
if (par->codec_tag != MKTAG('N','O','N','E'))
|
2009-10-15 12:45:16 +03:00
|
|
|
aifc = 1;
|
|
|
|
|
|
|
|
/* FORM AIFF header */
|
2011-02-24 08:36:02 +02:00
|
|
|
ffio_wfourcc(pb, "FORM");
|
2011-03-03 21:11:45 +02:00
|
|
|
aiff->form = avio_tell(pb);
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, 0); /* file length */
|
2011-02-24 08:36:02 +02:00
|
|
|
ffio_wfourcc(pb, aifc ? "AIFC" : "AIFF");
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
if (aifc) { // compressed audio
|
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 21:42:52 +03:00
|
|
|
par->bits_per_coded_sample = 16;
|
|
|
|
if (!par->block_align) {
|
2009-10-15 12:45:16 +03:00
|
|
|
av_log(s, AV_LOG_ERROR, "block align not set\n");
|
|
|
|
return -1;
|
|
|
|
}
|
|
|
|
/* Version chunk */
|
2011-02-24 08:36:02 +02:00
|
|
|
ffio_wfourcc(pb, "FVER");
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, 4);
|
|
|
|
avio_wb32(pb, 0xA2805140);
|
2009-10-15 12:45:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Common chunk */
|
2011-02-24 08:36:02 +02:00
|
|
|
ffio_wfourcc(pb, "COMM");
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, aifc ? 24 : 18); /* size */
|
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 21:42:52 +03:00
|
|
|
avio_wb16(pb, par->channels); /* Number of channels */
|
2009-10-15 12:45:16 +03:00
|
|
|
|
2011-03-03 21:11:45 +02:00
|
|
|
aiff->frames = avio_tell(pb);
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, 0); /* Number of frames */
|
2009-10-15 12:45:16 +03: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 21:42:52 +03:00
|
|
|
if (!par->bits_per_coded_sample)
|
|
|
|
par->bits_per_coded_sample = av_get_bits_per_sample(par->codec_id);
|
|
|
|
if (!par->bits_per_coded_sample) {
|
2009-10-15 12:45:16 +03:00
|
|
|
av_log(s, AV_LOG_ERROR, "could not compute bits per sample\n");
|
|
|
|
return -1;
|
|
|
|
}
|
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 21:42:52 +03:00
|
|
|
if (!par->block_align)
|
|
|
|
par->block_align = (par->bits_per_coded_sample * par->channels) >> 3;
|
2009-10-15 12:45:16 +03: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 21:42:52 +03:00
|
|
|
avio_wb16(pb, par->bits_per_coded_sample); /* Sample size */
|
2009-10-15 12:45:16 +03: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 21:42:52 +03:00
|
|
|
sample_rate = av_double2int(par->sample_rate);
|
2011-11-27 17:04:16 +03:00
|
|
|
avio_wb16(pb, (sample_rate >> 52) + (16383 - 1023));
|
|
|
|
avio_wb64(pb, UINT64_C(1) << 63 | sample_rate << 11);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
if (aifc) {
|
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 21:42:52 +03:00
|
|
|
avio_wl32(pb, par->codec_tag);
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb16(pb, 0);
|
2009-10-15 12:45:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Sound data chunk */
|
2011-02-24 08:36:02 +02:00
|
|
|
ffio_wfourcc(pb, "SSND");
|
2011-03-03 21:11:45 +02:00
|
|
|
aiff->ssnd = avio_tell(pb); /* Sound chunk size */
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, 0); /* Sound samples data size */
|
|
|
|
avio_wb32(pb, 0); /* Data offset */
|
|
|
|
avio_wb32(pb, 0); /* Block-size (block align) */
|
2009-10-15 12:45:16 +03: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 21:42:52 +03:00
|
|
|
avpriv_set_pts_info(s->streams[0], 64, 1, s->streams[0]->codecpar->sample_rate);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
/* Data is starting here */
|
2011-03-14 21:39:06 +02:00
|
|
|
avio_flush(pb);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int aiff_write_packet(AVFormatContext *s, AVPacket *pkt)
|
|
|
|
{
|
2011-02-20 12:04:12 +02:00
|
|
|
AVIOContext *pb = s->pb;
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_write(pb, pkt->data, pkt->size);
|
2009-10-15 12:45:16 +03:00
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
static int aiff_write_trailer(AVFormatContext *s)
|
|
|
|
{
|
2011-02-20 12:04:12 +02:00
|
|
|
AVIOContext *pb = s->pb;
|
2009-10-15 12:45:16 +03:00
|
|
|
AIFFOutputContext *aiff = s->priv_data;
|
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 21:42:52 +03:00
|
|
|
AVCodecParameters *par = s->streams[0]->codecpar;
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
/* Chunks sizes must be even */
|
|
|
|
int64_t file_size, end_size;
|
2011-03-03 21:11:45 +02:00
|
|
|
end_size = file_size = avio_tell(pb);
|
2009-10-15 12:45:16 +03:00
|
|
|
if (file_size & 1) {
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_w8(pb, 0);
|
2009-10-15 12:45:16 +03:00
|
|
|
end_size++;
|
|
|
|
}
|
|
|
|
|
2011-03-05 22:06:46 +02:00
|
|
|
if (s->pb->seekable) {
|
2009-10-15 12:45:16 +03:00
|
|
|
/* File length */
|
2011-02-28 15:57:54 +02:00
|
|
|
avio_seek(pb, aiff->form, SEEK_SET);
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, file_size - aiff->form - 4);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
/* Number of sample frames */
|
2011-02-28 15:57:54 +02:00
|
|
|
avio_seek(pb, aiff->frames, SEEK_SET);
|
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 21:42:52 +03:00
|
|
|
avio_wb32(pb, (file_size - aiff->ssnd - 12) / par->block_align);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
/* Sound Data chunk size */
|
2011-02-28 15:57:54 +02:00
|
|
|
avio_seek(pb, aiff->ssnd, SEEK_SET);
|
2011-02-21 20:28:17 +02:00
|
|
|
avio_wb32(pb, file_size - aiff->ssnd - 4);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
|
|
|
/* return to the end */
|
2011-02-28 15:57:54 +02:00
|
|
|
avio_seek(pb, end_size, SEEK_SET);
|
2009-10-15 12:45:16 +03:00
|
|
|
|
2011-03-14 21:39:06 +02:00
|
|
|
avio_flush(pb);
|
2009-10-15 12:45:16 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2011-01-26 00:03:28 +02:00
|
|
|
AVOutputFormat ff_aiff_muxer = {
|
2011-07-16 23:18:12 +03:00
|
|
|
.name = "aiff",
|
|
|
|
.long_name = NULL_IF_CONFIG_SMALL("Audio IFF"),
|
|
|
|
.mime_type = "audio/aiff",
|
|
|
|
.extensions = "aif,aiff,afc,aifc",
|
|
|
|
.priv_data_size = sizeof(AIFFOutputContext),
|
2012-08-05 12:11:04 +03:00
|
|
|
.audio_codec = AV_CODEC_ID_PCM_S16BE,
|
|
|
|
.video_codec = AV_CODEC_ID_NONE,
|
2011-07-16 23:18:12 +03:00
|
|
|
.write_header = aiff_write_header,
|
|
|
|
.write_packet = aiff_write_packet,
|
|
|
|
.write_trailer = aiff_write_trailer,
|
2012-04-06 17:50:48 +03:00
|
|
|
.codec_tag = (const AVCodecTag* const []){ ff_codec_aiff_tags, 0 },
|
2009-10-15 12:45:16 +03:00
|
|
|
};
|