Today we released our brand new V-Control 4. The first release has beta status and is available for Windows 64 Bit only. Other platforms will follow, including Raspberry Pi.
New in V-Control 4
- We implemented the concept of device variables. A device variable represents the status of a device, for example the time code position or power status. If one of those variables changes, an event is triggered. This event can handled by a task. To request status messages from connected devices, the V-Control device driver send commands periodically and ask for status changes. This can be up to every 20 Millisecond. The answer is automatically processed and stored in the device variables.
- Now two or more tasks can access the same device. V-Control buffers all commands and fires them if the device is free. This was necessary because of our new GUI designer and the concept how it works.
- New Platform Raspberry Pi. V-Control 4 is prepared to run on Raspberry Pi. We’re really looking forward to the beginning of next year when we launch V-Control on this exiting platform.
- Saving Projects is now processed by a separate Task, allowing to work during saving.
- Save Increment saves Projects and automatically adds an incrementing number. So saving “MyProject.vc4” leads to “MyProject_001.vc4” saving that again leads to “MyProject_002.vc4” and so on.
Under the hood we changed almost 40% of the code. The device manager was almost written new, and also the IO manager gets some improvements. The old Calendar and Timer events have been removed, because they are unnecessary now. The concept of device variables and a new System device providing time and date information replaces them.
- Timestrips broken, will be fixed later
- Remote Mode broken, will be fixed later