VideoHelp Forum




+ Reply to Thread
Page 4 of 5
FirstFirst ... 2 3 4 5 LastLast
Results 91 to 120 of 147
  1. Why I keep mentioning rgb is because color grading in NLE or applying LUT is in RGB anyway, so you do not avoid it anyway. To keep everything in YUV using your plugins and way of things is not possible.

    Guys are fixing videos in scripts, possibly all the way in YUV, but as soon you involve color grading NLE, you use RGB. If not, then you'd have to use NLE that fixes colors and such in YUV but it all changes for you, not sure with what result.
    Quote Quote  
  2. Originally Posted by lollo View Post
    .... If you want to go to your preferred editor Vegas, you can avoid the "illegal" YUV values (while in AviSynth) adjusting the input levels to stay in the range 16-235, to avoid clipping. This is the most important thing to fix.
    Most important fix and as a rule of thumb yes, but for strict legalization it is not sufficient to just keep the luma (and chroma) within their legal range. For example YUV(230,109,212) would still produce an out-of-gamut (clipped) RED channel.
    Image Attached Thumbnails Click image for larger version

Name:	RGB-YUV cube.png
Views:	30
Size:	40.2 KB
ID:	78794  

    Last edited by Sharc; 2nd May 2024 at 17:15.
    Quote Quote  
  3. Captures & Restoration lollo's Avatar
    Join Date
    Jul 2018
    Location
    Italy
    Search Comp PM
    Originally Posted by Sharc View Post
    Originally Posted by lollo View Post
    .... If you want to go to your preferred editor Vegas, you can avoid the "illegal" YUV values (while in AviSynth) adjusting the input levels to stay in the range 16-235, to avoid clipping. This is the most important thing to fix.
    Most important fix and as a rule of thumb yes, but for strict legalization it is not sufficient to just keep the luma (and chroma) within their legal range. For example YUV(230,109,212) would still produce an out-of-gamut (clipped) RED channel.
    Yes Sharc, we know, but the OP is already confused with basic stuff, no need (now) to complicate his life, I think. Maybe later
    Quote Quote  
  4. Originally Posted by lollo View Post
    Yes Sharc, we know, but the OP is already confused with basic stuff, no need (now) to complicate his life, I think. Maybe later
    It was a hint to those who don't know . It's in the context of the discussed YUV->RGB conversion issues. No intention to open another can of worms
    Last edited by Sharc; 3rd May 2024 at 02:50.
    Quote Quote  
  5. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by VHSvideocapture View Post
    Originally Posted by rgr View Post

    But why? Use Vegas for final editing and final encoding.
    And if you must, use ProRes.
    Or Vukoder plugin and lossless H264 encoding (10bit, YUV444).

    Looking at your operations, I wonder at what point you will save Rec601 as Rec709 and the colors will go to waste After going through Vegas, I'm guessing.

    What if I de-interlace in hybrid thrn safe it as Huffyuv .

    Take that hybrid encoded file into vegas and save it as .h264 in vegas
    Will this be ok and will it save in correct colorspace?
    There is no single answer to your question, it all depends on what you want to do and in what order.

    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly). Especially since you write: "I am using basic color correction plug ins in virtualdub for basic color correction, I also have neat video for cleaning up in virtuldub which is a must on VHS, that also works in RGB". There is no point in changing YUV->RGB->YUV every now and then.
    You can save to ProRes444XQ (YUV) -- there's no need to worry about losing 0.01% fidelity when you end up saving to YUV420 8bit anyway and losing 4-5% fidelity (according to SSIM).

    How should it be exported in .h264 render template.
    Upper field first, lower field first or progressive?
    Just like the source.
    Quote Quote  
  6. [QUOTE=poisondeathray;2733959]
    e.g. Preiere has YUV capable timeline, YUV capable filters. Shotcut can work in YUV too
    [\QUOTE]

    That's good news I will just work in premiere but would I need to set it a certain way?
    What settings on import and export?

    I have an old version of premiere I don't pay for the nee cloud based services.


    Originally Posted by poisondeathray View Post
    But huffyuv YUY2 gets converted to RGB automatically in Premiere and Vegas. For vegas it gets the "bad" RGB conversion with clipping - computer RGB conversion, not studio RGB conversion . Clipping is data loss. The opposite of "lossless"
    can lagrith be used? I was thinking important Huff from Hybrid clean up and transcode lagrith in vegas to .h264


    Originally Posted by poisondeathray View Post
    Those concepts mentioned above apply to vdub RGB filters such as deshaker, and neat video too. That typical RGB conversion can be damaging. Make sure you have legalized the YUV range to Y 16-235, CbCr 16-240 before any RGB conversion in vdub too, also vegas . Or control so you get a full range conversion to prevent Y 0-15, 236-255 range clipping right off the bat
    I've set the levels using graph studio with help from Alywen nothing goes into red but scenes do change from light to dark during films, how damaging is this conversation of colorspaces? Is it visible once you transcode to near lossless compressed.h264 and upload it to a video hosting site YouTube free or Vimeo a paid service?
    Quote Quote  
  7. Originally Posted by rgr View Post

    There is no single answer to your question, it all depends on what you want to do and in what order.

    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly). Especially since you write: "I am using basic color correction plug ins in virtualdub for basic color correction, I also have neat video for cleaning up in virtuldub which is a must on VHS, that also works in RGB". There is no point in changing YUV->RGB->YUV every now and then.
    You can save to ProRes444XQ (YUV) -- there's no need to worry about losing 0.01% fidelity when you end up saving to YUV420 8bit anyway and losing 4-5% fidelity (according to SSIM).

    How should it be exported in .h264 render template.
    Upper field first, lower field first or progressive?
    Just like the source.
    My order is virtuldub then de-noise with neat basic color correction in virtualdub and brightness, contrast, hsl adjustable then I have VD configured to save output as yuv2.

    Take it into hybrid de-interlace resize if needed using Huffyuv codec because hybrid does not have lagrith installed it does have HuffYuv, take it into Vegas do advanced color correction then encoded that yuv file to .h264, but it seems vegas will convert my yuv2 saved video in virtuldub and I'm going to get the wrong color, brightness, white levels on the .h24 encoded by vegas.

    This is how I have understood it please do correct ke if im wrong.
    I can't find a way to solve this.
    Quote Quote  
  8. Member
    Join Date
    May 2005
    Location
    Australia-PAL Land
    Search Comp PM
    I hate to say it but... teach yourself AVISynth/QTGMC. You sound like you've got your head screwed on re video so it won't be very difficult. I should do a guide for it.

    Totally avoid Hybrid.

    Then the flow is simple:

    Set up your 5 line AVISynth script that will deinterlace with QTGMC when you open the AVS file in VDub (you save the script for other projects and just change the filename) (including getting the levels right before entry into VDub)

    Open that script in VDub; apply whatever you need (eg Neat Video, Chromashifting, cropping, resizing) then export as HUFF or LAGS (or any other lossless codec you/Vegas likes)

    Open that exported progressive file in Vegas and finalise and export to your MP4-type format.

    I gave up on Hybrid because it couldn't do all the things I do to videos before the final export. And I'm a Visual person.

    I'm sure it is great for one-stop-shopping a video but it's not for me.
    Quote Quote  
  9. Originally Posted by rgr View Post
    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly).
    Only if the YUV levels are "legal" range first

    Vegas reads 601 / 709 correctly


    Originally Posted by VHSvideocapture View Post
    That's good news I will just work in premiere but would I need to set it a certain way?
    What settings on import and export?

    I have an old version of premiere I don't pay for the nee cloud based services.

    Not good news in Premiere if you use huffyuv 422 for import - it gets clipped too . Unless you're certain the levels are legal

    In that case, it doesn't matter if you use vegas or premiere - both will still get converted to RGB because lossless YUV codecs like huffyuv, lagarith, utvideo are mishandled

    For vegas, you still get the "computer range RGB" conversion, but you only get some expected errors fromr rounding and chroma up/down sampling , not major clipping


    Originally Posted by poisondeathray View Post
    But huffyuv YUY2 gets converted to RGB automatically in Premiere and Vegas. For vegas it gets the "bad" RGB conversion with clipping - computer RGB conversion, not studio RGB conversion . Clipping is data loss. The opposite of "lossless"
    can lagrith be used? I was thinking important Huff from Hybrid clean up and transcode lagrith in vegas to .h264
    Not for import unless the file is legal range to begin with. Lagarith YUV, huffyuv YUV get mistreated by both PP and Vegas





    I've set the levels using graph studio with help from Alywen nothing goes into red but scenes do change from light to dark during films, how damaging is this conversation of colorspaces? Is it visible once you transcode to near lossless compressed.h264 and upload it to a video hosting site YouTube free or Vimeo a paid service?
    I don't know what that process involves, but if you're certain these are legal levels, then you're ok . The "damage" for any integer RGB conversion is minimal and expected. You won't notice it on typical content on a VHS source. You can forget all the other stuff about codecs and editor incompatibilities and colorspaces .

    For higher quality sources, you might notice some deterioration - especially with color boundaries, graphics, solid colors. The reason for the difference is VHS has low chroma resolution to begin with

    For YT/Vimeo , the final file should be legal range to look normal
    Last edited by poisondeathray; 3rd May 2024 at 09:03.
    Quote Quote  
  10. Member
    Join Date
    May 2005
    Location
    Australia-PAL Land
    Search Comp PM
    Originally Posted by PDR
    I don't know what that process involves
    Simply using the digitiser's proc amp to stay within the limits using the VDub histogram. Graphstudio is merely the enabler, as it gives access to the proc amp tab when the video is playing (in most scenarios, the video freezes, disappears, or the proc amp cannot be accessed from within VDub.
    Quote Quote  
  11. Originally Posted by Alwyn View Post
    I hate to say it but... teach yourself AVISynth/QTGMC. You sound like you've got your head screwed on re video so it won't be very difficult. I should do a guide for it.

    Totally avoid Hybrid.

    Then the flow is simple:

    Set up your 5 line AVISynth script that will deinterlace with QTGMC when you open the AVS file in VDub (you save the script for other projects and just change the filename) (including getting the levels right before entry into VDub)

    Open that script in VDub; apply whatever you need (eg Neat Video, Chromashifting, cropping, resizing) then export as HUFF or LAGS (or any other lossless codec you/Vegas likes)

    Open that exported progressive file in Vegas and finalise and export to your MP4-type format.

    I gave up on Hybrid because it couldn't do all the things I do to videos before the final export. And I'm a Visual person.

    I'm sure it is great for one-stop-shopping a video but it's not for me.

    I understand what your saying but I'm frightened to death about downloading filters from avisynth in case I get a virus on the computer, avisynth came with hybrid so it's on the system already and so is QTGMC.

    Hybrid is easy you don't really have to do much just 5 clicks, with Avisynth you have to manually write a script it doesn't have an interface like virtualdub, this is why 99% of people run away from it, the other one percent don't care or don't know about it.

    I wish QTGMC was like Yadif in VD 2 clicks and the video is de-interlaced it is relatively fast as well.
    Quote Quote  
  12. Originally Posted by poisondeathray View Post
    Not good news in Premiere if you use huffyuv 422 for import - it gets clipped too . Unless you're certain the levels are legal

    In that case, it doesn't matter if you use vegas or premiere - both will still get converted to RGB because lossless YUV codecs like huffyuv, lagarith, utvideo are mishandled

    For vegas, you still get the "computer range RGB" conversion, but you only get some expected errors fromr rounding and chroma up/down sampling , not major clipping
    I don't know if they are or not but I sent the pro amp using graph studio.
    I made sure nothing was ij the red zone this should mean levels are legal right?

    Originally Posted by poisondeathray View Post
    But huffyuv YUY2 gets converted to RGB automatically in Premiere and Vegas. For vegas it gets the "bad" RGB conversion with clipping - computer RGB conversion, not studio RGB conversion . Clipping is data loss. The opposite of "lossless"
    How bad is the loss?
    How visible is it on a 24 inch. computer monitor?

    Originally Posted by poisondeathray View Post
    Not for import unless the file is legal range to begin with. Lagarith YUV, huffyuv YUV get mistreated by both PP and Vega
    It should be be because I've set the levels correctly using graph studio with help from Alywen nothing goes into red but scenes do change from light to dark during the films, how damaging is this conversation of colorspaces? Is it visible once you transcode to near lossless compressed.h264 and upload it to the internet a via YouTube free or Vimeo a paid service?

    Originally Posted by poisondeathray View Post
    I don't know what that process involves, but if you're certain these are legal levels, then you're ok . The "damage" for any integer RGB conversion is minimal and expected. You won't notice it on typical content on a VHS source. You can forget all the other stuff about codecs and editor incompatibilities and colorspaces.

    For higher quality sources, you might notice some deterioration - especially with color boundaries, graphics, solid colors. The reason for the difference is VHS has low chroma resolution to begin with

    For YT/Vimeo , the final file should be legal range to look normal
    That's good news
    Quote Quote  
  13. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by VHSvideocapture View Post
    Originally Posted by rgr View Post

    There is no single answer to your question, it all depends on what you want to do and in what order.

    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly). Especially since you write: "I am using basic color correction plug ins in virtualdub for basic color correction, I also have neat video for cleaning up in virtuldub which is a must on VHS, that also works in RGB". There is no point in changing YUV->RGB->YUV every now and then.
    You can save to ProRes444XQ (YUV) -- there's no need to worry about losing 0.01% fidelity when you end up saving to YUV420 8bit anyway and losing 4-5% fidelity (according to SSIM).

    How should it be exported in .h264 render template.
    Upper field first, lower field first or progressive?
    Just like the source.
    My order is virtuldub then de-noise with neat basic color correction in virtualdub and brightness, contrast, hsl adjustable then I have VD configured to save output as yuv2.
    Stick with RGB. These filters work in RGB, so there is no point in converting when saving to YUV. You can save your work in Lagarith 10- or 16-bit RGB (Neat works in RGB64) or ProRes444XQ 10-bit (YUV).
    Don't forget to check the options: Decode Format -> YUV 601, Limited.

    Take it into hybrid de-interlace resize if needed using Huffyuv codec because hybrid does not have lagrith installed it does have HuffYuv, take it into Vegas do advanced color correction then encoded that yuv file to .h264, but it seems vegas will convert my yuv2 saved video in virtuldub and I'm going to get the wrong color, brightness, white levels on the .h24 encoded by vegas.
    Do you really want to denoise first and then deinterlace? Okay . Then do the opposite and compare.
    I don't know Hybrid, if you want to do color correction in Vegas, I would use something 10-bit (ProRes) for the output.

    This is how I have understood it please do correct ke if im wrong.
    I can't find a way to solve this.
    The advice to do deinterlace first and then denoise is still valid.

    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise + color correction with Vegas (Neat).

    Only two steps. The best way, because Vegas works with a bit depth of 32 bits, so you don't lose any quality between Neat and color correction.

    (or:
    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise with VDub (Neat)
    3. Color correction in Vegas.
    )
    Last edited by rgr; 3rd May 2024 at 14:08.
    Quote Quote  
  14. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by poisondeathray View Post
    Originally Posted by rgr View Post
    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly).
    Only if the YUV levels are "legal" range first

    Vegas reads 601 / 709 correctly
    Vegas reads both limited and full range (depending on the format).
    In his case, YUV makes no sense anyway, using YUV no longer makes sense after the first filter in VD.
    Quote Quote  
  15. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    [QUOTE=VHSvideocapture;2734086]
    Originally Posted by poisondeathray View Post
    How bad is the loss?
    How visible is it on a 24 inch. computer monitor?
    You won't see ANY difference, even with a magnifying glass.
    Quote Quote  
  16. Originally Posted by rgr View Post
    Originally Posted by poisondeathray View Post
    Originally Posted by rgr View Post
    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly).
    Only if the YUV levels are "legal" range first

    Vegas reads 601 / 709 correctly
    Vegas reads both limited and full range (depending on the format).
    In his case, YUV makes no sense anyway, using YUV no longer makes sense after the first filter in VD.
    YUV makes sense for VHS capture , and YUV for delivery to YT/Vimeo

    RGB filters are ok - but for huffyuv YUV, lagarith YUV, ut video YUV inputs - convert to RGB using standard method ONLY if the YUV levels are "legal" range first , or you're sure you have no usable data in the 0-15 and 236-255 range - otherwise you clip . It happens with standard vdub RGB conversion too

    And yes, vegas mostly reads other limited/full range files correctly. The issue is the mishandling of the "lossless" YUV formats such as huffyuv, lagarith, ut video



    Originally Posted by VHSvideocapture View Post

    Originally Posted by poisondeathray View Post
    But huffyuv YUY2 gets converted to RGB automatically in Premiere and Vegas. For vegas it gets the "bad" RGB conversion with clipping - computer RGB conversion, not studio RGB conversion . Clipping is data loss. The opposite of "lossless"
    How bad is the loss?
    How visible is it on a 24 inch. computer monitor?
    Negligible for VHS sources if the YUV levels were in legal range before the RGB conversion . But if you had uncorrected usable overbrights, potentially worse, because there will beless detail in bright areas (because they are clipped), and possibly dark areas (less likely, as most sources rarely have usable data < Y=16)

    Chroma up/downsampling losses from YUV 422 => RGB => YUV 422 (or 420) are more visible with sharp color borders, higher quality sources. But VHS has low effective chroma resolution to begin with, so you usually won't see the extra blurring or deterioration
    Last edited by poisondeathray; 3rd May 2024 at 19:27.
    Quote Quote  
  17. yes, op is panicking, thinking of changing a software etc.
    I recommended it as well, legalize levels, that should be a norm anyway, using Vegas or something else.

    Flip the order of apps you work so far, start in Hybrid, legalize levels, deinterlace and load a lossless or almost lossless into Vegas, edit, export.

    Hybrid might even load your own made LUT to legalize blown highlights:
    In Vegas with a test capture clip, in Color Grading select RL Color Wheels, select Highlights and move Y a bit to the left. Watch Histogram so you have legal highlights. Then export that LUT to have it available to load it into Hybrid. I think Selur has some button to load a custom LUT there.
    Quote Quote  
  18. [QUOTE=rgr;2734099]

    There is no single answer to your question

    Stick with RGB. These filters work in RGB, so there is no point in converting when saving to YUV. You can save your work in Lagarith 10- or 16-bit RGB (Neat works in RGB64) or ProRes444XQ 10-bit (YUV).
    Don't forget to check the options: Decode Format -> YUV 601, Limited.
    [\QUOTE]

    I capture RGB, save RGB?
    Vegas does not show REC601
    or BT709 , you just have RGB
    or YUY2 in temple

    Originally Posted by rgr View Post
    Do you really want to denoise first and then deinterlace? Okay . Then do the opposite and compare.
    I don't know Hybrid, if you want to do color correction in Vegas, I would use something 10-bit (ProRes) for the output.
    I can capture and then de-noise in VD but that would mean it would be de-noising interlaced material, Neat asks you about that, it wants you tell it if the footage is interlaced or progressive.

    I could temporarily de-interlace in Yadif - bulit in to VD de-noise once neat is applied I can remove the Yadif interlace filter from the filters list, will this not have a negative effect on the overall image quality?

    Originally Posted by rgr View Post

    The advice to do deinterlace first

    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise + color correction with Vegas (Neat).

    Only two steps. The best way, because Vegas works with a bit depth of 32 bits, so you don't lose any quality between Neat and color correction.

    (or:
    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise with VDub (Neat)
    3. Color correction in Vegas.
    I think 2nd option is best
    1. Capture lossless
    2. Denoise in VD (neat)
    3. Color correction Vegas
    4. Save from Vegas .h264

    What would be the best bitrate?
    Quote Quote  
  19. Originally Posted by poisondeathray View Post
    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly).

    So I should change VD settings to save RGB


    [QUOTE=rgr;2734099]
    Vegas reads both limited and full range (depending on the format).
    In his case, YUV makes no sense anyway, using YUV no longer makes sense after the first filter in VD.

    YUV makes sense for VHS capture , and YUV for delivery to YT/Vimeo

    RGB filters are ok - but for huffyuv YUV, lagarith YUV, ut video YUV inputs - convert to RGB using standard method ONLY if the YUV levels are "legal" range first , or you're sure you have no usable data in the 0-15 and 236-255 range - otherwise you clip . It happens with standard vdub RGB conversion too

    And yes, vegas mostly reads other limited/full range files correctly. The issue is the mishandling of the "lossless" YUV formats such as huffyuv, lagarith, ut video
    [\QUOTE]


    So when I export I should tick the convert VUV to RGB in the huff settings?

    [QUOTE=poisondeathray;2733959]
    Negligible for VHS sources if the YUV levels were in legal range before the RGB conversion . But if you had uncorrected usable overbrights, potentially worse, because there will beless detail in bright areas (because they are clipped), and possibly dark areas (less likely, as most sources rarely have usable data < Y=16)

    Chroma up/downsampling losses from YUV 422 => RGB => YUV 422 (or 420) are more visible with sharp color borders, higher quality sources. But VHS has low effective chroma resolution to begin with, so you usually won't see the extra blurring or deterioration [\QUOTE]


    I have all levels set correctly but brightness and contrast changes scene to scene, but I can lowet brightness levels with VD built in filter and then export lossless to Hybrid de-interlace resize, final color correction.h264 render and not worry about anything else.
    Quote Quote  
  20. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by poisondeathray View Post
    Originally Posted by rgr View Post
    Originally Posted by poisondeathray View Post
    Originally Posted by rgr View Post
    You can immediately save everything in RGB, since it will be assembled in Vegas anyway (which works in RGB and, in addition, I don't know if it reads BT601 correctly).
    Only if the YUV levels are "legal" range first

    Vegas reads 601 / 709 correctly
    Vegas reads both limited and full range (depending on the format).
    In his case, YUV makes no sense anyway, using YUV no longer makes sense after the first filter in VD.
    YUV makes sense for VHS capture , and YUV for delivery to YT/Vimeo

    RGB filters are ok - but for huffyuv YUV, lagarith YUV, ut video YUV inputs - convert to RGB using standard method ONLY if the YUV levels are "legal" range first , or you're sure you have no usable data in the 0-15 and 236-255 range - otherwise you clip . It happens with standard vdub RGB conversion too

    And yes, vegas mostly reads other limited/full range files correctly. The issue is the mishandling of the "lossless" YUV formats such as huffyuv, lagarith, ut video
    Therefore, in his case there is no point in saving the VDub output file in YUV (Huffyuv YUV or Lagarith YUV). Because he already works in RGB after the Deshaker or the Neat filter (or other).
    Last edited by rgr; 4th May 2024 at 17:13.
    Quote Quote  
  21. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by VHSvideocapture View Post

    I capture RGB, save RGB?
    Capture YUV lossless.
    Since you are using VirtualDub with the Neat filter, you are already converting to RGB (Neat only accepts RGB). What's the point of then converting back to YUV (Huffyuv or Lagarith)?

    Originally Posted by rgr View Post
    Do you really want to denoise first and then deinterlace? Okay . Then do the opposite and compare.
    I don't know Hybrid, if you want to do color correction in Vegas, I would use something 10-bit (ProRes) for the output.
    I can capture and then de-noise in VD but that would mean it would be de-noising interlaced material, Neat asks you about that, it wants you tell it if the footage is interlaced or progressive.
    It never occurred to me to denoise interlaced video.I would advise deinterlacing first in Hybrid (QTGMC).
    Originally Posted by rgr View Post

    The advice to do deinterlace first

    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise + color correction with Vegas (Neat).

    Only two steps. The best way, because Vegas works with a bit depth of 32 bits, so you don't lose any quality between Neat and color correction.

    (or:
    1. Deinterlace with Hybrid (save as ProRes444XQ or something lossless).
    2. Denoise with VDub (Neat)
    3. Color correction in Vegas.
    I think 2nd option is best
    1. Capture lossless
    2. Denoise in VD (neat)
    3. Color correction Vegas
    4. Save from Vegas .h264

    What would be the best bitrate?
    In Vegas? Vukoder plugin and setting CRF to 17.

    But where's the deinterlacing?
    Quote Quote  
  22. Originally Posted by rgr View Post
    Therefore, in his case there is no point in saving the VDub output file in YUV (Huffyuv YUV or Lagarith YUV). Because he already works in RGB after the Deshaker or the Neat filter (or other).
    Yes

    But the original huffyuv can have problems with RGB encoding . FFMpeg Huffyuv option in vdub2 can do RGB but it will be flagged progressive. Lagarith will not have interlaced flags or field order signalling either

    It's not a problem if you interpret the field order correctly in the next software

    Originally Posted by VHSvideocapture View Post

    So I should change VD settings to save RGB

    So when I export I should tick the convert VUV to RGB in the huff settings?
    Exporting RGB after RGB filters makes sense

    But the original huffyuv can have problem with RGB output - it often converts back to YUY2 . There are several huffyuv variants around, maybe one of the does it correctly
    Quote Quote  
  23. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by poisondeathray View Post
    But the original huffyuv can have problem with RGB output - it often converts back to YUY2 . There are several huffyuv variants around, maybe one of the does it correctly
    So as usual, I recommend UTVideo for lossless conversion





    But: "Assume interlace video" is now non-recommended feature.
    Last edited by rgr; 4th May 2024 at 17:47.
    Quote Quote  
  24. Originally Posted by rgr View Post

    But: "Assume interlace video" is now non-recommended feature.
    Like lagarith, UT's interlaced status, and field order, aspect ratio - is not read by very many programs - so manually interpreting is usually required in the next program
    Quote Quote  
  25. Originally Posted by rgr View Post
    Therefore, in his case there is no point in saving the VDub output file in YUV (Huffyuv YUV or Lagarith YUV). Because he already works in RGB after the Deshaker or the Neat filter (or other).
    filter then save RGB
    Can I save original file as YUY2 then convert to RGB using direct stream copy option?
    or save YUY2 then save RGB?

    Originally Posted by rgr View Post
    But the original huffyuv can have problems with RGB encoding . FFMpeg Huffyuv option in vdub2 can do RGB but it will be flagged progressive. Lagarith will not have interlaced flags or field order signalling either
    Lagrith always shows as progressive it doesn't flag correctly

    Huffyuv does seem to foat but always bottom field first.

    Originally Posted by rgr View Post
    Exporting RGB after RGB filters makes sense

    But the original huffyuv can have problem with RGB output - it often converts back to YUY2 . There are several huffyuv variants around, maybe one of the does it correctly
    I have the original Huff the experts say use the original.
    Quote Quote  
  26. Originally Posted by poisondeathray View Post
    But: "Assume interlace video" is now non-recommended feature.

    Like lagarith, UT's interlaced status, and field order, aspect ratio - is not read by very many programs - so manually interpreting is usually required in the next program
    I de-interlace and tell hybrid to ignore input scan and I always change it to upper field first even huffy that shows bottom field first in hybrid media info section.

    Then I get shimmering on playback on the encoded file if I color correct in vegas first that's why I won't be doing that.
    I don't even resize in virtualdub or vegss I resize in hybrid, I read somewhere the shimmering can happen if it has been cropped snd resized?.

    At the moment I'm just going to capture stuff and then get back to all this because it all seems very complicated.
    Quote Quote  
  27. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by VHSvideocapture View Post
    Originally Posted by rgr View Post
    Therefore, in his case there is no point in saving the VDub output file in YUV (Huffyuv YUV or Lagarith YUV). Because he already works in RGB after the Deshaker or the Neat filter (or other).
    filter then save RGB
    Can I save original file as YUY2 then convert to RGB using direct stream copy option?
    or save YUY2 then save RGB?
    What for?
    And you can't convert anything using Direct Stream.

    Originally Posted by rgr View Post
    But the original huffyuv can have problems with RGB encoding . FFMpeg Huffyuv option in vdub2 can do RGB but it will be flagged progressive. Lagarith will not have interlaced flags or field order signalling either
    Lagrith always shows as progressive it doesn't flag correctly

    Huffyuv does seem to foat but always bottom field first.

    Originally Posted by rgr View Post
    Exporting RGB after RGB filters makes sense

    But the original huffyuv can have problem with RGB output - it often converts back to YUY2 . There are several huffyuv variants around, maybe one of the does it correctly
    I have the original Huff the experts say use the original.
    Expert says: use UTVideo
    Quote Quote  
  28. Member
    Join Date
    Aug 2018
    Location
    Wrocław
    Search PM
    Originally Posted by VHSvideocapture View Post
    Originally Posted by poisondeathray View Post
    But: "Assume interlace video" is now non-recommended feature.

    Like lagarith, UT's interlaced status, and field order, aspect ratio - is not read by very many programs - so manually interpreting is usually required in the next program
    I de-interlace and tell hybrid to ignore input scan and I always change it to upper field first even huffy that shows bottom field first in hybrid media info section.
    Set it as in the source.
    Quote Quote  
  29. Member
    Join Date
    May 2005
    Location
    Australia-PAL Land
    Search Comp PM
    Originally Posted by VHSVideocap
    I always change it to upper field first even huffy that shows bottom field first in hybrid media info section.
    Almost all analogue captures are Top Field First. If in doubt, you can check the field order by opening the file in VDub, set up the Deinterlace filter to YADIF and Double Frame Rate TFF. Then step through the video and if you've set the wrong field order, the video will jump backwards and forwards. From my dim recollection of Hybrid, you had to set TFF every time.
    Quote Quote  
  30. Originally Posted by Alwyn View Post
    Almost all analogue captures are Top Field First. If in doubt, you can check the field order by opening the file in VDub, set up the Deinterlace filter to YADIF and Double Frame Rate TFF. Then step through the video and if you've set the wrong field order, the video will jump backwards and forwards. From my dim recollection of Hybrid, you had to set TFF every time.
    That's what I always thought but whenever I capture with Huff and send it to Hybrid the media info section always says bottom field first I just ignore and ask it to overwrite input scan to TFF.
    I hope I am doing the correct thing by ignoring it?
    Quote Quote  



Similar Threads

Visit our sponsor! Try DVDFab and backup Blu-rays!