I have used ffmpeg and mp4box to create a non-adaptive mpeg-dash, and I am
doing it by using only one bitrate in each video (its just a test). here is
my demo link. my video has a delay about 15 seconds and its so bad for my
purpose. why am I having this delay?? is it a buffering problem?? I would
On Feb 25, 2017 9:35 PM, "JD" wrote:
I retried to use this flag as it was indicated in a previous response by a
user.
Sorry that I was unable to continue on the original thread, because the
gmail web
interface deletes original message sent to this list by the OP, when the OP
On Sun, Feb 26, 2017 at 11:28 AM, JD wrote:
> I retried to use this flag as it was indicated in a previous response by a
> user.
> Sorry that I was unable to continue on the original thread, because the
> gmail web
> interface deletes original message sent to this list by the
I retried to use this flag as it was indicated in a previous response by a
user.
Sorry that I was unable to continue on the original thread, because the
gmail web
interface deletes original message sent to this list by the OP, when the OP
deletes the
response from the list.
So, even though I
Kia ora,
*Andy*: thanks very much for this tip! Will add that filter to the script
as I definitely want to deinterlace.
Do you recommend this over *yadif*, or do I need to combine *scale* with a
deinterlacing filter?
*Kieran*: Hey there! How did I miss that ffmprovisr included that?
Excellent
Hi Katherine!
On Sat, Feb 25, 2017 at 10:54 PM, Katherine Frances
wrote:
> Marton, thank you very much, this is extremely helpful.
>
>
As Marton mentioned, the `p` refers to Planar, and the absence of `p` (as
far as i can tell) suggests Packed - https://ffmpeg.org/doxygen/
Katherine Frances wrote:
ffmpeg -i uncompressed_master.mov -c:v libx264 -pix_fmt yuv420p -c:a
libfdk_aac -b:a 128k access_copy.mp4
If the masters really are interlaced you will slightly break them
doing this.
You need to add -vf scale=interl=1
Additionally ffmpeg git master recently changed
Marton, thank you very much, this is extremely helpful.
Okay, I guess that the output MP4s are actually interlaced, despite the
video stream metadata that MediaInfo reads. Do you think that 'progressive'
is default for libx264 and that's why this metadata property is being added
erroneously?
On Sun, 26 Feb 2017, Katherine Frances wrote:
Hi Martin,
Oh! Thanks for letting me know. I just assumed the conflation of the two
things here.
But then, how are my output videos becoming deinterlaced?
Probably they are not.
Inputs are uncompressed v210 in MOV. They're definitely
Hi Martin,
Oh! Thanks for letting me know. I just assumed the conflation of the two
things here.
But then, how are my output videos becoming deinterlaced?
Inputs are uncompressed v210 in MOV. They're definitely interlaced, as
they're digitized from an analogue source (using an AJA ADC) with all
On Sun, 26 Feb 2017, Katherine Frances wrote:
Hi all,
When transcoding to H.264 from an interlaced 4:2:2 original, I always add
the flag *-pix_fmt yuv420p*, which obviously achieves two goals:
i. Chroma subsampling scheme: 4:2:2 -> 4:2:0
ii. Scan: interlaced -> progressive.
I'm interested in
To be clear, the MediaInfo specs quoted refer to the deinterlaced output
file.
On Sun, Feb 26, 2017 at 10:50 AM, Katherine Frances
wrote:
> Hi all,
>
> When transcoding to H.264 from an interlaced 4:2:2 original, I always add
> the flag *-pix_fmt yuv420p*, which obviously
Hello to everyone, I'm new in this forum. I would like to please help me to
solve a need. I have several ip cameras in different locations, I want to
get via rtsp to the live video stream for several cameras to send the
multiplexed stream to the main site where a monitoring system is located. I
On Sat, Feb 25, 2017 at 15:41:39 +0100, Moritz Barsnick wrote:
> The '+' sign in front of the flags is not going to work? I disagree.
> ffmpeg's command line parser doesn't care whether the first flag is
> prepended with a '+' or not:
Actually, I found this comment
On Fri, Feb 24, 2017 at 19:36:05 -0700, JD wrote:
> I did not stop the encoding.
> Just opened another gnome-terminal and cd'd to the directory and
> tried to play the unfinished file.
> But now I see that I should not have included the + sign for the
> faststart.
The '+' doesn't matter.
You're
On Fri, Feb 24, 2017 at 21:33:28 -0600, Reuben Martin wrote:
> On Friday, February 24, 2017 8:36:05 PM CST JD wrote:
> > I did not stop the encoding.
> > Just opened another gnome-terminal and cd'd to the directory and
> > tried to play the unfinished file.
> > But now I see that I should not have
16 matches
Mail list logo