Boxee Box as an extender? (xbmc perhaps?)

[tmiranda]

Originally Posted by grbsaaber

Got everything working. Very nice so far!!!!

Just one question how long does it take to play a file once you select it.

For me it takes almost 10 seconds or more to play the file.

Im wondering if that is normal or if I need to look at some settings or my network.

Thanks, keep up the good work

It can take even longer than 10 seconds depending on a number of variables including your network and how you have the Sage recordings organized. The delay is due to the Boxee firmware so there is little I can do about it

[tmiranda]

Originally Posted by zzo

All of my Sage TV recordings are from an HD Homerun - I installed Boxee on my Mac to try out this app as I can use another extender - however none of my recorded TV shows work.
I don't know how old the SageTV app in my Boxee is - think I initially set it up a month or so ago.
Anyway when I select a recording to watch it says 'launching player' and then just hangs there forever...
ideas??
thanks!!
Mark

I've never tried running the app on a Mac so you may be the Guinea Pig

First make sure you've set up the UNC mappings correctly. See Darci's user guide for details on how to do that. (http://code.google.com/p/sagetv-boxe...wToSetupAndUse) If you don't see thumbnails in the recordings menu odds are the UNC mapping is not correct.

If it still doesn't work go to the settings and set the logging level to debug and send me a log to look at.

Tom

[crusing]

I have it working on a mac, so it does work. Are the recordings local or on the network? You might need to look at the share perms if its on the network.

[zzo]

Thanks - I have attached the debug log - now it just won't load at all - I don't even get the 'loading player' dialog I had before - it just fails instantly.

The recordings are local - the meat of the matter in the log seems to be:

07:12:59 T:2691421984 M:431534080  NOTICE: DVDPlayer: Opening: C:\Users\Michelle\Videos\SageTV\ACharlieBrownThanksgiving-2158024-0.mpg
07:12:59 T:2691421984 M:431525888 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
07:12:59 T:2957332480 M:431517696   DEBUG: thread start, auto delete: 1
07:12:59 T:2965962752 M:431513600   DEBUG: thread start, auto delete: 0
07:12:59 T:2965962752 M:431509504  NOTICE: Creating InputStream
07:12:59 T:2965962752 M:431489024   ERROR: CDVDPlayer::OpenInputStream - error opening>>> [C:\Users\Michelle\Videos\SageTV\ACharlieBrownThanksgiving-2158024-0.mpg]
07:12:59 T:2965962752 M:431489024  NOTICE: OpenInputStream failed!
07:12:59 T:2965962752 M:431489024  NOTICE: CDVDPlayer::OnExit()
07:12:59 T:2965962752 M:431489024  NOTICE: CDVDPlayer::OnExit() deleting input stream

I also have a SageTV Placeshifter on this Mac & it can play the recording fine. Is Boxee trying to hit that path directly or thru SageTV?

thanks!!!
Mark

[tmiranda]

Originally Posted by zzo

Thanks - I have attached the debug log - now it just won't load at all - I don't even get the 'loading player' dialog I had before - it just fails instantly.

The recordings are local - the meat of the matter in the log seems to be:

07:12:59 T:2691421984 M:431534080  NOTICE: DVDPlayer: Opening: C:\Users\Michelle\Videos\SageTV\ACharlieBrownThanksgiving-2158024-0.mpg
07:12:59 T:2691421984 M:431525888 WARNING: CDVDMessageQueue(player)::Put MSGQ_NOT_INITIALIZED
07:12:59 T:2957332480 M:431517696   DEBUG: thread start, auto delete: 1
07:12:59 T:2965962752 M:431513600   DEBUG: thread start, auto delete: 0
07:12:59 T:2965962752 M:431509504  NOTICE: Creating InputStream
07:12:59 T:2965962752 M:431489024   ERROR: CDVDPlayer::OpenInputStream - error opening>>> [C:\Users\Michelle\Videos\SageTV\ACharlieBrownThanksgiving-2158024-0.mpg]
07:12:59 T:2965962752 M:431489024  NOTICE: OpenInputStream failed!
07:12:59 T:2965962752 M:431489024  NOTICE: CDVDPlayer::OnExit()
07:12:59 T:2965962752 M:431489024  NOTICE: CDVDPlayer::OnExit() deleting input stream

I also have a SageTV Placeshifter on this Mac & it can play the recording fine. Is Boxee trying to hit that path directly or thru SageTV?

thanks!!!
Mark

The Boxee app will try to access the path directly so you must remap C: to a network path, see the wiki referenced in my previous post.

[zzo]

Ok more info - I looked at the Setup page - first - NICE DOCS!
I set up the UNC paths & still a similar error - I have attached the debug log.
Via the Finder on my Mac I can connect as guest/anonymously to smb://192.168.1.76/SageTV where all of my recordings are but Boxee apparently still cannot & gives a permissions error.

10:03:03 T:2957856768 M: 53522432   DEBUG: OpenDir - Using authentication url smb://192%2e168%2e1%2e76/SageTV
10:03:03 T:2957856768 M: 53506048   DEBUG: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192%2e168%2e1%2e76/SageTV'
                                            unix_err:'d' error : 'Permission denied'
10:03:03 T:2957856768 M: 53506048   DEBUG: CFileSMB::Open - opened SageTV/ACharlieBrownThanksgiving-2158024-0.mpg, fd=-2
10:03:03 T:2957856768 M: 53936128   ERROR: InputStream: Error opening, smb://192.168.1.76/SageTV/ACharlieBrownThanksgiving-2158024-0.mpg

Unclear why Boxee is having trouble however my Mac can do it without a password as guest. Is Boxee trying to use that SMB share as some other username??
thanks!!
Mark

[tmiranda]

Originally Posted by zzo

Ok more info - I looked at the Setup page - first - NICE DOCS!
I set up the UNC paths & still a similar error - I have attached the debug log.
Via the Finder on my Mac I can connect as guest/anonymously to smb://192.168.1.76/SageTV where all of my recordings are but Boxee apparently still cannot & gives a permissions error.

10:03:03 T:2957856768 M: 53522432   DEBUG: OpenDir - Using authentication url smb://192%2e168%2e1%2e76/SageTV
10:03:03 T:2957856768 M: 53506048   DEBUG: SMBDirectory->GetDirectory: Unable to open directory : 'smb://192%2e168%2e1%2e76/SageTV'
                                            unix_err:'d' error : 'Permission denied'
10:03:03 T:2957856768 M: 53506048   DEBUG: CFileSMB::Open - opened SageTV/ACharlieBrownThanksgiving-2158024-0.mpg, fd=-2
10:03:03 T:2957856768 M: 53936128   ERROR: InputStream: Error opening, smb://192.168.1.76/SageTV/ACharlieBrownThanksgiving-2158024-0.mpg

Unclear why Boxee is having trouble however my Mac can do it without a password as guest. Is Boxee trying to use that SMB share as some other username??
thanks!!
Mark

Mark,

Boxee's SMB implementation is "challenged" to put it politely. If you look over on the Boxee forums you will see loads of people having different SMB issues.

I'm not sure what user boxee is trying to log in as but I'd guess it's not anonymous. Darci would know more about this but I suspect the user would be "boxeebox", try giving that user access and see what happens. If that doesn't work I'd suggest doing some searching on the boxee forums to see what other Mac users are doing to access SMB shares.

Tom

Edit: Look here: http://forums.boxee.tv/showthread.ph...ion#post210554

here: http://forums.boxee.tv/showthread.ph...smb+permission

here: http://forums.boxee.tv/showthread.ph...smb+permission

and here: http://forums.boxee.tv/showthread.ph...smb+permission

for some ideas. Lots of flaky things like "try it again and reboot", "turn off SMB and then turn it back on." Yuk!

[darcilicious]

Mac and SMB I don't know much about but the user name is on the Mac side, not the Boxee side so "boxeebox" isn't a great guess

What you want to do on the Mac side of the SMB stuff is to make sure that those folders allow anyone/everyone/anonymous access. More than that, I can't guide you.

BTW, the next Boxee firmware update (v1.2.3.xxxxx) should alleviate this issue for most if not all folks... I hope.

(I'm assuming zzo is doing this on a Box and not the Boxee software installed on the Mac?)

[zzo]

My setup is this: Windows 7 box running SageTV with recordings stored on a local disk. A MacBook Pro running Boxee. Am trying to verify this all works before plunking down for a Boxee Box as I would like another SageTV extender....
SO I'm sharing the SageTV recordings folder as Read-Only for 'Everyone' and 'Guest' and Boxee -> Files -> KITTY (Samba) doesn't mount the directory (KITTY is the name of my Windows box).
Clicking on KITTY causes Boxee to think about it for about 5 seconds & then it pops up a Username/Password dialog. Leaving it all blank, setting just the username to 'Guest' and even putting in a valid username/password for the Windows box still does NOT allow the share to be mounted.
So clearly this is a Boxee problem not a SageTV app problem. The samba browser clearly blows.
Meanwhile I can mount the SMB shares on my Mac itself no problem both as guest and using an actual username/password.
What's interesting is Boxee CAN mount SMB shares without a username/password from my NAS box but not from my Windows 7 box.
Guess I just need to keep playing around with the share settings on my Windows 7 box but there's not too much else to play with.
thanks!!
Mark

Originally Posted by darcilicious

Mac and SMB I don't know much about but the user name is on the Mac side, not the Boxee side so "boxeebox" isn't a great guess

What you want to do on the Mac side of the SMB stuff is to make sure that those folders allow anyone/everyone/anonymous access. More than that, I can't guide you.

BTW, the next Boxee firmware update (v1.2.3.xxxxx) should alleviate this issue for most if not all folks... I hope.

(I'm assuming zzo is doing this on a Box and not the Boxee software installed on the Mac?)

[drewg]

I'm trying to install the Boxee app on a Win7 "client" machine to a 64-bit Linux SageTV setup. I'm using all the defaults (8080, sage, frey). I use the web interface all the time for BMT, and for scheduling, etc. So it is not a firewall issue.

One thing I notice is that http://192.168.200.2:8080/ is a 404 (see screen shot). Is that a red-herring, or is that my problem?

Thanks,

Drew

[tmiranda]

Originally Posted by drewg

I'm trying to install the Boxee app on a Win7 "client" machine to a 64-bit Linux SageTV setup. I'm using all the defaults (8080, sage, frey). I use the web interface all the time for BMT, and for scheduling, etc. So it is not a firewall issue.

One thing I notice is that http://192.168.200.2:8080/ is a 404 (see screen shot). Is that a red-herring, or is that my problem?

Thanks,

Drew

Drew,

I'm assuming 192.168.200.2 is the IP address of your Sage server? If that's true then yes, that's the problem. It looks like jetty is not installed (or configured) properly. You should get a 403 (forbidden) error.

What happens when you enter http://192.168.200.2:8080/apps/

That should give you a listing of the jetty apps installed and one of them should be "sagex".

Tom

Edit: Make sure you have both "sagex-api" and "sagex-services" installed on the server.

[tmiranda]

Originally Posted by zzo

So clearly this is a Boxee problem not a SageTV app problem. The samba browser clearly blows. <snip> Guess I just need to keep playing around with the share settings on my Windows 7 box but there's not too much else to play with.
thanks!!

Unfortunately all statements are true. I'd recommend doing some more searching on the Boxee forums and asking Darci for help.

[crusing]

Don't forget to check the file level permissions as well. You will need guest to have read only on the share and in the folder/file perms.

[darcilicious]

These two posts might help:

http://forums.sagetv.com/forums/show...&postcount=459
http://forums.sagetv.com/forums/show...&postcount=461

Both listed under the Boxee Box issues section of the wiki document: http://code.google.com/p/sagetv-boxe...dUse#Boxee_Box

[drewg]

Originally Posted by tmiranda

Drew,

I'm assuming 192.168.200.2 is the IP address of your Sage server? If that's true then yes, that's the problem. It looks like jetty is not installed (or configured) properly. You should get a 403 (forbidden) error.

What happens when you enter http://192.168.200.2:8080/apps/

That should give you a listing of the jetty apps installed and one of them should be "sagex".

Tom

Edit: Make sure you have both "sagex-api" and "sagex-services" installed on the server.

Thanks... This is odd. I see what (I think) I should see at the /apps URL. See attached screen shot.

I've always thought the "404" behavior at the 8080:/ URL was odd.

I have sagex-api 7.1.9.3 and sagex-services 7.1.9.2 installed.. Is it possible I've got some old plugin installed that is causing problems? How do I get a list of plugins & their versions that I can post?

Thanks,

Drew

[tmiranda]

Originally Posted by drewg

Thanks... This is odd. I see what (I think) I should see at the /apps URL. See attached screen shot.

I've always thought the "404" behavior at the 8080:/ URL was odd.

I have sagex-api 7.1.9.3 and sagex-services 7.1.9.2 installed.. Is it possible I've got some old plugin installed that is causing problems? How do I get a list of plugins & their versions that I can post?

Thanks,

Drew

Curiouser and curiouser. Sagex looks like it is installed but I don't know why it's not working. A need to work up a testcase for you, I'll try to get to that tonight.

Tom

[stuckless]

Originally Posted by drewg

Thanks... This is odd. I see what (I think) I should see at the /apps URL. See attached screen shot.

I've always thought the "404" behavior at the 8080:/ URL was odd.

I have sagex-api 7.1.9.3 and sagex-services 7.1.9.2 installed.. Is it possible I've got some old plugin installed that is causing problems? How do I get a list of plugins & their versions that I can post?

Thanks,

Drew

Depending on if you upgraded from 6.x to 7, and you had neilm's webserver installed in 6.x, that might still be running, resulting the Jetty server not being properly installed/setup (bmt, sagex, mobile webserver, etc, all rely on Jetty)

Can you driectly access the http://server:8080/sagex/api ? (that's the sagex api url, and it will return a help page if no args are provided)

If this is a new install of Sage7 and you've only ever used the plugin manager to install stuff, then Jetty should be installed (on port 8080 by default). On startup jetty information is written to the sagetv_0.txt log file, and you see some statements about it "deploying" application and starting/creating a connector on port 8080.

[stuckless]

If you can access the sagex url (sagex/api) then try to issue a simple sagetv api command like...

http://server:8080/sagex/api?c=GetServerAddress

if that returns the hostname/address of your sagetv server, then you know the sagex-services is working.

btw... it is possible to disable the sagex-services from the sagex-services plugin configuration... maybe you disabled it at one point??

[drewg]

Originally Posted by stuckless

Depending on if you upgraded from 6.x to 7, and you had neilm's webserver installed in 6.x, that might still be running, resulting the Jetty server not being properly installed/setup (bmt, sagex, mobile webserver, etc, all rely on Jetty)

Can you driectly access the http://server:8080/sagex/api ? (that's the sagex api url, and it will return a help page if no args are provided)

If this is a new install of Sage7 and you've only ever used the plugin manager to install stuff, then Jetty should be installed (on port 8080 by default). On startup jetty information is written to the sagetv_0.txt log file, and you see some statements about it "deploying" application and starting/creating a connector on port 8080.

Yes, this was updated from 6.x, and I had neilm's web server installed. How do I tell if it is still running?

I can access the help page you reference above.

I see this in my logs ( I have debug logging enabled). Here is snippet around that time:

Tue 11/29 13:20:00.426 [SageTV@154864a] SAGEX-API: Starting Http Context
Tue 11/29 13:20:00.427 [SageTV@154864a] SAGEX-API: Updated Constrant Authentication: true
Tue 11/29 13:20:00.427 [SageTV@154864a] ::INFO:  Deploy /home/sagetv/server/jetty/contexts/sagex.xml -> org.mortbay.jetty.servlet.Context@1b45e9a{/sagex,null}
Tue 11/29 13:20:00.485 [SageTV@154864a] ::INFO:  Extract /home/sagetv/server/jetty/webapps/nielm_sagewebserver.war to /home/sagetv/server/jetty/webapps/nielm_sagewebserver/webapp
Tue 11/29 13:20:00.764 [SageTV@154864a] ::INFO:  Extract /home/sagetv/server/jetty/webapps/apps.war to /home/sagetv/server/jetty/webapps/apps/webapp
Tue 11/29 13:20:00.820 [SageTV@154864a] ::INFO:  Extract /home/sagetv/server/jetty/webapps/bmt.war to /var/tmp/sage/Jetty_0_0_0_0_8080_bmt.war__bmt__9xmt47/webapp
Tue 11/29 13:20:01.283 [SageTV@154864a] ::INFO:  Opened /home/sagetv/server/jetty/logs/2011_11_29.request.log
Tue 11/29 13:20:01.289 [SageTV@154864a] ::INFO:  Started SelectChannelConnector@0.0.0.0:8080
Tue 11/29 13:20:01.290 [SageTV@154864a] Moving starting of plugin Batch Metadata Tools - Web Interface to after Phoenix Core Services because of its dependency on it.
Tue 11/29 13:20:01.290 [SageTV@154864a] Calling start on plugin: sagex-services - SageTV Remote API Services
Tue 11/29 13:20:01.290 [SageTV@154864a] Moving starting of plugin Metadata Tools for SageTV - Commandline to after Phoenix Core Services because of its dependency on it.
Tue 11/29 13:20:01.290 [SageTV@154864a] Calling start on plugin: Sage Artifact Delete (SAD)
Tue 11/29 13:20:01.290 [SageTV@154864a] Moving starting of plugin Complementary Metadata Tools (CMT) to after Phoenix Core Services because of its dependency on it.
Tue 11/29 13:20:01.290 [SageTV@154864a] Calling start on plugin: Phoenix Core Services
Tue 11/29 13:20:01.296 [SageTV@154864a] Done starting core plugins.
Tue 11/29 13:20:01.296 [SageTV@154864a] Loading startup runnable:net.sf.sageplugins.webserver.StartServer
Tue 11/29 13:20:01.317 [SageTV@154864a] Loaded startup runnable:net.sf.sageplugins.webserver.StartServer
Tue 11/29 13:20:01.318 [PSNATMGR@8968f8] Starting UPnP NAT Manager...
Tue 11/29 13:20:01.319 [Startup-net.sf.sageplugins.webserver.StartServer@150a1ac] Starting webserver with args: [-p, 8080, -root, webserver, -t, throttles.properties, -s, servlets.properties, -r, realms.properties, -a, aliases.properties, -nohup]
Tue 11/29 13:20:01.787 [Ministry@1636311] Ministry is starting

Thanks for the help!

Drew

[drewg]

OK, I think I found what was starting the old webserver (load_at_startup_runnable_classes=net.sf.sageplugins.webserver.StartServer) in my Sage.properties. I've removed that, and still no joy.

I think I'm going to remove all these remote-api plugins & re-install them..

Drew