Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
18th April 2019, 18:40 | #21 | Link | |
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
|
|
18th April 2019, 18:42 | #22 | Link |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Yes it does confirm, but you'd see it had switched to encoding qp=0 anyway in the encode parameters - check with MediaInfo > Text view.
__________________
Nostalgia's not what it used to be |
18th April 2019, 18:50 | #23 | Link | ||
Registered User
Join Date: May 2011
Posts: 347
|
Quote:
that line would show you Matrix value, if 2, it means unknown, 1 is 709, 5 is 470bg (PAL DV), 6 is 170m (NTSC DV), before encoding don't forget to comment out that line or right after you load clip you could make sure and and set props correctly so Vapoursynth knows what the input is: clip = core.std.SetFrameProp(clip, prop="_Matrix", intval=6) clip = core.resize.Bicubic(clip, format=vs.YUV422P8, matrix_s="709") btw, QTGMC takes YUV422P10 or YUV444P10 also Quote:
Last edited by _Al_; 18th April 2019 at 19:15. |
||
18th April 2019, 18:52 | #24 | Link | |
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
Code:
Encoding settings : cabac=0 / ref=1 / deblock=0:0:0 / analyse=0x1:0x131 / me=umh / subme=9 / psy=0 / mixed_ref=0 / me_range=24 / chroma_me=1 / trellis=0 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=0 / threads=18 / lookahead_threads=1 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=0 / weightp=0 / keyint=1 / keyint_min=1 / scenecut=40 / intra_refresh=0 / rc=cqp / mbtree=0 / qp=0 |
|
18th April 2019, 19:04 | #25 | Link | |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 398
|
Quote:
The resize command: Code:
clip = core.resize.Bicubic(clip, format=vs.YUV422P8, matrix_in_s="170m", matrix_s="709") |
|
18th April 2019, 19:08 | #26 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
There you go, qp=0. Yes, I think with the linux version of MediaInfo you have to look in 'Show All Formats' or something. I'm not on linux just now to check.
__________________
Nostalgia's not what it used to be |
|
18th April 2019, 19:24 | #27 | Link |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Actually, to qualify that - with 8bit sources libx264 swiches -crf 0 to -qp 0 automatically when encoding to 8bit (by default or set -pix_fmt). But for 10bit sources and 10bit x264 encoding, you need to set -qp 0.
__________________
Nostalgia's not what it used to be |
18th April 2019, 21:57 | #28 | Link | |
Registered User
Join Date: Sep 2006
Posts: 1,657
|
Quote:
|
|
18th April 2019, 23:26 | #29 | Link | |
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
The aspect ratio is incorrect, and the video looks off. AVI input file to VapourSynth: Code:
Width : 720 pixels Height : 480 pixels Pixel aspect ratio : 0.889 Code:
Width : 720 pixels Height : 480 pixels Pixel aspect ratio : 1.000 To correct this, I've updated my ffmpeg command with "setsar=sar=8/9,setdar=dar=4/3" as follows.. Did I do this correctly?! Code:
vspipe --y4m ./Deinterlace.py -a "INVID=$INVID" - | ffmpeg -nostdin -i pipe: -i "$INVID" -pix_fmt yuv422p -c:v libx264 -crf 0 -tune fastdecode -x264opts keyint=1 -c:a copy -map 0:0 -map 1:1 -vf setsar=sar=8/9,setdar=dar=4/3 "$OUTVID" Code:
Width : 720 pixels Height : 480 pixels Pixel aspect ratio : 0.889 |
|
19th April 2019, 00:51 | #30 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,469
|
Quote:
Without getting into a lengthy AR interpretation discussion, that's one way of getting 4:3 DAR . Typically I only set the SAR, because setting the DAR will only give you non ITU aspect ratio options But for analog sources like VHS, technically the SAR is actually 10:11 . DV too. And those are what you are using according to the 1st post. The central portion or active image area is 702 width (rounded to 704), and pillar boxed You can verify with some objects, such as a round clock or car tire shot straight on. 99% of the time 10:11 will give you the perfect circle, but 8:9 will give you slightly oval. It also depends on the lineage and what steps or types of transfers were done inbetween. It also depends on the software, you might have to interpret the AR in some software, but resolve can distinguish between the two (at least with the SAR flag) It's the same with upscaling to HD . The AR will be slightly off if you use the wrong AR interpretation. (But many people don't care about tiny AR error . I guess it depends on how picky you are, or if driving on "oval" tires is ok ) |
|
19th April 2019, 03:43 | #31 | Link | |||
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
Quote:
According to "ffprobe -i", my AVIs are: Code:
Stream #0:0: Video: dvvideo (dvsd / 0x64737664), yuv411p, 720x480 [SAR 8:9 DAR 4:3], 28772 kb/s, 29.97 fps, 29.97 tbr, 29.97 tbn, 29.97 tbc Quote:
When it comes time to process in Resolve, I'll likely scale up 2x, crop those pillarboxes and the fuzzy bit at the bottom of the image out (not sure what it's called, but it's that distorted portion at the bottom of old video recordings). Do you have a suggestion for dimensions to output from Resolve? Would you avoid cropping? I want to do this properly, but am unsure what the "right way" would be. Last edited by sunshine; 19th April 2019 at 03:56. |
|||
19th April 2019, 04:08 | #32 | Link | ||
Registered User
Join Date: Sep 2007
Posts: 5,469
|
Quote:
ffprobe/ffmpeg , like mediainfo cannot tell you things such as what the actual content AR is. It will only tell you what the flags or how it was encoded. The content SAR is probably 10:11 . If you use 8:9 likely you will get ovals instead of circles for things like DV, VHS . 99.9% of those types of sources will NOT use 8:9. They will use the ITU aspect ratio rules So I am suggesting -vf setsar=sar=10/11 , but you have to check the actual footage with known objects or references because all sorts of things might distort the AR (studio screw up before broadcast, bad cap etc...) But a native DV camcorder will use ITU rules 99.9% of the time Quote:
Personally, I wouldn't use resolve to do this part . It's too limited of an editor (it's getting better... but... can't handle simple things like interlace properly). I would actually keep it as DV interlaced and edit it that way in a proper editor Resolve is fantastic for some things, not so much for others. Pros/cons |
||
19th April 2019, 05:18 | #33 | Link | |
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
|
|
19th April 2019, 06:14 | #35 | Link | |
Registered User
Join Date: Sep 2007
Posts: 5,469
|
Quote:
But the native DV camera, don't waste your time. Or do it for fun, because 99.9% is really underestimating and conservative. It's really 100% for 4:3 NTSC DV. https://en.wikipedia.org/wiki/Pixel_aspect_ratio PAR (pixel aspect ratio) is known as "SAR" (sample aspect ratio) in MPEG4 terminology. They mean the same thing, they just decided to change names. You can think of it as the w:h of the pixels . Eitherway 10:11 is correct . It's been confirmed many, many times over the years, and it's official in all the documentation and ISO standards Here is another recent example from another forum from a DV camera https://forum.videohelp.com/threads/...e5#post2547654 4/3 = 704/480 * 10/11 And definitely, "archive" is the original DV footage . Keep that safe. Something better might come along (definitely for scaling; but nothing on the horizon in the near future for deinterlacing compared to QTGMC, but you never know, some parts of it can be improved such as the NNEDI3 routines) |
|
19th April 2019, 17:44 | #36 | Link | |
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
1. Archiving the original MiniDV and Hi8 cassettes, though they're becoming effectively inaccessible due to the obsolescence of the hardware needed to use them. 2. Archiving the AVI transfers from the MiniDV camera. I'll keep these unedited as-is. They're not very "watchable" though, as they're interlaced and most playback devices my family/ friends will be using will not automatically deinterlace, and when they do, they do so relatively poorly compared to QTGMC for example. 3. From the AVIs, I'm producing deinterlaced, edited, color corrected, and likely scaled version for consumption on modern devices. If someone wants to view the original AVIs, they'll remain accessible for years to come. If they want to view the cassettes, it'll be a challenge but they'll be here. For day to day viewing, I feel the deinterlaced, edited, color corrected versions will be the most enjoyable. I think I'm covering all my bases with this approach, but I could be wrong. Thoughts? |
|
19th April 2019, 17:49 | #37 | Link | ||
Registered User
Join Date: Apr 2019
Posts: 17
|
Quote:
So it's a mixed bag.. and ideally I'd like to at least eliminate any damage I might do to it by goofing the AR. So a quick test (shot using analog Hi8, and some shot on Digital8, both sent to the PC via the same path described previously) may help me to identify any issues I'm introducing through this approach. Quote:
|
||
19th April 2019, 18:21 | #38 | Link | |
Cary Knoop
Join Date: Feb 2017
Location: Newark CA, USA
Posts: 398
|
Quote:
|
|
19th April 2019, 21:37 | #39 | Link |
Registered User
Join Date: Apr 2019
Posts: 17
|
For archival, I’m keeping the AVIs produced during WinDV transfer. For intermediary output I’m using x264 lossless in MOV, and for final output from Resolve I’m looking for a good lossless option for archival, and will use x264 in mp4 or mov for local use and pushing to YouTube.
|
19th April 2019, 22:12 | #40 | Link | |
Registered User
Join Date: Jan 2004
Location: Here, there and everywhere
Posts: 1,197
|
Quote:
https://forum.blackmagicdesign.com/v...s+TIFF#p494354
__________________
Nostalgia's not what it used to be Last edited by WorBry; 19th April 2019 at 22:29. |
|
Tags |
deinterlace, qtgmc, resize, resolve, vapoursynth |
Thread Tools | Search this Thread |
Display Modes | |
|
|