![]() |
|
SageTV Software Discussion related to the SageTV application produced by SageTV. Questions, issues, problems, suggestions, etc. relating to the SageTV software application should be posted here. (Check the descriptions of the other forums; all hardware related questions go in the Hardware Support forum, etc. And, post in the customizations forum instead if any customizations are active.) |
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#1
|
|||
|
|||
Network Encoder HowTo
Greetings,
I read through the manual: Quote:
Thanks! B |
#2
|
||||
|
||||
Some of your recent posts were in the Linux section of the forum... by any chance, are you trying to use a Linux system as one or both parts of the the network encoder setup?
- Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
#3
|
|||
|
|||
by chance I am, as the slave
The setup docs aren't clear as far as platform requirements, and the Linux FAQ says it can be done. B PS, I am asking from the master server point of view which is why this is not posted in LINUX forum. |
#4
|
||||
|
||||
There is a known issue when using a Linux setup as the network encoder for a Windows main server. Right now, it has to have Linux on both sides of the network encoder setup w/the smae file path that they can each see directly.
- Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
#5
|
|||
|
|||
For my own edification, it sounds like the guide on both sides needs to be configured the same as well as recording paths? I couldn't tell from the other threads how specifically to set up the master server. Isn't it the one responsible for writing files to the file share?
Supposing both sides were the same. Either windows or linux, etc. TIA B |
#6
|
||||
|
||||
If I could guess, I'd say the server just passes the recording directory on to the slave, if these aren't the same OS, paths are different format (ie //server/share doesn't work on Linux, at least not out of the box).
I think there would need to be some mapping done on one side or the other to map between linux paths and Windows paths, and that's not being done at the moment. |
#7
|
||||
|
||||
All video sources, channel lineups, and recording directories must be configured on the primary server, since that's where the unified EPG lives and where recordings are scheduled. Whether they also need to be configured in parallel on the network encoder I don't know, having never done it, but at a guess I don't see why they would. In theory all the encoder should need to do is tell the primary what capture devices it has available (per Device Manager), so they can show up as configuration candidates on the primary's Video Sources screen. After that, the primary server manages everything.
__________________
-- Greg |
#8
|
|||
|
|||
Quote:
Quote:
B PS. Thanks for the replies |
#9
|
||||
|
||||
Quote:
|
#10
|
||||
|
||||
Quote:
There is one caveat here: I haven't set up network tuners either, so I'm just passing along the instructions I was given, as I understand them. The manual section for this was proof-read by someone who knows very well how this all works, though. ![]() - Andy
__________________
SageTV Open Source v9 is available. - Read the SageTV FAQ. Older PDF User's Guides mostly still apply: SageTV V7.0 & SageTV Studio v7.1. - Hauppauge remote help: 1) Basics/Extending it 2) Replace it 3) Use it w/o needing focus - HD Extenders: A) FAQs B) URC MX-700 remote setup Note: This is a users' forum; see the Rules. For official tech support fill out a Support Request. |
#11
|
|||
|
|||
If SageTV were to use http://jcifs.samba.org/ as a loadable module, theoretically it could frame the request the same on both platforms? I am assuming this would require something more than loading it as a module, but maybe someone with better working knowledge of file i/o in SageTV could chime in.
B |
#12
|
|||
|
|||
Code:
mkdir /opt/sagetv/server/\\\\sagetv-server\\sagetv Code:
mount -t cifs //sagetv-server/sagetv /opt/sagetv/server/\\\\sagetv-server\\sagetv -o user=username,pass=password,domain=domainname Based on the conversation above, I need to reconfigure my channel lineups etc on the Windows box and strip down the config on the linux box. right? Back to fiddling.. |
#13
|
||||
|
||||
Remember, the conversation above is all speculation.
|
#14
|
|||
|
|||
Right, so is my ability to make this work.
![]() |
#15
|
|||
|
|||
I think I figured it out mostly..
I will have to test later, unless someone else can confirm in the meantime. This would not be an appropriate long term solution as it, but it might get folks past the hurdle. Windows would allow $FOO as a directory name. In linux $FOO would be treated as a variable. So if FOO was exported to /var/media/tv/ (trailing slash important) and /var/media/tv was mounted to your windows share for tv recordings.. It should work. The even better part is that $FOO\recordingfilename.mpg from Windows is what linux needs to make this work. I created a dir in linux called tv and did: Code:
export DIR="tv/" echo hi > $DIR\hello.txt The only items I was unable to confirm this morning:
Thoughts? My test later will be with a server setup on my son's pc. If it works, I will use junction link magic to point the directories to their actual locations. btw - If you are running Vista and presumably server 2008 junctions are built in to the OS now. B |
#16
|
|||
|
|||
Thought about it some more..
Here's what I can do On windows set path to be: \\server\share\a$VAR \\server\share\b$VAR etc. On linux create directory \\server\share\a... export $VAR = "/" mount \\server\share\a\$VAR to new dir. Benefits: allows me to keep unc paths for windows clients. Now the question is: Where will SageTV on linux think the dir \\server\share\a is located? B |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Converting SageTV to network encoder | vividweb | SageTV Software | 0 | 11-14-2006 11:56 AM |
Sage network Encoder and Sage failure? | nyplayer | SageTV Software | 1 | 09-27-2006 06:47 AM |
Help with Network Encoder | srothwell | SageTV Software | 7 | 09-13-2006 11:25 AM |
Network Encoder Questions | jamjam | SageTV Software | 3 | 07-04-2006 08:17 AM |
EXETunerPlugin, Sage 4 and network encoder | vuego | SageTV Software | 0 | 12-11-2005 02:47 PM |