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 ]
WHEN REINCODEING AVI-MPEG AT VARYING PERCENTAGES IN THE CYCLE WE KEEP GETTING A MESSAGE SAYING
ILLEGAL FLOATING DECIMAL POINT CALCULATING ORDER.
WE ARE RUNNING WINDOWS XP WITH A 800 Mhz CELERON PROCESSOR AND 400 MB RAM.WE HAVE INSTALLED DIVX 3.11/4 AND IT WORKED FOR US TWICE AND NOW WE GET THIS MESSAGE EACH TIME WE TRY TO RECODE.
Mark, I got that same error you got. I tried wat techno said but it didn't work. I did some more research and noticed I got that error at the point where my file was encoded 75%. I tried encoding it several times. Then I looked at my source file and that video frame at 75% was damaged in my source thats y you get that error. I just divided my file in 2 parts skipping that messed up frame and it works. Try it... I don't think those settings which techno and sherlock are telling you to uncheck have anything to do with it.
yes I m talking from my own experience. I think you get that error if you source frame is messed up. In my case it was. May be there are other causes of that error. I came here looking for solution to my problem. I found it on my own. Just trying to help others with wat I got....
I would like to fit a 125min MPEG-1 Movie on a 700mb CD. I've read that if you reduce the bitrate, that will reduce the file size and subsequently degrade the picture quality. Has anyone ever tried this to see what affect is has. As an example , if you decrease the bit rate by 10%, does this shrink the file size by 10%, and create a 10% decrease in picture quality?
if you go to "vcd help.com" there is an article there by some guy who says he can get 120min on a vcd with out changeing the bit rate,and he tell"s you how,but "I DON"T BELIEVE IT" ,but you can check it out and give it a try........
I have download the MPEGS created with this new method of downsizing to fit on one SVCD/VCD disk. Quality is definitely better than VCD but not as good as SVCD but amazing. The template for doing this with TMPGEn has been posted. It's kind of analogous to 1/2 DV vs. full DV but SVCD.
Hello, I see I am not he only one having problems in converting using this program. I have followed all of the directions several times. I still keep getting that my avi are not supported error. How do I fix this?
I've read through your BBS and see a lot of people who get the above mentioned error message.
Isnt it possible for you to make a version which does contain all the nescessary files for this to work.
I do have this problem, and nothing I do will make the progz work. I have reinstalled, uninstalled, added, removed, no codecs, divx versions, patches etc. You name it, I've tried it. Nothing works. I am simply not able to open MPEG2 files.
I know that I make something wrong, because a lot of people have made it work, but I simply cannot make it work.
I completely understand you frustration.
What really frustrates me is I have tested the same mpg file with tmpeg that I have installed at work and it accepts it with no problems.. Windows 2000 or 98 and whats really strange is I have the same software installed and codec at work as I do at home.
What's really odd is I previously had a dual OS which was 98 and 2000 .. tmpeg would open the mpg file in 98 but not in 2000... I only wanted to switch to 2000 because it "stabler"
You getting some sort of kicks from emails or are you afraid to post the link to your filters? Maybe you just get kicks from emails?
This is an Discussion forum where people DISCUSS things and finding better ways to do things. If you dont want to make your work public then DONT POST.
LOL bandwidth!!!! the config files are under 8 KB apiece. Btw. Thats roughly the same size your WWW Frontpage has. ROTFLMAO. Why dont you even snap and paste the essential lines in this forum?
Regarding my IP ... do what you like but stay out of my firewall logs.
Whoops hard to admit it but i might be wrong ... maybe Techno is talking not about his 'famous' encoding filters but is meaning the software needed to get TMPGEnc to work ... well, I doubt it but who knows. Even if its true its still am mysery why he wants email.
Just a good advice: Archive your threads and look at em again in 12 years or so. Recently I've looked up some ancient threads in Usenet and fidonet/znet from me ... no further comment %-)
helo "mr this is sick" I don"t see you giving advice,and with an attitude like that who would want it......ohh ,i allmost forgot "YOU SUCK"....na na nana na...
Thank-you very much Sherlock and Lucy, it is greatly appreciated for your support. Thank-you for helping me. Please feel free to email me or contact me.
I've been trying to get TMPGEnc (Ver. 2.53.35.130) to work, but I just can't figure it out.
Any help would be greatly appr.
I have an AMD Athlon 900mhz PC running Win2K. (400+mb mem) (DirectX installed) etc... DivX, Win Media Player all work fine, but I can't seem to get any video to come up. Could it be my CPU itself ?
I have a number of AVI files (some have formats that can't be read). The one I'm testing does show the the sound stream but I get no video.
I have been making vcds and noticed that if they are encoded with Divx 4.12, TMPGenc won't work right. It has a "fuzzy" quality in the Vcd's sound. While this isn't that bad, it's still a piss off. I mean, why is it doing this? I installed all the codecs I could and installed the 4.12 codec and it STILL happens. The playback of the video in Virtual Dub is choppy, too. I suppose this problem could lie in the Virtual Dub program, instead of TMPGenc. If anyone knows how to fix this, please leave some info.
BTW the VCD's video playback is perfect, I just can't get the nice audio that I'm used to with the 4.12 codec.
I had the same problem, but I dont know if it was because of DivX 4.12. Try to use graphedit and its filters to extract and write down the sound to a wav-file, and then load wav and avi into Tmpegenc as two seperate files. When converting divx to vcd/svcd I allways do this before the mpeg-encoding. Graphedit handels multicannels and other fancy stuff that might cause problems in tmpegenc.
Hello,
i have installed WinDVR, WinDVD, TEMPenc and DivX5.
This constellation would run very perfect, but with some changesyou will get to work with everything (Mpeg1, Mpeg2, Divx)
1. First of all deinstall DivX5. At my machine, TEMPGenc would not work together with DIVX5 and WinDVR.
2. Second install DivX4.12 (The Codec itself is enough, you don¡t need the bundle)
3. Install the ELCARD MPEG2 Codec (Get it at http://www.elcard.com)
4. Install WinDVR, WinDVD etc.¡
5. Install the newest Version of TEMPGenc ;)
6. USE IT!
OK, not the newest or best help, but thats the only way that it willowrk on my computer at home.
Question: did you manage to have sound at all since using TMPGEnc ?
I had the same experience, but this had nothing to do with TMPGEnc.
I used W2000 and simply activated ALL the controls in 'Volume Control' (right-click on speaker in right corner of Taskbar -> 'Open Volume Control'): ALSO Aux & Line In !!! Activate the latter via 'Options' -> 'Properties'.
Hi,
I'm using 2.52 for MPEG-2 VBR coding and I've faced a number of serious issues:
First of CQ_VBR seems to generate the same exact output as CBR, given that they are both set to the same bit rate; no matter how I vary the quality of CQ_VBR. How can this be??
Secondly, how do I get a CBR coded video at nominal 4000kbps with peaksof 4435kbps. It really does not sound that constant...
Thirdly, I'm using JNDmetrix software from www.sarnoff.com for subjective video quality analysis, and no matter what I try, all vbr combinations turn out with worse quality than cbr. To my knowledge, all theory points to the exact opposite. I'm pretty sure JND isn't the problem as I've seen it used by a number of companies in a number of white papers.
these are all problems with the older versions,most of these problems have been solved in the new "2.53.130.plus" version,try it, it is not only better but faster,and has many more options....i have allways had better results with "cbr"
unless I use multiple passes,but for multi pass encodeing I like to use "cinema craft" cuz it can do up to 9 pass encodeing at 10 times the speed,but it costs $2000,so your better off with "tmpgenc" unless you got money to burn....later sherlock
Hi,
I am in fact using 2.53.35.130 plus...and the problems are still there.
Secondly, it doesn't make much sense that cbr achieves better quality than vbr. video is inherently variable bit rate. This means that generally cbr has to contend with an added limitation, namely that of re-enforcing its bit rate limit on a per GOP basis. this means it has to use the same amount of bits for every GOP. VBR on the other hand, generally boast rate control algorithms that allow it to use more bits on fast changing GOP sequences and less bits where the GOP sequence is relatively still, hence achieve a much better quality. this is why I am doubting TMPGenc's VBR coding.
Finally, multi pass is not really an option to me. My final setup would involve real time encoding for transmission over a network. Multi-pass is therefore not an option is such a scenario as the coding delay would be unacceptable.
Victor....the 9 pass encodeing is exelent,and it is better that cbr,but they are 2 different programs"tmpgenc"and cinema craft" but in tmpgenc I haven"t noticed much differance....
That sounds like a load of interesting waffle you just spouted Joseph, but you obviously don't know how to use the bitrate settings in TMPG.
Ofcourse VBR will give better quality than CBR if you set it it right!
There are three settings you must take care of. One is Maximum bitrate, one is Minimum bitrate and the other is Quality.
The quality slider is probably the equation which you are leaving out.
Lets say we want to create a movie with a lot of action. This movie is going to create a lot of high bitrate peaks. So what we need to do is up the maximum bitrate to a point which will create an acceptable looking movie without many macro blocks. Now you cant just up the bitrate and expect TMPG to use this bitrate. What you must do is push up the quality slider. The higher you push the quality slider the more bitrate will be used to encode high bitrate scenes.
If you don't up the slider when you up the bitrate then TMPG won't use the maximum bitrate because you have told it to keep it at a certain quality. For instance you could set the bitrate to 10000kbps, but if the quality slider is set low say 50 the full bitrate will never be used and will be kept at something like a maximum of 5000kps.
The opposite is also true of the slider if you set say a maximum bitrate of 2000kps and up the slider to 100 then this won't give you any better quality than if the slider was at 50, because you have 'capped' the quality by reducing the maximum bitrate ,so the slider will lose any effect after 50.
The same goes for minimum bitrate if you set it too low and set the quality low then when a a particular scene in a movie only needs a low bitrate the bitrate used may be to low for the actual scene, macro blocks will then appear. If this is the case then the minimum bitrate needs to upped to ensure TMPG allows enough bitrate for the scene so the bitrate doesn't go short and macro blocks start to appear.
With CBR the Bitrate is kept at an 'average' constant. I say average because the bitrate isn't absolute it still varies by a few hundred kbps it's just whats called a nominal bitrate.
Using CBR if the movie requires more bitrate and the bitrate is set for a nominal 1150kbps, the result will be capping and the picture will have macroblocks due to the fact that there is not enough bitrate allocated for that scene.
The way to set the Maximum and Minimum is to find two points in the movie. One with low action and detail the other with high action and lots of detail.
Encode a minute of the low action using a particular bitrate minimum of say 300kps and see if this is acceptable quality if it isn't keep encoding with higher minimum bitrates until it looks acceptable.
The same goes with High action. Encode a minute and check the result if everthing looks ok you may be able to reduce the bitrate, if not up the bitrate, but remember upping the bitrate also requires an increase with the quality slider.
This way you will be able to encode a movie that uses acceptable minimum and maximum bitrates.
On a final point the maximum bitrate for MPEG1 is set at a nominal 3500kps, so to achieve this the quality slider needs to be 100. No matter if you set the bitrate to 10000kps, this much bitrate will never be used. This is not the fault of TMPG, but this is set as the MPEG1 standard.
If you want my advice use 'Constant quality (CQ)' as this will give much the same results as a 2 pass encode and better than 'Automatic VBR (CQ VBR)', but works in almost the same way.
Hi Ashy,
Thanks for your detailed reply :) there are a couple of points however maybe I was not clear about. First of all, I was aware of the quality bar...What I did was the following:
1) encoded a sequence of 15 secs with 4mbps cbr.
2) encoded the same sequence with CQ: quality =100, min bitrate = 0, max. = 4Mbps.
In this was, I am applying the same cap as cbr and i'm telling the encoder to throw in the best quality possibly (bar = 100), given the 4mbps limitation. At worst I would therefore expect the same subjective quality as the CBR file. The result however demonstratesthe oppisite, as when I used my subjecte quality analysis program, it reported a worse quality for vbr!!!
Also note that when encoding in this way, the output vbr file was larger in size than the cbr one (the encoder spent more bits). Hence one would expect a better vbr output!!! This is why I'm questioning the vbr implementation of TMPGenc.
Two other questions now:
1) Do you know what CQ_VBR actually is? No matter how I varied this, it have me the same output as CBR...
2) Do you know whether CQ in TMPGenc implements the capping at the GOP level? I know thaqt CBR does so, but don't know about CQ.
Cheers,
Joseph
I don't know if this is the root of everyone's tmpgenc crashes (the common problem with mpeg files), when using windows xp, but I checked to see what was causing the problem and it was a .dll file called mplam6.dll which is part of a Ulead package I had installed.
The file was in C:Program FilesCommon FilesUlead SystemsMpeg on my xp machine and after I renamed it to mplam6.dll_ it no longer causes tempgenc to crach.
I'm not 100% on this Techno may have a better idea, but I think I'm on the right lines.
The operating syetem cache works in a way to speed up file access.
What happens when a program requests a file, is that the operating system reads ahead of that file and 'guesses' what part the program wants next and puts it into memory ready for the program while it finishes what it is doing with the current part of the file.
This speeds up the access to the file rather than having to read it off the disk thus speeding up encoding within TMPG. So don't turn this function off or you will get slower performance.
I don't think its a bad file.
this fault comes on all files with this resolution,
everytime when the result mpg file is approx. 230MB on the HD.
(-> the fault comes always approx. after 65% encoding)
I use already separate audio and video files
(My normal way:
- PVACut
- PVAStrumento to demuxe audio and video
- DVD2AVI to make project file
- TMPGEnc
)
By the way, I can't use TMPGEnc to encode files with
the resolution 720x576 in W2K, the program terminates after a few
minutes completely without any error message.
Other user told this too, what could be the reason for this?
Any solution?
This looks like it's an area of memory that TMPG is trying to write to which can't be accessed and is already being used by something else.
Have you been playing with your BIOS by any chance. Try turning off any shadowing in your BIOS. i.e BIOS shadowing or Video card shadowing as these use certain parts of memory.
If anything tries to write to this address in memory you will get the 'Write address' error. Also shut down any programs running in the background such as memory managers or task schedulers as these may be hogging memory.
When given an .m2v file extracted from a directivo (see www.dealdatabase.com direct tivo extraction discussion for tools and data) format is 480x480 mpeg 2 progressive vbr. Tmpgenc only sees 1/4 of the true number of frames. For example: In a one hour clip with 100,000 frames (approx) it will report the length as 25000 frames and length as 15 mons. In a encoding pass, only 25000 frames will be processed. If the preview is used, you can see the entire file (1 hour worth) but again it reports the last frame as 25000 not 100000 and ending time as 15 mins not 0 mins even hough the pictures seen in the preview at the end of the clip are the correct end of the 1 hour clip.
If audio is multiplex'd in before transcoding usinf mpeg tools, simple mux, tmpgenc correctly sees the true frame count and time in the mux'd file.
Hi,
I've come across this too just this morning. I'm using sequences .m2v available at ftp://ftp.tektronix.com/tv/test/streams/Element/MPEG-Video/625/. the sequences are 375 frames in size. When encoded to cbr 4Mbps (i used the 40Mbps ones as a source from tektronix) the frame size was reduced to 350..., basically chopping off the last second of the sequence.
Joseph