Layout and Scheduling problems

Hello I have the same problem and the CMS log I verified that the following string is truncated to 460 characters
397.jpg the filename is truncated with 397.jp

when you start scheduling

XMDSSoap4

layout file=“37” fromdt=“2016-02-19 08:30:00” todt=“2016-02-19 21:00:00” scheduleid=“109” priority=“0” dependents=“38.jpg,345.jpg,346.jpg,347.jpg,348.jpg,349.jpg,350.jpg,351.jpg,352.jpg,353.jpg,354.jpg,355.jpg,356.jpg,358.jpg,357.jpg,359.jpg,360.jpg,362.jpg,361.jpg,363.jpg,364.jpg,365.jpg,366.jpg,367.jpg,368.jpg,369.jpg,370.jpg,371.jpg,372.jpg,373.jpg,375.jpg,374.jpg,376.jpg,377.jpg,378.jpg,379.jpg,380.jpg,381.jpg,382.jpg,383.jpg,384.jpg,385.jpg,397.jp”/>

you have any solutions?

Hi Andrea, Michele

My apologies I wasn’t aware of it, but there is indeed a bug regarding this character limit in 1.7 series.
Unfortunately it can’t be fixed in this series due to how this change would affect the players.

It is fixed in the 1.8 version (currently in alpha).

Again my apologies for all the confusion caused by it.

HI Peter, this error is serious problem for me,
because I can not install alpha release to solve the problem.
So I ask you do you have a tool that reset the MEDIAID on DB and rename all the file?
Currently I have media files that start from 2396 4 bytes, if they start to 1 the problem is solved.
Thanks
Andrea

i’m afraid we do not have such a tool we can share - the mediaId in the database is used throughout the CMS and also in the XLF file (which is generated at save time). I don’t like using the word impossible - but lets just say it is prohibitively difficult to make such a tool work in 1.7.

The best workaround we have at present is for you to manually split the layout into 2 layouts, with half the files in each layout. Then you would add the layouts to a campaign and schedule that (or schedule the two layouts individually - they will cycle).

We could not fix the linked problem in 1.7 because the only way to fix it is to change the whole format of the schedule.xml file sent to the player by the CMS. We had to change from a comma separated list of dependants to having dependant nodes under the layout node. This of course means an updated player application as well.

Sorry I do not have better news or a better workaround.

Thanks anyway.
I really appreciate your work
Andrea

Hi Dan,
have you any news about this problem?
Because now we have to manually split the layout into 3 layouts,
everything becomes more complicated
Thanks
Andrea