Macroblocks are last fence.

[baker]

I made a vcd and noticied that while I tought the resouloution was good macroblocks where my only problem.Does anyone have a filter that will help get rid of them?

p.s. I use tmpegenc and want to keep using it.

Baker

[shochan]

What is your source video. That makes a big differance if it is divix or grainy it will produce alot of macro blocks. any encoder will. and if you use to much noise reduction they all start looking fake. if your source is dvd then you might have your motion search turned to low.

[baker]

I am frameserving for dvdx and encoding in the newest version of tmpegenc at the highest quailty.Macroblocks only really shows when theres fire or something.

Baker

[baker]

COME ON I NEED HELP!!(in more ways than this!!!)

Baker

[bbb]

If you blur and darken your video, it will eliminate some blocks.

But, then it will be blurry and dark.

I don't know how to use dvdx filters so you might want to use dvd2avi, VDub, and Tmpgenc to blur and darken you videos and see if it's better than blocks.

You can also try inverse telecine to convert it to 23.97 or 24 fps. It seems to reduce blocks in fire.

[Truman]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-11-24 14:22:00, baker wrote:
I am frameserving for dvdx and encoding in the newest version of tmpegenc at the highest quailty.Macroblocks only really shows when theres fire or something.

Baker
</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>
Some more details would be nice. Resolution, bitrate, source, actual framesize (without borders), VCD, SVCD?

[vhelp]

baker,

can you provider the link where you got the divx file from?
...for this file, or ANY files one downloads.

Also, please enclude your setps/methods/settings in tmpgenc
that you use in your process.

[baker]

Who said n e thing about a DivX!!!!

[Truman]

<TABLE BORDER=0 ALIGN=CENTER WIDTH=85%><TR><TD><font size=-1>Quote:</font><HR size=1 color=black></TD></TR><TR><TD><FONT SIZE=-1><BLOCKQUOTE>
On 2001-11-24 16:18:02, baker wrote:
Who said n e thing about a DivX!!!!

</BLOCKQUOTE></FONT></TD></TR><TR><TD><HR size=1 color=black></TD></TR></TABLE>
I am very glad, that you solved the problem.

[baker]

truman, what da f*** are u on about? I am converting a dvd to vcd using dvdx and tmegenc and want less blocks,can you help me?

Baker.

[ngnr]

baker, there's an old saying, "you can catch more flies with honey then you can with vinegar". I doubt you will get much help with the tone of your last post.

[baker]

Plz does anyone have any filters for tmpegenc or dvdx to get rid of these annoying macroblocks!!!????

Baker

[baker]

Come on, please!!

[pinoy2201]

then simple dont frameserve with TMPGEnc if you frameserver the quality is not going to become greater..i sugest you use a plugin with DVDx like CCE or LSX ..unfortunaly Panasonic doesnt work if your encodeing NTSC..if you want to use Panasonic use FlaskMpeg to convert your video okay and you can use the other plugins with Flask too

[baker]

I tought I would achive the highest quailty when framserving as I don't have to save to divx or something and also I tought tmepgenc was the best encoder around.

A confused,
Baker

[shochan]

Doing a vcd, a just plain old vcd you will get macroblocks occasionaly, in high motion jumpy scene.... like fire.

Make a svcd if your that upset about a few macroblocks in some dancing fire.

raise your bitrate on your vcd.

turn off "No motion search for still picture part by half pixel"

change the 5 in your gop structure to a 4.

do a higher motion search if you arnt already maxed out.

do a search to find out which tmpge is the best for mpeg 1 encoding.

use dvd2avi and make a project file. get the vfapi converter and convert it to a frameservable avi (just names it avi so it can be opened by other things) use virtual dub to apply filters like the smoother and frame serve from there into cce or tmpgenc, then encode it.

tmpgenc is the best freeware encoder. I am starting to shift to cce as I feel the quality is better in multipass vbr encoding.

[baker]

I know how to change the gop structure in tmpgenc and I am going to try that now, but what is gop structure?

Baker

[shochan]

THe gop structure is how many of each of the following frames follow each other. (i.e. IBBPBBIBBPBB) well something like that
I found this at berkley it might help a little more.

Frame Encoding.

Frames are divided into 16x16 pixel macroblocks. Each macroblock consists of four 8x8 luminance blocks and two 8x8 chrominance blocks(1 U and 1 V). Macroblocks are the units for motion-compensated compression. Blocks are used for DCT compression.

Frames can be encoded in three types: intra-frames (I-frames), forward predicted frames (P-frames), and bi-directional predicted frames (B-frames).

An I-frame is encoded as a single image, with no reference to any past or future frames. The encoding scheme used is similar to JPEG compression. Each 8x8 block is encoded independently with one exception explained below. The block is first transformed from the spatial domain into a frequency domain using the DCT (Discrete Cosine Transform), which separates the signal into independent frequency bands. Most frequency information is in the upper left corner of the resulting 8x8 block. After this, the data is quantized. Quantization can be thought of as ignoring lower-order bits (though this process is slightly more complicated). Quantization is the only lossy part of the whole compression process other than subsampling. The resulting data is then run-length encoded in a zig-zag ordering to optimize compression. This zig-zag ordering produces longer runs of 0's by taking advantage of the fact that there should be little high-frequency information (more 0's as one zig-zags from the upper left corner towards the lower right corner of the 8x8 block). The afore-mentioned exception to independence is that the coefficient in the upper left corner of the block, called the DC coefficient, is encoded relative to the DC coefficient of the previous block (DCPM coding).

A P-frame is encoded relative to the past reference frame. A reference frame is a P- or I-frame. The past reference frame is the closest preceding reference frame. Each macroblock in a P-frame can be encoded either as an I-macroblock or as a P-macroblock. An I-macroblock is encoded just like a macroblock in an I-frame. A P-macroblock is encoded as a 16x16 area of the past reference frame, plus an error term. To specify the 16x16 area of the reference frame, a motion vector is included. A motion vector (0, 0) means that the 16x16 area is in the same position as the macroblock we are encoding. Other motion vectors are relative to that position. Motion vectors may include half-pixel values, in which case pixels are averaged. The error term is encoded using the DCT, quantization, and run-length encoding. A macroblock may also be skipped which is equivalent to a (0, 0) vector and an all-zero error term. The search for good motion vector (the one that gives small error term and good compression) is the heart of any MPEG-1 video encoder and it is the primary reason why encoders are slow.

A B-frame is encoded relative to the past reference frame, the future reference frame, or both frames. The future reference frame is the closest following reference frame (I or P). The encoding for B-frames is similar to P-frames, except that motion vectors may refer to areas in the future reference frames. For macroblocks that use both past and future reference frames, the two 16x16 areas are averaged.