All Activity

I just been using safari via web for now till the update.. don’t want another paid 3rd party app

I can't remember but I think the community rating is IMDb. It's taken directly from Emby.

Like I said before a few times in this thread my Roku Ultra is going to be at best a backup device for my home theater. The 2019 Shield does everything equally well then the Roku but most of the time even far better. Playing lossless audio is a bonus plus with custom launchers I don't have to look at all the home screen advertisement for a device that I bought outright. Glad this came up because the constant advertising on the home screen which could not be disabled started to bug me.

Unfortunately the experimental HEVC encode is not working properly. This results in the "no compatible streams" error when emby attempts to use HEVC. As far as I can tell there are no errors, but the issue is that the playlist files are not written fast enough and after 10s emby force-aborts ffmpeg. During playback attempts (observed with multiple playback devices trying to use HEVC), Emby repeatedly starts short-lived HLS transcode sessions for the same item. Each session: Initializes a new ffmpeg transcode job Begins segment generation successfully (HLS .ts segments are created and written and files grow) Processes are then terminated externally by Emby (Stopping ffmpeg process with q command) and replaced by another identical ffmpeg process a few seconds later x265 itself reports x265 [info]: HEVC encoder version 4.1+1-1d117be x265 [info]: build info [Unk-OS][clang 14.0.5][64 bit][noasm] 8bit x265 [info]: using cpu capabilities: none! So that explains why the transcoding is so slow (it's a 13 year old CPU). But there are no errors, the first stream just gives [... SETUP ...] 23:37:46.224 Side data: 23:37:46.224 cpb: bitrate max/min/avg: 3872000/0/3872000 buffer size: 7744000 vbv_delay: N/A 23:37:46.224 Stream #0:1(kor): Audio: aac (LC), 48000 Hz, stereo, fltp, 128 kb/s (default) 23:37:46.224 Metadata: 23:37:46.224 encoder : Lavc59.37.100 aac 23:37:46.225 subtitle input filter: decoding size 384x288 23:37:46.226 subtitle_kickoff: resend - pts: 292 23:37:46.226 subtitle_kickoff: call subtitle_resend_current 302 frame->format: 3 [... END OF SETUP ...] >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown >> ThrottleBySegmentRequest: Latest request position unknown When I disable experimental HEVC encode support, it switches back to x264, and everything works, and x264 reports: 23:43:11.257 [libx264 @ 0x850806400] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2 So could it be that the main issue is that the x265 that is statically linked in emby's shipped ffmpeg is compiled with no optimizations causing timeouts?

Hello. They are internal subtitles in SRT format muxed inside a MKV container. I just tested on my PC and the option is there but it is not on Emby for AndroidTV.

Hi. Click that little red heart... You had previously chosen to only show favorites.

Hi. Were these internal or external subs? The delay is only implemented for external text subs.

Hello Guys, I went to watch a movie last night and I noticed that the subtitles were a few seconds out of sync with the audio. I went into the subtitle section and found that section to make adjustments in subtitle display time was gone. I know I'm not crazy because I've used it before, it used to have a - and a + to increase or decrease the timing. Did this get removed? I went back to the latest release 2 days ago because I had issues with the latest Beta. Thank you.

I finally got the plugin to do what I need. I have a question, will a future release support imdb ratings?

I have decided to edit the files by removing ( , ) & [ , ] in order to have them accepted, by the current emby format. So we can close this discusion.

Working for me...

they are video files, mainly home movies and ads where my son/grandaughter starred in that were done over the years. The setup in them did work fine along time ago with emby.

Here are some screenshots first from Roku, for default user, and then from web incognito using same user.

Well that was odd, was doing a bit more testing and the old dots were working Whilst the newer dots give the audio not supported error. I tried a reboot to no luck, then one started working and then the other... Either some sort of cache? or emby's awareness of device capabilities was perhaps part of the issue and was fixed whilst i was testing....

From the homescreen library row I can click playlist and see all the playlists on my end. Can enter them all. Everything normal. Clicking playlists from which view/screen? If you show a screenshot will understand what you mean and try to reproduce and fix this.

Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. Thanks!

OK. The addresses that Emby displays are the actual Emby Server addresses. What you see in the browser address bar in your screenshot is when going through the TOS app.

Edit what files exactly?

Nice plugin I like it.. Any plans to add in an option to force re-detection of intros? There's an option for Detect Credits, but really need something that can force intro re-detection.

My Roku Ultra 4802X connected via HDMI to a Denon receiver offers Passthrough, and it correctly detects what the receiver can accept. I think this became available with the 4800 series, I had the Custom audio settings configured with my older model Ultra.

Bon bhe aujourd'hui la conexion par l'ip lan ne fonctionne plus "Accès local (LAN) : http://10.23.214.246:8096" Je ne comprend rien c'est pénible

Does you chosen metadata providers, provide Episode genres?

Digital output format would be what you want to change. A RokuTV device will show "Passthrough" as an additional option for digital output format. A Roku set-top-box or stick will need to use "Custom" and then enable DTS or not and choose the correct flavor of Dolby Digital either non-plus or plus. The "Passthrough" option of the RokuTV will allow the HDMI(-ARC/eARC) to pass these through. Using Auto it must determine support from the HDMI-CEC chain. If you have an AVR this might cause problems with auto-detection if the AVR is turned off, but the Roku is always on, as the order the devices are turned on matters. Detection is done as the Roku boots up. In order for Auto to work correctly all the time the Roku will need to turn off with the AVR and turn on with it. Using Custom will work correctly all the time without needing to make sure of the order of devices is turned on correctly. Audio mode allows you to quickly enable Stereo without goofing with the other settings. For when you want to do this. Preferred streaming format isn't really used by the Emby app. We aren't providing streams without multiple audio tracks. We don't provide your media. So we don't read this value from the Roku which would tell us how you want your audio packaged from our content delivery network. Since we do not have a CDN serving video this one exists for everything else, but Emby. Those who have content will surely use this to determine how best to handle your audio stream delivery. Since Emby is limited by what your media item has for audio this is why we can never use that field.

Sneak peek at the next update! Packed with dynamic studio logos (like Netflix and Prime Video), the ability to upload your own custom studio logos, and other new features. Coming soon.

My AVR plays ALL lossy DTS audio tracks thrown at it by the Roku. But just lossy DTS the Roku passes on and the front display of the AVR says DTS and no transcoding takes place. As soon as the Roku plays DTS-HD MA audio, Emby is transcoding it but ONLY when it is 5.1 NO core from the DTS-HD MA. This came only to my attention recently as the 2021 movie black widow also has a DTS-HD MA 7.1 audio track and no problems were detected a few years ago when I played it. The Roku is connected via HDMI to the AVR and the AVR connects directly to the Projector. 2 days ago I connected the 2019 Shield to a separate input and every content that I play displays on the front of the AVR the default audio format DTS-HD MA, Dolby Digital, DTS, TrueHD and whatever else. So all the movies we have listed here play the highest quality of audio when using the 2019 Shield where the Roku screws up. For the Roku's Audio it has 4 entries. 1. Audio Mode: It has 2 entries: Stereo | Auto (DD+, DTS-HD) 2. Preferred Audio Language (English) 3. Preferred Streaming Format it has 3 entries: Auto | Dolby | DTS 4. Digital output and it has 3 entries: Auto | Stereo | Customs. Under customs there is Dolby Digital and DTS. Nowhere is there anything regarding passthrough but I assume the Audio Mode Auto will pass through the audio format. Regardless of the changes in the settings the DTS core is not handed over to the AVR. I am off for the weekend and will not be where the equipment is.