can't fast forward / rewind a video

[ebr 14930]

20 hours ago, Theogeek said:

all seems to be working now

Excellent.  Thanks for testing.

[DreamSeason 5]

I've the same issue with my parents far from home having difficulies in fast forwarding certain high bitrate movies. The certificate is not the cause for me. So I'd like to ask devs to bring back the cache buffer option (at least for direct play). The issue is that if my parents ff say 30 seconds, playback is all right. But once they ff something like serveral mintues, then black screen comes along. They just switched from kodi to emby recently. I used to help them adjust the buffer big enough so that ff will not cause issues like this.

BTW, I've seen the feedback provided by op serveral posts above that the latest beta has cut the black screen loading time a lot.

Even though I still hope devs would consider my advice and give back the buffer settings to us maybe in advanced settings  .

Edited September 6, 2022 by DreamSeason

[DreamSeason 5]

On 9/4/2022 at 9:54 PM, ebr said:

Excellent.  Thanks for testing.

 Hi Emby dev. Would you mind checking my posts above?

[ebr 14930]

2 hours ago, DreamSeason said:

 Hi Emby dev. Would you mind checking my posts above?

Hi.  Have you tried the latest beta release of the app?

 

 

[DreamSeason 5]

On 9/6/2022 at 11:23 PM, ebr said:

Hi.  Have you tried the latest beta release of the app?

 

 

 By upgarding to latest version of emby for AndroidTV (2.0.79G) , the problems for my parents' tv is gone. Nontheless, could we have the buffer setting back? Buffer settings would be great for users who use direct play to avoid network inconsistency.

[horstepipe 356]

still having the problem but here is Cloudflare in place. At least chapters are now being created (also if the file doesn't contain them).

Thanks!

[austinluck 1]

My emby server was at 4.7.6.0 and I upgraded my shield app to the latest beta release 2.0.81.  I loaded up a 4k HDR Blu ray rip that has DTS-HD-7.1 and it actually was able to skip ahead once.  The second skip it hung for 2 minutes like before.  

Then I loaded the latest beta server version 4.8.0.8 and tried again.  Now I can skip forward and backward freely without pause or hanging or crashes!!  Amazing!  

[meadowcottage 0]

Just wanted to report I'm also experiencing this. Started with a few users and ended up being everyone who uses android TV. Getting a bunch of non tech people to side load apps is no solution so I've just moved everything over to plex (seems a lot more usable that when I tried it last) which has fixed everything for now.

 

Maybe I'll come back to emby one day but its only become more problematic for me over time.

[FrostyCoolSlug 6]

I'm still experiencing this with the 2.0.81 beta and beta server version 4.8.0.8, skipping ahead seems to completely hang the shield for a couple of minutes (unable to even return to the home screen), after which everything recovers back to normal.

[Luke 37116]

On 9/12/2022 at 2:04 PM, FrostyCoolSlug said:

I'm still experiencing this with the 2.0.81 beta and beta server version 4.8.0.8, skipping ahead seems to completely hang the shield for a couple of minutes (unable to even return to the home screen), after which everything recovers back to normal.

@FrostyCoolSlug 

Hi.  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

[Theogeek 6]

Hmmm...the Android TV app is ... "flaky" at this again.  Not sure what's going on, but the standard android app works great for nearly everything (especially FF/REV) so I've been sticking with that one.

One big thing that the Android App seems to be missing is the ability to rewind live TV. The Android TV app did this but I can't figure out how to get the Android App to do it too.

Thanks!

Jeff.

[FrostyCoolSlug 6]

On 14/09/2022 at 19:21, Luke said:

@FrostyCoolSlug 

Hi.  Can you try sideloading our standard android app on the same device and see how that compares?

https://emby.media/emby-for-android.html

Thanks.

 

Sorry for the delay, I've tested out the Android app, and fast forward / rewind seems to be working ok, however I occasionally see the same behaviour now when starting media. Although the loading spinner appears, the shield becomes completely unresponsive to button presses for up to 30 seconds until the media has started.

Edited September 26, 2022 by FrostyCoolSlug
Clarity

[FrostyCoolSlug 6]

Just to update, I've just had the regular android client hang when doing a long ff then immediately rewind. The ff was fine, but rewind broke it.

It seems to occur less often, but is still a problem.

[Luke 37116]

On 9/26/2022 at 8:08 AM, FrostyCoolSlug said:

Just to update, I've just had the regular android client hang when doing a long ff then immediately rewind. The ff was fine, but rewind broke it.

It seems to occur less often, but is still a problem.

For a given video, does it happen in the same spot each time you play?

[AngelOfTheOdd 6]

Seeing this behavior also.  I was using a 4k FireTV stick.. started noticing this problem a month or so back.  Decided to try a 2019 Nvidia shield pro this week. Problem still remained. Always worked fine on IOS. Always fine on Windows app.

Came across this thread.  Bypassed nginx(swag ssl) and the problem disappeared. Fast forward and rewind are working normally again.  Been using nginx(swag) with emby since it was “letsencrypt” back when.  Always worked great together. But there definitely seems to be some kind of failure going on with the Android client going through nginx now, when it comes to ff and rw.
 

What’s also interesting is, when ff and rw were effectively broken, going forward or back using chapter timeline worked just fine.
 

Glad there’s a workaround, but would be nice to get this going through nginx ssl again.

EmbyServer 4.7.8.0

Emby Android TV 2.0.79g

 

 

[Luke 37116]

On 10/11/2022 at 10:31 PM, AngelOfTheOdd said:

Seeing this behavior also.  I was using a 4k FireTV stick.. started noticing this problem a month or so back.  Decided to try a 2019 Nvidia shield pro this week. Problem still remained. Always worked fine on IOS. Always fine on Windows app.

Came across this thread.  Bypassed nginx(swag ssl) and the problem disappeared. Fast forward and rewind are working normally again.  Been using nginx(swag) with emby since it was “letsencrypt” back when.  Always worked great together. But there definitely seems to be some kind of failure going on with the Android client going through nginx now, when it comes to ff and rw.
 

What’s also interesting is, when ff and rw were effectively broken, going forward or back using chapter timeline worked just fine.
 

Glad there’s a workaround, but would be nice to get this going through nginx ssl again.

EmbyServer 4.7.8.0

Emby Android TV 2.0.79g

 

 

Have you taken a look at this?

 

[pir8radio 1292]

On 10/11/2022 at 9:31 PM, AngelOfTheOdd said:

Seeing this behavior also.  I was using a 4k FireTV stick.. started noticing this problem a month or so back.  Decided to try a 2019 Nvidia shield pro this week. Problem still remained. Always worked fine on IOS. Always fine on Windows app.

Came across this thread.  Bypassed nginx(swag ssl) and the problem disappeared. Fast forward and rewind are working normally again.  Been using nginx(swag) with emby since it was “letsencrypt” back when.  Always worked great together. But there definitely seems to be some kind of failure going on with the Android client going through nginx now, when it comes to ff and rw.
 

What’s also interesting is, when ff and rw were effectively broken, going forward or back using chapter timeline worked just fine.
 

Glad there’s a workaround, but would be nice to get this going through nginx ssl again.

EmbyServer 4.7.8.0

Emby Android TV 2.0.79g

 

 

odd been using nginx for years,   no issues.   yea maybe compare your config to the mine posted above?

[AngelOfTheOdd 6]

8 minutes ago, pir8radio said:

odd been using nginx for years,   no issues.   yea maybe compare your config to the mine posted above?

Yup, I have also.. with the swag docker image.  Just started to be a problem in the last month or so and only with the Android tv and Firetv players.  IOS and Windows EmbyTheater are still working great through ngnix(swag).  I've bypassed nginx for now, on the firetv and androidtv clients.  I'll try and find some time this weekend to compare your proxy config with what I got. 

[pir8radio 1292]

24 minutes ago, AngelOfTheOdd said:

Yup, I have also.. with the swag docker image.  Just started to be a problem in the last month or so and only with the Android tv and Firetv players.  IOS and Windows EmbyTheater are still working great through ngnix(swag).  I've bypassed nginx for now, on the firetv and androidtv clients.  I'll try and find some time this weekend to compare your proxy config with what I got. 

10-4  ping me if I can help! 

[AngelOfTheOdd 6]

Played around a bit with this today using @pir8radio's nginx configs.   Spun up a new ngnix container and pulled swag's letsencrypt's keys over.  So I'm 100% on @pir8radio's nginx.conf

 

version: "3.9"

networks:
  media-stack:
    ipam:
      driver: default
      config:
       - subnet: 172.19.1.0/24

  nginx:
    image: nginx:latest
    container_name: nginx
    volumes:
      - ${CONFDIR}/nginx/nginx.conf:/etc/nginx/nginx.conf
      - ${CONFDIR}/nginx/keys:/keys
      - ${CONFDIR}/nginx/logs:/etc/nginx/logs/
    networks:
      - media-stack
    ports:
      - 80:80
      - 443:443
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "10"

  emby-stable:
    container_name: emby
    image: emby/embyserver_arm64v8:latest
    environment:
     TZ: 'America/Chicago'
     UID: ${UID}
     GID: ${GID}
    networks:
      - media-stack
    ports:
      - "8096:8096"
      - "8920:8920"
    volumes:
      - ${CONFDIR}/emby-stable:/config
      - /GD:/GD
      - /GD/TV:/TV
      - /GD/Movies_HD:/Movies_HD
      - /GD/Movies_4K:/Movies_4K
      - /mnt/MoviesCombined:/MoviesCombined:ro
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "10"

 

cat /bsv/docker-state/nginx/nginx.conf
worker_processes  auto;

error_log  logs/error_test.log;

events {
    worker_connections  8192;
}

http {
    include       mime.types;
    default_type  application/octet-stream;
    server_names_hash_bucket_size 64;
    server_tokens off;

    ## The below will create a separate log file for your emby server which includes
    ## userId's and other emby specific info, handy for external log viewers.
    ## Cloudflare users will want to swap $remote_addr in first line below to $http_CF_Connecting_IP
    ## to log the real client IP address
    log_format  emby  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port "$http_x_emby_authorization"';


    log_format default '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port';

    sendfile        off;  ## Sendfile not used in a proxy environment.

    gzip on;   ## Compresses the content to the client, speeds up client browsing.
        gzip_disable "msie6";

        gzip_comp_level 6;
        gzip_min_length 1100;
        gzip_buffers 16 8k;
        gzip_proxied any;
        gzip_types
            text/plain
            text/css
            text/js
            text/xml
            text/javascript
            application/javascript
            application/x-javascript
            application/json
            application/xml
            application/rss+xml
            image/svg+xml;

    proxy_connect_timeout 1h;
    proxy_send_timeout 1h;
    proxy_read_timeout 1h;
    tcp_nodelay on;  ## Sends data as fast as it can not buffering large chunks, saves about 200ms per request.

    ## The below will force all nginx traffic to SSL, make sure all other server blocks only listen on 443
	
server {
    listen 80 default_server;
    server_name _;

    return 301 https://$host$request_uri;
}

    ## Start of actual server blocks
server {

    listen [::]:443 ssl http2;  ## Listens on port 443 IPv6 with http2 and ssl enabled
    listen 443 ssl http2;       ## Listens on port 443 IPv4 with http2 and ssl enabled
    proxy_buffering off;        ## Sends data as fast as it can not buffering large chunks.

    server_name embydr.*;    ## enter your service name and domain name here example emby.domainname.com

    access_log  logs/emby.log  emby;  ## Creates a log file with this name and the log info above.

     ## SSL SETTINGS ##
        ssl_session_timeout 30m;
        ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
        ssl_certificate /keys/fullchain.pem;
        ssl_certificate_key /keys/privkey.pem;
        ssl_session_cache shared:SSL:10m;

        location ^~ /swagger {   ## Disables access to swagger interface
        return 404;
}

     location / {
        proxy_pass http://emby:8096;  ## Enter the IP and port of the backend emby server here.
        client_max_body_size 1000M;  ## Allows for mobile device large photo uploads.

        proxy_hide_header X-Powered-By;      ## Hides nginx server version from bad guys.
        proxy_set_header Range $http_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header If-Range $http_if_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header X-Real-IP $remote_addr;  ## Passes the real client IP to the backend server.
        #proxy_set_header X-Real-IP $http_CF_Connecting_IP;  ## if you use cloudflare un-comment this line and comment out above line.
        proxy_set_header Host $host;  ## Passes the requested domain name to the backend server.
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;  ## Adds forwarded IP to the list of IPs that were forwarded to the backend server.

     ## ADDITIONAL SECURITY SETTINGS ##
     ## Optional settings to improve security ##
     ## add these after you have completed your testing and ssl setup ##
     ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ##
     ##         See https://hstspreload.org/ read through the "Deployment Recommendations" section first!   ##
           add_header 'Referrer-Policy' 'origin-when-cross-origin';
           add_header Strict-Transport-Security "max-age=15552000; preload" always;
           add_header X-Frame-Options "SAMEORIGIN" always;
           add_header X-Content-Type-Options "nosniff" always;
           add_header X-XSS-Protection "1; mode=block" always;

     ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client.
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
    }
}
}

 

Pointing my Nvidia Shield Pro - "Emby Android TV" client at "https://embydr.mydomain.com" port 443.  I still get the same behavior. 

-Video will play just fine, but if I use ff or rw it will freeze up.   
-If i use the chapter timeline on the Emby Android TV client, to go forward or back. It works just fine.

-Other Emby clients(pointed at the same nginx/emby server) IOS, Windows PC WebUI; Emby Theater work just fine.  Skipping around on the timeline works well.  
-I also sideloaded the "Emby for Android" app onto the Nvidia Shield.  ff and rw work fine; though I miss the progressive skip forward/back that the Emby Android TV app has. But ff and rw works just as you'd expect.  Again, still pointed at the same nginx/emby server.   

None of my clients/users are allowed to do transcoding.  This is all direct play.

The problem only seems to exist when it's the Emby Android TV client, plus nginx.  Pointing  Emby Android TV directly at tcp:8096, problem goes away.

Is the "Emby Android TV" client being deprecated and moving to just "Emby for Android"?  Or is the Emby Android TV app the only one that will be on the Google Play and FireTV app stores?  If it's being deprecated, then this is really a non-issue. 

 

EmbyServer 4.7.8.0
Emby Android TV 2.0.79g

[AsheAshe 4]

Started getting this on my Shield tv, didn't used to happen but now any time i ff or rw a small buffered amount it hangs for about a minute 

[pir8radio 1292]

41 minutes ago, AngelOfTheOdd said:

Played around a bit with this today using @pir8radio's nginx configs.   Spun up a new ngnix container and pulled swag's letsencrypt's keys over.  So I'm 100% on @pir8radio's nginx.conf

 

version: "3.9"

networks:
  media-stack:
    ipam:
      driver: default
      config:
       - subnet: 172.19.1.0/24

  nginx:
    image: nginx:latest
    container_name: nginx
    volumes:
      - ${CONFDIR}/nginx/nginx.conf:/etc/nginx/nginx.conf
      - ${CONFDIR}/nginx/keys:/keys
      - ${CONFDIR}/nginx/logs:/etc/nginx/logs/
    networks:
      - media-stack
    ports:
      - 80:80
      - 443:443
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "10"

  emby-stable:
    container_name: emby
    image: emby/embyserver_arm64v8:latest
    environment:
     TZ: 'America/Chicago'
     UID: ${UID}
     GID: ${GID}
    networks:
      - media-stack
    ports:
      - "8096:8096"
      - "8920:8920"
    volumes:
      - ${CONFDIR}/emby-stable:/config
      - /GD:/GD
      - /GD/TV:/TV
      - /GD/Movies_HD:/Movies_HD
      - /GD/Movies_4K:/Movies_4K
      - /mnt/MoviesCombined:/MoviesCombined:ro
    restart: unless-stopped
    logging:
      driver: "json-file"
      options:
        max-size: "500k"
        max-file: "10"

 

cat /bsv/docker-state/nginx/nginx.conf
worker_processes  auto;

error_log  logs/error_test.log;

events {
    worker_connections  8192;
}

http {
    include       mime.types;
    default_type  application/octet-stream;
    server_names_hash_bucket_size 64;
    server_tokens off;

    ## The below will create a separate log file for your emby server which includes
    ## userId's and other emby specific info, handy for external log viewers.
    ## Cloudflare users will want to swap $remote_addr in first line below to $http_CF_Connecting_IP
    ## to log the real client IP address
    log_format  emby  '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port "$http_x_emby_authorization"';


    log_format default '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" $request_time $server_port';

    sendfile        off;  ## Sendfile not used in a proxy environment.

    gzip on;   ## Compresses the content to the client, speeds up client browsing.
        gzip_disable "msie6";

        gzip_comp_level 6;
        gzip_min_length 1100;
        gzip_buffers 16 8k;
        gzip_proxied any;
        gzip_types
            text/plain
            text/css
            text/js
            text/xml
            text/javascript
            application/javascript
            application/x-javascript
            application/json
            application/xml
            application/rss+xml
            image/svg+xml;

    proxy_connect_timeout 1h;
    proxy_send_timeout 1h;
    proxy_read_timeout 1h;
    tcp_nodelay on;  ## Sends data as fast as it can not buffering large chunks, saves about 200ms per request.

    ## The below will force all nginx traffic to SSL, make sure all other server blocks only listen on 443
	
server {
    listen 80 default_server;
    server_name _;

    return 301 https://$host$request_uri;
}

    ## Start of actual server blocks
server {

    listen [::]:443 ssl http2;  ## Listens on port 443 IPv6 with http2 and ssl enabled
    listen 443 ssl http2;       ## Listens on port 443 IPv4 with http2 and ssl enabled
    proxy_buffering off;        ## Sends data as fast as it can not buffering large chunks.

    server_name embydr.*;    ## enter your service name and domain name here example emby.domainname.com

    access_log  logs/emby.log  emby;  ## Creates a log file with this name and the log info above.

     ## SSL SETTINGS ##
        ssl_session_timeout 30m;
        ssl_protocols TLSv1.2 TLSv1.1 TLSv1;
        ssl_certificate /keys/fullchain.pem;
        ssl_certificate_key /keys/privkey.pem;
        ssl_session_cache shared:SSL:10m;

        location ^~ /swagger {   ## Disables access to swagger interface
        return 404;
}

     location / {
        proxy_pass http://emby:8096;  ## Enter the IP and port of the backend emby server here.
        client_max_body_size 1000M;  ## Allows for mobile device large photo uploads.

        proxy_hide_header X-Powered-By;      ## Hides nginx server version from bad guys.
        proxy_set_header Range $http_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header If-Range $http_if_range;  ## Allows specific chunks of a file to be requested.
        proxy_set_header X-Real-IP $remote_addr;  ## Passes the real client IP to the backend server.
        #proxy_set_header X-Real-IP $http_CF_Connecting_IP;  ## if you use cloudflare un-comment this line and comment out above line.
        proxy_set_header Host $host;  ## Passes the requested domain name to the backend server.
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;  ## Adds forwarded IP to the list of IPs that were forwarded to the backend server.

     ## ADDITIONAL SECURITY SETTINGS ##
     ## Optional settings to improve security ##
     ## add these after you have completed your testing and ssl setup ##
     ## NOTICE: For the Strict-Transport-Security setting below, I would recommend ramping up to this value ##
     ##         See https://hstspreload.org/ read through the "Deployment Recommendations" section first!   ##
           add_header 'Referrer-Policy' 'origin-when-cross-origin';
           add_header Strict-Transport-Security "max-age=15552000; preload" always;
           add_header X-Frame-Options "SAMEORIGIN" always;
           add_header X-Content-Type-Options "nosniff" always;
           add_header X-XSS-Protection "1; mode=block" always;

     ## WEBSOCKET SETTINGS ## Used to pass two way real time info to and from emby and the client.
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
    }
}
}

 

Pointing my Nvidia Shield Pro - "Emby Android TV" client at "https://embydr.mydomain.com" port 443.  I still get the same behavior. 

-Video will play just fine, but if I use ff or rw it will freeze up.   
-If i use the chapter timeline on the Emby Android TV client, to go forward or back. It works just fine.

-Other Emby clients(pointed at the same nginx/emby server) IOS, Windows PC WebUI; Emby Theater work just fine.  Skipping around on the timeline works well.  
-I also sideloaded the "Emby for Android" app onto the Nvidia Shield.  ff and rw work fine; though I miss the progressive skip forward/back that the Emby Android TV app has. But ff and rw works just as you'd expect.  Again, still pointed at the same nginx/emby server.   

None of my clients/users are allowed to do transcoding.  This is all direct play.

The problem only seems to exist when it's the Emby Android TV client, plus nginx.  Pointing  Emby Android TV directly at tcp:8096, problem goes away.

Is the "Emby Android TV" client being deprecated and moving to just "Emby for Android"?  Or is the Emby Android TV app the only one that will be on the Google Play and FireTV app stores?  If it's being deprecated, then this is really a non-issue. 

 

EmbyServer 4.7.8.0
Emby Android TV 2.0.79g

does your android client do it on my server?    login details in my profile. 

[AngelOfTheOdd 6]

5 minutes ago, pir8radio said:

does your android client do it on my server?    login details in my profile. 

Yup, same behavior.  I started up AdAstra from your server; fast forwarded about 18min.. and it's frozen; though it did start playing again after about a minute.  

[AngelOfTheOdd 6]

After a couple days of usage.. I must say, "Emby for Android" is much better than "Emby Android TV".  ff/rw works perfect every single time. But there's also a ton more options for personalizing and managing not only the client but server also.  

@Luke is "Emby for Android" going to replace the Android TV and Fire TV apps and be available/updated on from the app stores?  IMHO, it works a lot better and has a ton more features.  Or will it always be a sideload to use on Android TV devices?

[AsheAshe 4]

1 hour ago, AngelOfTheOdd said:

After a couple days of usage.. I must say, "Emby for Android" is much better than "Emby Android TV".  ff/rw works perfect every single time. But there's also a ton more options for personalizing and managing not only the client but server also.  

@Luke is "Emby for Android" going to replace the Android TV and Fire TV apps and be available/updated on from the app stores?  IMHO, it works a lot better and has a ton more features.  Or will it always be a sideload to use on Android TV devices?

Is there any downsides / loss of features by using this as it'd starting to really grind my gears freezing when forwarding