Oh boy, so much hate @CougerJoe ... I always appreciate honest and raw feedback, but calling someone manipulative and greedy is really top notch raw!
As I mentioned before in a much lengthier post, the tool is
free and
open source.
Thank you @Videoneth for taking the time to explain this once more.
We give early access to features to some of our Patreon subscribers for supporting this project, but all features are or will be pushed to the free GitHub page for everyone.
We're currently testing the newest 0.19.5 patch in our editing room and will probably compile a standalone installer this or next week. We'd really want to add another optimization before that, but let's see if it doesn't break too much of the rest of the code...
Videoneth wrote:I have a question, what's the expectations (generally speaking) in term of time when indexing a video? Let's say with a 3090
On a 3090, the video indexing should take around 1-1.2x the length of the video irrespective of resolution, but it really depends on the number of scene changes - the tool runs an advanced scene detection algorithm that is interested to see if new stuff was added to the scene.
iddos-l wrote:Why not use the built-in transcription of Resolve?
The tool is evolving in handling more than transcriptions.
For eg.,
you can do semantic search on text - search by topic, question etc.,
there's a direct interface to ChatGPT that includes timecoded contexts - just ask AI anything about what's being talked about in your footage (or summarize, or ask it to translate or explain concepts),
And we recently added the video indexing feature which allows you to find anything in your videos using plain English - see the video link posted by Videoneth above.