A: reap and Opus share some similarities in that both help turn long-form videos into short, social-ready clips using AI. However, reap is not a direct clone or competitor — we’re building a broader creative platform.

Here’s how reap stands out:
• AI-first editing: reap is designed to evolve into a full AI-powered editor, not just a clipping tool.
• Creator-focused roadmap: We’re working toward features like AI voiceovers in clipping and captioning, full video captioning, and even creator personas.
• Community-driven development: Many of our updates come directly from user feedback — and we ship fast.

That said, we’re aware of current limitations (like clip trimming and subtitle accuracy) and are actively rolling out updates to address them — including better clip endings and more clip generation options, landing in the next few days. We appreciate the comparison and welcome the feedback — it helps us build something truly useful for creators like you!

---------------------------------------
To @wilde-olaf concerns:

first of all, I’m really sorry for the experience you’ve had so far. I totally understand where you’re coming from. I also appreciate the time you took to break things down — that kind of feedback is honestly gold for a small team like ours.

Let me start with something important: we’re not trying to be a one-to-one Opus clone. We’ve seen the comparisons, and yes, we’ve even acknowledged them in comments before. But we’re walking a different path — we’re building something bigger. Clipping is just the first step.

Now on to the issues you brought up:

Clips cutting mid-word:
The improvement is only its way and should go live in the next 48 hours. It wasn’t a limitation — it was an intentional decision early on, meant to keep the workflow clean and avoid abrupt cuts. But we’ve heard the feedback loud and clear. You’ll see a difference very soon— trust me when I say this programmatically it was basic check (if AI suggested sentence is in the middle slide to the last ended sentence or previous sentence)

Number of clips — we deliberately held back.
We only showed highlight-worthy moments instead of flooding you with every possible snippet. But we get it now — sometimes, more is better. The next update will reflect that. You’ll get the full spread, like how other tools approach it. We just wanted to avoid overwhelming users with noise, but we’ll trust you with the control.

Subtitles — if the issue happened in English, that’s fully on us. We’re using the same top-tier transcription backend most tools do, but if something slipped through, we’ll dig in. For other languages that have less data-sets, we’re working on fine-tuning and adapting (same is the limitations with others) — it’s a known challenge, but we’re committed to improving it. For English we will make sure its preciser than anything you have used.

And just to give you a bit of context — we’re not just building a clipping tool. What we’re working toward is an AI layer that lets creators drop in a video and walk away with captions, clips, and eventually full content drafts — all tailored and intelligent.

We’re still early, but we’re building fast. Every comment like yours shapes what we do next. So thank you. I hope you’ll give us another shot once the update is live — but even if not, you’ve already helped more than you know.