This forum is for users to exchange information and discuss with other users about a TMPGEnc product.
In case you need official support, please contact TMPG Inc.
Pegasys Products BBS [ Sorted by thread creation date ]
Im usually use the Sharpen filter when i encode Mpg1 with the 352*288 Resolution
in the Sharpen Filter option there is a option to enable field base .When i use that option the Video gets even more sharp it seems...but are that option only intended to be used with mpg2 interlaced videos..how about Mpg1 352x288 ?
is it normal to use the field base option in mpg1 too ?
anyone ever use Field base option when using sharpen filter in tnmpgenc ?
I use the Clip > Arrange > Center (custom) to plop a 640x272 avi (no black bars in source) onto a 480x480 frame. I enter the parameters to get what I want visually and naturally any area of the frame not covered by my avi show as black.
Now the question...
Does TMPGE encode the top and bottom black into the compressed video stream? Or does it only encode the active area and simply "tell" the player to blank-out the unused portions of the frame?
This is important (IMHO) because although a solid black field will compress to almost nothing, the transition from that black field to the active video will (I believe) take up valuable bandwidth.
Too bad you can't just encode the active video and let the player place it on the requested frame size on-the-fly. Kind of how a player reformats an anamorpic 16:9 for a 4:3 monitor. Actually, it would be an easier process for the player because it would not have to scale the video. Only add the blanking. Oh well...
So if TMPG encodes the voids as part of the stream anyway, what are the pros/con between letting TMPG add the black verses giving it a aspect ratio corrected, full frame source which includes the black void (ie frameserving it from avisynth all ready to encode)?
I don"t think that it really makes a Differance But it would Be interesting to do a Test to see what encoded faster and which used the given bitrate more efficiently?...
If you're working on a 16:9 source, you may wish to make an anamorphic video.
Some TVs/DVD players are capable of taking a 4:3 image and scaling it down to 16:9 adding their own black bars. My TV is capable of doing this, and it increases the pixel density while doing it resulting in a sharper output image.
>If you're working on a 16:9 source, you may wish to make an anamorphic video.
>
>Some TVs/DVD players are capable of taking a 4:3 image and scaling it down to 16:9 adding their own black bars. My TV is capable of doing this, and it increases the pixel density while doing it resulting in a sharper output image.
I had hoped that it was possible to only encoding the active playfield instead of the playfield + voids (albeit that the voids take up very little room). Making an anamorphic means the video has to be scaled vertically then reduced during playback. Thats 2 conversions away from the original source material, not to mention the larger file size and added encode time. A high price to pay for not putting the voids in the source from the get go.
The DVD video standard has 2 aspect ratios, 4:3 and 16:9. Black bars are NOT encoded except for very thin ones when 1.85:1 movies are encoded at 16:9 (1.78:1).
A DVD element (menu, video title, etc) with the 16:9 setting is assumed to be anamorphic and the player will squeeze the picture and add black bars (when instructed that the TV is 4:3). The squeeze is pretty sophisticated. Four lines are averaged together to get three.
This method allows 16:9 displays to retain full resolution.
When DVD authoring software sees mpeg input files with 16:9 flags in the header(s) it groups them together in a video title set that will have a 16:9 flag. Mpeg files that are not 4:3 or 16:9 will not be accepted by authoring software. Most consumer software does not accept 16:9.
IFOEdit can be used to change the aspect ratio setting for "video title sets" after a DVD has been authored. This allows you to supply anamorphic material encoded at 4:3 to consumer authoring software and fix the DVD database before burning.
What you say is correct. However, in my original post, the source material is 640 x 272. This translates to SVCD size of either 480 x 272 or 464 x 272 depending on how anal you want to be about pixel aspect ratios. I did not know if the MPEG-2 spec allowed the stream to be something less then 480 x 480 (or 720 x 480 for DVD) and simply place in the header information to the player that the video needs to be padded-out on the fly. If that were possible then 100% of the bitrate bandwidth could be for the active video.
To "take advantage" of amamorphic abilities of the player to vertically squeeze & pad-out with black would require that additional vertical detail be conjured up (ie vert scaling). That would increase the source material from 272 vertical to 400ish. Then the player takes that 400ish back down to 272 and plops it onto the output frame. Neither of these 2 conversions are lossless and the new vertically scaled source material is larger and would result in a larger encode.
I am trying to convert an avi to mpg but all I get is a blank, black screen (audio is OK). I have read others with the same type of problem and they've been recommended to increase the priority of the DirectShow plugin. When I do this however the whole program crashes! Any ideas? This avi is the second of two and the first one was fine.
Thanks
I doun understand why tmpg is going wrong. it is my first time using this software. I tried to convert avi to dvd file(mpg). And there was a error pop out ( scan line is out of range error:404).
P.S Plaze help!!!!
Can someone tell me why the exact same version of TMPEG can decoded AC3 on one computer and not on another? The only difference between the versions is that one is registered and the other if the free version. The free version is the one that works but they are the exact same version otherwise.
I have encoded hundreds of VCD's from avi files with this program before, but now lately, the program seems to be doing something very strange. I have a 349mb 44:00 video file, but when I try to convert it to VCD TMPGEnc says that the file is 142:00 minutes long and the program informs me that this is obviously going to be too large to fit on a CD.
Interestingly enough, I have a 140mb video file of the same length and it encodes perfectly...but I have been downloading more and more of these higher quality avi's and seem to keep running into this problem.
This file that is giving me problems is 512x384 24bit @ 23fps, and windows tells me the video compression is DIVXMPG4 V3. The audio is MP3 at 109kbs.
Any help you folks could give me would be much appreciated.
Well, guys, it looks like I fixed the problem...sort of....if I use the source range option and I set the end point just a few frames away from the very end of the file, suddenly TMPGEnc suddenly decides that I have a 44 minute video file instead of a 142 minute video file...is this a bug in the program of just something crazy going on with my crappy computer?
The Thing with Downloaded files is that they Get corrupted from being downloaded repeatedly so there are probably corrupted Frames or the header is corrupted and that is why it is giveing you this and other problems ,Downloaded movies aren"t the Best way to make High Quality VCD"s and Svcd"s out of..It is Best to Rip them yourself...
Hello, I'm having loads of trouble while trying to encode MPEG-2 with. I get loads of DLL errors, what i get is 'Write error occured at address 77F546F7 of module "ntdll.dll" with 00000000' and then run time error 216, please please please can someone help me ?
I'm using version 2.59 on a P3 700 running XP Professional.
Same problem here, narrowed it to XVID codec. Have WinXP with SP1, WinMediaPplayer9, tmpgenc .59. Can easily create from div3, xvid crashes... any help?
Yes the file i trying to encode is an XviD too :( Sometimes, very vgery rarely will it work fine, as i have done a few XviD encoding on .59, but none for a while because of this problem. I trying using ME, and 3 other computer with no joy :(
I used TMPGEnc very often without problems but not I can't encode AVI files into mpeg anymore. Everytime I try to do it and i click to start the process a window opens saying that the file can't be opened or supported....It's quite strange because these files are normal DivX....can anyone give me a help please?
hi i`m having problems with aiv and tryin to put it in mpeg and its sayin
cannot be opened or unsupported" i can watch it in windows media and its a avi file .but just wont let me put it into mpeg ..i hope anyone can help me and know what i`m on about ..do i need any over progs to do it
thank you all byr julie
hey there,
I try to frame serve an AVI with VirDub using the Avery Lee subtitle plugin. When I start TMPG it says: error: divide by 0 !
What goes wrong?
Make sure that the vdr file is a Good files, Meaning that the Frameserver is working properly, you can do this By opening up another instance of Virtual Dub and loading the Vdr file in and see if you can see the image..
If the .vdr will load back into Virtualdub this means the frame server is working ok.
The problem must be TMPG. Try disabling the the 'directshow reader' filter in the VFAPI plugins and then raising the priority of the 'VFW reader' filter.
I can't seem to convert Windows Media Files anymore. I have Windows Media Player 8 and the Divx 5.0.2 Codec installed, so I'm a little stumped. Anybody able to give me some pointers, cause I know I'm missing something!
Try Raiseing the Priority of the "Direct Show File Reader" in the "Vfapi Plugins" and if that don"t work It could be cuz the File is corrupted Cuz WMV Files are easily corrupted Cuz they are so highly compressed So use ASF Tools to repair it and that Might help But if you are totally stumped you can try converting the WMV to AVI then encode it to Mpeg...
I was getting a nasty read error pretty consistantly with many files on XP with my Asus A7V266 motherboard system. Even after re-installing XP and Win2K, tmpgenc would get about 1/3 through the file via frame serving with Avisynth from Premier and then error out. Disabling Norton gave a slight improvement. But what finally made it stable was upgrading the BIOs to version 1011.
Email me for details.
rdt