VegastoHandBrake installation

Skywatcher wrote on 5/6/2015, 11:45 PM

Thanks Wwaag . . . . i changed it to RGB24. added 1 second of looped time at the end. Lets wait and see if Downunder has any success. I loaded frameserver on the "C" drive. Some suggested it be loaded in the Vegas Program file . . . . I actually tried both.

I'm using HB 9.9.1. Let me update to the latest version and see if that makes a difference . . .

Skywatcher

Downunder wrote on 5/7/2015, 5:19 AM

I am very sad to report that nothing has V2H working. Have tried all and everything you guys have suggested including using the 2 replacement scripts VidMus (and WILEMT) suggested as a fix, have the 1 second at the end etc etc. 2 fresh OS/Vegas installs first one was with Vegas build 428 and second with Vegas build 444. I originally installed V2H software with Vegas build 373 (V2H worked perfectly) and even when installed Vegas 428 over 373 V2H was working perfectly too. I just might have to reinstall 373 (when I have time) to see if that works.... Skywatcher JFYI I have the exact same Windows//cmd.exe hang window as yours when using VidMus replacement scripts.Tried both handbrake 9.6 and 10.1 too. Have even tried to PM Marco (via this forum) to see if he can shed some light on the issue but his email address bounced back...

Marco. wrote on 5/7/2015, 6:59 AM

Actually I don't know what's going on there. You might try to pause or disable your virus scanner if active.

john_dennis wrote on 5/7/2015, 12:58 PM

When this process was first released, I successfully installed it on one of my machines the first time. On Tuesday, I attempted to install it on another machine and failed miserably. After restoring a virgin image a couple times and failing a couple times, I was successful when I used the files from a folder on the first machine. I usually keep copies of useful items because things change on the Internet.

I've put the files on my dropbox in case someone else would care to try a "known good" set. Maybe it was one of the files, maybe it was just me doing a better job on the third try.

Let me know. I don't really want to host files if they are really the same as can be downloaded somewhere else.

Link removed. Not a fix.

Downunder wrote on 5/7/2015, 4:18 PM

Hi Marco, I have no 3rd party anti virus software on my video computer. By reading both mine and Skywatcher's screen shots does that help you to understand the issue?

Downunder wrote on 5/7/2015, 4:21 PM

Thanks John I will give them a whirl.

Marco. wrote on 5/8/2015, 6:39 AM

I can see the problem but unfortunately I have no idea what the cause is, sorry.

Downunder wrote on 5/8/2015, 7:18 AM

OK Marco. I will keep trying different scenarios and hopefully one will eventually work. In your opinion would a video driver be in anyway connected to the issues with V2H like I am having?

Marco. wrote on 5/8/2015, 8:41 AM

If frameserving works fine and if HandBrake used stand-alone works fine, I don't think a video or grafic driver could have any more influence.

wwaag wrote on 5/8/2015, 9:56 AM

Since everyone seems to be in the dark, I'll try another shot. Have you installed avisynth? The nice thing about using Virtualdub is that you can ensure that both frameserving and avisynth are working properly.

wwaag

Skywatcher wrote on 5/8/2015, 9:33 PM

Yes. I have installed avisynth. In the correct order per the V2HB website (page). I couldn't help but to notice that downunder is using a GTX570 card and I have two GTX580 cards . . . could this be the issue??

Skywatcher

OldSmoke wrote on 5/8/2015, 9:50 PM

I had 2 GTX580 and now 2 R9 290 and Indidnt have that problem with either setup.

Skywatcher wrote on 5/8/2015, 9:59 PM

Then I'm at a loss . . .

Skywatcher

Downunder wrote on 5/9/2015, 2:13 AM

Ok I have "some" movement here not good movement but a change... Installed the John_Dennis files and now I get this error message which I have not seen before:

https://www.dropbox.com/s/iemlaoetoqgea7s/Vegas2Handbrake%20error%20image%202.jpg?dl=0

All files are installed in the correct place(s) ie copied frameserver folder to C:\. this folder has:
AVFS
batch
source
avfs.dll
vegas

Any ideas on this error?

Skywatcher JFYI the reason I did a fresh re-install of OS/Vegas was to install a Radeon 6970 video card to try out ...as they say "if it ain't broke........" certainly bit me... If all else fails I may have to put the GTX570 back and do another re-install of OS/Vegas to see if that makes any difference as V2H worked perfectly with that card.. (will keep my specs as is until then).

Marco. wrote on 5/9/2015, 3:00 AM

The message you linked via Dropbox would appear if the AviSynth script got no data to read or if AviSynth does not work correctly.

Try checking your frameserve file first. Start the process Vegas2HandBrake from Vegas Pro and when this process hangs, open the folder "C:\source\".
Right-click the file "vegas.avi" and take a look at its properties.

How big (in MB) is this file "vegas.avi"?

Downunder wrote on 5/10/2015, 12:26 AM

Hello Marco

Her are links to the C:\frameserver\source_properties. "vegas.avi" file size is 7.43 MB

https://www.dropbox.com/s/o6sfqjfsw12hvk7/V2H%20frameserver_source%20properties%201.jpg?dl=0

https://www.dropbox.com/s/82ocic2uxiw9436/V2H%20frameserver_source%20properties%202.jpg?dl=0

https://www.dropbox.com/s/2xuxqx6gpx6tmg5/V2H%20frameserver_source%20properties%203.jpg?dl=0

Marco. wrote on 5/10/2015, 3:18 AM

Thanks for testing. This means to me FrameServer is working correctly. Then my guess is AviSynth fails.

In your post from yesterday you mention the content of the folder "C:\frameserver" and according to your post there is a file called "vegas".

This certain file should be the AviSynth file/script. But the correct name must include the file type AVS. So the file name actually should be "vegas.avs"!

Maybe simply renaming this file does the trick for your.

Downunder wrote on 5/10/2015, 3:43 AM

Marco

Re your comments please have a look at this image and let me know if it looks right

https://www.dropbox.com/s/1r8z10qvfl3812x/frameserver_vegas%20image.jpg?dl=0

Marco. wrote on 5/10/2015, 5:18 AM

Ah, yes, looks correct. Seems like only the display of the file type extension (.avs) is hidden.

Mmh, then I'd say AviSynth itself isn't working correctly on your system, if it works at all. So you might try uninstalling AviSynth and reinstall.
Then check the path: "C:\Program Files (x86)\AviSynth 2.5"

If it still doesn't work after a reinstall of AviSynth I'd be back to what wwaag already suggested: Using VirtualDub to check AviSynth.

Downunder wrote on 5/10/2015, 5:28 AM

I will keep trying. Just confirm though when one installs DebugMode FrameServer should it be in the default C:\Program Files (x86)\DebugMode\FrameServer\ or change to C:\Program Files\DebugMode\FrameServer\

Marco. wrote on 5/10/2015, 5:48 AM

C:\Program Files (x86)\DebugMode\FrameServer\

But DebugMode's FrameServer does not seem to cause the problem, otherwise there would not have been the vegas.avi file with a correct length.

Marco. wrote on 5/10/2015, 5:57 AM

Now before you proceed, please wait a minute. I just setup a small package which could help you test if both AviSynth as well as the File Mount works properly. I'll upload in a minute.

Marco. wrote on 5/10/2015, 6:10 AM

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

Download, uninstall and move the folder "test" to "C:\frameserver\source\".

Then from this location open the folder "test" and double-click the file "test.bat".

If something's broken an error message will appear.

If things work fine the file "video.avs" will turn into a folder "video.avs". Open this folder "video.avs", ensure there is a file "video.avi".
Go back the path one step, right-click the folder "video.avs" and select "unmount" from the dropdown menu.

.

Downunder wrote on 5/10/2015, 6:25 AM

Thanks will let you know in a few minutes.