I tested it, and you are right, it is not working. @Julusian or @silid: can you check, if the INFO TEMPLATE command uses the new URL syntax or if we need to add another path to the allowlist of Flash player, please?
EDIT: I disabled the allowlist and the problem persisted. So it seems to be broken somewhere else.
The INFO TEMPLATE command is the one that let a lot of users stay at the 2.0.7 version, to be able to query the variables from the template (for instance to use them inside a MOS system).
Hello everyone. Today flash has definitely stopped working. Although I had the updates disabled, Windows 10 did not allow the templates to run. A quick way to solve it has been to change the date to the servers and tell it that it is 2020. It has worked again.
Thanks didikunz, we were waiting to change everything following the instructions, but we didn’t have time. Today they have stopped working and I have posted this solution in case it has happened to someone else. Many thanks for your work.
Hi
The fix worked for me.
Had done nothing beforehand
Today I tried to run flash template from 2.3.0 didnt work
downloaded 2.3.1 and FlashCfgWriter.
copied config-files from 2.3.0 to 2.3.1
did run FlashCfgWriter as administrator, added my template folder, checked version (said “Everything well”) and wrote config.
started casparcg 2.3.1 and flash-templates did work.
Hello, any update on this? On other fixed server versions INFO TEMPLATE command is working, but not on 2.0.7.1. As a result some programs on my side don’t display text fields on this version.
Was wondering if there will be a fix.
The INFO TEMPLATE command is the one that let a lot of users stay at the 2.0.7 version, to be able to query the variables from the template (for instance to use them inside a MOS system).
It’s a shame because the ‘Info Template’ command is kind of critical to our workflow, so in the end we didn’t apply the patch and we’ll stay in Windows 1909 for a bit longer. We’ll consider changing if it gets a fix.
Did anybody try to apply the patch after the 12th of January or is that no longer an option at all?
You can run the patch anytime, with any Flash.ocx version. As long as Windows does not uninstall it, it works anyway. The trick with that mms.cfg file helps to keep the ocx in place after EOL. But there is also a way to install (the latest) OCX files on new systems, described here.
I been trying to run flash templates for a couple of days in a new installation without success. I downloaded and tried 3 versions of casparCG: 2.0.7.1-flash-eol-hotfix, 2.1.12NRK and 2.3.1-lts-stable, also FlashInstaller.zip and FlashCfgWriter.zip. I followed step by step the guide and I can’t get it work. Also I searched in the log file if I found something and this what i got in 2.0.7, for example:
2.0.7
I checked the Flash.ocx files (System32 and SysWOW64) and in the properties says 32.0.0.445.
I have CasparCG running flash templates in a notebook and the log shows also version 32.0.0.387, weird.
It does not really matter, what version it reports. But what really matters is, that the correct path to your template folder is set inside the mms.cfg. Because when it says (like it does in the line above) “Flash call failed” it is very likely, that something is wrong there.
I’ve been testing flash in the new releases today and I managed to get the 2.0.7.1 working just fine but I didn’t have the same luck with the 2.3.1 / 2.3.2.
I’ve tried setting parcial/total template paths in the server but the message is the same “CG ADD FAILED”.
I have not used the new versions a lot so maybe I’m missing something related to the media scanner or something like that?
I am currently trying fringe and weird configurations with the new flash situation and seeing if they work at all.
I know it defies its purpose and its kind of a security risk but I just set the mms.cfg template path to the C: drive so my different testing servers work without having to change the path every time.
Is there any other undesired effect from this that we know of?
When testing servers it’s a bit of a hassle having to change it every time I open a different build so I may keep this for a bit.
You also could add multiple AllowListUrlPattern=... lines to the mms.cfg files. The little FlashCfgWriter.exe utility does not support this, to keep it simple, but these files can be edited manually.