VP18 Planar Tracker Issue

PhilippZ wrote on 9/24/2020, 5:20 AM

Hi,

unfortuntely I have the next issue with VP18. You can see it here:




 

--------------------------------------

This is the text from the box:

Beim Aufruf einer COM-Komponente wurde ein HRESULT E_FAIL-Fehler zurückgegeben.

   bei ScriptPortal.Vegas.IOFXPlugCOM.GetUniqueID(String& val)
   bei ScriptPortal.Vegas.Effect.get_OFXEffect()
   bei MotionTrackWindow.MainWindow.GetValidGenericVideoEffects(VideoEvent evnt, Boolean lookForRotationalParams)
   bei MotionTrackWindow.MainWindow.PopulateAttachMenu()
   bei MotionTrackWindow.MainWindow.UpdateControlValues()
   bei MotionTrackWindow.MainWindow.AddMask(Object sender, RoutedEventArgs e)
   bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   bei System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   bei System.Windows.Controls.Primitives.ButtonBase.OnClick()
   bei System.Windows.Controls.Button.OnClick()
   bei System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
   bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   bei System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
   bei System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
   bei System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
   bei System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
   bei System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
   bei System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
   bei System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
   bei System.Windows.Input.InputManager.ProcessStagingArea()
   bei System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
   bei System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
   bei System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
   bei System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   bei MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   bei System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   bei System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

------------------------------------

Unfortunately, VP18 is so buggy with me that I cannot use it. I am very disappointed with VP18 and also from the (unfortunately) bad support. In contrast, VP17 works well.

Maybe anybody here in the forum can help me. Thank you!

Philipp


------

System: Win10 64 / AMD 1800x / Nvidea GTX 1080

Comments

VEGASPascal wrote on 9/24/2020, 5:27 AM

@PhilippZ Bad support???? 5 minutes after your post the first developer is responding. Please also send a bug report with a good description to follow the steps you have done.

PhilippZ wrote on 9/24/2020, 5:38 AM

@PhilippZ Bad support???? 5 minutes after your post the first developer is responding. Please also send a bug report with a good description to follow the steps you have done.

Hi Pascal,

yes. Unfortunately the support team from Dresden (Germany) only responded to my other problem with VP18 after 14 days and after several inquiries. The problem could not be solved and none of the suggested solutions had much to do with the problem (and no reaction to my order cancellation emails). I think that's not good support.

I've already sent bug reports (except in this video).

Thank you for your fast response.
 

Vegas_Sebastian wrote on 9/24/2020, 5:44 AM

@PhilippZ It seems something is wrong with installation. Could you check if 'Motion Tracker FX' listed in your Video FX window and you're able add that FX to our clip? And which FXs are attached to clip 'P1122438'?

VEGASPascal wrote on 9/24/2020, 5:47 AM

The VEGAS support team is in Madison. The Magix support in Dresden is only redirecting your issue. The responce was bad and took too long??? Please send always bug reports with a good description and your forum name... so it is easier to find and to respond.

PhilippZ wrote on 9/24/2020, 5:52 AM

@PhilippZ It seems something is wrong with installation. Could you check if 'Motion Tracker FX' listed in your Video FX window and you're able add that FX to our clip?

Hi Sebastian, thank you for response.

I can add the FX to the clips and it shows the box in the viewer. But after that, I can't open the Tracker anymore (right click and click on Tracker -> nothing happens anymore).

I started the project in VP17, but the clip is added in vp18 to the timeline. Maybe that is the problem?

If I start a new clean timeline with one clip, the tracker works fine.

If I copy the project timeline in a new clean timeline, I have the same issue.

PhilippZ wrote on 9/24/2020, 6:01 AM

The VEGAS support team is in Madison. The Magix support in Dresden is only redirecting your issue. The responce was bad and took too long??? Please send always bug reports with a good description and your forum name... so it is easier to find and to respond.


Okay thank you! I started a ticket over the "Support" Site here: "www.vegascreativesoftware.info/de/support/" and got a answer from the German Team in Dresden. With my dynamic RAM issue, Vegas never crashed, so I don't saw the bug report mask.