Hybrid/Vapoursynth is crushing shadow detail?
2 Attachment(s)
I am trying to use QTGMC to de-interlace some Video8 tapes, and having a problem with colors. I think colorspace, but I'm pretty inexperienced there, so who knows. Mebe you.
Background: I'm getting decent captures from my Osprey 260e connected with S-Video to a CCD-TRV108 with [EDIT], [TCB], and [DNR] all turned on. There's a very occasional tear at near the beginning of some scenes because the tapes were sometimes playback reviewed while shooting, and the tapes were never striped first, so the VTR TCB has a hiccup while it catches up and sorts things out, but there aren't a lot of these borders, and 99 percent of scenes are captured looking like they do on the the old tube TV with no issues. I don't really think this is relevant, but what the heck. I'd like these to eventually be watchable on a 1080p display, so I'm working on establishing a workflow for deinterlace, upscale, and noise removal. Hitting a snag at the first step. I'm using the latest Hybrid package for MacOS from https://www.selur.de/downloads The only thing I've checked is the checkboxes for: Use QTGMC selected Fast selected Even selected Bob not selected OpenCL selected Not doing any other processing right now (I was earlier, but stripped it all out for troubleshooting, and it\'s still happening. The container is AVI, and video is processed to FFvHuff But the shadows look like this! Attachment 14445 Original: Attachment 14446 It's got something to do with video levels, and digital colorspaces, but I'm not sure where to start. |
Post a segment of your video to better understand and do some experiment...
|
2 Attachment(s)
Original: Attachment 14447
After going through Hybrid: Attachment 14448 Why is the filesize cut in HALF? That doesn't seem like it should be possible unless I'm really screwing up somewhere. I'd much prefer to cut the huffing all together since they're a pain in the neck for file interchange, none of my NLE's will read them, and I have storage galore, but I can't figure out how to get Hybrid to output uncompressed AVI files. |
8 Attachment(s)
If you see problems with your Hybryd flow, it must be related to it, so double check your settings. Using a GUI like Hybryd is not easy, because some processing on the video can be hidden or not managed by the user.
I do not use Hybrid, so I am not familiar with its options and cannot help here, sorry. Some preliminary remarks:
Attachment 14449 The levels and histogram on captured video looks ok, and in the range 16-230: Attachment 14450 Attachment 14451 The histogram on your processed video shows an expansion to 0-235, thus you see darker areas. You can compensate for that with Levels() at the end of the processing according to your taste: Attachment 14452 I quickly run a not optimized avisynth script to deinterlace, denoise and upscale, and I do not see a level problem. The histogram of the final video is narrower than yours: Attachment 14454 Here a comparison between sample.avi resized and video processed, compressed to mp4 for upload size reason. A bit of plastic look and halo on video processed because not optimized script: Attachment 14455 Here a comparison between sampleQTGMC.avi resized and video processedd, compressed to mp4 for upload size reason: Attachment 14456 For final delivery you can compress to h264 using ffmpeg in a command line: Code:
ffmpeg.exe -i input.avs -c:v libx264 -aspect 4:3 -c:a aac output.mp4 Used script: Attachment 14457 Edit: your deinterlaced file is at the same framerate as the original, so not sure anymore what you wanted to achieve... |
2 Attachment(s)
I added a bit of HDRAGC with
Code:
hdragc(corrector=0.5) Attachment 14458 Attachment 14459 |
HuffYUVMT: http://www.digitalfaq.com/forum/vide...lters-pre.html
Quote:
720 vs 640: OK, I admit, I’m waaaay down the rabbit hole at this point, but we’re talking about the horizontal dimension right? It’s already showing the overscan on the left side, and the PAR is correct and not distorted. Are you saying it’s cutting the video signal off the right side? Or that I should be capturing non square pixels? This is Video8 not Digital8 iiiif that makes a difference? Deinterlaced is at the same frame rate: Er, wasn’t this captured at 59.98i and I am trying to output 29.97p, or have I greatly misunderstood what QTGMC is doing? Halos: Preeeeetty sure I’ve got that all turned off/down as far as it will go, but will double check. Maybe is the [DNR] in the Sony? Quote:
|
1 Attachment(s)
Quote:
Quote:
A reference file (PAL, replace 576 with 480): http://www.arachnotron.nl/videocap/d..._cap_v1_en.pdf Quote:
interlaced frames video, 25 frames (50 fields) per second (25 frames i) frame1 frame2 frame3 frame4 frame5 frame6 frame7 frame8 A..........C..........E.........G................. ........................................(field 0) even lines b..........d..........f..........h................ .........................................(field 1) odd lines PAL50Ii --> field 0 and field 1 are even and odd lines of "camera" frames taken at different time [true interlaced video] [Bob interpolates the missing scanlines to make progressive frames] QTGMCdeinterlaced [frame count is doubled] frame1 frame2 frame3 frame4 frame5 frame6 frame7 frame8 A..........B'..........C..........D'.........E.... .....F'.........G..........H'..........(field 0) even lines a'..........b..........c'..........d..........e'.. ......f..........g'..........h..........(field 0) odd lines x' and X' represents scanlines interpolated from X and x Quote:
It does not happen when processing your video with a "standard" AviSynth filtering. If you add a bit of more processing (hdragc) you can improve a bit the overall look; here a final comparison between original video and full processed video: Attachment 14462 If you do not wish to move to standalone AviSynth, try to debug your Hybrid settings. Maybe some user with experience on Hybrid can help here, or ask direct to Selur on his forum. He's a very nice person! |
I will ask Selur
|
Scratch that - I found the "Show Vapoursynth Script" button in Hybrid and checked to see what it was doing in the background. Turns out: a whole bunch of unnecessary color-space conversion. Commented it all out and ran it myself in the terminal and ffmpeg is outputting the correct levels.
Weird. Works for me, though. Also: Quote:
|
Well done ;)
|
Quote:
Cu Selur |
Welcome Selur! Nice to have you here
|
Thanks!
Hopefully bradgranath can give some feedback regarding the unncessary color space conversions. :) Cu Selur |
Quote:
|
Correct, there is a peak. But we normally call a pattern "spike" if it is much higher than the average profile. And in this case if you look to the histogram of the OP processed video, there is no sign of crushed levels.
Once the OP posts is procedures as requested, we'll understand what happened inside his flow. |
Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.