Jump to content

Movies won't open in Media Centre

jhs39

By jhs39
in Roku

 Share

Recommended Posts

jhs39

jhs39 13

Posted
Posted

I have a number of movies that will not play in Media Centre.  As soon as I try to open them the app crashes and I am thrown back out to the channel select screen.  But these same movies play fine in Media Browser.  Any idea what is going on?  I'm not sure how to attach my log file since it's much larger than 39.95(KB).  

 

Joe Smart

 

 

im85288

im85288 1493

Posted
Posted (edited)

The log files are normally not of much use, the best bet is for me to connect to your server to attempt to debug it. Is it happening for the same movies? Are you able to PM me your server address with a user created for me to test? Version 1.15 is due out soon(ish)..Roku have been testing it for almost 2 weeks now which brings in quite a few bug fixes but if possible I'd like to see what exact issue your having.

 

When you say crashing do you get as far as seeing the screen details and pressing "Play" ?

 

HnbEuzb.jpg

Edited by im85288
jhs39

jhs39 13

Posted
  • Author
Posted

It happens with the same movies repeatedly.  Roku app crashes when I hit play on the titles--I get as far as the play button but no further.  I don't know how to create a special user for you to access my server and I'm not honesty sure that I'm comfortable giving you access to my computer.  It seems potentially like a dangerous security breach for me to do something like that.  

im85288

im85288 1493

Posted
Posted (edited)

That's your choice completely. I cannot debug/see what is going wrong without actually connecting to your server (not computer) so this will have to be sorted out if I can reproduce it locally or another user reports it. Just FYI, in MediaBrowser on the main page it shows you what the remote server address is:

 

GrCs9fw.png

 

Using this address you can give it to others to access your server from outside your house. If you create them a user that does not have rights to mess with your server then you'll be quite safe knowing they can do no harm to it.

 

Cheers

Edited by im85288
jhs39

jhs39 13

Posted
  • Author
Posted

I'm not a computer expert but connecting to the server remotely still means you are connecting to my hard drive.  If you did something other than debug the server I don't even know how I would be able to tell.  If that's my only option I'll wait for the next release and hope for the best.  Thanks anyway.

im85288

im85288 1493

Posted
Posted

Like I said if you feel it's a security breach then that's your decision. As for other options, perhaps you can list the names of the movies that are causing it to crash along with showing the media info from the web client for the offending movie..and maybe even share the movie file itself that causes the problem. Any logs may also help. Basically I need as much info as you can provide

jhs39

jhs39 13

Posted
  • Author
Posted

The offending films where I have noticed the issue are all Japanese pornographic films.  If you want me to share one of the films that is crashing I would be fine with that if you want to let me know exactly how to do that.

im85288

im85288 1493

Posted
Posted

Hmm I'm guessing they didn't get scraped properly or something. You said it plays fine in the web client? You can share it via Dropbox or whatever means you feel comfortable with

jhs39

jhs39 13

Posted
  • Author
Posted

The files don't just play fine on the web client--they play fine on Roku via the older Media Browser channel--they just don't play on the newer premium version that I purchased.  I'll see if I have enough storage available to use Dropbox.   

im85288

im85288 1493

Posted
Posted

I can put you back on media browser ++ if you prefer that version. Just let me know.

jhs39

jhs39 13

Posted
  • Author
Posted

I'm uploading two of the files to Dropbox but it looks like its going to take a while.  After they're uploaded and I figure out how to share files I'll provide a link.

jhs39

jhs39 13

Posted
  • Author
Posted

I'll stick with Media Centre.  I can always use the old Media Browser when I run in to problems with specific files.  Most things play fine.  

jhs39

jhs39 13

Posted
  • Author
Posted

Thanks for the offer.  

jhs39

jhs39 13

Posted
  • Author
Posted

I'm getting errors when I try to upload large files to Dropbox so I guess that isn't going to work out.

im85288

im85288 1493

Posted
Posted

Well hopefully version 1.15 resolves this for you, it should be released any day now as Roku are taking their time approving apps at the minute.

 

Out of interest, can you screenshot the media info for the offending movie(s)? Does it display rotating backgrounds on the video details screen?

 

9JXoTRP.jpg

Cheesegeezer

Cheesegeezer 3096

Posted
Posted

I'm confused here... Is this an issue with Roku or MBC?

 

If its MBC i'll guarantee you have codec problems. Roku... No idea.

im85288

im85288 1493

Posted
Posted

It's a problem with MB Media Centre (an unofficial roku client) not to be confused with MBC :)

Cheesegeezer

Cheesegeezer 3096

Posted
Posted

It's a problem with MB Media Centre (an unofficial roku client) not to be confused with MBC :)

Right.. Ok!!

 

Why is this client named this.... It does obviosly confuse issues.

im85288

im85288 1493

Posted
Posted

I liked the name, and tbh this is the first I've heard off any confusion!

 

I'll keep it in mind though and see if it causes any other confusions in the future. Cheers.

jhs39

jhs39 13

Posted
  • Author
Posted

It's getting much worse.  Now about half of my movies, including movies I watched with no problems in the past, will not open.  There appears to be some kind of codec issue.  The movies start to open in Media Centre and the progress bar gets to the end but the movie never actually opens.  I've tried watching 4 movies today so far where that happened.

 

 

 
2014-07-03 16:40:32.8963 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 219.0125 ms
2014-07-03 16:40:33.4174 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 519.0297 ms
2014-07-03 16:40:42.6769 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 11.0006 ms
2014-07-03 16:40:43.3389 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 661.0378 ms
2014-07-03 16:40:43.5969 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 256.0147 ms
2014-07-03 16:40:44.4960 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 897.0513 ms
2014-07-03 16:40:45.0760 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 578.0331 ms
2014-07-03 16:40:46.2931 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1215.0695 ms
2014-07-03 16:40:47.1841 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 888.0508 ms
2014-07-03 16:40:48.2122 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1026.0587 ms
2014-07-03 16:40:48.8382 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 622.0356 ms
2014-07-03 16:40:49.1083 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 268.0153 ms
2014-07-03 16:40:49.7083 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 598.0342 ms
2014-07-03 16:40:50.7333 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1023.0585 ms
2014-07-03 16:40:51.4024 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 667.0381 ms
2014-07-03 16:40:51.6164 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 212.0121 ms
2014-07-03 16:40:52.3724 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 753.0431 ms
2014-07-03 16:40:52.8875 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 513.0293 ms
2014-07-03 16:40:52.8875 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 2.0001 ms
2014-07-03 16:40:54.3196 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1426.0816 ms
2014-07-03 16:40:54.8576 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 536.0306 ms
2014-07-03 16:40:55.3996 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 539.0308 ms
2014-07-03 16:40:56.7197 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1317.0753 ms
2014-07-03 16:40:57.3727 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 650.0372 ms
2014-07-03 16:40:57.9098 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 535.0306 ms
2014-07-03 16:40:58.8668 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 954.0545 ms
2014-07-03 16:40:59.3008 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 432.0247 ms
2014-07-03 16:41:00.3509 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1048.0599 ms
2014-07-03 16:41:01.6830 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57132. Response time: 1330.0761 ms
2014-07-03 16:41:17.8929 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 3.0002 ms
2014-07-03 16:41:42.8893 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 2.0001 ms
2014-07-03 16:42:07.8918 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 4.0002 ms
2014-07-03 16:42:32.8882 Debug - HttpServer: HTTP Response 200 to 192.168.1.130:57131. Response time: 5.0003 ms
jhs39

jhs39 13

Posted
  • Author
Posted

Rebooting the Roku might have taken care of the issue.  Sorry. :(

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
 Share
Go to topic listing
×
×
  • Create New...