All Activity

it says min value is 9000. I thought I had it working before on port 8096 even with truenas port being off, but I maybe mistaken.

If I understand it correctly you're telling the docker container to use 9096 instead of 8096 and I'm not sure that that's correct since I don't see anything that would be mapping 9096 to 8096 in the container. Again, not particularly versed on TrueNAS Scale but it might be a good idea to match that for now.

good day what's the status here I'm confused. I have the latest server 4850 and the add on stable from the first page here. but I cannot get it to work. many thanks for help!!

If you meant my truenas config here it is.

I'll give 4.8.6 a try and report back.

Sorry my mistake, I didn't include 9096 port forwarding in the picture because there was about 11 other records above it in the port forwarding list. 9096 is being forwarded and so is 8096 and 8920, but I didn't include it in the picture. attached is my settings but my server name replaced.

This isn't right. The only reason for the horizontal rows would be if you added more than one media type to the collection. First things first, please try the Emby Server 4.8.6 update and let us know how that compares. Thanks !

HI, not yet. Please contribute your feedback into the other topic. The more users that request the feature, the higher priority that it will be. Thanks !

The audio channel number isn't supported. This means the audio is being transcoded. The Roku keys video frames to sync with the audio. It isn't making the normal 3 second slices. The duration is coming up short. Here is what a normal transcode duration should be. The Roku is having problem stitching them together for some reason. Almost like the timestamps go back into the previously fetched section for the just fetched section. If you run this through MKVToolNix GUI and just "start remux" and let it complete does the newly remuxed file have the same problems? If it is a problem with the header or something odd remuxing it should take care of it. Unless it is something they've encoded into the stream. That is the problem with these types of media from that particular release group. Anyone in their group can encode and they don't really have standards. This isn't a "scene" release which has standards. You may have to correct the problems the media has, such as bad headers, multiple default streams set, etc. The Roku is very strict about adhering to standards. Let us know if remuxing solves the problem.

I'm not familiar with TrueNAS Scale beyond a few minutes playing around a few months ago, what does your configuration look like for the application? Not sure how external access on 9096 would make sense since your port forwarding configuration didn't mention that port, unless that was a typo.

HI, we have a new windows app coming soon, so please reevaluate with that once available. Thanks.

One minute. It isn't designed to lock you out and require reactivating the user. Only to prevent brute force login attempts.

Thank you. If I fix the cert then it should start listening on 8920! I still don't know why I can't access it from 8096.

What is the solution?

On the FireTV client, I can see only the Final Cut, in both 4K and 1080p. On other clients, all six versions of the film are available. Different users, so potentially a permissions issue, but AFAIK there's nothing in place on the FireTV user that would cause this. All three versions of each resolution are in the same folder, and the parental controls restrict only a couple of tags, neither of which is applied to any version of Apocalypse Now. Further, when playing the 4K version of the film, the screen is blank. I can't even bring up the OSD. Audio is fine, as are other 4K/DolbyVision films. embyserver.txt

That solved it - not sure how it got set to only specific devices in the first place, but never mind that - but my questions regarding the length and override of the lockout remain.

Thank you for your quick response. Is a solution being worked on? The question is a bit older, from 2016. Thanks...

HI, thanks for following up.

The former is just our old code base from about five years ago, so I know it quite well. It's back from a time when we required a specific folder structure for music, so songs would get lumped into an album just by being in the same folder together. Now we've become fully tag driven and use all of the embedded information within your files.

Hi, please let us know what you find. Thanks.

@Luke Has something changed with the Discogs plugin again? I am back to having hours upon hours of too many requests errors in the logs and that is impeding Emby from doing any other scans Today's logs have 6 hours so far of Discogs Errors.

Hi, can you please attach the information as plain text rather than pdf? Thanks !

@Smitty0182104.8.6 is heading up now and the missing links to see all in non-tv mode are are resolved. Thanks !

@kasablur?

Hi, we are looking into it. Thanks.