From Vegas to HandBrake

Comments

flyingski wrote on 8/17/2014, 3:17 PM
Thank you Marco. Great time saver and it works perfectly on my Vegas 13 64 bit system.
Byron K wrote on 8/17/2014, 3:47 PM
Huge thanks Marco! Got it working.
I'm a doofus. Was installing the FrameServer app in the default path and as others were eluding to, needed to install it in the Vegas 12 folder.

- At DebugMode FrameServer Setup: Installation Options screen, Select: Sony Vegas (64-bit) Plugin. Click: Next
- Install FrameServer in the root "C:\Program Files\Sony\Vegas Pro 12.0" folder.
- Install frameserve_scripte in the "C:\Program Files\Sony\Vegas Pro 12.0\Script Menu\" folder.
Marco. wrote on 8/17/2014, 4:02 PM
Great to hear it works now.

Later next week I will add a more precise info to VegasVideo.de about what to take care of when installing the FrameServer. This is a trap indeed.
Byron K wrote on 8/18/2014, 6:41 AM
Just in time for my latest project, 4 cameras w/ an audio recorder track. I'll have a chance to put it thru it's test! (:

I also noticed that Handbrake has an option to shutdown the computer after render. I tried it on a short clip and it did shut down the PC. Of course it just shutdown Vegas, not sure if this would be bad for Vegas, but probably OK as long as the project is saved prior to rendering.

Thanks again Marco.
Marco. wrote on 8/18/2014, 1:01 PM
Thanks for raising and linking this topic in the HandBrake forum. I also sent a post (as reply to a former thread of yours) yesterday but it seems like they didn't publish.
Tom Pauncz wrote on 8/18/2014, 2:19 PM
Marco,
Just started to install your package and find that in one step we download "fs2hb_en.zip", however the name of the saved file is "fs2hb_de_02.zip".

Where is one mentioned in your doc?

Thx,
Tom
Grazie wrote on 8/18/2014, 2:35 PM
"de", gotta be the German language version.

G

Tom Pauncz wrote on 8/18/2014, 2:40 PM
Too true, mon...
Tom
Marco. wrote on 8/18/2014, 3:15 PM
Urgh … You are right. This mistakenly was the wrong (German) file, sorry. I just replaced against the English one, so now you will find the correct one by using same link on VegasVideo.de.
Both versions should work fine. In the English folder only the readme files and the explanations and messages in one Vegas script are different.
Tom Pauncz wrote on 8/18/2014, 3:25 PM
Thanks Marco... :-)
Tom Pauncz wrote on 8/18/2014, 3:55 PM
OK .. got it all installed, but having problems.

1. For the tab "General" at "When done" select "Quit HandBrake" - I don't see that option and am on the latest version.

2. More problematic, an error is thrown:
An Unknown Error has occured.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.IO.FileNotFoundException: Could not find file 'D:\Program Files\Sony\Vegas Pro 13.0\HandBrakeCLI.exe'.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at HandBrakeWPF.Helpers.CliCheckHelper.CheckCLIVersion() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.9.9\win\CS\HandBrakeWPF\Helpers\CliCheckHelper.cs:line 48
at HandBrakeWPF.ViewModels.MainViewModel.OnLoad() in c:\HandBrake\Hudson\workspace\Release_WindowsGui64\0.9.9\win\CS\HandBrakeWPF\ViewModels\MainViewModel.cs:line 890
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Caliburn.Micro.ActionMessage.<.cctor>b__d(ActionExecutionContext context) in C:\Projects\Blue Spire\Caliburn.Micro\src\Caliburn.Micro.Silverlight\ActionMessage.cs:line 266
at Caliburn.Micro.ActionMessage.Invoke(Object eventArgs) in C:\Projects\Blue Spire\Caliburn.Micro\src\Caliburn.Micro.Silverlight\ActionMessage.cs:line 228
at System.Windows.Interactivity.TriggerBase.InvokeActions(Object parameter)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at MS.Internal.FrameworkObject.OnLoaded(RoutedEventArgs args)
at System.Windows.BroadcastEventHelper.BroadcastEvent(DependencyObject root, RoutedEvent routedEvent)
at System.Windows.BroadcastEventHelper.BroadcastLoadedEvent(Object root)
at System.Windows.Media.MediaContext.FireLoadedPendingCallbacks()
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Interop.HwndTarget.OnResize()
at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)

Hope some of this makes sense to you.

Tom


edit 1: Though not mentioned in your install notes, copying HandBrakeCLI.exe from the HB install folder to the SONY Vegas Pro 13.0 directory solved this issue.

Now, all I see is HB comes up, black bar appears on bottom showing "Scanning Title...." and then nothing. Render does not take off. If I click the green Start button it renders.

edit 2: I watched the final video tutorial again and I see that I have to manually press the green Start button. Sorry for confusion.
Erni wrote on 8/18/2014, 6:56 PM
Hi Marco, the things come to work!

I have a problem in the variable "path", some script of AfterEffects seem have changed it.
I restore with c:\windows;c:\windows\system32;c:\windows\system32\wbem
and now the process works.

I can not find your script in Vegas, but I can start it manually ->Tools/Scripting/Run script and voilá!

Thanks!

Erni :)
Byron K wrote on 8/18/2014, 10:22 PM
Tom,
You may have an older version of Handbrake. I had to download the latest version of Handbrake to see the "Quit Handbrake" dropdown.
Tom Pauncz wrote on 8/19/2014, 7:05 AM
Thanks Byron,
I figured I may have to do that and got the latest nightly build. And there it was..
All good now.
Tom
Marco. wrote on 8/19/2014, 10:09 AM
-> There is another case where Vegas Pro refuses to show up .js scripts in the script menu.

Do other .js scripts show up fine for you in the Vegas Pro script menu, e. g. can you see the script "Export EDL"?
Erni wrote on 8/19/2014, 12:07 PM
Marco.

In Tools/Scripting:

I see: Add Timecode to All Media(cs), Batch Render (cs), CC_ShowEventLenght (dll), Dawf (dll) and Excalibur5 (folder, dll) . All working.

Can't see: (all in the same folder .../Vegas Pro 13.0/Script Menu): Export Chapters (cs), Export Regions as Subtitles (cs), Export EDL (js), Remove Letterboxing (cs), and yours Send2HandBrake (js) and unmount (js). All working in manual mode.

Why? I don't now. Older Vegas versions work fine with all (I remember)

Maybe is a netFramework issue...

Thanks again

Erni

Grazie wrote on 8/19/2014, 12:17 PM
Hmm...

I'm doing something wrong:



1] I do have FrameServer installed and working correctly in VP13.

2] I do have the Icons on the Toolbar.

3] I get the process starting and proceeding and opening HandBrake.

4] I don't get an MP4 at the end of the process.

I must be doing something incorrectly ion install.

Grazie


Tom Pauncz wrote on 8/19/2014, 12:21 PM
Grazie,
One of the options in Handbrake - Tools-Options-Output Files, the last option is "MP4 File Extension" select "Always use MP4".
Tom
Grazie wrote on 8/19/2014, 12:30 PM
Nah Tom . . I needed to RE-boot the PC! A swift kick in the Kishkes . . .

Now working like a charm.

No more friggin' interim renders.

MARCO FOR KING OF THE UNIVERSE!

G

Erni wrote on 8/19/2014, 12:31 PM
"MARCO FOR KING OF THE UNIVERSE!"

Yes!!!!
Marco. wrote on 8/19/2014, 12:33 PM
One indication for the error message you show above is there might be no frameserve file created.

So if you try to frameserve manually (completly without using that Vegas2HandBrake workflow) and use same path (C:\frameserver\source\): Is the FrameServer's signpost AVI in this folder while frameserving?

Edit:
See it's working now. Never mind.
Marco. wrote on 8/19/2014, 12:36 PM
Strange. Vegas bug or .Net issue. I will report to SCS.
Grazie wrote on 8/19/2014, 12:39 PM
Hi Marco. Does this help you determine what I'm doing wrong?



G

Tom Pauncz wrote on 8/19/2014, 12:39 PM
+1 Erni
+1 Grazie.
:-)