Re: [vdr] xbmc-pvr (was - HD clients for vdr)
Seppo Ingalsuo wrote: On Sun, 2009-08-23 at 09:05 -0700, VDR User wrote: Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. I really do not understand the rage about HD OSD and/or skins. VDR is meant for watching TV-programs, like sports, movies, documents, and porno, not OSD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Sun, Aug 23, 2009 at 11:24 PM, Lauri Tischlerl...@iki.fi wrote: Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. I really do not understand the rage about HD OSD and/or skins. VDR is meant for watching TV-programs, like sports, movies, documents, and porno, not OSD. Many of us are using real tv's and not computer monitors for viewing. And of course many are now doing hdtv. It's likely you're not a user of either or both of those. Certainly an HD OSD isn't required to watch tv but if you knew how ass ugly it was to see the crappy low-res 8bit OSD on a big high definition tv, you'd understand. Consider the HD OSD like having real nice woodgrain trim in your car. It's not required to drive but damn sure makes your car look better. Something else you might not have considered is that it really is necessary to have a flexible OSD these days when you have tons of users both with SD HD...Their display device capable of say 1920x1080 but the current OSD implementation not allowing you the full resolution when you're tuned to an SD channel. If you're going to update it to accommodate current/future needs, why not improve the OSD as a whole? There's no law that says VDR has to be stuck in the stone age.. It really can be slim trim, stable, and provide users with luxury as well. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Mon, 2009-08-24 at 09:12 +1000, Torgeir Veimo wrote: Maybe a streamosd plugin could provide what you need. I can't find further information about that with Google. Is that an existing project? So, I'm not really having problem with VDR's OSD. I just want three independent user interfaces to each HTPC/television. Xbmc test drive status: I found the VDR recordings as well from xbmc but unfortunately the recordings database seems to be corrupted. Selecting something from the list brings up a random recording :^) I was just lost with UI philopsophy that is totally different from native VDR. I suppose XBMC's was developed by Microsoft so it can't be bad, it just takes some time to learn ;^) BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ttxtsubs patch for vdr-1.7.9
Hi, just thought I'd post the ttxtsubs patch I modified to apply cleanly to vdr-1.7.9 if someone is interested. /Magnus H vdr-1.7.9-ttxtsubs.patch Description: Binary data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
2009/8/24 Seppo Ingalsuo seppo.ingal...@iki.fi: On Mon, 2009-08-24 at 09:12 +1000, Torgeir Veimo wrote: Maybe a streamosd plugin could provide what you need. I can't find further information about that with Google. Is that an existing project? So, I'm not really having problem with VDR's OSD. I just want three independent user interfaces to each HTPC/television. I was merely suggesting a new type of plugin that allows a remote client to access and control the osd instance of the vdr server. The reason this is a problem is that vdr only have the notion of one osd instance, and streamdev doesn't really provide a way of controlling this osd. -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdpau patches
I was thinking of giving xine/vdpau/xineliboutput another try after failing earlier in the year. I came across these patches: http://www.nfvdr.net/bbs/thread-5856-1-1.html Is anyone using these? -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Mon, 2009-08-24 at 14:26 +0200, Theunis Potgieter wrote: So what happens when the main/server machine gets stuck on channel zapping, when there and you see only a no channel display on the client? Should the recording happen on the server? or on the client side? how do you restart vdr if you can't see the server's menu? I didn't say it was either flawless or an ideal approach, but there are always methods by which to deal with such failure. (e.g. the 'remote' plugin can listen on a TCP port and give you text OSD via telnet) IMO, the recordings should always happen on the server. The xbmc-modified streamdev is now able to playback recordings over its own VTP: http://www.xbmc.org/trac/ticket/5595#comment:29 The 'clever stuff' is handling clashes of recordings / timers - some kind of priority system e.g. parents timers override the kids ones. gdh ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Mon, Aug 24, 2009 at 3:57 AM, Lauri Tischlerl...@iki.fi wrote: I really wouldnt care less, if the OSD on my Toshiba 42 FullHD looks ass ugly, so be it, just about anything, while developing VDR, is more important then HD OSD. Real nice woodgrain trim in cars was used in some 1950's stationwagons. :) While I would place other things higher on the TODO list (well-designed server/client capability for example), a nice HD OSD wouldn't be at the bottom. I'm glad Klaus took notice of how many users wanted this. Keep in mind, that's why VDR even has HD support now, and probably TS as well because from previous postings he didn't show much interest since those wern't things he needed. But it's made the user base happy! Overall I'm for anything that improves/enhances VDR, and attracts more users in. If that's a fancy OSD or something else, it's all fine by me. I stand by my earlier statement that VDR can be slim trim, stable, and provide users with luxury as well because I think it's foolish not to believe that. Some people like peas carrots, some don't. ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
Seppo Ingalsuo wrote: Hi, Are there cleaner or later patches somewhere for vdr (1.7.8) for xmbc? The patch vdr-1.7.4-ext68-streamdev.patch from ticket http://xbmc.org/trac/ticket/5595 could be applied but there could be some extra that I don't need from some VDR extensions patch. I'm also wondering if streamdev cvs is good as such. The HISTORY file mentions added XBMC support by extending VTP capabilities (thanks to Alwin Esch). Anyway this is what I got when compiling g++ -march=pentium4 -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DUSE_STREAMDEVEXTENSION -DREMOTE_KBD -DVDR_USER=\vdr\ -DLIRC_DEVICE= \/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/video\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\/usr/local/share/locale\ -I/usr/include/freetype2 -I/usr/src/v4l-dvb/linux/include channels.c In file included from skins.h:17, from osdbase.h:15, from player.h:14, from status.h:15, from channels.c:17: recording.h:66: error: ‘const cEvent* cRecordingInfo::GetEvent() const’ cannot be overloaded recording.h:63: error: with ‘const cEvent* cRecordingInfo::GetEvent() const’ make: *** [channels.o] Error 1 BR, Seppo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I've stripped the ext72 patch to contain just the two necessary extensions streamdevext and parentalrating and adapted it to vdr-1.7.9 but it should work for 1.7.8 also. Seems to work here so far and it's compatible with the iptv and ttxtsubs patches. Now all you need to get vdr-xbmc running is: vdr (duh!) my attatched patch for vdr streamdevoutput plugin from cvs XBMC pvr-testing from svn (with the streamdev patch in the XBMC tree, the osdteletext plugin also works) No guarantees that it's gonna work for you though. /Magnus H vdr-1.7.9-xbmc.patch Description: application/mbox ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ttxtsubs patch for vdr-1.7.9
VDR User wrote: Have you tested it to make sure it works? I only ask cuz making a patch apply clean, and having it still work can be two totally different things sometimes. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr I just checked it worked in my own environment, no thorough testing, no guarantees.. /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
svan...@bahnhof.se wrote: Yes, it has limitations but given the low power consumption it's still impressive. The ION runs fine with advanced deinterlacer for 576i and temporal for 1080i. A 9500GT can do advanced on 1080i but for me it's not worth the extra heat and space. I have the computer on the back of my TV. http://www.minhembio.com/magho /Magnus Are you sure your ION can play 1080i with temporal? What is the source? I have tried a lot of HD-channels on Thor 0.8W without success and I have to use bob deinterlace filter or else the hardware drops frames. See: http://www.nvnews.net/vbulletin/showthread.php?t=136326highlight=deinterlace I have installed Ubuntu 9.04 amd64 server with a minimum of services. /Svankan ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr In XBMC it works fine with Eurosport HD recordings on Thor at least. Ubuntu 9.04 32bit on the diskless ION, recordings on nfs. /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7.9 patches
Thanks for the ttxtsubs patch for vdr 1.7.9 Anybody has a vdr-1.7.9_extensions.diff patch? Or a setup plugin patch for vdr 1.7.9 have a look here please http://www.forum.free-x.de/wbb/index.php?page=ThreadpostID=7872#post7872 Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau patches
On Mon, 24 Aug 2009 12:49:18 +0100 scott sc...@waye.co.uk wrote: I was thinking of giving xine/vdpau/xineliboutput another try after failing earlier in the year. I came across these patches: http://www.nfvdr.net/bbs/thread-5856-1-1.html Is anyone using these? Looks like this: http://vdrportal.de/board/thread.php?threadid=86804 And yes, I use the patches and they improved playback considerably. -- --- Malte Schröder malte...@gmx.de --- signature.asc Description: PGP signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] EPG information kpn digitenne vdr 1.7.8
Hello all I have a question about the epg information in vdr. digitenne does a good job with epg info. They deliver two weeks epg but i have one problem. They probably don't send genre information. I use xbmc svn tree pvr-testing. This is still work in progress but it works great. The pvr client does patch streamdev for stuff like teletext which works ok. The problem i have is when showing the epg guide which fetches the info from the epg.data file from vdr. The epg.data file contains the folowing: == E 70 125118 600 50 10 T NOS Journaal met gebarentolk S Serie. e == XBMC can show genre in colors and probably in the future you can select a specific genre but now the genre information is not available(probably not in the stream). So i thought using xmltv2vdr which can extend the already known data. The xml file i get contains the folowing == programme start=20090823110500 +0200 stop=2009082312 +0200 channel=25 title lang=nlTrue life/title desc lang=nlReportageserie met opmerkelijke real-life verhalen over jonge mensen en de subculturen waartoe zij behoren./desc categoryEducational/category /programme == What for me is important is the peace category which contains the genre information. So i tried to import that data with the xmltv2vdr script which you can download from the vdr site. When i run the script with the modified channels.conf and the xml file it puts the new data in the epg data file but not the genre information. So i tried to do it manualy with telnet and added the genre info like this: telnet localhost 2001 PUTE C T-8720-2212-25 Animal Planet;Digitenne E 10140 1251016200 1800 0 T Wildlife SOS D Reportageserie Geen detailgegevens beschikbaar. G Sports (Genre) e c . = But i get an error 451 Error while processing EPG data Is there a possibility to add the G parameter or is it something else? I'm not a real programmer but i'm familiar with linux for about ten years so thats not a problem. Can someone shed some light? I'm out of ideas ;( Will try the latest version also tomorrow. With kind regards William ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
Well, video.output.vdpau_enable_inverse_telecine:1 is the one that stoped the problem with it freezing and then runing fast forward. The buffer settings help reduce droped frames as does the chroma setting, though it's not a big impact and I see no change in video quality. Having it deint chroma doesn't seem to have any effect other then eat a few more gpu cycles. video.output.vdpau_honor_progressive:1 simply turns off deint if you have a progressive video. No need to deint was isn't. I do know that as per other recomendations I had the video buffers up around 1 and audio down at 5 for awhile and I had more droped frames with high buffer setting. I could only use bob and the inverse_telecine setting is only for spectral. - Original Message - From: VDR User user@gmail.com To: VDR Mailing List vdr@linuxtv.org Sent: Sunday, August 23, 2009 11:34 AM Subject: Re: [vdr] HD clients for vdr On Sun, Aug 23, 2009 at 11:12 AM, Timothy D. Lenztl...@vorgon.com wrote: I've had a problem with seeminly under powered video card using a 8400gs (g98) and little by little am finding out what settings are needed: # vdpau: Try to recreate progressive frames from pulldown material # bool, default: 1 video.output.vdpau_enable_inverse_telecine:0 # vdpau: disable deinterlacing when progressive_frame flag is set # bool, default: 0 video.output.vdpau_honor_progressive:1 # vdpau: disable advanced deinterlacers chroma filter # bool, default: 0 video.output.vdpau_skip_chroma_deinterlace:1 # number of audio buffers # numeric, default: 230 engine.buffers.audio_num_buffers:500 # number of video buffers # numeric, default: 500 engine.buffers.video_num_buffers:1000 I use an 8400gs in two boxes and I don't get freezing video. However, my settings are different. I didn't have to change the values for the following, they work by default: video.output.vdpau_enable_inverse_telecine:1 video.output.vdpau_honor_progressive:0 video.output.vdpau_skip_chroma_deinterlace:0 engine.buffers.audio_num_buffers:230 engine.buffers.video_num_buffers:500 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD clients for vdr
Some stations do 1080i others do 720p. The 1080i seem to be worse but then I turn of deint for progressive video which should free up some of the video card. - Original Message - From: Goga777 goga...@bk.ru To: vdr@linuxtv.org Sent: Sunday, August 23, 2009 11:45 AM Subject: Re: [vdr] HD clients for vdr I use an 8400gs in two boxes and I don't get freezing video. do you mean 1080i video ? which deinterlaicer are you using ? my settings are different. I didn't have to change the values for the following, they work by default: video.output.vdpau_enable_inverse_telecine:1 video.output.vdpau_honor_progressive:0 video.output.vdpau_skip_chroma_deinterlace:0 engine.buffers.audio_num_buffers:230 engine.buffers.video_num_buffers:500 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Turn off/relocate ts error logging
This is my complete channels.conf file: :@1041 KVOA-DT,KVOA-DT:527028615:B6M10:T:0:49=2:0;52:0:0:3:0:211:0 :@1061 PBS HD,PBS HD:569028615:B6M10:T:0:49=2:0;52,56:0:0:1:0:213:0 :@1062 V-Me,V-Me:569028615:B6M10:T:0:65=2:0;68,72:0:0:2:0:213:0 :@1063 CREATE,CREATE:569028615:B6M10:T:0:81=2:0;84,88:0:0:3:0:213:0 :@1091 KGUN-DT,KGUN-DT:189028615:B6M10:T:0:49=2:0;52:0:0:3:0:215:0 :@1092 MEXI ,MEXI :189028615:B6M10:T:0:65=2:0;68:0:0:4:0:215:0 :@ KMSB,KMSB:539028615:B6M10:T:0:49=2:0;52:0:0:3:0:217:0 :@1131 KOLD-DT,KOLD-DT:213028615:B6M10:T:0:49=2:0;52:0:0:3:0:219:0 :@1132 Weather,Weather:213028615:B6M10:T:0:65=2:0;68:0:0:4:0:219:0 :@1133 Tube,Tube:213028615:B6M10:T:0:81=2:0;84:0:0:5:0:219:0 :@1181 KTTU-DT,KTTU-DT:503028615:B6M10:T:0:17=2:0;20:0:0:1:0:221:0 :@1271 PBS HD,PBS HD:557028615:B6M10:T:0:49=2:0;52,56:0:0:1:0:223:0 :@1272 KIDS,KIDS:557028615:B6M10:T:0:65=2:0;68,72:0:0:2:0:223:0 :@1273 WORLD,WORLD:557028615:B6M10:T:0:81=2:0;84:0:0:3:0:223:0 :@1401 KHRR-40, Telemundo Tucson, AZ,KHRR-DT:629028615:B6M10:T:0:49=2:0;52,54:0:0:3:0:225:0 :@1461 Univision,KUVE-DT:665028615:B6M10:T:0:49=2:0;52:0:0:1:0:179:0 :@1462 TeleFutura,KFTU-CA:665028615:B6M10:T:0:65=2:0;68:0:0:2:0:179:0 :@1581 KWBA-1,KWBA-1:653028615:B6M10:T:0:49=2:0;50:0:0:3:0:207:0 :@1582 KWBA-2,KWBA-2:653028615:B6M10:T:0:65=2:0;66:0:0:4:0:207:0 Adding a channel number to that last field (13) seems to cause problems with vdradmin getting guide data for the channels. - Original Message - From: Klaus Schmidinger klaus.schmidin...@cadsoft.de To: vdr@linuxtv.org Sent: Sunday, August 23, 2009 1:26 PM Subject: Re: [vdr] Turn off/relocate ts error logging On 23.08.2009 20:03, Timothy D. Lenz wrote: Form /var/log/user.log: Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (2) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (6) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (9) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (11) Aug 23 10:53:31 LLLx64-32 vdr: [2635] TS continuity error (8) This doesn't come from VDR (any more), because it no longer uses cTS2PES. But in looking at the log now with it having run a bit with good signal, I find another log spam: Aug 23 10:44:18 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 Aug 23 10:44:39 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa,72=spa:0:0 Aug 23 10:45:00 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng,88=eng:0:0 Aug 23 10:45:21 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;50=eng:0:0 Aug 23 10:45:42 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;66=spa:0:0 Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=spa:0:0 Aug 23 10:46:03 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:46:24 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=spa:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng:0:0 Aug 23 10:46:45 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:47:06 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 17+17=2:0;20=eng:0:0 Aug 23 10:47:27 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:47:48 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 65+65=2:0;68=eng,72=eng:0:0 Aug 23 10:48:09 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 81+81=2:0;84=eng:0:0 Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of channel 0 from 0+0=0:0:0:0 to 49+49=2:0;52=eng,56=eng:0:0 Aug 23 10:48:30 LLLx64-32 vdr: [2230] changing pids of
Re: [vdr] Turn off/relocate ts error logging
for the TS error: [14:01] rnissl simply comment out that line in vdr172_remux.c ../PLUGINS/src/xine-0.9.3/vdr172remux.c - Original Message - From: Klaus Schmidinger klaus.schmidin...@cadsoft.de To: vdr@linuxtv.org Sent: Sunday, August 23, 2009 2:15 AM Subject: Re: [vdr] Turn off/relocate ts error logging On 22.08.2009 19:12, Timothy D. Lenz wrote: My log files get so big it,s very hard to check them because of the ts error messages that get flooded to it. I've had logs near 2gb in size. I have a problem with xine crashing when there is a weak signal and the ts loging bloating the log files is creating a lot of problems. Need a way to turn off ts error loging or relocate to another file. Are these reports coming from the core VDR or from xine? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7.9 patches
Goga777 schrieb am Montag 24 August 2009: Thanks for the ttxtsubs patch for vdr 1.7.9 Anybody has a vdr-1.7.9_extensions.diff patch? Or a setup plugin patch for vdr 1.7.9 have a look here please http://www.forum.free-x.de/wbb/index.php?page=ThreadpostID=7872#post7872 Has anybody tested this patch? Or does anybody know that's about the original extensions-patch from zulu? greetings ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7.9 patches
On Mon, Aug 24, 2009 at 2:57 PM, Marcel Wittebaltasa...@web.de wrote: Goga777 schrieb am Montag 24 August 2009: Thanks for the ttxtsubs patch for vdr 1.7.9 Anybody has a vdr-1.7.9_extensions.diff patch? Or a setup plugin patch for vdr 1.7.9 have a look here please http://www.forum.free-x.de/wbb/index.php?page=ThreadpostID=7872#post7872 Has anybody tested this patch? Or does anybody know that's about the original extensions-patch from zulu? Is there an archive somewhere of all the patches that make up the extentions mega-patch (for lack of a better term)? I absolutely hate when patches are grouped together like that when I only want a couple features but forced to have 20 other things that are useless or I don't want. And it's not always so easy to just rip out the patches you actually want since difference patches can overlap in the source code. :\ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput vs xine-vdr plugin
Am wondering if the xineliboutput is a tad better thant xine-vdr w/ xine patched for vdpau? I currently use the latter, with the advantage that I can stop xine in order to run xbmc and possibly toggle between them using a lirc hotkey setup, all the while vdr runs all the time in the background for eventual recordings, but it seems that xineliboutput might have some more advanced features wrt cropping etc? -- -Tor ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
