Re: [FFmpeg-user] How to set 3 specific metadata flags (ITU601/displayoffset) in FFmpegs IMX50 MXF-OP1a encoding?
On 19/03/15 15:48, Christoph Gerstbauer wrote: Shame, don't understand the qmax issue. but if you look at:- tests/lavf_regression.sh line 90 you will see an IMX30 example which uses -qmax 12 and my other other parameters. However not sure what difference closed/open gop makes on I frame only, but being purist I can see how you might want to set closed gop! S356m makes no reference to it that I can see. Looks like we might need a patch for what you want. In fact, the most important metadata flag is the display y offset = 32 (high priority for patching, if possible) Having a quick scan through mxfenc.c it looks like that UL is missing, as are some others. I have tracked them down in RP210 but am struggling with the local_tag values at the moment. It should be relatively straightformward to add in the relevant tag though. Without it, some programs like GRass Valley Edius misinterpret the IMX files - the VBI area is shown in the editing window: [..] Best Regards Christoph [..] -- Tim. Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83 ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Problems with opening some DPX files
On 19-03-15 13:47, Christoph Gerstbauer wrote: Hello, I am testing the transcoding of different DPX files from different sources. I have here 2 files which cannot be opened by ffmpeg. https://dl.dropboxusercontent.com/u/26129407/ProblematicDPX_1.zip When I open the files with ImageMagick and GraphicsMagick they look distorted (can be seen in the png from the zip file). Opening the files with Photoshop they look also very weird but different to GM and IM. (see PNGs in zip) Any ideas whats going on here? Best Regards Christoph COMMAND LINE OUTPUT: C:\Users\gerstiffmpegnew -i I:\DPX\_DPX examples\Bojan\009.dpx ... [dpx @ 02cf7c40] Packing 2 is not implemented. Update your FFmpeg version to the newest one from Git. If the problem still occurs, it means that your file has a feature which has not been impl Hi Christoph, after a little search these are my findings ffmpeg throws a packing error at you Packing 2 is not implemented According to the DPX v2 specs packing 2 is 8 bit values: The origin of your DPXs as stated in the header is a Scanity, which can do 8 bits scans. This might be the origin of the issue. http://www.dft-film.com/downloads/datasheets/Scanity-HDR.pdf 8 Bit data values are not supported in ffmpeg (and not very well supported in any program as far as I know): https://github.com/FFmpeg/FFmpeg/blob/master/libavcodec/dpx.c lines 141-144 Here's a bit more info about 8 bit image data issues in the DPX specs: http://www.simplesystems.org/users/bfriesen/dpx/dpx-issues.pdf I see a black and white image in Nuke which sort of confirms the storage of RGB channels in one value. The skew in the image is probably caused by a mismatch in image width and pixel aspect ration (which says it's 2048x2048) gr Arno ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] hls_size
Sorry, I meant g = segment_length * framerate On Friday, March 20, 2015 5:21 PM, Bogdan ioan Gabor bogdanioan.ga...@yahoo.com wrote: Hi, I had the same issue, and I managed to fix it by setting the framerate (-r parameter) and the GOP (-g parameter) which I think it depends on the framerate.So, for 3 seconds segments, I've used a framerate of 10 and a GOP of 30. I thought it's good/normal to have an I-Frame on every segment.My advise will be to just make sure that you have at least one I-Frame for each segment. g = segment_length + framerate. Good luck. On Saturday, March 14, 2015 9:16 PM, Davood Falahati d.falahati.1...@ieee.org wrote: I want to stream my capture card using HLS. I get the input well and everything seems to bo fine. The problem is the latency. I want to lessen the chunk sizes to 3 seconds or less, and put less than 5 chunks in every list. But when I run the ffmpeg as below: ffmpeg -re -i rtmp://serveradress/live/channel -codec copy -map 0 -f segment -segment_list playlist.m3u8 -delete -segment_list_flags +live -segment_time 3 out%03d.ts the generated segments are much longer than 3 seconds. I think the problem is with iFrames. How should I fix that issue? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] hls_size
Hi, I had the same issue, and I managed to fix it by setting the framerate (-r parameter) and the GOP (-g parameter) which I think it depends on the framerate.So, for 3 seconds segments, I've used a framerate of 10 and a GOP of 30. I thought it's good/normal to have an I-Frame on every segment.My advise will be to just make sure that you have at least one I-Frame for each segment. g = segment_length + framerate. Good luck. On Saturday, March 14, 2015 9:16 PM, Davood Falahati d.falahati.1...@ieee.org wrote: I want to stream my capture card using HLS. I get the input well and everything seems to bo fine. The problem is the latency. I want to lessen the chunk sizes to 3 seconds or less, and put less than 5 chunks in every list. But when I run the ffmpeg as below: ffmpeg -re -i rtmp://serveradress/live/channel -codec copy -map 0 -f segment -segment_list playlist.m3u8 -delete -segment_list_flags +live -segment_time 3 out%03d.ts the generated segments are much longer than 3 seconds. I think the problem is with iFrames. How should I fix that issue? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] hls_size
Thank you, I managed to do that finally. What is your recommendation for segment_length and list_size for a low-latency live broadcasting? Davood Falahati, PhD candidate in Isfahan University of Technology. d.falahati.1...@ieee.org On Fri, Mar 20, 2015 at 8:22 AM, Bogdan ioan Gabor bogdanioan.gabor-at-yahoo@ffmpeg.org wrote: Sorry, I meant g = segment_length * framerate On Friday, March 20, 2015 5:21 PM, Bogdan ioan Gabor bogdanioan.ga...@yahoo.com wrote: Hi, I had the same issue, and I managed to fix it by setting the framerate (-r parameter) and the GOP (-g parameter) which I think it depends on the framerate.So, for 3 seconds segments, I've used a framerate of 10 and a GOP of 30. I thought it's good/normal to have an I-Frame on every segment.My advise will be to just make sure that you have at least one I-Frame for each segment. g = segment_length + framerate. Good luck. On Saturday, March 14, 2015 9:16 PM, Davood Falahati d.falahati.1...@ieee.org wrote: I want to stream my capture card using HLS. I get the input well and everything seems to bo fine. The problem is the latency. I want to lessen the chunk sizes to 3 seconds or less, and put less than 5 chunks in every list. But when I run the ffmpeg as below: ffmpeg -re -i rtmp://serveradress/live/channel -codec copy -map 0 -f segment -segment_list playlist.m3u8 -delete -segment_list_flags +live -segment_time 3 out%03d.ts the generated segments are much longer than 3 seconds. I think the problem is with iFrames. How should I fix that issue? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] Why start_time is sometimes non zero?
I know files captured with Final Cut Pro 7 have this attribute. The software starts recording the audio and video tracks and then inserts metadata for each track to indicate the offset of the start of the track relative to the start time of the container. This aligns the tracks, to this point. Chris On Friday, March 20, 2015, Andrzej Borucki borucki.andr...@gmail.com wrote: I convert .mov file created by Canon to H.264, container mp4 - QuickTime(?) ffprobe give me: [format] format_name=mov,mp4,m4a,3gp,3g2,mj2 format_long_name=QuickTime / MOV start_time=0.045000 duration=7.808000 size=954931 video stream [streams.stream.0] codec_name=h264 codec_time_base=1/18 time_base=1/9 start_pts=5940 start_time=0.066000 duration_ts=702702 duration=7.807800 bit_rate=810598 nb_frames=234 audio [streams.stream.1] codec_name=aac codec_time_base=1/48000 time_base=1/48000 start_pts=2160 start_time=0.045000 duration_ts=372736 duration=7.765333 After converting it to h264: [format] start_time=-0.03 duration=7.842000 size=889221 bit_rate=907136 [streams.stream.0] r_frame_rate=3/1001 avg_frame_rate=3/1001 time_base=1/3 start_pts=0 start_time=0.00 duration_ts=235235 duration=7.841167 [streams.stream.1] time_base=1/48000 start_pts=-1600 start_time=-0.03 duration_ts=374336 duration=7.798667 Why start_time is not zero? In second movie, audio begins before or after start movie? In first - both video and audio start_time is non zero, what it means? ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org javascript:; http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to set 3 specific metadata flags (ITU601/displayoffset) in FFmpegs IMX50 MXF-OP1a encoding?
Am 20.03.2015 um 16:21 schrieb tim nicholson: On 20/03/15 09:19, tim nicholson wrote: On 19/03/15 15:48, Christoph Gerstbauer wrote: Shame, don't understand the qmax issue. but if you look at:- tests/lavf_regression.sh line 90 you will see an IMX30 example which uses -qmax 12 and my other other parameters. However not sure what difference closed/open gop makes on I frame only, but being purist I can see how you might want to set closed gop! S356m makes no reference to it that I can see. Looks like we might need a patch for what you want. In fact, the most important metadata flag is the display y offset = 32 (high priority for patching, if possible) Having a quick scan through mxfenc.c it looks like that UL is missing, as are some others. I have tracked them down in RP210 but am struggling with the local_tag values at the moment. It should be relatively straightformward to add in the relevant tag though. Attached is a quick hack that worked for me. Do you want to give it a spin? Hello Tim, thank you! I have to wait for next week when I am in the office because I am not able to apply this patch (I have no expierience in doing that ;). A collegue of mine is able to compile. . I am just working with ffmpeg .exe files. Best Regards Christoph ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to set 3 specific metadata flags (ITU601/displayoffset) in FFmpegs IMX50 MXF-OP1a encoding?
On 20/03/15 15:21, tim nicholson wrote: On 20/03/15 09:19, tim nicholson wrote: On 19/03/15 15:48, Christoph Gerstbauer wrote: Shame, don't understand the qmax issue. but if you look at:- tests/lavf_regression.sh line 90 you will see an IMX30 example which uses -qmax 12 and my other other parameters. However not sure what difference closed/open gop makes on I frame only, but being purist I can see how you might want to set closed gop! S356m makes no reference to it that I can see. Looks like we might need a patch for what you want. In fact, the most important metadata flag is the display y offset = 32 (high priority for patching, if possible) Having a quick scan through mxfenc.c it looks like that UL is missing, as are some others. I have tracked them down in RP210 but am struggling with the local_tag values at the moment. It should be relatively straightformward to add in the relevant tag though. Attached is a quick hack that worked for me. Do you want to give it a spin? [..] If it works for you I will submit a tidied up version, with revised fate checksums, but that will have to wait awhile as I'm away next week... -- Tim. Key Fingerprint 38CF DB09 3ED0 F607 8B67 6CED 0C0B FC44 8B0B FC83 ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
