[vdr] VDR doesn't add new h264 SD DVB-T channels
Hi. Since february there are some new h264 SD channels in the Swedish DVB-T network. I have my VDR 1.7.13 setup to automatically add transponders and channels and that has always worked before, both on DVB-T and -S/S2. However, if I manually add one channel on this new frequency: Discovery TL;Discovery Communications:50600:B8C23G8M64T8Y0:T:27500:489=27:0:0:0:570:8945:1026:0 , containing: Stream #0.0[0x1e9]: Video: h264, yuv420p, 544x576 [PAR 64:33 DAR 544:297], 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0.1[0x1e8](swe): Audio: aac, 32000 Hz, 5 channels, s16, 295 kb/s , it works just fine. But no other channels are automatically added. Can someone point me to where in the VDR code I should look to add some debug prints? /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XBMC with vdr-1.6.0 ??
Sorry for the delay. vdr is set to run all the time, I start mine with this line in inittab but anyway will do: vdr:35:once:/usr/local/bin/runvdr This is the while loop in my .xinitrc. This has to go before any exec lines that you might have which would be present to start window managers etc: ### bash script excerpt start while [ 1 -eq 1 ] do XINE=/data/downloads/xine-ui/src/xitk/xine $XINE -A alsa --video vdpau --post tvtime:method=use_vo_driver -f vdr://tmp/vdr-xine/stream#demux:mpeg_pes --no-gui --no-mouse --hide-gui --no-logo --no-splash --verbose=2 21 /tmp/xine_log #run xbmc export SDL_AUDIODRIVER=null # I use this to workaround an issue I had with navigation sounds in xbmc /usr/local/bin/xbmc --fullscreen 21 /tmp/xbmc done ### bash script excerpt end So this loop will just cycle between xine and xbmc unti the X session is killed. To stop xine I use the Music button on my Hauppauge remote, so I have this in the my .lircrc begin remote = Hauppauge button = Music prog = xine repeat = 0 config = Quit end This will close xine, causing the while loop to move on and start xbmc. I use MediaStream as my xbmc skin and this next bit is specific to that skin, if you use a different skin then you will have to look up how to add menu items for that skin. Also I think I read recently that xbmc has changed the way skins are handled so if you are on a new svn build, or maybe the latest release then things might have changed. I am using a SVN build from 8 Sep 2009. From the same home directory as the above .xinitrc, in .xbmc/skin/MediaStream/720p (That's the resolution I'm using, I don't think MediaStream has any other) you should have a file, Home.xml. Near the end there is a section which defines the main menu, normally preceded by the comment !-- Main Menu --. About 30 lines lower you should find a section which describes the buttons available in the top level menu, something like: content item id=7 descriptionPower Button/description label $LOCALIZE[31007] /label label2 $LOCALIZE[31017] /label2 onclickXBMC.ActivateWindow(ShutdownMenu)/onclick /item item id=6 descriptionMy System Menu/description label $LOCALIZE[31006] /label label2 $LOCALIZE[31016] /label2 onclickSetFocus(506)/onclick /item At a location of your choosing, but at the right xml indentation, you can add a button with the following xml: item id=11 descriptionMy VDR Button/description label $LOCALIZE[31905] /label label2 $LOCALIZE[31906] /label2 visible!Skin.HasSetting(HideTVShows)/visible onclickXBMC.Quit()/onclick /item The id of 11 must be unique in this list, my last one was 10, so I picked 11. The significant bits are the 2 numbers 31905 and 31906, plus the XBMC.Quit() which tells XBMC to close down when the menu item is clicked, and due to the bash while loop, xine will start up. Finally to get the right text for your new menu button, you need to define values for 31905 and 31906 in .xbmc/skin/MediaStream/language/English/strings.xml. Something like this before /strings will do: string id=31905TV/string string id=31906Watch/string As already mentioned you can achieve the same thing with less changes by using irexec, I guess the only advantage of the technique above is that you get a nice button in xbmc. Apologies for putting all this xbmc specific stuff in the vdr list, but its probably good to have the whole solution in one message. Its not exactly what you are after but it may give you some clues. -- Scott On Wed, 10 Mar 2010 10:12:30 +1300, Simon Baxter linu...@nzbaxters.com wrote: - Original Message - From: scott sc...@waye.co.uk To: VDR Mailing List vdr@linuxtv.org Sent: Monday, March 08, 2010 9:45 PM Subject: Re: [vdr] XBMC with vdr-1.6.0 ?? One way thats been suggested before, and which I use, is to put xbmc and vdr-xine in a while loop inside a bash shell script and set up a button to stop vdr-xine, and a menu option in xbmc to close it down. If you search this thread you should find some info, if not I can post my stuff. -- Scott Thanks Scott. Yes please, would like to see how you've implemeted it. I found a number of threads and have achieved the following: * added a script (vdr.py) under the My Scripts which calls the xine frontend. But this flags an error Errors in system config or similar, launches xine but closes xbmc at the back end http://forum.xbmc.org/showthread.php?t=42205 * added a phantom button on the main menu, which I'd hoped would launch vdr-py (lower in the above thread). But this just crashes xmbc What I want to achieve is a main menu button which
Re: [vdr] A/V out of sync for a lot of channels
I watch Channel4 a lot and I don't have any issues with it using xineliboutput or my Reel HDe (read: it's not noticable). But if you could tell mee the German channels, I could check with those as well. For me the frontend doesn't seem to make a difference: - vdr-xine/xine-ui - vdr-xine/gxine - xineliboutput show the same behaviour. Can I ask which xine-lib version is behind your xineliboutput? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR doesn't add new h264 SD DVB-T channels
Hi again and sorry for spamming this list with thing that may not be VDR related, I just discovered It seems there's something strange about this transponder since tzap -r doesn't work. I get a lock with tzap, I can watch the channels in VDR but I get no output on /dev/dvb/adapterX/dvr0 then tzap'ing to 506 MHz. On all other transponders I get a stream on dvr0. So I guess this is a question for linuxtv rather than VDR. Scan finds some strange channels that don't provide a name on this frequency: [04b0]:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:1200:3 [0316]:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:790:3 [0320]:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:800:3 Boxer Navigator:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:T RANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:65534:3 [0302]:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:770:3 [02ee]:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRAN SMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:750:3 BBC World News:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSM ISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:560:3 Discovery TL:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMI SSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:570:3 Discovery Science:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRA NSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:580:3 Disney XD:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMIS SION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:590:3 Showtime:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TR ANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:600:3 7:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISS ION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:810:3 Star!:50600:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANS MISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE:0:0:960:3 /Magnus H -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Magnus H Sent: den 12 mars 2010 09:27 To: vdr@linuxtv.org Subject: [vdr] VDR doesn't add new h264 SD DVB-T channels Hi. Since february there are some new h264 SD channels in the Swedish DVB-T network. I have my VDR 1.7.13 setup to automatically add transponders and channels and that has always worked before, both on DVB-T and -S/S2. However, if I manually add one channel on this new frequency: Discovery TL;Discovery Communications:50600:B8C23G8M64T8Y0:T:27500:489=27:0:0:0:570:8945:1026:0 , containing: Stream #0.0[0x1e9]: Video: h264, yuv420p, 544x576 [PAR 64:33 DAR 544:297], 25 fps, 25 tbr, 90k tbn, 50 tbc Stream #0.1[0x1e8](swe): Audio: aac, 32000 Hz, 5 channels, s16, 295 kb/s , it works just fine. But no other channels are automatically added. Can someone point me to where in the VDR code I should look to add some debug prints? /Magnus H ___ 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] enna + vdr
So nobody here has Enna working at all or can give me a clue?? Steve Steve wrote: Lucian Muresan wrote: from Enna to VDR, well, Enna runs all the time, VDR too, and Enna has a main menu entry called TV Guys, do the standard binary packages have this 'TV' item enabled, or only if you build it yourself from source? I ask because I'm having a real time getting it to compile/work on Ubuntu Karmic - all I get is * Developer Warning * : This program is calling: ecore_evas_object_associate(); With the parameter: obj being NULL. Please fix your program. . I've asked on the geexbox devel list and not had any response at all. I tried the yaVDR distro but no 'TV' option appears in the menu... Steve ___ 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] A/V out of sync for a lot of channels
2010/3/12 Günter Merz lotan...@hotmail.com: For me the frontend doesn't seem to make a difference: - vdr-xine/xine-ui - vdr-xine/gxine - xineliboutput show the same behaviour. Can I ask which xine-lib version is behind your xineliboutput? You may :) I use the regular xine-lib version from the VDR Team PPA (1.2.0+hg+vdpau+r285+crop+v11-1tvt6). The only thing I compiled by hand (using the vdr pre-patched sources from the VDR Team PPA), is the xineliboutput plugin. Since I wanted to use the latest CVS edition. I only have an other issue now... But I'll reserve that for a new thread. Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Feature request: program guide scroll
On 12.03.2010 08:33, István Füley wrote: Hello list, At the moment if I press the Guide button (or select a specific program from EPG list) i can see the detailed description of the event. Now pressing up/down or left/right scrolls the Long Description, if this doesn't fit in the OSD window. I wonder if it's possible to implement a different behaviour for the left/right keys: to scroll between programs. Pressing right should bring up the next event, pressing left should bring up the previous event. To scroll in the OSD window Up and Down are fine. Left and Right are used to page up/down within long list, and that's not going to change. However, we could use the Green and Yellow buttons (and additionally the kPrev and kNext keys) for this. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)
Hello All, For a couple of months I'm very happy with my new Asus ION/330. But last week I decided to swap my Hauppauge NOVA-HD-S2 for an USB based Tevii S660. The reason, I wanted to get me a new HTPC enclosure and to use my Reel ExtensionHD (the Asus ATN37A only has one PCI-slot available). I use the The VDR Team PPA builds (VDR 1.7.10) with the latest CVS of the xineliboutput plugin. Now I encounter a strange problem. During the start of VDR I encounter system unresponsiveness. It hangs a bit, like if the CPU is at 100%. However, top doesn't show me anything out of the ordinary. And it seems to happen on SDTV (for example BVN) and HDTV (for example ArteHD). As a result, during LiveTV using vdr-sxfe, I encounter picture breakups. I tried removing all of the non-essential plugins and swapping xineliboutput for vdr-xine, but I have the same problem. I tried the official Tevii drivers as well as the drivers from s2-liplianin. The only thing I didn't try, is upgrade to VDR 1.7.13. But before the DVB-device swap it worked great, so I don't see a reason to upgrade I haven't build the reelbox stuff yet, so the EHD is *not* configured in my system. I'm a bit reluctant to remove the EHD since I just made everything nice (enclosure and furniture). Also, I tested my configuration with MS Windows in combination with DVB Viewer Pro and no issues. And a fast test with TVHeadend doesn't seem to give issues also. So it must be VDR in combination with my Tevii S660 USB device. Has anybody seen this kind of behaviour and have a solution or something else for me to look at? Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-femon-1.7.7 vdr-iptv-0.4.0 vdr-skinsoppalusikka-1.7.1 vdr-rssreader-1.7.0
On 08.03.2010 04:22, ? ?? wrote: Hi IPTV doesn't need patches anymore. Fine :) But I have another trouble. create channel RENTV;IPTV:10:S=1|P=1|F=UDP|U=239.4.0.1|A=2020:I:27500:300=2:301:0:0:1:0:0:0 Start vdr and select it, works fine. Change to sat channel, and select iptv again The channel can't selected, in log: Mar 8 12:57:57 ua0lnjvdr vdr: [6823] ERROR: Invalid channel parameters: S=1 Mar 8 12:57:57 ua0lnjvdr vdr: [6823] ERROR: Unrecognized IPTV address: S=1 Mar 8 12:57:57 ua0lnjvdr vdr: [6823] ERROR: Can't start Transfer Mode! After this, in channels.conf have: RENTV;IPTV:10:S=1:I:27500:300=2:301:0:0:1:0:0:0 I found also http://www.vdr-portal.de/board/thread.php?threadid=94442 Any suggestions? Not sure if this applies here, but there was a bug in VDR 1.7.13's channel editing in cDvbSourceParam. The attached patch fixes this. Klaus --- dvbdevice.c 2010/03/06 11:07:05 2.30 +++ dvbdevice.c 2010/03/07 11:45:43 2.31 @@ -576,7 +576,7 @@ class cDvbSourceParam : public cSourceParam { private: int param; - cChannel data; + int srate; cDvbTransponderParameters dtp; public: cDvbSourceParam(char Source, const char *Description); @@ -589,19 +589,19 @@ :cSourceParam(Source, Description) { param = 0; + srate = 0; } void cDvbSourceParam::SetData(cChannel *Channel) { - data = *Channel; - dtp.Parse(data.Parameters()); + srate = Channel-Srate(); + dtp.Parse(Channel-Parameters()); param = 0; } void cDvbSourceParam::GetData(cChannel *Channel) { - data.SetTransponderData(Channel-Source(), Channel-Frequency(), data.Srate(), dtp.ToString(Source()), true); - *Channel = data; + Channel-SetTransponderData(Channel-Source(), Channel-Frequency(), srate, dtp.ToString(Source()), true); } cOsdItem *cDvbSourceParam::GetOsdItem(void) @@ -612,7 +612,7 @@ switch (param++) { case 0: ST( S ) return new cMenuEditChrItem( tr(Polarization), dtp.polarization, hvlr); else return GetOsdItem(); case 1: ST( S ) return new cMenuEditMapItem( tr(System), dtp.system, SystemValues); else return GetOsdItem(); -case 2: ST( CS ) return new cMenuEditIntItem( tr(Srate),data.srate); else return GetOsdItem(); +case 2: ST( CS ) return new cMenuEditIntItem( tr(Srate),srate);else return GetOsdItem(); case 3: ST(ACST) return new cMenuEditMapItem( tr(Inversion),dtp.inversion,InversionValues);else return GetOsdItem(); case 4: ST( CST) return new cMenuEditMapItem( tr(CoderateH),dtp.coderateH,CoderateValues); else return GetOsdItem(); case 5: ST( T) return new cMenuEditMapItem( tr(CoderateL),dtp.coderateL,CoderateValues); else return GetOsdItem(); ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-femon-1.7.7 vdr-iptv-0.4.0 vdr-skinsoppalusikka-1.7.1 vdr-rssreader-1.7.0
On Fri, 12 Mar 2010, Klaus Schmidinger wrote: Not sure if this applies here, but there was a bug in VDR 1.7.13's channel editing in cDvbSourceParam. Well, there were bugs also in the plugin, but those should already be fixed in 0.4.1. BR, -- rofa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] A/V out of sync for a lot of channels
I demand that Niels Wagenaar may or may not have written... I use the regular xine-lib version from the VDR Team PPA (1.2.0+hg+vdpau+r285+crop+v11-1tvt6). Hmm, looks a bit old. You might do better to grab the version in Debian experimental. [snip] -- | Darren Salt| linux at youmustbejoking | nr. Ashington, | Doon | using Debian GNU/Linux | or ds,demon,co,uk| Northumberland | Army | + They're after you... Your kindness and generosity cause envy in a powerful person nearby. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)
2010/3/12 Niels Wagenaar n.wagen...@xs4all.nl: I haven't build the reelbox stuff yet, so the EHD is *not* configured in my system. I'm a bit reluctant to remove the EHD since I just made everything nice (enclosure and furniture). Also, I tested my configuration with MS Windows in combination with DVB Viewer Pro and no issues. And a fast test with TVHeadend doesn't seem to give issues also. So it must be VDR in combination with my Tevii S660 USB device. Ok, I removed the ExtensionHD. This didn't solve the problem. Then I decided to put an old TT 1500-S in and now it works. I also found out that TVHeadend experienced the same problem. Upgrading VDR didn't resolve the issue. So I guess it's a problem with the Tevii S660 (as I thought). And I found that other have curious problems as well. *sigh* Oh well, time to find an other DVB-S2 based USB device. Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)
Hello, Am 12.03.2010 22:23, schrieb Niels Wagenaar: 2010/3/12 Niels Wagenaarn.wagen...@xs4all.nl: I haven't build the reelbox stuff yet, so the EHD is *not* configured in my system. I'm a bit reluctant to remove the EHD since I just made everything nice (enclosure and furniture). Also, I tested my configuration with MS Windows in combination with DVB Viewer Pro and no issues. And a fast test with TVHeadend doesn't seem to give issues also. So it must be VDR in combination with my Tevii S660 USB device. Ok, I removed the ExtensionHD. This didn't solve the problem. Then I decided to put an old TT 1500-S in and now it works. I also found out that TVHeadend experienced the same problem. Upgrading VDR didn't resolve the issue. So I guess it's a problem with the Tevii S660 (as I thought). And I found that other have curious problems as well. *sigh* Oh well, time to find an other DVB-S2 based USB device. The S660 works well for me. It is a problem of the drivers and/or firmware. I had also the same problem. The only working driver for me is the official driver from the TeVii website and also just an older version. Unfortunaly I have deleted the original .rar so I can't tell you the exact version I am using right now. The s2-liplianin drivers do not work reliably. Regards, Artem smime.p7s Description: S/MIME Cryptographic Signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)
2010/3/12 Artem Makhutov ar...@makhutov.org: The S660 works well for me. Yes, I read this for many people. As well that others have issues with it. It is a problem of the drivers and/or firmware. I had also the same problem. I thought it was a driver issue. The only working driver for me is the official driver from the TeVii website and also just an older version. Unfortunaly I have deleted the original .rar so I can't tell you the exact version I am using right now. The s2-liplianin drivers do not work reliably. I tested the drivers from: - Tevii drivers called 100302_linux_tevii_ds3000.rar - s2-liplianin - v4l I made no difference, with all drivers I encountered the same issue. Picture breakup and at that time the system becomes inresponsive during a SSH session. Would you be willing to tar, compress it and upload both drivers somewhere? You may also mail them to me, my mailbox is quite large and can handle large attachements. Regards, Artem Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On Fri, Mar 5, 2010 at 7:31 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
On Fri, Mar 12, 2010 at 3:08 PM, VDR User user@gmail.com wrote: On Fri, Mar 5, 2010 at 7:31 AM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: What about VDR 1.7.11 and 1.7.13 (just to further narrow this down)? I have experienced this problem several times today while on HD h264 channels. Like previously posted: Mar 12 15:02:23 vdr: [20675] buffer usage: 70% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 80% (tid=20674) Mar 12 15:02:24 vdr: [20675] buffer usage: 90% (tid=20674) Mar 12 15:02:25 vdr: [20675] buffer usage: 100% (tid=20674) VDR was unresponsive and had to be restarted to fix. Best regards, Derek Sorry, forgot to mention this is with VDR-1.7.13... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] System unresponsive and picture breakup with VDR 1.7.10 and Tevii S660 (USB)
Hi, Am 12.03.2010 22:56, schrieb Niels Wagenaar: I tested the drivers from: - Tevii drivers called 100302_linux_tevii_ds3000.rar - s2-liplianin - v4l I made no difference, with all drivers I encountered the same issue. Picture breakup and at that time the system becomes inresponsive during a SSH session. I had the same issue. The system was freezing several times per minute for a few seconds. All of this drivers won't work. The only working driver for me was called something like this: 09X_tevii_x.rar Unfortunatly this driver does not build with kernel 2.6.33 anymore. So I have to stick with 2.6.32-gentoo-r6. Would you be willing to tar, compress it and upload both drivers somewhere? You may also mail them to me, my mailbox is quite large and can handle large attachements. Files sent. Regards, Artem smime.p7s Description: S/MIME Cryptographic Signature ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr