Re: [vdr] vdpau experience
On Tue, 2009-10-27 at 13:46 +1000, Torgeir Veimo wrote: > 2009/10/27 Malcolm Caldwell : > > Which is a shame for me, as I like xineliboutput's media player. > > Unfortunatly the media player crashes xineliboutput when I use vdpau, > > although I have not tried patching to the latest patch for xine-lib. > > This might just be due to the particular way some files are encoded? > Or does it happen for any file? It happens for every file that I tried. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdpau experience
On Mon, 2009-10-26 at 12:05 +0100, Christian Tramnitz wrote: > Theunis Potgieter wrote: > > I reverted to older version of vdr-xineliboutput (20091013) where the > > channel becomes garbage (green blocks) after a while when cropping is > > enabled. I also see these green blocks when changing a channel. With > > vdpau, when using streamdev-client with a bad wifi connection, vdpau > > does not seem to get to correct it self gracefully like xxmc/xvmc+vlc > > video output driver of xineliboutput. It becomes so bad that I have to > > restart vdr-sxfe. vdpau doesn't seem to be production ready yet, > > because I had it run for 18 hours and... well not in my opinion, I > > will be reverting back to xxmc for now. This was all tested on SD > > channels. > > To use the advantages of vdpau you don't necessarily need xineliboutput, > a lot of users have a better experience (especially stability) using the > vdr-xine-plugin. Which is a shame for me, as I like xineliboutput's media player. Unfortunatly the media player crashes xineliboutput when I use vdpau, although I have not tried patching to the latest patch for xine-lib. > Using the xine-post-plugins from xinelibout you have the best of both > worlds and can use cropping in combination with xine-ui. > > There is a very good (but german) howto here: > http://www.vdrportal.de/board/thread.php?threadid=89920 > I guess most of the steps are self-explaining, if not just ask in this > thread and I'm sure you'll also get help in english! > > > Best regards, > Christian > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe buffer empty
On Tue, 2009-09-29 at 17:33 +0300, Seppo Ingalsuo wrote: > Reverse patching this one (just patch view from the same link) > > http://xineliboutput.cvs.sourceforge.net/viewvc/xineliboutput/vdr-xineliboutput/xine_input_vdr.c?view=patch&r1=1.278&r2=1.279&sortby=date > > seems to work for me for current CVS version. What problem does this fix? On my setup, things run fine for a minute or so, and then audio starts to break up more and more. It finally stops for a few seconds and then things seem to "reset", and audio/video work fine again for a few minutes, until the whole process starts again. Will reverting this fix my problem? > BR, > Seppo > > > On Mon, 2009-09-28 at 18:35 +0300, Seppo Ingalsuo wrote: > > Shouldn't write in hurry :^) > > > > On Mon, 2009-09-28 at 17:18 +0300, Seppo Ingalsuo wrote: > > > On Sun, 2009-09-13 at 11:08 +0400, Goga777 wrote: > > > > > > > please try to revert this comment > > > > http://xineliboutput.cvs.sourceforge.net/viewvc/xineliboutput/vdr-xineliboutput/xine_input_vdr.c?r1=1.278&r2=1.279&sortby=date > > > > > > > > > > I was using CVS version from August 1st to avoid audio breaks. There are > > > problems so I've had interest to upgrade. > > > > The other problem with this otherwise pretty OK version is that vdr-sxfe > > stops occasionally to respond to Lirc and keyboard. Also zapping to any > > HDTV channel freezes vdr-sxfe but HDTV functionality is not a big > > priority for me at the moment. > > > > I have sampled every now and then xineliboutput CVS. E.g. Aug 24th > > version has bad audio. I haven't tried to iterate where the problems > > exactly started. > > > > > With CVS version from > > > yesterday September 27th I get these problems again. > > > > Here I meant audio breaking problems with live TV and recordings that is > > pretty annoying. > > > > BR, > > Seppo > > > > > > > > Would this proposed change help? The diff is rather large, do I need to > > > revert everything shown by this link (or just some commment somewhere)? > > > > > > Is the change needed on server, client or both? > > > > > > Thanks, > > > Seppo > > > > > > > > > > > > ___ > > > vdr mailing list > > > vdr@linuxtv.org > > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > > > > ___ > > vdr mailing list > > vdr@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-xine 0.9.3 audio problems
On Sat, 2009-10-03 at 23:08 -0700, VDR User wrote: > On Sat, Oct 3, 2009 at 4:29 PM, Simon Baxter wrote: > > Card is a NVIDIA GPU GeForce 8400 GS too, but I'm not using the vpdau - as I > > currently have no HD or H.264 content. > > > > Do you think I should change to vpdau anyway?? > > I'm a big fan of vdpau so my answer is automatically to give it a try > since you've got nothing to lose. Except media-player if you are using xineliboutput. vdpau makes it crash. (For me). > Cheers > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe buffer empty
I don't want to steal a thread, but my questions are related: I guess there is something I don't understand: Does this "*-crop-v9" patch offer anything that the patches from http://www.jusst.de/vdpau/files/xine-lib-1.2/ do not, besides the autocrop functionality? And what is this autocrop functionality good for: I have a 16:9 set, and the content I want to view is 16:9 material, with occasional 4:3 encoded into a 16:9 frame. So what would this auto crop business gain me. I have one issue with xineliboutput and vdpau: when I view xvid files vdr-sxfe crashes with an error from glibc. Is there a known fix for this. "On Sat, 2009-09-19 at 13:33 +0400, Goga777 wrote: > > > which xineliboutput version are you using ? cvs ? > > > any patches from here ? > > > http://www.vdr-portal.de/board/thread.php?threadid=86804 > > > > > > Goga > > > vdr 179 + xbmc > > > > vdr 1.7.8 + xinelibeoutput cvs -minus said patch. Am using the > > did you try vdr 179 with cvs xineliboutput ? > > > xine-lib 1.2 vdpau branch, which I previously used to run xine with > > have you any difference between xine-lib 1.2 vdpau branch and xine-vdpau > branch ? > > > I'm amazed that vdr-sxfe manages to completely avoid any judder in > > playback, something which I haven't really seen since I ran with a ff > > card. > > did you try with local frontend ? not with vdr-sxfe > > >There's some occasional loss of audio lipsync, and channel > > change is not "smooth"; I see both audio and video freeze for a few > > frames. I guess both of those are work in progress. > > > > Would any of the patches from the vdr-portal thread above help on those > > issues? > > You can try that patch xine-vdpau-r281-crop-v9.diff.gz > http://www.vdr-portal.de/board/attachment.php?attachmentid=22895 > > there're good reports about it > http://www.forum.free-x.de/wbb/index.php?page=Thread&postID=8313#post8313 > > > I have to say that vdpau is looking like a very good solution for hdtv > > playback, it's just a shame that they didn't implement field parity > > support for interlaced material. > > +1 > > Goga > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Unable to record ITV HD (was : ITV HD)
On Sun, 2009-06-21 at 18:20 +0200, Christian Tramnitz wrote: > Klaus Schmidinger schrieb: > > Well, if they don't broadcast their Vpid in the SI data, how is a > > receiver supposed to know what to receive? > > > > Maybe you should complain to the broadcaster about this. > > > > Klaus > > Afaik this is intentional to limit the scope of viewers to users of > their "Freesat" receivers. So this problem also exist for other > (non-freesat) receivers out there that do not allow manual vpid > settings. While vdr does allow setting the vpid (while not auto-updating > channel data) in this case recording seams to fail anyway while live > view is working. I don't know about the recording problem, but I have dealt with this type of issues (auto-updating overwriting channels.conf) by having two copies of the channel: one with rid=0 and one with rid=1. When vdr updates the channel, it only updates the one with rid=0, leaving the other along. I then put the one with rid=1 at the end of my channel list when I never try to tune to it. A bit of a hack, but it works. > > I know, this is non-standard behaviour and you probably do not want to > support this by adjusting vdr. On the other hand, if (with manual > interaction) its possible to view the channel, shouldn't it also be > possible to record it? > > > Best regards, > Christian > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Any really working HD video output systems for VDR?
One "problem" with vdr is that it is not obvious from this list when people are just happy and thing are just working fine. Maybe such success stories are posted to the VDR portal/forum. But that is mostly in German, so not obvious to us English speakers. (Lack of German is failing on our part, I am sure, but so things are). People only post to this list when things are wrong, so things like software decoding, vdpau etc etc seems difficult and next to impossible. On Thu, 2009-06-04 at 21:42 -0700, VDR User wrote: > 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. > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelibout sxfe freeze
On Thu, 2009-05-21 at 12:38 +0300, Rolf Ahrenberg wrote: > On Wed, 20 May 2009, Malcolm Caldwell wrote: > > > Is sxfe freezing a known issue? Any fix? > > Yes, I tracked down the bug and informed the author months ago. Last > time I communicated to him, he had a (possible) fix running on his > development setup, but I haven't checked lately, if it had been commited > to CVS. I am running CVS, so my guess is that there is no fix committed yet! > > BR, > -- > rofa > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelibout sxfe freeze
On Wed, 2009-05-20 at 12:23 +0300, Pertti Kosunen wrote: > Malcolm Caldwell wrote: > > Is sxfe freezing a known issue? Any fix? > > It freezes eventually with every software combination i have used (very > infrequently at best). I used softdevice for years and honestly do not think freezing was a problem. > Workaround is to kill frontend with remote and irexec. I run frontend in > loop, so it starts again in 2 sec. I have setup a key on the physical keyboard to do such. Thanks for pointing out that I can check the return values, that could be useful. One thing that I notice is that when vdr-sxfe freezes I can no longer do a svdrp GRAB. So, perhaps a cron job can be setup to try a grab, and if that fails restart vdr-sxfe. Or, xineliboutput could implement a PING command. A hack, yes, but it still might be better than frozen video! > > /etc/lircrc: > begin > remote = origen > button = Record > prog = irexec > repeat = 0 > config = killall -9 vdr-sxfe > end > > vdr-sxfe.sh: > #!/bin/bash > while true; do > vdr-sxfe --options.. > if test $? -eq 0 -o $? -eq 2; then > exit > fi > /bin/sleep 2 > done > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xinelibout sxfe freeze
On Wed, 2009-05-20 at 10:03 +0200, Jaroslav Bachorik wrote: > Do you happen to use xine-lib 1.2dev ? No. I am on fedora fc10 and have: xine-lib-1.1.16.3-2.fc10.i386 > Exactly the same happens to me and I was able to track it down to closing and > deallocating the stream in xine-lib. I didn't investigate further as the > xine-lib 1.2 is in a development state still. > > JB > > > Pôvodná správa ---- > > Od: Malcolm Caldwell > > Predmet: [vdr] xinelibout sxfe freeze > > Dátum: 20.5.2009 02:27:41 > > > > Hello, > > > > After a hard disk crash I am rebuilding my vdr system. Of course, I am > > taking the opportunity to "upgrade" parts where needed. > > > > In the past I used softdevice with TVout, using a mga card and directfb. > > > > As I now have an HD LCD screen, I decided to try xineliboutput. > > > > I am running vdr with "-P xineliboutput --local=none --remote=37890", > > and then using a user account to run sxfe > > > > Everything is working except: sxfe freezes from time to time. When this > > happens ESC does not kill it, the only way to keep going is to kill the > > sxfe process twice (or do kill -9). > > > > It could be that this is because my DVB reception is quite bad at the > > moment (another issue, could be my antenna needs fixing. I changed > > dvb-t card to a nova 500 during my "upgrade"). > > > > Is sxfe freezing a known issue? Any fix? > > > > > > ___ > > vdr mailing list > > vdr@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > > > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xinelibout sxfe freeze
Hello, After a hard disk crash I am rebuilding my vdr system. Of course, I am taking the opportunity to "upgrade" parts where needed. In the past I used softdevice with TVout, using a mga card and directfb. As I now have an HD LCD screen, I decided to try xineliboutput. I am running vdr with "-P xineliboutput --local=none --remote=37890", and then using a user account to run sxfe Everything is working except: sxfe freezes from time to time. When this happens ESC does not kill it, the only way to keep going is to kill the sxfe process twice (or do kill -9). It could be that this is because my DVB reception is quite bad at the moment (another issue, could be my antenna needs fixing. I changed dvb-t card to a nova 500 during my "upgrade"). Is sxfe freezing a known issue? Any fix? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Editing usability
On Mon, 2009-05-11 at 07:06 -0700, VDR User wrote: > On Mon, May 11, 2009 at 1:36 AM, Stuart Morris > wrote: > > > > I haved lost count the number of times I have pressed the numbered keys on > > my remote by accident and then panic because I don't know how to undo what > > then happened. > > > > This is definitely a trap for unsuspecting beginners. > > I mean this in the nicest way possible but paying more attention to > what you're pressing would pretty much resolve your problem. > > In all honesty most of the complaints I've read have little or no real > issue with VDR itself but rather the users either not paying attention > to what they're doing, not bothering to read the manual & memorize the > few keys involved, and/or wanting VDR to kid-proof the remote for > them. It seems all of these "problems" could be eliminated with a > little extra effort by the user. That being said, if there's > something that could be done to help and Klaus is willing to do it > then super. Or better yet if someone else takes it upon himself to > create these patches so Klaus can be left to focus on the bigger fish > to fry. > > For the record, I have kids, who can be more like monkeys often times, > and have no problem keeping the remote away from their curious > fingers. Perhaps I should keep my remote at your house? :) > I've accidentally pressed buttons that had undesired actions > before as well. So, when I say these problems can be resolved with a > little more effort & attention on the users part, I'm speaking from > experience. Of course it's easier to decide you can't be bothered > with it on your end and ask someone else to fix it for you, but > truthfully speaking the user-side fix isn't exactly hard to begin > with. I guess we'll have to agree to disagree as to how serious of an > issue this stuff is, or whether it's even a problem with VDR itself or > not. > > Regards, > Derek > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
On Thu, 2009-05-07 at 09:39 +0200, Frank Scherthan wrote: > Hi Theunis, Hi list, I have read the manual. I understand how vdr works. I don't like finding 4 instant recordings going, using up disk space and 10 old instant recordings that no one actually wanted. IMHO: it is too easy to 'accidentally' bump the pause key. I have done it, my wife has done and my kids do it. I could re-read the manual but my opinion won't change. :) > Theunis Potgieter schrieb: > > Well honestly I'm confused. I use vdr 1.6 and when I press down or up > > it changes channel only. My vdr never pauses live tv. Mind you I don't > > have a pause key either and neither defined. So perhaps this is the > > way to for him. > > Why didn't you just read the manual? > It is all there! :) It is really great! > > The point is: keys do different things in differnet environments. > > In liveview, the "down"- key decreases channel by 1 > in replay-mode the "down"-key pauses the recording. > > If you define a pause-key, than this key pauses in replay-mode. > In live-view it creates an instant-recording, that is replayed and paused. > > Before anyone posts to this topic, would you please read the manual? > > > I think this whole thread would not exist, if anyone would have read the > manual ;) > > btw. the manual comes with every copy of VDR and can be read via web in > the WIKI: > http://www.linuxtv.org/vdrwiki/index.php/VDR_User's_Manual > > Frank, who read the manual ;) > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
On Sat, 2009-05-09 at 16:29 +0300, Lauri Tischler wrote: > VDR User wrote: > > On Sat, May 9, 2009 at 4:05 AM, Gerald Dachs wrote: > >> Am Sat, 09 May 2009 12:38:39 +0200 > >> schrieb Klaus Schmidinger : > >>> 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. > > The Real Problem is that people are too lazy to educate their brats > properly. For F sake. Do you have kids? You can educate a 5 year old, but a 2 year old? Have you even tried? Just to say: I am not lazy, and my kids are not brats, and I don't think I or the the others here who raised this issue deserve to be ridiculed. (Or perhaps you intended your post to be humorous??) > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
On Sat, 2009-05-09 at 06:15 -0700, VDR User wrote: > On Sat, May 9, 2009 at 4:05 AM, Gerald Dachs wrote: > > Am Sat, 09 May 2009 12:38:39 +0200 > > schrieb Klaus Schmidinger : > >> 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. Just to say: I have kids, and this happens to me. I go in every now and again and delete all the instant recordings. Not a big problem, but annoying. I once lost something I wanted because an instant recording filled the disk. (I should have set the priorities correctly. I know) If my remote has a pause key, I want it to work when I am replaying recordings. I don't want to remove that "feature". During live TV, I would prefer that the Pause key != Record. Perhaps a two step: press pause, and it says "Press OK to pause live TV"? > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update for certain channels
On Wed, 2009-01-28 at 08:39 +0200, Alex Betis wrote: > > On Wed, Jan 28, 2009 at 2:26 AM, Malcolm Caldwell > wrote: > On Tue, 2009-01-27 at 10:34 +0100, Matthias Dahl wrote: > > Hi. > > > > For certain situations, it'd be great to exclude some > channels from the > > automatic channel update. For example, when one has entered > a channel manually > > which broadcasts wrong channel informations. With the next > channel update, all > > is overwritten. So one has to either completely disable the > automatic updates > > or live without the channel for the time being. > > > > I had just a quick look over the vdr source and figured it > wouldn't be too > > hard to come up with a patch to support something like this > I guess. So I > > wanted to ask if this new feature would be considered ok for > inclusion into > > vdr-1.7.x or if there are reasons against it? Otherwise I > would put it on my > > todo list and get to it when I get some time... if no one > else does it in the > > meantime that is. :-) > > I deal with this type of problem by having two copies of the > channel, > with one with rid=1. The one with rid=0 will be automatically > updated > to incorrect values, while the one with rid=1 will not be > updated, so it > can be tuned as needed. > > Can you have 2 channels without changing anything in the code? > > I had to change some functions to have this. I found that VDR deletes > duplicate channels by default. > > > > What is rid by the way? Duplicates would be removed, but if one channel has rid=1 and one has rid=0 they are not exact duplicates. >From man 5 vdr: RIDThe Radio ID of this channel (typically 0, may be used to dis- tinguish channels where NID, TID and SID are all equal). The fields are separated by : and the last one is the rid. > > > > > Best regards, > > matthias. > > > > ___ > > vdr mailing list > > vdr@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update for certain channels
On Tue, 2009-01-27 at 10:34 +0100, Matthias Dahl wrote: > Hi. > > For certain situations, it'd be great to exclude some channels from the > automatic channel update. For example, when one has entered a channel > manually > which broadcasts wrong channel informations. With the next channel update, > all > is overwritten. So one has to either completely disable the automatic updates > or live without the channel for the time being. > > I had just a quick look over the vdr source and figured it wouldn't be too > hard to come up with a patch to support something like this I guess. So I > wanted to ask if this new feature would be considered ok for inclusion into > vdr-1.7.x or if there are reasons against it? Otherwise I would put it on my > todo list and get to it when I get some time... if no one else does it in the > meantime that is. :-) I deal with this type of problem by having two copies of the channel, with one with rid=1. The one with rid=0 will be automatically updated to incorrect values, while the one with rid=1 will not be updated, so it can be tuned as needed. > Best regards, > matthias. > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Freeview+ aka TV-Anytime Patch (updated)
On Mon, 2008-10-06 at 11:11 +0200, Klaus Schmidinger wrote: > On 10/06/08 11:06, Laz wrote: > > On Monday 06 Oct 2008, Frank Scherthan wrote: > >> Laz schrieb: > >>> On Sunday 05 Oct 2008, Gavin Hamill wrote: > On Sun, 2008-10-05 at 15:10 +0100, Dave P wrote: > >>> On another Freeview specific note, I'd love to have my channels > >>> renumbered to their "proper" Freeview numbers. At the moment, I have > >>> to go through and move them about by hand every time something > >>> changes! I don't think there is currently any support for assigning > >>> channels a specific number within vdr (probably not much point with > >>> gazillions of satellite channels but more useful with the handful of > >>> terrestrial Freeview ones in the UK). > >> man 5 vdr: > >> A group delimiter can also be used to just set the next channel’s > >> number, without an explicit delimiter text, as in > >> > >>:@201 > > > > That's what I mean by "doing it by hand"! My channels.conf is littered > > with those! > > > > ;) > > > > Would be nice if each channel entry had a field for channel number > > instead, especially when they helpfully decide to move a channel! > > > > It's also the way "real" set-top boxes do it. I think "scan" can output > > the channel numbers to a vdr-readable channels.conf but I think that just > > puts in a :@1, :@2, :@3, etc. every other line. Just doesn't seem neat to > > me, especially as the channel numbers are broadcast. > > > > I did start looking at this a while back but never got very far: might > > have another go... > > I don't think it makes any sense to put actual channel numbers into > each channel's line in channels.conf. For one, what if different > providers want to use the same channel numbers? And: what if channels > are moved around, inserted or deleted? It might not make sense in your environment. In the UK and here in Australia there are fixed, advertised channel numbers. It makes sense if something is advertised as being on channel 20, then pressing '2' and then '0' should tune to that channel. "Makes sense" means that "I can describe it to my wife". > The channel numbers are implicitly derived from the position of each > channel in the channels.conf file. Offsets can be suggested with :@nnn > lines, but are only hints and may be ignored if there are too many > channels before them to actually implement the desired numbers. Maybe I should try to explain this to my wife instead? > Klaus > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Sequential or random play?
On Sun, 2008-07-06 at 20:09 +0300, Teemu Suikki wrote: > Hi! > > Is there an easy way to add sequential or even random playback to VDR? This may or may not be a help for you: I use softdevice and softplay to do this. Softplay can play avi, mpeg files etc AND vdr recordings. So I have a link from my softplay media directory to /video Then you can use the playlist functions in softplay to play the episodes as you need. This may well work with xine, mplayer plugin etc etc: I don't know because I have not tried it. (The one problem with this is that softplay often tries to play resume.vdr, info.vdr etc recordings. It does not matter much, you just get a message saying "cannot play resume.vdr etc. One day I might hack up a list of "exclude this filename" into softplay) > I have a lot of children's programs stored, for example 52 episodes of > "Peppa Pig". :) The episodes are only 5 minutes each, so now I have to > interrupt my serious work (IRC :) ) every 5 minutes to start a new > episode, to keep the kids quiet for a while. :) This was almost the exact problem I had (although not for "Peppa".) Hopefully Daddy Pig can use this as a solution. :) > The recordings-listing doesn't have many buttons assigned for > directories, only "Open".. There could be a command to playback entire > directory, perhaps with some "bookmark" feature so it starts from the > episode that was previously played back. > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] disabledoubleepgentrys and vdr 1.6
Hello, Does anyone know if there is a version of the disableDoubleEpgEntrys patch for vdr 1.6? If not, is there another solution? Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rotor patches
On Wed, 2008-04-16 at 16:23 -0700, Timothy D. Lenz wrote: > Strange, that patch fails on all hunks. looking to patch by hand, it's not > even close. The vdr-1.5.5-rotor.diff patch applies. Where does one find these patches? > > - Original Message - > From: "lucian orasanu" <[EMAIL PROTECTED]> > To: > Sent: Tuesday, April 15, 2008 11:45 PM > Subject: [vdr] Rotor patches > > > > Hy. > > > > No, just Rotor-0.1.4-vdr1.5.10.diff. > > > > Lucian. > > > > > > > > > > Be a better friend, newshound, and > > know-it-all with Yahoo! Mobile. Try it now. > http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ > > > > ___ > > vdr mailing list > > vdr@linuxtv.org > > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput: viewing 16:9 content on 4:3 output device
On Wed, 2008-04-09 at 13:43 +0300, Petri Helin wrote: > On Wed, Apr 9, 2008 at 9:43 AM, Jouni Karvo <[EMAIL PROTECTED]> wrote: > > > Nevertheless, although probably most techies feel the crop mode is not > > interesting, perhaps you'll be able to find one that is willing to > > implement it - or perhaps you can DIY and share the code. > > > > I think the idea of cropping material from aspect ratios 16:9 or > 2.39:1 to 4:3 is not worth putting attention, because it will often > result in quite awkward image. When done properly with technique > called pan&scan (http://en.wikipedia.org/wiki/Pan_and_scan) where the > cropped selection can reside at any part of the original image, the > result is bearable. But think about a movie shot and broadcasted in > 2.39 and crudely cropped so that the 4:3 part in the middle is > shown... You will see half heads, people talking to people not > included in the picture and so on. Or think about a football match in > 16:9 cropped to 4:3... with the ball in the portion left out. However, often things just work out: the camera operators are sometimes directed to shoot the full 16:9 frame but keep the action in a 4:3 frame. This does happen, and IMHO makes for shots that seem too wide on a 16:9 screen. Production companies do this to maximise the market potential for their material. To use the football case: the international feeds still need to deliver 4:3 images. So the host broadcaster who wants both a 16:9 version and a 4:3 version can either employ twice as many camera operators and have twice as many cameras etc etc OR shoot 16:9 but keep the action in the 4:3 frame. Then there is 14:9 material. This is shown on a 4:3 image with smaller black bars, or cropped less (than 16:9) and shown full screen on a 4:3. (I myself prefer the black bars on top and on bottom and view all 16:9 programmes that way on my 4:3 set) (For movies the transfer to video can take more time: there pan&scan is used, but so are other techniques including letterbox, image distortion etc. It is particularly noticeable at the end of a movie with credits that use the whole 16:9 width) > > -Petri > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] Use pkg-config to find freetype/fontconfig flags
On Sat, 2008-03-08 at 19:12 +0100, Clemens Kirchgatterer wrote: > Klaus Schmidinger <[EMAIL PROTECTED]> wrote: > > > I still believe, though, that freetype2's include files are broken. > > A simple '#include ' should be enough. If their header > > file(s) would behave like the rest, we wouldn't have this discussion. > > no. pkg-config and freetype-config have absolutly nothing to do with > that. i think nearly every "obtional" library has one of these to > provide a way to find them at compile and link time. please see the > output of: ls /usr/bin/*-config I don't know make's syntax, but why not do something like: in shell: $(freetype-config 2>/dev/null --cflags || echo /usr/include/freetype3) As I said I don't know make's config but it might be: $(shell freetype-config 2>/dev/null --cflags || echo /usr/include/freetype3) > clemens > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [patch] channels with same pids
On Sun, 2008-02-24 at 10:34 +0100, Klaus Schmidinger wrote: > On 02/24/08 07:20, ua0lnj wrote: > > Hi > > 1. cChannel::PluginParam() need for iptv plugin. > > sorry, i was attached bad version for native vdr. > > See attach for this message. > > > > 2. You right of cause, the triplet SID/NID/TID is supposed to be unique > > within one satellite, but in really we have incorrect pid tables on many > > satellites, and in local iptv networks. Example, see > > http://www.lyngsat.com/eam2.html, some channels have equal pids: > > 11650V, 11190H, and 11044H too. > > This is fault of sat providers, but we have it as is. And be a fine, if > > vdr can works correct with such channels, without editing channel.conf > > manually. > > Have you ever tried complaining to those providers, telling them about > their non-standard behavior? > > If we always just work around the provider's faults, we're never going > to get standard behavior... Satellites are a multi-million dollar business. Do we really think that a few VDR users complaining that they cannot use their particular choice of receiver (VDR) is going to make a difference? > Klaus > > > On Sat, 23/02/2008 18:03 +0100, Klaus Schmidinger wrote: > >> On 02/22/08 04:29, ua0lnj wrote: > >>> Hi. > >>> Some satellites have many channels with same sid, nid, tid on different > >>> transponders. This is incorrect pid table, and vdr works with it not > >>> good, need scan channels and change rid manually, but if you select > >>> "transponder update" all you settings will be rewrite and channels > >>> deleted as duplicate. > >>> I have this trouble on ABS1 75.0 E and Express AM2 80.0 E, and I have > >>> very many channels with same pids on my iptv stream. > >>> After this patch, vdr parsing duplicate pids, and if transponders is > >>> not equal, channel not deleted, but rid wil be increased. If pids and > >>> transponders are equal, channel will be deleted as duplicate. > >>> Patch was made for vdr-1.5.12, but works with 1.5.15 too. > >>> Attached 3 patches, for native vdr and vdr + iptv plugin patched and for > >>> native reelchannelscan-0.4.1 plugin (include patch for 1.5.xx). > >> First of all, there is no cChannel::PluginParam() in plain vanilla VDR > >> 1.5.15. > >> > >> Secondly, as far as I understand this, the triplet SID/NID/TID is supposed > >> to be unique within one satellite. > >> Can you point me to a standard document that would indicate otherwise? > >> > >> Klaus > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.5.15
On Mon, 2008-02-18 at 17:57 +0100, Klaus Schmidinger wrote: > On 02/17/08 21:29, Luca Olivetti wrote: > > El Sun, 17 Feb 2008 15:46:42 +0100 > > Klaus Schmidinger <[EMAIL PROTECTED]> escribió: > > > >> Note that you may need to switch back to an older version of your > >> channels.conf file if you have already used version 1.5.14, because > >> it introduced new parameters. > > > > In case there's no older version of channels.conf, is there some simple > > sed/awk/perl script to remove the extra fields, or is it not strictly > > necessary? > > Is it just a 's/M2O0S0//' when you only have dvb-s channels? > > Should be pretty much it. Why not make 1.6.0 ignore this field so it can just work for people who upgrade/downgrade? > Klaus > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
My vote is yes. Release early, Release Often. Perhaps teletext subtitling is missing, however it was missing from 1.4 and so why not release. (Is there a teletext patch for those users who must have this functionality?. Or even better, can a teletext plugin be written) Also, reading between the lines it would seem that you will release a new developer version straight away anyway. So what is there to loose? I don't think you (Klaus) are going to slow down development on developer versions any time soon. On Sun, 2008-02-03 at 11:17 +0100, Klaus Schmidinger wrote: > There has been some controversy about my recent decision to > move forward and require the "multiproto" driver for VDR in > the developer version. It is also currently rather unclear > whether the current PES recording format can be kept to handle > HDTV, or whether it would make sense (or even be feasible) > to switch to TS (as suggested by the people from RMM). > > In order to take the edge of this, I was wondering if it would > make sense to revoke the switch to the "multiproto" driver and > go straight towards a stable version 1.6.0 with what is now in > version 1.5.14. This should satisfy all those who are eagerly awaiting > a new stable version, without forcing them to make the driver switch > now. > > If we decide to go that way, I would release a version 1.5.15 with > what could become the new stable, wait until like the end of the month > to see whether it still needs some minor fixes, and call it 1.6.0 then. > I know there are still some patches out there that some would expect > to go into the next stable version, but I actually want to prepare VDR > for HDTV before looking into these patches. > > So, here's the straw poll: > >Should there be a stable version 1.6.0 now, based on what's in >version 1.5.14, but without DVB-S2 or even H.264 support? > > Yes or No? > > Klaus > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
