ZoneMinder Forums

Maybe it's the syntax of the flags? Do you need to use an intial + ? movflags=+something+somethingelse+theotherthing ? Or does ZM handle checking and correcting the user-input? Today I noticed, in shotcut (video editor) under the "Export/Advanced/Other" tab ... movflags=+faststart preset=fast So I ...

From a quick google -- ffmpeg understood movflags from version 3.X and 4.X you'd think it would be in your version. I just checked on my Ubuntu 22.04 system ... ffmpeg version 4.4.2-0ubuntu0.22.04.1 ffmpeg --help | grep movflag Nothing is returned, meaning it doesn't know about it. Hmmm. man ffmpeg ...

Would the explanation you provided also explain the errors shown in the log posted above or is that another issue? "failed: Connection refused" seems to be unconnected to the corruptions. Not sure exactly what that's coming from though, I'm not understanding whether it's zms failing to connect TO ...

IT could be as simple as the camera's highly tested, standards compliant H264 implementation falls a tiny weeny bit short of being compliant :) And that when ZM gets its hands on the wonky H264 and shoves it through FFMPEG to recode it as H264, that FFMPEG is a lot more tolerant to incoming-stream ...

I did not go for ext4. One doesn't want to jump on the new stuff until it's been thoroughly field tested, does one? :) I realise you are gently poking fun (I accept that!), but the serious answer is that at that time (2010) ext4 *wasn't* thoroughly field tested. I'm more than happy to let other ...

when first mkfs.ext3-ing my data partitions OK, I forgot your experience probably predates ext4 :lol: It really does ... I was using the default ext2 when I started (Slackware on 50 floppy disks, 1993 era), and when ext3 turned up it was basically "ext2 with journaling bolted on" so had no worries ...

dougmccrary wrote: ↑Sat Jun 15, 2024 9:46 pm Upvote...

except ext3?

From man: "tune2fs - adjust tunable file system parameters on ext2/ext3/ext4 file systems"

So yes, including ext3. Just because there's a 2 in the name, doesn't mean it only does ext2

Reserved block count: 3125725 I guess this explains it? At 4096 bytes (4k per block) that's 12.8E9 bytes, so close enough ... Also, 5% of your 237G is ... 11.6G -- and co-incidentally 5% is the default reserved block count. You definitely could recover most of that by setting reserved blocks to ...

Can you test with a provider other than gmail? Gmail have some very funny ideas about how email works, and have decided that they don't feel the need to create bounce emails when they don't like something you've done. They just eat the email without trace, without explanation, and without apology ...

I am not sure though, why its showing usage. root@ubuntu-tiny-3:/mnt/nvme-storage/zm-events# df -h /mnt/nvme-storage/zm-events/ Filesystem Size Used Avail Use% Mounted on /dev/nvme0n1p1 234G 32K 222G 1% /mnt/nvme-storage Used: 32K ? That will be because you created a directory or two. It's nothing ...

ENOTTY is correct. It's not a TTY. You are redirecting input from a file. So it's not a TTY. Sure, but I don't know why it's sending an lseek only when I do not have a tty. That is, when I use telnet directly I don't see any lseek calls. This is based on an example zoneminder script. I'm really not ...

Thanks. That makes this unusable for me, I don't want to have to depend on an external website. Time to get a "No Cloud Garbage!" T-shirt :D Remember, the whole point of most of these cloud cameras is that the manufacturers get to hold you to ransom, pay subscriptions, tie you into their products ...

Can you be a bit more specific? I have a nest camera, have gotten the rtsp-server installed and working, but not sure how to run ffmpeg, is it running as a daemon? Also, I don't understand what this is doing: -i https://stream-eu1-delta.dropcam.com/ne ... ZZZZZZZZZ Thanks in advance It looks like a ...

Ummm, not to state the obvious that I should have mentioned in the first place

ENOTTY is correct. It's not a TTY. You are redirecting input from a file. So it's not a TTY.

I don't suppose that is actually really an error, as such.

Maybe that's why it's a swap file now? Probably. There used to be an issue (chicken and egg, horse and cart) with using a swap *file* that lives in an encrypted file system, which meant you couldn't access the swap *file* early enough in the boot to restore from it. And by the time you could access ...