Jump to content

Recommended Posts

Posted

let's keep hls on since that is the default setting, thanks.

Posted

Forgot I turned it off earlier.

 

Same file - HLS back on

 

Ok, I'm pretty sure this file is fixed in beta that the beta group is currently testing.

cgrey000
Posted

Ok, I'm pretty sure this file is fixed in beta that the beta group is currently testing.

Will watch for a public release.

 

Assuming, the fix still requires subs to be off?

 

Thanks Luke!

Posted

yes it does

CBers
Posted (edited)

FTV updated to v1.0.30a.

Having a problem playing a movie (Avatar).

Tried starting at a specific chapter, but all I got was a spinning circle.

Backed out and tried again, but still only the spinning circle.

Backed out again and tried starting from the beginning, but nothing.

The dashboard shows it got a play request, but it never started playback.

The ffmpeg process was only using 10% (un-throttled) when I checked.

I restarted the FTV and Emby server and tried again and eventually it started playback after 3 or 4 minutes.

Skipping forward to a chapter causes the slow playback start-up again.
 

Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))

In the transcode log, FPS is really low, around 26. Maybe due to the server scanning the library, as the Media.Browser process was ~46% at the time ffmpeg was running at ~10%.

Logs:

 

Server

Transcode

Transcode

 

MediaInfo:

 

Capture1054.jpg

 

.
 

Edited by CBers
dark_slayer
Posted

How much does it cost to unlock playback in the app for non-supporters?

CBers
Posted

How much does it cost to unlock playback in the app for non-supporters?

If you become an Emby supporter, you'll have access to more than just Android TV playback

dark_slayer
Posted

I'm a supporter, that wasn't the question

CBers
Posted

I'm a supporter, that wasn't the question

Fair enough.

 

If you want to test, before anyone else replies, remove your supporter key from the server and then see how much it is on your device.

CBers
Posted

FTV updated to v1.0.30a.

 

Having a problem playing a movie (Avatar).

 

Tried starting at a specific chapter, but all I got was a spinning circle.

 

Backed out and tried again, but still only the spinning circle.

 

Backed out again and tried starting from the beginning, but nothing.

 

The dashboard shows it got a play request, but it never started playback.

 

The ffmpeg process was only using 10% (un-throttled) when I checked.

 

I restarted the FTV and Emby server and tried again and eventually it started playback after 3 or 4 minutes.

 

Skipping forward to a chapter causes the slow playback start-up again.

 

Stream mapping:
  Stream #0:0 -> #0:0 (h264 (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))
In the transcode log, FPS is really low, around 26. Maybe due to the server scanning the library, as the Media.Browser process was ~46% at the time ffmpeg was running at ~10%.

 

Logs:

 

Server

Transcode

Transcode

 

MediaInfo:

 

Capture1054.jpg

 

.

Seeing the same issue on the Nexus Player as well (v1.0.30g).

 

Something awry with the movie, as other videos seem you play OK?

dark_slayer
Posted (edited)

Surely somebody knows how much it costs. No ftv in the house . . . will have to ask my relatives . . . and they will have recall their Amazon passwords ;)

Edited by dark_slayer
rblackhaw
Posted

Surely somebody knows how much it costs. No ftv in the house . . . will have to ask my relatives . . . and they will have recall their Amazon passwords ;)

 

 

fr_129.jpg

  • Like 1
dark_slayer
Posted

Thanks

Posted
In the transcode log, FPS is really low, around 26. Maybe due to the server scanning the library, as the Media.Browser process was ~46% at the time ffmpeg was running at ~10%.

 

There is your answer right there.

 

This really has nothing to do with the app.  The server is simply not able to deliver the video fast enough.

CBers
Posted

There is your answer right there.

 

This really has nothing to do with the app. The server is simply not able to deliver the video fast enough.

I know, but I don't understand why.

 

I think Emby itself was hogging the CPU stopping ffmpeg from processing quicker.

 

I don't use any throttling.

 

It's a wierd situation.

Posted

Your machine simply isn't capable of transcoding a high bitrate source like Avatar while simultaneously doing a library scan.  I think that is the real answer.

CBers
Posted (edited)

Perhaps, but it is a Quad-Core, so should do.

 

I normally play movies via the Samsung Smart TV app as it direct plays.

 

.

Edited by CBers
paul777
Posted

Your machine simply isn't capable of transcoding a high bitrate source like Avatar while simultaneously doing a library scan.  I think that is the real answer.

Perhaps the library scan should be run on a lower priority thread than the transcoding?

  • Like 2
Posted

If you guys could take a moment to review the app in the amazon store, it means a lot to us. Thank you :)

  • Like 1
CBers
Posted

Your machine simply isn't capable of transcoding a high bitrate source like Avatar while simultaneously doing a library scan. I think that is the real answer.

It seems the problem is that neither the NP or FTV will stream copy the movie so has to transcode it, whereas my little Now TV box (Roku LT) does.

 

Stream mapping:
  Stream #0:0 -> #0:0 (copy)
  Stream #0:1 -> #0:1 (ac3 (native) -> aac (native))

As a consequence, the playback is a lot quicker to start, and the FPS is higher due to only the audio being transcoded.

 

frame=  370 fps=148 q=-1.0 size=N/A time=00:24:15.59 bitrate=N/A    
frame=  487 fps=162 q=-1.0 size=N/A time=00:24:20.30 bitrate=N/A    
frame=  568 fps=162 q=-1.0 size=N/A time=00:24:23.59 bitrate=N/A    
frame=  655 fps=164 q=-1.0 size=N/A time=00:24:27.24 bitrate=N/A    
frame=  761 fps=169 q=-1.0 size=N/A time=00:24:31.91 bitrate=N/A    
frame=  841 fps=168 q=-1.0 size=N/A time=00:24:35.17 bitrate=N/A    

So it may be my Quad-Core PC isn't "man-enough" to transcode to the NP/FTV, but it only has to do that due to the limitations of the target devices.

paul777
Posted

@@CBers The reason that video is transcoding is probably because it is set as Level 41 by whatever encoded it, even though the bitrate is within spec for level40 (Handbrake sets level 41 by default). The FTV only supports level 40 so it is being transcoded. I see this with a lot of my videos and have tested "fixing" it by removing the check on the level on the server where is makes the transcoding decision and indeed videos then play fine without transcoding. Ultimately I think we need an override of the check to allow level 41 videos where bitrate is within spec for level40. Difference is the levels for reference is here http://en.wikipedia.org/wiki/H.264/MPEG-4_AVC#Levels

  • Like 2
CBers
Posted

removing the check on the level on the server

Where's that option?

Posted

Where's that option?

 

It isn't an option.  He modified the code to test it.

Guest
This topic is now closed to further replies.
×
×
  • Create New...