Re: [vdr] xmltv2vdr.pl
On 9 March 2012 15:54, Dominic Evans wrote: > I don't know if anyone else still uses the xmltv2vdr.pl perl script > for piping XMLTV data into VDR's epg, but I've been keeping a version > of it updated with some additional function here: > > https://github.com/oldmanuk/xmltv2vdr > > These are the changes since the last version (1.0.9) was released on > the mailing list > > - Add support for XMLTV episode-num. Currently gets added as EPG entry > 'sub-title', if no existing subtitle has been found, in the form > sXXeXX (e.g., Bones~s01e01). > - Change default SVDRP port number to 6419. > - Better support for ATSC/PVRINPUT EPG sources. > - Allow multiple channels to have the same XMLTV channel id, useful for > multi input (e.g., DVB-T, DVB-S) systems where you want to feed VDR > the same info. Previously only a 1:1 mapping was permitted. > > I've also received a pull request from someone who rewrote the whole > script to be a lot more readable and to use full XML parsing (rather > than just line-by-line scraping), but I still need to investigate what > the performance penalty is before accepting that in. Yep! I still use it on a daily basis. :-) Will grab new version over the weekend and give it a whirl. Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xmltv2vdr.pl
On 10 March 2012 09:52, brian wrote: > I still use it, everyday. Mostly because it works so I never saw the need to > chnage to the plugin. Ditto! I had a quick play with the plugin a few months back but never managed to get it to work. I currently have a simple cron job that runs early every day that grabs XML listings from Radio Times and then feeds in to vdr with the xmltv2vdr.pl script. Works a treat! Could be time to reinvestigate the plugin, though. Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe OSD transparency
On 12 August 2012 21:12, Scott Waye wrote: > > Upgraded a bunch of stuff (vdr -> 1.7.28, xinelib -> latest from hg) and > I've lost my transparent OSD (ST:TNG) when using vdr-sxfe. What is it that > controls the transparency of the OSD? Does vdr overlay the OSD onto the > video, or is it sent as a separate layer somehow to the output device and > the output device decides how to merge? I would like to know if I need to > concentrate on vdr config or xine config. I had a similar problem a little while back: I upgraded (I think...) xineliboutput, libxine, ffmpeg and vdr on my frontend box. I _think_ I had vdr-1.7.26 on the server and 1.7.27 on the frontend. Bizarrely, I had lost all transparency on skinsoppalusikka that I usually use but did have transparency with the ST:TNG skin! I spent quite a while trying to work out why because both skins used the same alpha values for the backgrounds, etc.! A couple of weeks back, I bit the bullet and hacked about some of my plugins so that I could compile them with vdr-1.7.29, and I also upgraded ffmpeg, libxine, xineliboutput to the latest CVS, mercurial, SVN, or whatever, and transparency is back! I never did work out what caused it (I suspect different versions of "something" on the server and the front end) but updating various things to the same versions on both seemed to do the trick. Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-xine breakage with Freeview HD
On 7 September 2012 02:28, Darren Salt wrote: > I've noticed audio brokenness with vdr-xine 0.9.4 and (at least) the BBC > channels on Freeview HD. Recordings are fine and are played back without > problem if played directly rather than via vdr. > > There's a sample recording (tarball, with b0rked filename due to the lack of > decoding in stock Debian vdr) at http://tartarus.org/ds/bbchdvdr.tar (file > size is 84172800 bytes; still being uploaded when I sent this). I've never really had that much success with HD channels on Freeview, although it seemed more stable with live TV rather than HD recordings. For me (I think! I tend not to bother trying most of the time!), I get both video and audio but after a while the video will freeze but the audio carries on. If I play back an HD recording, this will probably happen after a couple of minutes or so. Due to this, I didn't really both trying again until recently! I gave it another go when the olympics was on and BBC 1 HD played live fairly happily for hours on end. Every now and then the video would freeze but this could be fixed by switching to another channel and back (audio carries on quite happily otherwise!). The time between video freezes seems to be random so could be caused by an error in the stream that cannot be corrected, or something like that?! Every now and then, I update xineliboutput + libxine + ffmpeg to the latest cvs / hg / git source (and I can never remember which is which version control system!). I'm currently on all of those from near the end of July. I keep hoping it will suddenly "just work" but it hasn't really changed much in this respect that I can see. Also with vdr-1.7.29. For SD recordings it is much more stable although skipping multiple times in quick succession usually locks it up and requires vdr-sxfe to be restarted! It's a bit of a pain but I've (nearly?!) learned to live with that! Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR on Raspberry Pi
On 30 September 2012 19:50, Dave wrote: > I'm using VOMP on Raspberry Pi as my main output device. The OSD is still > work-in-progress but all the VOMP features are working and TV quality is > fine (though I haven't used HD yet). Oooo...interesting. I'm currently using an Ion ITX board for my front-end using xineliboutput. It works but the frontend needs restarting many times a day which gets a tad annoying! I@m very tempted to sort something else out and at 25-quid or so, a Raspberry Pi sounds like it could be my next thing to try! I've got a couple of MediaMVPs that I use occasionally with VOMP but I didn't realise much was still being done on the development of it. I can't find much on t'internet about VOMP on the Pi, though, apart form the git repository and the forum. Does VOMP run the same on the Pi as on the MediaMVPs, i.e. totally separate frontend with it's own remote? What remote receivers are supported? Definitely looks like something to follow, though... Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR on Raspberry Pi
On 1 October 2012 08:21, Dave wrote: > On 30/09/12 23:04, Laurence Abbott wrote: >> >> On 30 September 2012 19:50, Dave wrote: >>> >>> I'm using VOMP on Raspberry Pi as my main output device. The OSD is still >>> work-in-progress but all the VOMP features are working and TV quality is >>> fine (though I haven't used HD yet). >> >> >> Oooo...interesting. I'm currently using an Ion ITX board for my >> front-end using xineliboutput. It works but the frontend needs >> restarting many times a day which gets a tad annoying! I@m very >> tempted to sort something else out and at 25-quid or so, a Raspberry >> Pi sounds like it could be my next thing to try! > > You also need to buy a licence code to enable the GPU decoder for MPEG-2 at > £2.40 (MPEG-4 is already enabled). Slightly annoying but not a deal-breaker. >> I've got a couple of MediaMVPs that I use occasionally with VOMP but I >> didn't realise much was still being done on the development of it. I >> can't find much on t'internet about VOMP on the Pi, though, apart form >> the git repository and the forum. >> >> Does VOMP run the same on the Pi as on the MediaMVPs, i.e. totally >> separate frontend with it's own remote? What remote receivers are >> supported? > > It currently uses CEC, ie passthrough from the TV over HDMI, and so uses the > TV's remote. Of course not all TV remotes are the same, and different TVs > have different ideas about which buttons to pass through... Oooo...not come across CEC before: will have to look into it... I see that OSD is a work-in-progress but presumably it will be its own OSD (like the MediaMVPs) rather than "forwarding" the standard vdr OSD. The thing I always missed from the MediaMVPs was the inability to interact with plugins like epgsearch. At the price of these things, I suspect I'll be getting one to test this anyway! And I suspect lots of people who bought them initially have discovered that they are not quite the computing experience they expected and will be moving them on cheaply...! ;-) Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Converting videos into vdr TS format
Hi, Has anyone worked out a simple way of converting, e.g. part of a DVD or any miscellaneous video into an MPEG-TS that vdr is happy to play? I had a bit of a play with ffmpeg and mencooder but never managed to generate something that vdr would play! Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Converting videos into vdr TS format
On 30 May 2013 19:22, Stephan Loescher wrote: > Some months ago I had success with ffmpeg: > > ffmpeg -i input.mp4 -f mpegts -vcodec mpeg2video -aspect 16:9 -sameq -s 4cif > -acodec mp2 -ar 48000 -ab 192k 1.ts Works a treat, thanks! :-) I did initially wonder about creating the index file but vdr now creates one if it's missing, rather than needing an updated version of genindex. Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr and raspberry pi
I've been using vompclient on a Raspberry Pi as my only front-end for a few months now. Works well but sadly lacks editing capabilities. Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr 1.7 -> 2.1 upgrade tips (FHS)
Hi, I've been using vdr for a number of years now, mainly keeping abreast of the latest development versions. However, I "missed" the upgrades that incorporated FHS standards (busy with other stuff, etc.). I'm currently running vdr-1.7.29 (I think the last version before the changes) but think I should take the plunge and upgrade. I did do some very quick tests with vdr-2.0.3 but could never work out which config files to move where! Is there any simple way of working out which files go in CONFDIR and what goes in CACHEDIR, for example? Or is the easiest method to backup all of my current config files, build with my set of plugins, fire it up, and then see what new config files get created where and copy over the original set? Or I could just grep the source for config and cache. Others must have made this transition so any tips would be greatly received. Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7 -> 2.1 upgrade tips (FHS)
On 4 November 2013 10:22, Halim Sahin wrote: > Hi, > Have a look to Make.config.template if you want to use vdr 2.x like 1.6 > running in one single dir! Yeah, I saw that sort of thing is doable but it's probably worth my while doing things "properly" to fit in with the current way of thinking. Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7 -> 2.1 upgrade tips (FHS)
Having had a quick look, I ended up defining both LCLBLD=1 and ONEDIR=1 and it all built fine (with a few edits to add cVideoDirectory:: to the relevant bits in several plugins...) and I was up and running with version 2.1.2. I may or may not look into the FHS bits at a later date... Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New tool to load VDR with XMLTV Data
On 24 December 2013 21:59, Adam Flott wrote: > I tried it and got frustrated with the syntax and configuring the channels. > Plus it was fun to learn SVDRP (for future itch scratching) I've never managed to get the plugin to work when I've tried it but I've been using xmtv with that xml2vdr Perl script for quite a few years now. How does your new script improve on the old one? I should probably have a look myself, really... Laz ___ 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!
Thanks, thanks, and more thanks! It's been my main source of TV for at least 11 if not 12 years! Couldn't watch without it! :-) Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR User Counter: now with map!
On 1 March 2015 at 15:53, Klaus Schmidinger wrote: > I have refurbished the VDR User Counter (see http://www.tvdr.de/counter.htm) > and added a map of all registered VDR users. You can now also enter the > number > of VDRs you are using (default is '1' for existing entries). > > I'm asking all registered users to please access their entries and verify > the > "Location" (and adjust it as desired). By default the location is determined > from > the IP number and may be way off. Please make sure you press the "Change" > button in the editing dialog to verify your location, even if you don't > adjust it! > > Registered users have received an email upon registration, containing a link > to the page where they can edit their entry. If that link got lost, a new > one can be requested via the "Forgot your password?" function (see > http://www.tvdr.de/cgi-bin/vdr-counter.pl?action=forgot). > > I would appreciate if many VDR users update their counter entries, or newly > register their VDRs. As a word of warning, it appears that gmail marks the autoresponse messages as spam! I eventually thought to look in my spam folder so I could register properly! :-) Cheers, Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR User Counter: now with map!
On 3 March 2015 at 08:20, Klaus Schmidinger wrote: > On 03.03.2015 09:15, Laurence Abbott wrote: >> As a word of warning, it appears that gmail marks the autoresponse >> messages as spam! >> >> I eventually thought to look in my spam folder so I could register >> properly! > > Thanks. That's why I added "Please also check your SPAM folder, because > sometimes > automated emails are wrongfully considered SPAM by some filters" to the > message > that appears right after the verification mail has been sent. > > Any ideas how Gmail determines that this is an autoresponse message? Nothing particularly helpful on the gmail help page it links me to (just very general stuff). The (possibly?) relevant bits from the header could be: Received-SPF: none (google.com: k...@tvdr.de does not designate permitted sender hosts) client-ip=188.40.50.18; Authentication-Results: mx.google.com; spf=none (google.com: k...@tvdr.de does not designate permitted sender hosts) smtp.mail=k...@tvdr.de Sending address now added to my contacts so (hopefully!) that will help convince gmail it's not spam! :-) Laz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 20 Years of VDR
Ditto! I've been using vdr continually for at least 16 years, and tinkered with it at times in the couple of years before that. Over this time, I think I've gone through about 5 different types of frontend as things have progressed over the years. I was getting a little worried that Klaus had given it up when there hadn't been any new releases in ages. Then again, I haven't felt the need to upgrade for ages (since 2014, going by file dates!) because it "just works". Talking of which, maybe it's time to build a new version... :-) Cheers, Laz On Fri, 28 Feb 2020 at 00:44, Josce wrote: > > >Back then a VDR was something special, while today it's just an ordinary > device. > > Well, I am sitting here installing vdr yet again on a new pc :) > > It might be old, it might be this and that, but to me it is still the best > there is. Simple, efficient and works all the > time. I have been using it since the first version, and I will probably use > it for as long as it can be used. > > So again, thank you Klaus! > > Josce > > > ___ > vdr mailing list > vdr@linuxtv.org > https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr