Yeah, it's pretty simple. I'm using a beta build, that adds an automatic cps calculate & display, and better supports my workflow... don't know the beta has seen public release yet. I found I could live with Cadet's quirks better than those of kdenlive. Chief among the latter: because kdenlive is based on video, it insists on changing exported srt times, presumably to conform to the frame timestamps (of a non-existent video). This bothered me too much, maybe more than it should.
I don't specifically, though I do use utility programs and Excel to help calculate constraints and make decisions about -
inserting line breaks
when to use the new inline durationExtend option, and what value to give it
SRT instead of inline
Non-verbatim instead of verbatim transcription
For a given vocal set, it appears just a small number of bark clips need the SRT treatment (and so Cadet) instead of inline.
Another satisfied customer of buildSubtitleShaders.
I've got another console utility about ready to release, for group checking SRTs. Soon.
For me, this is an example of where it CAN fit in an inline, but should be placed in an SRT instead. I would definitely put the final phrase into a subtitle message, and at least consider breaking into 3 or 4 messages.
For The Wench, there were some clips (of 7 - 30 seconds) where she's idly humming. Rather than a single inline, e.g., "(humming long tune, hoarsely)" that stayed up the whole time, I went with srt, showed that message briefly, and then towards clip end showed "(humming ends)".