vdr January 2013

vdr@linuxtv.org

42 participants
38 discussions

range-select in live plugin
by Torgeir Veimo 13 Jan '13

13 Jan '13

I was getting carpal tunnel symptoms trying to select multiple recordings for deletion in the live plugin, so I made a patch to add range selection using the Quickboxes mootools plugin. It works by allowing you to click and hold the mouse, while moving over subsequent selection checkboxes of recordings. Is the live plugin still being maintained? It seems most activity halted about four years ago. This patch is a bit rough, so some testing in different browsers might be required. The Quickboxes plugins i MIT licensed, so can safely be included if accepted.

2 1

DVB_API_VERSION problem
by Leo Márquez 13 Jan '13

13 Jan '13

Dear all, I'm trying to build vdr-1.7.35. I know that it requires at least a DVB driver with api version 5.3 or higher. For this reason I downloaded and compiled the V4L-DVB dvb drivers from linuxtv.org. The process seems to be completed ok, I restarted to be sure the new driver is used and I also created a Make.config file in the vdr folder in order to specify the DVBDIR but VDR is still complaining about the DVB_API_VERSION. At this time I'm a little bit confused and I'm not sure if I'm using the new driver or not. Is there a way to check if I'm using a dvb api version 5.3 or higher? If I check the DVB api version and it is ok, what can I do next? I'm using debian squeeze with kernel 2.6.32. Thank you very much. Leo

4 3

daap plugin for vdr-1.7.x???
by Halim Sahin 12 Jan '13

12 Jan '13

Hi, where can I find the daap plugin for vdr? www.wahnadium.org doesn't show me any links :-(. Regards Halim

2 1

projects.vdr-developer.org - scheduled maintenance on Saturday/Sunday
by Tobi 10 Jan '13

10 Jan '13

Hi everyone! On Saturday/Sunday (2013-01-12 / 2013-01-13) I will run a lot of upgrades on the server. The Redmine projects might be offline for some hours but the Git repositories will still be accessible. Sorry for any inconveniences! I'll try to keep the downtime as short as possible. bye, Tobias

2 1

Recording plan
by Marx 10 Jan '13

10 Jan '13

Hello I would like to do/find some automation of choosing what to record from TV on VDR. In previous century :) it was newspaper I had to read and program recordings on my VCR. Now I have VDR, EPG, many web sites with movie descriptions and rankings, tracking sites like trakt.de etc. Hovewer I don't see it integrates well together. The closest is XMBC which hit PVR usable version. It can use trakt.de to mark what I watched, shows EPG and allow to plan recordings, It can scan recorded file in IMDB or similair and add it to library (probably, didn't do it yet). Hovewer I prefer to do such things from web or Android interface. And here is workflow i would like to use: 1) See EPG with good filtering capacity (for example "show only movies") 2) Each movie is checked against "watched" library like trakt.de and marked accordingly 3) Each movie I didn't see needs to be find in IMDB or one of many others movie databases (main difficulty is languge of EPG which isn't english in my country so titles of movies are translated). Informations (and maybe rating) should be shown accordingly on EPG 4) Movie I like needs to be planned as recording in VDR I think all steps are already done, hovewer I didn't find them integrated. Web interface of VDR have some integration with IMDB only, but it works in another window when you click, it doesn't works good with EPG in other language then english. VDR doesn't integrate with trakt.de or some similair site. I don't even think it should be done on VDR side. I rather think about some software which works with different sources like this: a) source of EPG from XMLTV, PVR or maybe web site b) many different PVRs so I can plan recording on VDR and for example enigma based tuner c) different tracking sites d) different movie database site e) multiplatform interface (web site with lite version for Android etc?) I know it's beyond this mailing list but here are many people which probably needs something like this Marx

2 2

[ANNOUNCE] another more or less useless plugin: avahi4vdr
by Lars Hanisch 09 Jan '13

09 Jan '13

Homepage: https://github.com/flensrocker/vdr-plugin-avahi4vdr What is it: It's a helper, so you can easily announce network services of your vdr and its plugins to your LAN via avahi (a Zeroconf implementation) or retrieve information about other network services (not limited to vdr such as nfs mounts etc.). Please read the README at https://github.com/flensrocker/vdr-plugin-avahi4vdr/blob/master/README I'm trying very hard to keep my README up-to-date. If there are questions please let me know. Please get familiar with Avahi, the avahi-tools like avahi-browse, avahi-publish and their manpages. How does it work: The "static way" is using a file "services.conf" in the plugin's config directory. For an example please look at https://github.com/flensrocker/vdr-plugin-avahi4vdr/blob/master/examples/se… Please forgive my long post... :) Server-Example: How to announce streamdev-server (aka announcing a static network service with fixed port) # line in services.conf, for syntax and escaping see README name=vdr-streamdev-server on %h,type=_http._tcp,port=3000,subtype=_vdr_streamdev_server._sub._http._tcp name: is something to display to the user (%h will be replaced with the hostname) type: is the service type, there are standards, look at http://www.dns-sd.org/ServiceTypes.html port: the port the service is listening on (handy for dynamic ports, since you can update the service on the fly and reannounce a new port, but sadly not in this static example, you have to use the plugin's SVDRPCommand "CreateService" for more control) subtype: you can specify details of the service, streamdev is on the lowest level a webserver, hence the type _http._tcp, but will publish special services with another "protocol", I suggest "_vdr_<plugin's name>.sub.<service type>" if it's for a vdr plugin. You can specify as many subtypes as you want. txt: you can add as many txt records to a service with service specific data (not used in this example, if you know avahi, you'll understand). On vdr startup, avahi4vdr connects to the avahi-daemon and will announce the streamdev-server. What for? Read next. :) Example: How to find streamdev-server (suggestion as extension to streamdev-client, feel free to implement) I will create a patch as soon as I can find time and really do need this fetaure at streamdev... You can call avahi4vdr's SVDRPCommand directly for registering a browser for services: int replyCode = 0; cString browserId; // remember this! cPlugin *avahi4vdr = cPluginManager::GetPlugin("avahi4vdr"); ... if (avahi4vdr != NULL) browserId = avahi4vdr->SVDRPCommand("CreateBrowser", "caller=streamdev-client,protocol=IPv4,type=_vdr_streamdev_server._sub._http._tcp", replyCode); ... If you don't need the browser anymore you can delete it anytime (will be done automatically on vdr-exit). ... if (avahi4vdr != NULL) avahi4vdr->SVDRPCommand("DeleteBrowser", *browserId, replyCode); ... Your plugin's Service function will be called if the browser raises an event: bool cPluginDbus2vdr::Service(const char *Id, void *Data) { if (strcmp(Id, "avahi4vdr-event") == 0) { cAvahiHelper options(Data); const char *event = options.Get("event"); const char *browser_id = options.Get("id"); if (strcmp(event, "browser-service-resolved") == 0) { const char *name = options.Get("name"); const char *host = options.Get("host"); const char *protocol = options.Get("protocol"); const char *address = options.Get("address"); const char *port = options.Get("port"); const char *local = options.Get("local"); const char *txt = NULL; int txt_nr = 0; while (true) { txt = options.Get("txt", txt_nr); if (txt == NULL) break; ... txt_nr++; } ... } else if (strcmp(event, "browser-service-removed") == 0) { const char *name = options.Get("name"); const char *protocol = options.Get("protocol"); const char *local = options.Get("local"); ... } return true; } return false; } cAvahiHelper is located at https://github.com/flensrocker/vdr-plugin-avahi4vdr/blob/master/avahi-helpe… It's a helper class for parsing parameters, only header is needed, so just copy it to your plugin. caller: (at CreateBrowser) the name of the plugin which should be called. You needn't to take your plugin's name. It's possible to create browsers for other plugins. It's not a bug, it's a feature. :) Whenever the browser detects a new service, an event "browser-service-resolved" is emitted. streamdev-client should instantiate a new device for each detected server (or reuse an unconnected device, multi-device support should be added first to streamdev-client) and if a server shuts down (event "browser-service-removed") the corresponding device can be "deactivated" (e.g. set to -none-). No more editing ips or ports in config files... :) For now there is just one "user" of the feature "dynamic publishing of services": dbus2vdr It starts a dbus-daemon listening on a dynamic tcp port and publishes it as subtype "_vdr_dbus2vdr._sub._dbus._tcp". On this separate dbus-daemon dbus2vdr just offers some read-only objects and methods like listing the timers or recordings. Listing channels will be added soon. I want to use these "dbus2vdr"-daemons to collect all timers from the stations on the LAN. I will add some simple logic (will be announced next month or so) and then all vdrs will record every thing they want. Timer conflict check is not yet planned, first incarnation will be "record everything I find important". Each vdr will decide on its own if it wants to record the timer of the remote vdr. Please be patient, project is at planning/documentation state, I have nothing coded yet. What would you like to do with avahi4vdr? Please let me know... Have fun! Lars.

1 0

half-viewed recordings, can they be moved at the top of the list?
by cedric.dewijs＠telfort.nl 09 Jan '13

09 Jan '13

Hi All, Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again. In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut. I would also like to see that VDR remembers the current position in the list of recordings. This is already the case during a vdr-sxfe session, but not when vdr has been restarted. After a restart, VDR goes to the top of the list. Or I should not have so many recordings :-) Best regards, Cedric

9 17

Re: [vdr] Problem with vdr-1.7.x and three DVB-T HD channels
by Karim 06 Jan '13

06 Jan '13

Update. I just recorded "France2HD" and I played back with VLC without problem. It seems ther is a dialog problem between vdr and xlo for tree HD channels Any hint please ? Regards -----Message d'origine----- De : vdr-bounces(a)linuxtv.org [mailto:vdr-bounces@linuxtv.org] De la part de kafifi Envoyé : dimanche 6 janvier 2013 20:40 À : 'VDR Mailing List' Objet : [vdr] Problem with vdr-1.7.x and three DVB-T HD channels Hi, Happy new year 2013 to Klaus and all vdr users !! Under vdr-1.7.x and xineliboutput, I have some trouble with **tree** dvb-t HD french channels (Eiffel Tower near Paris) : - SD channels : OK - HD channels : all OK except "France2 HD", "M6HD" and "6ter" (see below). Channels "KO" When I zap on one of them, image appears about one second, freezes, and then I get a black screen. Sometimes it's impossible to zap to another channel, vdr-sxfe can't drive vdr anymore, and I have to reload vdr. Sometimes, afert about 10s, image appears for one second, and freezes again, and then I get black screen. Here is latest tests performed on a Wheezy x64 fresh install. Same issues (signal strenght about 82%) : - with NOVA-T-500 tuner - with TBS6280 tuner - alternating vdr-1.7.27 (+ patch ppid) and vdr-7.1.33. - With parameter menu> configuration> DVB card> update channels "NO" - With parameter menu> configuration> DVB card> update channels "name and pid" Installation is OK, no problem under Win7. Could you please help me to find what's wrong ? Could it be a bad setting of config_xineliboutput ? Thanks a lot ! Karim channels.conf :@201 TF1 HD;MR5:530000:B8C34G8M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;140=fra,141=fra:0:1281:8442:5:0 France 2 HD;MR5:530000:B8S0Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad@122:0; 240=fra,241=fra:0:1282:8442:5:0 :@206 M6HD;MR5:530000:B8C23M2S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;340=fra,341=fra:0:1283:8442:5:0 ARTE HD;Multi 4:546000:B8C23M64T8Y0:T:27500:720=27:731=qaa@3,732=deu@3,733=qad@3,730=fra@3 :0;740=fra,741=deu,742=fra:0:1031:8442:4:0 HD1;MHD7:642000:B8C23M64S0T8Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132= qad@122:0;150=fra,151=fra:0:2561:8442:10:0 RMC DECOUVERTE;R8:770000:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122 ,332=qad@122:0;340=fra,341=fra:0:2819:8442:11:0 Chérie 25;MHD7:642000:B8C23M64S0T8Y0:T:27500:320=27:0;330=fra@122,331=qaa@122,332=q ad@122:0;350=fra:0:2563:8442:10:0 NUMERO 23;R8:770000:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qaa@122,232=qad @122:0;240=fra,241=fra:0:2818:8442:11:0 6ter;R8:770000:B8S0Y0:T:27500:120=27:0;130=fra@122,131=qaa@122,132=qad@122:0 ;140=fra,141=fra:0:2817:8442:11:0 L'Equipe 21;MHD7:642000:B8C23M64S0T8Y0:T:27500:220=27:0;230=fra@122,231=qad@122:0;250 =fra:0:2562:8442:10:0 vdr-sxfe Jan 6 20:29:56 pctest vdr: [4480] switching to channel 202 Jan 6 20:29:56 pctest vdr: [4792] TS buffer on device 3 thread ended (pid=4480, tid=4792) Jan 6 20:29:56 pctest vdr: [4791] buffer stats: 164688 (3%) used Jan 6 20:29:56 pctest vdr: [4791] receiver on device 3 thread ended (pid=4480, tid=4791) Jan 6 20:29:56 pctest vdr: [4802] receiver on device 3 thread started (pid=4480, tid=4802, prio=high) Jan 6 20:29:56 pctest vdr: [4803] TS buffer on device 3 thread started (pid=4480, tid=4803, prio=high) Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264: Found NAL SPS at offset 8/152 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: profile_idc 100 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_width: 120 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: pic_height: 34 mbs Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: frame only flag: 0 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: MBAFF Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: cropping 0 0 0 2 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: aspect_ratio_idc 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: -> aspect ratio 1 / 1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] H.264 SPS: -> video size 1920x1080, aspect 1:1 Jan 6 20:29:58 pctest vdr: [4802] [xine..put] Detected video size 1920x1080 Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:02 pctest vdr: [4786] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:30:02 pctest vdr: [4786] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:30:02 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57549 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57550 Jan 6 20:30:04 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:04 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:04 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57551 Jan 6 20:30:06 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57552 Jan 6 20:30:06 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:06 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:06 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) ..... ..... Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:14 pctest rsyslogd-2177: imuxsock begins to drop messages from pid 4480 due to rate-limiting Jan 6 20:30:23 pctest rsyslogd-2177: imuxsock lost 804 messages from pid 4480 due to rate-limiting Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57553 Jan 6 20:30:23 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57554 Jan 6 20:30:23 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:23 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:23 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:28 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:28 pctest vdr: [4827] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:30:28 pctest vdr: [4827] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:30:28 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57555 Jan 6 20:30:30 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57556 Jan 6 20:30:30 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:30 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:30 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:31 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:31 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57557 Jan 6 20:30:33 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57558 Jan 6 20:30:33 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:33 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:33 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:38 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:30:38 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57559 Jan 6 20:30:40 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57560 Jan 6 20:30:40 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:30:40 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:30:40 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) .... .... Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:30:51 pctest rsyslogd-2177: imuxsock begins to drop messages from pid 4480 due to rate-limiting Jan 6 20:31:05 pctest rsyslogd-2177: imuxsock lost 206 messages from pid 4480 due to rate-limiting Jan 6 20:31:05 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:31:05 pctest vdr: [4864] [xine..put] cBackgroundWriter: TCP write error Jan 6 20:31:05 pctest vdr: [4864] [xine..put] (ERROR (tools/backgroundwriter.c,247): Mauvais descripteur de fichier) Jan 6 20:31:05 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57565 Jan 6 20:31:07 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57566 Jan 6 20:31:07 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:07 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:31:07 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:31:08 pctest vdr: [4501] [xine..put] Client connection 0 closed Jan 6 20:31:08 pctest vdr: [4501] [xine..put] Closing connection 0 Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Client 0 connected: 127.0.0.1:57567 Jan 6 20:31:10 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Client 1 connected: 127.0.0.1:57568 Jan 6 20:31:10 pctest vdr: [4501] loading /DATA/configVDR/plugins/xineliboutput/allowed_hosts.conf Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cxSocket: setsockopt(SO_SNDBUF): got 262142 bytes Jan 6 20:31:10 pctest vdr: [4501] [xine..put] Data connection (TCP) requested Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cBackgroundWriterI initialized (buffer 2048 kb) Jan 6 20:31:10 pctest vdr: [4501] [xine..put] cTcpWriter initialized (buffer 2048 kb) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) Jan 6 20:31:20 pctest vdr: [4802] [xine..put] cXinelibServer::Play Buffer overflow (TCP/PIPE) etc.. _______________________________________________ vdr mailing list vdr(a)linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr

1 0

Permissions in vdr-1.7.35 tarball
by Dave 06 Jan '13

06 Jan '13

The directories in the vdr-1.7.35 tarball are set to mode 700. If, like me, you run vdr directly from the source tree but under a different user to the one you use for compiling, your plugins will not load. Dave

3 3

vdr-1.7.35 Makefile woes
by Torsten Duwe 05 Jan '13

05 Jan '13

Hi all! This may or may not be related to the Make.config discussion. I'm having difficulties to package vdr-1.7.35 compiled along with some plugins; "make install" produces nonsense under $DESTDIR, no matter whether I change $UP3 to use `pwd` or not. libdir and locdir always contain $UP3, which is always incorrect. I haven't even tried yet to compile other plugins against the installed vdr package. Please correct me if I'm wrong, IMHO there's a difference between the place where vdr is compiled, and the final runtime on the target system. Thus, if you stick to the package-config approach, 2 separate vdr.pc files would be required: one for the plugins compiled along with vdr, and one to be installed on the target system. I also fail to see this differentiation in the Makefile: LOCDIR and PLUGINDIR (and derived LIBDIR) appear only once in it, not to talk about INCDIR, see above. All contain $CWD. What am I missing? Torsten

4 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr January 2013