Page 1 of 1

Remoting with Ventuz 6 - Cue Errors

Posted: 14 Feb 2019, 12:40
by Meldur
Hello Ventuz Team,

I have a big project for a TV Station. 6 Machines with the current Ventuz version with 12 ports. I've wrote a tool using your Remoting SDK. When I try to cue a template, it works - take - works - clear - problem! After that also the cuing of other templates failes. The error message is:

Cue/Take/ClearGet DataItmes faild: Received TakeInfos are inaccurate (The separate takes of the machine returned different durations)

This only happens, if I have multiple machines in one cluster. If I have only one machine, it works. I also tried with the latest SKD samples, but the same.



Do you have any idea? We're a little bit lost right now.

Thanks,
Meldur

Re: Remoting with Ventuz 6 - Cue Errors

Posted: 15 Feb 2019, 10:22
by Karol
Hi Meldur,

are you sure that the projects and scenes on all machines are identical?

Best Regards
Karol

Re: Remoting with Ventuz 6 - Cue Errors

Posted: 15 Feb 2019, 10:41
by Meldur
Hello Karol,

yes, I'm absolutely sure. If using Director, it works but not with the SDK.

Best,
Meldur

Re: Remoting with Ventuz 6 - Cue Errors

Posted: 15 Feb 2019, 17:44
by Karol
This is weird because Director also uses the Remoting 4 API like Remoting Demo application.
Probably Director just ignores this error but I doubt that.
It could be somehow related to the take duration calculation but I have no idea how.
Do you have the same the same Format settings in the Region and Language configuration of Windows?

Best Regards
Karol

Re: Remoting with Ventuz 6 - Cue Errors

Posted: 18 Feb 2019, 14:29
by Meldur
I see, that the Remoting.dll from Director is newer than the DLL form the latest SDK but also with the new DLL I've got the same error. Because I'm just using the default project "Remoting 4" I think it's not a question of the implementation. It's allmost happen after the first take. If I cue two templates without a take in between, there is no error. If I'm using only one machine per cluster (so I'm using 3 machines with 3 cluster for testing), it works fine.

Any idea?

Thanks,
Meldur