[FFmpeg-user] Detect Missed or freezed sound, Video in DVB an restart the FFMPEG Command

2017-05-05 Thread Spyer spyer 
Hello, i use ffmpeg with Tvheadend to transcode DVB to my mobilephone. In some 
case I habe no sound, But Video or no Video, But sound, or the Video has 
freezer. After close ffmpeg and Start again its work Fine. How can i implement 
a automatic detection to restart ffmpeg?

Now my pipe is:


#!/bin/bash
url=$1
su
/usr/local/bin/ffmpeg \
-i $url \
-i /home/logo/HD.png \
-filter_complex overlay=main_w-overlay_w-10:main_h-overlay_h-10 \
-vcodec h264_qsv \
-b 2000k \
-minrate 2000k \
-maxrate 2000k \
-bufsize 2000k \
-preset fast \
-s 1280x720 \
-acodec aac \
-ab 128k \
-ar 44100 \
-ac 2 \
-strict \
-2 \
-metadata service_provider="Team" \
-metadata service_name=$name \
-f mpegts pipe:1

exit 0

Best reguards
Spyer
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Avid opAtom trouble

2017-05-05 Thread Jaka Bac 
Hi Bouke,

No the question was not for you :) But for people who are in position to
accept patches..
But probably this is the wrong mailing list.. I should have asked the
question on ffmpeg-devel

However I am fairly certain that this is the source of your problem...
Maybe I can do a test with your file with the patch applied...

Jaka

On 5 May 2017 at 14:15, Bouke (VideoToolShed) 
wrote:

>
> - Original Message - From: "Jaka Bac" 
> To: "FFmpeg user questions" 
> Sent: Friday, May 05, 2017 12:31 PM
> Subject: Re: [FFmpeg-user] Avid opAtom trouble
>
>
> Hello
>>
>> This probably happens because the ffmpeg MXF muxer does not write some
>> metadata that Avid expects.
>>
>> Namely the following entries in the CDCI descriptor will be missing:
>> SampledWidth = 1920
>> SampledHeight = 1080
>>
>> and this will be set (where 1920x1088 comes from):
>> StoredWidth = 1920
>> StoredHeight = 544
>>
>> But the actual problem I believe is the missing metadata.
>>
>> There is a patch floating around the mailing lists which fixes this (and
>> also same problem which happens where OP1a XDCAM HD files generated by
>> ffmpeg are imported into Avid editors).
>> https://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/194830.html
>>
>> Is there any reason why this patch is not accepted/applied?
>>
>
> Hi Jaka,
> Is this a question for me? I can't answer it, just took the latest Zeranoe
> build...
> thx,
> Bouke
>
>
> Jaka
>>
>> On 2 May 2017 at 17:37, Bouke (VideoToolShed) 
>> wrote:
>>
>> - Original Message - From: "Carl Eugen Hoyos" >> >
>>> To: "FFmpeg user questions" 
>>> Sent: Tuesday, May 02, 2017 4:31 PM
>>> Subject: Re: [FFmpeg-user] Avid opAtom trouble
>>>
>>>
>>> 2017-05-02 14:46 GMT+02:00 Bouke (VideoToolShed) <
>>> bo...@videotoolshed.com
>>>
 >:

 Toying around with Avid opAtom mxf, generating test clips.

> When I look at the clip in Avid, the bin info shows a raster dimension
> of
> 1920x1088, pixel aspect ratio of 1.007 (expected 1920x1080 / 1.000)
> And of course, when editing the clip into a seqence, frameflex kicks
> in.
>
> same line but output to Mov and AMA the clip in does give the
> expected result.
>
>
 What happens if you use FFmpeg to remux the working mov file
 into mxf?


>>> -vcodec copy NEEDS the FPS, or FFmpeg bitches. When I add -r 25, it does
>>> the re-wrap, but output gives the same trouble in Avid.
>>>
>>> What happens if you use FFmpeg to remux the broken mxf file
>>>
 into mov?


>>> FFmpeg reports the frame size has changed from 1088 to 1080, and all is
>>> well.
>>> (Except the UUID or something is copied over, so doing the dance twice to
>>> two filenames makes Avid refuse to import both, as it 'knows' it
>>> already...)
>>>
>>> Nice details, with -vcodec copy also timecode comes across (From MXF to
>>> MOV and vice-versa.)
>>> Also the interlace flag is set without issue.
>>>
>>> Can you provide a working mxf file similar to the one FFmpeg
>>>
 produces?


>>> Yes, see here:
>>> Download link
>>> https://wetransfer.com/downloads/d35f135d397837227c965ee7b95
>>> ea7bf20170502152440/018e64f2872c5c6e4de8bca6e08ca3f620170502
>>> 152440/fd3691
>>>
>>>
>>> Note, this is an AVID generated mixdown of the (good) AMA linked MOV. Tc
>>> has changed to seqence TC (00:00:00:00)
>>>
>>> (I believe I remember what the issue is but would like to
>>>
 verify.)


>>> Let me know if you need more, and thanks!
>>>
>>> Bouke
>>>
>>> Carl Eugen
>>>
 ___
 ffmpeg-user mailing list
 ffmpeg-user@ffmpeg.org
 http://ffmpeg.org/mailman/listinfo/ffmpeg-user

 To unsubscribe, visit link above, or email
 ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


>>>
>>> ---
>>> This email has been checked for viruses by Avast antivirus software.
>>> https://www.avast.com/antivirus
>>>
>>> ___
>>> ffmpeg-user mailing list
>>> ffmpeg-user@ffmpeg.org
>>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>>
>>> To unsubscribe, visit link above, or email
>>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>>
>>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org

Re: [FFmpeg-user] Avid opAtom trouble

2017-05-05 Thread Bouke (VideoToolShed) 


- Original Message - 
From: "Jaka Bac" 

To: "FFmpeg user questions" 
Sent: Friday, May 05, 2017 12:31 PM
Subject: Re: [FFmpeg-user] Avid opAtom trouble



Hello

This probably happens because the ffmpeg MXF muxer does not write some
metadata that Avid expects.

Namely the following entries in the CDCI descriptor will be missing:
SampledWidth = 1920
SampledHeight = 1080

and this will be set (where 1920x1088 comes from):
StoredWidth = 1920
StoredHeight = 544

But the actual problem I believe is the missing metadata.

There is a patch floating around the mailing lists which fixes this (and
also same problem which happens where OP1a XDCAM HD files generated by
ffmpeg are imported into Avid editors).
https://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/194830.html

Is there any reason why this patch is not accepted/applied?


Hi Jaka,
Is this a question for me? I can't answer it, just took the latest Zeranoe 
build...

thx,
Bouke


Jaka

On 2 May 2017 at 17:37, Bouke (VideoToolShed) 
wrote:

- Original Message - From: "Carl Eugen Hoyos" 


To: "FFmpeg user questions" 
Sent: Tuesday, May 02, 2017 4:31 PM
Subject: Re: [FFmpeg-user] Avid opAtom trouble


2017-05-02 14:46 GMT+02:00 Bouke (VideoToolShed) :

Toying around with Avid opAtom mxf, generating test clips.
When I look at the clip in Avid, the bin info shows a raster dimension 
of

1920x1088, pixel aspect ratio of 1.007 (expected 1920x1080 / 1.000)
And of course, when editing the clip into a seqence, frameflex kicks 
in.


same line but output to Mov and AMA the clip in does give the
expected result.



What happens if you use FFmpeg to remux the working mov file
into mxf?



-vcodec copy NEEDS the FPS, or FFmpeg bitches. When I add -r 25, it does
the re-wrap, but output gives the same trouble in Avid.

What happens if you use FFmpeg to remux the broken mxf file

into mov?



FFmpeg reports the frame size has changed from 1088 to 1080, and all is
well.
(Except the UUID or something is copied over, so doing the dance twice to
two filenames makes Avid refuse to import both, as it 'knows' it 
already...)


Nice details, with -vcodec copy also timecode comes across (From MXF to
MOV and vice-versa.)
Also the interlace flag is set without issue.

Can you provide a working mxf file similar to the one FFmpeg

produces?



Yes, see here:
Download link
https://wetransfer.com/downloads/d35f135d397837227c965ee7b95
ea7bf20170502152440/018e64f2872c5c6e4de8bca6e08ca3f620170502152440/fd3691


Note, this is an AVID generated mixdown of the (good) AMA linked MOV. Tc
has changed to seqence TC (00:00:00:00)

(I believe I remember what the issue is but would like to

verify.)



Let me know if you need more, and thanks!

Bouke

Carl Eugen

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". 


___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Avid opAtom trouble

2017-05-05 Thread Jaka Bac 
Hello

This probably happens because the ffmpeg MXF muxer does not write some
metadata that Avid expects.

Namely the following entries in the CDCI descriptor will be missing:
 SampledWidth = 1920
 SampledHeight = 1080

and this will be set (where 1920x1088 comes from):
 StoredWidth = 1920
 StoredHeight = 544

But the actual problem I believe is the missing metadata.

There is a patch floating around the mailing lists which fixes this (and
also same problem which happens where OP1a XDCAM HD files generated by
ffmpeg are imported into Avid editors).
https://ffmpeg.org/pipermail/ffmpeg-devel/2016-June/194830.html

Is there any reason why this patch is not accepted/applied?

Jaka

On 2 May 2017 at 17:37, Bouke (VideoToolShed) 
wrote:

> - Original Message - From: "Carl Eugen Hoyos" 
> To: "FFmpeg user questions" 
> Sent: Tuesday, May 02, 2017 4:31 PM
> Subject: Re: [FFmpeg-user] Avid opAtom trouble
>
>
> 2017-05-02 14:46 GMT+02:00 Bouke (VideoToolShed) > >:
>>
>> Toying around with Avid opAtom mxf, generating test clips.
>>> When I look at the clip in Avid, the bin info shows a raster dimension of
>>> 1920x1088, pixel aspect ratio of 1.007 (expected 1920x1080 / 1.000)
>>> And of course, when editing the clip into a seqence, frameflex kicks in.
>>>
>>> same line but output to Mov and AMA the clip in does give the
>>> expected result.
>>>
>>
>> What happens if you use FFmpeg to remux the working mov file
>> into mxf?
>>
>
> -vcodec copy NEEDS the FPS, or FFmpeg bitches. When I add -r 25, it does
> the re-wrap, but output gives the same trouble in Avid.
>
> What happens if you use FFmpeg to remux the broken mxf file
>> into mov?
>>
>
> FFmpeg reports the frame size has changed from 1088 to 1080, and all is
> well.
> (Except the UUID or something is copied over, so doing the dance twice to
> two filenames makes Avid refuse to import both, as it 'knows' it already...)
>
> Nice details, with -vcodec copy also timecode comes across (From MXF to
> MOV and vice-versa.)
> Also the interlace flag is set without issue.
>
> Can you provide a working mxf file similar to the one FFmpeg
>> produces?
>>
>
> Yes, see here:
> Download link
> https://wetransfer.com/downloads/d35f135d397837227c965ee7b95
> ea7bf20170502152440/018e64f2872c5c6e4de8bca6e08ca3f620170502152440/fd3691
>
>
> Note, this is an AVID generated mixdown of the (good) AMA linked MOV. Tc
> has changed to seqence TC (00:00:00:00)
>
> (I believe I remember what the issue is but would like to
>> verify.)
>>
>
> Let me know if you need more, and thanks!
>
> Bouke
>
> Carl Eugen
>> ___
>> ffmpeg-user mailing list
>> ffmpeg-user@ffmpeg.org
>> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> ___
> ffmpeg-user mailing list
> ffmpeg-user@ffmpeg.org
> http://ffmpeg.org/mailman/listinfo/ffmpeg-user
>
> To unsubscribe, visit link above, or email
> ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
>
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

Re: [FFmpeg-user] Long delay on subtitle overlay from a subtitles embedded video

2017-05-05 Thread Dennis Huang 
Just to bring up my question again.  Is anyone could help on this?  Thank 
you.-Dennis
 

On Monday, April 24, 2017 12:41 AM, Dennis Huang 
 wrote:
 

 Hi all,
First of all, thanks for the great ffmpeg software.  It is useful and neat.  
Good job.

My question is regarding the long delay before ffmpeg transcodes a file, with 
following command,
ffmpeg -i embed_sub.mkv -vf subtitles=embed_sub.mkv -sn result.mkv
With -loglevel trace, it shows the command takes over 30 seconds going through 
ALL subtitles in mkv before it starts the transcoding.  Yet this causes problem 
for a real-time transcoding server like Universal Media server, which needs the 
output stream within certain time, usually a few seconds.  The long wait before 
the transcoding causes the server to timeout.
When the delay is taking place, it stops with following messages,
[Parsed_subtitles_0 @ 0x1c8f6e0] Shaper: FriBidi 0.19.6 (SIMPLE) HarfBuzz-ng 
1.4.5 (COMPLEX)
[Parsed_subtitles_0 @ 0x1c8f6e0] Using font provider fontconfig

I have 2 questions,
1. Why ffmpeg needs to go through all the subtitles before the transcoding?  
And2. Is there any way ffmpeg could start the transcoding without the long 
delay in this case?
The file, embed_sub.mkv includes following tracksTrack1 libx264 videoTrack2 dts 
audioTrack3 ASS subtitles
Thank you for the time and information in advance.
-Dennis

___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".

   
___
ffmpeg-user mailing list
ffmpeg-user@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".