TMPGEnc crash when doing VBR

[aamir12345678]

I think it might have been a combination of something else in SP2 & DirectX 9.0c because I had installed 9.0c earlier and it didn't do the trick.

[DRP]

Oh okay, good. Thanks for that. In that case I won't bother upgrading my currently working and reliable W2K SP4 + DirectX 8.1 setup to 9.0c just to see if it works or not

What is it you Americans say? Somethin' like "If it ain't broke, don't fix it"

[jimmalenko]

Oh okay, good. Thanks for that. In that case I won't bother upgrading my currently working and reliable W2K SP4 + DirectX 8.1 setup to 9.0c just to see if it works or not

What is it you Americans say? Somethin' like "If it ain't broke, don't fix it"

If you're happy with your current setup then stick with it.

That said, I resisted the temptation to switch to XP for about 12 months because I had seen it on a mate's computer and initially didn't like the look or feel of it. After closing my eyes and taking the plunge, it is the best decision I ever made. It's more NOOB-Friendly, which at times can be a pain in the ass but most annoying things can be turned off and I believe the benefits it provides far outweigh these annoyances.

Win2K has always been pretty good to me also.

[Bondiablo]

I recently started getting errors after upgrading some hardware. TMPGEnc would quit during the 2nd pass. It turned out to by my RAM settings, even though I could run all kinds of benchmarks and stress tests without error. TMPGEnc must be awfully demanding on RAM, after I relaxed the settings a little in the BIOS, no more errors.

[DRP]

I recently started getting errors after upgrading some hardware. TMPGEnc would quit during the 2nd pass. It turned out to by my RAM settings, even though I could run all kinds of benchmarks and stress tests without error. TMPGEnc must be awfully demanding on RAM, after I relaxed the settings a little in the BIOS, no more errors.

I also started going down this route when I began investigations. It never led me anywhere however and nothing I changed made any difference. Good to hear it worked for you though.

[DRP]

Oh okay, good. Thanks for that. In that case I won't bother upgrading my currently working and reliable W2K SP4 + DirectX 8.1 setup to 9.0c just to see if it works or not

What is it you Americans say? Somethin' like "If it ain't broke, don't fix it"

If you're happy with your current setup then stick with it.

That said, I resisted the temptation to switch to XP for about 12 months because I had seen it on a mate's computer and initially didn't like the look or feel of it. After closing my eyes and taking the plunge, it is the best decision I ever made. It's more NOOB-Friendly, which at times can be a pain in the ass but most annoying things can be turned off and I believe the benefits it provides far outweigh these annoyances.

Win2K has always been pretty good to me also.

I know what you're saying because my brother is always on at me to take the plunge as well ever since he upgraded to XP (from SE). There are other things to consider however like the fact that my still perfectly reliable and serviceable Canon printer doesn't have any XP drivers available for it and the W2K driver only provides "limited functionality" under XP. Other computers in the office are also W2K and this makes for a much easier task of software updating. They also need to be the same OS in order for the a.m. Canon printer to operate as a network printer.

I can't justify having to buy another whole printer just because Canon won't provide a new driver for the old one. Also, I am far from being a n00b user to computers, so all the flowery menu driven bloat that comes with XP is of no use to me. Sure... you can switch it all off, but really, why should I have to?

[jimmalenko]

I know what you're saying because my brother is always on at me to take the plunge as well ever since he upgraded to XP (from SE). There are other things to consider however like the fact that my still perfectly reliable and serviceable Canon printer doesn't have any XP drivers available for it and the W2K driver only provides "limited functionality" under XP. Other computers in the office are also W2K and this makes for a much easier task of software updating. They also need to be the same OS in order for the a.m. Canon printer to operate as a network printer.

I can't justify having to buy another whole printer just because Canon won't provide a new driver for the old one. Also, I am far from being a n00b user to computers, so all the flowery menu driven bloat that comes with XP is of no use to me. Sure... you can switch it all off, but really, why should I have to?

No dramas mate. Different strokes for different folks I guess. I'm guessing you've probably got 2-3 years before Microsoft stop issuing patches for win2K anyway.

EDIT:

Other computers in the office are also W2K and this makes for a much easier task of software updating.

What job do you do that allows you to use your work PC for video encoding ?

[DRP]

No dramas mate. Different strokes for different folks I guess. I'm guessing you've probably got 2-3 years before Microsoft stop issuing patches for win2K anyway.

EDIT:

Other computers in the office are also W2K and this makes for a much easier task of software updating.

What job do you do that allows you to use your work PC for video encoding ?

To be honest the writing is already on the wall for W2K. I have noticed some software already coming out (fortunately nothing that I want to use yet) that only works under XP with specific notation that it doesn't work on W2K.

I am self-employed. I work from a home office and the boss (me) lets me do with my work computer whatever I want whenever I want.

[jimmalenko]

I am self-employed. I work from a home office and the boss (me) lets me do with my work computer whatever I want whenever I want.

Lucky bastard

I managed to talk my boss into getting a DVD burner in my work PC, which I'm only using for Data Backup purposes of course

[aamir12345678]

I can't believe it! It started happening again! When I select 2-Pass (Old Type), it doesn't happen. I formatted the computer and reinstalled everything carefully. I tried it before installing any updates or anything like it. Then, after it didn't work, I updated to SP 2. It still doesn't work. For some reason, the particular registry values, codecs, or other files that SP2 changes seemed to make it work again. I must have modified something to make it stop working, though this does not explain why when I just recently reinstalled SP2, it didn't fix the problem.

It seems that it might be my particular configuration, but I can't see what. This is by far the most frustrating error I have ever had...

[DRP]

Just for my own curiosity, why are you using the old type of 2-pass VBR?

[aamir12345678]

--What I meant to say was that the 2-Pass VBR messes up like this when I select the newer algorithm, the default; but when I use 2-Pass VBR (Old Type), it doesn't mess up. If I ask for 5000, I get 5000; but there's still a problem. The 2-Pass (Old Type) basically does a CBR. It doesn't analyze motion correctly. It'll say - in the [.log] file - that the motion is all pretty much the same; therefore, it produces the correct avg bitrate. Unfortunately, this is what the CBR also produces. It's a waste of time. The 2-Pass (New), according to the [.log] file, analyzes motion correctly, but it'll produce a significantly lower avg bitrate than required for that scene. It'll do this throughout the whole video. You can actually see it at each GOP - in the [.log] file, of course - taking each required value and giving a lower value. It ends up producing a much lower avg bitrate than you ask for. It was just working, but I still have no idea exactly what caused it to start working or stop working again.

--This is the only time you can appreciate error messages from the software because at least they tell you which direction you need to go to get it working again.

Since it might be of some assistance, I'll give a list of the programs I have installed on my PC:

7-Zip
AC3-ACM Decompressor
Audacity
AVICodec
DirectShow Ogg Vorbis Filter
Divx
Download Accelerator Plus
DVD Decryptor
DVDInfoPro
Easy CD Creator 5 Basic
eTrust EZ AntiVirus
ffdshow
FilZip
GSpot
HexWorkshop
HP Precision Scan LTX
InterVideo WinDVD
Jave 2 Runtime Env
MS Broadband Networking
Office XP
Monopoly
MSN Gaming Zone
Opera
PCI Audio Applications
PCI Audio Driver
RAMMedic
Real Alt
Registrar Lite
Subtitle Workshop
The Core Media Player
TMPGEnc
VideoLan
VobSub
SP2
Xvid

[aamir12345678]

--I unchecked all the vfapi plugins of TMPGEnc's except AVI2(OpenDML) File Reader. I left this checked because otherwise it would give an error saying that the file is not supported. I got the same result as when I left the DirectShow Filter or when I increased its priority to the highest. It looks like this problem has nothing to do with DirectShow. Seems it's not even using the DirectShow filter to open or encode the video file...

--I'm going to try uncompressing the Mpeg4 to the big size [.avi] using VirtualDubMod.

[aamir12345678]

I uncompressed the Mpeg4 with VirtualDub & unchecked all vfapi plugins except the TMPGEnc built in AVI2(OpenDML) File Reader and it worked. This is what Pegasys (the TMPGEnc company) told me to do. As far as the actual conflict with the Mpeg4 direct, I still cannot say; but, for now, it works if I uncompress the video.