I previously used the -CreatePlayer argument of Client.exe to create a Player that could open an Milestone export or database. This used to work correctly until the latest Milestone versions (2022 R2 tested) where I could no longer re-export footage when using the export Smart Client.
After comparing the Client Data folder between a Player exported from within the Smart Client and a Player exported from the Command Line the -CreatePlayer flag is not including the Plugins and MIPPlugins folders, meaning the Export plugin is not getting included. I don’t remember seeing Export as a Plugin in previous versions of the Smart Client.
Is this the intended behaviour or should the plugins be getting copied over too?
Is there any update on this? I could do with knowing if I need to develop a workaround or Milestone will fix the problem as it is causing us some problems.
Good news from Milestone Development: they fixed this issue and the fix will be included next release. So please keep eye on the release news from Milestone.
Hello, it looks like this bug has reoccured with the 2023 R1 release. When I include the Smart Client from the command line, the only Plugin that gets copied across is the Export plugin. If I do an export from within the Smart Client 4 other plugins get included.
This is causing issues as the search plugin is not getting included in exported footage
Smart Client when done as an export with “Include Smart Client” has the following plugins in the Plugin folder:
VideoOS.RemoteClient.Plugin.AdvKeyControl
VideoOS.RemoteClient.Plugin.CentralizedSearch
VideoOS.RemoteClient.Plugin.Export
VideoOS.RemoteClient.Plugin.HtmlViewItem
VideoOS.RemoteClient.Plugin.KeyboardSupport
Command line “Include Smart Client” has the following Plugins in the folder:
VideoOS.RemoteClient.PlugIn.Export
Both “exports” were performoned on the same machine using 2023 R1
Good news from Milestone Development: they fixed this issue and the fix will be included 2023R3 release. But I am wondering if you need a patch for the issue (like last time), please let us know about it.
Yes I could do with a hotfix. Multiple customers have a 2023 R1 installation that would require this fix as currently they are having to manually copy the plugins across to the exports for the search functionality.
If it is not going to be released until 2023R3 would a hotfix be available for the upcoming 2023R2 as well?
2023R2 will soon be released, it is 20th of June if I remember correctly.
If you update all your VMSs to 2023R2 then you might want to get a hotfix for 2023R2 only and you don’t need 2023R1 hotfix…? (Or you will keep some VMSs as 2023R1?)
So here comes questions from us to you -
Do you need the hotfix both for 2023R1 and 2023R2?
IF you need both, then which one should we deliver first?
We would need both as we are unlikely to update the 2023 R1 installs for a while yet. As for the priority, 2023 R1 would be the top of priority for us as it is already affecting customers. We are unlikely to be installing 2023 R2 until at least a couple of weeks after the release date so will not be an immediate issue.