In older versions, it was possible to use LOADBG AUTO with growing files (for example during ingest or transfer to the playout storage).
Since ~7.3 it is no longer possible.
You can simulate growing MXF file using following command:
With 7.0a, the growing file plays to the end (although started during its creation) and then the server correctly switches to the color producer.
In later versions (tested 7.3a - I do not have any builds in between), Caspar switches to the color producer right after LOADBG command is executed.
I believe it has again something to do with duration reporting - 7.0a does not give you duration information of the growing file's duration until it's finished (which is expected).
In older versions, it was possible to use LOADBG AUTO with growing files (for example during ingest or transfer to the playout storage). Since ~7.3 it is no longer possible.
You can simulate growing MXF file using following command:
and then execute the following AMCP commands:
With 7.0a, the growing file plays to the end (although started during its creation) and then the server correctly switches to the color producer. In later versions (tested 7.3a - I do not have any builds in between), Caspar switches to the color producer right after LOADBG command is executed.
I believe it has again something to do with duration reporting - 7.0a does not give you duration information of the growing file's duration until it's finished (which is expected).