If you delete the items from 1-3, version 2.15 will no longer work either. If you've already deleted them, then the best thing to do is run the FrameServer uninstaller and "start over" with installation of v2.15 as well.

The Debugmode FrameServer is actually a part of Veg's compilation (that I intend to install). I don't know which version he put into the compilation... but it doesn't really matter as long as Handbrake works.

Veg writes the following: "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."

Veg's tutorial is very well done too, very clear. I think it is definitely worth trying.

Let's hope it'll work. And if not? Well I'll just have to try something else. I have to keep trying, until one of them (Handbrake or Happy Otters) suddenly starts working. There is no reason for me not to succeed. My OS is healthy, my Vegas Pro 14 is in perfect condition too... there must be, somewhere, some small "invisible" mistake that I /we haven't discovered yet - but it is only a question of time. At the end of the year I will get myself a new computer with Windows 10 and a stronger processor, and probably a newer version of Vegas too - and then everything will be much easier. But for the time-being, the only thing I can do is follow every professional advice I am given.

Veg, you are a GENIUS. Thank you soooo much. It works!!!!!!!!!

Your compilation is flawless from the beginning till the end. My Vegas Pro 14 is perfectly compatible with your chosen (older) versions.

Last night I couldn't believe my eyes when I saw the friendly Handbrake screen suddenly pop up from my Vegas. It seemed too good to be true; I didn't want to cry victory too early (it might have been just a happy accident). So I tested it two times last night and several times today… not once did Vegas or Handbrake crash. Wow.

There is only one tiny little issue, which in my humble opinion should be easily solvable, but for the time-being let's fully enjoy the present achievement:

Thanks a million, Marco and Wwaag, for opening my eyes on so many important details. Wwaag, by bringing up the FrameServer version subject ("the new version 3.0 has really messed up things for some systems") and sending me the 2.5 version, you solved half of the problem.

I hope this thread will help many people who, like me, are still using older versions of Vegas and have recently experienced problems with Handbrake.  

Congrats for solving this severe issue! Now give it some time then join us using HOS instead … ;)

I will! It is a promise. :)

I have just noticed something (concerning this forum). Two days ago I tagged Wwaag's idea as a solution. Today I wanted to add Veg. But by clicking on "Tag as a solution" under Veg's compilation link - it has automatically erased the tag under Wwaag's post. Why? Clearly, the solution to my problem has been brought in two part, or steps. So why am I not allowed to tag both? Can't there be two, or even several right ideas, several solutions, or several parts of a solution? Explain please, thanks.

@Dana

Glad it worked!

There is only one tiny little issue, which in my humble opinion should be easily solvable, but for the time-being let's fully enjoy the present achievement:

I looked at your timeline and noticed that you didn't add a 1 second event at the end of your project.

See again the tutorial I made from 00:02:05, note that I added an event of exactly 1 second at the end of the project.

It will always be necessary to add a 1 second event to the end of the projects you will render using Send2Handbrake to avoid a bug that exists during the rendering process that does not allow the last seconds to render correctly.

@Former user

Thank you for bringing up my most recent issue.

--"I looked at your timeline and noticed that you didn't add a 1 second event at the end of your project."-- I did add the 1 second buffer; I always do so before sending my project to Handbrake. My yesterday screenshot was not detailed enough for you to see it, sorry about that. Here is a close up:

My recent "tiny little issue" concerns frameserver. A weird thing happened at the end of the rendering procedure yesterday: FrameServer Status - Not Responding. Fortunately I had already rendered the project several times with success, so I was not really worried, just a bit annoyed. Today the same "not responding frameserver" occurred again. This time I decided to wait, but after several hours nothing changed so I stopped the rendering procedure and closed the applications. It intrigues me. I must have checked (clicked on) something wrong in the Handbrake settings... Or is it caused by my CPU that is not of the best quality? My processor is easily overloaded; I definitely need a new laptop the sooner the better. But most probably it is something inside Handbrake that I messed up yesterday while trying to understand the software better. So I guess this new issue is the price to pay for my insatiable curiosity. Oh well. Am trying to solve it by myself, but if you are willing to give me a hand I would be glad.

The Encode Log says the following:

For 50P you need to increase your level to 4.2 (I believe). Handbrake should have an Auto setting as well which automatically sets your Profile and Level based on your input. The safest thing is to use that setting.