John:

Good Morning, and thank you so much!

I found your reply in the way-too-early hours when getting home after the Event, which had a social gathering afterward which was both successful and well-attended and just kept on going smile

By the time I got back I was on a direct line from door to bed as I needed to rise early today also, so whilst wanting to check here for any response I couldn't do anything to see what the result might be for me, and then leave a response accordingly.

So I am pleased to say I got the same results following the "Audio > render" pathway, thank you.

Though at the same time I am a little embarrassed as well blush because that should have occurred to me to look for anyway. But it didn't, and I suppose that at first I was just looking at my *normal* Export Song/Audio steps and alternative approaches and than getting buried by fault-chasing diligence in just that direction, by which time I was then too close to see sideways much at all.

I got around things for last evening with a tweak from Audacity to create the speed-up, though not exactly what I had in my head, well, to my ears anyway smile

Tonight however I will now be using the *proper* version! I know I will be asked to pass-on the thanks of all the others too, so do so very happily now.

The audio-drop still existed however on the couple of trials I just ran, and rigidly at 9'08" even if I falsely make the total runtime longer or shorter than its normal length. It doesn't therefore seem triggered by any compositional input.

I can't think why it happens, but fortunately the timing has worked out very well insofar as the speed-up has pulled the total run-time down to what it should be, and the audio-drop has landed literally a breath after the piece finishes, now at 9'07"instead of 9'33"without the tempo-changes ... couldn't be much closer!!

So other than a click in the immediate silence, which I can easily eliminate (though hopefully it would be buried beneath tumultuous applause anyway smile ) there is now no significant effect on the work itself.

Just before this reply, and before knowing precisely where the audio-drop would actually fall, I ran quickly down to the Venue to let everyone know that I would be using the original audio tonight and Wednesday ... I instructed the Company to dance louder as a precaution "in case it still clipped a couple of seconds", which raised some smiles once it was realised that was a joke smile

So, I am happy that it turned out to be simply (?) a glitch rather than senility or brainfade smile ... and yes I will report it to PG so it can be looked at and avoid someone else going in the same loop.

Is that just an email to "support@ ..", or is there a specific reporting procedure for this kind of thing? Direct to Peter G?

I'd like that audio-drop's cause identified at some point however just for peace of mind ... I have BIAB'd songs and tracks up to 12 minutes in the past with no such effect.

Though, on thinking about it I can't now be sure I actually exported or saved the song/audio on some/any of them, so maybe the condition is there just not encountered if I only played in/through BIAB direct ... or just saved the work as a sgu file anyway. I'll explore that in the next couple of days.

Again many thanks, and also to VideoTrack for your kind interest.