I'm going to think on it some tonight and will probably try a couple of things tomorrow or the next day.Fixed a folder permissions issue that prevented some enterprise end-users from accessing Snagit.įixed an issue that prevented accessing Snagit with a Windows username containing non-Latin characters.įixed an issue that caused video recording to fail on some Intel GPUs and monitors with a resolution higher than 1080p.Īdded the ability to customize the fade time for Screen Draw objects to the Video Capture settings. ![]() My working theory of what the problem is : When using the COM API in Snagit we take a lot of precaution to not overwrite existing settings in Snagit so that you could use the COM API and not have it mess up the Snagit UI and those extra precautions might be a bit too aggressive while doing a delayed capture. I've spent some time reviewing the code involved in Snagit and I haven't pinned down a good way to fix this yet. If that isn't working for you with the latest 13.1 release of Snagit, let me know the exact screen capture settings in MM that you are seeing trouble with. If I use a capture delay through the Snagit UI ( by creating a new profile that has a 5 second delay ), it works fine, but if I do the same from the COM API, everything falls apart and the code path taken isn't right.Ī workaround to use Snagit 13 with MM is to set the capture delay to 0, that is working well for me. I have verified what you already know and that is that it is related to the capture delay.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |