digitalFAQ.com Forums [Archives]

digitalFAQ.com Forums [Archives] (http://www.digitalfaq.com/archives/)
-   Video Encoding and Conversion (http://www.digitalfaq.com/archives/encode/)
-   -   KVCD: LBR Encode problem? (http://www.digitalfaq.com/archives/encode/2735-kvcd-lbr-encode.html)

andybno1 02-22-2003 01:54 PM

KVCD: LBR Encode problem?
 
firstly I'm using this script:

Code:

LoadPlugin("C:\fitcd\mpeg2dec.dll")
LoadPlugin("C:\fitcd\fluxsmooth.dll")
LoadPlugin("C:\fitcd\GripFit_preview.dll")
LoadPlugin("C:\fitcd\blockbuster.dll")
LoadPlugin("C:\fitcd\legalclip.dll")
LoadPlugin("C:\fitcd\convolution3d.dll")
LoadPlugin("C:\fitcd\dustv5.dll")

Mpeg2Source("C:\BBCDVD1118\VIDEO_TS\Stasis Leak.d2v")
legalclip()
GripCrop( width=352, height=288, overscan=0 )
GripSize()
#PixieDust()
SpaceDust()
#faerydust()
Convolution3d(preset="movieLQ")
Blockbuster(method="noise", variance=.5, seed=1)
GripBorders()
LegalClip()

I spotted when tmpgenc was encoding that there was a bluey tinge in the video. Here is a sample the blue tinge is not in the source.

kwag 02-22-2003 02:09 PM

Re: LBR Encode problem
 
Quote:

Originally Posted by andybno1
I spotted when tmpgenc was encoding that there was a bluey tinge in the video. Here is a sample the blue tinge is not in the source.

Start by removing filters and run a test. Like this:

Code:

LoadPlugin("C:\fitcd\mpeg2dec.dll")
LoadPlugin("C:\fitcd\fluxsmooth.dll")
LoadPlugin("C:\fitcd\GripFit_preview.dll")
LoadPlugin("C:\fitcd\blockbuster.dll")
LoadPlugin("C:\fitcd\legalclip.dll")
LoadPlugin("C:\fitcd\convolution3d.dll")
LoadPlugin("C:\fitcd\dustv5.dll")

Mpeg2Source("C:\BBCDVD1118\VIDEO_TS\Stasis Leak.d2v")
legalclip()
GripCrop( width=352, height=288, overscan=0 )
GripSize()
#PixieDust()
#SpaceDust()
#faerydust()
#Convolution3d(preset="movieLQ")
#Blockbuster(method="noise", variance=.5, seed=1)
GripBorders()
LegalClip()

And see if the blue thing dissapears. If it does, start adding filters one at a time until you find the one that is causing that. If you still have that effect with all filters removed, remove the GripCrop, GripSize and GripBorders too, and adjust aspect in TMPEG. If that removes it, then the problem is GripX.

-kwag

Kane 02-22-2003 02:20 PM

talking about GripCrop, i´m still wondering , what the option overscan means

GripCrop( width=352, height=288, overscan=0 )

where´s the difference between overscan=0 , 1 or 2?[/u]

kwag 02-22-2003 02:29 PM

Quote:

Originally Posted by Kane

where´s the difference between overscan=0 , 1 or 2?[/u]

Consumer TV sets use overscan to prevent black vertical bands from appearing due to variations in the horizontal deflection circuitry of TV sets. Overscan causes a loss of an average of five percent of the image on each side of the tube. So when you set overscan blocks to 1 or 2, you're encoding less film area and making the image smaller. When you play it back on your TV, it will be expanded flush with the edges and you won't loose image on the sides :wink:
Overscan 0 doesn't do any resize. 1 = 8 lines on each side, and 2 = 16 lines on each side.

-kwag

andybno1 02-22-2003 03:21 PM

I used the script u suggested, still got the blue now if I remove all grip filters whats best to put in place of gripcrop?

kwag 02-22-2003 03:26 PM

Quote:

Originally Posted by andybno1
I used the script u suggested, still got the blue now if I remove all grip filters whats best to put in place of gripcrop?

Just set aspect on TMPEG to full screen, keep aspect. Don't worry about the aspect. It's just to find out what's causing the problem.

-kwag

andybno1 02-22-2003 03:30 PM

I already have tmpgenc set to full screen in tmpgenc because its a 4:3 source.

Kane 02-22-2003 04:33 PM

thx for info


All times are GMT -5. The time now is 05:18 AM  —  vBulletin © Jelsoft Enterprises Ltd

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