O.k., then I'm almost sure AviSynth doesn't work correctly (or doesn't work at all) on your system.

When I run unmount, the cmd.exe window says "Could not find C:\frameserver\source\vegas.avi

I am at a loss to understand why V2H is not working on my same system(except for a change of video card brand) when it worked perfectly before..my oh my..

Marco your help has been very much appreciated.

"Could not find C:\frameserver\source\vegas.avi"

After running unmount this message actually should appear. It just tells you FrameServer was correctly terminated again.

I'd focus on a new, clean install of AviSynth (after having uninstalled current AviSynth installation).

I have done about 5 or 6 uninstall and reinstall of the all the V2H software today except Handbrake.. so..

Marco, thank you!! You and the others are putting in some serious time just to help a few . . . we appreciate it. I will try all your suggestions above later today. Off to Church and to take the Mrs. out to dinner . . .

HAPPY MOTHERS DAY!!

Skywatcher

I see there are two cases which could throw a mount failure message.

- One is AviSynth is not working (correctly).

- The other one is the file mount systems failed to register the AVS file.

Both cases causes same error message.

So I'd suggest downloading VirtualDub 1.10.4 (32 bit version). Once the zip file is downloaded, unzip and run "VirtualDub.exe".

When the VirtualDub GUI is opened, from the "test" folder (which I linked for download above) drag the file "video.avs" and drop onto the VirtualDub GUI.

Does VirtualDub display a test pattern now?

.

If anyone is having trouble with AviSynth using the old Avisynth_258.exe installer, you could try a later version. AviSynth 2.6 is now up to RC3 status and has a mountain of additions/fixes/optimisations over 2.58. SEt's MT builds have always been robust and stable for me, and someone wrote an installer for his latest one which is based on AviSynth 2.6_RC1, so you don't have to manually swap out avisynth.dll.

So you could try one of those.

Hello Marco, sorry for the delay in getting back to post due to time difference. Have done what you asked and the answer is "YES" VirtualDub shows the test pattern..

Thanks for your input Nick.
I cannot find the actual download link for AviSynth 2.6 as there are so many links that take me all over the place and back again. When I eventually find 2.6 is it as simple as just installing version 258?

Lee

Ahh, o.k. Then AviSynth itself is working fine. And then it looks like the file mount systems fails to register the AVS file. Need some time to think about it.

I look forward to your thoughts Marco . Don't rush as I am off to bed now (here in Australia) got an early start tomorrow.

Lee

I wonder wether it's maybe a timing problem again. You could try this:

In the folder "test" which I linked two days ago open the file "test.bat" within a text editor.
The second line in "test.bat" is:

"timeout /t 2 /nobreak"

Change this line into:

"timeout /t 10 /nobreak"

Save the file again and then double-click. Be patient. The whole process will last about 10 seconds now.

Same error message?

"I cannot find the actual download link for AviSynth 2.6 as there are so many links that take me all over the place and back again. When I eventually find 2.6 is it as simple as just installing version 258?"

Standard AviSynth 2.6_RC3 is here (the file is called AviSynth_150419.exe). Like I said, there's been a lot of development since that old 2.58 version. But if 2.58 is working for you, as Marco says, you might still choose to leave it alone.

For AviSynth MT 2.6_RC1 (a version which allows multi-threading features in an AviSynth script), you can either download and unpack this dll and manually swap it for the standard avisynth.dll that you installed previously, or you can try that installer that I linked to in my previous post. It does open an ad page when you download it, and I haven't tested it.

I'm guessing that the MT features aren't really relevant for VegastoHandBrake, but they're important if you plan to do any other intensive work with AviSynth.

Note that most of the AviSynth 2.6 installation is still in a folder called "AviSynth 2.5" until it's fully released.

"O.k. – here's the test package.

Marco, I did this test and I believed it worked (i think) . . . however, when the cmd prmpt window opened, it closed with no error. The "video.avs" didn't create its own folder. It stayed in the test folder.

Also, after checking the test.bat in VirDub, I got the color bars test pattern.

Now i'm about to try AviSynth 2.6 . . .

Skywatcher

I tried "AviSynth 2.6_RC3" and still nothing. Frameserver (or Vegas) won't open handbrake. I'm passing all the tests. I feel this is something really simple like . . . some really obscure program or script running in the background.

If I start my rig in "safemode" and try it . . . think that's worth a whirl? Is that even possible? (just throwing mud at the wall . . . I ran out of errr . . . )!!

Skywatcher

Hi Marco, have changed the "test.bat" as instructed to "timeout /t 10 /nobreak" Still have the same "Mount Failure " window pop up after 10 seconds...

Here I'm lost. I did a web search up and down to find out what exactly could prevent the file mount system from registering a file but I didn't find any info about it.

Maybe Nick's note trying to use AviSynth 2.6.0 would help – if this does mean you wouldn't need to register the AVS file via a batch command. But on the other side this maybe would need to rewrite other parts of the Vegas2HandBrake workflow but I won't have the time to do that.

No more idea, sorry.

See other post. Problem seems to be for an unknown reason the file mount system fails to register the AVS file. Without having registered the AVS file, Pismo can't mount the file and HandBrake won't find the file needed.

No glue from here. Didn't find any information about a register failure of the file mount system.

This is really baffling, so here goes another shot in the dark. When you "uninstall", do you use the Win7 uninstall from the control panel? If so, suggest you try something like Revo Uninstaller (they have a free version), which starts with the built-in uninstall and then searches for leftover entries in the registry as well as file folders. I find it surprising how many things are simply "left over" from a normal Windows uninstall. Just another WAG.

wwaag

I see latest Pismo File Mount Audit Package is build 1.77. But Vegas2HandBrake workflow is based on build 1.70. Maybe something changed in the later builds which would need another kind of file registration.

So please check your Pismo File Mount Audit Package build number. If it is not build 1.70, download pfmap-170-win.exe from the PFM archive, install (after having uninstalled the current installation) and test again.

@Marco. Your time and thought into this issue has been very much appreciated, thank you. It has been frustrating for all of us not to nail this issue. Regarding PFMAP, I have tried versions174 ( this was the version that had V2H working for me before the fresh install) 175 and 171 so will give 170 a whirl.
@wwaag I also thank you for your help too..Regarding uninstalling I have been using Ashampoo uninstall 4 for a few years and this uninstalls all traces of previously installed software. However I will still give Revo a whirl too ...As said before I will keep on trying but you know what for some reason in the back of my head I think PFMAP has a part in this issue

Lee

"Downunder, Grazie, WWAAG, Risce1, John Dennis, VidMus, Marco, Old Smoke and Nick Hope:

Thank you all for your input and diligence. Not just this post but ALL of your insight which directly led to this latest rig I built a few months ago. I will continue to monitor the forum until a fix for our issue can be found.

THANK YOU, Thank You . . . thank you;

Skywatcher