I don't want to hide the x264 settings. If this is part of the bitstream,
are all decoders going to understand it? Will it be used in some way? For
decoders that do not understand it, will it cause issues or will it be
ignored?
Thanks
On Mon, Apr 13, 2015 at 4:47 PM, Kieran Kunhya kier...@obe.tv
Ok, thank you for the info.
On Mon, Apr 13, 2015 at 5:22 PM, Kieran Kunhya kier...@obe.tv wrote:
On 13 April 2015 at 12:49, Kamaldeep Tumkur kamaldeep.tum...@gmail.com
wrote:
I don't want to hide the x264 settings. If this is part of the bitstream,
are all decoders going to understand
Hello,
I have an mov file encoded as an mp4 MBR stream at 3-4 different bitrates
with x264 encoding.
Is there a way for me to remove the x264 specific metadata from the MDAT
box of the mp4? Right now, my MDAT has the following as the first few
bytes. Is this length accounted for as part of MDAT
I have an mpeg4 transcoded from an mov source that has the following:
Stream #0:0(eng): Video: h264 (Constrained Baseline) (avc1 / 0x31637661),
yuv420p(tv, bt709), 480x270 [SAR 1:1 DAR 16:9], 462 kb/s, 25 fps, 25 tbr,
12800 tbn, 50 tbc (default)
Why is tbn value so high? Why do the tbc and tbn
Thanks for the detailed answer. Needs no more clarifications. I will pursue
such questions on the user list.
Thanks
On Mon, Apr 13, 2015 at 7:09 PM, Jean First jeanfi...@gmail.com wrote:
On Mon Apr 13 2015 15:30:03 GMT+0200 (CEST), Kamaldeep Tumkur wrote:
I have an mpeg4 transcoded from
Hi All,
I am trying to use the HLSContext struct inside ffmpeg.c, in order to
have access to the context's send_buffer_size value. However, the
context struct is only defined inside hlsenc.c.
Is there a specific reason for hlsenc not to have a header file? Are
there any other options I may be
led on? AVFormatContext->priv_data cast as an
HTTPContext? What if I wanted to use AVClass to verify that the class
name and only then proceed with reading the option? Thanks again.
Kamal
On Fri, Jan 13, 2017 at 3:21 PM, wm4 <nfx...@googlemail.com> wrote:
> On Fri, 13 Jan 2017 14:35:09 +0530
>
On Fri, Jan 13, 2017 at 4:51 PM, wm4 <nfx...@googlemail.com> wrote:
> On Fri, 13 Jan 2017 16:04:57 +0530
> Kamaldeep Tumkur <kamaldeep.tum...@gmail.com> wrote:
>
>> Thanks a lot for explaining this. I do see now that the needed
>> metadata is being set on t
Hello,
Is there a possibility to provide the option to write vstats info from
an encoding session remotely, say to another DB or to memory from
where it can be handled by another process.
The only possibility for consuming vstats info in real-time seems to
be to have some kind of watch+notifier
