All Activity

Hi. Have either of you been following the beta? I'd say there are some major feature updates in the immediate pipeline.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, please try Emby for Apple TV 2.0.7 and let us know how that compares. Thanks.

Hi, what time was this example?

HI, this will be resolved in Emby for Apple TV 2.0.8. Thanks.

Hi. They are already there...

Why? The issue with this is someone has to put the infected file onto your server, and then has to wait for ffmpeg to do it's thing, and even then, Emby is apparently not RCE capable. If you're not getting your files from questionable sources, and doing it all yourself, you really have nothing to worry about. I remember when everyone was freaking out back when there was the subtitle exploit, and people blew it out of proportion. You could fully RCE a system with en embedded subtitle, but again, if you weren't getting your files from sketchy sources, you had nothing to worry about.

Pixel, size, sorry. if you zoom in my picture you see that the covers are to small. that's just ugly... and is probably an easy fix?

Hi, what do you mean by adding some px?

Sounds like something a tool could be developed for but not really broadly applicable such that it should be a part of the main interface.

For those that do not want to wait - You can possibly just replace the ffmpeg from the beta. I would suggest keeping a copy of the stable ffmpeg to rollback if this does not work, but it would seem unlikely that a newer ffmpeg would fail to work with the stable codebase imo. Beta source here - just extract the ffmpeg from the zip's etc - do not replace ALL the files ! https://github.com/MediaBrowser/Emby.Releases/releases/tag/4.10.0.16 Try at your own risk - I have not tested this.

Hello everyone, As we move closer to the end of the Ear Wax beta program, I wanted to take a moment to share the Ear Wax development roadmap with you. Ear Wax has come a long way since the beginning of the project, and development will continue after the public release. The goal of Ear Wax—and the lane it will stay in—is simple: to let you listen to your personal music library on your Alexa-enabled speakers using consistent voice commands, regardless of which supported media server you use. Ear Wax is designed to complement Plex and Emby—not replace them. Its purpose is to enhance voice control of your personal music library while allowing Plex and Emby to continue doing what they already do well. Going forward, there will be two editions: Ear Wax – Free Ear Wax Select – Available through a small monthly subscription. Rather than describe every feature in detail, I’ve attached a feature comparison spreadsheet that shows what’s included in each edition. Thank you all for your assistance during the beta. Your feedback has helped shape Ear Wax into what it is today, and I look forward to hearing your thoughts on where it goes next https://global.discourse-cdn.com/plex/optimized/4X/c/8/a/c8aaa96888fd20fe623b9c178a167d01a61d595c_2_690x446.jpeg

Pushed into the latest beta and not as a hotfix is really disappointing. Regardless, thank you for the fix.

Is there a plan to add back the previous functionality to limiting refreshing internet channels to only new/added links? Each refresh takes 10hrs to reprocess 500k+ links when only a handful are new. I feel a little guilty of all the carbon emissions that are created with each refresh.