I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
Second problem: xine does not work with vdr mplayer plugin (mplayer cannot access X, hence no video). Are there any alternatives?
I wonder if there are any solutions for this? I’m back to using softdevice, but it does not compile with latest ffmpeg, plus segfaults every now and then.
Peter
Hi, Try xineliboutput.
2009/4/28, Peter zelts@ruksis.com:
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
Second problem: xine does not work with vdr mplayer plugin (mplayer cannot access X, hence no video). Are there any alternatives?
I wonder if there are any solutions for this? I’m back to using softdevice, but it does not compile with latest ffmpeg, plus segfaults every now and then.
Peter
I tried. It compiles OK but produces choppy video full of artifacts. VDR version 1.7.6, CVS xineliboutput.
-----Original Message-----
Try xineliboutput.
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
On Tue, Apr 28, 2009 at 12:56 AM, Peter zelts@ruksis.com wrote:
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
In my tv script I do this before starting xine: until [ -e "/tmp/vdr-xine/stream" ]; do sleep 1; done
This waits until vdr-xine has started before loading xine itself and resolves the problem of delayed startups.
Second problem: xine does not work with vdr mplayer plugin (mplayer cannot access X, hence no video). Are there any alternatives?
I'm using VDR-1.7.6 with xine-0.9.1 and the mplayer plugin just fine. Maybe you're missing the required mplayer.sh(.conf)?
Thanks for the tv script tidbit! However that wont help if vdr backend restarts while xine frontend is active.
My mplayer works just fine with softdevice, but not with vdr-xine: I get no video (but audio is fine). Maybe I have to run vdr backend inside X session as well?
-----Original Message----- From: VDR User [mailto:user.vdr@gmail.com] Sent: Tuesday, April 28, 2009 5:13 PM To: VDR Mailing List Subject: Re: [vdr] Best practices for running vdr-xine
On Tue, Apr 28, 2009 at 12:56 AM, Peter zelts@ruksis.com wrote:
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
In my tv script I do this before starting xine: until [ -e "/tmp/vdr-xine/stream" ]; do sleep 1; done
This waits until vdr-xine has started before loading xine itself and resolves the problem of delayed startups.
Second problem: xine does not work with vdr mplayer plugin (mplayer cannot access X, hence no video). Are there any alternatives?
I'm using VDR-1.7.6 with xine-0.9.1 and the mplayer plugin just fine. Maybe you're missing the required mplayer.sh(.conf)?
I've recently taken a different approach altogether.
I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, pictures, music, weather, radio etc etc and TV. When you select TV, it launches vdr-xine.
I wanted a high quality graphical (open-gl) look - and the ability to play music playlists while cycling through my photo collection.
VDR, vdr-xine and mms seem to work very well together too....
----- Original Message ----- From: "Peter" zelts@ruksis.com To: "'VDR Mailing List'" vdr@linuxtv.org Sent: Wednesday, April 29, 2009 4:13 AM Subject: Re: [vdr] Best practices for running vdr-xine
Thanks for the tv script tidbit! However that wont help if vdr backend restarts while xine frontend is active.
My mplayer works just fine with softdevice, but not with vdr-xine: I get no video (but audio is fine). Maybe I have to run vdr backend inside X session as well?
-----Original Message----- From: VDR User [mailto:user.vdr@gmail.com] Sent: Tuesday, April 28, 2009 5:13 PM To: VDR Mailing List Subject: Re: [vdr] Best practices for running vdr-xine
On Tue, Apr 28, 2009 at 12:56 AM, Peter zelts@ruksis.com wrote:
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
In my tv script I do this before starting xine: until [ -e "/tmp/vdr-xine/stream" ]; do sleep 1; done
This waits until vdr-xine has started before loading xine itself and resolves the problem of delayed startups.
Second problem: xine does not work with vdr mplayer plugin (mplayer cannot access X, hence no video). Are there any alternatives?
I'm using VDR-1.7.6 with xine-0.9.1 and the mplayer plugin just fine. Maybe you're missing the required mplayer.sh(.conf)?
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Tue, Apr 28, 2009 at 1:20 PM, Simon Baxter linuxtv@nzbaxters.com wrote:
I've recently taken a different approach altogether.
I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, pictures, music, weather, radio etc etc and TV. When you select TV, it launches vdr-xine.
I wanted a high quality graphical (open-gl) look - and the ability to play music playlists while cycling through my photo collection.
VDR, vdr-xine and mms seem to work very well together too....
Interesting. Do you have a howto for this? I'm sure I know some guys who would like to try it as an alternative to xbmc+VDR.
Thanks, Derek
VDR User wrote:
On Tue, Apr 28, 2009 at 1:20 PM, Simon Baxter linuxtv@nzbaxters.com wrote:
I've recently taken a different approach altogether.
I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, pictures, music, weather, radio etc etc and TV. When you select TV, it launches vdr-xine.
I wanted a high quality graphical (open-gl) look - and the ability to play music playlists while cycling through my photo collection.
VDR, vdr-xine and mms seem to work very well together too....
Interesting. Do you have a howto for this? I'm sure I know some guys who would like to try it as an alternative to xbmc+VDR.
Has anybody made some kind of pros and cons analysis between vdr-xine and xineliboutput. Which is better or are they just different ?
On Wednesday 29 April 2009, Lauri Tischler wrote:
Has anybody made some kind of pros and cons analysis between vdr-xine and xineliboutput. Which is better or are they just different ?
I've tried to set up *something* that would give me a picture on X11, the old Hauppauge cards only have s-video outputs and, well, today with HDMI and FullHD projectors that just doesn't cut it anymore.
I compiled and installed xineliboutput-1.0.4 and it was really trivial to get going. I use http streaming to a Phonon/Xine based Qt client on the same system and stuff kind of works. Half the channels never give any picture even though they tune just fine on VDR and normal s-video watching shows them just fine. Also the OSD isn't working making normal VDR use a hassle and I'm forced to switch the the s-video side to see EPG, timers etc.
Perhaps the supplied vdr-sxfe (or something like that) binaries work better, but from my initial tests that client didn't show most channels either.
So xineliboutput can't be what budget card people use, so I guess it's time to test vdr-xine. My initial gut feeling is that VDR isn't meant for X11 output at all, and it just happens to be possible to kludge it somehow.
I'd be extremely happy to be larted into submission so that I see a light though. :)
I use xineliboutput, permanently on my vdr, with xvmc enabled on my old nvidia 440 MX card. however only on SD mpeg2 broadcasts. It does provide some multimedia playback on other formats, which is useful. Normal vdr recordings are a bit of a pain, since fast forwarded/rewind doesn't work as you would expect with softdevice. If my vdr loses signal for a minute, I have to restart VDR, perhaps I should just try restarting xineliboutput. It is good enough for what I use. I didn't see any support for a vdr menu to play back other multi media content in vdr-xine, so there for never used it.
On 29/04/2009, Jan Ekholm jan.ekholm@smultron.net wrote:
On Wednesday 29 April 2009, Lauri Tischler wrote:
Has anybody made some kind of pros and cons analysis between vdr-xine and xineliboutput. Which is better or are they just different ?
I've tried to set up *something* that would give me a picture on X11, the old Hauppauge cards only have s-video outputs and, well, today with HDMI and FullHD projectors that just doesn't cut it anymore.
I compiled and installed xineliboutput-1.0.4 and it was really trivial to get going. I use http streaming to a Phonon/Xine based Qt client on the same system and stuff kind of works. Half the channels never give any picture even though they tune just fine on VDR and normal s-video watching shows them just fine. Also the OSD isn't working making normal VDR use a hassle and I'm forced to switch the the s-video side to see EPG, timers etc.
Perhaps the supplied vdr-sxfe (or something like that) binaries work better, but from my initial tests that client didn't show most channels either.
So xineliboutput can't be what budget card people use, so I guess it's time to test vdr-xine. My initial gut feeling is that VDR isn't meant for X11 output at all, and it just happens to be possible to kludge it somehow.
I'd be extremely happy to be larted into submission so that I see a light though. :)
-- Jan Ekholm jan.ekholm@smultron.net
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Wednesday 29 April 2009, Theunis Potgieter wrote:
I use xineliboutput, permanently on my vdr, with xvmc enabled on my old nvidia 440 MX card. however only on SD mpeg2 broadcasts. It does provide some multimedia playback on other formats, which is useful. Normal vdr recordings are a bit of a pain, since fast forwarded/rewind doesn't work as you would expect with softdevice. If my vdr loses signal for a minute, I have to restart VDR, perhaps I should just try restarting xineliboutput. It is good enough for what I use. I didn't see any support for a vdr menu to play back other multi media content in vdr-xine, so there for never used it.
Does the normal OSD work for you? I don't see it, nor do I see the channel info when I switch channels. Also, if a channel switch is successful it does take 5s+ which I think is a bit long as "normal" VDR changes channel in 1-2s or so.
Yes, I setup vdr-skinsoppalusikka, but I had to set the video in xineliboutput to auto, not xvmc directly (can't remember off hand), by setting it to xvmc only, the colours are incorrect. The one that does work is xvmc+... will have to look it up when I get home.
What I do find odd is, that my idle shows 91%, but vdr uses 17% cpu usage and this is on an old Pentium 4, 2.4GHz. So I'm not sure how that works.
On 29/04/2009, Jan Ekholm jan.ekholm@smultron.net wrote:
On Wednesday 29 April 2009, Theunis Potgieter wrote:
I use xineliboutput, permanently on my vdr, with xvmc enabled on my old nvidia 440 MX card. however only on SD mpeg2 broadcasts. It does provide some multimedia playback on other formats, which is useful. Normal vdr recordings are a bit of a pain, since fast forwarded/rewind doesn't work
as
you would expect with softdevice. If my vdr loses signal for a minute, I have to restart VDR, perhaps I should just try restarting xineliboutput.
It
is good enough for what I use. I didn't see any support for a vdr menu to play back other multi media content in vdr-xine, so there for never used it.
Does the normal OSD work for you? I don't see it, nor do I see the channel info when I switch channels. Also, if a channel switch is successful it does take 5s+ which I think is a bit long as "normal" VDR changes channel in 1-2s or so.
--
Jan Ekholm jan.ekholm@smultron.net
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Wednesday 29 April 2009 14:05:33 Pertti Kosunen wrote:
Jan Ekholm wrote:
fine. Also the OSD isn't working making normal VDR use a hassle and I'm forced to switch the the s-video side to see EPG, timers etc.
"--primary" option to xineliboutput-plugin might help.
I use the following:
PLUGINS="-P"xineliboutput --primary --local=none --remote=37890 -- post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1""
So yeah, it's primary all right.
On Wed, Apr 29, 2009 at 5:22 PM, Jan Ekholm jan.ekholm@smultron.net wrote:
On Wednesday 29 April 2009 14:05:33 Pertti Kosunen wrote:
Jan Ekholm wrote:
fine. Also the OSD isn't working making normal VDR use a hassle and I'm forced to switch the the s-video side to see EPG, timers etc.
"--primary" option to xineliboutput-plugin might help.
I use the following:
PLUGINS="-P"xineliboutput --primary --local=none --remote=37890 -- post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_flag=1""
So yeah, it's primary all right.
You said earlier that you use HTTP to connect with your frontend. The xineliboutput README states the following:
Using with other media players (mplayer, vlc, ...)
Primary device video and audio (without OSD or subtitles) can be streamed from plugin control port to almost any media player using http or rtsp.
So, you might want to use a xine-based frontend (for example vdr-sxfe or xine-ui) with xvdr.
-Petri
I've only ever used vdr-xine and I must say it's pretty easy to get going. I've never used (or installed) Linux as a desktop either, maybe that's where people get problems?
For years it was console-only Debian with nexus-s tv-out. When that didn't cut it anymore due to things like hdtv, hdmi, etc. I bought a cheap vdpau video card, tried vdr-xine for the first time, and have been happy ever since! The few problems I had were all code-related and quickly resolved by the developers so I couldn't be happier.
The old advice is still true, use whatever works for you. :)
Cheers, Derek
2009/4/30 VDR User user.vdr@gmail.com
For years it was console-only Debian with nexus-s tv-out. When that didn't cut it anymore due to things like hdtv, hdmi, etc. I bought a cheap vdpau video card, tried vdr-xine for the first time, and have been happy ever since! The few problems I had were all code-related and quickly resolved by the developers so I couldn't be happier.
Is interlaced output with interlaced material still a no-go with vdpau, when no deinterlacer is involved? Last time i tested that resulted in a double (ghosted) output picture, as if the two fields were merged, then scaled, then output to separate fields again, which causes exactly such an effect. This was with driver rev 185.29 though.
I am a happy VDR user since a couple of years ago. Before VDR, I used Mythtv but switched due to its hardware requirements and bugs. My VDR is an (very) old Duron 700 MHz with 1 Technotrend FF card and 1 PVR 350 card. It has been no problem recording two channels (SD) at a time and watch a different recording trough FF card tv-out. FANTASTIC! The VDR box is soon going to be replaced by a faster machine, but will keep the current tv cards.
The problem is now to find out how to setup VDR on my new computer. Should I use - FF-TVout? - vdr-xine - xine-liboutput?
By just reading this thread, I can see that people has different favourites. My personal fealing is that VDR is lacking recommendations / good documentation on how to setup/configure "TV-out" in the best way, or at least describe pros/cons for each alternative. Is this a point where Mythtv beats VDR? I hope that I am wrong. Or have I missed anything?
regards, baronen
2009/4/29 VDR User user.vdr@gmail.com
I've only ever used vdr-xine and I must say it's pretty easy to get going. I've never used (or installed) Linux as a desktop either, maybe that's where people get problems?
For years it was console-only Debian with nexus-s tv-out. When that didn't cut it anymore due to things like hdtv, hdmi, etc. I bought a cheap vdpau video card, tried vdr-xine for the first time, and have been happy ever since! The few problems I had were all code-related and quickly resolved by the developers so I couldn't be happier.
The old advice is still true, use whatever works for you. :)
Cheers, Derek
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Lars Olsson wrote:
I am a happy VDR user since a couple of years ago. Before VDR, I used Mythtv but switched due to its hardware requirements and bugs. My VDR is an (very) old Duron 700 MHz with 1 Technotrend FF card and 1 PVR 350 card. It has been no problem recording two channels (SD) at a time and watch a different recording trough FF card tv-out. FANTASTIC! The VDR box is soon going to be replaced by a faster machine, but will keep the current tv cards.
The problem is now to find out how to setup VDR on my new computer. Should I use
- FF-TVout?
- vdr-xine
- xine-liboutput?
By just reading this thread, I can see that people has different favourites. My personal fealing is that VDR is lacking recommendations / good documentation on how to setup/configure "TV-out" in the best way, or at least describe pros/cons for each alternative. Is this a point where Mythtv beats VDR? I hope that I am wrong. Or have I missed anything?
regards, baronen
That depends solely on your display device. If you use an "old style" CRT or something similar with an interlaced input, your FF-card will give you the best output. But if you have a progressive display with preferably a digital input you might want to use a software output device like vdr-xine or xineliboutput. Even with a reasonably slow system you can take advantage of vdpau with an nvidia card and have a perfect progressive output. There are graphic cards with both PCI and PCI-Express bus connection that you can acquire with a modest expense.
-Petri
On Wednesday 29 April 2009 17:47:46 Petri Helin wrote:
You said earlier that you use HTTP to connect with your frontend. The xineliboutput README states the following:
Using with other media players (mplayer, vlc, ...)
Primary device video and audio (without OSD or subtitles) can be streamed from plugin control port to almost any media player using http or rtsp.
So, you might want to use a xine-based frontend (for example vdr-sxfe or xine-ui) with xvdr.
Oh, thanks for pointing that out, I'm such a n00b. I've read the README up and down but happily read the part "without OSD" as "with OSD". Doh! Then it's time to test vdr-sxfe and see how that fares. I wanted to keep the display in the same process as the rest of my media frontend app, but controlling an external process is no big hassle.
On Wednesday 29 April 2009 17:47:46 Petri Helin wrote:
On Wed, Apr 29, 2009 at 5:22 PM, Jan Ekholm jan.ekholm@smultron.net wrote:
I use the following:
PLUGINS="-P"xineliboutput --primary --local=none --remote=37890 -- post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_f lag=1""
So yeah, it's primary all right.
You said earlier that you use HTTP to connect with your frontend. The xineliboutput README states the following:
Using with other media players (mplayer, vlc, ...)
Primary device video and audio (without OSD or subtitles) can be streamed from plugin control port to almost any media player using http or rtsp.
So, you might want to use a xine-based frontend (for example vdr-sxfe or xine-ui) with xvdr.
Ok, I tried vdr-sxfe and it indeed is a much better solution and the OSD works exactly as it should. It's really looking nice.
However, I still can see only a small subset of the channels that "normal" VDR can see. I somehow suspect it's due to my hw setup:
* 1 Hauppuage FF DVB-c * 1 Hauppuage FF DVB-c + CI
The second card is the old primary card where the s-video is connected. I can only actually see channels that the second card *only* can tune into, i.e. a few encrypted channels for which the CI is used. All other normal open channels can not be seen using vdr-sxfe, I just get a "No signal" image. I suspect that the first DVB card is normally used for tuning into these channels, but that shouldn't matter, should it?
If I could just get all channels shown this solution would totally rock my setup. :)
You might have to specify that those encrypted channels are only tuned through that card.
2009/5/1 Jan Ekholm jan.ekholm@smultron.net
On Wednesday 29 April 2009 17:47:46 Petri Helin wrote:
On Wed, Apr 29, 2009 at 5:22 PM, Jan Ekholm jan.ekholm@smultron.net
wrote:
I use the following:
PLUGINS="-P"xineliboutput --primary --local=none --remote=37890 --
post=tvtime:method=Linear,cheap_mode=1,pulldown=0,use_progressive_frame_f
lag=1""
So yeah, it's primary all right.
You said earlier that you use HTTP to connect with your frontend. The xineliboutput README states the following:
Using with other media players (mplayer, vlc, ...)
Primary device video and audio (without OSD or subtitles) can be streamed from plugin control port to almost any media player using http or rtsp.
So, you might want to use a xine-based frontend (for example vdr-sxfe or xine-ui) with xvdr.
Ok, I tried vdr-sxfe and it indeed is a much better solution and the OSD works exactly as it should. It's really looking nice.
However, I still can see only a small subset of the channels that "normal" VDR can see. I somehow suspect it's due to my hw setup:
- 1 Hauppuage FF DVB-c
- 1 Hauppuage FF DVB-c + CI
The second card is the old primary card where the s-video is connected. I can only actually see channels that the second card *only* can tune into, i.e. a few encrypted channels for which the CI is used. All other normal open channels can not be seen using vdr-sxfe, I just get a "No signal" image. I suspect that the first DVB card is normally used for tuning into these channels, but that shouldn't matter, should it?
If I could just get all channels shown this solution would totally rock my setup. :)
-- Pets are always a great help in times of stress. And in times of starvation too, o'course. -- Terry Pratchett, Small Gods
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Friday 01 May 2009 11:29:52 Torgeir Veimo wrote:
You might have to specify that those encrypted channels are only tuned through that card.
The encrypted channels work 100% fine, they are streamed to vdr-sxfe just fine. The problem is all other non-encrypted channels, they cause a "No signal" image. I would imagine that it should not matter which card receives a channel in this case?
Jan Ekholm wrote:
So xineliboutput can't be what budget card people use, so I guess it's time to test vdr-xine. My initial gut feeling is that VDR isn't meant for X11 output at all, and it just happens to be possible to kludge it somehow.
Bad luck? Obsolete xine libraries? I'm running three vdr-sxfe clients at home with nice 50 Hz progressive 720p/1080p output to DVI with close to perfect vertical blanking sync (or in other words the horizontal text scrolls are smooth and sharp). I didn't get that working with on-board AMD780G graphics in my newest PC but a cheapo Nvidia card fixed that. Now I'm looking forward to eventually switch to VDPAU.
BR, Seppo
On Wed, 29 Apr 2009 22:27:00 +0300, Seppo Ingalsuo seppo.ingalsuo@iki.fi wrote:
Jan Ekholm wrote:
So xineliboutput can't be what budget card people use, so I guess it's time to test vdr-xine. My initial gut feeling is that VDR isn't meant for X11 output at all, and it just happens to be possible to kludge it somehow.
Bad luck? Obsolete xine libraries? I'm running three vdr-sxfe clients at home with nice 50 Hz progressive 720p/1080p output to DVI with close to perfect vertical blanking sync (or in other words the horizontal text scrolls are smooth and sharp). I didn't get that working with on-board AMD780G graphics in my newest PC but a cheapo Nvidia card fixed that. Now I'm looking forward to eventually switch to VDPAU.
BR, Seppo
How did you get the smooth scrolling, mine is jerky? I have on board nvidia HDMI connected to a plasma. I have a 50 Hz setting in xorg.conf and the Xorg.0.log and nvidia-settings both report a 50hz rate, the TV however reports 60 Hz so may be down to a duff TV (Samsung).
-- Scott
On Thu, 30 Apr 2009 21:08:26 +0100 scott scott@waye.co.uk wrote:
How did you get the smooth scrolling, mine is jerky? I have on board nvidia HDMI connected to a plasma. I have a 50 Hz setting in xorg.conf and the Xorg.0.log and nvidia-settings both report a 50hz rate, the TV however reports 60 Hz so may be down to a duff TV (Samsung).
No, it's a "useful feature" in the NVidia driver because NVidia's scaler does a better looking job than the one built into a typical LCD monitor. Add this to your "Device" section in xorg.conf:
Option "FlatPanelProperties" "Scaling = Native"
If you use xrandr to view/choose refresh rates, add this too:
Option "DynamicTwinView" "false"
There are more details in the driver's README. I think the nv driver has an option corresponding to the scaling one, but probably not the TwinView one.
scott wrote:
How did you get the smooth scrolling, mine is jerky?
With latest nvidia drivers I had to disable EDID entirely to avoid getting always 1080p60 backend resolution for all modes. Here's my xorg.conf suitable for a full-HD Sony. Some smarter ways to do this would be nice.
With my HTPC without AV receiver where I listen sound from TV speakers I disabled EDID because there seems to be HDMI audio support in my GS8400 card but no way to feed audio from ALSA there! Sonys select HDMI audio if it is present as even as zero stream.
The benefit with this is that TV does not need to be powered when X comes up to get a valid display mode.
---
# xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type "man xorg.conf" at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg
Section "Device" Identifier "Configured Video Device" Driver "nvidia" EndSection
Section "Monitor" Identifier "Configured Monitor" DisplaySize 480 270 ModeLine "1920x1080p50" 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +HSync +VSync ModeLine "1920x1080p60" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +HSync +VSync ModeLine "1920x1080p24" 74.16 1920 2558 2602 2750 1080 1084 1089 1125 +HSync +VSync EndSection
Section "Screen" Identifier "Default Screen" Monitor "Configured Monitor" Device "Configured Video Device" DefaultDepth 24 Option "ExactModeTimingsDVI" "True" Option "UseEdid" "FALSE" Option "ModeValidation" "AllowNon60HzDFPModes, NoEdidModes, NoEdidDFPMaxSizeCheck, NoVertRefreshCheck, NoHorizSyncCheck, NoMaxSizeCheck, NoDFPNativeResolutionCheck" Option "UseEvents" "True" SubSection "Display" Depth 24 Modes "1920x1080p50" "1920x1080p60" "1920x1080p24" EndSubSection EndSection
Section "Extensions" Option "Composite" "Enable" EndSection
---
BR, Seppo
Hello
Am Samstag, 2. Mai 2009 schrieb Seppo Ingalsuo:
scott wrote:
How did you get the smooth scrolling, mine is jerky?
With latest nvidia drivers I had to disable EDID entirely to avoid getting always 1080p60 backend resolution for all modes. Here's my xorg.conf suitable for a full-HD Sony. Some smarter ways to do this would be nice.
I wanted my HTPC to boot into X11 without the need to turn on the LCD-TV. When the TV is powered on later the X11 resolution should be like when booted with TV powered on. This is my solution:
1. Enable verbose logging of Xorg with the -logverbose 6 option. (I edited /etc/X11/xinit/xserverrc)
2. Start X with TV powered on to create a Xorg.0.log with the new logging level.
3. use the nvidia-xconfig utility to extract the TV's EDID data from the log file. $ nvidia-xconfig -E /var/log/Xorg.0.log \ --extract-edids-output-file=edid.bin \ --output-xconfig=/tmp/xorg.conf
The --output-xconfig is to not overwrite the normal /etc/X11/xorg.conf.
4. copy the created edid.bin file to some 'system place'. I copied into /etc/X11/edid.bin.
5. Then I use the following xorg.conf to boot with the TV powered off:
# xorg.conf (X.Org X Window System server configuration file) # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg
Section "Device" Identifier "NVIDIA GeForce 9300" Driver "nvidia" Option "ConnectedMonitor" "DFP-0" Option "UseDisplayDevice" "DFP-0" Option "CustomEDID" "DFP-0:/etc/X11/edid.bin" EndSection
When X is starting without the TV set turned on the driver uses the captured edit.bin file and selects the correct resolution.
I didn't test yet whether the custom edid is not used if some other display device is connected and the driver can get live edid data.
I found the pointer to this solution in the easy-vdr forum.
Regards Dieter
Hi,
On Sat, May 02, 2009 at 10:18:27PM +0200, Dieter Hametner wrote:
I wanted my HTPC to boot into X11 without the need to turn on the LCD-TV. When the TV is powered on later the X11 resolution should be like when booted with TV powered on. This is my solution:
Thanks for the tip. I had a similar problem. When my LCD-TV was on standby during startup of X it got not detected by the X-Server. I have managed to force the detection by adding a monitor section with all the modlines and also adding "ConnectedMonitor" "DFP-0". Now the I was able to turn the monitor on afterwards, and I got a picture, but it was only 640x480 pixel in size :(
Adding the "CustomEDID" "DFP-0:/etc/X11/LG-edid.bin" option solved everything for me. Now the X-Server starts with the native LCD-TV resolution, even when the TV is turned off.
Regards, Artem
Off-topic question:
Are there any (free) EDID binary data editors available that are able to edit the CEA block http://en.wikipedia.org/wiki/EDID#Extension_Block_Details ?
I'd like to disable 1080i modes from my EDID via CustomEDID option to avoid Nvidia drivers to use them as back-end resolution for scaling all modes on my HD-Ready LCD TV. 720p modes give best visual result but latest Nvidia driver's artificial intelligence decides that 1080i is best for me :^(
I'm too lazy to decode, encode and compute checksum for the block by hand :^)
BR, Seppo
Artem Makhutov wrote:
Adding the "CustomEDID" "DFP-0:/etc/X11/LG-edid.bin" option solved everything for me. Now the X-Server starts with the native LCD-TV resolution, even when the TV is turned off.
Regards, Artem
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Hi,
On Mon, May 04, 2009 at 06:56:22PM +0300, Seppo Ingalsuo wrote:
Off-topic question:
Are there any (free) EDID binary data editors available that are able to edit the CEA block http://en.wikipedia.org/wiki/EDID#Extension_Block_Details ?
I'd like to disable 1080i modes from my EDID via CustomEDID option to avoid Nvidia drivers to use them as back-end resolution for scaling all modes on my HD-Ready LCD TV. 720p modes give best visual result but latest Nvidia driver's artificial intelligence decides that 1080i is best for me :^(
I'm too lazy to decode, encode and compute checksum for the block by hand :^)
I am not sure about this. Have you tried to force a differnet resolution with a modline?
Regards, Artem
Artem Makhutov wrote:
I am not sure about this. Have you tried to force a differnet resolution with a modline?
I'm doing that at the moment but I lost the feature of making slightly underscanned desktop to compensate the overscan of this old HD Ready TV. I'm able to get a smaller resolution but it's shifted towards upper left corner and I'm not sure if vertical and horizontal shift is possible without loosing sync. Xvidtune refused to alter the mode parameters.
With an old nvidia driver that scaled to closest back-end resolution (visible in nvidia-settings utility) in EDID I could this way make a centered non-scaled underscanned desktop that fitted about exactly the 1366x768 display. But now this scaling happens compared to EDID resolution that is reported as native (1080i60 I think) and the trick doesn't work. The result is a stamp sized flickering picture :^(
Nvidia didn't respond at their forum.
BR, Seppo
Regards, Artem
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Seppo Ingalsuo wrote:
Off-topic question:
Are there any (free) EDID binary data editors available that are able to edit the CEA block http://en.wikipedia.org/wiki/EDID#Extension_Block_Details ?
I'd like to disable 1080i modes from my EDID via CustomEDID option to avoid Nvidia drivers to use them as back-end resolution for scaling all modes on my HD-Ready LCD TV. 720p modes give best visual result but latest Nvidia driver's artificial intelligence decides that 1080i is best for me :^(
Some info about EDID www.quantumdata.com/pdf/EDID.pps
Phoenix EDID Designer 1.3 http://www.tucows.com/preview/329441#MoreInfo
Lauri Tischler wrote:
Some info about EDID www.quantumdata.com/pdf/EDID.pps
The information looks useful, thanks!
Phoenix EDID Designer 1.3 http://www.tucows.com/preview/329441#MoreInfo
After figuring out the right hex format I tried it but I think it operates only with the standard DVI EDID not the CEA extension. Based on my partial hand decoding I think the stuff I need to edit is in the CEA extension. Or by intentionally loosing some features such as HDMI audio that I may use in the future I could of course make a 720p50 basic EDID block from scratch with this tool.
BR, Seppo
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
IMHO...
I've used both, and xineliboutput is arguably easier to get working as you only need the standard xine-lib for your repo, but....
I've chosen over the years to use vdr-xine as it seems to give the most options to change the front end, as it uses the standard one. I start it with:
xine --no-splash -Bfpqg -r anamorphic -V xv -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1 --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes
/dev/null 2>&1
It's served me well for 5 years...
----- Original Message ----- From: "Lauri Tischler" lwgt@iki.fi To: "VDR Mailing List" vdr@linuxtv.org Sent: Wednesday, April 29, 2009 9:42 PM Subject: Re: [vdr] Best practices for running vdr-xine
VDR User wrote:
On Tue, Apr 28, 2009 at 1:20 PM, Simon Baxter linuxtv@nzbaxters.com wrote:
I've recently taken a different approach altogether.
I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, pictures, music, weather, radio etc etc and TV. When you select TV, it launches vdr-xine.
I wanted a high quality graphical (open-gl) look - and the ability to play music playlists while cycling through my photo collection.
VDR, vdr-xine and mms seem to work very well together too....
Interesting. Do you have a howto for this? I'm sure I know some guys who would like to try it as an alternative to xbmc+VDR.
Has anybody made some kind of pros and cons analysis between vdr-xine and xineliboutput. Which is better or are they just different ?
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Simon Baxter wrote:
IMHO...
I've used both, and xineliboutput is arguably easier to get working as you only need the standard xine-lib for your repo, but....
I've chosen over the years to use vdr-xine as it seems to give the most options to change the front end, as it uses the standard one.
What do you mean here?
xineliboutput can be used with standard xine frontends as well, e.g. with xine-ui: xine "xvdr://127.0.0.1#nocache;demux:mpeg_block"
I start it with:
xine --no-splash -Bfpqg -r anamorphic -V xv -Dtvtime:method=Greedy2Frame,cheap_mode=0,pulldown=0,use_progressive_frame_flag=1 --post vdr_video --post vdr_audio vdr://tmp/vdr-xine/stream#demux:mpeg_pes
/dev/null 2>&1
It's served me well for 5 years...
Simon Baxter wrote:
IMHO...
I've used both, and xineliboutput is arguably easier to get working as you only need the standard xine-lib for your repo, but....
I've chosen over the years to use vdr-xine as it seems to give the most options to change the front end, as it uses the standard one.
What do you mean here?
xineliboutput can be used with standard xine frontends as well, e.g. with xine-ui: xine "xvdr://127.0.0.1#nocache;demux:mpeg_block"
Umm, ok. Shows how little I know!
No, I've not done a how to - but am happy to help.
I'm running mms-1.1.0. Had to configure in mms: .lircrc GenericPlayerConfig MovieConfig MplayerConfig TVConfig Config PictureConfig WeatherConfig XineConfig EPGConfig
but if you have it working under xineliboutput or vdr-xine, it pretty much works out of the box. The following how-to was really useful too: http://mms.mymediasystem.net/index-7.html
----- Original Message ----- From: "VDR User" user.vdr@gmail.com To: "VDR Mailing List" vdr@linuxtv.org Sent: Wednesday, April 29, 2009 8:41 AM Subject: Re: [vdr] Best practices for running vdr-xine
On Tue, Apr 28, 2009 at 1:20 PM, Simon Baxter linuxtv@nzbaxters.com wrote:
I've recently taken a different approach altogether.
I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, pictures, music, weather, radio etc etc and TV. When you select TV, it launches vdr-xine.
I wanted a high quality graphical (open-gl) look - and the ability to play music playlists while cycling through my photo collection.
VDR, vdr-xine and mms seem to work very well together too....
Interesting. Do you have a howto for this? I'm sure I know some guys who would like to try it as an alternative to xbmc+VDR.
Thanks, Derek
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Tue, Apr 28, 2009 at 10:56:28AM +0300, Peter wrote:
I have a bit of a problem running xine frontend – it will not reconnect if vdr backend restarts. Also, my vdr can take 10-15secs just to start up, and xine frontend will bail out during that time, too. Since frontend is being run on unattended TV box (read: no keyboard) it is cumbersome to restart xine every time this happens.
easy way around this: tell xine to exit when the stream finishes and run it in a loop. I am running the following in a shell loop. the important options being --no-splash and --auto-play=fhq, so xine starts immediately playing the stream and exits as soon as the stream finishese (e.g. when vdr restarts) or when xine chokes on a "faulty" stream. I also sometimes saw runaway xine processes, which still hold the xv/xvmc port, so everything called xine is killed forcibly afterwards.
xine $VERBOSE --aspect-ratio 4:3 --geometry 1024x768 --no-splash --no-lirc \ -V xxmc -A alsa --post vdr --auto-play=fhq \ vdr://tmp/vdr-xine/stream#demux:mpeg_pes killall -9 xine
-
Anssi Hannula -
Artem Makhutov -
Dieter Hametner -
Henning Glawe -
Jan Ekholm -
Lars Olsson -
Lauri Tischler -
Pertti Kosunen -
Peter -
Petri Helin -
scott -
Seppo Ingalsuo -
Simon Baxter -
Theunis Potgieter -
Tomasz Bubel -
Tony Houghton -
Torgeir Veimo -
VDR User