Leaderboard

of course it is, and there needs to be a fall back. Especially for users that meticulously create Episodes under custom series for non TVDB, TMDB or IMDB. This is where testing comes in so we capture everything. It's not my first rodeo at this pal

Actually, you have it backwards. Emby streams are much more complex streams to deliver than Netflix or others streaming services use. Netflix uses only prepared media so it's mainly working as a login/security system and web browser. Netflix delivery media from the edge of the network not from a central location. They create what's called a bitrate ladder. What this means is that the Netflix do very little work. They have multiple versions of each piece of media created in different formats and codecs. As an example, they might encode a simple video at the following profiles: 1080p 5.0 mbps 720p 4.0 mbps 640p 3.2 mbps 480p 2.0 mbps 270p 1 mbps They could do 5 like this for AVC, 5 for HEVC and 5 for VP9 or AV1. They will do something similar for audio. Storage is so much cheaper than CPU/GPU resources they would have to use otherwise. These different feeds are all passed by way of the manifest files which may look like this: #EXTM3U #EXT-X-VERSION:4 #EXT-X-MEDIA:TYPE=AUDIO,GROUP-ID="audio",NAME="aac_UND_6_384",DEFAULT=YES,URI="QualityLevels(384000)/Manifest(aac_UND_6_384,format=m3u8-aapl)" #EXT-X-STREAM-INF:BANDWIDTH=1355199,RESOLUTION=640x360,CODECS="avc1.64001e,mp4a.40.2",AUDIO="audio" QualityLevels(926058)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=1355199,RESOLUTION=640x360,CODECS="avc1.64001e",URI="QualityLevels(926058)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=2532741,RESOLUTION=960x540,CODECS="avc1.64001f,mp4a.40.2",AUDIO="audio" QualityLevels(2078252)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=2532741,RESOLUTION=960x540,CODECS="avc1.64001f",URI="QualityLevels(2078252)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=3617004,RESOLUTION=1280x720,CODECS="avc1.64001f,mp4a.40.2",AUDIO="audio" QualityLevels(3139175)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=3617004,RESOLUTION=1280x720,CODECS="avc1.64001f",URI="QualityLevels(3139175)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=4843919,RESOLUTION=1920x1080,CODECS="avc1.640028,mp4a.40.2",AUDIO="audio" QualityLevels(4339679)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=4843919,RESOLUTION=1920x1080,CODECS="avc1.640028",URI="QualityLevels(4339679)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=6086786,RESOLUTION=1920x1080,CODECS="avc1.640028,mp4a.40.2",AUDIO="audio" QualityLevels(5555791)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=6086786,RESOLUTION=1920x1080,CODECS="avc1.640028",URI="QualityLevels(5555791)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=7959113,RESOLUTION=2560x1440,CODECS="avc1.640032,mp4a.40.2",AUDIO="audio" QualityLevels(7387814)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=7959113,RESOLUTION=2560x1440,CODECS="avc1.640032",URI="QualityLevels(7387814)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=9868842,RESOLUTION=2560x1440,CODECS="avc1.640032,mp4a.40.2",AUDIO="audio" QualityLevels(9256433)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=9868842,RESOLUTION=2560x1440,CODECS="avc1.640032",URI="QualityLevels(9256433)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=11768326,RESOLUTION=2560x1440,CODECS="avc1.640032,mp4a.40.2",AUDIO="audio" QualityLevels(11115028)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=11768326,RESOLUTION=2560x1440,CODECS="avc1.640032",URI="QualityLevels(11115028)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=13681062,RESOLUTION=3840x2160,CODECS="avc1.640033,mp4a.40.2",AUDIO="audio" QualityLevels(12986590)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=13681062,RESOLUTION=3840x2160,CODECS="avc1.640033",URI="QualityLevels(12986590)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=15592476,RESOLUTION=3840x2160,CODECS="avc1.640033,mp4a.40.2",AUDIO="audio" QualityLevels(14856858)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=15592476,RESOLUTION=3840x2160,CODECS="avc1.640033",URI="QualityLevels(14856858)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=17530162,RESOLUTION=3840x2160,CODECS="avc1.640033,mp4a.40.2",AUDIO="audio" QualityLevels(16752832)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=17530162,RESOLUTION=3840x2160,CODECS="avc1.640033",URI="QualityLevels(16752832)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=19403831,RESOLUTION=4096x2304,CODECS="avc1.640033,mp4a.40.2",AUDIO="audio" QualityLevels(18586168)/Manifest(video,format=m3u8-aapl) #EXT-X-I-FRAME-STREAM-INF:BANDWIDTH=19403831,RESOLUTION=4096x2304,CODECS="avc1.640033",URI="QualityLevels(18586168)/Manifest(video,format=m3u8-aapl,type=keyframes)" #EXT-X-STREAM-INF:BANDWIDTH=400608,CODECS="mp4a.40.2",AUDIO="audio" QualityLevels(384000)/Manifest(aac_UND_6_384,format=m3u8-aapl) That's got over a dozen streams the client can pick from. The client app basically watches the buffer it has. If it can't keep the buffer filled it needs to use less bitrate. So now the client can pick the stream it wants to use and keep switch what it uses if needed to handle changes in bandwidth available to it. It gets to pick perfect streams that often take over a week being prepared for streaming. These streams are then pushed out to it's storage at the edge of the network Emby on the other hand doesn't get things nearly as easy. It tries to playback any format you have stored. One media might have 24 subtitles, 4 audio channels, none that match what the client needs and be using an old video codec. Not only does Emby handle this but does it at better than real-time. The job an Emby server does is easily 100x what a Netflix server has to handle!!! Amazon Prime has it slightly tougher than Netflix as they handle Live TV and sell this as a package. That's more demanding but still pretty easy as the starting format hardly ever changes, and they use dedicated encoding devices.

I will do it in 2-3 days - little busy at work

@Seger So you want an option to hide the library but keep the row just line New Releases.

i can knock this up pretty quickly i think.

We won't have any updates until they release it - unless it is rejected for some reason. All we know is it is "in review". Any attempt to find out any other information is met with boiler-plate responses of "some apps take longer to approve". I can say that the last production review process took about 3 weeks. It's been two weeks for the beta track and one week for production so far.

This is fixed in Verison 1.0.0.19. If NFO files exist for an item in the library, they are now serialized for use in top picks. if an NFO files doesn't exist for an item in the library, then emby will attempt to identify the top pick item, and we hope it identifies it properly. Top picks also now allows you to target a specific library. It is optional. If left empty, all movies are targeted.

first, I don't think anyway is suggesting disabling h.264 support so web browser access shouldn't be affected. second, zero percent of my users are using a browser. It's all apps or TVs. All devices that fully support h.265 and some that do AV1 as well. I think this is the most typically use case. Right now, emby streams are far inferior to the likes of Netflix and Youtube etc. We are basically a decade behind in streaming tech and the mobile/remote user experience suffers as a result. This makes Emby essentially an in-home platform for my family because it really drags streaming it out. I have symetrical 1G fiber btw. Mobile networks are my issue and having double the bandwidth requirements for mobile is the strain.

Hi. I believe this is fixed in the new version currently under review by Roku.

You get at least one tester !!! I volunteer

i´ll send one tomorrow

Yes, but no difference I have Emby server v.4.7.8.0 and Chrome version 106.0.5249.119 (Official Build) (64-bit). I also for the sake of it tried running with Disable HLS Subtitles & Disable Subtitle Streams checked in the diagnostics plugin but still happens. Will try to use the emby beta and see if that acts any different.

@LukeTranslation is bad Auf deutsch: Anscheinend ist ein Dankeschön heutzutage zu viel verlangt.

This is not what i had in mind for the restore/backup utility. The user can set up a backup every 24hrs and it will just overwrite the existing backup. On a restore, it will completely overwrite all of the Intro/Credit Markers with the information stored in the backup. Recap isn't even a feature yet. We planned to add that to the introskip plugin, where the user could say that a season or episode's recap was directly before the Intro and then everything before the IntroEndMarker would be skipped. But we never implemented it, the core took over and TeamB decided to go his own route. so we binned the IntroSkip Plugin that was far superior to all of the current solutions available. Anyways. That's what i'm planning with the scope of this plugin.

Ah, okay. @Seger, Let me see if that is available in library creation. If it is, I will add it. I find out...

Log started and 13:23:34.798 with normal system info then nothing til 13:30:19.700 and a minute later you scanned. So we will probably need debug logging with a specific example (names and times).

Release 20221023: HDHR5/HDFX/HDVR/HHDD models: IPv6 support. HDHR5/HDFX/HDVR/HHDD models: Improvements to automatic reboot handling required for EU certification. HDFX/HDVR/HHDD models: Optimized handling of a new DVR request for the same channel from the same client. HDFX/HDVR/HHDD models: Fix problem where duplicates could start recording at startup while existing recordings are still being detected. ATSC3 models: Fix problem handling ATSC 3.0 stations missing media content type tag. ATSC3 models: Fix problem handling ATSC 3.0 stations where the sample duration was not specified. HDFX models: Use the first 17.6TB of the hard drive rather than failing to configure a hard drive 18TB or larger. HDVR models: Operate as a tuner only if the hard drive is removed or not functioning. HDTC: Fix reporting of codec tag in http response when transcoding. Add lineup.m3u for use with VLC and other apps that import m3u channel lists. Fix parsing of URLs without URI after the IP address. Improvements to URL generation so the URLs are valid from .local names or if port forwarding across private subnets. Don’t limit TTL for discover, control, or webpage access on private networks. Upgraded discover support. Security: Improved IP validation. Legacy models: Update lineup URL. Legacy models: Security: Limit TTL for non-private networks. Firmware Changelog

Got cracking with this, shouldn't take long. I have to help some clients in Holland with some oilfield data this evening, so will be limited on what I can actually get stuck into. But hopefully will have something for testing tomorrow.

After further playing around, I think two of the other issues are with the Roku app, so they don't belong here! However the other one is: On both the Now Playing and the Play Queue screens, the Previous and Next track buttons do not appear. This is regardless of which version of Android and which app it is playing to, so I believe it's a problem with the mobile app. It may be a deliberate design decision? But it's inconvenient that they don't appear on those screens.

I assume the F isn't for "Friendly" or "First"

RTFP

Like I previously said, I don't currently have a log of when the issue took place. Until I'm able to get 20 concurrent streams going again all I can do is ask if anyone has run into this issue and find out how they manage their transcoding-temp folder with that many streams.

I can only speak for emby-next-gen plugin for Kodi: Yes, cinema mode is supported (this is a Premium feature). Also live TV, skip intro etc. is supported Yes, Kodi companion is required especially when you remove content, but Kodi companion is not a Premium feature. Only on local network as long as you don't use plugins like trakt or configure Emby for internet access etc. Emby is a standalone server based system. Content metadata is downloaded from internet (moviedb etc), but not uploading content or profiles btw, even this could be disabled. Finally, if you use next-gen plugin, try the latest 7.x. versions (only for Kodi 19+) @Luke Any comments from your side?

wanted to give feedback, with the new option to not show anything on the original poster, it looks very clean to me now and the original poster remains untouched. I understand that the sort order cannot be influenced further, but is it possible to add the option to hide the folder completely? With collections there is such a function in the view: Thank you and best regards Seger

@TeamB In my example TMDB had 7.25 and OMDB did not have anything and Emby showed 7.3. But the next episode showed 8 and TMDB shows 7.198 while OMDB shows 8. Arrow S01E01 and S01E02 You can see the provider metadata in the cache folder.

As stated: Specific example will be needed with some more details, like your folder structure, naming scheme etc.

Sorry, I can't use host mode stably on myserver, after every reboot it would mess up my network settings. Right now I have to switch back to bridge mode, I guess I have to give up on dlna server until I can fix this problem. On a related topic, is there a plan for EMBY VR version?

I could add it back for you, but it sounds like you don't need it anyway. It is always better to retrieve only what you need, so if just getting the Ids is sufficient then that is much better than retrieving the whole objects. I would use GetExtraIds instead of GetExtraGuids.

THANKS YOU THANK YOU !!!!!!! That was my problem !! I created a new library instead of adding the addition path in the same folder. You guys are great !!! sorry I got back so late on the issue but I been working extra hours and have not had time to come back here but that was the trick ! I added the path in the same folded and it works. Thank you again and the picture help out alot.

Ah, gotcha. No problem. Glad you figured it out.

Aha, I found it. Sorry it was custom css height limit on .skinheader... Sorry everyone. Thanks for responding so quickly. It was all my fault to my too fancy CSS custom styling.

All the new channels are in the guide now.

What is the library setting? But Collections come from Item metadata now so you may have to ensure your media is unlocked and refresh all metadata.

Dev will have to comment but removing/reinstalling the plug will not make a difference.

You all were probably like wow! this guy lol!

Thanks everyone I got. I was thinking that the emby server was updating automatically I had no Idea how far back I was.

ok doing now

there's an echo in here

Nothing like everyone cross posting.

So, I will need an update on the emby server then?

I'm adding this option to the configuration settings. You will have the opportunity to choose the movie library to create top picks from. This will fix another issue where some adult content was find it's way into the library as well. Some people will have multiple entries listed in the select box, some will have only one. But I still am unsure about what will happen when you group items across libraries together. I'm not really not even sure how the auto-group plugin is doing that. This might be the best I can do.

A quick update. I moved a 2Tb SSD from my Windows computer to my M1 Mini to start with. Everything went fine, I only made 2 sections, photos and videos and just lumped everything into them for now. I need to tweak some settings and move some folders, but so far it is going faster and better than I thought as sometimes moving from Win to Mac is not simple. This is my M1 Mini 16gB Memory activity when playing a video thru Emby. This is the CPU:

I decided for the Nvidia Shield pro and got it yesterday. It absolutely outperforms the 4K Stick. While the 4K Sticks plays my Home Videos H.265 8 Bit (Main) 4K 60 fps up to a Bitrate of 75mbit/s (Level 153 = Level 5.1) and starts to lag as soon as the Bitrate is higher than 75 mbit ( 85 mbit; Level 156=Level 5.2) because they need to be transcoded, Nvidia Shield plays also 100 Mbit without any lag in direct play without transcoding (level 186 = level 6.2). I did not try higher Mbit rates yet. Fire Stick 4K does not play H265 10bit (main 10) 4K 60fps files with 35 Mbit/s (Level 156=Level 5.2) without lags (need transcoding), while Shield TV pro has no problem at all with these files. Also here I did not test higher bitrates. None of these files could be played by the old Fire Stick 2nd Generation (non 4K) with was substituted by the Nvidia Shield pro. It hat an illuminated remote control which works absolutely intuitive! seems I found my new favorite device! I am even considering now to buy a second one to substitute the 4K Stick on my main TV. Regards, Tsch3ns

Great idea, thank you!

I figured out my problem. My new router/modem combo is on a different subnet than the old outgoing one. I all I had to do is assign an extra network port I wasn't using an IP address on the same subnet as my switch and problem solved.

HI, yes some sort of edit and backup process for this is planned for future updates. Thanks.

Just added some new movies and all have the same problem. I just PM'ed you screenshots and logs.

Out of sync audio is no longer a problem. It resolved itself without me doing anything. My problem remains what I pointed out to you in the other post.

Same issue for me on Safari (Mac and iOS) web app through a proxy. Nothing in the logs expect that the transcoding or direct play was stopped by the application. Currently using Chrome or Emby apps to avoid the issue but that's annoying... EDIT: found out that activating proxy_buffering in nginx may have solved the issue.

Also it’ll saves me about $1,000 for not having to buy as many SSDs by converting most of my videos to x265 so there’s that argument too. I agree though when Emby does decide to roll out this transcoding feature there will be many moans and groans. Initially though just having it do conversions would be ideal.