Vegas Pro 14 to Handbrake: no FrameServer 3.0 in "render as" window

Back to post

Comments

wwaag wrote on 8/9/2019, 11:00 AM

What a nightmare.

Here is the link to a previous version. https://www.dropbox.com/s/j1g7uss2ssezot5/fssetup-2.15.exe?dl=0

Before installing, I would first completely uninstall HOS, which will also get rid of VirtualDub which is OK.

Then go to those registry locations and make sure that the registry entries are deleted. If any there, post a screen shot just to make sure they are OK to remove since other entries also have "dfsc" as part of their name.

Then install the old version and see if it is there in Vegas 14.

Sorry. Posted wrong link.

 

Last changed by wwaag on 8/9/2019, 11:03 AM, changed a total of 2 times.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Dana wrote on 8/9/2019, 12:28 PM

Yes, it definitely is.

Thank you for the 2.15 version. It could be the solution. But then it would also mean that there is something wrong with the 3.0 version.

Or maybe that brand new 3.0 version of Frameserver is intended for Windows 10 only? Is it my version of Windows that causes the problem? Idk. I don't know anything anymore. Although it wouldn't be really logical, would it, because many people still use Vegas Pro 14 on Windows 7. And the FrameServer download page doesn't say that the new 3.0 version is meant exclusively for Windows 10 and for recent updates of Vegas. And if the issue was linked to my Windows 7, then my Vegas Pro 14 would just stop working, wouldn't it. Yet everything else is working quite fine with my operating system, except for that "vegas pro to handbrake" export option.

 Anyway far from having your detailed professional knowledge in the matter, the only thing I can do is try to be logical. Another question I've been asking myself: what about all the other files that go with Handbrake, such as AviSynth, Pismo File Mount, AVFS…? I have now the most recent versions of them installed, and maybe it is not really good. Perhaps these brand new versions are really meant for a newer system and a newer version of Vegas, even though the download pages do not specify it. My Handbrake did work well with the previous versions of AviSynth, Pismo File Mount, AVFS, and of course of FrameServer. Until it stopped working last week, that is. Maybe I shouldn't have uninstalled everything and installed new versions straight away; maybe I should have looked for another reason of the Handbrake failure first.  Too late now. But if nothing else works, I could at least try to install all the old versions back, and see how my Vegas Render As window behaves then.

I will now follow your advice /instructions. And please know that I am very grateful for all your suggestions. It must be extremely difficult to guide someone like me (not a real pro) from a distance. I am pretty sure if you could have a close look at my laptop you would find the problem straight away.

Dana wrote on 8/9/2019, 12:55 PM

Looking for any remaining "dfsc" in the Registry:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 -- No trace of dfsc.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\drivers.desc -- No trace of dfsc.

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Drivers32 -- as above

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc -- idem

wwaag wrote on 8/9/2019, 1:01 PM

"HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\drivers.desc -- idem"

What is idem?

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

vkmast wrote on 8/9/2019, 1:05 PM

idem = the same

Dana wrote on 8/9/2019, 1:11 PM

Waagg -- It is a Latin word, sorry. It means "ditto", "as above". https://www.wordreference.com/ende/idem

Dana wrote on 8/9/2019, 1:43 PM

Eureka /heureka /yippee /hooray!!!!!!! I can see Debugmode FrameServer in my Vegas Pro 14 !!!!!!!!

Thank you so much, waagg, and to all of you in Vegascreativesoftware... you are the best!!!

I have literally tears in my eyes right now. Here is the proof, I have to post it quickly before it disappears:

wwaag wrote on 8/9/2019, 2:01 PM

@Dana

If this works for you, great!! Just be aware that you may experience the same problem with the old version that you have just installed. When the new version (3.0) was introduced, quite a few (including me) experienced Vegas crashes whenever the old FrameServer version started. The problem was traced back to the old version attempting to "check for updates". I might add that the new version (which includes a 64bit decoder) has no advantage to you since the Vegas 2 Handbrake workflow only uses the 32bit decoder.

Another word of caution. The latest version of HOS is not compatible with the old FS version. At some point, however, you may wish to try HOS since it offers significant advantages over the Vegas2Handbake workflow. It is still a mystery why the latest frameserver version does not work with your system.

In any case, good luck and post again if there are problems.

BTW. Thanks for the Latin lesson.

Last changed by wwaag on 8/9/2019, 2:02 PM, changed a total of 1 times.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Dana wrote on 8/9/2019, 2:15 PM

Waagg -- Oh my, what a pity that Happy Otters do not work with the 2.5 version! That's very disappointing to me. But maybe, somehow (don't know how though), the 3.0 will start working with my Vegas. For the time-being my priority is to render my project via VegasToHandbrake, and then I will have enough time to try again and again, until I succeed in making the 3.0 version appear in the Render As window. I was born under the Taurus sign, so I do not abandon easily, lol. Thanks again for your help, incl the heaps of important and interesting info.

As for "idem" you are very welcome; I live in southern France so it is easy for me to understand Latin (the tongue of ancient Rome).

Former user wrote on 8/9/2019, 2:38 PM

Congratulations! I am impressed with your determination to solve the problem. I am also from Latin America (Brazil). wwaag is a great teacher and one of the most knowledgeable people in this forum. I'm glad the problem has been resolved. I know exactly what the feeling of accomplishment is like when we get over something.

Dana wrote on 8/9/2019, 2:50 PM

Veg -- Tu tambien me ayudaste muchisimo, eres un verdadero pro. Gracias gigantes! (hablo solo espanol, no portuges, sorry.)

Todavia tengo que hacer la configuracion de Frameserver 2.5... hope it'll go well and that the handbrake will start working properly. We'll see.

Dana wrote on 8/9/2019, 4:10 PM

Okay... so I am back. Handbrake is not working. "Unable to create mount". *sigh*

Is it caused by the latest version of Pismo File Mount Audit Package?

I have just finished reading a discussion in which Marco suggests downloading Pismo File Mount Build 180, from an archive: https://www.vegascreativesoftware.info/us/forum/vegas2handbrake-not-working-handbrake-doesn-t-work-video-stays-0--109538/

I have Pismo build 192. Should I download a different version? Thanks.

wwaag wrote on 8/9/2019, 4:17 PM

I don't use Vegas2Handbrake any more, but as I recall the problem concerns the location of the Volume mount that changed in the latest edition of PFMA. There is a script somewhere that requires changing to the new location---something like C:\Volume. Perhaps someone familiar with Vegas2Handbrake could comment.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Marco. wrote on 8/9/2019, 4:35 PM

Sorry, not even I am familiar with Vegas2HandBrake anymore. I left it for a more simplified and very individual solution and I was very glad to see HOS arising. Really, taken all the time someone is going to invest making Vegas2HandBrake working, invest same time in learning HOS and you'll get so much more out of it.

Dana wrote on 8/9/2019, 4:53 PM

Thank you, wwaag and Marco.

I find Handbrake truly amazing. But you are right, the problems I've been experiencing with frameserver and now Pismo are just too exhausting and time consuming, and even if I solve the current problem now, something else may occur again in the near future which might prevent Handbrake from working.

I would happily switch to HOS right now - but how? Unfortunately it doesn't work with frameserver 2.5. And my Vegas Pro 14 "render as" window doesn't seem to like the 3.0 version of frameserver at all. What to do, what to do...

Maybe if I installed the HOS again (now that I can see the frameserver in the "render as" window), maybe it would work? The version 3.0 would somehow overwrite the older version... I don't know. I just don't want the frameserver to disappear from the list of the templates.

Former user wrote on 8/9/2019, 5:40 PM

@Dana

I am sending you the version of HandBrake that I use here and also a compiled of all the material that is needed to work properly in Vegas Pro 14. The installation of the compile is automatic, you just have to confirm the installations. Hope it works. Worth trying.

Download link here:

https://drive.google.com/file/d/1VKx2X0fJXRM2ti9sCyJlis8ZhikOs91u/view?usp=sharing

Installation tutorial here:

Dana wrote on 8/10/2019, 5:36 AM

Veg -- I spent my night uninstalling and reinstalling everything, in vain. Am reading your msg only now (at noon, French time)... omg, you are an angel!! Thousand thanks!!! I will do the installation of the compile later tonight. Or better first thing tomorrow; I need a full night sleep to recover my capacity to focus on things.

Dana wrote on 8/10/2019, 6:30 AM

@Former user

Google drive doesn't let me access the file, grrrrrr. Could you please send it to me in another way, maybe via dropbox? Thanks in advance. Sorry to take more of your time.

Former user wrote on 8/10/2019, 8:50 AM

@Dana

This is the DropBox link

https://www.dropbox.com/s/wxna3y2krk4026w/Vegas2Handbrake.rar?dl=0

Dana wrote on 8/10/2019, 9:15 AM

@Former user

Safely downloaded in my Data drive. Can't thank you enough!

Dana wrote on 8/11/2019, 5:37 AM

@wwaag

--"Then go to those registry locations and make sure that the registry entries are deleted. If any there, post a screen shot just to make sure they are OK to remove since other entries also have "dfsc" as part of their name."--

Before installing Veg's precious compilation, I am doing a clean uninstall of Hos, Handbrake and everything that goes with it. While checking the Registry and the System32 folder, I have found some traces of "dfsc". Should I delete them please? Thanks.

wwaag wrote on 8/11/2019, 10:38 AM

If you uninstalled HOS properly, those should not be there. However, you can remove those items shown in the top images and bottom left image safely. However, do NOT remove those items shown in the bottom right image--they are NOT part of the frameserver.

Last changed by wwaag on 8/11/2019, 10:39 AM, changed a total of 1 times.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.

Dana wrote on 8/11/2019, 2:06 PM

So sorry for the confusion. Let me precise: The images with red underlines are your own. You had sent them to me as a reference (for me to search identical things in my registry). The rest, in blue color, is what I see in my computer.

I was comparing everything to your "models"... and then, silly me, I made screenshots of both your images and mine. Sorry again.

I have just cropped your images out of the screenshots. Here is what I see in my registry, and in my System32:

1.

2.

3.

4.

So if I understand well, I shouldn't delete anything... or should I?

 

wwaag wrote on 8/11/2019, 2:13 PM

The items shown in 1,2,3 are from your installation of 2.15. If you uninstall 2.15, they should be removed. If you want to keep 2.15, then leave them alone. You should definitely NOT remove those items from 4.

AKA the HappyOtter at https://tools4vegas.com/. System 1: Intel i7-8700k with HD 630 graphics plus an Nvidia RTX4070 graphics card. System 2: Intel i7-3770k with HD 4000 graphics plus an AMD RX550 graphics card. System 3: Laptop. Dell Inspiron Plus 16. Intel i7-11800H, Intel Graphics. Current cameras include Panasonic FZ2500, GoPro Hero11 and Hero8 Black plus a myriad of smartPhone, pocket cameras, video cameras and film cameras going back to the original Nikon S.