[Michael Rampe]

Yes, it fails after one frame.

What are you trying to achieve?

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

Just tried to replicate it and it didn’t work. Just wrote one frame and failed.

I will keep looking into it.

What is the intended purpose for this process? There might be a workaround if I know what you are trying to achieve.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

[nayan kapadia] “Is there any way to generate only one image and overwrite that image after each frame using ffmpeg?”

Do not use the “%d” in the image name. This is what creates sequential image numbers.
The “-y” flag will overwrite the previous image which you are using. Try putting it just before the output filename.

Eg.
ffmpeg -i rtsp:///main.mp4 -an -r 1 -s 320×240 -y video.jpg

This might work or might just create one frame and stop. Not too sure about this. Try it and see.

[nayan kapadia] “When i type ffmpeg.exe in command line it displays ffmpeg version message and configuration message, how can i stop display of these messages on command line?”

You cannot stop this display.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

Try:

ffmpeg -i yourfile.avi -vcodec copy -acodec copy -aspect 16:9 output.avi

The -vcodec copy command will ensure no recompression is done.
The -aspect 16:9 command sets the correct aspect ratio flags.

Let me know if this works for you.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

Do you want to convert anamorphic to square pixel 16:9 for the web or use this in a video editing application?

The simple answer is “yes”, FFmpeg can do the task you require.

The more complex answer is “they already are (most likely) 16:9 but the player is ignoring the aspect ratio flag”

There are three values which dictate aspect ratio. SAR, PAR and DAR.

SAR=source aspect ratio
This is the aspect ratio of the source pixels. It can be calculated by dividing the width by the height. In standard definition D1 pal, this is 5:4 or 1.25 (720×576)

DAR=display aspect ratio
This is the intended display aspect. Usually 16:9 or 4:3 for standard definition, always 16:9 for high definition.

PAR=pixel aspect ratio
This is usually deduced by dividing DAR by SAR. In a 16:9 PAL example as used above: PAR=DAR/SAR therefore PAR=16:9/5:4 =16×4/9×5 =64/45 =1.42

For 16:9 D1 PAL:
SAR=1.25 or 5/4
DAR=1.78 or 16/9
PAR=1.42 or 64/45

Your player is most likely ignoring these settings and just showing the source pixels as they are. Most editing applications will read these settings correctly or allow you to assign them to the footage.

To give you more help it would be good to get the ffmpeg readout of the file you are trying to convert.
Use the command:
ffmpeg -i yourfile.avi
Paste the console/shell readout to a new post.

This will allow me to see whether the footage has the correct 16:9 settings already or needs them added by FFmpeg.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

Hi Thomas,

Good info to know.

Thanks for posting the end of the story.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

The dreaded “Quicktime gamma bug” that has been identified for several years but not entirely solved. It sucks.

Technically speaking, the gamma bug is due to the use of the +dct8x8 flag in the encode and not erroneous colr nclc atoms in the Quicktime wrapper.

+dct8x8 is DISABLED in main and baseline encoding methods but is ENABLED in high profile settings.

Try FFmpeg.

I found that by using a “high profile” H.264 (in fact, Videolan’s x264 codec), the gamma bug went away. Good original colour in Quicktime with or without the Final cut pro compatibility switch.

Check the FFmpeg forum for an installation guide for Mac. It’s really not that hard.

https://forums.creativecow.net/ffmpeg
https://forums.creativecow.net/readpost/291/22

I would be happy to supply some command lines to get you started with H.264 Mp4 files if you like.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

Howdy Nayan,

What system are you using (osx, linux, windows)?

[nayan kapadia] “IP camera”

Does this mean a webcam or a local camera?

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

The main difference I see between the two files is the Level.

FFmpeg: Codec Profile -> Main@L4.1
Episode: Codec Profile -> Main@L5.0

The level is dictated by the number of macrobloks/bits per sec/image size/frame rate.
Have a look at the bottom of https://en.wikipedia.org/wiki/H.264 for a good chart explaining the limitations.

It also directly effects the “decoded picture buffering” which could affect playback in FCP. (Level 4.1 has a buffering limit of 4 frames at 1080, Level 5.0 has a buffering limit of 13 frames at 1080.

You might want to try adding: “-level 50” to your command line.

The only other significant difference I see is that you are using -refs 2 whilst episode is using -refs 6.
Give that a go as well. You do not need “-refs 2” as this is already specified in the “normal” x264 preset but this will override the preset setting for -refs if it is different.

Also, I see that you are setting minrate and maxrate to 12M. This is a way of creating a constant bitrate file but it still reports as VBR in Mediainfo. Try removing these two flags and see what results you get.

And finally, try a high profile setting as well. (This sets the -refs to 4)

ffmpeg -y -deinterlace -i FICHIER.mov -vcodec libx264 –vpre hq -level 50 -b 12M -bt 12M -s hd1080 -aspect 16:9 -acodec libfaac -ab 384K -threads 0 -coder 0 -refs 2 -r 25 FICHIER.1080.mp4

Just some ideas. Let me know how they go.

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”

[Michael Rampe]

[Thomas Brender] “I know, H264 is not great to edit”

Correct. Why not use an edit friendly format?

[Thomas Brender] “but when I encode the same MP4 files in H264 with Episode, it works much better…”

Can you post the media info result for this file?

Also, can you post the command line you are using in FFmpeg?

[Thomas Brender] “Codec Profile -> Main@L4.1”

I would like to know why you are not using high profile….

Michael

“half-way to world domination A.K.A. the belligerent blue bike shed”