Boxee Box as an extender? (xbmc perhaps?)

[darcilicious]

I will turn on debug logging and try enabling guest access (is read only enough?)

That's what I did on my WHS, read-only for guest. My share is \\server\videos and recordings are stored in \\server\videos\sagetv -- I would recommend applying the change to the top level folder (e.g. "videos" in my case) and not just the recordings folders (unless it is the top level folder, of course).

[darcilicious]

Originally Posted by KeithAbbott

Boxee software.

Yeah, that's probably the difference... I think there are issues with the Box resolving hostnames from within apps.

Tom (one of the developers) specifically recommended using IP addresses and that's how it's documented in the wiki, regardless of the platform (the software version might have a similar issue if/when it gets updated the 1.x, similar to what's running on Boxes now).

[tmiranda]

Originally Posted by darcilicious

However, if you can view the list of recordings, then the SageTV for Boxee app is communicating with the SageTV server since that's where the list is coming from.

Yes and No. The list of recordings is obtained using sagex/jetty. So if you get a list of recordings it means the app can communicate with the Sage server via sagex/jetty.

When the recording information is fetched from the server the path to the mediafile (the physical file on disk) will be in the format that you've specified in the Sage setup. (So if you set your recording directory to be w:\recordings the path to the mediafile will contain w:\recordiings\filename.mpg. If you set your recording directory to \\Server\directory the path to the mediafile will contain \\Server\directory\filename.mpg.)

Before the file is played the app converts the path to the mediafile based on what you've setup in the UNC Mappings setting. I'm pretty sure that if the Box can't resolve \\Server there is no wya to remap this to an IP address. I'll open a ticket on this to make sure we get it fixed.

[tmiranda]

Originally Posted by KeithAbbott

Boxee software.

As Darci said, that's a big difference. The Box and the software client resolve IP addresses in completely different ways.

[bkavanaugh]

Originally Posted by tmiranda

When the recording information is fetched from the server the path to the mediafile (the physical file on disk) will be in the format that you've specified in the Sage setup. (So if you set your recording directory to be w:\recordings the path to the mediafile will contain w:\recordiings\filename.mpg. If you set your recording directory to \\Server\directory the path to the mediafile will contain \\Server\directory\filename.mpg.)

So, to be clear, I will need to:

1) On the SageTV server, change the recording directories from \\ServerName\Share to \\IPAddress\Share
2) Map them in SageTV\Setup on the Boxee Box as described elsewhere in this thread
3) Both

?

[darcilicious]

Originally Posted by tmiranda

Before the file is played the app converts the path to the mediafile based on what you've setup in the UNC Mappings setting. I'm pretty sure that if the Box can't resolve \\Server there is no wya to remap this to an IP address. I'll open a ticket on this to make sure we get it fixed.

For what it's worth, my recordings setting in SageTV server is: \\SERVERNAME\Videos\SageTV and I have no problems with playback from the recordings browser with guest access enabled on \\SERVERNAME\Videos.

But I also have \\SERVERNAME\Vidoes\CurrentTV and other similar folders added as Local Sources to Boxee so maybe that makes it possible for Boxee to resolve \\SERVERNAME in the SageTV app -- I really don't know.

[tmiranda]

Originally Posted by darcilicious

For what it's worth, my recordings setting in SageTV server is: \\SERVERNAME\Videos\SageTV and I have no problems with playback from the recordings browser with guest access enabled on \\SERVERNAME\Videos.

But I also have \\SERVERNAME\Vidoes\CurrentTV and other similar folders added as Local Sources to Boxee so maybe that makes it possible for Boxee to resolve \\SERVERNAME in the SageTV app -- I really don't know.

Darci,

I don't know either Take a look at this discussion I had with Slugger http://code.google.com/p/sagetv-boxe...il?id=71&can=1

[darcilicious]

Except, that's for the jetty authentication, where I do indeed use the IP address in the SageTV for Boxee app.

For playback based on the SageTV recordings setting using UNC paths, the server name works for me...

[tmiranda]

Originally Posted by bkavanaugh

So, to be clear, I will need to:

1) On the SageTV server, change the recording directories from \\ServerName\Share to \\IPAddress\Share
2) Map them in SageTV\Setup on the Boxee Box as described elsewhere in this thread
3) Both

?

Do the first, but it will only help with new recordings. The existing recordings will still have \\ServerName in them. I opened a ticket to fix this issue, the app needs to handle \\ServerName in the MediaFile path. Once the fix is made you'll need to do #2 (and not #1).

[darcilicious]

the app needs to handle \\ServerName in the MediaFile path.

this already works for me... but no else can get it to work in the current version of the app?

[gplasky]

Server names work for me. Using USC paths in both Sage and the Boxee PC app.

Gerry

[darcilicious]

Whew. I really hate being "special" Er, anyone else on the Box have it work? PC version is much better and resolving hostnames... so not a good test case.

[tmiranda]

Originally Posted by darcilicious

Whew. I really hate being "special" Er, anyone else on the Box have it work? PC version is much better and resolving hostnames... so not a good test case.

I think it will depend on your network config. Look at the entry (5th from last) in the issue I posted a link to where Slugger explains how to use "nslookup" to see if the DNS can resolve the hostname.

[darcilicious]

As a former Unix admin, I've got a little experience with nslookup For what it's worth, my Boxee Box's DNS server is set to one of Google's public DNS servers -- which of course doesn't know anything about hostnames on my local network

Somehow, my Box is resolving my servername just fine. *shrug* Would like to hear the experiences from other Box owners about this...

[Slugger]

Originally Posted by darcilicious

As a former Unix admin, I've got a little experience with nslookup For what it's worth, my Boxee Box's DNS server is set to one of Google's public DNS servers -- which of course doesn't know anything about hostnames on my local network

Somehow, my Box is resolving my servername just fine. *shrug* Would like to hear the experiences from other Box owners about this...

Didn't you say at one point that you also added some of your Windows shares to Boxee? If so, then the Boxee SMB client probably is active/has cached the NetBIOS names and that's why the box can resolve the hostnames. If you don't have any Windows shares registered with Boxee then the Samba client on the box probably isn't active therefore you'd need a proper DNS server on the LAN to resolve the hostnames since I've been told you can't edit the /etc/hosts file on the device.

[darcilicious]

Yes and the Box also discovers all my other windows boxes on my network -- I should think those are cached as well even though I don't explicitly add any of them as local sources.

[Deacon Crusher]

Just got a boxee box and set it up with sage using the wiki directions all is good except for some issue with UNC mappings so a question or 2 and an example or 2.

In sage server (a win 7 box) my recording paths are
D:\sage-d
E:\sage-e
H:\sage-h

They are shared as
\\serverip\sage-d
\\serverip\sage-e
etc.

So, inside the sage app on boxee in the unc mappings area I entered

D:\sage-d,\\192.168.167.13\sage-d

So, 1st question, is the above correct?

2nd question, how do you add the other shares? It seems like you can only have one entry, so I tried to enter them as one long string with spaces separating the 3 entries. That isn't working but of course that could be because my base syntax isn't working or the shares aren't allowing access or because the space doesn't work. So, will take whatever advice you all have.

Will say this is a nifty setup as I like the boxee interface and device and you guys have done an amazing job getting the sage app to look like sage on the boxee, very cool.

thanks

[darcilicious]

Just use a semi-colon between the pairs of mappings -- I'll update the docs to include an example like this as well.

[Deacon Crusher]

Found a post that said use ; between multiple unc path mappings.

Did that and problem persists.

[darcilicious]

What isn't working exactly? After you enter one or more mappings and go to TV->Recordings -- do you see any recordings?