|
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
|
||||
|
||||
Full screen second monitor/tv
I've been running my TV in dual monitor mode. SageTV does a good job of going to full screen on the monitor its window is on, but the size it uses for full screen seems dependent on the resolution of the primary monitor. This means I have to keep both the monitor and TV at the same resolution, if I want full screen to work right.
|
#2
|
|||
|
|||
That's the same boat I'm in. What I do is use SageTV in windowed mode on the second monitor. I just size the window so that the window's borders are not seen on my TV. This allows me to run my monitor and TV at different resolutions and still have what appears to be a full screen picture on my TV.
Before 1.4.9 Sage would forget what monitor/TV it was on. So whenever it was shutdown or the computer was rebooted Sage would show up on my computer monitor. As of 1.4.9 Sage rembembers it's size and monitor(TV) placement correctly. The only downside to this is if you wish to use Sage on your computer's monitor you mess up all your carefull window positioning for TV. I'm thinking of buying a client license so that SageTV can be a server and that window will always stay in place. I'd then use the client whenever I wished to view Sage on my computer monitor. Does anyone else have a better/easier solution? General system info:I have a GeForce4 Ti4600 with one DVI(hooked to LCD), one VGA(unused), and a SVHS output(TV). I'm using the latest Nvidia drivers, WinXP Pro SP1, DX9a and usually run SageTV in VMR mode. |
#3
|
|||
|
|||
I'm running into this exact same problem now on my workstation that has the client running on it.
Any better workarounds for this issue, or do we know if it's fixed in version 2? Thanks,
__________________
--FJC |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|