How to migrate from v9 to v10?
v10 SDK have a lot of API changes, a lot of properties and methods remove or replaces, now SDK API not "plain" as before, we got near 200-300 properties and methods for 1 main class of each SDK, that's too much.
Media Player SDK migration:
-
Upgrade project to .Net 4.0 or later. .Net 2.0 - 3.5 is no longer supported.
-
Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
-
Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
-
Update your video effects like shown in demo code and here.
-
Update video renderer like shown in demo application.
-
Update motion detection, chroma-key or object detection using special classes like shown in demo.
Video Capture SDK migration:
-
Upgrade project to .Net 4.0 or later. .Net 2.0 - 3.5 is no longer supported.
-
Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
-
Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
-
Update your video effects like shown in demo code and here.
-
Update video renderer like shown in demo application.
-
Update motion detection, chroma-key or object detection using special classes like shown in demo.
-
Now SDK have special class for each available output format. You must create class instance, apply parameters and assign it to Output_Format property, instead enum that used before.
Video Edit SDK migration:
-
Upgrade project to .Net 4.0 or later. .Net 2.0 - 3.5 is no longer supported.
-
Replace VisioForge.Controls.WinForms / VisioForge.Controls.WPF to VisioForge.Controls.UI in references.
-
Remove all properties that not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml for example). Store non-default values somethere in your code to apply them later.
-
Update your video effects like shown in demo code and here.
-
Update video renderer like shown in demo application.
-
Update motion detection, chroma-key or object detection using special classes like shown in demo.
-
Now SDK have special class for each available output format. You must create class instance, apply parameters and assign it to Output_Format property, instead enum that used before.
-
File adding API has been changed, please check demo code. Now you can add multiple segments from the same source file and specify additional independent setting.