Just browsing I found this thread.
So some random comments.
The changelog for the releases is on github and pretty easy to understand
Each new ‘minor’ beta cycle seems to be about picking off a bunch of issues. Nowhere is it clear to the outside world what the major functionality / design objectives are for a given beta cycle. It would be nice if at the start of each cycle the major objectives for the next release were given.
I am one of the silent beta users. If I find something I will try to help the devs by reporting it. I know that using a beta it’s on my head and (sorry!) I have Plex as backup if Emby crashes, but I think despite my 99% silence it’s useful I’m there. I certainly would make the effort to report anything major.
Regarding the OP. I went the other way from Plex to Emby. A major part of that decision was the support forum. It’s just so blatantly obvious with Plex that even the structure of the forum is about monetisation. I know everyone has to earn a living but I really started to dislike the Plex culture. I really appreciate the different culture of Emby and want to support it.
Now I am here I think Emby is a clear winner in transcoding and remote bandwidth management. These are important things for me. Otoh I think the Plex UI is better especially for multiple servers and tbh I find the Emby UI a bit clunky.
Minor points for me: I only played with IPTV (be it the Roku side or the Hauppauge side) and my impression is that different design decisions impact the user experience. I think I probably agree with the Emby decisions, but I will find out more later in the year!!! If I ever bother to harden up my remote access I think Emby is better because I don’t trust that Plex system. Finally though Plex has better device support and better music support. I want to move my music library later so look forward to continued development there.
Edited by scb99, 19 June 2019 - 05:43 AM.