Answering to myself, in my previous attempt, the second hls output expects
a separate set of transcode process, hence the unable to map stream error.
The better solution would be to use tee to send to multiple outputs,
however the latest git seems to be suffering from this
https://trac.ffmpeg.org/
Slight different command line, i'm trying to produce 2 separate abr streams
with different stream map structures, as well as doing transcoding but that
should not be of any circumstance:
./ffmpeg -ignore_unknown -async 1 -probesize 1M -analyzeduration 100 \
-i "udp://:1234?fifo_size=50
On Fri, Jul 19, 2019 at 09:08:23 -0400, Jim Shupert wrote:
> On 7/19/2019 5:26 AM, Marc Roos wrote:
> > Is there a way to ffmpeg or maybe another tool that detects if video has
> > been re-coded to a higher resolution?
> I have wondered on this as well
> my notion is there is a ' traceable artifact
On Thu, Jul 18, 2019 at 3:13 PM Kieran O Leary
wrote:
> On Thu, 18 Jul 2019, 21:25 William Caulfield, <
> william.caulfi...@contentbridge.tv> wrote:
>
> > I hope I'm getting your intention right here. I had to do this a while
> back
> > for some PAL files. Split the fields, scale, pad, then inter
On Fri, 19 Jul 2019, Carl Eugen Hoyos wrote:
Am Do., 18. Juli 2019 um 22:25 Uhr schrieb William Caulfield
:
I hope I'm getting your intention right here. I had to do this a while back
for some PAL files. Split the fields, scale, pad, then interlace.
-filter_complex
"yadif=1:0,scale=1440:108
Am 19.07.19 um 15:58 schrieb Stéphane Chauveau:
>
> You don't get it. The problem is not that you need a better formula.
> The problem is that some values such as 10.2 cannot be exactly
> represented using floating point values.
>
> For example, let's consider a few examples using the printf buil
oups, i had extra space in command line, actually it works fine with 2nd
stream_map
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.
Am 19.07.19 um 15:51 schrieb Paul B Mahol:
> Really hard to guess something when there is missing information in chain.
Hm, which information is missing in my chain from Fri, 19 Jul 2019
01:21:54 +0300 (EEST)
-Ulf
___
ffmpeg-user mailing list
ffmpeg-u
i tried for live, it took *only the first* var_stream_map...
ffmpeg -v verbose -y -vstats_file stats.txt -re -i 'http://URL.m3u8'
-map 0:v:1 -c:v copy -copyts -start_at_zero -metadata:s:0 language=eng
-map 0:v:2 -c:v copy -copyts -start_at_zero -metadata:s:0 language=eng
-map 0:v:3 -c:v copy -copy
Hi to everybody,
Is it possible to have multiple HLS outputs specified with
different var_stream_map structures ?
Thanks,
Viorel
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-user
To unsubscribe, visit l
On 7/19/19, Ulf Zibis wrote:
>
> Am 19.07.19 um 11:33 schrieb Ulf Zibis:
>>
>> [.]
>>
>> For the 1st catched frame there is "next_dts_time:10.24" and
>> "next_pts_time:10.16". So how can I be sure, that this is the
>> corresponding frame to the output of my filter? :
>> [Parsed_lineshiftrecove
On 7/19/19 3:16 PM, Ulf Zibis wrote:
Using eq() on floating points is indeed a bad idea because of floating
point rounding.
In the code of the select filter I've found:
#define TS2D(ts) ((ts) == AV_NOPTS_VALUE ? NAN : (double)(ts))
select->var_values[VAR_T ] = TS2D(frame->pts) *
av_q2d(i
Am 19.07.19 um 11:33 schrieb Ulf Zibis:
>
> [.]
>
> For the 1st catched frame there is "next_dts_time:10.24" and
> "next_pts_time:10.16". So how can I be sure, that this is the
> corresponding frame to the output of my filter? :
> [Parsed_lineshiftrecover_0 @ 0x55798cbf8f80] frame: 254, pts
Am 19.07.19 um 13:28 schrieb Moritz Barsnick:
> On Fri, Jul 19, 2019 at 13:24:58 +0200, Ulf Zibis wrote:
>> frames but I meant a random collection such as:
>>
>> "select='eq(t\,10.16\,10.2\,10.24\,15.16\,100.5)'"
> Ah, sorry. A list operator. No, no such support.
So what would you think on ..
Wo
Am 19.07.19 um 11:22 schrieb Stéphane Chauveau:
> On 7/19/19 9:18 AM, Moritz Barsnick wrote:
>> On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote:
>>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
>>> select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36
On 7/19/2019 5:26 AM, Marc Roos wrote:
Is there a way to ffmpeg or maybe another tool that detects if video has
been re-coded to a higher resolution?
For instance if I am offered two downloads one 720p and one 1080p. I
have sometimes the impression that the 1080p is just the 720p converted
to 10
On Fri, Jul 19, 2019 at 13:24:58 +0200, Ulf Zibis wrote:
> frames but I meant a random collection such as:
>
> "select='eq(t\,10.16\,10.2\,10.24\,15.16\,100.5)'"
Ah, sorry. A list operator. No, no such support.
Moritz
___
ffmpeg-user mailing list
ffmpeg
Am 19.07.19 um 13:03 schrieb Moritz Barsnick:
> On Fri, Jul 19, 2019 at 12:11:15 +0200, Ulf Zibis wrote:
>> Wouldn't it be comfortable to allow a syntax like
>> "select='eq(t\,10.16\,10.2\,10.24)'" to select a collection of frames?
> That's what Stephance suggested:
>
>> So my advice is to add a 3
Moritz Barsnick (12019-07-19):
> I'm not sure whether expressions actually work with string values,
> though.
The expression parser is very limited and hard to extend. Furthermore,
its API is very inconvenient. If somebody were to rewrite it from
scratch, it would be a great progress. (But do not
On Fri, Jul 19, 2019 at 12:11:15 +0200, Ulf Zibis wrote:
> Wouldn't it be comfortable to allow a syntax like
> "select='eq(t\,10.16\,10.2\,10.24)'" to select a collection of frames?
That's what Stephance suggested:
> So my advice is to add a 3rd digit to your time values and to replace, for
> ins
Am 19.07.19 um 00:21 schrieb Ulf Zibis:
> Hi,
>
> my command is:
> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
> select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36)+eq(t\,10.4)+eq(t\,10.44)+eq(t\,17.52)+eq(t\,47.96)+eq(t\,49.08)+eq(t\,49.2)+eq(t\,55.72)+e
Am 19.07.19 um 11:22 schrieb Stéphane Chauveau:
> On 7/19/19 9:18 AM, Moritz Barsnick wrote:
>> On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote:
>>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
>>> select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36
Am 19.07.19 um 09:18 schrieb Moritz Barsnick:
> On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote:
>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
>> select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36)+eq(t\,10.4)+eq(t\,10.44)+eq(t\,17.52)+eq(t\,47.9
Am 19.07.19 um 08:30 schrieb Carl Eugen Hoyos:
> Am Fr., 19. Juli 2019 um 00:22 Uhr schrieb Ulf Zibis :
>
>> my command is:
>> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4
> If you want support on this mailing list, do not use -v warning
> and post the command line together with the complete,
Is there a way to ffmpeg or maybe another tool that detects if video has
been re-coded to a higher resolution?
For instance if I am offered two downloads one 720p and one 1080p. I
have sometimes the impression that the 1080p is just the 720p converted
to 1080p (not significant better quality).
On 7/19/19 9:18 AM, Moritz Barsnick wrote:
On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote:
./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36)+eq(t\,10.4)+eq(t\,10.44)+eq(t\,17.52)+eq(t\,47.96)+eq(t\,
On Fri, Jul 19, 2019 at 00:21:53 +0200, Ulf Zibis wrote:
> ./ffmpeg -y -v warning -i debug/CYD_1.5m_x264.mp4 -vf
> select='eq(t\,10.16)+eq(t\,10.2)+eq(t\,10.24)+eq(t\,10.28)+eq(t\,10.32)+eq(t\,10.36)+eq(t\,10.4)+eq(t\,10.44)+eq(t\,17.52)+eq(t\,47.96)+eq(t\,49.08)+eq(t\,49.2)+eq(t\,55.72)+eq(t\,83.0
27 matches
Mail list logo
