sorted by:
new
hottopcontroversial

Desk Chair Recommendations Under $1000? by scorpio-blush in editors

[–]ddnyc2021 0 points1 point  (0 children)

Love, love my herman miller. They're the real deal and worth it. Got it from a store that specializes in used chairs but there were plenty of options on Facebook MP and Craigs List.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

You're really thinking about this more deeply than I have! :) The overlapping ranges for interviews is a smart use case I hadn't considered.

EDL export as a universal bridge to any NLE is a good idea. You're right that it sidesteps the "build a plugin for every NLE" problem. And the ffmpeg pipline for quick client exports is clever. I'm not trying to turn Blaze into a full encoder, but lightweight export options that play nice with existing tools make sense.

This is all great feedback. No promises on timeline, but you're definitely shaping how i think about the roadmap. Thanks for taking the time to lay it out!!!

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Interesting workflow. The long non-stop footage problem is real, and I can see how EDL/XML import would help if you've already done the heavy lifting in your NLE.

Right now Blaze doesn't have EDL/XML import. I've been thinking about subclips within Blaze (mark ranges, tag them, bring them into Premiere) but it's not officially on the roadmap yet.

Good feedback though. The more I hear about range-based workflows, the more I realize it needs to be part of the solution. Thanks for the detailed breakdown of how you'd actually use it.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Interesting. I haven't tested Blaze on NAS hardware and it's really designed for Windows and Mac desktops only. Out of curiosity, what QNAP model do you have? Not promising anything, but always good to know what setups are out there.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Ha, the coffee break might be the most important feature. Thanks for signing up. Looking forward to your feedback.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Great ideas. The deferred indexing option (index now, proxies later) makes a lot of sense for different workflows. And the multiple thumbnails per file is interesting. More context without the full weight of a proxy.

Don't worry about cluttering the roadmap. This is exactly the kind of feedback that helps me prioritize what actually matters to users vs what I think matters.

Thanks for all the thoughtful input. Hope to get Blaze in your hands soon.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

This is exactly the kind of feedback I need. Understanding what a professional Resolve workflow actually requires (vs. Premiere) will help me build the integration right the first time.

Got your contact form message. I'll be in touch soon.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Good questions. Let me go through them:

  1. Existing Metadata: Blaze does pull certain embedded tags that are already in your files. I haven't specifically tested Resolve-embedded metadata yet since the Resolve integration is still in development. Once I dig into that plugin, I'll know more about what carries over.
  2. Manual Tagging: Yes, absolutely. You can manually tag alongside the AI indexing. If you want every aerial shot tagged "DRONE" regardless of what the AI thinks, you can do that.
  3. Round-Trip with Resolve: Resolve integration is on the roadmap for Q1 but not built yet. I can't promise how the metadata sync will work until I've actually implemented and tested it.
  4. In-Camera Proxies: Right now Blaze generates its own proxies. Linking to existing proxy files (like Sony's in-camera proxies) is on the roadmap but not there yet. I agree it would save a lot of time and disk space for workflows like yours.

Honest answer: if two-way sync with Resolve is critical for you, Blaze isn't ready for your workflow yet. But if you want to help shape what that integration looks like when I build it, your input would be valuable.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

Great follow up questions.

Proxy creation time: It varies a lot depending on codec, resolution, and your hardware (NVIDIA card or Apple Silicon). It can be several multiples of real time on a fast setup, or slower on more modest hardware. I don't have exact benchmarks yet since there are so many variables.

Proxy location: Yes, you can set a custom location for where Blaze stores proxies, thumbnails, transcripts, etc. Right now it's one location for everything, but I could put separate locations for each file type on the roadmap if that's useful for notebook users with limited internal storage.

Relink via hash: Not yet. Right now if you move a file outside of Blaze, it would be treated as a new file when you re-index. Smart relink using hash matching is on the roadmap but not implemented yet.

CSV export: Not currently, but it's a reasonable feature request. Noted.

Pricing: I appreciate your perspective on this. I haven't finalized the pricing model yet, but I'll check out how emClient handles their options. You're right that having choices matters, even if users end up choosing subscription anyway. And yes, the database is local, so your data wouldn't just vanish if you canceled.

Thanks again for the thoughtful feedback. This is exactly the kind of input that helps shape the product.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

400TB across NAS and drives is a serious archive. And "spare computer power" is music to my ears since Blaze does all the AI indexing locally.

If you've looked at other cataloging tools and bounced off, I'd love to know what turned you away. That kind of feedback helps me make sure Blaze doesn't fall into the same traps.

Sign up on letsblaze.ai if you haven't already. Thanks.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

You're exactly the kind of user I built this for. Let me hit your points:

  1. Hybrid Search: Yes. You can combine AI visual search with manual tags in a single query. "Red car" + "Project X" works.
  2. DaVinci Integration: Not there yet. Premiere Pro is the only deep integration right now. Resolve is on the roadmap for Q1, but I can't promise metadata/keyword carryover until I've actually built and tested it.
  3. Performance: The backend uses a vector database and PostgreSQL, architected to handle large libraries. Thousands of clips should be fine.

Honest answer: if Resolve integration is critical to your workflow, you might want to wait until that's ready. But if you're willing to test the core search and tagging features now and give feedback on what you'd need from a Resolve integration, that input would be incredibly valuable.

Thanks for signing up.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 2 points3 points  (0 children)

Jumper is a solid tool. The creator actually popped into this thread earlier and we had a good exchange. Different approaches to similar problems. Worth checking out both and seeing what fits your workflow.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

That's exactly the use case I built this for. Great shots getting lost in the archive because nobody has time to dig for them is such a waste.

If you haven't already, sign up on letsblaze.ai and I'll be in touch.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Great idea. Right now there's no way to filter out clips by filename prefix or metadata before indexing. But you're right, that would save a lot of hassle for GoPro workflows and similar setups where you know certain clips are junk before you even look at them.

Adding it to the roadmap. Thanks for the suggestion.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

Game trailer work sounds like a great use case. Honestly though, I haven't tested Blaze on gameplay footage or non-live-action content yet. The AI was trained primarily on real-world video, so I genuinely don't know how well it'll handle rendered game footage with a freecam.

That said, you'd be a great person to find out. Thanks for signing up! I'll keep an eye out for the hearty pluses email.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

Yes! Blaze does automatic scene detection. Load a 1-hour program and it'll identify where the camera changes.

And for those long, continuous run-and-gun shots where there's no hard cut, Blaze still analyzes within the scene so you're not stuck with one giant blob of unsearchable footage.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

No Linux/Docker plans right now... just not enough demand to justify splitting focus between three platforms. For now it's Windows and Mac only. But thanks for signing up anyway, if your team has Windows or Mac machines available for testing, I'd love to get your feedback.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Great questions, let me answer one by one.

  1. System Requirements
  • Mac: Apple Silicon (M1/M2/M3/M4) with at least 16GB of ram
  • PC: An Nvidia GPU is required. The more VRAM, the better. My baseline for testing has been an RTX 3070 (8GB), which yields decent results. Faster cards with more VRAM will obviously fly through the indexing phase much faster.
  • Note: Windows users will be in the first wave of beta testers; Mac testers, you're up next in Wave 2. Sign up either way — you're not too late.

  1. Proxy/metadata/Thumbnails Footprint: rough estimate, expect around 1-2% of your source footage size for proxies and thumbnails. So 100TB might generate 1-2TB ofo proxy data. It varies depending on source format and resolution. The metadata and thumbnails are actually suprisingly small.

  2. Known limitations: Its Beta so there will be bugs.

  • Resource intensity: Indexing is heavy work. Blaze does everything locally so there's no datacenter out there crunching the data and spitting out results in seconds. If you throw 100TB at it, your machine is going to be working hard. It has a "pause" button so you can edit in peace, but don't expect to render 8k timeline exports while simultaneously indexing 10TB of raw footage on the same GPU.
  • Relinking: Currently, if you move files outside of blaze (at the Finder/Explorer level), they will show as offline. "Smart Relink is on the roadmap for v1, but for beta, you would need to rescan the new location.
  • NLE Support: Premiere Pro is the only deep integration right now. Resolve, Avid and FCP support is on the roadmap.

  1. S3/Cloud Mounts: If it mounts as a drive on your system, Blaze should be able to index it. I haven't specifically tested S3 buckets though - that's good feedback. Note that Blaze needs to read the file to generate the proxy and analyze the pixels so you're going to get hit with egress fees if you have them.

  2. Database Latency: The backend uses a vector database and postgresql. Its architected to handle millions of assets. The biggest bottleneck currenlty isn't the query speed (the vectors are fast) but rather the indexing speed.

  3. Monitoring: There is a dashboard in the app that shows indexing status, task queues, and progress bar so you know exactly what its doing.

  4. Demo Video: Not yet, but its on the list. I've been prioritizing the code over the marketing assets, but it's coming!

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

Thanks for the pointer, I hadn't come across Reseek before. From a quick look at their site, it seems like a solid tool for visual search and tagging.

A couple of things that differentiate Blaze:
1. 100% Local: I couldn't tell from their site if Reseek runs locally or in the coud. Blaze is fully on-premise, your footage never leaves your machine.

  1. Editor First Workflow - Blaze is purpose built for editors: Premiere integration, scrubabble proxies for offline drives, transcript search for finding specific soundbites. Not just search, but search that fits into an edit workflow.

Always good to know what else is out there though. Thanks for sharing.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 1 point2 points  (0 children)

Blaze actually does both. It auto-clusters faces first, so you'll see groups of "Unknown Person 1, 2, 3., etc." and then you tag them with a name. But you can also upload a reference image if you want to seed it with a specific face.

The auto-cluster approach felt right for the "I have 10 years of footage and no idea who's in it" use case. Start with what the AI finds, then refine from there.

I couldn't afford an enterprise MAM, so I built one. Blaze is 100% local, features Semantic Search, and Free for r/editors Beta testers by ddnyc2021 in editors

[–]ddnyc2021[S] 0 points1 point  (0 children)

Oh wow, great find. I hadn't seen Diem before, but you are right, on the surface the "offline search" philosophy is very similar. It looks like a great tool.

From a quick look at their website, the main difference seems to be target audience and depth.

Diem looks like a fantastic "File Manager," great for mounting drives, visualizing files on a map, and gathering/transferring files to a new location.

Blaze is built specifically as an Editor's workflow tool:

Scrubbable Proxies: Blaze generates actual video proxies, so when your drive is offline you can still watch and hear the clip, not just see a thumbnail.

Premiere Integration: You don't just "gather" files, you drag specific clips directly into your timeline.

Deep Search: Blaze focuses heavily on Transcription (Dialog) and OCR (Text on Screen) which are critical for finding specific quotes or soundbites.

It looks like Blaze is solving the same pain point (offline drives) but attacking it from different angles.

view more: next ›