I'll be the first to admit, I probably understand scaling and resolution less than I do most advanced x264 options, so this may be user error, but I can't figure it out for the life of me.
I noticed "shimmering" in a video I encoded today, and my first thought was I screwed up something with the output resolution settings.
I double checked my log and it seems correct:
Crop and Scale (width=1920:height=804:crop-top=138:crop-bottom=138:crop-left=0:crop-right=0)
[17:49:58] + source: 1920 * 1080, crop (138/138/0/0): 1920 * 804, scale: 1920 * 804
[17:49:58] + Output geometry
[17:49:58] + storage dimensions: 1920 x 804
[17:49:58] + pixel aspect ratio: 1 : 1
[17:49:58] + display dimensions: 1920 x 804
I was viewing on a Playstation 4 served by a Plex server that was direct streaming the file locally. I then loaded the file into VLC and viewed it directly from the server and the shimmering was still evident and looked exactly the same as through Plex..
The _only_ strange thing I can find is VLC reports the resolution as 30 pixels taller.
Resolution: 1920x834
Display resolution: 1920x804
I then tried disabling any anamorphic settings and cropping completely:
[22:57:52] + Crop and Scale (width=1920:height=1080:crop-top=0:crop-bottom=0:crop-left=0:crop-right=0)
[22:57:52] + source: 1920 * 1080, crop (0/0/0/0): 1920 * 1080, scale: 1920 * 1080
[22:57:52] + Output geometry
[22:57:52] + storage dimensions: 1920 x 1080
[22:57:52] + pixel aspect ratio: 1 : 1
[22:57:52] + display dimensions: 1920 x 1080
...and the shimmering is still there with VLC reporting as:
Resolution: 1920x1090
Display resolution: 1920x1080
Logs are attached for both examples referenced above.
I can upload a small sample file and lossless chapter from the source if needed.
If this is user error, I'd appreciate some guidance. Thanks!
Encode a video through handbrake and potentially notice shimmering or a moire pattern in the output. Check VLC Media Information > Codec for different resolution than what appears in Handbrake logs.
1.0.2
Windows 10
Kingsman The Secret Service T01-1_anamorphic.m4v 01-29-2017 00-01-43.txt
Kingsman The Secret Service T01-1_no anamorphic.m4v 01-28-2017 23-10-45.txt
Disabling anamorphic is the same as setting a 1:1 pixel aspect ratio, which the source already is; aside from the cropping, there should be no difference between those encodes. The logs seem straightforward enough, so it may be unrelated.
Nothing obvious comes to mind, so I'll let others contribute their thoughts.
If this helps:
Notice the brick to the left at the beginning, the floor when he walks in, and the most obvious part is the grey sweater of the guy standing front and center towards the end.
The interlace detection filter thinks those frame are interlaced, so it deinterlace them. I guess the wood texture is misleading it. So disable decomb and interlace detection.
@cameronks Can your turn off the decomb for me and try again?
[23:10:45] decomb: deinterlaced 3634 | blended 0 | unfiltered 0 | total 3634
Oh actually you don't have the interlace detection filter enabled, and it's deinterlacing everything.
Yup, Closing.
@galad87 Thanks. Yes, Deinterlace was set to Decomb with Preset and Interlace Detection both set to Default as they are in the preset,
I checked my other recent logs from other sources and every frame is deinterlaced there as well. Switching from Decomb to Off for now fixes it.
Should I edit this Issue to clarify Decomb is Deinterlacing everything or start a new one?
It's supposed to if interlace detection is turned off.
@sr55 It would seem Interlace Detection would need to be turned off in the preset then since it's not detecting but deinterlacing everything it sees? I looked at recent logs from other encodes, and every file has every frame deinterlaced and this is progressive source material.
I'll get logs put together and make a new Issue unless I'm wrong in my thinking here.
Ideally, if you have all progressive content, set Deinterlace to None. Otherwise, if you have mixed content, set interlace detection to a suitable value.
You have it turned off, so it didn't do the detection part, which means it'll deinterlace every frame.