Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. jasonmcroy

    Atrium — a native tvOS app for your Emby server

    I can confirm the Next Episdoe button is now behaving.
  3. Im having problems accessing my emby account thats attached to my server. I originally never had one and the ones that would have been it, doesn't work. I tried to recover everything but its not showing in the directory thats giving. This server is on the Nvidia Shield Pro and everything was working fine until this happened... I also tried to make a new account and that didn't work either, it just put me in a constant loop to where I have to sign in and the password doesn't work. Is there a better link, better instructions or even a way to start from scratch, this is very frustrating and this is the only way it seems to get a hold of you. Thank you and I hope your able to help.
  4. lcasadonte

    Verizon Fios killing my CableCard: Options? Ideas?

    Well I hooked up an hdhomerun flex4k with the atsc 3 tuners and after a great deal of messing with cables, was able to dial in over 80 stations, so short term significant success with this. I'm still curious if my old verizon equipment is going to die with this change too.
  5. Luke

    LDAP Plugin, Download validation failed

    Hi, I'll push another one just in case there's an issue with it.
  6. I am attempting to install the LDAP plugin, but the installation fails (see attached log). I am able to install other plugins successfully (e.g. CoverArt, Statistics). I noticed that the plugin's Revision History shows the latest version, 1.0.45, as having a release date of 2026/08/29. That seemed off to me, as that same version was referenced in the solution to another user's issue back in November of 2024 (see provided link). Perhaps the update from 8/29 was meant to be a 1.0.46 release but someone failed to update the revision number and now the back end is confused? embyserver-63924128170_anon.txt
  7. lbkBrad

    Fresh New Look

    from the images, I think it looks nice. I do agree about preferring dark theme. I'm usually only in the web interface for image/metadata work, checking watched date, or editing collections. so I might not see it a whole lot (unless of course some client UIs follow this)
  8. Teddyknuddel

    Direct File Access - Exoplayer

    I brought this up years ago. But it keeps getting ignored.
  9. Today
  10. Luke

    Direct File Access - Exoplayer

    Hi, I think you mean SMB support? I would not say that it's being rejected.
  11. vdatanet

    Necesito un servidor

    Aquí te explican como armarlo: https://emby.media/support/articles/Quick-Start.html
  12. Teddyknuddel

    Direct File Access - Exoplayer

    Why is direct file access being rejected? Why are they so keen on Exoplayer when there are better solutions available?
  13. Luisfredo

    Necesito un servidor

    Necesito un servidor
  14. Lessaj

    New Emby for Android 3.5.45 Released

    I think there's room for compromise here, perhaps it shouldn't show until ~2-3 seconds have elapsed without a connecting being established. It's understandable that it may take some time to load some assets after establishing the connection, which the regular spinner can handle, but if genuinely still waiting for a connection to be established then it should display after that period which you can then cancel.
  15. Actually, if you want to talk about direct file access, I will be happy to discuss it in a thread dedicated to that. And I'm sure ebr will as well. But when I come in this thread, my priority is for PeteGul and his resolution matching issue.
  16. I’m out. Whether I bring it up in a new thread or not – which I’ve already tried – nothing’s going to change anyway.
  17. FrostByte

    New Emby for Android 3.5.45 Released

    I'm not quite sure of the point here. I've never asked for it to be removed and think it's a nice addition for those who need it. However, if your connection is so fast that the logo appears and then a popup is displayed and disappears before you can even read it before the home screen is shown then it isn't really necessary to make it show in the first place and just confuses people.
  18. That's what I said in the beginning Every time we (devs) come back in here, we look at the thread title to refresh our memory, and we expect to be talking about resolution matching.
  19. ..
  20. @PeteGulis right — this has nothing to do with the app not detecting the resolution correctly.
  21. Luke

    New Emby for Android 3.5.45 Released

    Only if the connection succeeds between 300ms and 600ms will it slow it down and hold it until 600ms. Anything quicker or slower and it will not add any additional time.
  22. crusher11

    New Emby for Android 3.5.45 Released

    I'm also pretty sure it's actively slowing down the startup process, because there's a minimum time for the message to display that's longer than my normal connection time. It looks like an error message, and there's not generally enough time to properly read it and figure out what's going on. It's incredibly annoying.
  23. Why? It’s the Exoplayer itself that’s the problem. Direct File Access, or a different player, would sort it out.
  24. Please make your own thread about direct access. Even if it is slightly in the lane of my first question.
  25. Luke

    Trailer naming?

    Hi, older versions might have just grabbed the trailer file name. Newer versions base it on movie name, so it depends on when it was imported into your library.
  26. chowbok

    Trailer naming?

    Not a big deal, just curious: when Emby shows a trailer for a movie, where does it get the name of the trailer from? It doesn't seem to be derived from either the trailer's filename or its embedded title.
  27. richt

    Hardware Transcoding Failing - TOS7

    @LukeYes! This has not changed at all. New logs attached. 16:14:32.573 [h264_qsv @ 0x2fd776c0] Selected ratecontrol mode is unsupported 16:14:32.573 [h264_qsv @ 0x2fd776c0] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters. 16:14:32.573 Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height 16:14:32.574 [aac @ 0x2fbc5180] Qavg: 157.327 16:14:32.574 [aac @ 0x2fbc5180] 2 frames left in the queue on closing 16:14:32.574 [aac @ 0x300ee880] Qavg: 324.867 16:14:32.574 [aac @ 0x300ee880] 2 frames left in the queue on closing 16:14:32.574 Conversion failed! 16:14:32.574 EXIT embyserver.txt ffmpeg-transcode-8425b3a3-1cf9-4e32-9b8b-531d57774594_1.txt hardware_detection-63924135176.txt
  1. Load more activity
×
×
  • Create New...