_time that /indicates time in terms of ticks of the program’s 90 kHz
clock/, it does not relates to PCR but relates to PTS of video stream.
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/f
On 08.11.2021 16:41, Kieran Kunhya wrote:
On Mon, 8 Nov 2021 at 06:35, Maksym Veremeyenko wrote:
Hi,
Attached patch implement muxing SCTE-35 and EPG packets into mpegts stream.
SCTE Markers need timestamping, no?
SCTE markers has no timestamping, during reading at mpegts.c it
Hi,
Attached patch implement muxing SCTE-35 and EPG packets into mpegts stream.
--
Maksym Veremeyenko
From dc1b87f5e34c688bb3691767f8026a2815aab03e Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Mon, 8 Nov 2021 08:10:59 +0200
Subject: [PATCH] avformat/mpegtsenc: Implement muxing SCTE
On 02.11.2021 12:47, Maksym Veremeyenko wrote:
One of latest commit
https://source.ffmpeg.org/?p=ffmpeg.git;a=commitdiff;h=6f36eb0da71d22aadf8f056f0966bd86656ea57e
claim it fixes endless loop on package generation if muxrate specified
and copyts used. But actually it does not work properly if
On 03.11.2021 11:19, lance.lmw...@gmail.com wrote:
On Tue, Nov 02, 2021 at 05:36:37PM +0200, Maksym Veremeyenko wrote:
On 02.11.2021 16:59, lance.lmw...@gmail.com wrote:
[...]
+if (!ts->first_dts_checked && dts != AV_NOPTS_VALUE) {
+ts->first_pcr += dts * 30
delay if
copyts is
0.
proposed patch extend updating ts->first_pcr not only when copyts is 0
but when copyts is 1 (*-mpegts_copyts 1* specified)
very similar issue i found at
http://ffmpeg.org/pipermail/ffmpeg-devel/2019-April/242766.html
--
Maksym Veremeyenko
_
it.
--
Maksym Veremeyenko
From fff0339c6d764e18fc4ecf111d035095309dc4d4 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Tue, 2 Nov 2021 12:33:54 +0200
Subject: [PATCH] Fix first_pcr initial update
---
libavformat/mpegtsenc.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions
ortfolio/interface-conversion/# ?
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 21.03.2019 13:31, Nicolas George wrote:
Maksym Veremeyenko (12019-03-21):
i just extrapolated your main statement *The work was removed because the
library is 100% closed source and userland.* that should be applied to any
parts of ffmpeg... or not?
Please stop being shifty: what parts of
On 20.03.2019 21:36, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 18:03, Maksym Veremeyenko wrote:
On 20.03.2019 17:37, Jean-Baptiste Kempf wrote:
On Wed, 20 Mar 2019, at 16:35, Martin Vignali wrote:
[...]
We don't talk about a contribution remove for technical reason.
ed because the library is 100% closed source
and userland.
when do you plan to remove nVidia and BlackmagicDesign parts that is
/closed source and userland/ ?
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://
authors should find the core of their hates: either NDI
technology or NewTek company
FYI,
from my experience NewTek and Blackmagic are only two adequate
SDK-for-developers companies that does not requires you signing NDAs and
make it close-source from beginning...
--
Maksym Veremeyenko
On 09.03.2019 22:12, Kieran Kunhya wrote:
They have not responded to any communications:
https://trac.ffmpeg.org/ticket/7589
code you going to remove was not made by you nor NewTek company.
if you have a problem with NewTek company - do a step to solve it - dont
ruin a code.
--
Maksym
21.02.2018 0:39, Carl Eugen Hoyos пише:
2018-02-20 23:35 GMT+01:00 Marton Balint :
On Tue, 20 Feb 2018, Carl Eugen Hoyos wrote:
2018-02-20 17:32 GMT+01:00 Maksym Veremeyenko :
attached patch implement dynamic loading of NewTek library and
drop dependencies from NewTek SDK (if previous
Hi
attached patch implement dynamic loading of NewTek library and drop
dependencies from NewTek SDK (if previous patch with including headers
applied)
please review/comment/apply
--
Maksym Veremeyenko
From 8c0337878bdb8a1ccbc56ede42686e2a4d8e882e Mon Sep 17 00:00:00 2001
From: Maksym
Hi
attached patch add a NewTek NDI headers to source tree.
these headers is under MIT license.
please apply.
--
Maksym Veremeyenko
From 1f0ac55ce4da973f8def3ab24a70381007382cb8 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Tue, 20 Feb 2018 17:14:46 +0200
Subject: [PATCH 1/2] Add
.
NDI sdk has a dynamic library loading method, if it used, then only
headers files required during building binaries.
In this case, which conditions should be applied to headers files? What
text should be provided by owner/manufacturer that allow include it into
the source tree
26.10.2017 16:43, Carl Eugen Hoyos пише:
2017-10-24 12:46 GMT+02:00 Maksym Veremeyenko :
24.10.2017 13:35, developm...@axeltechnology.com пише:
The patch contains trailing whitespace and tabs, both cannot be
committed to the FFmpeg repository.
You can use tools/patcheck to find the issues
proposed early (with more descriptors):
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-April/193395.html
http://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/194829.html
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
06.10.2017 22:10, Marton Balint пише:
On Thu, 5 Oct 2017, Maksym Veremeyenko wrote:
29.09.2017 0:20, Carl Eugen Hoyos пише:
Hi!
I don't have decklink hardware but I assume it never outputs actual
transparency.
Or does it?
it outputs or use internal keyer to put it over passthro
e for *fill* another one for *key*
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
13-16
[...]
get simultaneous fill and key capture and playback ...
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
29.09.2017 0:20, Carl Eugen Hoyos пише:
Hi!
I don't have decklink hardware but I assume it never outputs actual
transparency.
Or does it?
dual link SDI could provide fill/key, some boards could support this
--
Maksym Veremeyenko
___
ffmpeg-
ve an idea what?
clock_audio or clock_video do exactly what you mean - it prevent sending
more packets then realtime.
in my case clock_audio=1, clock_video=1, video_queue=2, audio_queue=2
gives very smooth result. extending queue size make monitoring software
unsync output...
--
Maksym Vereme
code looks fine.
thanks
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
04.09.2017 17:10, Maksym Veremeyenko пише:
Hi,
attached patch implemented threaded NDI output - separate output thread
for each stream. it makes audio preview in my case more smooth.
updated patch allows running audio/video threads separately
please review
--
Maksym Veremeyenko
From
Hi,
move interlacing setting of NDI frame to packet sending function and
take care on field order AV_FIELD_UNKNOWN - take a interlacing settings
from avframe->interlaced_frame
--
Maksym Veremeyenko
From 93dc2a881674d9371963d4555f81c000ceb09bdc Mon Sep 17 00:00:00 2001
From: Mak
Hi,
attached patch add usage example with additional audio packets preparation.
--
Maksym Veremeyenko
From b83e8bb3253f6872d4b50f9bf466bd338a793c99 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Mon, 4 Sep 2017 09:01:18 -0400
Subject: [PATCH 2/3] lavd: add audio packets adopting
Hi,
attached patch implemented threaded NDI output - separate output thread
for each stream. it makes audio preview in my case more smooth.
--
Maksym Veremeyenko
From de4a2cd8688671b730f3d881e4dc73d15b9f067e Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Mon, 4 Sep 2017 08:53:29
27.08.2017 19:13, Marton Balint пише:
On Fri, 25 Aug 2017, Maksym Veremeyenko wrote:
25.08.2017 0:17, Marton Balint пише:
[...]
Ok. If it works in v3, then I guess it is OK to apply as is. Let me
know when you want me to do that.
please apply
Applied with a small fix to the docs
25.08.2017 0:17, Marton Balint пише:
[...]
Ok. If it works in v3, then I guess it is OK to apply as is. Let me know
when you want me to do that.
please apply
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http
22.08.2017 23:14, Maksym Veremeyenko пише:
[...]
One more thing I noticed testing, maybe you can take a look: rgba and
rgb0 format is not working (I used the V1 SDK), only audio frames are
received, but no apparent error is shown. On the other hand, bgr0 and
bgra formats do work. If you can&#
22.08.2017 21:06, Marton Balint пише:
On Fri, 18 Aug 2017, Maksym Veremeyenko wrote:
[...]
Thanks for all the fixes. Is it ok to apply this version, or we are
still waiting for some V3 SDK stuff?
i received updated v3 SDK with a fixed issues i noticed, but i will ask
about next release
here.
+
+ if (ctx->audio)
+av_freep(&ctx->audio);
And here.
done
--
Maksym Veremeyenko
>From c36ec001d30649bfeb80b6b5f32fe34d692111d4 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Fri, 18 Aug 2017 09:34:06 -0400
Subject: [PATCH] lavd: im
On 17.08.2017 11:42, Ali KIZIL wrote:
[...]
As general infomation, NDI v3 SDK is released at:
http://pages.newtek.com/NDI-Developers-SDK-Download-Link.html
i found two issues with v3, so wait for final issues resolving.
--
Maksym Veremeyenko
On 05.08.2017 22:46, Marton Balint wrote:
On Thu, 3 Aug 2017, Maksym Veremeyenko wrote:
[...]
About the warnings for the bottom field order and the negative linesize,
I still think it is better to reject them (return an error), this way
the user will be forced to fix the input, by changing the
On 03.08.2017 10:41, Steinar H. Gunderson wrote:
On Thu, Aug 03, 2017 at 08:21:09AM +0300, Maksym Veremeyenko wrote:
You should reject bottom field first formats, as NDI explicitly
disallows them.
even if it disallowed, why to drop? may be warning message would be enough?
FWIW, the
ght local sources should appear as well.
it should... that is my current testing environment
i reworked *ndi_find_sources*, please do a tests
Also, v3 of the SDK is to be released very soon. Maybe better to wait
for it
and use that? Hopefully less bugs in the SDK itself?
i hope they will r
On 24.07.2017 20:11, Nicolas George wrote:
Le quintidi 5 thermidor, an CCXXV, Maksym Veremeyenko a écrit :
would it be ok:
Subject: [PATCH] lavf: implement NewTek NDI support
Exactly. Except I mistyped: that would be lavd, not lavf; my bad.
fixed
would you *newtek_ndi* or
Hi,
attached updated version of NewTek NDI support.
i think i fixed all notices/comments except:
On 24.07.2017 16:30, Nicolas George wrote:
> Le quintidi 5 thermidor, an CCXXV, Maksym Veremeyenko a écrit :
>> according to SDK documentation terminology, *source* and *find* used fo
g found sources until find_sources specified
+/* Find available sources. */
+ret = ndi_find_sources(avctx, avctx->filename,
&recv_create_desc.source_to_connect_to);
+if (ctx->find_sources) {
+ return AVERROR_EXIT;
+}
+if (ret < 0) {
+return AVERROR(ENOEN
mented" / "Function not supported"
EINVAL -> "Invalid argument"
In this case, the problem is that the avctx argument has several
streams: EINVAL is really the correct one.
i can use whatever you prefer
--
Maksym Veremeyenko
_
hink it is better if it works with unkown channel layouts as well, as
long as the number of channels are supported.
ok
--
Maksym Veremeyenko
___
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
On 23.07.2017 13:20, Nicolas George wrote:
Le quintidi 5 thermidor, an CCXXV, Maksym Veremeyenko a écrit :
[...]
Subject: [PATCH] Implement NewTek NDI support
Nit: "lavf: implement..."
would it be ok:
Subject: [PATCH] lavf: implement NewTek NDI support
[...]
I wo
Hi,
attached patched for HEAD and n3.3 that implemented NewTek NDI, standard
created by NewTek to make it easy to develop video-related products that
share video on a local Ethernet network.
--
Maksym Veremeyenko
>From d5df13750d029d5314be24c9b1cb7306947507c1 Mon Sep 17 00:00:00 2001
F
* and *192*.
Attached patch use local variable for storing this intermediate value of
chroma vertical position not modifying default context value.
--
Maksym Veremeyenko
From 912ecf538b6b2f7a8df4afdfed2d34052162335c Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Mon, 6 Feb 2017 17:03
Hi,
attached patches extends Generic/CDDI/MPEG2 essence descriptors with
additional items. These items required by AMWA AS-10 MXF specification.
--
Maksym Veremeyenko
From 937b1e3f14d641b83a40c9dc5e64e227121dddfa Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Thu, 21 Apr 2016 01:18
On 18.11.2015 19:37, Michael Niedermayer wrote:
[...]
the first field of the context must be a AVClass
updated patch attached
--
Maksym Veremeyenko
From 665751883fd515c753ada7bbf4d24c89a24f3d30 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Wed, 18 Nov 2015 23:44:08 +0200
Subject
makes possible to work with *crtmpserver* and YouTube by
simple remuxing streams for publishing
--
Maksym Veremeyenko
From afdc10c4f496d1e72a3b955513cf6891767d731a Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Tue, 17 Nov 2015 20:02:22 +0200
Subject: [PATCH] AAC sequence header
ontext @ 0x1ffc540] Statistics: 0 seeks, 0 writeouts
[AVIOContext @ 0x1fe8b20] Statistics: 14936 bytes read, 0 seeks
after investigation of latest patch i found that problem comes from
*mov: Double-check that alias path is not an absolute path*
http://git.videolan.org/?p=ffmpeg.git;a=commitdiff
hi,
attached patch fix input stream detection by Icecast that do not
understand chunked http input.
--
Maksym Veremeyenko
>From e733ea6b31d341d2850070e378c2c841ebec0e35 Mon Sep 17 00:00:00 2001
From: Maksym Veremeyenko
Date: Wed, 20 Aug 2014 12:15
51 matches
Mail list logo
