All Activity

@PeteGul Like this: Remember to enable Dolby Vision if your TV supports it.

Hopefully this answers the question. Here is a drill down all the way to Hercules (2014). As stated I was finally able to get it to work. In this case Emby was combining it with the Hercules (1997) film. I split the two then identified this one appropriately and the metadata was finally found. Then I refresh the metadata again and everything I uploaded after finally came through.

I just let them play, they are music videos, mostly live performances. Today I tested on the web client and didn't get any of the pop ups. Is there a setting in the system that might trigger it, such as length of the video itself? They run anywhere from 3 to 20 minutes. There has to be some sort of trigger as to when the pop up does show up. Based on my testing it seems to be totally random.

@bingbong69_ Installed Moonfin 2.5.1 on windows 10 ran fine the first time, test played media. Upon exit it would not load again, just a solid grey window. Removed app and deleted install directory, reinstalled same thing grey screen. Not sure why it doesnt want to work anymore. When it did work it was great, although not having the ability to frame rate match with refresh is a deal breaker.

@ebranything on this please

Yes, I receive warning, but no-ip tunnels only support DNS and HTTP.

Your panel is always showing in 4K (or it wouldn't fill the screen) so it is upscaling any other input it gets. I suggest setting your Shield to 4K/60.

So, on your browser, you get a big "unsafe" warning? Most browsers hate straight http these days.

Let us know how things go. Thanks.

I probably won't use it much out of network. I'll look into a VPN and tailscaoe. Thanks for the help

HI, for the next update to the Emby iOS app, we have registered 10 second skip forward/back as supported. We don't have any control over whether CarPlay will actually display the buttons but so far in the simulator it is. Thanks.

I think it probably shows for all videos (except the last) you just aren't waiting long enough for it to show. When it shows depends on the length of the video being played.

And that's the problem. Our current versions aren't for different parts or different editions. We have logic in each app to choose the version that best plays on the device so using them in they way you are is never really going to work out like you want. We have in our future plans to introduce the concept of "Editions" which would allow this type of thing.

But yes that does seem like a lot. Usually I hear people paying around $5 for it.

The alternative is having to setup a vpn or tailscaoe on your client machines before they can connect. If there are going to be a lot of clients, that $10 will save you the trouble of having to do that.

Okay, now I got what you mean. The point is that there are 4 separate TOCs - they are separate for a reason: The reference tocs are just gigantic and not really handy for browsing and even recognizing conceptual documentation topics from reference documentation pages. I agree that the whole entry to the site can be improved in a number of ways and we'll surely do at some point, but I also believe that we have the best and most comprehensive developer documentation in the competition and all you have to remember for now is to click "REFERENCE" to get exactly to the TOC tree you're indicating... Thanks a lot for your feedback. It won't get acted upon immediately, but be assured that it will be remembered once we'll be working on it again.

Thanks for everyone's help I have a cgnat, they want $10 a month to do it the other way not worth it,I was wondering because I tried everything a couple of times. Thanks for the help again

3.5.56 Core UI Update Only Core UI Changes from 26.0.18 to 26.0.19 Fix live tv setup screen showing blank on first run Fix black screen for av1 in firefox

Emby for Android 3.5.56 Released Changes 3.5.56 Core UI Update Only Core UI Changes from 26.0.18 to 26.0.19 Fix live tv setup screen showing blank on first run Fix black screen for av1 in firefox

Hi, this is resolved for the next update to Emby for iOS. Thanks.

Hi, this is resolved for the next update to Emby for iOS. Thanks.

Right now, from the root index.html I have to do the following (and remember, I dont work on this every day ), so Im doing this. Open index.html Click the emby SDK on the left hand side tree. Realize that was the wrong page.. Then I have to read the first block in "Whats new?" and find the Just take a look and see link, nope wrong again Then finally ill remember to find the "worth a look" and click that. Im simply saying, in the menu tree Emby SDK | - Emby Server .NET API | - Emby Server Rest API | - Rest API Clients | - Plugin Sample Code Would make finding the C# server api much easier

Not sure what you mean, to me it looks like the two are treated equally:

I see the confusion, Im taling the Emby.SDK/Documentation/index.html The home page for emby dev documenation, should have a one click way to go to the C# api, just as it does the REST API Clients

Understood — I'll test the next one the same way. Two things I measured in the meantime, in case either is useful before you cut it. THE JUMP THRESHOLD — YOUR LOG PRINTS IT I said the tail fails "after a seek", which is too broad. On 4.10.0.29, in a throwaway container with a synthetic 30-minute MKV, your own log says: 6-second segments: "segmentGap is 19 and max allowed gap is 4. requestedIndex=31" 3-second segments: "segmentGap is 11 and max allowed gap is 8. requestedIndex=16" 4 × 6 = 24, and 8 × 3 = 24 — the limit is 24 seconds of media whatever the segment length. Either side of it, with 3-second segments: jump +5 -> 200 after 19.8 s no restart: it attaches to the running transcode and waits jump +9 -> 200 after 31.1 s no restart jump +12 -> 200 after 5.6 s one restart So a short jump costs nothing; it is only when the jump forces a restart that the tail is a problem. Which is also why resuming an episode is enough to hit it — resume, chapter start and scrub are the same thing here, and all three are well past 24 seconds. If it helps you reproduce: on an idle machine the same request failed 10 times out of 16, and with two other transcodes running alongside it, 0 out of 16. YOUR QUESTION ABOUT THE TRANSCODE TEMP DIRECTORY You asked a while back whether the segment was in the transcode temp directory. Sampling it every 10 ms through a request that ends in 500: t+0.085 s ..._300.ts.tmp (0 bytes) t+0.171 s ..._300.ts (1,060,320 bytes) complete, named as your ffmpeg logs it t+0.215 s <- the response: 500 The file is on disk 44 ms before the 500 goes out. A second later: 10:58:51.721 EncodingManager: Deleting temp folder /config/transcoding-temp/8AA322 DirectoryNotFoundException: Could not find a part of the path '.../8AA322/...' which is why retries after that point answer 404. So the answer is: it is there, and then it isn't. No mechanism from me — I have offered three and measured all three dead. This is just what the server does, in its own words.