Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 10.02.2016 um 16:58 schrieb VDR User: >> No, absolutely not. The setup of OpenELEC is much less complicated and >> dependencies are no problem. >> The vdr-addon and the vnsi-addon gets installed by some clicks on the remote >> and a first channel scan >> needs only some clicks more. > It's always no problem until something breaks.. > >> The raspberry pi has superior HDMI-CEC support that is used automatically by >> Kodi, so in most cases >> there is even no need for an IR receiver and an extra remote. The remote of >> the TV is just enough. That >> simplifies the setup even more. > He's not asking about HDMI-CEC so this is irrelevant. Additionally, > HDMI-CEC support can be very limited on the device end so just because > a device technically supports it, that doesn't automatically mean you > can do what you want using HDMI-CEC. And plenty of people like me > already use multi-device remotes so we don't have to bother with > configuring HDMI-CEC at all. > >> The topic is about playing .mkv. That is just a container. What about the >> used codecs? In the upcoming OpenELEC >> 0.7 there will even be support of H265 on the RPi. The Kodi GUI has no >> problems with playing 3D content. >> Is this working with your solution too? > I use the vdr-mplayer plugin with mpv-player (rather than mplayer). > Yes, it works great. I've already played plenty of h265 content. I > don't have a 3D capable card or tv but that works fine too. Very > simple, very lightweight. Adding Kodi is adding a whole other layer of > software and it's completely unnecessary. He's asking for something > very simple, the solution should also be the same. There's no point in > bloating his system and adding a whole other layer of software on top > of VDR that he never asked for in the first place. You don't have to > defend Kodi, I'm not trashing it. Kodi is nice when it's not broken. > I'm only stating the obvious, that Kodi is absolutely unnecessary to > give the OP what he's asking for. There is no denying this. And, he > can decide if he wants to bother adding Kodi to his setup just to play > mkvs, or if something less extreme makes more sense. > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > !DSPAM:56bb82fd484001781562189! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Sorry for the empty answer before. Am 10.02.2016 um 16:58 schrieb VDR User: >> No, absolutely not. The setup of OpenELEC is much less complicated and >> dependencies are no problem. >> The vdr-addon and the vnsi-addon gets installed by some clicks on the remote >> and a first channel scan >> needs only some clicks more. > It's always no problem until something breaks.. That is irrelevant, because that can happen with your solution too >> The raspberry pi has superior HDMI-CEC support that is used automatically by >> Kodi, so in most cases >> there is even no need for an IR receiver and an extra remote. The remote of >> the TV is just enough. That >> simplifies the setup even more. > He's not asking about HDMI-CEC so this is irrelevant. Additionally, > HDMI-CEC support can be very limited on the device end so just because > a device technically supports it, that doesn't automatically mean you > can do what you want using HDMI-CEC. And plenty of people like me > already use multi-device remotes so we don't have to bother with > configuring HDMI-CEC at all. I can't see why it is a problem to mention other features he would get with another solution. >> The topic is about playing .mkv. That is just a container. What about the >> used codecs? In the upcoming OpenELEC >> 0.7 there will even be support of H265 on the RPi. The Kodi GUI has no >> problems with playing 3D content. >> Is this working with your solution too? > I use the vdr-mplayer plugin with mpv-player (rather than mplayer). > Yes, it works great. I've already played plenty of h265 content. On an RPi? With hardware support? I don't believe that. I'm only stating the obvious, that Kodi is absolutely unnecessary to give the OP what he's asking for. There is no denying this. And, he can decide if he wants to bother adding Kodi to his setup just to play mkvs, or if something less extreme makes more sense. If you let him really decide you shouldn't make solutions bad without any proof, only because you don't like them. I asked you already before to explain what makes OpenELEC more complicated, you didn't answer. The only thing that is really obvious that you have no idea what you are talking about. As the founder of yaVDR I have some experiences how complicated a vdr setup can be. As a contributor to OpenELEC I know how simple the setup in OE currently is. Gerald !DSPAM:56bb8663485834103731893! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 2016-02-09 22:55, schrieb VDR User: You don't need to bother with Kodi (unless you actually want to use it). VDR + the mplayer plugin work perfectly fine. There's no point in unnecessarily complicating a persons setup if that's not what they want. I know nothing in OpenELEC that is complicating a persons setup, what do you have in mind? At least his current setup is complicated enough so that he has no idea what to do next. He has no idea what to do next because he lacks information, not because his setup is complicated. And, any time you bundle additional software along with all of the dependencies that come with it, it's just more to maintain and more that can break. What sense does that make when all he wants to do is play mkvs? Kodi is completely unnecessary, surely you agree. No, absolutely not. The setup of OpenELEC is much less complicated and dependencies are no problem. The vdr-addon and the vnsi-addon gets installed by some clicks on the remote and a first channel scan needs only some clicks more. The raspberry pi has superior HDMI-CEC support that is used automatically by Kodi, so in most cases there is even no need for an IR receiver and an extra remote. The remote of the TV is just enough. That simplifies the setup even more. The topic is about playing .mkv. That is just a container. What about the used codecs? In the upcoming OpenELEC 0.7 there will even be support of H265 on the RPi. The Kodi GUI has no problems with playing 3D content. Is this working with your solution too? Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 10.02.2016 um 23:45 schrieb VDR User: > I haven't said any solution to his problem is bad and I have said I > don't like anything. Once again I have to point out that Kodi is > unnecessary to play mkvs. It's idiotic to even question that fact but > if you really need "proof" then go ahead and install the vdr-mplayer > plugin and prove it to yourself. Of course not. You told that my solution is too complicated, you have to prove it. I did not judge about your solution. > It's really starting to seem teenage girl'ish so maybe you should give > it a rest. My fault, I should have learned over the years that you are just a troll. Gerald !DSPAM:56bbc3a8493521263344062! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 2016-02-09 10:19, schrieb Nicolas Huillard: Hi all, My new Raspberry Pi2 install lacks a media player, which begins to be a bit annoying. The current setup : * NFS server * DigitalDevices Octopus Net DVB network server * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings, etc. IMHO OpenELEC covers all your needs and is still lightweight. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 2016-02-09 10:43, schrieb Nicolas Huillard: Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit : Am 2016-02-09 10:19, schrieb Nicolas Huillard: > Hi all, > > My new Raspberry Pi2 install lacks a media player, which begins to be a > bit annoying. The current setup : > * NFS server > * DigitalDevices Octopus Net DVB network server > * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings, > etc. IMHO OpenELEC covers all your needs and is still lightweight. As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which by definition gets VDR out of the way. No, that is not true. I even helped to better integrate VDR into OpenELEC. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 2016-02-09 12:01, schrieb Nicolas Huillard: Le mardi 09 février 2016 à 11:35 +0100, Gerald Dachs a écrit : Am 2016-02-09 10:43, schrieb Nicolas Huillard: > Le mardi 09 février 2016 à 10:33 +0100, Gerald Dachs a écrit : >> Am 2016-02-09 10:19, schrieb Nicolas Huillard: >> > Hi all, >> > >> > My new Raspberry Pi2 install lacks a media player, which begins to be a >> > bit annoying. The current setup : >> > * NFS server >> > * DigitalDevices Octopus Net DVB network server >> > * VDR + rpihddevice + satip on the Pi2 : live TV, timers, recordings, >> > etc. >> >> IMHO OpenELEC covers all your needs and is still lightweight. > > As I understand OpenELEC, it is a lightweight Kodi (XBMC) distro, which > by definition gets VDR out of the way. No, that is not true. I even helped to better integrate VDR into OpenELEC. I meant that Kodi becomes the main interface, with a VNSI/PVR client add-on, while the VDR instance will remain (in my case) on the headless server, with a limited or non-existing UI. No, OpenELEC supports and provides a local VDR. Will the current stable Kodi 15.2 include your work ? yes Any specific advice on how to have this kind of setup running ? not really. My work just allows a channel scan from the vdr-addon settings instead of using the vnsi client interface to the VDR. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Media (.mkv) player on Raspberry Pi2 VDR client
Am 09.02.2016 um 17:07 schrieb VDR User: > You don't need to bother with Kodi (unless you actually want to use > it). VDR + the mplayer plugin work perfectly fine. There's no point in > unnecessarily complicating a persons setup if that's not what they > want. I know nothing in OpenELEC that is complicating a persons setup, what do you have in mind? At least his current setup is complicated enough so that he has no idea what to do next. Gerald !DSPAM:56ba1e4b68607589549215! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Using a rasberry pi as vdr client
Am 01.02.2016 um 15:01 schrieb Harald Milz: > Hi, > > a bit late maybe but vnsiverver on the VDR side and Openelec / kodi on the > RPi side should be fine, that's what I am using, and the WAF is pretty high. I > got a Hama MCE remote with USB IR receiver, which worked out of the box. > An IR receiver is usually not necessary. The HDMI-CEC support of the raspberry pi is very good. Mostly the remote of the TV is just enough. Gerald !DSPAM:56afa1b4373991281062396! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] rpihddevice plugin 1.0.0
Am 2015-10-19 01:22, schrieb Torgeir Veimo: Do you know any rpi distro this one will be included in? Don't think it's included in raspian yet? MLD: http://www.minidvblinux.de/ Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and streamdev at the same time
Am 20.04.2015 um 15:34 schrieb Marko Mäkelä: On Mon, Apr 20, 2015 at 03:15:08PM +0200, Patrick Boettcher wrote: Is it technically possible to for example pause a live SD TV stream and copy some files over the Ethernet at the same time? Which scenario? VDR on RPI or on a remote? If VDR on a remote host, IIRC, pausing causes very few bandwidth as only a still image is displayed. VDR client+server on the same RPi. I guess it is simply too much to ask of the poor RPi. Kodi and vnsi-addon + vdr and vnsi-server-plugin are working on the same RPi, and it is a much heavier load than your setup. I can't see why this shouldn't work. Gerald !DSPAM:55352184204551113121336! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 2015-04-15 22:54, schrieb Lars Hanisch: Am 15.04.2015 um 18:37 schrieb VDR User: On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there wouldn't be any reason to ask. Of all the people who are scolded with `code it yourself then`, how many actually can? Probably very very very few, so why bother with such useless comments? Nonsense, I have not been rude. I have even some examples where I told this to other users that started coding afterwords. That made it a very useful comment. To not say it and miss a change to get it done is useless. Who, and what have they coded? Project names? restfulapi and dynamite are two of them. And he encouraged me to start with dbus2vdr. Restfulapi and dynamite were the projects I had in mind, thanks Lars. And restfulapi was a starter for even two more fellows. And just in case that you will tell now that nobody needs that, then you talk only for yourself. Dynamite is used by all yaVDR users. Restfulapi is now part of OpenELEC. Are you man enough to confess that you are wrong? I doubt that, you will surely find some excuses. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 16.04.2015 um 17:09 schrieb VDR User: Gerald, my opinion is my opinion - you disagreeing doesn't change anything. It's not wrong and nobody is the opinion police. So why you then argued against my argumentation to show that I am not rude and named me even a liar? And after I proofed that I didn't lie you just continued to let me me just look stupid? All the years I had the feeling that you are just a troll, but I hoped that I was wrong. Gerald !DSPAM:552fdaa1645671082260260! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 2015-04-16 16:09, schrieb VDR User: What exactly do you think I was wrong about? You forgot already? You told that I was rude and I proofed that I was not. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 2015-04-15 16:43, schrieb VDR User: On Wed, Apr 15, 2015 at 3:56 AM, Gerald Dachs v...@dachsweb.de wrote: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice + vdr + streamdev-client on the clients and connect to a streamdev-server on the main vdr. Well, that works so far, but it is not an effective substitute for the functionality of vdr-sxfe, at least not for what I use it mainly. All functions run on the remote machine, and only the screen is transferred to the local machine. This solution, or the already mentioned possibility with Kodi and vnsi/xvdr, are the only supported ways currently. If this is not good for you, then start coding. Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there wouldn't be any reason to ask. Of all the people who are scolded with `code it yourself then`, how many actually can? Probably very very very few, so why bother with such useless comments? Nonsense, I have not been rude. I have even some examples where I told this to other users that started coding afterwords. That made it a very useful comment. To not say it and miss a change to get it done is useless. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 15.04.2015 um 18:37 schrieb VDR User: On Wed, Apr 15, 2015 at 8:03 AM, Gerald Dachs v...@dachsweb.de wrote: Proper server/client has been on the user wishlist for ages. There's no reason to be rude to someone looking for something better. If those solutions were all that great then there wouldn't be any reason to ask. Of all the people who are scolded with `code it yourself then`, how many actually can? Probably very very very few, so why bother with such useless comments? Nonsense, I have not been rude. I have even some examples where I told this to other users that started coding afterwords. That made it a very useful comment. To not say it and miss a change to get it done is useless. Who, and what have they coded? Project names? So, you name me a liar? Would it change something if I would name projects? Gerald !DSPAM:552e984a166098533532618! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 2015-04-15 00:55, schrieb Niedermeier Günter: Am 14.04.2015 um 09:56 schrieb Gerald Dachs: Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice + vdr + streamdev-client on the clients and connect to a streamdev-server on the main vdr. Gerald Well, that works so far, but it is not an effective substitute for the functionality of vdr-sxfe, at least not for what I use it mainly. All functions run on the remote machine, and only the screen is transferred to the local machine. This solution, or the already mentioned possibility with Kodi and vnsi/xvdr, are the only supported ways currently. If this is not good for you, then start coding. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] from xineliboutput to ... perhaps softhdddevice?
Am 2015-04-14 08:59, schrieb Matthias Wächter: While streamdev and VNSI/XVDR solve some of the issues, most notably the multi-client dependency, they create new ones. No native OSD with VNSI/XVDR, VDR configuration synchronization hassle with streamdev. use softhddevice + vdr + streamdev-client on the clients and connect to a streamdev-server on the main vdr. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] merge 3 recordings of the same show to remove glitches?
Am 19.02.2015 um 20:32 schrieb Gerald Dachs: Am 19.02.2015 um 19:24 schrieb VDR User: Do you know of any that are capable of frame-accurate h264 editing, and that don't produce any corrupted frames or artifacts? This requires several frames around the cut point to be reencoded while the rest of the frames can be fast-copied. Don't know about the details. I am using Avidemux for cutting my recordings as I told and have never seen artefacts. I use Avidemux, because it is the only editor I have found that does not transcode the movie if I don't want it. Ah, I forgot, I always cut on I-frames. Gerald !DSPAM:54e63b73480795911313045! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] merge 3 recordings of the same show to remove glitches?
Am 19.02.2015 um 19:24 schrieb VDR User: Do you know of any that are capable of frame-accurate h264 editing, and that don't produce any corrupted frames or artifacts? This requires several frames around the cut point to be reencoded while the rest of the frames can be fast-copied. Don't know about the details. I am using Avidemux for cutting my recordings as I told and have never seen artefacts. I use Avidemux, because it is the only editor I have found that does not transcode the movie if I don't want it. Gerald !DSPAM:54e63a3f479529078611732! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR version 2.2.0 released - Celebrating 15 years of VDR!
Am 19.02.2015 um 11:38 schrieb Klaus Schmidinger: VDR version 2.2.0 is now available at Sorry, no facebook account, so it has to go here: +1 Gerald !DSPAM:54e5c696350228714022420! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] merge 3 recordings of the same show to remove glitches?
Am 19.02.2015 um 16:42 schrieb VDR User: I'm not aware of any video editing software for Linux There is plenty of it: - Avidemux - Cinerella - flowblade - Kino - Kdenlive - LiVES - Open Movie Editor - OpenShot - PiTiVi to name only a few. I use Avidemux, but for merging movies I would try OpenShot Gerald !DSPAM:54e61c52441034184121461! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Restart of frontend
Am 14.02.2015 um 19:53 schrieb VDR User: At yavdr we use this feature to start X and vdr in parallel and attach softhddevice when X is ready. And you can restart X when softhddevice is detached. Do you happen to know approx. how much startup time is saved doing this? We have no times for this isolated feature of starting X and vdr parallel, because we do more. We don't use lircd, but eventlircd, because eventlircd has not to wait until the remote devices are ready, so the vdr don't need to wait for them too. Many current dvb tuners need long time to get ready, sometimes because usb enumeration happens late, or firmware has to be loaded. For this Lars has invented the dynamite plugin that collects tuners when they are ready and gives them to the vdr. Other distributions have to wait with the vdr start till the last dvb tuner is ready. We don't wait for any of them. The vdr will show a picture when the first tuner comes ready. Of course it is very hardware related, but 10 seconds from bios post till live tv is possible. We had even some customized setups that did it in 6 seconds. Gerald !DSPAM:54dfe318514691998282038! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] plex
Am 08.01.2015 um 18:16 schrieb jacek burghardt: I wonder if anyone is using plex with vdr.? I use vdr 2.1.6 and it does not seems to work with vdr i get channel not responding and plex plugin shows unavaiable I don't understand exactly what you mean, because plex is ambiguous. There is the Plex Media Server, the Plex Apps for smartphones, or TVs, Plex Home Theater, Plex Web App ... I use the Plex Media Server, but not directly with the vdr. I use a vdr recording hook, that transcodes every recording to mp4 with x264 codec and renames it so that Plex Media Server easy gets it infos from the themoviedb, and thetvdb. That works very good, at least good enough for me. I don't use Plex for live TV, my TV can do this alone. Gerald !DSPAM:54aec131579451973119193! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Forced boot once a day
Am 14.09.2014 um 12:02 schrieb Thomas Maaß: Hi! I use epgsearch's searchtimer to record my favorite series. But there could be a problem when using automatic shutdown and wakeup. When there is no event in the current epg, the searchtimer will not be updated any more. The shutdown script will get no wakeup time, because there is no timer. The VDR will do no wakeup, and no more searchtimer records will be done. Maybe an option could be added to VDR to force a boot once a day. When the next timer is later than a specific time, set the wakeup time to this time. So you could make sure, that VDR is booted once a day, and the searchtimer could be updated. No searchtimer recording would be lost. It is not the job of the vdr to do such OS depending actions. Use the ACPI Wakeup addon for this task like most vdr distributions do. Gerald !DSPAM:54156be3490091730197352! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Forced boot once a day
Am 14.09.2014 um 17:07 schrieb VDR User: Why don't you just use a cron job for this? Why to use cron if the ACPI wakeup addon has a setting for this? Gerald !DSPAM:5415b51e652171744718748! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Forced boot once a day
Am 14.09.2014 um 19:42 schrieb VDR User: Why don't you just use a cron job for this? Why to use cron if the ACPI wakeup addon has a setting for this? Because you don't need to bother with a whole plugin just for that. It is an addon, no plugin, just some scripts and there is a big chance that it is already installed. How else would his computer start to record scheduled events? Gerald !DSPAM:5415d62873265520375805! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] converting ts to mkv
Am 2014-05-26 05:09, schrieb VDR User: There's no reason to touch the audio/video streams at all unless you actually want to re-encode them for some reason. If all you want is an .mkv rather than a .ts, that can be done in seconds with mkvmerge. Re-encoding in that case is pointless a waste of time. This is all true. Beside that there is no need to extract audio before using handbrake, there is even no need to use mkvmerge if you don't pretend on mkv. I had used an after recording script that just checked with avprobe, whether the video codec is mpeg2video, or h264. If it was mpeg2video I simply renamed the file to .mpeg, and for h264 to .mp4. Every programs known by me played this files without any problems. No need for mkv. To add some ts files to one use cat: cat 1.tx 2.ts new.ts Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] converting ts to mkv
Am 25.05.2014 16:20, schrieb jacek burghardt: I had recording setup last night and now I have 111 ts files. I guess heavy rain may caused so many ts files. is there a script that would merge them into one ts and convert them into mkv ? How I can setup after recording rules to convert recordings ? Why do you want to do this? You will get a movie with 110 breaks that last some seconds in it. Throw it away. Gerald !DSPAM:5382455b408061556753072! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] still image at end of replay
Am 2014-04-10 12:52, schrieb Peter Münster: On Thu, Apr 10 2014, VDR User wrote: This really sounds like something that should be solved in parenting and not code. With code it's easier... ;) Not for the coder. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 2.1.3
Am 05.01.2014 14:40, schrieb Lars Hanisch: I'll do my very best... :) Lars. This is funny! English, but only understood by German. Gerald !DSPAM:52c9992d302581408685597! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] libcec integration
Am 23.12.2013 12:09, schrieb Torgeir Veimo: True, but libcec-daemon is tricky at best, and currently doesn't compile (nor run properly after tweaking the source) on raspbian . And cec is more than just remote controls, you can turn on and off the tv etc. That doesn't work when piped through the remote plugin. I didn't talk about the remote plugin and the extra functionality can be done with irexec. Gerald !DSPAM:52b8387b137254908619775! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] libcec integration
Am 22.12.2013 15:06, schrieb Torgeir Veimo: Have anyone looked into integrating libcec into VDR, similar to lirc? I don't think that this is necessary. AFAIK the libcec provides generation of uinput events. Together with eventlircd it should be possible to control the vdr. Gerald !DSPAM:52b6fb6f86201284335806! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] libcec integration
Am 22.12.2013 15:47, schrieb Gerald Dachs: Am 22.12.2013 15:06, schrieb Torgeir Veimo: Have anyone looked into integrating libcec into VDR, similar to lirc? I don't think that this is necessary. AFAIK the libcec provides generation of uinput events. Together with eventlircd it should be possible to control the vdr. I wanted to say the libcec-daemon. Gerald !DSPAM:52b7082188345275951292! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Why use /var/lib/vdr?
Am 11.12.2013 18:55, schrieb cedric.dew...@telfort.nl: Hi All, I have build VDR systems based on arch linux and debian. On both, one half of the configuration files in is /etc/vdr, the other half in /var/lib/vdr. Why has the location /var/lib/vdr been choosen for the configuration files? That is not true. Configuration-Files are only in /etc/vdr. What you can see in /var/lib/vdr are data files. Configuration files are only modified by root and never by the application. The files in /var/lib/vdr are modified by the vdr. Gerald !DSPAM:52a8b97950221956011510! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] aufs instead of mhddfs with vdr 2.1.2
Am 01.12.2013 11:24, schrieb Matthias Biel: Hi Mike, If I understand your question correctly, you have several file systems for video data and you want to join them for use with VDR. VDR supports this out of the box: If your video directory ends with '0', VDR will automatically look for directories ending with 1, 2, ... and will use all of them. So you could mount your filesystems to directories that correspond to the naming scheme. You can find a more detailed description at: http://www.vdr-wiki.de/wiki/index.php/VDR_Optionen This is true, but the current vdr developer version doesn't support this anymore. So why not look for new solutions? Gerald !DSPAM:529b13a3216559371165570! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] DNS-323 NAS with 64MB ram, can this run VDR?
Am 2013-11-18 15:26, schrieb cedric.dew...@telfort.nl: Hi All, I have been given a D-link DNS-323 NAS. This machine runs linux, but only has 64MB RAM. I have tested on my x86 machine. VDR uses 28MB RAM while idle, and this rises to 48MB while decrypting and recording one SD channel. Is it possible to run VDR on this machine? How can I keep the RAM usage low? RAM is not the problem. An ARM CPU with 1.2 GHz ist maxed out decrypting one HD stream. I doubt that your CPU has more performance. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Makefile system
Am 24.03.2013 15:48, schrieb VDR User: On Sun, Mar 24, 2013 at 5:24 AM, Helmut Auer v...@helmutauer.de wrote: Which plugin are you refering to? softhddevice and live Plugin. There was a mismatch between c an c++ flags and this was surely caused by the new makefile system :) When using the new style Makefile supplied with softhddevice git, I was getting crashed. Johns acknowledged the plugin had issues with the new Makefile and recommended to continue using the provided old-style Makefile. So are you saying that you've actually fixed softhddevice so it works correctly and no longer crashes when using the new-style Makefile? If so, would you mind submitting that patch to Johns so he can merge it? I don't know whether Tobi started his plugin from scratch, or used our yavdr package as template, but we don't have crashes either. With vdr 1.7.41 and 1.7.42 and softhddevice 0.6.0 there are no Problems at least with vdpau on 64 bit systems. The only used patch (attached) has nothing to do with the new makefiles. Gerald !DSPAM:514f1e83250661305017642! Index: vdr-plugin-softhddevice-0.5.2.git.20130303.1729/Makefile === --- vdr-plugin-softhddevice-0.5.2.git.20130303.1729.orig/Makefile 2013-03-11 16:32:00.0 +0100 +++ vdr-plugin-softhddevice-0.5.2.git.20130303.1729/Makefile2013-03-12 11:40:16.893647421 +0100 @@ -32,8 +32,8 @@ #CONFIG += -DHAVE_PTHREAD_NAME # supports new pthread_setname_np #CONFIG += -DNO_TS_AUDIO # disable ts audio parser #CONFIG += -DUSE_TS_VIDEO # build new ts video parser -#CONFIG += -DUSE_MPEG_COMPLETE # support only complete mpeg packets -#CONFIG += -DUSE_VDR_SPU # use VDR SPU decoder. +CONFIG += -DUSE_MPEG_COMPLETE # support only complete mpeg packets +CONFIG += -DUSE_VDR_SPU# use VDR SPU decoder. ifeq ($(ALSA),1) CONFIG += -DUSE_ALSA ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Audio only output device?
Am 13.03.2013 15:09, schrieb Füley István: Subcribe. To what? Gerald !DSPAM:5140aac1168913192934288! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Call for development: enhancing mplayer-plugin
Am 2013-02-27 11:56, schrieb Peter Münster: Hi, Support for seeing the VDR osd over mplayer doesn't exist yet. Who could add this feature please? And what would be the price? I think this is already work in progress: http://www.vdr-portal.de/board17-developer/board21-vdr-plugins/p1127401-play-git-up-to-date/?highlight=%5Bplay%5D#post1127401 Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD Test clip(s)
Am 16.02.2013 17:14, schrieb VDR User: If you want the highest quality deinterlacing on 1080i, a GT220 is required. A GT610 is good enough, costs only the half and it is much easier to cool it quietly. Gerald !DSPAM:511fb59841991258417478! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD Test clip(s)
Am 16.02.2013 21:28, schrieb VDR User: On Sat, Feb 16, 2013 at 8:36 AM, Gerald Dachs v...@dachsweb.de wrote: If you want the highest quality deinterlacing on 1080i, a GT220 is required. A GT610 is good enough, costs only the half and it is much easier to cool it quietly. I've read the opposite -- that the GT610 struggle with 1080i highest deinterlacing. I don't have to read about it, I own one. I know it better. And I am not the only one that thinks like this. It is common sense in the vdr-portal.de that the GT610 is good enough for temporal-spatial. Gerald !DSPAM:51200d5c44881319480443! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] bug in channels.conf.terr?
Am 2013-02-15 08:49, schrieb Marx: What I would like to have is scraper for KingOfSat which is probably most up-to-date sat channels database. I would prefer to filter this database by provider, sat name etc and produce channels.conf based on it. There would be need to keep some preferences, like list of FTA channels, sorting etc but that way making fresh channels.conf would be fast, easy, and productive. Sounds interesting, go for it. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] bug in channels.conf.terr?
Am 2013-02-11 12:40, schrieb Klaus Schmidinger: On 11.02.2013 05:04, VDR User wrote: On Sun, Feb 10, 2013 at 1:32 PM, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: Maybe I should completely remove all channels.conf* files from the source archive? The existing ones are already rather old, and I can't possibly keep them up to date, anyway. If they're not going to be kept up-to-date then they don't really serve any purpose since an outdated channels.conf is useless. People will just have to channel scan themselves anyways so why bother keeping outdated files in the source? I see no harm in removing them. On second thought, I guess I won't touch that area at this time, so close to version 2.0. I'll drop these files after version 2.0, once automatic transponder scanning will be implemented. In this case it would be a good idea to delete this line Lars mentioned from channel.conf.terr that lets the vdr crash. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
Am 30.12.2012 01:08, schrieb Christopher Reimer: I don't consider the mailinglist as central spot of developement. Here I'm forced to speak English. Almost all VDR Users are German. And in VDR-Portal I reach the critical mass. With the addition that I am allowed to speak my native language. What makes you believe that? Do you have any numbers? I don't have user counts either. I know that visitors of yavdr.org are not the same as vdr users, but they might be somehow related. Our statistics shows that the german group is with %67 of course the biggest, but far away from almost all. Gerald !DSPAM:50e02a13296741317615234! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
Am 28.12.2012 16:38, schrieb Klaus Schmidinger: So should we go back to the Makefiles of version 1.7.33 and declare this area of the program source untouchable forever? +1 Gerald !DSPAM:50ddc50a174441059718148! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
Am 27.12.2012 19:11, schrieb Helmut Auer: I'm just glad Linux distribution managers don't build cars - otherwise we would most likely be long dead before we find the brake pedal... ;-) As a distribution manger I have to disagree ;) All I'm doing now, is to wait til you find a solution which won't be changed within the next five days and then I put my distribution around it ;) Something similar I wrote in the portal. So Full ACK. Gerald !DSPAM:50dc90eb87784772790529! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [DISCUSSION REQUEST] reintroduce a common make configuration file in VDR-1.7.35
Am 27.12.2012 22:21, schrieb VDR User: On Thu, Dec 27, 2012 at 10:20 AM, fnu v...@auktion.hostingkunde.de wrote: But don't forget, you don't make a solution liek VDR a success or BBS like vdr-portal only with a few make; make install users. Over 95% of VDR users are using a distribution. I completely disagree with you claiming over 95% of VDR users are using a distribution. Most of the users I talk to regularly, or observe in various forums do not use pre-made distributions, they compile VDR themselves so they have full control over what patches (if any) are being applied, how it's set up, etc. I would never come to the idea to say that over 95% of the VDR users use a distribution and I even would not say the opposite, because I really have no idea. But what makes you so sure that it is wrong? Do you think you know more than 5% of all VDR users? Gerald !DSPAM:50dccbaa99813830873357! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Reserve device for Live-Tv
Am 19.12.2012 10:30, schrieb brian_dorl...@t-online.de: Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices. And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless. Gerald !DSPAM:50d19286143496329019569! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Reserve device for Live-Tv
Am 19.12.2012 15:11, schrieb Brian-Imap: On 19.12.2012 11:10, Gerald Dachs wrote: Am 19.12.2012 10:30, schrieb brian_dorl...@t-online.de: Hi, might be simple. From ct. If you are using DVB-S, install a FF DVB-C card. That is the primary device. But it cannot record, so recordings are done on all other DVB-S devices. And how can he use this DVB-C-Device then for Live-TV? He can only view the signal from one of the DVB-S-Devices that are locked to the transponder they are recording. Additionally for streamdev it is totally useless. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I haven't tested this yet. But this solution was the one favoured by CT to solve the problem of the FF cards not having enough bandwidth to handle live viewing and recording at the same time. The DVB-C FF card will never record in a DVB-S system. I assumed that you could view live TV via transfer mode from a DVB-S card. You didn't understand the problem. If this used DVB-S-Card will be needed by an recording it will again switch away from the live channel. And again, to use a FF-Card will not help with streamdev. Gerald !DSPAM:50d1f3b2162182740914572! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Reserve device for Live-Tv
Am 19.12.2012 16:51, schrieb VDR User: I ran into the same problem. My solution was to add another dvb card. When I hit that wall again, I added another. This is the easiest fix imo and doesn't require any patching. :) This is always the way to go. Gerald !DSPAM:50d1f3d8162281845871878! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Special Character problems
Am 17.12.2012 20:35, schrieb Brian-Imap: Hi, I did an apt-get update at the weekend on my Ubuntu with VDR 1.7.33 system. Now the special characters in the recording menu in front of the channel number are incorrect. Other text and epg data seems to be OK. I am using UTF-8 It depends on the used version of Ubuntu and the used PPA for the vdr. At least Ubuntu 12.04 has no vdr 1.7.33. Gerald !DSPAM:50cf8014266161366175190! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Betr: Re: xineliboutput reports no signal when started on a paused playback
Am 09.12.2012 10:14, schrieb cedric.dew...@telfort.nl: I agree this behavior is normal and technically correct. I think its a bit confusing, because when I see no signal, i think there's something wrong with the receiving hardware, like crashed DVB-t receivers, loose antenna and so on. Xineliboutput is aware the stream is paused. Therefore I can think of 2 solutions: 1)Display a screen that says Paused instead of No signal And how shall xineliboutput notice the difference? 2)Unpause, and then re-pause the stream, just long enough to let VDR send an image. Xineliboutput didn't pause the stream, so it is not the job of xineliboutput to unpause the stream. Gerald !DSPAM:50c46e6f187481547110970! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] get a segmentation fault when starting vdr (backtrace included)
Am 2012-11-30 10:17, schrieb Lars Hanisch:
Looks like the pointer returned by sscanf is not valid:
32: bool tComponent::FromString(const char *s)
33: {
34: unsigned int Stream, Type;
35: int n = sscanf(s, %X %02X %7s %a[^\n], Stream, Type,
language, description); // 7 = MAXLANGCODE2 - 1
36: if (n != 4 || isempty(description)) {
37: free(description);
38: description = NULL;
39: }
40: stream = Stream;
41: type = Type;
42: return n = 3;
43: }
From man sscanf:
The GNU C library supports a nonstandard extension that causes
the library to
dynamically allocate a string of sufficient size for input
strings for the %s
and %a[range] conversion specifiers.
This is the reason why it doesn't work with ulibc.
Gerald
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.32 plugin dvbhddevice fails
Am 19.11.2012 05:27, schrieb Richard Scobie: I have just upgraded from vdr-1.7.31 to vdr-1.7.32 with S2-6400 and on making plugins, I receive the following error: make[2]: Entering directory `/home/rs/vdr-1.7.32/PLUGINS/src/dvbhddevice/libhdffcmd' gcc -O3 -Wall -fPIC -shared -o libhdffcmd-0.1.0.so bitbuffer.o hdffcmd_av.o hdffcmd_base.o hdffcmd_generic.o hdffcmd_hdmi.o hdffcmd_mux.o hdffcmd_osd.o hdffcmd_remote.o /usr/bin/ld: bitbuffer.o: relocation R_X86_64_PC32 against undefined symbol `memset@@GLIBC_2.2.5' can not be used when making a shared object; recompile with -fPIC /usr/bin/ld: final link failed: Bad value collect2: ld returned 1 exit status make[2]: *** [libhdffcmd-0.1.0.so] Error 1 As -fPIC is being used, I am not sure how to handle the comment, recompile with -fPIC The error message asks for compile with -fPIC, but the command you show is the link, not the compile command. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] emergency restart is too fast for my USB DVB-T receiver
Am 28.10.2012 20:50, schrieb cedric.dew...@telfort.nl: Hi All, The problem is that the kernel does not reinitialize the receiver until nobody is using the device. reinitialize takes a few seconds, but vdr does not release the device long enough for that to happen. The result is that vdr restarts many times. The dynamite plugin should handle this for you. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Please share your systemd (Upstart) service file
Am 28.06.2012 09:01, schrieb Ludwig Nussel: Manuel Reimer wrote: Ludwig Nussel wrote: Yes. Not only for better systemd integration but in general it would be better if vdr could work without requiring any external scripting or configuration. You need some external script to call VDR as somewhere it is required to configure plugins and plugin parameters and many more stuff, VDR gets via command line options. That's the current state. I can't think of a good reason why it has to stay that way though. VDR itself could have a menu that allows to enable, disable and configure plugins. I can't see a benefit of this approach. At least for distributors it would get more complicated to install plugins with a specific default configuration, because that would mean all configuration informations would go into the setup.conf and it is no good idea to manipulate this file from outside. I would like to see the first user of this idea to try to disable a plugin that prevents the start of the vdr because of binary incompatibility. Must be funny. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR form packages
Am 12.05.2012 17:32, schrieb VDR User: On Sat, May 12, 2012 at 7:47 AM, abangab...@t-ipnet.net wrote: I just noticed, that the missing plugins for squeeze are already in Tobi's VDR repository. Sorry for the confusion! But I can't upgrade: The following packages have unmet dependencies: vdr-plugin-chanorg: Depends: vdr-abi-1.7.23-multipatch which is a virtual package. vdr-plugin-burn: Depends: vdr-abi-1.7.23-multipatch which is a virtual package. vdr-plugin-imonlcd: Depends: vdr-abi-1.7.23-multipatch which is a virtual package. Any ideas? Do all those plugins _actually_ depend on that patch? I can't imagine they do. Just remove the dependency. If they work, the debian/control file needs to be fixed so the needless dependency is removed. Ist is not a patch. It is the name of the ABI version. Debian packages are using this ABI version to prevent that vdr and vdr plugins with different ABIs get mixed up. The error message means, the mentioned plugins do not belong to the vdr that abang is using. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR form packages
Am 2012-05-08 14:16, schrieb Marx: Hello I use Debian for years and to keep it clean I'm trying to use all software from packages. It generally works, hovewer I have problem with VDR, XBMC and drivers. Usually to have the newest driver I need to use some unstable version of VDR with the newest possible kernel. VDR in Debian is an option, hovewer it's usually behind the newest VDR, and number of plugins in repository is low. This lead to alternative repositories. I know two valuable: e-tobi and yavdr. I was using e-tobi but it lately isn't updated to the newest VDR. Yavdr is built on top of Ubuntu, and while it generally works on Debian, it's not recommended (some things doesn't work). So there is an option to build packages myself - really no option, because I have to make package manually for every plugin and for every new version of VDR. Any idea? Any idea to what? Your have not asked any questions. What do you want to know? Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Memory leak (was Re: Channel 4 HD on Freesat)
Am 2012-03-26 16:44, schrieb Tony Houghton: I was probably still running it when I thought I was testing without a few months ago, because I didn't realise the debian init script/loader now automatically loads all installed plugins, not just the ones in order.conf. I am not aware that this ever has been the case. Must be more than 5 years ago then. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.24
Am 2012-03-02 00:18, schrieb Tony Houghton: Going off on a tangent, there's been some discussion about Pause and rewind live TV. That could be implemented fairly easily in clients with a big RAM buffer, without adding any complexity to the server. Big RAM buffer means long breaks between channel changes. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] SoftHDDevice
Don't worry just post in english, you'll get the answer also in english. Or feel free to open a new one in english, you will get answers in english ... ;-) Thanks, I just send him a private message providing a link to this thread and asked that he read it when he has a few free minutes so I don't have to copypaste. He told already in the vdr-portal that he wouldn't like to subscribe to this list. Generally it might be better if you would have a little bit more work doing cutpaste than the plugin author, because he is very busy working on the plugin. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LiveBuffer for vdr 1.7.x
And no, this patch is not from Gerald D. as the header of the patch might imply ;) regards, Tim It is true that the code in the original patch is not made by me, but the patch is made by me, because I had to manipulate the original patch so that it fits to the changes the yaVDR-Team made to the vdr. This is why my name is shown there. If a patch author wants to be mentioned, I would apply to them to not only patch the code, but to add a line with their name to the changelog file too. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UK FreeviewHD and VDR
If that's not doable, I guess I'll build a new Ion-based box and use xine for output. The problem then is that you don't tend to get many PCI slots for DVB cards (well, not with the small Atom boards). Maybe I could just keep the current vdr box (2.66 MHz P4) and stick an Nvidia graphics card in it. Decisions decisions... Let your DVB-Cards in your vdr box and stream to the Ion box either by using a vdr instance on both boxes and use streamdev between them, or having only a vdr instance on the ion box and use vtuner to stream directly from the DVB cards on the vdr box to the ion box. Currently I am testing vtuner on a Seagate Dockstar with 2 sundtek DVB-C USB sticks that is streaming to a Zotac HD-ID 40. It is promising. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UK FreeviewHD and VDR
On 12 August 2011 12:33, Gerald Dachs v...@dachsweb.de wrote: Currently I am testing vtuner on a Seagate Dockstar with 2 sundtek DVB-C USB sticks that is streaming to a Zotac HD-ID 40. It is promising. FYI vtuner is available here http://code.google.com/p/vtuner/ And here for Ubuntu Natty https://launchpad.net/~yavdr/+archive/unstable-vdr/ And in this dockstar repository: deb http://dockstar.yavdr.org unstable/ deb-src http://dockstar.yavdr.org unstable/ Currently I am working here on a version that uses memory mapping between client and kernel module that needs much less cpu: https://github.com/gdachs/vtuner. I want to simplify the client even more but I am not ready. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] will VDR run on this?
http://www.geek.com/articles/chips/raspberry-pi-25-pc-goes-into-alpha-production-20110728/ Any thoughts? VDR runs just fine on a seagate dockstar, so I see no reason why it shouldn't run on this device, but I don't believe that it has enough power show the TV signal via hdmi. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] cppcheck: VDR 1.7.18: [timers.c:53]: (error) snprintf size is out of bounds
Am Wed, 15 Jun 2011 18:34:59 +0200 schrieb Klaus Schmidinger klaus.schmidin...@tvdr.de: ...this should be sizeof(file) - 1 Thanks for the bug report. This is no bug. The size parameter includes the '\0' byte. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TT Premium S2-6400
Am Tue, 19 Apr 2011 12:53:18 -0700 schrieb Timothy D. Lenz tl...@vorgon.com: I just looked at the pdf on this card. Euro only as it only supports PAL. Also, I just got my new 32 TV in dec and noticed that most where 1080p. There where few new 1080i. The local TV dealer said companies are discontinuing 1080i. Many new TV's even upscale to 120 or 240 creating interpolated frames. This card only goes to 1080i. It's already outdated. Totally nonsense, tell me where are the TV provider that sends 1080p? Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] dynamite plugin
L. Hanisch d...@flensrocker.de writes: questions : - have you considered changing the way vdr detects adapter on startup ? for instance vdr won't detect /dev/dvb/adapter1 if /dev/dvb/adapter0 does not exist. this might happen when using udev rules and restarting vdr while a module isn't loaded Not sure what you mean. There is no reason anymore to restart vdr, even not after resume from suspend2ram. Dynamite is signaled by udev that a new adapter is detected. So it is not important whether the vdr sees an adapter, or not. - what about a github tree of vdr with your patch already applied ? I know it is not what you asked for, but the vdr 1.7.17 in the unstable-vdr PPA from yaVDR uses the plugin already. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Messages from Lirc have to be longer than 21 chars, why?
Hi,
during my tests with eventlircd I noticed that the up key of my remote
didn't work with vdr, but with xbmc. I debugged vdr and stumbled above
the line lirc.c:89 (not vanilla sources):
if (ready ret 21) {
Lirc sends this to vdr:
67 0 KEY_UP devinput
So this key gets ignored, all other key have longer names and are
working. Solution seems to be easy. Instead of 21 I could use 19, but
with inputlircd I get this string for the same key:
67 0 KEY_UP event7
It would get ignored again.
What is the intention for this condition:
ret 21?
Is it to make sure to not get garbage from lirc? But why 21 chars? What
would be a better length, or a better check?
Gerald
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [yavdr] Fw: RfC: add encryption and compression to VDR
Am Tue, 25 Jan 2011 17:44:23 +0100 schrieb Steffen Barszus steffenbpu...@googlemail.com: On Tue, 25 Jan 2011 17:12:24 +0100 (CET) Gerald Dachs g...@gmx.de wrote: Wegen der Diskussion über live im moment, nur nochmal um es in Erinnerung zu rufen die mail von Tadi: I just checked the web-page[1] and found out that one of the newest features of cxxtools is now native support for xmlrpc (without the need for tntnet). It will also implement the complete http server needed. Das würde den HTTP-Server-Part eines solchen Plugins natürlich deutlich vereinfachen: http://www.tntnet.org/cxxtools_httpserver.cpp.html Schade das noch keine Doku online ist für den JSON-Part. hier steht was zu JSON http://www.tntnet.org/howto_xmlrpc.html Die Seite kenne ich, da steht nur zweimal das Wort JSON ;) Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am Sun, 16 Jan 2011 12:19:41 +0100 schrieb Gero geronimo...@gmx.de: Hello, thank you for the link. Gerald Dachs wrote: It is not really what you are looking for, ... Hm - may be I missed the real thing, but I did not find anything about installing 2 vdr instances on the same machine. Maybe you didn't find anything about installing a second instance, because it has not to be done. You only have to start your already installed vdr with another configuration. This happens in the addon I pointed you to. You should really look more carefully into it. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] new OSD system
Am Sun, 16 Jan 2011 16:27:47 +0100 schrieb Gero geronimo...@gmx.de: I beg your pardon second time! I don't use yavdr and I'm not willing to change my vdr to yavdr - so using your addon is no acceptable solution - no matter how good your addon might be! You know, that the reason for not using yavdr is ubuntu being the base of yavdr and that my rejection is NOT related to the yavdr team in any kind! Sorry, but I think I don't ask you for too much, if I ask you to look into the sources of this addon yourself. It is really very easy. You can find it here https://launchpad.net/~yavdr/+archive/unstable-yavdr/+sourcepub/1385820/+listing-archive-extra Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Developer versions
On 01/13/11 13:31, Rolf Ahrenberg wrote: On Wed, 12 Jan 2011, VDR User wrote: And you get VDR's full osd doing this? FYI, xineliboutput provides three different OSD implementations: xinelib, composite HUD, and opengl HUD. For example the composite HUD OSD is drawn directly onto transparent window located exactly over the (xine-lib powered) video window and therefore is completely independent from the actual video decoding library. I'm curious as to how you got the composite and opengl HUD's working, I have been far from successful. It appears to just not work at all :S Both are working. You need a compositing manager like xcompmgr or compiz for the first possibility, or the option --opengl-all (not sure about correct typing for the second possibility. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Developer versions
oh, so now we need opengl and a compositing manager on top of everything else? You miss the point. If you would quote mails right you would have noticed that I answered a sentence that told that it doesn't work at all. How did I miss this point? have been far from successful. It appears to just not work at all :S Both are working. You need a compositing manager like xcompmgr or compiz for the first possibility, or the option --opengl-all (not sure about correct typing for the second possibility. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Developer versions
And yavdr doesn't include sxfe for some reason. That is complete nonsense: https://launchpad.net/~yavdr/+archive/stable-vdr/+files/xineliboutput-sxfe_1.0.6%2Bcvs20110110.1350-0yavdr0_i386.deb Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Request: E parameter in channels.conf for epg scan
Am 13.12.2010 23:21, schrieb Gerald Dachs: Maybe I understand the code in epg.c wrong, but it look like that the whole epg.data file is always read and write complete by the vdr. Even if only one record has to be changed. Maybe the coding with sqlite will look less elegant, but it will be much faster. I/O is always expensive. Afaik the epg.data will be read at startup and written at shutdown. In the meantime the epg data will be read from memory and thats surely much faster than via sqlite. This is true, but not if you update it from an external source, and this was the reason for this discussion. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Request: E parameter in channels.conf for epg scan
Am Mon, 13 Dec 2010 22:19:45 +0100 schrieb Udo Richter udo_rich...@gmx.de: Never under-estimate a native C/C++ coded data structure, at least if it's a smart one. Reading/writing to a tree or hash might be done before the sql interpreter even starts. Maybe I understand the code in epg.c wrong, but it look like that the whole epg.data file is always read and write complete by the vdr. Even if only one record has to be changed. Maybe the coding with sqlite will look less elegant, but it will be much faster. I/O is always expensive. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] dvb devices on demand patch
Am Sat, 4 Dec 2010 10:09:42 -0800 schrieb VDR User user@gmail.com: b) have a beginning of dvb device hotplug - if dvb devices are discovered on demand, its a good chance at a later stage to also add and remove cards on the fly. There is sure some notification required from udev to vdr so it can keep internal reference of the how many devices are there. I wonder if this is actually useful. Is there anyone that would need/want this in the real world? In which world did you live the last months ;) ? Sorry, I couldn't insist. Our VDR-Distribution yaVDR is optimized for a short boot. With old fashioned PCI cards you can get down to 6 seconds boot time since grub, but if one of our user decides to buy another p. e. usb device, we have to delay the boot up to 30 seconds to allow the usb device to get ready. With device hotplugging there would be no need to wait for this device and the user would already see tv 30 seconds earlier. Believe me there are users that thinks this matters. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine vdpau not working?
Am Sat, 9 Jan 2010 12:25:51 +1300 schrieb Simon Baxter linu...@nzbaxters.com: ls -l /usr/local/lib/libxine* Any ideas?? What am I doing wrong? Good chance that you have built against another libxine that is in /usr/lib. Use --prefix=/usr with autogen, so that the new libxine replaces the old one, or use our ppa: https://launchpad.net/~the-vdr-team/+archive/vdr-ubuntu-karmic Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] rewind recordings doesn't work with xineliboutput and vdr 1.7.10
Hello, if I try to rewind a recording, I can see the movie going fast backwards, but if I stop rewinding, the movie continues from the moment I started the rewinding. This doesn't happen with xine-ui and the xine-plugin and with xbmc using the streamdev-plugin, so I believe it is a xineliboutput problem. I use a cvs snapshot from today and vdr 1.7.10 on Ubuntu 9.10, xinelib 1.2 with vdpau patch r285 and durchflieger cropping patch. I posted this already on the xineliboutput-user ML, but this list seems to be dead. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
Am Fri, 25 Dec 2009 11:43:06 +0100 schrieb Carsten Koch carstenkochelsd...@web.de: On Thu, 2009-12-24 at 17:55 +, Tony Houghton wrote: ... + I originally set up the system as a diskless (nfsroot) system, but KDE 4 (I am using OpenSuSE 11.2) performs unbearably slow, so I was forced to install a hard disk. Couldn't you use a much lighter desktop if this is a PC especially for VDR? Running VDR is important, but not the only purpose. Surfing the internet, watching DVDs and BlueRays, etc. is a lot of fun on an HD beamer. :-) The desktop doesn't play DVDs or BlueRays. This is done by xineliboutput, xine and xbmc ... To start xbmc a lircrc skript for irexec would be enough. No need for a desktop. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau setup steps for vdr client
Am Wed, 25 Nov 2009 21:50:16 +0200 (EET) schrieb Mika Laitio lam...@pilppa.org: I just bought a zotac ion motherboard and plan to harness it in the weekend as a ultimate super master dream vdr client for my 19 monitor :-) Sofar I have used to run vdr-xineliboutput in my clients and would like to do that also with this machine if possible. Currently my server runs vdr 1.6 but I plan to update that also to 1.7.10. You could give this a try: https://launchpad.net/~the-vdr-team/+archive/vdr-ubuntu-karmic Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] strange issue with DVB-S2 and VDPAU
I will reinstall Ubuntu 9.04 on this weekend, and I hope that will help. This is never a good idea, this way you will never find out the reason for the problem. So there is no warranty that it will not happen again. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] dxr3 plugin compilation error
Am Tue, 27 Oct 2009 09:31:11 -0700 schrieb VDR User user@gmail.com: Try this patch: --- vdr-1.7.5/vdr.c.orig2009-04-12 11:05:51.0 -0700 +++ vdr-1.7.5/vdr.c 2009-04-12 11:07:08.0 -0700 @@ -32,6 +32,7 @@ #include pwd.h #include signal.h #include stdlib.h +#include linux/types.h #include sys/capability.h #include sys/prctl.h #include termios.h #include stdint.h should do it too. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Enhancement request: sorting recordings by date pressing
I like to patch vdr as little as possible to keep it stable so not too keen on applying the Liemikuutio all-in-one patch. Is this patch available stand-alone for 1.7.9? For what reason do you not give the extrecmenu plugin a try? Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [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? Why is that an advantage of xine-vdr? I toggle between xineliboutput and xbmc. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau patches
I take it you are using them on xinelib 1.2, are you using xineliboutput 1.0.4 or cvs? I use 1.0.4, cvs has currently audio problems. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] repeat vol key
Am Sun, 7 Jun 2009 19:01:00 +0200 schrieb marti...@embl.de: in /etc/vdr/remote.conf I have (among others) these two entries: LIRC.Volume+VolumeUp LIRC.Volume-VolumeDown My wife complains that to increase the volume she has to press many times VolumeUp rather than simply hold it down. Is there something I can do to make her happy? Recently I have read about some simple USB IR receivers that don't send the toggle bit that lirc needs to recognize the hold of a button. I suppose you use one of them, because normally it works like your wife expects. So I believe you should exchange the IR receiver. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
VDR User schrieb: VDR + hdtv has been pretty stable for me for some time now. The few problems I ran into (with VDPAU) were quickly fixed by the xine-vdpau devs. I'm not the only one either, I know a bunch of guys doing the same. It's a highly discussed topic and I'm honestly surprised to hear someone suggest it's in an unstable/crashing/unusable state. My experience has been basically the opposite of that. I would recommend you make sure to have a nice good signal, proper configurations, etc. I agree with VDR User, I use it for months now without problems. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
Nicolas Huillard schrieb: Gerald Dachs a écrit : VDR User schrieb: VDR + hdtv has been pretty stable for me for some time now. The few problems I ran into (with VDPAU) were quickly fixed by the xine-vdpau devs. I'm not the only one either, I know a bunch of guys doing the same. It's a highly discussed topic and I'm honestly surprised to hear someone suggest it's in an unstable/crashing/unusable state. My experience has been basically the opposite of that. I would recommend you make sure to have a nice good signal, proper configurations, etc. I agree with VDR User, I use it for months now without problems. Could you please both detail a bit the DVB sources, software versions, plugins, patches, etc. related to HD, that you actually use now ? (DVB-T, DVB-S or S2, DVB kernel patches, VDR core, xineliboutput or xine plugin, xinelib patches...) DVB-C, stock Jaunty kernel, vdr 1.6.0 + extension patch v72 + h264 patch, nvidia-driver 180.60, xine-lib 1.2 + vdpau patch r262 + crop patch v5, xineliboutput 1.0.4 + crop patch v5, vdr-sxfe Maybe there is an english howto somewhere ? Here it is: install jaunty and add the packages from my repository https://launchpad.net/~gda-dachsweb/+archive/vdr, but there is no support from me. I have not enough time. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
Pertti Kosunen schrieb: Gerald Dachs wrote: DVB-C, stock Jaunty kernel, vdr 1.6.0 + extension patch v72 + h264 patch, nvidia-driver 180.60, xine-lib 1.2 + vdpau patch r262 + crop patch v5, xineliboutput 1.0.4 + crop patch v5, vdr-sxfe What is crop patch and where do i find it? It cuts the black borders from the letterbox format: http://vdr-portal.de/board/thread.php?threadid=86804 Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
jori.hamalai...@teliasonera.com schrieb: I think it would also help if we could reach an agreement over the terms stable and good quality and everything is working because they are highly subjective. For me I'd add a class; Set-top-box quality For me there exists another class: Good enough Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
Tony Houghton schrieb: On Fri, 5 Jun 2009 10:06:20 +0200 (CEST) Gerald Dachs v...@dachsweb.de wrote: Here it is: install jaunty and add the packages from my repository https://launchpad.net/~gda-dachsweb/+archive/vdr, but there is no support from me. I have not enough time. They look useful, but are the deb source files available so Debian users can build similar packages? yes Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ExtensionHD and VDR 1.7.6
Magnus Hörlin schrieb: xineliboutput HD OSD works as of wednesdays cvs. If you mean an OSD with more than lets say 1000x800 Pixels, I forgot the exact numbers, I use this already with the stable xineliboutput 1.0.4. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to change channels.conf externally into a running vdr?
Seppo Ingalsuo schrieb: Does it synchronize channels too? Forget it, I wrote nonsense, sorry Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] epgsearch as default EPG browser/guide?
Am Wed, 27 May 2009 21:40:58 +0200 schrieb Nicolas Huillard nico...@huillard.net: Alex Betis a écrit : Is there a way to configure VDR show the epgsearch plugin as default guide? Currently I can access the plugin by pressing green button or from the menu. I'd like it to replace the default EPG browser when pressing guide button and another place (less important for me) when pressing info button and than back button. I recently read about a menu plugin, which handles all the menu system, right from the main menu. The menu tree appears to be configured with an XML file, which calls standard submenus, plugin menus, or even launches commands. Unfortunately, I can't remember where, and I have no browsing history at the moment. Two plugins come to my mind, the submenu and the menuorg plugin. It seems that in this list the vdr-wiki is generally ignored, but why? The plugin list http://vdr-wiki.de/wiki/index.php/Plugins is very informative. Okay, not all entries exist in the english version, but it doesn't hurt to learn a little bit german ;) Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
Am Sat, 09 May 2009 10:33:58 +0300 schrieb Jouni Karvo jouni.ka...@iki.fi: No, I meant deleting automatically the pause-live-TV recording. That recording is conceptually just a technical implementation issue (and should not be visible in the recordings list, even, in my opinion). The end user needs not care for the object structure of VDR source code, and the implementation of pause-live-TV is in the same category. This is the first good idea in this thread. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
Am Sat, 9 May 2009 06:15:18 -0700 schrieb VDR User user@gmail.com: On Sat, May 9, 2009 at 4:05 AM, Gerald Dachs v...@dachsweb.de wrote: Am Sat, 09 May 2009 12:38:39 +0200 schrieb Klaus Schmidinger klaus.schmidin...@cadsoft.de: It also raises several questions: - When should such a recording be deleted? If it gets deleted as soon as replay is stopped, you'll be very surprised when you (or your kids ;-) inadvertently press Stop, and you can't resume replay. Shit happens, not really a problem. Kids pressing remote buttons is one of the main reasons this thread was started so apparently for some people it really _is_ a problem. I had already answered the OP how to solve this problem in a former thread. Gerald ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 2 little bugs report
Quoting marti...@embl.de: Also one little thing that is driving me crazy. My 3 years old daughter presses accidentally the Pause button and starts al l sort of instant recordings silenty, my wife then complains vdr is broken because she can´t change channels. What I am asking for is for some possibility to make the instant recording ask for confirmation before starting the instant recording. My 1.5 years old son and my 3 years old daughter would do the same, but I have found an easy workaround. I put the remote control out of their reach. Gerald This message was sent using IMP, the Internet Messaging Program. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
