its owned by the user, or by the SYSTEM). If still isn't working then this may be because you aren't the owner of the folder (ie. ![]() It sounds like you might be running the service not as an administrator, despite being logged in as an administrator.Ĭan you confirm that you running the Windows Service with elevated admin rights? (Right-click -> Run as Administrator) However, running your Windows Service as an administrator should allow you to read and execute from the Program Files directory. If you're trying to access these using a Windows Service they will be unreachable due to security permissions of the directory. It appears that the Blackmagic API files are in fact installed in the Program Files folder. What can I change, so the ImageCapture can capture images using the Blackmagic video drivers and the windows service will be started as real windows service.Ĭould it be that de “Blackmagic desktop video drivers” are installed in the ‘program files’ folder and therefore unreachable for our ImageCapture program? (I already tried to give the domainAdminUser full control to the Blackmagic folder) Ě windows service can’t write a log file in its “program files” folder.If the windows service is not started as a service, but started as a normal process, the ImageCapture is able to capture images.net with a manifest that required admin elevated rights The windows service is running using a real admin account (domainAdminUser).Please install the Blackmagic Desktop Video drivers to use the features of this application. However, as soon as we start a windows service which on his turn starts the ImageCapture as a child process, then the ImageCapture reports : If we start the ImageCapture with a logged in user, it works without any problems. This piece of software (called ImageCapture) is being used for some years without any problems. We are using our self-built C++/Qt/Opencv software for capturing 4K frames. We are using a Blackmagic intensity Pro card (Device display name: Blackmagic DeckLink Mini Recorder 4K, driver date July 2nd 2018, driver version 10.9.11.0) for video input.
0 Comments
Leave a Reply. |