Search the Community

Downgrading from beta to stable release is not supported and will likely break. Too many backend changes that are incompatible. You don't need to compare the servers if you installed them the same way. The idea is to find out where the files are located by default so that you can get the logs from the failed one for evaluation. Unless you deviated from a typical installation those locations should be the same on both servers. I haven't used the snap package and don't know if they differ or how.

Hi, Many thanks ofr taking time to try to answer my question and solve my problem. I tried to do what you said but unfortunately (as I expected) it does not work. Because : - 1°) I can not even launch the server on second computer, so I can not compare set ups ; - 2°) the hard drive that cdontains the music is hooked up to the compûter that does not work and as such I can not set it as the volume containing the music library. I should mention that I had installed "emby-server-beta" package on the computer that is not working now. And that it used to work quite nicely until for some reason it stopped go to the next track. So I stopped the server, uninstalled it and re-installed the "non-beta" package. And that is the one not working... I thought it could be some kind of daemon that was still running but it seems it is not as it also happens after several reboots And I can not install the emby-server-beta package as it seems maintainer has not updated it So I am "stuck" with the Snap version, that works but can't be restarted on the fly.

Ahh, that might be the case. I am pointing to the mediainfo binary that is within the snap package. Let me have a look... Edit: That was it, the snap package seems to have the gui version instead of the cli. Thank you!

Hello Thanks for answering.. the thing is that I saw this.. https://archlinux.org/packages/extra/x86_64/emby-server/ but I am not very sure if I have to uninstall emby first in its 4.7.11 version and install the new one or with a sudo pacman - Syu would update itself. For now snap packages do not convince me much.

Cause the client dosen't work, these days I was using tv and plex instead. Yestday I tried again and found it still couldn't play any viseo so I removed it. Then I found there's a snap version and after installed, this one works well. Seems there's something wrong with your apt pack.

No you don't want to play any games and redirect it. You want to copy it and then set the permissions as shown in the article. The instructions that are in that article are spot on and have been used hundreds of times. I've done over 100 upgrades myself. Just follow the instructions exactly as written using the latest version of Emby and it will work. I'd run a full library scan before getting too critical with it. I'm not sure I understand what you mean by the part I bolded above. Could you snap a picture and show me what you mean?

@rbjtechAlways a pleasure to read your full_of_wisdom replies Indeed, I was testing Emby on a mini HP PC yesterday (12500T/M2 SSD + 16Go Ram), after a quick and dirty install of debian 11 (not working with 12th gen) and 12 (yeah supporting the iGPU). The medias are on a separate machine over a simple 1G connection. Really nothing fancy. But I'm so new to Intel Transcoding that I have everything to learn. I had a really poor experience with that distro, being blocked a every steps to make transcoding work... On the pre-installed windows 11, I also tested emby server and couldn't pass 3 to 4 concurrent streams. Not the performance I had in mind when reading you could do 7 to 8 4K with your setup, but I had no memories about the details of your hardware either. Today, I reinstalled the last fedora on the miniPC and installed the snap version of Emby (4.7.11). No quick-sync available, only vaapi. Performance is quite OK. I could hit 5 transcodes of 1080p but 4K was not starting at all. So I installed on bare metal the last beta to the system. QuickSync is showned in the list (yeah) and 4K is playing pretty nicely (yeah x2). I could ran 5-6 streams (with regulation activated) before hitting the 1G bandwith. The result was much better than expected for a 2 hours experience with that distro starting from scratch In the end, it seems that Emby-beta is far more confortable with quick-sync on linux and for my setup (Emby on a different machine than the media and a slow lan connection), even faster than windows. I wonder if I could hook up the mini to the main server with something else than a lan connecter, like thunderbolt for example... Anyway, I will continue to benchmark all of this in the days to come.

... of course that's how it works - overthinking it by a LOT on my side So, it passes a tokenized URL to the client, alright! What's the format on it? Does it try for something like snap:// or steam:// or the like? I assume it pulls the rest of the base URL by what's in 'external domain' in emby's network settings, right?

Something I have noticed regarding the web interface for mobile: on my Nexus 7, attempting to open a pop up window in the server (such as the advanced refresh window in the metadata manager) results in an "Aw, Snap" error in Chrome for Android. I am attaching a screenshot of the error page. The crash was produced by attempting to open the advanced refresh window. Server v. 3.0.5347 Linux Mono build Sent from my Nexus 7

I hope this wil help others running Emby on Ubuntu. After reading around a lot, I've got let'sEncrypt to kindly provide me with a certificate. I added a txt reord to the domain by editing the DNS. Here are the commands sudo snap install --classic certbot -This installs certbot But you need the right values to add a txt record to your domain, I changed this line from the web "certbot -d bristol3.pki.enigmabridge.com --manual --preferred-challenges dns certonly" You get the responce " Please deploy a DNS TXT record under the name _acme-challenge.bristol3.pki.enigmabridge.com with the following value: 667drNmQL3vX6bu8YZlgy0wKNBlCny8yrjF1lSaUndc Once this is deployed, Press ENTER to continue" Create and add this text to your domain records, then issue certbot -d "Your Domain" --manual --preferred-challenges dns certonly -this issues the certificate, after querying your domain's txt record sudo certbot renew --dry-run I've changed the domain name in the examples below. root@emby:/etc/letsencrypt/live/domainname# ls cert.p12 cert.pem chain.pem fullchain.pem privkey.pem README I used "openssl pkcs12 -export -out cert.p12 -in cert.pem -inkey key.pem -passout pass: -nokeys" to create a PKS12 certificate, that's the cert.p12 file. And that's as far as I can get I can't add the path to emby. Once I select live, the path disappears, as if I hadn't entered anything. Im so close What am I doing wrong? Thanks

Forgot to mention that I tried opening with snap command in terminal and got error messages about "xxx cannot be preloaded (cannot open shared object file: ignored". The last error message says "/snap/emby-theater/x1/emby-theater...No such file or directory.

Hi everyone, is there anyone using Emby with lots of mp3s? I only have scene releases, so they are perfectly fine with .m3u and .nfo. and renamed like this "Snap-Rhythm_is_A_Dancer-CDM-1992-XXL" I divided the folders by years and with subfolders with letters, in order to make navigation from ftp and hd faster. Example: 1990 -> 0-1-2-3-4-5-6-7-8-9 / A-B-C-D-E / F-G-H-I-J-K etc etc. Aside from the fact that it's very slow to scan files, I've actually made it to the year 2001 and have started to see how Emby works. The problem is that it is very slow to navigate between playlists, folders, songs etc probably due to the fact that within each year I have something like 50 to 100,000 mp3s. Browsing also by genre is definitely too slow to load all the folders. This I believe is related to Emby doing too many functions at a time and failing to handle them. Also when it's being scanned, Emby is unusable and sometimes you can't even log in. Emby for ARMv8 is installed on a SSD Samsung (Qnap TS-233) and the mp3 are actually on a WD 12TB. Has anyone encountered similar problems? I also tried Plex but it's definitely immediate to load, but I don't like it for many reasons besides the limited functions. It was just to rule out other problems. Thanks.

Hello, after finding the tutorial on naming tv shows, I renamed my folder structure TV/Dexter - New Blood/Season 1/Dexter, New Blood - s01e01 - Cold Snap.mp4 and still can't seem to get it to show correctly in Emby. So I went to TVDB and looked up the ID for this particular episode and entered it in the box under the Identify prompt and it comes up that it can't find it. The same is true for doing the same via IMDB. Is the lack of information due to the way I have it named in Emby? The "TV" folder is on the same drive as my movies, does affect it also? I have the folder's properties set to "TV Shows" and have the TVDB listed as the first database. Any help would be appreciated. Thank you in advance. Scott

Therein lies your issue: your movie library is J:\ - can't have library with folder that is subset of another library. Hence your Dexter items are being queried as movies: 2023-01-23 09:28:38.528 Info HttpClient: GET https://api4.thetvdb.com/v4/search?type=movie&q=Dexter, New Blood - s01e01 - Cold Snap Transfer all your movies to J:\Movies and put that as Movie library path. Leave TV shows library as J:\TV. Rescan and everything will sort itself out.

Hi, I’ve been running a “native” Emby install on Linux Mint for the last year or so installed via the .deb package. I’m having just awful issues with Mint and impossible to pin down bugs so I decided to grab an NVMe SSD and start over with OpenSUSE Tumbleweed (so I’m keeping the Mint install limping along till I get the new one sorted out). oST is now installed and I’m about to install Emby but before I proceed, I wondered if anyone had compared running Emby as a native install, via Flatpak, vs Docker. I’ve read that for Plex, Docker can limit the number of threads/CPU making things like transcoding a much different experience (in this case, the person could do I think 10 transcodes in the native install vs around 2 transcodes in the Docker install). I’ve run Plex on my Mint install via a Snap and found that Snaps take up a lot of CPU usage and I’d find myself with 100% usage on all CPU/threads on my quad core/8 thread Core i7 setup. What I don’t know is what is from the Mint bug issues, what is from running in a Snap, and if Docker, Flatpak or a native install would be better (or if either of them would be similar/worse). The thing I like about Snap/Flatpak/Docker is the sandboxing of files and not worrying as much as dependencies running into each other. Obviously, that means there can be duplicated dependencies and I worry about the performance. What have any of you used and has anyone compared performance of running Emby in Docker vs Flatpak vs native install? I’d love to hear any thoughts, advice, experiences, etc. Thanks so much in advance!

Luke: 04:45 dgrio: doesn't look like it 2022-12-06.01:00:04 zfs snap -r DATA01@2022-12-06 2022-12-06.01:00:09 zfs destroy DATA01@2022-12-06 2022-12-06.01:13:55 zfs send -wI DATA01/home@2022-12-05 DATA01/home@2022-12-06 2022-12-06.01:14:27 zfs send -wI DATA01/dockers@2022-12-05 DATA01/dockers@2022-12-06 2022-12-06.01:14:30 zfs send -I DATA01/backups@2022-12-05 DATA01/backups@2022-12-06 2022-12-06.01:46:49 zfs send -wI DATA01/home@2022-12-05 DATA01/home@2022-12-06 2022-12-06.02:07:48 zfs send -wI DATA01/dockers@2022-12-05 DATA01/dockers@2022-12-06 2022-12-06.02:11:13 zfs destroy -R DATA01/ftp@2022-12-03 2022-12-06.02:11:19 zfs destroy -R DATA01/home@2022-12-03 2022-12-06.02:11:23 zfs destroy -R DATA01/dockers@2022-12-03 2022-12-06.02:11:24 zfs destroy -R DATA01/backups@2022-12-03 2022-12-06.02:11:29 zfs destroy -R DATA01/cache@2022-12-03

We have the packages built already but snap doesn't work well with the .NET core runtime as it blocks certain things from working. We had a back and forth dialog with snap about it but they kind of stopped responding to us about it and eventually I stopped bugging them. The packages only work when built in developer mode. When built using their strict mode, they're blocking the net core runtime from being able to load.

Im hitting the same issue for a while now. It seems to be unconsistent, but whenever I really want to add something, its technically broken. "Search for images" returns black cards If I open in a new window # .. i just wanted to snap it, but suddenly it works again for no obvious reason. Running emby version 4.7.8.0 embyserver(2).txt

A second workaround is to just update the font-family Emby is using from 'Material Icons Round' to just 'Material Icons'. So, this: Becomes: Yes, I linked to it above, in line. Here it is with the fancy previewer: Both cases seem to be the same after further investigation. I fixed the issue I originally reported within my plugin, and that fix still works within the scoped css of the plugin (again, though, I uninstalled the plugin to rule out interference). I think Emby's CSS needs to be revisited and tested with the font-family modification. I notice the suffix on the file name went from 2 to 3, suggesting another font version change. What are the chances Google deprecated something in your last font update (2), and removed it in the new one (3)? That could explain why only the new fonts failed in 2 and now all of them are failing in 3. I'm curious if anyone else can reproduce with 22.04.1 and FF 105.0.3 snap.

None of the known issues seem to match this one. The Material Design icons are actually rendering fine on the rest of the web. They're even working fine within the UI for my Iconic plugin (which I have since uninstalled to rule out interference). But, I previously had to put in a workaround to get around a similar rendering issue, which I documented here. This appears to be a specific incompatibility between this version of Firefox (I'm guessing the new snap build) and Emby. I've managed to 'fix' it by using the developer tools style tab to override the default font-face coming from Emby with relative links to the font file locations: @font-face { font-family:'Material Icons'; src:url('../../web/modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmP_3.woff2') format('woff2'), url('../../web/modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmJ_3.woff') format('woff') } This fix doesn't work when added through the custom CSS option in the UI, though. There seems to be some sort of disconnect between Emby pre-loading the font with javascript and the font being available to the dynamically loaded CSS files. So, even though this loads without error within the head tags: <link rel="preload" href="modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmP_3.woff2" as="font" type="font/woff2" crossorigin=""> It may not be available to the css for some reason. This has been in the console log for some time, even though the icons were still rendering. Maybe something else changed with this version of FF that stopped it from working at all: The resource at “http://localhost:8096/web/modules/fonts/material-icons/LDItaoyNOAY6Uewc665JcIzCKsKc_M9flwmP_3.woff2” preloaded with link preload was not used within a few seconds. Make sure all attributes of the preload tag are set correctly. index.html

better, but stil have a lot of useless thing, /dev /run /dev/shm /run/lock /sys/fs/cgroup /snap/lxd /snap/... 4-5 snap rep /run/snapd/ns and major problem / isnt there anymore so we dont have our main harddrive. only mounted one is there

Hi folks, I have an IPTV camera that provides its stream via RTMP. It works fine using VLC. Not sure if LiveTV supports RTMP 100% but I do have some that work with no issues. Here is snap of the log when I attempt to stream it via Emby. Startup: 2018-09-24 12:18:49.841 Application version: 3.6.0.47 http://192.168.yyy.253:8096/emby/videos/468787/live.m3u8?DeviceId=GTMZz8sx00knOUj8t4GA12QQDQoFTTGINPzofuQn3u4&MediaSourceId=ea3f592095b715ec1b463c910a57d626&VideoCodec=h264&AudioCodec=aac&VideoBitrate=139808000&AudioBitrate=192000&PlaySessionId=81c7735b72ad4d76ac8e84218ea60b20&api_key=b8e4c33f7079479eaaf0cd4c4281931d&LiveStreamId=a17c75760a04e99b68cf766e11316e1c_09efa0d56b934a82adec00a87b837fb0_ea3f592095b715ec1b463c910a57d626&TranscodingMaxAudioChannels=6&SegmentContainer=ts&MinSegments=1&BreakOnNonKeyFrames=True&h264-profile=high,main,baseline,constrainedbaseline&h264-level=51&TranscodeReasons=ContainerNotSupported,VideoCodecNotSupported {"Protocol":"Rtsp","Id":"ea3f592095b715ec1b463c910a57d626","Path":"rtsp://192.168.xxx.250/live/ch00_1","Type":"Default","Container":"rtsp","IsRemote":false,"ReadAtNativeFramerate":false,"DiscardCorruptPts":true,"FillWallClockDts":true,"IgnoreDts":false,"IgnoreIndex":false,"SupportsTranscoding":true,"SupportsDirectStream":false,"SupportsDirectPlay":true,"IsInfiniteStream":true,"RequiresOpening":true,"RequiresClosing":true,"LiveStreamId":"a17c75760a04e99b68cf766e11316e1c_09efa0d56b934a82adec00a87b837fb0_ea3f592095b715ec1b463c910a57d626","RequiresLooping":false,"SupportsProbing":true,"MediaStreams":[{"Codec":"h264","TimeBase":"1/90000","CodecTimeBase":"0/2","VideoRange":"SDR","DisplayTitle":"720P H264","NalLengthSize":"0","IsInterlaced":false,"BitRate":8000000,"BitDepth":8,"RefFrames":1,"IsDefault":false,"IsForced":false,"Height":720,"Width":1280,"RealFrameRate":16,"Profile":"High","Type":"Video","AspectRatio":"16:9","Index":-1,"IsExternal":false,"IsTextSubtitleStream":false,"SupportsExternalStream":false,"PixelFormat":"yuv420p","Level":40,"IsAnamorphic":false}],"Formats":[],"Bitrate":8000000,"RequiredHttpHeaders":{},"AnalyzeDurationMs":3000} User policy for Jason: EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True C:\Users\User\AppData\Roaming\Emby-Server\system\ffmpeg.exe -analyzeduration 3000000 -rtsp_transport tcp -rtsp_transport udp -rtsp_flags prefer_tcp -fflags +discardcorruptts+fillwallclockdts -f rtsp -i "rtsp://192.168.xxx.250/live/ch00_1" -map_metadata -1 -map_chapters -1 -threads 0 -sn -codec:v:0 copy -vsync -1 -codec:a:0 aac -strict experimental -ac 6 -ab 192000 -f segment -max_delay 5000000 -avoid_negative_ts disabled -start_at_zero -segment_time 3 -individual_header_trailer 0 -segment_format mpegts -segment_list_entry_prefix "hls/0a5c5d5210f366d1898948c4204562a5/" -segment_list_type m3u8 -segment_start_number 0 -segment_list "C:\_mb\transcode\transcoding-temp\0a5c5d5210f366d1898948c4204562a5.m3u8" -y "C:\_mb\transcode\transcoding-temp\0a5c5d5210f366d1898948c4204562a5%d.ts" ffmpeg version 4.0.2-emby_2018_09_13-g5abbb1430d+205 Copyright (c) 2000-2018 the FFmpeg developers built with gcc 8.2.0 (Rev1, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-cuda --enable-cuvid --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-nvenc --enable-zlib --enable-sdl2 --disable-debug --enable-ffnvcodec --enable-nvdec --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libvpx --enable-libx264 --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmfx --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwavpack --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-gpl --enable-avisynth --enable-libxvid --enable-libaom --enable-version3 --enable-libzvbi --enable-gnutls --extra-cflags=-DLIBTWOLAME_STATIC --extra-libs=-lstdc++ --extra-cflags=-DLIBXML_STATIC --extra-libs=-liconv libavutil 56. 14.100 / 56. 14.100 libavcodec 58. 18.100 / 58. 18.100 libavformat 58. 12.100 / 58. 12.100 libavdevice 58. 3.100 / 58. 3.100 libavfilter 7. 16.100 / 7. 16.100 libswscale 5. 1.100 / 5. 1.100 libswresample 3. 1.100 / 3. 1.100 libpostproc 55. 1.100 / 55. 1.100 [rtsp @ 0000016b4c77d340] Missing PPS in sprop-parameter-sets, ignoring [udp @ 0000016b4c781e00] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required) [udp @ 0000016b4c7920c0] 'circular_buffer_size' option was set but it is not supported on this build (pthread support is required) [rtsp @ 0000016b4c77d340] Invalid timestamps stream=0, pts=0, dts=9223090561878065152, size=8 [rtsp @ 0000016b4c77d340] Invalid timestamps stream=0, pts=0, dts=9223090561878065152, size=1447 [rtsp @ 0000016b4c77d340] Invalid timestamps stream=0, pts=0, dts=9223090561878065152, size=1442 Last message repeated 27 times Input #0, rtsp, from 'rtsp://192.168.xxx.250/live/ch00_1': Metadata: title : RTSP Server Live comment : ICL Streaming Media Duration: N/A, bitrate: N/A Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720, 90k tbr, 90k tbn, 180k tbc Codec AVOption b (set bitrate (in bits/s)) specified for output file #0 (C:\_mb\transcode\transcoding-temp\0a5c5d5210f366d1898948c4204562a5%d.ts) has not been used for any stream. The most likely reason is either wrong type (e.g. a video option with no video streams) or that it is a private option of some encoder which was not actually used for any stream. [segment @ 0000016b4d47b400] Opening 'C:\_mb\transcode\transcoding-temp\0a5c5d5210f366d1898948c4204562a50.ts' for writing Output #0, segment, to 'C:\_mb\transcode\transcoding-temp\0a5c5d5210f366d1898948c4204562a5%d.ts': Metadata: encoder : Lavf58.12.100 Stream #0:0: Video: h264 (High), yuv420p(progressive), 1280x720, q=2-31, 90k tbr, 90k tbn, 90k tbc Stream mapping: Stream #0:0 -> #0:0 (copy) Not urgent, but any assistance appreciated.

I realize this is not an emby question per se, but this seems to be the only forum I can find that has the xteve expertise that I need. I just migrated everything off an old Windows 10 PC onto a new Windows 11 machine, including Emby Server, xTeVe, and a new IPTV Service Provider. I had the same setup (albeit a different IPTV Service Provider) working fine on the old PC, but I been fighting this new setup for two days without any progress. My brain is fried and I'm out of ideas. Any xTeVe expertise is welcome! After transferring Emby perfectly to the new machine using the Backup Configuration plugin, I thought the hard part was over. I attempted to go to the xteve.de website to download the latest Windows version of xteve. This where the bad luck started. When I entered the url for xteve, I got a wierd page popping up telling me that this domain was available to be purchased (see screenshot). Did xTeVe website close down? Anyway, because of this, I had to rely on an older xteve.exe file I had copied from the old PC. Oddly, when I ran it, the xTeVe pop-up command line window ran and seemed to be loading all of the old settings from the setup on the old PC. While I thought it was strange, I figured it would not be too difficult to overcome that issue. Well, when I launched Chrome and opened a tab with the xTeVe web interface, it was indeed loaded with my old provider's m3u and xmltv links. I deleted them and replaced them with the new provider's m3u and xmltv credentials and successfully saved them. The xTeve header fields at the top of the screen showed over 413,000 streams, but 0 of them as available (see screen shot). I then realized that I had old filters still in there and were possibly eliminating all of the channels. After battling for hours trying to even see the filters due to constant "Aw Snap!" pop-ups in Chrome saying I was out of memory, I found that the only way to see the filters was to first delete the playlist and xml entries and only then I could immediately get into the Filters screen. So, I went into the Filters screen and deleted all of the filters and clicked Save. I then re-added the m3u and xmltv links and thought that would fix everything. No change. 0 of the 413,000 channels were available. I then looked at the Mapping secreen, and as expected, there were no channels shown at all. I have tried uninstalling xteve (impossible since nothing ever gets installed), deleting every file on my PC with "xteve" in its name. Nothing helps. When I re-load it, the same 0/413,000 channels is there waiting on me. Separately, I loaded NextPVR and input the new m3u and xmltv links and they immediately populated. I only did this to eliminate the possibility of one or both of those links were problematic. They were fine. Somehow, I have managed to screw up a pretty straight forward process - and one that I was familiar with. As of now, I have a non-functional xteve setup. If possible, I'd like to flush it and start over, but I don't know how. Otherwise, I'd love to hear anyone's thoughts on repairing it. Thanks in advance!

Thanks for the response about the website. Admittedly, I'm not a developer, but that github link does not serve the needs of normal users. I looked for 30+ minutes to find a simple "xteve for 64-bit Windows Download" button. There either is no such button or it has been so cleverly hidden as to only be accessible by the select few insiders with privileged or specialized knowledge. If it's that difficult to find, it is worthless to 99% of the public IMHO. Independent of that, I did manage to find a workaround for anyone else out there that may be frustrated with xteve's peculiarities... GOTCHA #1: It seems xteve presumes all users are Plex users, therefore enforces a default rule that only 480 channels or less can be made available, (as that is the ridiculously low channel streams limit set by Plex). If your m3u playlist has more than 480 channels (mine had over 400,000!), then xteve will show NONE or zero (0) of them as available. To get around that, you must add a filter on the xteve "Filters" screen. So, you must open the "Filters" screen to add at least 1 filter. Simple enough, right?... GOTCHA #2: If you have an m3u playlist from a modern IPTV service provider, it will likely have tens of thousands of channels, if not hundreds of thousands. Reducing that enormous number of channels/streams down to a reasonable number of interesting channels is usually the primary reason people want to use xteve in the first place. Well, because the playlist is so large, the "Filters" screen will not open. It times out and pops up the dreaded Chrome "Ah snap!" error screen indicating there is not enough memory to perform the selected action. Now, don't bother increasing the browser cache size - I did that all the way up to 2GB, and the results were exactly the same. It's a waste of time unless you just love playing with Chrome settings. I was at the end of this Chrome cache size increase process (with no improvement) when I originally opened this ticket. The Work-Around: Only by a long and painstaking process of trial and error, I discovered that by deleting the m3u playlist in xteve, you are immediately able to open the "Filters" screen. Woo-Hoo! Note: You do not need to remove the xmltv list in xteve as it doesn't seem to affect the Filters screen. So I did this, and then added a simple "Custom" filter that would find all the streams that included the word "Sport" in their name. Then I closed the Filters screen. I went back to the Playlist screen and once again added my m3u playlist and pressed Save. It worked! xteve found all of the Sports channels that were in my m3u playlist and showed them all as available. So to get this same process to work to get all of the channels I wanted, I again had to delete the m3u playlist from xteve, open the Filters screen, modify the Custom filter to include all of the channel types I wanted (in my case it was US, CA, UK, Sport). This means that if xteve finds any of these words in the name of the channel stream, it will now include it in the list of available channels. After completing this expansion of the filter, I went back and once again re-added the m3u playlist into xteve. Viola! You may have to repeat this seemingly silly process several times to get the filter(s) correct for your needs, but until someone finds and shares a more efficient solution, this one will work and chop that huge list of channels into something waasay more useful, and allow you to pass this smaller playlist on to Emby. Hope this helps someone. Good luck.

Hi All, I've been trying out using the Windows store version of Emby Theatre due to its superior resizing and ability to be snapped to the edges of my display (I would use the regular Emby Theatre if it had a regular windows title bar with functioning snap). Anyways, I've found that this version of Emby Theatre cant natively play any kind of subtitles I've used (ASS, PGSSUB, DVDSUB). Is this just a limitation of the player within the app? Is there any future plan to allow this version of Theatre to correctly play subtitles without burning them in? Thanks!