grayline with mpeg2source

[lexor]

heya guys,

I'm having a weired problem with avisynth 2.5.6a (I just got this one after reinstall), I capture my HDTV fine (1080i which is what's broadcast), no problem with .ts, I used HDTVtoMPEG2 no problem, got my .mpg file, plays fine no artifacts. open it up in DGIndex, save the project, no probs.

now avs script:

mpeg2source("clip.d2v")

simple, huh? and it produces a thick gray line under the image (in the black area) if I try to playback .avs, and it's still there if I encode a sample to x264 (tried xvid too) so it's not an on-the-fly artifact, it actually adds gray line to picture.

any ideas what the problem could be? I never had avisynth do this before on any source and quite frankly I'm at a loss as to what could be wrong in such a simple setup.
(I know it needs deinterlace, that doesn't help, so here I keep the script simple for debugging)

[Pookie]

I'm not certain of the cause, but you might want to run Fix1088.exe on the source file.

"fix1088 Will process a transport stream recording to remove the grey
or black bar that you see at the bottom of some 1080i broadcasts. It
will replace any vertical size value of 1088 in the sequence headers
with 1080. Note that sometimes the grey bar is caused by a bug in
the decoder rather than in the encoder, in which case this will not help.

Usage: fix1088 [-s] <input file/pattern> <PID>
-s: save input files instead of overwriting them
specify PIDs in hex without the leading 0x.


fix1088 has not been tested with files greater than 2 GB, but I think
it should work."

http://www-personal.umich.edu/~balaz...88/fix1088.exe

[neuron2]

Why do you need to run HDTVtoMPEG2, rather than just opening it in DGIndex directly?

[laserfan]

When I encounter this (using AutoGK to convert my 1080i ts to Xvid) AGK "sometimes" adds that line to the Xvid. Something about needing 1088 not 1080 to be divisible by 16. Dunno why, but the grey/white line doesn't always appear, but...

The solution with AutoGK is just to crop it off (CTRL-F9). Not sure what you are trying to do, but avisynth can crop it of course.

[lexor]

Originally Posted by neuron2

Why do you need to run HDTVtoMPEG2, rather than just opening it in DGIndex directly?

becouse it doesn't open them, tells me to check pids, but the .mpg I extract plays back fine, I'll try that fix1088 later, but does it take in .ts or .mpg?

[Pookie]

Fix1088 works on Transport Streams.

[laserfan]

I use AutoGK which is Avisynth-based. AGK always detects my 1080i ts captures as '1920x1088'. When I look at these captures with other tools, they say 1920x1080. Then I run fix1088 on them, and it finds nothing to fix!

When I run a FILM-based 1080i program thru AGK (again, detected as 1920x1088) it applies Telecide to the program, and it comes out (Xvid) with no grey line.

When I run an Interlaced 1080i program thru AGK (which always as I've said states it is 1088) it applies KernelDeint to the program and it comes out with the grey line at the bottom.

As I said, fix1088 doesn't work. Something about the way AGK detects these files, and Telecide (OK) and KernelDeInt (not OK).

Bottom line: I have to use CTRL-F9 and crop 8 pixels off the bottom of an interlaced 1080i ts program to avoid the grey line. Film-based doesn't have the same problem.

[lexor]

sweet gorilla of manila, crop(0,0,0,-8) fixed it, and I run leakkerneldeint no probs on it as well. thanx a bunch laserfan

now I just have a nice clean script without needing to run any other tools

[neuron2]

Originally Posted by lexor

becouse it doesn't open them, tells me to check pids

If you'd bother to read the user manual, you'd know how to set your PIDs.

Here's a hint for you: Stream menu/Detect PIDs.

[lexor]

Originally Posted by neuron2

If you'd bother to read the user manual, you'd know how to set your PIDs.

Here's a hint for you: Stream menu/Detect PIDs.

Well the only reason I even use DGIndex is because d2v is what mpeg2source likes, I can't be motivated to learn about program I have no wish to use, but am required to. For me it's just another hoop I need to jump through to get my video to avisynth, quite ennoying going file -> open, file -> save project everytime (I mean it has no other purpose on its own), so I try to pretend it doesn't exist.

[neuron2]

If you use the Stream menu, which is very simple, you can eliminate one of the tools that you are using. So it will simplify your process, which you seem keen to do. It will also be faster, since you will make one less pass over the source file.

[laserfan]

I have never used DGindex directly myself, only via AutoGK and maybe some others I don't even know about. But owing to this question (the grey line) I launched DGindex and opened one of my 1920x1080 transport streams, and it is recognized as a 1920x1088 file, and sure enough a grey line appears at the bottom.

neuron2 I wonder why DGindex does this (says it is 1088)? If you know can you suggest--is it something that could be tweaked about DGindex, or should I raise this with len0x re: AutoGK? Seems strange to have to always think for 1920x1080 sources to "leave alone if FILM and crop-off if Interlaced" in AutoGK.

[scharfis_brain]

OMG. if the line bothers you, just use this workaround:

mpegsource("1080i.d2v")
(height==1088) ? crop(0,0,0,-8) : last

[laserfan]

Originally Posted by scharfis_brain

OMG. if the line bothers you...

The line is quite troublesome when viewing 16:9 programs on a 4:3 TV!

[lexor]

@scharfis_brain we already figured that out, no need to quote my own posts to me

@neuron2 Problem is that my capture machine is what you would call legacy (read an array of small FAT32 drives) which means I have to break up .ts on capture into relatively small files (about 500mb) to make my hardware keep up (it chockes if I try to make larger continuous files), and after I fill them up, I just do one batch encode (of multiple movies cupped continuously, I separate them later rather than make breaks at capture time, there is a reason for this too, and it can't be helped), problem being that there seems to be an uppper limit on how many .ts files I can add to DGIndex at once (though I didn't try to find out how many), so I need HDTVtoMPEG2, to make one big .ts on my encode machine anyway, though now that you pointed it out, I no longer covert to .mpg, but single .ts. Still my process can't be simplified by heavier use of DGIndex. So unless someone wants to sponsor my capture machine's upgrades, I'm afraid there isn't much that can be done in the current chain, which is:

hdtvtompeg2 -> many .ts to one .ts -> load in DGIndex -> save project -> mpeg2source in avisynth -> megui

I dunno, but that dgindex step just seems like pointless busy work, just because I can't load .ts directly... well that sounded like a dis of some great software and effort (I think you developed it?) but it really isn't, it's just this separation of tools to make them more modular really backfires in my setup.

[neuron2]

problem being that there seems to be an uppper limit on how many .ts files I can add to DGIndex at once (though I didn't try to find out how many), so I need HDTVtoMPEG2

DGIndex will open up to 512 files. I find it hard to believe you hit that limit. Are you saying that you tried to add all your files and ran into a problem? If so, please tell me about it so I can fix it.

I dunno, but that dgindex step just seems like pointless busy work, just because I can't load .ts directly... well that sounded like a dis of some great software and effort (I think you developed it?) but it really isn't, it's just this separation of tools to make them more modular really backfires in my setup.

MPEG2Source() could not work without the index file created by DGIndex.

[neuron2]

Originally Posted by laserfan

I have never used DGindex directly myself, only via AutoGK and maybe some others I don't even know about. But owing to this question (the grey line) I launched DGindex and opened one of my 1920x1080 transport streams, and it is recognized as a 1920x1088 file, and sure enough a grey line appears at the bottom.

If it is encoded as a 1088 high file in the MPEG2 syntax, then that is what DGIndex will give you. It's not just making stuff up to irritate you. Use Crop().

I wonder why DGindex does this (says it is 1088)?

Because the MPEG2 stream is coded as 1088.

If you know can you suggest--is it something that could be tweaked about DGindex, or should I raise this with len0x re: AutoGK? Seems strange to have to always think for 1920x1080 sources to "leave alone if FILM and crop-off if Interlaced" in AutoGK.

I don't consider it worth modifying DGIndex and DGDecode to support an auto-crop to support this special case when it is so easy to add a crop call to your script.

[laserfan]

Having a bad day, Donald?

The only program I can find that says these are 1088 files is DGindex. So I asked the question.

Sorry you find this irritating!!!

[scharfis_brain]

@lexor: I didn't quote anywhere.

@laserfan: I thought it was for recoding purposes, so always put this line after mpegsource and get happy

[neuron2]

Originally Posted by laserfan

Having a bad day, Donald?

The only program I can find that says these are 1088 files is DGindex. So I asked the question.

Sorry you find this irritating!!!

Please read and follow forum rules, specifically, rule 4: respect the moderator. Thank you.


I made no attack on you, nor am I irritated; I merely stated the facts as I see them. Please follow up with a PM if you want to pursue this; it is off topic for this thread.