What a pity that Mpeg in mp4 container doesn't work. For me the regular mp4 method is only of use if I wanted to really lower bit rates for internet. I had difficulty telling quality apart when I render mp4 in Vegas at very high bitrates. The ultimate winner would be that mpeg 2 conversion to DVD.
UPDATE: I'm on Handbrake 0.9.9 version and the mpg option is available on the video tab. I simply select the 720 width (PAL widescreen resolution) 25 fps and hey presto it renders out without error. DVDA however does insist on re-rendering even though I changed the file extension from .mp4 to .mpg
Now immediately I notice something. My 1080 -> SD renders from Vegas mpeg2 all have what I can only describe as artifacts around moving objects, a bit like noise. The Handbrake render does not. This is a big improvement but still to my HD spoiled eyes, both SD versions, Vegas and Handbrake look soft.
I shall fiddle some more, but so far, looks promising.
In theory certainly there are several choices how you could modify the given scripts, cmd and macro functions to work with different tools. For example I have another version only meant for lanczos scaling from Vegas to Vegas.
It always depends on how the used applications (like HandBrake) work and in which ways you could control them. But I don't know how MakeMKV works.
> This is a big improvement but still to my HD spoiled eyes, both SD versions, Vegas and Handbrake look soft.
Try adding a little sharpening before any downrezzing. I use the simple Sony sharpening filter that comes with Vegas. The default setting of 50% is a good place to start.
I just went through the setup process following all the directions on this page: http://www.vegasvideo.de/vegas-2-handbrake-en for Vegas 12. It looked like everything was working. However, after the step where handbrake scans the video, nothing happened. handbrake's status message on the bottom left just says Ready and there's no MP4 file in the designated folder. What could have gone wrong? I should also mention that the only change I made was removing the line about progressive video since my source is interlaced. Rereading this thread, it seems mine is the same problem that dingus reported.. I'm using the latest production version of Handbrake.
Edit: I'm not entirely too bright, I was trying to figure out how the script told handbrake which preset to use, then I realized that it stops on purpose so you can select settings, or a preset to use, then just click start (for anyone else who runs into this)
Microsoft.JScript.Vsa.JSVsaException: UnknownError (0x801330FF): System.ComponentModel.Win32Exception (0x80004005): The system cannot find the file specified
at System.Diagnostics.Process.StartWithShellExecuteEx(ProcessStartInfo startInfo)
at System.Diagnostics.Process.Start(ProcessStartInfo startInfo)
at JScript 0.Global Code() in Sony.Vegas://Script/__ScriptText__:line 9
at Sony.Vegas._Startup.Startup()
at Microsoft.JScript.Vsa.BaseVsaEngine.Run()
Why does everyone keep upgrading their software?? "If it ain't broke, don't fix it" is not just a clever saying, but is something everyone here should live by, if they value their time and want to get things finished before their deadline passes.
Most software upgrades, especially once you get past the first few releases, provide very small incremental improvements, but usually also often break things that used to work.
My recommendation:
1. Turn off ALL automatic updates.
2. Only update software when there is a feature that will actually make a HUGE improvement in your life, and let you get something done faster or better.
3. When you are going to upgrade, at the very least create a system restore point, and better yet, do a complete backup of your boot drive.
I just looked at my Program Files folder, and almost all the the "modified" dates are several years old. Everything works just fine.
As for this specific problem, I use MeGUI instead of Handbrake, but it is similar in some ways. When I first installed it 4-5 years ago, I didn't realize it was constantly updating itself (they don't make the automatic update obvious), and suddenly one day, nothing worked. I was able to restore the original installation using a backup, and I haven't updated since.
I just spent more time typing this than I've spent solving update problems in the past five years.
JM: Why does everyone keep upgrading their software??
Er, wanting "better"? And, not speaking for everybody, when I do, I do it when there is an option to back-track - apparently not here with HB for me - and reinstall an earlier working copy. Could this could be a clue? Maybe I need to uninstall all the components of the One-Click and restart in the order as described by Marco. Maybe I can't - for me - just reinstall an earlier version of HB and have the LINKAGES to be available, again.
No Auto Updates here. Each update done manually and have been for at least 3 years now.
Restore did nothing to improve matters. I went back to a point prior a date that I can prove this one-clicked did work.
FYI, how would I know the benefits unless I trailed it? - But that's me and not you.
Thank you for your typing-time and your wish to assist.
I don't know whether this one relates to your problem but now I have an issue on my own system. It seems like after a Windows update the file mount system doesn't work no more. In this case when using the start script from Vegas, frameserving starts fine but then the process hangs in a cmd loop.
I will take a look at the file mount system though at the moment I have no idea how to fix that.
Marco, sorry to hear that. Could it be that the M$ Update broke a connection to and from your script? Would a reinstall of your Script make any difference?
Back in biz. This was missing.- Move the folder "frameserver" to the main partition C:\ (this is critical because all the scripts and batch files used in this process refer to this path)
I ALSO reinstall AVISynth too.