Thanks Bot!! that was awesome.
vatw
joined 1 year ago
I might violate your top "ideal solution" checkmark, but I have a raspberry pi running Motion Project (https://motion-project.github.io) on site and it makes an easily viewable webpage-stream. My Rpi4 can handle 2-3 video streams, with motion detect-video-save, periodic snapshot, etc. etc.
Not for the feint of heart, but it is the way I solved a very similar problem. I'm using random mixed brand of IP Cams, whatever was cheap at the time.
For what it's worth, NFS in my experience is also faster. I had a very similar use case (but QNAP instead of Sinology) and switched everything over to NFS and saw performance gain. Little things like previewing IP Camera security footage would feel slow on SMB, but snappier on NFS. I'd gotten over the user thing, but the speed is why I switched.
I did eventually wipe QNAP's software in favor of stock Debian -- but the prevailing wisdom seems to say Sinology's OS is pretty good.
I was wondering about this. What is the right etiquette? It’s not the same as multiple channels on the same server. But at the same time - supply side? Or consumption side?
Should clients filter them out? Do we need a way to “merge” on a per post basis?(or link or relate or…)
It is an interesting concept to ask. I don’t have a good answer.
Wow.
Did you actually change anything when it wasn't working in the middle there (Apart from what chatGPT suggested)? was it enough to just say "Nope. still not working"?
That is amazing.
I love the idea of tossing some yaml in and saying 'please help me fix'.