Ability to loop a call-cue cue

[d_korman]

I'd like to be able to loop a call-cue cue. Why?

Well, currently I am doing a show that requires the Westerkerke in Amsterdam to strike a number of different hours (answers on a postcard, no prize ).
I have a sample of a single strike which I can use to build each cue by copy and paste and then changing the number of loops, but then I have to set the level of each copy separately if the director wants them changed. It would be quicker in the tech if I could just set up a single callable audio file cue with the loop points, levels etc. set and have the number of times to loop as a passable parameter from a call-cue cue. Then I just have to set the level of the callable cue once.
Of course, that also requires the ability to pass parameters from call-cue cues to the callable cues - a bit like passing parameters to a subroutine. I guess that would require callable cues to have the capability of specifying which of their fields were to be passed as parameters from the calling cue.

Cheers.

[Mike Daniell]

We are planning to provide the option to include parameters in 'Call Cue' cue types - see Arguments for Call Cues. Other cue types that will be able to use such parameters will increase over time, but I'll note your request to allow the Audio File Cue 'number of loops' property to be set by a Call Cue parameter.

[d_korman]

Thanks Mike,

I'd seen that request but had forgotten!

An idea for eventual maximum flexibility (not sure if it's feasible or too fiddly to code....) ......provide a tick box by each parameter in the callable cue that, if ticked, makes that parameter symbolic (i. $1, $2 etc) for that cue. You could fix the order e.g. Start point, end point, fade in time, fade out time might be the first four parameters for an audio file cue. If the tick box for fade in time was the only one checked, it would be $1 in the calling cue. If the boxes for start point and fade in time were checked, then start point would be $1 and fade in time would then be $2, etc.

Initially just a fixed set of parameters for each cue type would be fine, as we could pass null value for those that we wished to be fixed in the callable cue - but my experience is that it's very easy to get the number of commas wrong when passing null values!

Regards

Dave