We support a few different renderers that you can select from the preferences. We build the graph manually to avoid the common issues where a system has badly configured filter priorities (Select the player from preferences). C# allows us pretty easy access to interface with c components. The video player in Fast video cataloger is custom for FVC and is written in C++ and uses a DirectShow filter graph to play videos. WPF has a video player component but that one has pretty bad performance and does not support all video formats. The browser window is a hosted Chromium web browser, CEF sharp. WPF has a web browser component but that uses internet explorer. Video encryption uses Aes encryption and we hook the filesystem to be able to work on a stream level. You can extend Fast Video Cataloger with C# either by loading the scripts in the console windows or by creating actions that link to C# scripts. The scripting interface uses CSScript and we expose the API through some abstract interface classes as well as the direct WCF interfaces. We have made quite a few optimizations to handle huge video collections with good performance. WPF uses DirectX internally, and DirectX uses graphics hardware for rendering. The user interface in Fast video cataloger is done in WPF and a few extra UI components. We have had quite a bit of performance issues with garbage collection and quite a few tricks to work around these performance issues. C# is generally pretty efficient, and we have access to most of the windows system using the. We use a lot of async/await for threading as wait as background workers and explicit threading. The main application is written in C# using Visual Studio and the. The goal has always been to provide a video content management system for Windows with great performance. Here is a very high overview of the technology we have used to build Fast Video Cataloger.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |