View Full Version : Filters for use with DVB-S recordings?
chrome307
29th February 2008, 11:22
Hi there
I was looking for some help with helping me encode recordings I have made with my PC satellite card, which records in TS format.
I am looking at creating a script that only uses a 1 Pass encode simply for speed purposes.
So far, after recording my TS stream, I then use DGIndex to demux the video and save as a *.d2v.
http://b.imagehost.org/0173/TS_INFORMATION_IN_DGINDEX.png
Once I have carried this out I then use BeLight to convert the audio stream from *.MPA to *.MP3.
Then I use an Avisynth script to load my video into VirtualDub Mod
LoadPlugin("C:\Program Files\AviSynth 2.5\plugins\dgdecode.dll")
mpeg2source("c:\Clip.d2v")
BilinearResize(640,352)
This is the area I need help with.
If I use the video in Gordian Knot and select the Field Operations.
http://b.imagehost.org/0173/DEINTERLANCE_OPTIONS_GORDIAN_KNOT.png
I guess I should be using these options, but when I preview the output using any of these I do not see much difference on playback.
Is this because I have resized the video thereby eliminating the need for deinterlacing ( common sense tells me not ).
Therefore some help with this would be appreciated.
Needless to say I don't use Gordian Knot but VirtualDub Mod, so I thought I should add this option in the above script.
In VirtualDub Mod I use FAST RECOMPRESS ( told it saved on Colour Conversion ) and select Single Pass Encode with the Xvid codec ( Quarter Pixel Off + Maximum Consecutive BVops = 1 + Profile Level = Advanced Level @ L5 ). This I had hoped would be suitable for playback on a Xvid DVD player.
My understanding was that Quarter Pixel ON + Maximum Consecutive BVops = 2 would be better for PC playback.
Thanks for reading and I look forward to your comments.
Guest
29th February 2008, 12:12
If your video is interlaced it is a terrible idea to resize it before deinterlacing, unless you resize it by half by throwing away a field (but you haven't done that). If you have a film (progressive) it's OK and deinterlacing isn't needed.
Is your material interlaced or progressive?
chrome307
29th February 2008, 12:43
If I load up the video clip in TMPGenc Express this is the information given:
http://b.imagehost.org/0173/1_20.jpg
So as my source is interlaced in this case
Guest
29th February 2008, 12:52
As I said, if it is interlaced, it is terrible to resize it before deinterlacing. Or, if you want to keep it interlaced, you need to use a special resizing technique designed for interlaced content. You can find it by searching the forum.
chrome307
29th February 2008, 12:58
When I find this resizing filter for interlaced material, can I simply add it to my *.avs file (above) and leave in the BilinearResize?
(adding it to my VirtualDub MOD plugin folder)
Hope that makes sense?
btw Is deinterlacing necessary if the output is going to be on my UK PAL TV which is interlaced?
I'm not trying to make a movie or DVD which which are progressive, that's my understanding.
Guest
29th February 2008, 18:13
If you are making a PAL DVD, then you can leave it interlaced, but your resize is wrong because 640x352 is not a legal PAL DVD resolution. Why do you want to resize it?
chrome307
1st March 2008, 15:43
I'm not making a DVD, I just want to simply convert the TS recording from my PC Satellite card to Xvid format quickly using a single pass encode. I have added the resize option in my script to lower the overall size of the Xvid file.
Is this wrong?
I have found various 'Xvid Bitrate Calculators' which have various options for 'overall file size' 'input/output' etc
http://b.imagehost.org/0179/1_30.jpg
I have searched the forum and found topics that cover recording from PC DVB Satellite cards, but these suggest using tools like MEGUI to do the encoding. I do not wish to use additional tools as I was quite happy learning to use Avisynth in this manner.
Guest
1st March 2008, 15:49
No, it's not wrong.
You need a good TV out interface to pass interlaced to your TV. Also if you want to view it on a PC, you'll want to deinterlace it.
So deinterlace or not, that's your choice. If you do, then deinterlace before resizing. If you don't, then use the special interlaced resizing.
You have now added a picture of the bitrate calculator but there is no question. Why did you post that?
chrome307
1st March 2008, 15:54
The reason I posted the picture was to explain why I resized the video from 720 x 576 to a smaller size ( but I only found this yesterday! ) so would amend the line
BilinearResize(640,352)
From your comments I should interlace ( using my old Xbox with XBMC for playback ), which filter do I use for my PAL recordings and can this simply be added to my script?
Sorry for asking these questions ( but it helps me tremendously ) , if this is not appropriate in this section and needs to be moved to another section, can you do this?
Thank you for your patience!
Guest
1st March 2008, 16:27
From your comments I should interlace ( using my old Xbox with XBMC for playback ), which filter do I use for my PAL recordings and can this simply be added to my script? You should interlace?! Is that a typo? Do you mean deinterlace? Please explain because you're losing me now.
Comatose
1st March 2008, 17:53
In short, you should deinterlace and *then* resize.
chrome307
2nd March 2008, 11:03
Oops sorry Neuron2, it was a typo !!
OK, now that we are agreed I need to 'deinterlace' can anyone tell me how ? and can I simply add this to my script to use in Virtual Dub OR is it a separate process that requires the use of another application?
thanks!
20-40
2nd March 2008, 12:44
I doubt that you need deinterlace - appears as you have 25 fps - PAL source. Feed your .avs in Vdub and watch for presence of "jagged" edges in fast moving frames. If you cannot find them, you have true 25 fps as PAL should be (but rarely it is not, maybe one in hundred captures ain't).
I do it with simple .avst template, which is almost what you need IF your .ts is 29.97 and I doubt it is 'couse you speak of 25 fps and PAL (I have PAL too):
Cap2Xvid(NTSC).avst
[MPEG2Source("%f")]
#crop(8,64,0,-64) # Uncomment to crop if needed
#UnDot() # Uncomment to remove mosquito noise
FieldDeinterlace()
#FOR 29.970 source to Film 23.976 fps
Decimate(cycle=5)
LanczosResize(704,416)
# TRIM
#trim(0,189240)
For PAL is similar Asynther template without deinterlacing (not needed for PAL):
Cap2Xvid(PAL).avst
[MPEG2Source("%f")]
#crop(8,64,0,-64) # Uncomment to crop if needed
#UnDot() # Uncomment to remove mosquito noise
LanczosResize(704,416)
# TRIM
#trim(0,189240)
Change just first line (choose your .d2v source) and save as .avs. I use them for years.
P.S. If you already have .mp3, it's a bad practice, bytheway. Why? Trimming (cutting-out commercials or unneeded stuff).
It is better to convert to .wav, perform AudioDub inside .avs, THEN trim as you want in VDMod (afterward open in Tools tab of VDMod your script, and click on trim line (for now commented out with #) inside the script, then on Edit, then on Insert Framesets as trims)). That way, you won't loose sync, and you can convert to any fps you want by AssumeFPS(…,true) for instance 23.976 to 25 fps.
Such .avs then open in VD and choose CBR 128 kbps MP3 as audio compression and for video IF you really want 1-pass, choose CQ encoding and some decent quant. 3.4 to 3.8. Most standalones DO have problems only with q-pel and GMC, newer ones have NO problems with Xvid's b-frames (1 or 2). Mark Adaptive Quantization (as YES). You do NOT want Xvid's packed bitstream. Level is best to be "unrestricted".
Anyhow, you don't need GordianKnot.
Guest
2nd March 2008, 14:08
OK, now that we are agreed I need to 'deinterlace' I can't agree to that without seeing your specific source material. It may be progressive. You could post a link to an unprocessed source clip for us to inspect.
can anyone tell me how? I'm resisting the temptation to issue a rule 1 strike here. :)
and can I simply add this to my script to use in Virtual Dub OR is it a separate process that requires the use of another application? There is a large selection of Avisynth deinterlacing filters to choose from.
Guest
2nd March 2008, 14:11
I doubt that you need deinterlace - appears as you have 25 fps - PAL source. Feed your .avs in Vdub and watch for presence of "jagged" edges in fast moving frames. If you cannot find them, you have true 25 fps as PAL should be (but rarely it is not, maybe one in hundred captures ain't). PAL isn't inherently more progressive than NTSC. It all depends on the content. Just as with NTSC, sports and live video are almost always interlaced, not progressive (leaving aside HD progressive formats).
20-40
2nd March 2008, 14:43
Sure, I must lied. Sorry, all 200 Gigabytes of my captures must be deinterlaced. Also, read again what I wrote, then call me again stupid.
chrome307
2nd March 2008, 16:40
Thank you for your input and suggestions so far.
I have uploaded a series of samples from my DVB-S and DVB-T capture cards, you did not specify the length of each clip so I made a few
http://www.mediafire.com/?ix9tvh3yvjk
Hope this helps
[EDIT]
Here's another clip which seems to Progressive/Interlaced ? .... football coverage
http://www.mediafire.com/?qx31cbteibw
chrome307
5th March 2008, 15:15
Any feedback on the samples that you requested??
Guest
5th March 2008, 15:55
I looked at three of the seven:
1. 20080302-160418-PREMIERE_SPORT_3.TS
This is interlaced content, which is not surprising for sports.
2. 20080302-141116-BBC_World_PROGRESSIVE.TS
You say this is progressive but it too is interlaced. The video of the guy in the middle is interlaced (new picture each field) while the background graphic is progressive, but overall it is interlaced content.
3. 20080302-141154-PREMIERE_1_PROGRESSIVE.ts
This one really is progressive.
The method for deciding is easy. Apply SeparateFields and then open in VirtualDub to step through the fields. If you see new pictures at every field (in a segment with good motion), it is interlaced content. If you see a new picture every two fields, it is progressive content.
chrome307
6th March 2008, 11:11
Thank you for again for your answers and taking the time for looking at the samples .... lol wasn't too sure how many to add .
Regards
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.