rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Felipe W Damasio
Hi all,
 
 I've trying to use ffmpeg to replicate a signal from one multicast RTP
(using MPEGTS) to another, just to act as a kind of mirror signal.
 
  I'm having to problems with this. First one is that the metadata isn't
being copied. I understand that there's a bug[1] and even a proposed
patch[2], but no final solution. Does any know how is this going?
 
 Also, the rtp_mpegts muxer is setting pmt_pid and pcr_pid  (using ffprobe
-show_programs) to default values. 4096 and 256 respectively .I'd like to
set them to the same value as the source (which is 598 and 801, if it
matters). Usually this can be done using the mpegts muxer, but with
rtp_mpegts there doesn't seem to be any option. Does anyone know how can
this be done?
 
 We need this for a satellite encoder which requires the same values in
order to detect the streams.
 
 Thanks!
 
 Felipe Damasio
 
 
 [1]https://trac.ffmpeg.org/ticket/7293
 [2] http://ffmpeg.org/pipermail/ffmpeg-user/2018-July/040417.html

 
 

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Micael Silva
On Tue, Jun 11, 2019 at 4:27 PM Felipe W Damasio <[hidden email]>
wrote:

> Hi all,
>
>  I've trying to use ffmpeg to replicate a signal from one multicast RTP
> (using MPEGTS) to another, just to act as a kind of mirror signal.
>
>   I'm having to problems with this. First one is that the metadata isn't
> being copied. I understand that there's a bug[1] and even a proposed
> patch[2], but no final solution. Does any know how is this going?
>
>  Also, the rtp_mpegts muxer is setting pmt_pid and pcr_pid  (using ffprobe
> -show_programs) to default values. 4096 and 256 respectively .I'd like to
> set them to the same value as the source (which is 598 and 801, if it
> matters). Usually this can be done using the mpegts muxer, but with
> rtp_mpegts there doesn't seem to be any option. Does anyone know how can
> this be done?
>
>  We need this for a satellite encoder which requires the same values in
> order to detect the streams.
>
>  Thanks!
>
>  Felipe Damasio
>
>
>  [1]https://trac.ffmpeg.org/ticket/7293
>  [2] http://ffmpeg.org/pipermail/ffmpeg-user/2018-July/040417.html
>
>
Did the output option -streamid has some use on this case?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Felipe W Damasio
Hi Micael,
 
 
 

----------------------------------------
 From: "Micael Silva" <[hidden email]>

>
Did the output option -streamid has some use on this case?
 
 -
 
 Not really, rtp_mpegts seems to fallback to default values, completely
ignoring the setting.
 
 Cheers,
 
 Felipe Damasio

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Micael Silva
On Tue, Jun 11, 2019 at 4:49 PM Felipe W Damasio <[hidden email]>
wrote:

> Hi Micael,
>
>
>
>
> ----------------------------------------
>  From: "Micael Silva" <[hidden email]>
>
> >
> Did the output option -streamid has some use on this case?
>
>  -
>
>  Not really, rtp_mpegts seems to fallback to default values, completely
> ignoring the setting.
>
>  Cheers,
>
>  Felipe Damasio
>

I'm not familiar with streaming over RTP but seems to me that the way
forward is to set the params on the mpegts muxer side then send it to the
RTP protocol. Maybe the lack of specific settings on mpegts side made RTP
fill these gaps with default values. Look at some examples on the
documentation: https://ffmpeg.org/ffmpeg-formats.html#mpegts-1
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Felipe W Damasio
Hi Micael,
 
 
 

----------------------------------------
 From: "Micael Silva" <[hidden email]>

I'm not familiar with streaming over RTP but seems to me that the way
forward is to set the params on the mpegts muxer side then send it to the
RTP protocol. Maybe the lack of specific settings on mpegts side made RTP
fill these gaps with default values. Look at some examples on the
documentation: https://ffmpeg.org/ffmpeg-formats.html#mpegts-1
 
 -
 
 Great, thanks.
 
 Indeed the mpegts muxer has everything I need. Although I can't do
something like this:
 
 ffmpeg -i rtp://<address>:<port> -c copy -f mpegts <all the options>
rtp://<another address>:<port>
 
 I'm going to have to pass it to -f rtp_mpegts which will reset all the
options to the default values.
 
 Cheers,
 
 Felipe Damasio

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Moritz Barsnick
In reply to this post by Felipe W Damasio
On Tue, Jun 11, 2019 at 16:26:52 -0300, Felipe W Damasio wrote:
>   I'm having to problems with this. First one is that the metadata isn't
> being copied. I understand that there's a bug[1] and even a proposed
> patch[2], but no final solution. Does any know how is this going?

Oh, indeed, that was me. That proposed patch is broken though. I
crafted a proper one - which should be correct - and forwarded it to
the development list upstream:

http://ffmpeg.org/pipermail/ffmpeg-devel/2018-July/231816.html
https://patchwork.ffmpeg.org/patch/9566/

But this patch was never merged, or even reviewed.

>  Also, the rtp_mpegts muxer is setting pmt_pid and pcr_pid  (using ffprobe
> -show_programs) to default values. 4096 and 256 respectively .I'd like to
> set them to the same value as the source (which is 598 and 801, if it
> matters). Usually this can be done using the mpegts muxer, but with
> rtp_mpegts there doesn't seem to be any option. Does anyone know how can
> this be done?

I can't pitch in on this one. I don't know whether the mpegts sub-muxer
of rtp_mpegts parses mpegts's options, and whether these can be passed
on to rtp. I experimented a bit, but have a hard time interpreting the
results. Someone else should comment.

Cheers,
Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: rtp_mpegts metadata copying and pmt_pid/pcr_pid setting

Felipe W Damasio
Hi Moritz,
 
 

----------------------------------------
 From: "Moritz Barsnick" <[hidden email]>
Sent: Wednesday, June 12, 2019 5:59 AM

Oh, indeed, that was me. That proposed patch is broken though. I
crafted a proper one - which should be correct - and forwarded it to
the development list upstream:

http://ffmpeg.org/pipermail/ffmpeg-devel/2018-July/231816.html
https://patchwork.ffmpeg.org/patch/9566/

But this patch was never merged, or even reviewed.
 
 -
 
 Right, I saw that too...but since there was no comment, I decided to check
if there was a reason nobody merged the code (or if just was a matter of
showing interest in the fix to get things moving :-)).
 
 -
I can't pitch in on this one. I don't know whether the mpegts sub-muxer
of rtp_mpegts parses mpegts's options, and whether these can be passed
on to rtp. I experimented a bit, but have a hard time interpreting the
results. Someone else should comment.
 -
 
 
 Right, according to my testing, it doesn't. as soon as data flow through
rtp_mpegts muxer, everything is back to default values.
 
 What I've been trying to use in the meantime is something like this:
 
  ffmpeg -i rtp://<multicast input>:<port> -map_metadata 0 -movflags
use_metadata_tags -c copy -f mpegts -mpegts_flags
"resend_headers+initial_discontinuity" udp://127.0.0.1:12345
 
 And then using the multicat tool to trying to transform UDP packets to RTP
ones
 
 multicat -p 68 -u 127.0.0.1:12345 <multicast output>:<port>
 
 Then we could get potentially the benefits from the mpegts muxer and all
those options, and have someone ele generate the RTP packets. But this is
not working great currently. Still testing.
 
 Cheers,
 
 Felipe Damasio


_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".