Jump to content

External Roku problems dumping tons of small transcode files / server reports connect/disconnect


BAS
Go to solution Solved by BAS,

Recommended Posts

I rebuilt my entire server this is a fresh install of Win 7. 

 

MB Server 3.0.5416.0 / Media Browser for Roku 1.64

 

External Roku connects and plays content fine, even though the server reports the user is constantly disconnecting/reconnecting. It also appears that its just dumping a bunch of tiny 15-20 sec transcode clips, the directory is currently sitting at about 700 files. I have my transcode location set to a specific path for server. Help would be appreciated to address this issue.

 

 

Server Log

 

Transcode Log

 

Link to comment
Share on other sites

techywarrior

That's normal behavior. I think that the disconnect/reconnect is a bug but I don't know where it is in the priority list tho.

 

The number of transcoding files is because of HLS. Basically it breaks the video into lots of little pieces and the player plays a "playlist" comprised of all the little pieces. This allows the server to adjust the quality based on network traffic in 30 second increments. (this is how HLS works, NOT necessarily what MB is doing with HLS). ^^ at least this is my understanding of HLS.

  • Like 1
Link to comment
Share on other sites

OK thanks for the explanation on the HLS transcoding. How often does this transcode directory get cleaned up? Is there a way to set the max size allowed?

Link to comment
Share on other sites

techywarrior

I'm not sure how often it cleans itself but I know it does. Luke would know the answers to those two questions.

Link to comment
Share on other sites

I'm still getting this disconnect/connect messages from an external Roku 2 XS user on 1.64 and Server 3.0.5421.0. Any other info I need to provide?

Link to comment
Share on other sites

  • 3 weeks later...
Redshirt

When the video completes playback the client is supposed to make an api call that tells the server to remove all the transcoding files. That can fail for various reasons, app crash, cellular dropout etc... The server does clean up those files regardless though. 

 

Expanding on Techywarriors comments. MB's implementation of HLS is directly related to getting the iOS clients approved in the Apple store. Their validator is fairly strict on how each hls segment should be formed.

Edited by Redshirt
Link to comment
Share on other sites

He just pasted the same response in two threads so I'm not even sure he understands the topics being discussed

Link to comment
Share on other sites

  • 5 weeks later...
  • Solution

The disconnect/connect messages in activity appeared to be fixed with Server Version 3.0.5464.40000 and clients on Roku 1.72 or 1.75.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...