..If you’re asking for BIAB to be a slave to play/stop commands, this isn’t advisable as we don’t (yet) support floating point tempos. So if the master tells us to play at tempo=124.54 , we can’t do it and tracks would be out of sync. It also wouldn’t work well as BiaB isn’t always ready to play instantly. It would also generally be a complicated feature to implement for us, many code changes and there is “lower hanging fruit” in that regard.
I realize that but thought you could change the playback % rate ??
And once you drag it into the DAW ACID will fit it.
I could understand if it's not generated the tracks already there would be a wait but it should start instantly to follow the DAW once the users generates beforehand.
I remember mine never started instantly until I removed the Bandstand.ini from bb\ root that was still there from years gone by.
If it's just Biab users using it with their DAW they are likely to be whole tempos as you can drag a midi from Biab to DAW to set tempo map.
Are the complicated code changes to do with the decimal tempos or just receiving the VstTimeInfo play/stop/continue ?