VDub frameserving to TMPGNec problems...

[mjack]

Hi, I'm having a problem frameserving from VDub to TMP...if ya didn't catch that in the subject.
Here's the problem...
1. I load a captured .avi file into VDub
2. load the filters and start the server
3. I then open TMP and load the *.vdr file I created
4. ...and then it comes back telling me that "the file is unsupported"

Any suggestions would be helpful...I've tried all I can think of including the proxy...don't know much about it though...

Thank You

[xxBladExx]

Try to install the divx codecs first.

- 3.11 alpha and 4

See tool section

[Craig Tucker]

When you save the vdr file give it an avi extension. eg frameserver.avi

Craig

[mjack]

Thank you for the suggestions but neither of them will work. I d/led both codecs for VDub and tried adding the .avi extension when frameserving but neither worked. Any other suggestions? I've tried everything I can think of...

Another question: What is the best sound compression to use for both compression and retaining sound quality?



Jack

[ViperXT]

You should always capture with .wav audio at 16/44.1. When compressing the file however mpeg layer 2 at 160 or up retains good compression and quality.

[liquid217]

i think you need to dl the tmpgenc vfapi project file...

http://www.tmpgenc.net/files/TMPGEnc-2.56.39.143-Free-VFP.zip

[mjack]

Liquid,

I installed that file and it still won't work. Then I tried to skip frameserving and uncompress the file, filter it, and then compress the .avi with VDub into a DivX 4.12 at 3500 kb/s keeping the audio on direct stream. My computer came back with an illegal operation for Vdub when I tried to start processing the AVI. All I want to do is apply these filters and compress the avi again without compromising too much quality. Thing is I don't have enough room on my hard drive to completely uncompress the file. If you have any more suggestions for frameserving to TMP or the deal with the illegal opperation...they would be appreciated

Jack

[liquid217]

try increasing the directshow plugin in tmpgenc.

in tmpgenc, goto options...environmental...vfapi

make it +1

[ewokthecat]

I have had the exact same problem, and after systematically eliminating the various factors, I have discovered the problem to be related to VirtualDub 1.4.10. By downgrading to 1.4.7, there was no problem with TMPGEnc accepting the file.

Looking at the development logs of VirtualDub, It appears that 1.4.10 was compiled with a new version of Visual C++, which utilised Microsoft .NET technology. I postulate that unless the version of Windows you are using has the .NET framework, VirtualDub 1.4.10 will not work in the same way as previous versions. I have not yet tested versions 1.4.8 and 1.4.9 to see if they also work, and I am waiting to do this prior to informing the VirtualDub author of the problem.

I am using Windows ME (fresh install), with current critical updates installed, but without the .NET framework added.

In the meantime, downgrade to VirtualDub 1.4.7 and try frameserving again (it works for me with just AVIFile handler installed - no need to use avi proxy.)

I hope this helps.

Cheers,


Ewok 8)

[aguillon]

I had the very same problem recently. Even though I could frameserve perfectly for a long time, suddenly nothing seemed to work.

I found a fix on the net: delete the config files of TMPGEnc (One is called currentCfg.tpr, the other TMPGEnc.ini) Then re-install the VDub frameserver by using AuxSetup in the Vdub directory

Restart TMPG - You lose your settings (ie which template loads, etc) but guess what.. Frameserving works again.

Worked for me, you may want to try it out.

[aguillon]

And by t he way, I frameserve from 1.4.10 to TMPGEnc 2.56 - no problem. I d hold back on reporting so-called incompatibilities...

[mjack]

That is the only thing that I have found to work...I d/led all the patches..all the drivers...tweaked the priorities...and d/ling an older version is the ONLY thing that has worked! I suggest to anyone having problems frameserving to TMP from VDub to d/l AuxSetup from 1.4.9. It is the only thing that will work 100% of the time. I appreciate all the replies...

[ewokthecat]

aguillon & mjack:

Do you use a .NET enabled version of Microsoft Windows?
What version do you use?

I'm interested in feedback from others with the same problem, to try and determine the cause - obviously some people have no problems, but _what_ is it about their configuation that is different?

Cheers,

Ewok
8)