Switched from tl;dv to Sembly. Regretting it due to the 45-minute processing limit.

Hey everyone, I've been a long-time lurker and occasional poster, usually sharing HubSpot workflows and campaign automation stuff. But today I need to vent and get some advice because I think I made a major platform switch mistake.

So, for context, I've been using tl;dv for meeting notes and transcriptions for our sales and marketing syncs. It was working fine, but I was enticed by Sembly's promise of more detailed AI insights and the integration ecosystem. The workflow of having meeting summaries automatically pushed to our Slack channel *seemed* perfect for keeping everyone aligned without extra steps.

Here's my big, painful issue: **Sembly has a hard 45-minute processing limit on its recordings.** This wasn't glaringly obvious during the trial, but it's become a massive operational blocker. Our weekly deep-dive marketing strategy meetings, our cross-functional campaign post-mortems, our agency check-ins—they all regularly run 60 to 90 minutes. Now, I'm stuck manually stitching together recordings or, worse, having to choose which 45-minute segment gets analyzed and which gets lost. The summary and action items are completely fragmented.

Compared to tl;dv, which handled our 2-hour quarterly planning sessions without a hiccup, this feels like a huge step backward. I'm spending more time managing the tool's limitation than benefiting from its insights.

Has anyone else run into this? I'm specifically wondering:
* Did you find a workaround within Sembly, or did you have to adjust your entire meeting culture?
* For those using Sembly successfully, are you just ruthlessly keeping every meeting under 45 minutes?
* If you left Sembly for this reason (or another), what did you switch to? I'm looking at Otter and Fireflies again, but integration smoothness is key for me.

The promise of AI meeting assistants is to save time and create clarity, not add another layer of manual work. Really hoping someone in the community has navigated this before I have to go back to my team and admit the switch was a flop 😅.