v10 SDK has many API changes, a lot of properties and methods removed or replaced, now SDK API is not “plain” as before, we got near 200-300 properties and methods for one 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 not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml, for example). Store non-default values somewhere in your code to apply them later.
- Update your video effects like shown in demo code and here.
- Update video renderer like shown in the demo application.
- Update motion detection, chroma-key, or object detection using special classes like shown in the demo application.
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 are not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml, for example). Store non-default values somewhere in your code to apply them later.
- Update your video effects like shown in demo code and here.
- Update video renderer like shown in the demo application.
- Update motion detection, chroma-key, or object detection using special classes like shown in the demo application.
- Now SDK has a special class for each available output format. You must create a class instance, apply parameters and assign it to Output_Format property instead of enum 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 are not found in your WinForms/XAML designer file (Form1.Designer.cs or Windows1.xaml, for example). Store non-default values somewhere in your code to apply them later.
- Update your video effects like shown in the demo code and here.
- Update video renderer like shown in the demo application.
- Update motion detection, chroma-key or object detection using special classes like shown in the demo application.
- Now SDK has a special class for each available output format. You must create a class instance, apply parameters and assign it to Output_Format property instead enum that was used before.
- File adding API has been changed. Please check the demo code. Now you can add multiple segments from the same source file and specify the additional independent setting.