Nice default setting Scrypted

The default remote streaming bitrate, is 1000000, doesn’t say if that’s Kbps or what though. If it’s Kbps, that’s 1000 Mbps. They think it’s common to have 1000 Mbps upload speed?

Not in America, if using shitty Comcast, you get a whooping 10 Mbps.

I searched for packet loss for Scrypted, and they said to lower your remote bandwidth. If lowering the bitrate, doesn’t fix it, well you’ll have to guess what to do.

Search the console for the camera for “1000000” and find nothing. So don’t ask me what they do with that number. Multiply it by two perhaps? Nope, can’t find that either. Perhaps searching in a browser doesn’t work.

Copied it and pasted in a text editor, found “-maxrate 2000000”. So don’t set it to 6 either, if you have a 10 Mbps upload, the max you can set it to is 5, since it apparently thinks you have twice the bandwidth of the bitrate. I’ll set it to 3000.

You can easily test it, if your networks are isolated, disable firewall rule allowing access to the Apple TV or whatever is the home thing.

What’s funny, is on the cell network, everything is fine. The video likes pausing, if you get packet loss. Annoying.

And why does it need to transcode the low quality stream? Perhaps it’s set to. Medium resolution is, not low. Medium must be set to stream 2 as well.

I set the local stream to stream 2, because that’s the only way to change the main remote stream, otherwise it uses stream 1, must be hard coded. Didn’t fix it, probably because it’s transcoding the local stream, with more bitrate then the video has most likely, and the same format. Not sure what the point in that is. Guess you have to restart it after changing that setting, or you can’t change it.

The “-maxrate 2000000” is hard coded it looks like. So how do you lower the bandwidth then? No instructions are nice. Might as well ditch it, at this point.

Anybody know what “-maxrate” does? Well, the bitrate setting is useless, you can’t find 3000 or 6000 when searching the console log.

They claim it’s better then Homebridge, not for 10 Mbps upload speed. Thanks to it’s hard coded bull shit. “2000 kb/s” if that’s the case, what’s the problem? Oh right, it’s only 10 Mbps. That’s under 2000 kb/s. I should say “kB/s”.

How the fuck do you set that to a lower number? I guess you have to modify the source code. Switching to Homebridge is easier. Setting the transcoding max bitrate to 1000 doesn’t work either. I tried 100 in the past, I think it just reset to the huge number.

I think 2000 is set on the camera. I ain’t changing it on the camera, that works just fine for me. The videos that are saved to computer, look fine. The max bitrate is set to 2048 Kb/s on the camera.

It should work with the shitty stream, as the max is only 1024. And you have to apparently change it on camera, so no idea what the transcoding max bitrate is for. Adding -b:v 1M won’t do any good, you can thank the hard coded option that is after it.

Here you go. Maybe it’s only if you run in a container. If you put a k in the bitrate, it removes the k. And the workaround of restarting it right after, doesn’t work.

What database does it use? Going to edit the database file directly, or look in it. The extension is .ldb. NoSQL? SQLite? It needs a password, according to sqlitebrowser. Wonder what the password is. Not my user’s password. I shouldn’t have to brute force my own database.

If you want to fix it, the easiest way is to set the local stream and all other streams, to the low quality one, and disable transcoding, since you can’t change the max bitrate. Nice feature. Maybe the recording streams can be left alone, since I don’t use that, it’s all saved to my computer. Maybe if you delete all transcoding stuff and re add it, it’ll work right. That didn’t fix it, or maybe didn’t change the bit rate in the right place.

Well, I guess you could try rm -fr the entire folder and starting over. Not worth it.

“destination: ’local’”, too bad you can’t change that. I have no other WiFi to test it on. Maybe it thinks it’s local at her house too. In that case, good luck. Still local, using VPN.

You’ll have to edit the code to change what it thinks is local. Funny though, it’s connecting using Apple’s server, and it’s local.

And you have to upgrade to their NVR, if you want to fix it, or use stream 2, the lower quality one. Nice. It’s a money grab. All WiFi is believed to be local, and the bitrate is hard coded.

There is one other fix, run ffmpeg encoding the stream 24/7, or when it tries to access the encoding stream, but set it to whatever you want. You’d have to add it as a “camera” though. Might be a messy solution.

Now to see how much their NVR is. And maybe some other day, switch to Homebridge, since it might let me set the bitrate.

I just set the local to stream 2. That’ll fix it for now, looks like ass though.

Now you could fork the code, and allow that bitrate to be changed. Assuming it’s open source.

You do know I’m incredibly lazy though right? How much space do you get? Can’t even find pricing. $40 a year, but you store videos on your own computer. Not sure it’s worth paying for, just to be able to stream better quality.

But port forwarding is optional. I don’t trust it though, so only use the local part.

You might have to use the cloud thing to view your cameras remotely. Guess it doesn’t do HomeKit, with lower bitrates. Hmm, says it does on the main page after you login, so you don’t need their cloud.

You could make another VLAN, and put the server on it. Except, the Apple TV should be on same VLAN. And the drive I use is in desktop. You could still do it though. But too much work.

Maybe tomorrow I’ll pay for it, after I find out if I don’t have to use the cloud part. Or do the third option, custom ffmpeg encoding streaming. And add that as a camera. Not exactly a great solution.

But I can stop using FTP for the videos, if I get their NVR, and it can save as H265, cause I don’t want massive H264 files.