This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

From 5:4 to 4:3
#11
Sorry Selur boring you (again) but there is something that i can't understand how works ...  i read a lot about SAR PAR and formats
BUT... i'm using latest dev version...

i have an input AVI that is 720x576 (recorded from pal source)
i place it on Hybrid, to make sure OLD TV can play the deinterlaced output .. just set a RESIZE to 768x576 (leaving PAR without any change) .. mediainfo is (correclty) showing that my input clip is a 5:4 format (correct from PAL)
opening the preview of Hybrid is showed a nice and correct 4:3-Like preview (something like from 5:4 -720x576 to 4:3 768x576)
BUT .. after rendering... VLC is showing a 16:9 clip (saved as 768x576) and also mediainfo is showing the clip as a: 16:9

from where come from this 16:9 if i don't use 16:9 clips ? ... and i just selected on Hybrid a resize? (i have also deleted the Hybrid configuration folder and also reinstalled from scratch)

here a video about what happens: www.wcn.it/D3GOXB23C4.mp4

and attached there is the mediainfo of the output file

[EDIT] installed the standard release of Hybrid and my output is correctly a 4:3... there is something wrong with the DEV version? [/EDIT]


Attached Files Thumbnail(s)
   
Reply
#12
16:9 is the DAR, by changing the SAR, you are also changing the DAR.
Without a debug output I can't really tell what you are doing.
Read the sticky and provide proper data and I can try to reproduce what you did.
I'm not going through some video of what you are doing,..

Cu Sekur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#13
very thank you for your time
here the debug: www.wcn.it/debug.zip
here the clip i used: www.wcn.it/test.avi

doing some more tests seems that using the MKV container show the issue ( a 16:9 output ).. using the MP4 container the output is a correct 4:3. (looking at mediainfo and on played video)


Attached Files Thumbnail(s)
   
Reply
#14
Here's what I did:
  • Started Hybrid
  • Loaded the source.
  • Looked at it. It has a SAR of 720x576 and a PAR of 1:1. Since 1:1 PAR is rather uncommon, I suspect that the content should be 1150/1053 (analog PAL with a DAR of 4:3).
  • Since the input is interlaced, but not flagged as interlaced, I checked whether it's tff or bff. tff has fuild motion when bobbed, so it's tff.
  • Additionally, I cropped the black bars, distortions.
With this I created: par_1150_1053.mp4 and par_1150_1053.mkv using x264 as format like you did in the debug output.
Muxing calls used were:
mkvmerge --ui-language en -o "G:\Output\2023-06-15@16_46_50_3010__03.mkv" --global-tags "G:\Output\mkvtags_2023-06-15@16_46_50_3010__03.xml" -d 0 --default-track 0:yes --default-duration "0:50/1fps" --aspect-ratio-factor 0:1150/1053 --fourcc 0:MP4V --no-chapters --compression -1:none --forced-track 0:yes --field-order 0:0 --no-audio --no-subtitles "G:\Output\2023-06-15@16_46_50_3010_02.264"
and
MP4Box -par 1=1150:1053 -add "G:\Output\2023-06-15@16_47_01_0110_02.264"#video:fps=50:name="":lang="" -brand avc1 -itags tool="Hybrid 2023.06.15.1" -tmp "G:\Output" -new "G:\Output\2023-06-15@16_47_01_0110__03.mp4"
both tell the muxer that the PAR should be 1150:1053.

For the mkv 'mediainfo --full' reports:
Width                                    : 692
Width                                    : 692 pixels
Height                                   : 568
Height                                   : 568 pixels
Stored_Width                             : 704
Stored_Height                            : 576
Sampled_Width                            : 692
Sampled_Height                           : 568
Pixel aspect ratio                       : 1.331
Original pixel aspect ratio              : 1.092
Display aspect ratio                     : 1.621
Display aspect ratio                     : 16:10
Original display aspect ratio            : 1.331
Original display aspect ratio            : 4:3
for the mp4 'mediainfo --full' reports:
Width                                    : 692
Width                                    : 692 pixels
Height                                   : 568
Height                                   : 568 pixels
Stored_Width                             : 704
Stored_Height                            : 576
Sampled_Width                            : 692
Sampled_Height                           : 568
Pixel aspect ratio                       : 1.092
Display aspect ratio                     : 1.329
Display aspect ratio                     : 4:3
Original display aspect ratio            : 1.331
Original display aspect ratio            : 4:3

So yes, something is amiss here.
=> I'll ask the author of mkvmerge about this. (https://forum.doom9.org/showthread.php?p...ost1988463)

It seems to work fine if I use ffmpeg for muxing mkv files, to enabling 'Config->Containers->MKV->FFmpeg for .mkv muxing' should work as a workaround until I manage to figure out what is going wrong with mkvmerge.

Cu Selur

Ps.: I didn't notice this since I usually use PAR 1:1 output. Smile
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#15
seems to me a regression because using an old MKVtoolNix (provided with your build of march) the issue is not happening.

P.S. the unflagged interlaced and the PAR 1:1 are coming from the default software of Blackmagic Intensity Pro ( media express ) i think a lot of other users in the world have similar files.

P.P.S.
Quote:I checked whether it's tff or bff. tff has fuild motion when bobbed, so it's tff.
this is a nice hint Smile thank you!
Reply
#16
I think so, too. (+ I don't think I changed anything around the mkv muxing call, aside from ui-placement of some options.)

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#17
i saw that the issue is not reproducible Sad strange.. maybe is related to the specific clip?
Reply
#18
There was some issue with the mkvmerge binary in Hybrid.
I'll create a new dev version and send you a link once I compiled, packed and uploaded it (~30min), maybe that fixes the problem for you too.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply
#19
meanwhile i made some tests... and replacing the MKVmerge (and company) from official version of Hybrid to the latest dev i have .. make the MKV works fine..


Attached Files Thumbnail(s)
       
Reply
#20
Happy that worked out.

Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Reply


Forum Jump:


Users browsing this thread: 2 Guest(s)