Search the Community

Hi, I'm noticing that whenever I set quality to auto, it direct plays but the video stutters every 2 seconds. If i manually set the bit rate to match the video bit rate it works smoothly.. but setting it to auto causes it lag or buffer every 2 seconds on certain videos. If i seek then it struggles to play it. Sometimes auto picks up the wrong quality setting entirely like choosing 720p 4Mbps for a 10Mbps bitrate.. I'm not sure what's wrong with my config. Any help would be appreciated. I'm using emby server 4.8.10 and I have an NVIDIA GPU. I'm attaching logs for reference when this happens.. embyserver.txt ffmpeg-transcode-c32e80a8-e89c-448a-b8e3-23d0dffdf933_1.txt

I'm running emby server on a linux kubernetes cluster with 2 NVIDIA GPUs. On any device (Fire stick, ipad, phone or browser) for several videos if i seek the stream forward or backward even by a little bit, the video starts stuttering every 2 seconds. There's no recovery from that. Even if i exit the app and come back and try to resume the lag remains. Then I tried fiddling with the quality settings - I don't need to reduce to the point of transcoding. I just kept swapping between Auto and 1080p - 10Mbps. The video is a 1080p H264 and bitrate of 8mbps. Finally after multiple tries it continues playing normally at 1080p - 10Mbps still as a Direct play. The server dashboard says the stream is direct play throughout. I'm attaching some logs. The logs are while playing on the ipad. If you would like me to get you logs for some other device, let me know and i would be more than happy to pull them. ffmpeg-remux-seek-recov.txt embyserver-seek-recov.txt ffmpeg-remux-seek.txt embyserver-seek.txt

Hello, I used emby on docker right now and i want to migrate to k8s... With the following manifest i can deploy emby and access it: apiVersion: v1 kind: Service metadata: labels: app: emby-server name: emby-server namespace: media spec: ports: - name: http port: 8096 protocol: TCP - name: https port: 8920 protocol: TCP selector: app: emby-server --- apiVersion: apps/v1 kind: Deployment metadata: name: emby-server namespace: media spec: replicas: 1 selector: matchLabels: app: emby-server template: metadata: labels: app: emby-server spec: containers: - image: 'emby/embyserver:latest' imagePullPolicy: IfNotPresent livenessProbe: httpGet: path: /web/index.html port: 8096 timeoutSeconds: 30 name: emby-server ports: - containerPort: 8096 - containerPort: 8920 readinessProbe: httpGet: path: /web/index.html port: 8096 timeoutSeconds: 30 volumeMounts: - mountPath: /mnt/library name: media-library - mountPath: /mnt/perso name: media-library-perso volumes: - name: media-library nfs: path: /volume1/Data/k8s server: 192.168.x.x - name: media-library-perso nfs: path: /volume1/Data/k8s/Photos server: 192.168.x.x --- apiVersion: traefik.containo.us/v1alpha1 kind: IngressRoute metadata: name: emby-server namespace: media spec: entryPoints: - websecure routes: - kind: Rule match: Host(`emby-dev.xxxx.fr`) services: - name: emby-server port: 8096 tls: secretName: xxxxxxxxxx From this point i have 2 issues: - I can browse the folder (GUI) but he's empty and if i access it in cli and show the contents of the folder i can see my files. MY second problem is i can't reach a subfolder in the GUI. on my Nas i have many folders under /volume1/Data/k8s but i have an error if i try to add it: But i see then in cli: Did i miss something ?

Hi guys, So I've seen that quite a few are already running Emby in a Kubernetes Cluster. My setup currently looks like this: - One Kubernetes Node (I'm using K8s because I'm familiar with it and I like writing deployment-manifests :-) ) - A standard router from my ISP, doing port-forwards on HTTP & HTTPS - MetalLB assigning virtual IPs for loadbalancers (L2) - Nginx Ingress using a LoadBalancer, so it gets a virtual IP. uses Service with `externalTrafficPolicy: local`. - Emby using an Ingress-Resource, HTTPS, letsencrypt certificates. My issue though is that it seems like Emby considers everything to be the "local" network. From skimming through the logs: 2019-11-05 19:40:11.692 Info HttpServer: HTTP GET http://<mydomain>:8096/emby/Users/<key>. UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.0.2 Safari/605.1.15 2019-11-05 19:40:11.695 Info HttpServer: HTTP Response 200 to 127.0.0.1. Time: 3ms. http://<mydomain>:8096/emby/Users/<key> A few things: My Emby instance is not reachable under http://<mydomain>:8096, but rather on https://<mydomain>:443 (through the Ingress). It seems like Emby responds to the request to localhost?? This would explain why Emby considers everything to be local network. Anybody an idea why? Or what did you guys set to actually pass through the Source IP? Like mentioned before, I'm already using `externalTrafficPolicy: Local` for the nginx-ingress service. Also, for reference, the deployment yaml: apiVersion: app/v1 kind: Deployment metadata: name: emby-server labels: app: emby spec: replicas: 1 selector: matchLabels: app: emby template: metadata: labels: run: emby-server app: emby spec: containers: - name: emby-server image: emby/embyserver:latest env: - name: "UID" value: "1030" # emby user - name: "GID" value: "1111" # share group ports: - containerPort: 8096 name: emby-http volumeMounts: - mountPath: /config name: emby-config - mountPath: /mnt/media name: emby-media volumes: - name: emby-media hostPath: type: Directory path: /media - name: emby-config hostPath: type: DirectoryOrCreate path: /mnt/cluster/emby Total noob with emby, deployed it a couple of days ago. Any help would be appreciated.