frameserveing to mainconcept

[sandman112]

im currently using virtualdum as a frameserver to TMPGenc but i would like to use Mainconcept as my encoder but i cant get it to read from the frameserver

anyone know how i can make this work

cheers

[BJ_M]

load the vdr file into MC , assuming you've installed the VD frame server correctly , it works .

[sandman112]

all i get in the preview is a green screen ???

[mats.hogberg]

Actually, so do I, since my latest reinstall. Frame serving from AviSynth works tho...
It encodes the correct amount of frames and all, but all is a green screen.

/Mats

[BJ_M]

try turning off one of the avi handlers in main concept options

[rgs_uk]

I have had this a couple of times and uninstalling the XVid codec always solves the green screen problem.

[mats.hogberg]

?? ...and what if the original is an XviD AVI?

/Mats

[sandman112]

k i think ive solved this one, at least it worked last night, i reinstalled the xvid codecs, start the frameserver thing as normal, then open teh VDR file using VFAPI codec thing, click convert and it will create and AVI file that you can then feed into mainconcept.

it worked for me last night

[BJ_M]

well you should be able to open the vdr file also (which is faster than using vfapi) , try renaming the vdr to avi and see if that helps ..

did you try turning the v-dub proxy on or off ?

[sandman112]

well you should be able to open the vdr file also (which is faster than using vfapi) , try renaming the vdr to avi and see if that helps ..

did you try turning the v-dub proxy on or off ?

i just tried going straight from V-Dub to mainconcept and its back to the green screen, but its ok if i use VFAPI ......

didnt find the proxy thing, could you tell me where that setting is ?

[BJ_M]

in the v-dub directory

/aviproxy

The AVIFile handler included with VirtualDub 1.3b is capable
of running in Proxy mode -- that is, you can install it as the
*default* handler for AVI files, and it will work with signposts
that are renamed to the AVI extension. This means that
applications which previously failed with the AVIFile handler
because of the .VDR extension can now be used, provided that
the .VDR files are renamed to the .AVI extension.

This support is very experimental, so try at your own risk.

To try the AVIFile proxy support, first use auxsetup.exe to
install AVIFile frameserver support, then use the REGEDIT tool
to install the proxyon.reg file. Use the proxyoff.reg file
to disable it.

The proxy support will be invisible to most programs, but some
programs do not like the proxy handler and will no longer work
if it is installed; you will have to disable the proxy for
these programs.

[BJ_M]

you also of course have the auxsetup.exe in your v-dub directory to setup the handler

[lchiu7]

A bit late to this thread but I just encountered the green screen with Virtualdub frameserving to MCE. And this is a newly installed machine. Turned out to be (for me anyway) the installation of the XVID codec. Removed that it was fine. Don't really need the XVID codec at all since I don't encode on this machine (it's my PVR) and I can use FFDShow to decode XVID files that I have

Larry

[mats.hogberg]

Hm... -I'll try that, since I've yet to find a solution for this. VDub frame serving might still come handy when I'm too lazy for writing a AviSynth script...

/Mats

[lchiu7]

Avisynth looked too hard for me and pretty cumbersome when you want to edit out commercials in a recorded show. I had seen someplace that people had done the following to get rid of the green screen

1. Edit in Virtualdub
2. Frameserve to Avisynth
3. Send the avs file to MCE

Looked like a pain to me

Interestingly no problems in framserving to tmpgenc but that program is really slow compared to MCE (no comments about quality)

Larry

[SatStorm]

In case you have xvid installed at your system, unistall it! There are plenty reports that this happens because of the xvid codec. Not the codec actually, but a conflict it has with M$ or something...
Try it, it won't harm!

[lchiu7]

Yes that is what I did and it fixed the problem. As noted didn't need it to decode xvid files since ffdshow can do that and I don't encode xvid video myself

Larry