Conversion 4:3 to 16:9

[DB83]

Thanks for the clips. I noticed atleast a few things not 'standard' about them. But before I mention these, unless others chip in, allow me to offer my own clip. Does this play ok ?

[Sharc]

@ Sharc,
@DB83,
I have 2 videos for you to check that have the green artifacts.
Both were done before I read Sharc's post.
Horseavid(1C).mp4 was created from just a ffmpeg cut named Horse.mts.
Horse.mts has no encoding,cropping, or resizing.
BDavid.mp4 was created from the original full BD rip with Passkey.
Avidemux did not detect the DTS or any other audio tracks.
Just video on BDavid.mp4.

I did both crop & resize these 2 files with avidemux but No denoising.
The settings were the same as in post# 322 except for the denoise filter was not used.
I did cut & append on both files to make them smaller.
My BD player has the green artifacts on both these.
My TV could not play them direct.

@cholla
No wonder. Both your files are BD/HW-player incompatible encodes, in many respects. They violate BD standards badly. They may play on some BD/HW-players, but just by chance. Just ditch these files.
(On PC/SW player they are playable. I don't get green artifacts).

[Sharc]

Thanks for the clips. I noticed atleast a few things not 'standard' about them. But before I mention these, unless others chip in, allow me to offer my own clip. Does this play ok ?

Your file is also violating (BD) standard. Much less badly than cholla's though. Variable framerate (?), long GOPs, risky b-pyramid 2 .... It will probably play on 'tolerant' HW players, but may fail on picky BD players.
Why don't you guys just adhere to standards, rather than playing roulette in a casino?

[DB83]

fairy nuff

But the whole point of the excercise is to see if cholla can play this without issue just like he did with my earlier clip.

[Sharc]

fairy nuff

But the whole point of the excercise is to see if cholla can play this without issue just like he did with my earlier clip.

fairy nuff.

[cholla]

@Sharc,
I was able to create a video without the green artifacts using your settings with the crop,resize, & denoise.
Played on my BD player.
I will be creating a video with higher settings in the General window to see what happens.

@DB83,
I was able to play Horse-1080_test.mp4 (32.54 MB) with no green artifacts on my BD player.
I don't know what the difference is but you must have something set different in avidemux.

[DB83]

Good to read that.

Now my version is older than yours @2.7.5 but that should make no difference. And ALL settings are 'out of the box' apart from the CRF.

[Sharc]

@Sharc,
I was able to create a video without the green artifacts using your settings with the crop,resize, & denoise.
Played on my BD player.

Perfect. So you should find your way now.

[DB83]

^^ And let's hope that the horse can finally be put out to grass and not find itself in a tin of dogfood

[cholla]

@DB83,
Unless the difference is you have a 64-bit Windows OS.
When I have mine set to use exactly those settings without any additional settings like the ones Sharc posted.
I get the green pixelation.
The version I'm using is 2.7.4

@ Sharc.
The higher quality settings in General worked fine with no green artifacts.
I did crop,resize,& denoise with this video.
The reason the video is short is Alwyn advised me to make them smaller.
If you want a longer one I can do up to the 500MB limit.
This is to for you to check for (BD) standard.
If it is not tell me what I need to change.

I still see a sort of translucent blue reasonably light.when I use the denoiser in avidemux.
When used with ffmpeg it is more like a softening of facial features & is a lighter amount of blue.
So I'm still not sure I like the denoiser.

Horse2.mp4 was done with the settings like in the image.
Except "Fast first pass" was unchecked.


[Attachment 81413 - Click to enlarge]

[DB83]

I really can not see how a 64 bit OS will make the difference.

In fact the only difference I see in your settings, other than the CRF - smaller = larger bitrate = larger files - is the IDC level (auto rather than 4.1 - and the final vid encodes @ level 4). If you mesed around with any other tabs, I can not comment.


But you now have a working, and better, video without messing around with avidemux. And now I am 'saddle-sore'

[cholla]

@DB83,
Other that the higher quality settings I made on the "General" tab>(& I tried with the exact settings Sharc posted in #329 the first time).
I made the settings in the other tabs exactly as Sharc posted.
I believe those changes are what made the green artifacts go away.

The difference is usually updates are available that are not for 32-bit.
Many times files are written some different .dll files for example.
Because you can't put .dll files for a 64-bit OS & have them work in a 32-bit OS.

[cholla]

For assistance you might wish to share your ffmpeg script

But whatever crop you used it is still useful to know how you arrived at your final 1920 vids without the sidebars

I used avidemux to determine the crop.
I tried ffmpeg cropdetect but it did not give me the correct crop.
It might work for some videos.

Here are my codes.
With a lot of help from Sharc even if he does not approve of the "horizontal stretching".

This is the code I use without denoise:

ffmpeg -i "input.m2ts" -vf "fps=24000/1001,crop=1804:1080:exact=1,scale=1920:1080:flags=lanczos,setdar=16/9" -c:v libx264 -pix_fmt yuv420p -preset veryslow -profile:v high -level 4.1 -crf 14 -map_metadata:g -1 -map_metadata -1 -disposition 0 -g 47.952 -x264opts keyint=24:min-keyint=1:vbv-bufsize=78125:vbv-maxrate=62500 -c:a eac3 -ab:a 1411k -ac 2 -c:s copy output.m2ts

This is the code I use with denoise:

ffmpeg -i "input.m2ts" -vf "fps=24000/1001,crop=1804:1080:exact=1,hqdn3d=14.0:14.0:15.0:15.0,scale=1920:1080:flags=lanczos,setdar=16/9" -c:v libx264 -pix_fmt yuv420p -preset veryslow -profile:v high -level 4.1 -crf 14 -map_metadata:g -1 -map_metadata -1 -disposition 0 -g 47.952 -x264opts keyint=24:min-keyint=1:vbv-bufsize=78125:vbv-maxrate=62500:nr=1000 -c:a eac3 -ab:a 1411k -ac 2 -c:s copy output.m2ts

If you do want to stay blu ray compatible you can add this to the code:
"bluray-compat" this should be in the code after x264opts.

bluray-compat (bluray-compat)Configure the encoder to be compatible with the bluray standard. It is a shorthand for setting "bluray-compat=1 force-cfr=1".

[Sharc]

Other that the higher quality settings I made on the "General" tab>(& I tried with the exact settings Sharc posted in #329 the first time).
I made the settings in the other tabs exactly as Sharc posted.
I believe those changes are what made the green artifacts go away.

Exactly. BD/HW-player compliant encoding is key. Usually not provided by defaults or out-of-the box settings. (Personally I prefer GUI-independent ffmpeg commandlines anyway for such basic tasks).

The difference is usually updates are available that are not for 32-bit.

There might always be subtle differences (worst case: flaws) between versions and releases which are beyond our control.

[Sharc]

Here are my codes.
With a lot of help from Sharc even if he does not approve of the "horizontal stretching".

This is the code I use without denoise:

ffmpeg -i "input.m2ts" -vf "fps=24000/1001,crop=1804:1080:exact=1,scale=1920:1080:flags=lanczos,setdar=16/9" -c:v libx264 -pix_fmt yuv420p -preset veryslow -profile:v high -level 4.1 -crf 14 -map_metadata:g -1 -map_metadata -1 -disposition 0 -g 47.952 -x264opts keyint=24:min-keyint=1:vbv-bufsize=78125:vbv-maxrate=62500 -c:a eac3 -ab:a 1411k -ac 2 -c:s copy output.m2ts

This is the code I use with denoise:

ffmpeg -i "input.m2ts" -vf "fps=24000/1001,crop=1804:1080:exact=1,hqdn3d=14.0:14.0:15.0:15.0,scale=1920:1080:flags=lanczos,setdar=16/9" -c:v libx264 -pix_fmt yuv420p -preset veryslow -profile:v high -level 4.1 -crf 14 -map_metadata:g -1 -map_metadata -1 -disposition 0 -g 47.952 -x264opts keyint=24:min-keyint=1:vbv-bufsize=78125:vbv-maxrate=62500:nr=1000 -c:a eac3 -ab:a 1411k -ac 2 -c:s copy output.m2ts

If you do want to stay blu ray compatible you can add this to the code:
"bluray-compat" this should be in the code after x264opts.

bluray-compat (bluray-compat)Configure the encoder to be compatible with the bluray standard. It is a shorthand for setting "bluray-compat=1 force-cfr=1".

Apart from the stretching which I dislike:
- You put HW player compatibility at risk with your vbv settings. Where did you get these values from?
- where did you get the funny -g 47.952 from? (2 sec GOPs may be ok but it conflicts and is overwritten by the keyint=24)
Seems you have copied some parts of these commandlines from somewhere else (?).

But anyway, if this works for you so be it and you do what you like.

horse2.mp4 in your post#340 looks basically compliant to me, apart from a red-blue color shift and killed details due to the much too strong detrimental denoiser. Not sure where the color shift comes from.

[cholla]

You put HW player compatibility at risk with your vbv settings. Where did you get these values from?

I could not get ffmpeg to give me those settings again when I tried to duplicate what I did when it gave them to me.
It had those vbv in yellow as what should be used. They worked without any errors or warnings so I kept them.
I probably will try others

where did you get the funny -g 47.952 from? (2 sec GOPs may be ok but it conflicts and is overwritten by the keyint=24)

If keyint= is used the -g may be ignored.So it may not do anything.


https://www.reddit.com/r/learnjavascript/comments/133z8k7/how_to_know_what_options_to_...in_ffmpeg_hls/
"Set a keyframe interval with the -g option. A common value is 2x the frame rate, e.g., -g 50 for 25fps video."
http://trac.ffmpeg.org/wiki/EncodingForStreamingSites
Use a 2 second GOP (Group of Pictures), so simply multiply your output frame rate * 2. For example, if your input is -framerate 30, then use -g 60.
double
For -g 47.952 23.972x2=47.952 I could have just rounded up but this one played OK.

horse2.mp4 in your post#340 looks basically compliant to me, apart from an odd color shift. No idea where this shift comes from.
Seems whatever you are doing you are messing it up somehow.

I can test again as I deleted the video that I did not use the avidemux denoiser.
I believe horse2.mp4 had the denoiser used & this causes the color shift.

Here are the two files created with avidemux:
The MP4 format won't Copy Audio but it's not necessary for this comparison.
The only difference is the denoise filter . All other settings are the same.
The video with the denoise used is a lot smaller in kbs for some reason.

[Sharc]

The video with the denoise used is a lot smaller in kbs for some reason.

Of course. Denoising saves bits because the encoding of noise is like encoding of details which is bitrate hungry. See the graph in post#323. Removing noise and removing picture details = low bitrate. Denoising is always a compromise between removing unwanted noise but keeping wanted picture details.

The 2 files above (post#346) are BD compliant which is fine. The denoised version has however the color tint and details loss. Way overfiltered.
(By the way the color shift is much less for the ffmpeg commandline version, so I guess it must be your 32bit Avidemux version which causes it)
For the unfiltered version don't go unnecessary low with -crf. It challenges the vbv management.

No comment about the stretching. That's your personal decision.

You got all the options, recommendations, examples and help for ffmpeg commandline and Avidemux settings. So you should know by now what you can/should do wrt resizing, x264 encoder settings and basic denoising.
HW (BD) compliant encoder settings will avoid the green ants which you had before. That's the main point for successful playback via your BD player or TV.

Next phase would be to learn avisynth some day, for more sophisticated filtering - if this should matter at all for your projects.

[Alwyn]

Denoising saves bits because the encoding of noise is like encoding of details which is bitrate hungry. See the graph in post#323.

Cholla did ask before; what software are you using to generate that bitrate graph?

[cholla]

Cholla did ask before; what software are you using to generate that bitrate graph?

I looked for the software & believe I found it.
Unfortunately it is 64-bit only.
https://www.videohelp.com/software/FFBitrateViewer

I do have Bitrate Viewer. To compare 2 videos I have to open two GUIs.

[Sharc]

Denoising saves bits because the encoding of noise is like encoding of details which is bitrate hungry. See the graph in post#323.

Cholla did ask before; what software are you using to generate that bitrate graph?

Apparently I missed that, being too busy trying to lead cholla out of the madhouse, and finding out for myself and for the GUI lovers how to configure Avidemux for HW/BD compliant x264 settings (post#329), hopefully preventing green artifacts and other threats. (Nothing against Avidemux, but as I am not an Avidemux GUIer it took me some time). Also take note that @cholla's problem was basically solved with post#312 and he can run ffmpeg commandlines, the rest was mainly exhaustive GUI gossip.
The (64bit) ffbitrate viewer is actually irrelevant and out of context anyway, but I see in the meantime @cholla was smart enough to google for bitrate viewers which work for him

[Alwyn]

"Alwyn, ffbitrateviewer." would have sufficed.