digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Video Capturing / Recording (http://www.digitalfaq.com/archives/capture/)
-   -   Recording Video: What's Best to do? (http://www.digitalfaq.com/archives/capture/5195-recording-video-best.html)

andybno1 09-09-2003 11:11 AM

Quote:

Originally Posted by incredible
Quote:

Originally Posted by andybno1
firstly heres the script I used as indicated in the link posted by incredible:

....

and well I got one interesting colour sceme.

here is the sample. Anyone know what is wrong here?

(first you have to tell the people to copy the URL in the browser adressbar directly to get into the link, it seems that Yahoo prohibits links to Files)

Well your encoding example seems to be strange!
Maybe its a Problem when using this script handling NTSC Streams?

As I told ....

Quote:

LoadVirtualdubPlugin("C:\Virtualdub\Smart.vdf","_V D_smartdeinterlace",1)
_VD_smartdeinterlace(0, 1, 15, 100, 0, 0, 0, 0, 1, 2, 1, 0)
.. this line has to be used with caution, cause I don't know if these Values are the same for NTSC.

But, how does the Pictore look like when opening the .avs in Windows Media Player?
ok?

If there are still Problems ... try to switch off these lines as quoted right here above by adding a "#" in front of the lines and do a test, also by watching the .avs in WindowsMediaPlayer.
If the problem is gone, then you have to correct the Number Values of the Vdub PlugIn by loading this movie into Virtualdub, adding the SmartDeinterlace Filter an do your special settings in the Window.
Let it run in Vdub to test your deinterlacing. If its ok, safe the processing Settings in Vdub and open the .vcf file using Windows Editor.
Copy exactly the new values strored in the line where the SmartDeinterlace command is shown and post them into the capture .avs script.

Another problem could be the ConvertToYV12() command.
Whats the colorspace of your Avi?
Try to switch off the ConvertToYV12() line and do a test. Gone?
Or try to change it to ConvertToYUY2().

Well lets see if it helps.

Let me know .... ;-)

well for starters I didn't know geocities had a link protection on as it was fine when I left clicked it.

I'll have a go at those lines, bt I get same results in media player. and this aint a ntsc stream its pal capture from satalite. Nothin wrong with my encodin samples, its only that small cause I have dialup and decided to only do a few seconds encodin. The colourspace is 16 rgb

but anyway I'll get onto this one way or another lol.

incredible 09-09-2003 11:21 AM

Quote:

and this aint a ntsc stream its pal capture from satalite
Satelite???

How do you capture? Directly from the receiver?
Do you have the possibility to capture digital?
If yes, this stream could be progressive if its "captured" (better said "streamed") digitally.

Well give me infos ;-)

But anyway if you receive a PAL program via satelite, your receiver will convert it to NTSC so your TV will accept it. So you still receive a NTSC interlaced stream from your receiver if captured using an analog capture-card.

andybno1 09-09-2003 12:25 PM

its a satalite feed captured via vdub in vfw drivers. captured at 640 480 (don't ask why) usin mjpeg codec with forecd quality of 80and capture quality set to 100 colourspace is rgb 16 bit

incredible 09-09-2003 05:47 PM

Quote:

Originally Posted by andybno1
its a satalite feed captured via vdub in vfw drivers. captured at 640 480 (don't ask why) usin mjpeg codec with forecd quality of 80and capture quality set to 100 colourspace is rgb 16 bit

Whats the name of your card?
Which mjpeg codec do you use?
and capturing using rbg 16bit???? Wow, isnt it possible to capture at least at rgb 24 or even YUV??

I think there is a problem with the colorspace you use, and it seems that you really capture at NTSC interlaced, thats why you have to check the script as I mentiones above (deactivating the deinterlacing lines just for testing).

Well the standard capture size for PAL is 704x576 and I think for NTSC its 640x480, .. thats why.

Try to use the PicVideo Codec for capturing, it gives you a good quality by using less HD space for capturing. And you can capture using YUV!

andybno1 09-09-2003 06:49 PM

could ya give a link to this codec pls.

incredible 09-10-2003 02:54 AM

http://www.pegasusimaging.com/picvideomjpeg.htm

Its a trial version and it puts a note on the black bars in the screen, but you can overlap it when using the Avisynth command

Letterbox(xx, xx, 16, 16)

Or you use the HuffYUV codec:
http://www.divx-digest.com/software/huffyuv.html

It needs more space on HD but also as named a YUV Codec ... and its free!

vmesquita 09-10-2003 09:00 AM

@andybno1,

According to someone at dvdrhelp.com, you can also install the Trial of ShowShifter (a TV recording program) and deinstall, and it will leave behind a freeware Picvideo MJPEG codec. Never tested but lots of people said it works.
And for really lossless codecs, besides huffyuv, there are some lossless YV12 codecs in doom9 forum that take about 70% less space than HuffYuv. If I remember correctly, the name of the codec is VBLE. I have used it with great results, but generally I use PicVideo MJPEG because I only got a 40 Gb HD! :(
Capture using at least YUYV, any RGB is a waste of space and a consequent loss, since your source signal is YUYV, and you're converting to RGB.

@incredible and vhelp
I like avisynth deinterlacers and they don't perform slow in my atlhon XP 2000+, but It's also a matter of taste... :D For trully interlaced stuff I prefer Tomsmocomp or FieldDeinterlace(blend=false). GreedyHMA is said to be good with hybrid material. By the way, decomb 5.00 (which fielddeinterlace is part of) has been released this week, I haven't tried it yet but you can find at doom9 forum...
Actually, I don't like to deinterlace, because the picture looks wired for my eyes when there's movement. Even when back in my CVD days, I never deinterlaced stuff. I believe there's no way to build a perfect deinterlacer since you need a temporal information you don't have... :D But that's of course my personal oppinion.

[]'s
VMesquita

incredible 09-11-2003 05:56 AM

Quote:

Originally Posted by vmesquita
For trully interlaced stuff I prefer Tomsmocomp or FieldDeinterlace(blend=false). ...

Ill try it again to see ;-)

Quote:

Actually, I don't like to deinterlace, because the picture looks wired for my eyes when there's movement. Even when back in my CVD days, I never deinterlaced stuff. I believe there's no way to build a perfect deinterlacer since you need a temporal information you don't have... :D But that's of course my personal oppinion.
I totally agree with you!
But with noisy captures you already get less CQ (even when handling them via Avisynth) and so I decided for myself to work with adaptive deinterlacing methods like the SmartDeinterlacer to be able to encode at mpeg1 which only supports non-interaced encoding. Ther're also other adaptive deinterlacers and I'm still running through the web to find the best for me which gives me the Quality I need. The advantage of deinterlacing is also to encode your mpeg afterwards in mpeg1 which doesn't support interlaced encoding.
So I'll try FieldDeinterlace(blend=flase) to compare it with the smartDeinterlacer and others ... ;-)
And thats the point of captures: If you work with DVD mpeg sources you most will work with a good quality sources, but in case of captures there is a mega-big bandwith from noisy bad up to good little-grainy.
In my case of handling captures with avisynth, every avisynth script for each capture is special "modifyed" cause of the difference of each capture.
(more less denoising, more less sharpening and so on...).
There will not be the "right" capture avs script to use for general, its just a basic script as a base for further optimizations.

;-)

So lets see Varmesquita if we get a good combination of our both experiences. Would be great ... cause it seems that you do the "other" way: NTSC ... right?

Tantos saludos
Inc.

vmesquita 09-11-2003 06:23 PM

Quote:

Originally Posted by incredible
I totally agree with you!
But with noisy captures you already get less CQ (even when handling them via Avisynth) and so I decided for myself to work with adaptive deinterlacing methods like the SmartDeinterlacer to be able to encode at mpeg1 which only supports non-interaced encoding. Ther're also other adaptive deinterlacers and I'm still running through the web to find the best for me which gives me the Quality I need. The advantage of deinterlacing is also to encode your mpeg afterwards in mpeg1 which doesn't support interlaced encoding.
So I'll try FieldDeinterlace(blend=flase) to compare it with the smartDeinterlacer and others ... ;-)
And thats the point of captures: If you work with DVD mpeg sources you most will work with a good quality sources, but in case of captures there is a mega-big bandwith from noisy bad up to good little-grainy.
In my case of handling captures with avisynth, every avisynth script for each capture is special "modifyed" cause of the difference of each capture.
(more less denoising, more less sharpening and so on...).
There will not be the "right" capture avs script to use for general, its just a basic script as a base for further optimizations.

;-)

So lets see Varmesquita if we get a good combination of our both experiences. Would be great ... cause it seems that you do the "other" way: NTSC ... right?

Tantos saludos
Inc.

incredible,

There are pretty good (and pretty slow) denoising plugins for avisynth. For real hard analog noise, there's nothing better than GoldDust (from the dust package), GrapeSmoother and CNR. But of course you have to regulate youre filtering according to the level of noise. To use GoldDust with analog stuff I have a special script, I can give you if you want.
For not so hard analog noise, PeachSmoother, CNR and GrapeSmoort are my choice.
For my Satellite captures, I use almost always the Convolution3D script I posted. The only modification I sometimes do is remove Undot when the signal is very clean.
As vhelp pointed, some stuff are really worse to deinterlace. The worst material is those shaky and panning home movies. They will look awful deinterlaced, no matter what you do. But I deinterlace a ABBA DVD and it looked OK most of the time.
An extra tip. If you want, try Procoder (an MPEG encoder) using MPEG2 CVD at 352x480. Encode interlaced, 1-pass VBR in Mastering Quality mode. Beware that's very slow, but it'll produce the best output from interlaced noisy stuff you'll ever see.
And yes, I am in NTSC land! :D

[]'s
VMesquita

andybno1 09-13-2003 09:27 AM

well I have found out its not any of the filters, I done a script with just the avisource line in and I still got the colour problem so god knows whats wrong.

Boulder 09-13-2003 02:01 PM

Could you post some screenshots of the color issue? I couldn't get the mpg file in that link earlier in this thread.

andybno1 09-13-2003 03:40 PM

right click the link and save target as just tried it then and it works for me.

Boulder 09-13-2003 04:03 PM

Looks to me you'll need SwapUV() added to the script. Put it right after the AVISource line.

andybno1 09-14-2003 08:33 AM

cheers for the SwapUV() line worked a treat. :ole: hurray for Boulder :ole:

xiaNaix 09-17-2003 12:24 AM

Quote:

Originally Posted by vmesquita
There are pretty good (and pretty slow) denoising plugins for avisynth. For real hard analog noise, there's nothing better than GoldDust (from the dust package), GrapeSmoother and CNR. But of course you have to regulate youre filtering according to the level of noise. To use GoldDust with analog stuff I have a special script, I can give you if you want.
For not so hard analog noise, PeachSmoother, CNR and GrapeSmoort are my choice.

Hey! I'd like to have a look at your noise reduction scripts. I'm also capturing NTSC VHS as 352x480 Huffyuv. If you would, post 'em up or PM me. :D

Stutz 09-17-2003 10:11 AM

vmesquita,
I too would be very interested in seeing your noise reduction scripts using GoldDust. NTSC VHS @ 352x480 Huffyuv. Also, is there a filter that will help control the 'blooming' of red colors in a VHS capture?

vmesquita 09-17-2003 04:47 PM

Quote:

Originally Posted by Stutz
vmesquita,
I too would be very interested in seeing your noise reduction scripts using GoldDust. NTSC VHS @ 352x480 Huffyuv

Ok! I'll post it later. :D
Quote:

Also, is there a filter that will help control the 'blooming' of red colors in a VHS capture?
I think there isn't such a thing... :( The only way to cure this would be using a TBC.

[]'s
VMesquita[/quote]

Boulder 09-18-2003 03:31 AM

You might be able to do something about the colors by using RGBAdjust (internal Avisynth 2.5 filter).

From the documentation:

RGBAdjust(clip, float red, float green, float blue, float alpha)

This filter multiplies each color channel with the given value, clipping the result at 255.

You could try reducing the red channel and see if it helps.

vmesquita 09-23-2003 09:26 AM

Here it goes:
Quote:

AVISource("capture.avi")

#Cropping and Resizing #
########################
#Crop(12,6,628,228).AddBorders(12,6,12,12).Bilinea rResize(352,240)
Crop(24,24,672,432).AddBorders(24,24,8,24).Bilinea rResize(352,480)

#Filtering (heavy ) #
#####################
cnr2()
GrapeSmoother(80)

#Dust#
######
SeparateFields()
Weave()
Setparity(false)
UnFoldFieldsVertical(true)
Golddust()
FoldFieldsVertical(true)

unfilter(25,0)
#Functions #
############
# SetParity
#
# Sets the parity of a clip.
#
# PARAMETERS:
# parity - true for TFF;
# false for BFF
#
function SetParity(clip c, bool parity)
{
return parity ? c.AssumeTFF() : c.AssumeBFF()
}
# UnfoldFieldsVertical
#
# Separates the fields in a clip and stacks them vertically.
# Regardless of field order, even fields are on top.
#
# PARAMETERS:
# flip - pass true to flip the bottom field vertically;
# useful when dealing with spatial filters
# (default: false)
#
function UnfoldFieldsVertical(clip c, bool "flip")
{
flip = default(flip, false)
oldParity = c.GetParity()
c = c.AssumeTFF().SeparateFields().AssumeFrameBased()
top = c.SelectEven()
bottom = c.SelectOdd()
c = StackVertical(top, flip ? bottom.FlipVertical()
\ : bottom)
return c.SetParity(oldParity)
}
# FoldFieldsVertical
#
# Folds fields from a clip that resulted from calling
# UnfoldFieldsVertical.
#
# PARAMETERS:
# flip - pass true if the bottom field was flipped vertically with
# UnfoldFieldsVertical
# (default: false)
#
function FoldFieldsVertical(clip c, bool "flip")
{
assert(c.Height() % 2 == 0, "FoldFieldsVertical: unexpected frame height")
flip = default(flip, false)
oldParity = c.GetParity()
originalHeight = c.Height() / 2
evens = c.Crop(0, 0, c.Width(), originalHeight)
odds = c.Crop(0, originalHeight, c.Width(), originalHeight)
odds = flip ? odds.FlipVertical() : odds
c = Interleave(evens, odds).AssumeFieldBased().AssumeTFF().Weave()
return c.SetParity(oldParity)
}
I resize before filtering because GoldDust is very slow. You can Tweak GrapeSmoother according to the source. Please remember that this is only for very Bad VHS.

[]'s
VMesquita


All times are GMT -5. The time now is 03:57 PM  —  vBulletin © Jelsoft Enterprises Ltd

Site design, images and content © 2002-2024 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2024 Jelsoft Enterprises Ltd.