I am very happy with my Omada setup. It's an ecosystem, not a single device. I use an er605 as router and eap610 as AP. I also have a switch, probably you don't need that, and I now have an Omada controller (you can also host that in as a docker container, so not strictly needed). For wifi you can simply throw another ap somewhere and have excellent Mesh wifi. It's more complex than a simple consumer router, but also has a lot more functionality.
momsi
joined 1 year ago
Out of curiosity, why would that be a problem?
tried with transcoding disabled, no joy, still freezes. Subtitles were also disabled, I rarely watch with subtitles. Edit: I just noticed, when forcing transcoding by limiting the quality (Bitrate) on the client to lower values, it does not freeze
container is mkv, codec says AVC
Checked on transcoding, it happens on direct streaming....
Bitrate varies, some files work, some don't. Even in one season of a show episode 1 streams perfectly fine, episode 2 freezes every 2 mins.
Bitrate of a file is around 8Mbps, local bandwidth is 1Gbps.
How I'd go above this is dependent on how much storage you expect to be using mid term/until you want/can buy another drive.
Must have 7TB ? Swap the 10tb for 2x4TB, then do 4TB parity 4+2+1TB as Data drives.
Is 3TB enough for the time being? Keep the 10TB and use as parity, 1+2TB as Data drives. When full, go for up to another 10TB as Data.
That second option is more upgradable in the future.
I'm guessing everyone meant Data drives by saying "pool". In unraid, Data drives are the ones protected by parity, in the array. Pools are "out of the array", not protected by parity.
The controller does not need to run 24/7. The controller configures the devices and the config remains on the devices. Though, when your devices are adapted by a controller, you cannot access any settings on the devices themselves, only via the controller.
Maybe should add: depending on the network set-up, I'd strongly recommend getting a hardware controller. For me, I have one server hosting all my stuff. I also hosted the controller with docker in this server. Which ends up being a single point of failure, and no way to look into your routing if your server is down/unreachable. I got a hardware controller (oc200) eventually just to separate my interner and network infrastructure from my hosting and service infrastructure.