Barco S4 1.8.5 and ICMP 1.4.4.20 released.

[Steve Guttag]

This seems to be, primarily, an ICMP-X related release. The previous release was 1.8.3 (and ICMP 1.4.4.18) so I'm showing what changed since then.




Version 1.8.5 (Service release)

This version includes the ICMP Software 1.4.4.20 and ICP-D software 1.2.1.10

Bug fixes:

• ICMP: Improve SP2K-xxC MKII support
• ICMP: New convergence pattern for MKII platforms
• ICMP: Fix an issue where some fast transitional effects were seen on screen
• ICMP: Implementation of an API way to retrieve the Video Mezzanine firmware version

Version 1.8.4 (Production release)

This version includes the ICMP Software 1.4.4.19 and ICP-D software 1.2.1.10

Bug fixes:

• ICMP: Fix an issue that could occurs while applying SCC file on SP2K-xxS

[James Gardiner]

Ok, does anyone know if this addresses an issue in that, for a content source, we found, if the password as a URL encoded character, say "#" url encoded is turned into a %23
The TEST button in communicator would pass fine..
We found that the ICMP would give a strange error when you selected the source in the web interface, and the FTP server would not even have an attempt of a login.

As you can expect, this was a huge problem for TMSs that have a # in the ftp password.

Has this been addressed? I reported this bug to Barco quite a few days ago and its a show-stopper.

I wouldn't be surprised why they came out just now.

[Leo Enticknap]

I thought this was fixed in 1.4.4.18. I had a customer affected by this (the Eclairplay download server has special characters in the default password used by the SMS to connect to it), and, per Barco/Cinionic's advice, updating their ICMP to 1.4.4.18 fixed it.

[James Gardiner]

I thought this was fixed in 1.4.4.18. I had a customer affected by this (the Eclairplay download server has special characters in the default password used by the SMS to connect to it), and, per Barco/Cinionic's advice, updating their ICMP to 1.4.4.18 fixed it.

So I am not the only one seeing this issue? I have a 60L with 1.4.4.18.29514. It gives a quick error in red "Parsing has been interrupted" and stops.
Looking at the FTP logs, the TEST command under communicator and all works as expected.
But when in the web interface and selecting the source with a # in the password to ingest from, there are no FTP logs generated, only the error in the web interface when selected.

Can others please confirm if they have seen this error?? I have been told no one else has this problem.

We are looking to go to the previous version to see if that fixes the problem.

[James Gardiner]

On my issue here, downgrading to 1.4.4.5.28134 fixed the problem. A comment is that setting the port number could be connected to the problem. Not that you can effect that option from a TMS ingest API command. But a bug was confirmed and Barco will address it.