View Profile
View Forum Posts
Private Message
As suggested I downloaded QTGMC for Avisynth. As far as I know I have all the needed elements.
When I try to run it on a Huffyuv test file I get the error shown. Also including a shot of my plugins folder to confirm I have what's needed.
This is the script I'm using
AviSource("e:\test segment.avi")
QTGMC ( Preset="slow" )
Thanks for all assistance.
+ Reply to Thread
Results 1 to 30 of 57
-
-
ConvertToYV12(interlaced=true)
Post your avs script
It should look something like
Code:AVISource("video.avi") ConvertToYV12(interlaced=true) QTGMC(preset="faster") -
You beat me to it, I revised my original post.Originally Posted by poisondeathray
-
So does it work now? If not, post the error message
-
Your script works, why doesn't the original? It came off the Avisynth.org site.Originally Posted by poisondeathray
-
Because your source video wasn't in YV12 (Y'CbCr 4:2:0 planar) . Some filters require certain colorspaces or models. The clue was in the error message (mentioning RGB32)Your script works, why doesn't the original? It came off the Avisynth.org site.
There is a QTGMC variant that can work in YUY2 (Y'CbCr 4:2:2), but it's slower and requires some fiddling with specific dlls
What is your source video, and why is it in RGB? -
Original source is DV captured off VHS. Then converted to Huffyuv just to retain as much original quality as possible after processing and upscaling to 1080p.Originally Posted by poisondeathray
This really does work well. From initial tests it seems to be in a different universe than the deinterlacer plugins for Virtualdub. I see it also makes some nice adjustments to brightness and contrast. -
DV captured from a VHS source should be Y'CbCr , not RGB. HuffYUV normally comes as YUV , that's what the YUV stands for (YUV can be used synonomously with Y'CbCr)Originally Posted by brassplyer
Original source is DV captured off VHS. Then converted to Huffyuv just to retain as much original quality as possible after processing and upscaling to 1080p.Originally Posted by poisondeathray
This really does work well. From initial tests it seems to be in a different universe than the deinterlacer plugins for Virtualdub. I see it also makes some nice adjustments to brightness and contrast.
You're doing something in your workflow to inadvertently convert it to RGB (quality loss, possibly clipping) - unless you are converting to RGB on purpose for some processing, like color work ? (and even if you did it on purpose, you might have to make adjustments before converting it to RGB to avoid clipping)
QTGMC does NOT make changes to brightness, contrast. These are all signs of red flags in your workflow -
Btw, what makes you say it's in RGB? It's a HuffYuv file. Is that RGB?Originally Posted by poisondeathray
-
I say your file is RGB because of the error message you posted in post #1 . That's why I went on to ask about your source - it raised a "red flag" . You shouldn't have an RGB source to start withOriginally Posted by brassplyer
Btw, what makes you say it's in RGB? It's a HuffYuv file. Is that RGB?Originally Posted by poisondeathray
Huffyuv can come in RGB, or YUY2 . But DV is YUV 4:1:1. When captured with huffyuv, it should be YUY2 (4:2:2), not RGB. You're inadvertently converting to RGB somewhere in your workflow . Maybe describe in more detail the steps prior to this stage -
This is the mediainfo output.Originally Posted by poisondeathray
After capturing DV via firewire passthru from a Sony Digital8 cam, I then re-saved it as a HuffYuv file, not RGB. Chose Huff Yuv from the codecs in Virtualdub and saved it as avi.Maybe describe in more detail the steps prior to this stage -
Did you use video=>fast recompess in vdub before saving the clip ?
If you load a clip by using
AVISource()
Info()
It will post the colorspace -
No, was I supposed to? I used full processing mode.Originally Posted by poisondeathray
-
Could you spell this out a bit more? Is this an avisynth script?Originally Posted by poisondeathray
-
full processing mode in vdub will cause you to incur RGB conversion . What operations are you doing in vdub at that stage? (most vdub filters require conversion to RGB)
-
Originally Posted by brassplyer
Could you spell this out a bit more? Is this an avisynth script?Originally Posted by poisondeathray
What I mean is if you load that as an avs script, preview it with vdub, or avspmod, it will tell you information about the clip in the corner of the preview, including the colorspace -
Yes, comes up as RGB. Hmmm... if I don't want it to save that way, how should I convert to Huff from DV in Vdub?Originally Posted by poisondeathray
To be honest, though I *like* the results - maybe it's not supposed to change the brightness/contrast, but it looks good.
Also, I appreciate you taking the time to walk me though this. -
Describe exactly what you are doing at that stage - why are you converting to huffyuv then ?
You can load DV-AVI directly into avs scripts , resaving it as huffyuv for farther processing provides zero benefit, just a waste of space . Unless you meant AFTER processing ?
Why are you even using vdub ? What are you using it for ?
What you would normally do is load the DV in the avs script (with QTGMC), so now you have bobbed 720x480p59.94 , then use vdub in "fast recompress" mode with huffyuv or other lossless codec . Then that can be used as input into other programs
If your other processing can be done in avs script (e.g. you can bob & upscale in the script), you avoid the colorspace conversions and quality loss. Sometimes, it's unavoidable (some color work is better/easier to do in RGB) -
Loading DV file into Vdub, choose Huff compression (full processing), save file. Done.Originally Posted by poisondeathray
Simple to use, found some filters that do what I want - except for the one crucial step of deinterlacing. That particular function falls short in Vdub.Why are you even using vdub ? What are you using it for ?
Converting to Huff because it's going through a couple of stages of processing - deinterlace, then taking that deinterlaced file and applying filters and upscaling to 1080p, then converting that to Blu-Ray. My understanding is Huff is lossless as opposed to DV, won't take a hit at the various stages. DV also can't be converted to 1080p which Huff can.Last edited by brassplyer; 3rd Dec 2012 at 23:57.
-
Ok, but you're allowing vdub to do the RGB conversion. It doesn't handle interlaced YV12 conversions correctly (if your DV decoder outputs YV12, you're messing up the chroma; if it outputs YUY2 you're safe for that part) . But I would deinterlace firstOriginally Posted by brassplyer
Loading DV file into Vdbu, choose Huff compression (full processing), save file. Done.Originally Posted by poisondeathray
Ok, normally you would deinterlace before everything else, so you can stilll do what you're doing , but keep track of when you are in RGB . If you can find the equivalent filter in avisynth, you don't have to go to RGB at allSimple to use, found some filters that do what I want - except for the one crucial step of deinterlacing. That particular function falls short in Vdub.Why are you even using vdub ? What are you using it for ?
Converting to Huff because it's going through a couple of stages of processing - deinterlace, then taking that deinterlaced file and applying filters and upscaling to 1080p, then converting that to Blu-Ray. My understanding is Huff is lossless as opposed to DV, won't take a hit at the various stages. DV also can't be converted to 1080p which Huff can.
You don't want to convert back and forth (each trip incurs loss, and gets worse each trip). Yes - huffyuv is lossless, but a lossless codec is only "lossless" in the same colorspace .
Also 1080p59.94 is not blu-ray compatible (not to mention a waste from a DV source). You would have to re-interlace it at the resolution to 1080i59.94 . Even 720p59.94 which is blu-ray compatible is a waste IMO. I would leave it SD, but if that doesn't turn you on, then 720p59.94 is a better option than re-interlacing it and allowing the TV to deinterlace (you spend all this time with QTGMC to go to waste) -
The point is that if possible, it's better not to change colorspaces (use VDub filters) at all. So if maybe you told us what VDub filters you find so necessary, we can suggest pure AviSynth equivalents. The only time I ever go into RGB is if I have some serious color work to do.
For example, elsewhere you mentioned using the Smooth Deinterlace filter, which is a complete waste of time, as I think you discovered later.
Edit: pdr beat me to it.
-
Ultimately my goal is going from this...
To this....
-
Is that the only frame rate at which QTGMC will save?Originally Posted by poisondeathray
-
Easy enough in AviSynth. And not Hi-Def, either.Originally Posted by brassplyer
Ultimately my goal is going from this...
[Attachment 14980 - Click to enlarge]
To this....
[Attachment 14981 - Click to enlarge]
It's a bobber. That means double the framerate. Add SelectEven after it if you want progressive 29.97fps.Originally Posted by brassplyer
-
-
Originally Posted by brassplyer
Is that the only frame rate at which QTGMC will save?Originally Posted by poisondeathray
No, it's a frame rate at that resolution that is incompatible with blu-ray
When you bob deinterlace NTSC VHS it will be 59.94 frames/second (essentially each field becomes a frame)
The only progressive blu-ray compatible upscaled resolution will be 720p59.94 . You don't want to make it "30p" and throw away 1/2 the frames - it will become jerky, motion less smooth. And I doubt you want to re-interlace it - you just used QTGMC for almost nothing then -
What do I need to do to use this deinterlacer and with the ultimate goal of eventually turning it into Blu-Ray compatible 1080p video?Originally Posted by poisondeathray
Originally Posted by brassplyer
Is that the only frame rate at which QTGMC will save?Originally Posted by poisondeathray
No, it's a frame rate at that resolution that is incompatible with blu-ray
When you bob deinterlace NTSC VHS it will be 59.94 frames/second (essentially each field becomes a frame)
The only progressive blu-ray compatible upscaled resolution will be 720p59.94 . You don't want to make it "30p" and throw away 1/2 the frames - it will become jerky, motion less smooth. And I doubt you want to re-interlace it - you just used QTGMC for almost nothing then -
Why ??Originally Posted by brassplyer
From a VHS source?!!
The effective resolution of VHS is crap. Upscaling it won't make it look better
The only 1080p compatible resolution/framerate is 1080p29.97 (encoded as 1080i59.94) , but you lose 1/2 the frames . 1080p24 and 23.976 is compatible but not applicable for you
Like I said it's a complete waste from a good SD source, even more of a complete uber super waste from a VHS source.
If you're going to upscale for bluray, 720p59.94 makes more sense. You keep all the frames & smoothness. People won't be able to tell between upscaled 1080, 720., or 480 from a VHS source, but you can tell between 29.97p and 59.94p at any resolution -
Deep cleansing breaths...deep cleansing breaths..Originally Posted by poisondeathray
Why ??Originally Posted by brassplyer
From a VHS source?!!
The effective resolution of VHS is crap. Upscaling it won't make it look better
In part as an experiment. Simply upscaling it won't make it look better but tweaking it - as per the screen shots above - will. It won't be out of the box VHS. Certainly not true HD but better than normal VHS. The idea is to have it in an HDTV format already and not depend on some player to do the upscaling.
Are you saying it's not possible to end up with smooth, 29.97 1080p video using this deinterlacer? -
Yes, but it' s not the deinterlacer's fault. 59.94 will be smoother than 29.97, as simple as that. It's just math - you're throwing away half the motion samples. The original video , when deinterlaced by the TV will look like 59.94 on a flat panel .Originally Posted by brassplyer
Do this simple test
QTGMC()
vs
QTGMC()
SelectEven()
Just watch it as SD resolution. It will look buttery smooth in the 1st case , but look relatively jerky in the 2nd . On some types of content it might not be noticeable. Things like action, sports, big , big difference
I don't know why someone would jump through all these hoops with a lossless workflow only to throw away 1/2 the data later.
QuoteSimilar Threads
-
Using Avisynth MT with QTGMC
By agni451 in forum Video ConversionReplies: 11Last Post: 15th May 2014, 07:37 -
Using QTGMC in ffmpeg
By agni451 in forum Video ConversionReplies: 1Last Post: 10th Nov 2012, 10:16 -
Add QTGMC Deinterlacer to MeGUI's avisynth script creator drop down list?
By Simcut in forum Newbie / General discussionsReplies: 2Last Post: 30th Jul 2012, 16:58 -
QTGMC Help
By TuFFrabit in forum Newbie / General discussionsReplies: 16Last Post: 23rd Jun 2012, 06:53 -
MSU Deinterlacer Problems
By kernelhack in forum RestorationReplies: 3Last Post: 26th Sep 2008, 13:16