Earlier quoted context omitted.
reminds me of telling a friend: I hacked your system: file:///etc/passwd
There was a Userfriendly comic with Miranda telling some ‘hacker’ “my IP addy is 127.0.0.1, come get some”.
[dead]
Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
111–120 of 151 posts
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#112Earlier quoted context omitted.
We just got a modern example of the classic message from a friend who just picked up programming, containing: "I just created my own web app, wanna check it out? It's here: http://localhost:8080"
I've been getting this weekly from colleagues. It's very much an epidemic right now! And the port number is indeed almost always a random number between 8000 and 8100.
> I've been getting this weekly from colleagues. It's very much an epidemic right now! And the port number is indeed almost always a random number between 8000 and 8100.
Really? A bit hard to believe, unless you have many dumb colleagues.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#113Earlier quoted context omitted.
reminds me of telling a friend: I hacked your system: file:///etc/passwd
There was a Userfriendly comic with Miranda telling some ‘hacker’ “my IP addy is 127.0.0.1, come get some”.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#114This is great. I wish I had enough ram for a local model. I just spent the last few weeks writing something very similar, but I made it a local Electron app with Whisper, ffmpeg and I added semantic search and embeddings for chatting with the videos. It talks to Claude for the vision analysis, tagging and video chat. Do you only send one image for yours? I used a customised scene detection algorithm to find multiple…
Not one image - 5 frames per clip, sent in a single request with a transcript snippet. So the multi-frame + subtitles in one call part is the same as yours.
But yeah, how it picks the frame is the weak-point here. Scene detection would definitely help - this is #1 on the Roadmap.
Could you share how your scene-detection picks the frames?
---
For the vector search, I went for the trade-off of not having it but keeping it simple with plain Markdown files for more portability. The knowledge travels with the files when an SSD moves, no index to keep in sync, and plain text that outlives the tool. But the other path you mentioned is interesting as well to explore.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#115Earlier quoted context omitted.
I don't dislike those tropes because they are frequent or because they are not pleasing to read intrinsically. I dislike them because it tells me it was made by AI and AI output varies strongly in quality and most of it is low on insight but rings the right bells to make it seem insightful. It indicates a lack of human care. Hiding these clues by another AI pass doesn't solve the core problem. Now you just end up wit…
I feel like human copywriters have been using those same tricks for clickbait articles for years…
Sure, but the omniprevalence of LLMs just just crystallized these into clearly recognizable patterns. Just like cliches, but not being limited to simple phrases.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#116The post is a mix of human and AI writing and the AI-mannerisms get on the nerves. At least it has a clear topic and some actionable insights and code examples.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#117Earlier quoted context omitted.
They haven't: this is the top thread, and the entire threads is saying its unreadable and explaining step by step how to do the basics you should have done before you posted. I'm not sure why you're pleasantly surprised, I would have expected embarrassed, and taken down the HN post to get at least the basics down before sharing it under my name (if possible, dunno how HN submissions work)
Unfortunately will have to disappoint you, can't get embarrassed easily. In fact when all of this worked well locally, felt pretty proud ngl.
It's quite sad that you're feeling pride largely for your ability to write a prompt, and it's sadder that you're being snarky with someone who expects more from HN users.
Your behaviour is not affecting the HN community in a positive way.
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#118My take is that B2C AI applications are kind of structurally limited by how hard it is to build personalized context. The idea of capable local models could be a huge unlock here if they are able to do the bottom-up context collection research / tagging / etc. at scale.
I made a B2C AI app that's fully local (and free) to do AI based contextual file renaming. So if you give it a bunch of screenshots it will try and intelligently name them based upon what is in the screenshot. Same for videos, PDFs, etc. But to your point I haven't even tried charging money as it feels like something Apple is just going to bake in as a feature. https://finalfinalreallyfinaluntitleddocumentv3.com/
This is cool. And yeah love the name!
Are you planning to open source it? Or maintain it in the future?
Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#119Re: Indexing a year of video locally on a 2021 MacBook with Gemma4-31B (50GB swap)
#120This is great. I wish I had enough ram for a local model. I just spent the last few weeks writing something very similar, but I made it a local Electron app with Whisper, ffmpeg and I added semantic search and embeddings for chatting with the videos. It talks to Claude for the vision analysis, tagging and video chat. Do you only send one image for yours? I used a customised scene detection algorithm to find multiple…
Not one image - 5 frames per clip, sent in a single request with a transcript snippet. So the multi-frame + subtitles in one call part is the same as yours. But yeah, how it picks the frame is the weak-point here. Scene detection would definitely help - this is #1 on the Roadmap. Could you share how your scene-detection picks the frames? --- For the vector search, I went for the trade-off of not having it but keeping…
I originally limited mine to 10 frames spread evenly throughout the video, but it missed a fair bit of context at the analysis step, and didn't scale with length. So now when a video is loaded the app extracts a bunch of frames for the entire video, then calculates an image histogram and compares similarity to the previous one. There's some configuration so it doesn't send too many to the LLM, but still gets a good cross-section of frames to send.
You could also just use FFmpeg as it can do scene detection too. I tested both but liked the results from the histogram analyzer more.
Yeah, markdown works well if you're going to search through it with Claude Code or something like that. I built ClipScape as an Electron app with a local SQLite database, as I wanted an interface I could search and chat in and see the relevant thumbnails.