Re: [vdr] Shutting a system down.
Paul Menzel wrote: Am Freitag, den 25.12.2009, 13:38 -0800 schrieb VDR User: […] However, in my case since VDR is my main tv/media source, it would be annoying to have to boot the computer every time someone wanted to watch/listen to something, therefore the box stays on 24/7. Thus, never having use for shutting down. Well, I guess energy prices are still too low. Really stupid comment, maybe you also believe that food is too cheap if people can afford to eat. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Channel to Adapter mapping?
VDR User wrote: On Wed, Dec 16, 2009 at 3:03 PM, Calypso Cricket wrote: Hi All, Where does VDR maintain the adapter to channel mapping? Thanks. Unfortunately it doesn't support this feature. I wish it did however, believe me! Actually it does, sort of. If the conditional access field in channels.conf contains value 0x1-0xF the it is interpreted as card number. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
Artem Makhutov wrote: Hi, On Wed, Nov 18, 2009 at 10:40:38AM +0200, Lauri Tischler wrote: Luca Olivetti wrote: The asus P5N7A-VM motherboard seems a good candidate, is its integrated 9300 graphics powerful enough for good deinterlacing? P5N7A does not have enough slots :( Any comments about M4N78 PRO ? I have an Asus M4N78 Pro. It works pretty nice and stable. Also 1080p and audio over HDMI ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
Luca Olivetti wrote: The asus P5N7A-VM motherboard seems a good candidate, is its integrated 9300 graphics powerful enough for good deinterlacing? P5N7A does not have enough slots :( Any comments about M4N78 PRO ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Gavin Hamill wrote: On Sat, 2009-09-05 at 08:18 -0700, VDR User wrote: On Sat, Sep 5, 2009 at 6:24 AM, Lauri Tischler wrote: Somewhat related question is, is there some solution to have HD-VDR without X, other than eHD ? Not that I'm aware of but by no means have I researched that question in depth. ;) All this hullaballoo with vdpau/X/xine etc.. is somehow stupid if all you want is HD-STB. I'm not sure why you think vdpau is stupid if you want an HD stb. Using vdpau gives you the ability to have HD on systems that normally wouldn't have a chance at all, and it provides this at a very lost cost. The cheapest I've paid so far is $20 ($30-$10 MIR) for an 8400GS pci-e. So for a mere $30 on average, your old system that couldn't handle HD now can. Stupid is the last thing I would describe that as. Hm, I'd be happy to pay $150-200 for a hardware output card, similar to the good old FF technotrend cards, if it could save me hours of messing around with SVN bleeding edge code and trying to run exotic deinterlace filters :) I think that's what Lauri is getting at - the statement 'vdpau is stupid' is perhaps a little inflammatory, but there must be more time-efficient ways (other than the eHD card which is now hard to obtain) I should have said 'needing X to run HD-VDR is stupid".. I sure wish there was a NEXUS-FF-S2 card with HDMI 1080p output, or similar, I dont like X and GUIs in general. In old Byte Magazine guy named Steve Ciarcia said "the best compiler is solder", still true. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Klaus Schmidinger wrote: Maybe it's ok if I use this opportunity to ask if somebody could point me to a "complete idiot's guide to installing the eHD software" (meaning the necessary software that goes into the eHD itself, as well as the latest version of their plugin). I know, I could search for this myself, but I'm sure there's somebody out there who knows exactly where to find these ;-) Maybe I'll find the time to actually bring up my eHD and adapt the plugin to the latest developer version of VDR... Somewhat related question is, is there some solution to have HD-VDR without X, other than eHD ? All this hullaballoo with vdpau/X/xine etc.. is somehow stupid if all you want is HD-STB. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
VDR User wrote: On Sun, Aug 23, 2009 at 11:24 PM, Lauri Tischler wrote: Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. I really do not understand the rage about HD OSD and/or skins. VDR is meant for watching TV-programs, like sports, movies, documents, and porno, not OSD. Many of us are using real tv's and not computer monitors for viewing. And of course many are now doing hdtv. It's likely you're not a user of either or both of those. Certainly an HD OSD isn't required to watch tv but if you knew how ass ugly it was to see the crappy low-res 8bit OSD on a big high definition tv, you'd understand. Consider the HD OSD like having real nice woodgrain trim in your car. I really wouldnt care less, if the OSD on my Toshiba 42" FullHD looks ass ugly, so be it, just about anything, while developing VDR, is more important then HD OSD. "Real nice woodgrain trim in cars" was used in some 1950's stationwagons. :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
Seppo Ingalsuo wrote: On Sun, 2009-08-23 at 09:05 -0700, VDR User wrote: Did you know that Klaus is giving VDR a new 24bit OSD? High resolution/high color will soon be in vanilla VDR, no expensive eHD card or otherwise required. ;) That's nice but my main problem with vdr is having two televisions + one computer that can be used for TV watching too. HD UI is not the main driver for me. There really should be a proper server/client(s) architecture with vdr. Possible HD UI development for vdr to be useful should be developed to operate as IP streaming client. I really do not understand the rage about HD OSD and/or skins. VDR is meant for watching TV-programs, like sports, movies, documents, and porno, not OSD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.8 xine-9.2 compile error
VDR User wrote: > VDR-1.7.8 needs xine-0.9.3. Well, unfortunately xine-0.9.3 does not exist, yet :) vdr-xineliboutput does not compile either. Maybe after the holydayseason is over, september-october... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
Lauri Tischler wrote: > Carsten Koch wrote: > >> I did a >>cd /usr/src/v4l-dvb/linux/include/linux >>ln -s /usr/src/linux-2.6.27.21-0.1/include/linux/compiler.h . >> >> that fixed it. > > This has been a problem with all drivers for a long time, > whenever i grab complete new set of drivers, i need to add > compiler.h to them. > It also seems that it does not need to be actually the > same version as current headers, some compiler.h will do, odd.. Actually it's not the problem with drivers, they compile just fine, but VDR will not compile unless the file compiler.h is added to /usr/src/v4l-dvb/linux/include/linux directory Maybe VDR needs some include parameter... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
Carsten Koch wrote: > I did a >cd /usr/src/v4l-dvb/linux/include/linux >ln -s /usr/src/linux-2.6.27.21-0.1/include/linux/compiler.h . > > that fixed it. This has been a problem with all drivers for a long time, whenever i grab complete new set of drivers, i need to add compiler.h to them. It also seems that it does not need to be actually the same version as current headers, some compiler.h will do, odd.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to keep the channel list tidy automatically
Goga777 wrote: >> There used to be a plugin ,'autosort' i believe, which did >> some of those things. > > http://www.vdr-wiki.de/wiki/index.php/Autosort-plugin > http://www.copypointburscheid.de/linux/autosort.htm > > > home page of that plugin doesn't work > > where is it possible to download that plugin for vdr 1.7.7 ? I have no idea, I have vdr-autosort-0.1.3.tgz file, dated 1.4.2007 so I'm sure it needs work, to run with vdr-1.7.7 I can mail it to you if you like, its only 40kb file. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to keep the channel list tidy automatically
Klaus Schmidinger wrote: > On 05/23/09 12:44, Carsten Koch wrote: >> On Sat, 2009-05-23 at 11:47 +0200, Klaus Schmidinger wrote: >> ... >>> You could also remove all unwanted channels from your list and set >>> "DVB/Update channels" to "names and PIDs". Then the EPG scan would >>> only switch through the desired transponders. >> I believe there is room for improvement. >> >> Of course I want *all* channels I can use >> and I want new channels, too, if can use them. >> >> And I do not want to go through my list of channels >> manually all the time, find those that I cannot view >> and delete them manually. >> >> I believe VDR could do a much better (more thorough, >> less error-prone) job at that than I ever could. >> >> Here is a list of improvements that would greatly >> help maintaining a clean and useful channel list: >> >> 1) When VDR does its EPG scan, it switches to all >>channels anyway. Why not test each channel and >>see if it actually delivers data? > > Actually it only tunes to *transponders*, not individual channels. > >>If it does, set a new configuration field to 0. >>If it does not, increment that field by one. >>Lets call this field the "absent" value. >>The reason why we do not get any data does not >>matter. Maybe the channel is temporarily not >>broadcasting. Maybe it has ceased to exist. >>Maybe I do not have a cam for it. Maybe I have >>a suitable cam, but no subscription. >> >> 2) When zapping, automatically skip channels that >>have an "absent" value of > 5 (maybe that value >>should be configurable). >> >> 3) Do not display channels anywhere that have an >>"absent" value of > 5 (maybe that value >>should be configurable. If you set it to zero, >>all useless channels will show up again). >> >> 4) A "cleanup" run could remove all channels >>that have an absent value that exceeds a >>certain number (maybe 50). >> >> 5) You could define additional criteria that >>would increment the "absent" value during >>an EPG scan. >>For example: >>5a) the channel does not broadcast one of the >>audio languages that I have configured as >>the set of languages that I can understand. >>5b) the channel broadcasts video, but with less >>than 1 Mbit/s. >>(That would get rid of all those advertising >> channels which only broadcast slide shows). > > Sounds like a perfect task for a plugin - with tons of > config parameters and endless threads about what makes sense > and what doesn't ;-) (SCNR). There used to be a plugin ,'autosort' i believe, which did some of those things. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Timeouts and lost locks
Tony Houghton wrote: > It would also be nice if > VDR had a logfile to itself instead of syslog. Fix your syslogd and RTFM :) -l level, --log=level Set logging to level. 0 = no logging, 1 = errors only, 2 = errors and info, 3 = errors, info and debug. The default logging level is 3. If logging should be done to LOG_LOCALn instead of LOG_USER, add '.n' to LEVEL, as in 3.7 (n=0..7). ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
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. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best practices for running vdr-xine
Seppo Ingalsuo wrote: > Off-topic question: > > Are there any (free) EDID binary data editors available that are able to > edit the CEA block > http://en.wikipedia.org/wiki/EDID#Extension_Block_Details ? > > I'd like to disable 1080i modes from my EDID via CustomEDID option to > avoid Nvidia drivers to use them as back-end resolution for scaling all > modes on my HD-Ready LCD TV. 720p modes give best visual result but > latest Nvidia driver's artificial intelligence decides that 1080i is > best for me :^( Some info about EDID www.quantumdata.com/pdf/EDID.pps Phoenix EDID Designer 1.3 http://www.tucows.com/preview/329441#MoreInfo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best practices for running vdr-xine
VDR User wrote: > On Tue, Apr 28, 2009 at 1:20 PM, Simon Baxter wrote: >> I've recently taken a different approach altogether. >> >> I use MyMediaSystem (mms) as the "front end" to my pvr for dvd, movies, >> pictures, music, weather, radio etc etc and TV. When you select TV, it >> launches vdr-xine. >> >> I wanted a high quality graphical (open-gl) look - and the ability to play >> music playlists while cycling through my photo collection. >> >> VDR, vdr-xine and mms seem to work very well together too > > Interesting. Do you have a howto for this? I'm sure I know some guys > who would like to try it as an alternative to xbmc+VDR. Has anybody made some kind of pros and cons analysis between vdr-xine and xineliboutput. Which is better or are they just different ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] channelscan plugin
Any working/compiling (with VDR 1.7.5) channelscan plugin anywhere ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-skinsoppalusikka-1.6.4 & vdr-rssreader-1.6.4
Rolf Ahrenberg wrote: > Hi, > > new releases of Skinsoppalusikka and RSSReader plugins are now > available. One might humbly assume that these for VDR 1.6.x only ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and PrimaryDVB
Pertti Kosunen wrote: > Lauri Tischler wrote: >> I wonder if it is possible to somehow make xinelibout automagically >> detect correct PrimaryDVB, now, every time I plug/unplug usb-devices >> I need to manually edit setup.conf for correct PrimaryDVB. > > vdr --help > >-p--primary Force xineliboutput to be primary device when > there are active frontend(s) > > Give -p option to xineliboutput-plugin. Aargh... Thank You, I did not think of looking for plugin options in vdr itself, these is no mention of -p option in plugin itself. I did RTFM (README) of xineliboutput. I think that 'vdr -help' is not the correct place for any plugin options. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput and PrimaryDVB
I wonder if it is possible to somehow make xinelibout automagically detect correct PrimaryDVB, now, every time I plug/unplug usb-devices I need to manually edit setup.conf for correct PrimaryDVB. ie, I have - dev 1 DVB-S FF PCI - dev 2 DVB-T PCI - dev 3 DVB-T USB (occasionaly) this setup requires PrimaryDVB = 4 to work If I now remove USB-device and restart VDR, PrimaryDVB reverts to 1 and I need to edit setup for 3. Cheers, Happy Easter... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 & xineliboutput
Petri Helin wrote: > Artem Makhutov wrote: >> Hi, >> >> On Sat, Mar 07, 2009 at 12:22:11AM +0200, Lauri Tischler wrote: >>> Artem Makhutov wrote: >>> >>>> Is some body working on getting xineliboutput to work vdr-1.7.4? >>> Latest CVS works. >> I tried the lastest CVS, but it does not work for me. >> Only the OSD is working. >> >> I am just getting a lot of this error messages: >> >> ar...@gandalf ~ $ vdr-sxfe --video=xv xvdr:tcp://192.168.10.2 >> vdr-sxfe 1.0.4 (build with xine-lib 1.1.16, using xine-lib 1.1.16) vdr-sxfe 1.0.4 ?? Shouldn't cvs-version say 1.0.90-cvs I dont know, I run it just locally and no HD. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 & xineliboutput
Artem Makhutov wrote: > Is some body working on getting xineliboutput to work vdr-1.7.4? Latest CVS works. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe from background script
Petri hintukainen wrote:
> Pertti Kosunen wrote:
>> Lauri Tischler wrote:
>>> - trying to play dvd (Starship Troopers) does not show
>>>correct subtitles, wanted language is defined in VDR.
>> Maybe this helps also for dvd?:
>> http://www.kosunen.fi/vdr/matroska-subtitles.diff
>
> Does it work if user selects another language from DVD menus ?
DVD-menus dont show properly, only the frame shows, no text,
so cant select language. :(
btw, several dvd's seem to use depreciated languagecode
for hebrew (iw) instead of (he).
Using both codes in tools/iso639.h at least removes the error from log.
{"heb","he"},
{"heb","iw"},
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wishlist: Genre
Rolf Ahrenberg wrote: > On Sun, 22 Feb 2009, Lauri Tischler wrote: > >> Adding decoding of content descriptor would be nice. >> It would allow recording of all soaps or football matches or >> whatever without close watching of EPG. >> patching of VDRADMIND might be needed. > > google: vdr-1.6.0-parentalrating-content.diff.gz Well, it installs and compiles in 1.7.4 too, only few line offsets, no rejects or errors. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Wishlist: Genre
Adding decoding of content descriptor would be nice. It would allow recording of all soaps or football matches or whatever without close watching of EPG. patching of VDRADMIND might be needed. Cheers ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe from background script
Petri hintukainen wrote: > pe, 2009-02-20 kello 22:02 +0200, Alex Betis kirjoitti: >> The problem is that when this script is run in background (& at the >> end), the job is shown as "stopped". >> I've tried to run vdr-sxfe itself in background, it opens the window >> and the job stops. >> I know there is a switch that will run it in daemon mode, but that's >> not that good for the script I want to have. >> >> Any ideas what can be wrong or any other ways to run vdr-sxfe from >> background? > > Try --nokbd option for vdr-sxfe. > Reading from console suspends application when it is running at > background. Seems that this just appeared in CVS, is this also available in non-announced 1.0.4 version ? CVS seems to work with vdr-1.7.4, tiny wishlist tho... - add key for subtitle into file remote.conf.example - trying to play dvd (Starship Troopers) does not show correct subtitles, wanted language is defined in VDR. Whats up duck :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XXV and missing epg data
Matti Ropo wrote: > Lauri Tischler wrote: >> Some operators (at least Welho) have rearranged their channel id's, >> so you may need to re-scan your channels or allow VDR to automatically >> update pid's and id's. > > I have allowed vdr to search new channels and transponders so it should > also found new PIDs I think. At least in logfile it says that vdr has > found some new pids. > > I did update first only channel data for channels which had missing epg > data in xxv. This did help, but at the same time TV2 did start miss epg > data. Then I updated whole channel.conf and now TV2 seem to be workin, > but MTV3 is missing some of its program and SUBTV does not have any epd > data in XXV. At the same time data in vdradmin is correct. Strange. Are you sure you dont have duplicate channels, that is same name, ie. 'YLE Teema' but different SID's, this is what happened when Digita rearranged antenna-channels, VDR added second 'YLE Teema' with new SID, I had to manually remove the old YLE Teema. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XXV and missing epg data
Matti Ropo wrote: > Hi > > I am using xxv with my vdr, but lately there has been strange problem. > Couple of channels are missing most of the EPG data. Same data is in the > vdr epg file, but does not appear in xxv. I have tried to look some > erros from log file but haven't found any error messages. > > This was what I did found: > 853 (200) [2009-02-12 20:39:37] EPG: Compare EPG Database with data from > vdr : 55 / 181 for channel 'Sub' - C-0-2-97 > > If I have understood correctly number 55 refers to programs in xxv > database and 181 to programs in vdr epg file. At least most of the > channels these two are the same and one can see all event in epg. Some operators (at least Welho) have rearranged their channel id's, so you may need to re-scan your channels or allow VDR to automatically update pid's and id's. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 & xineliboutput
gimli wrote: > I saw some things going on in the xineliboutput CVS. > Not sure if TS should work or not. Seems to be "Work in Progress", no picture, no sound, OSD works and subtitles appear. Patience ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Darren Salt wrote: > I demand that Lauri Tischler may or may not have written... > >> Reinhard Nissl wrote: >>> after being away 7 month from VDR development I'm pleased to announce >>> release 0.9.0. You can find it on my homepage as usual: > >> Wonder where can I find keybindings of vdr-xine. >> It seems that keypadkeys in general work (keypad arrows, keypad enter) but >> where the hell are colorkeys (red, green, yellow, green) ? >> Started VDR with -P 'xine -r' > > They're wherever the rest of the key bindings are for whichever xine-lib > front end you happen to be using. Sort of assumed that they would be defined in VDR's remote.conf file, where the Lord intended them to be :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.9.0 plugin
Reinhard Nissl wrote: > Hi, > > after being away 7 month from VDR development I'm pleased to > announce release 0.9.0. You can find it on my homepage as usual: Wonder where can I find keybindings of vdr-xine. It seems that keypadkeys in general work (keypad arrows, keypad enter) but where the hell are colorkeys (red, green, yellow, green) ? Started VDR with -P 'xine -r' ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] errors with latest vdr
I'm getting tons of messages like... Jan 21 18:16:47 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (17843 bytes, max size 8192 bytes), data ignored ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (50251 bytes) ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (50251 bytes, max size 8192 bytes), data ignored ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (15743 bytes) ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (15743 bytes, max size 8192 bytes), data ignored ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] get_buf_element: big PES (13100 bytes) ! Jan 21 18:16:48 lassehome vdr: [4716] [input_vdr] vdr_plugin_write: PES too long (13100 bytes, max size 8192 bytes), data ignored ! VDR-1.7.3, xinelibout-1.0.3, drivers from http://linuxtv.org/hg/v4l-dvb/ Whats up duck ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Sascha Vogt wrote: > Hi Lauri, > > Lauri Tischler schrieb: >> Sascha Vogt wrote: >>> as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 >>> with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD >>> videos) >> Couldn't find M2N78Pro, do you mean M3N78PRO ? > Sorry, you're right, meant the M3N78Pro. Any idea if its possible to get also audio via HDMI-connection ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] German translation for "Plugin"
Klaus Schmidinger wrote: > If anybody else thinks translating the word "Plugin" to "Erweiterung" makes > sense, please speak up (or otherwise argue against it). Plse dont change it, now when searching for 'plugin' something sometimes comes up also from german sources, if the term is changed to 'erweiterung' all german sources will become essentially black holes. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] WinTV USB CI-Module and recommended distribution for VDR?
Sascha Vogt wrote: > Hi all, > > as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 > with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD > videos) Couldn't find M2N78Pro, do you mean M3N78PRO ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
Andrew Herron wrote: > Hi, > > This ASUS board would be suitable; > > http://www.asus.com/products.aspx?modelmenu=1&model=2579&l1=3&l2=11&l3=812&l4=0 Too small, not enough pci-slots, minimum three pci-slots needed. Four or five pci-slots would be nice. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR Development
Davide Cavalca wrote: > Finally, I personally fail to see why people switching to MythTV is a > bad thing; VDR is not a religion, I think everyone should use whichever > software he thinks suits best his needs. I'm very happy with VDR and > won't be switching anytime soon. Switching to MythTV is *not* a solution to anything. MythTV is slow huge, kitchen sink where nothing really works. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7 - DVB Linux API problem
Gregoire Favre wrote: > On Wed, Aug 13, 2008 at 04:11:46PM +0300, Lauri Tischler wrote: > >> Vanilla VDR-1.7.0 does not work with v4l-dvb drivers. >> You have two options : >> - download multiproto drivers from http://jusst.de/hg/multiproto >>make and make install >>you may need to patch those drivers, depends on your kernel version > > And if you want an up to date tree, AFAIK there is only one : > > http://liplianindvb.sourceforge.net/cgi-bin/hgwebdir.cgi/liplianindvb/ Aarrgghh.. Yet-Another-Secret-Multiproto-Tree :) Well, this seems to compile with kernels 2.6.24 and 2.6.26 without hacks, patches or file copying. Good Show.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7 - DVB Linux API problem
David Hláčik wrote: > Hello guys, > > I have Fedora 9 with lastest kernel. I have Skystar 2 DVB PCI card rev 2.8. > As this revision is using FlexCopII DVB i needed to recompile v4l dvb > modules. I have downloaded lastest v4l using mercurial. > Now my Skystar 2 works fine with Fedora 9 . I am using Kaffeine , which > works fine. > > My problem is : > I am trying to compile vdr-1.7.0 from source, when i will do "make" i will > get this error : > > [EMAIL PROTECTED] vdr-1.7.0]# make > In file included from audio.c:12: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > In file included from dvbdevice.c:10: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > In file included from dvbosd.c:15: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > In file included from eitscan.c:13: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > font.c:14:10: error: #include expects "FILENAME" or > In file included from vdr.c:45: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > make: *** Deleting file `.dependencies' > g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD > -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE > -DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" > -DLOCDIR=\"./locale\" -I/usr/include/freetype2 > -I/usr/src/v4l-dvb/linux/include audio.c > In file included from audio.c:12: > dvbdevice.h:19:2: error: #error VDR requires Linux DVB driver API version > 3.3! > In file included from audio.c:12: > dvbdevice.h:38: error: 'dvbfe_delsys' does not name a type > make: *** [audio.o] Error 1 > > > As i mentioned before, i had to recompile v4l-dvb modules, location is > /usr/src/v4l-dvb/. > > I have edited Make.config and uncommented : > ### The directory environment: > DVBDIR = /usr/src/v4l-dvb/linux > > Which seems to me correct right? Vanilla VDR-1.7.0 does not work with v4l-dvb drivers. You have two options : - download multiproto drivers from http://jusst.de/hg/multiproto make and make install you may need to patch those drivers, depends on your kernel version - patch vdr-1.7.0 with dvb-api-patch, then it works with standard v4l-dvb drivers. http://www.udo-richter.de/vdr/patches.en.html#dvb-api-wrapper if you need support for dvb-S2 then your only option is multiproto ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: Finnish Yle HD olympics channel..
Seppo Ingalsuo wrote: > Pasi Kärkkäinen wrote: >> Maybe try with recent mplayer (from svn).. and give it >> "-demuxer lavf -lavdopts fast:threads=2 -no-correct-pts" or something >> similar.. >> you can also try with threads=4 etc.. >> > "mplayer -demuxer lavf -lavdopts fast:threads=4 -nocorrect-pts ..." > gives steady but slow motion (roughly 50% speed) video. It is weird that > the load on CPU1 and CPU2 is less than 40% during playback according to > gnome system monitor. Somehow mplayer is not able to max both CPUs close > to 100%. > > With mplayer I noticed that the video is 1080i -- it is silly to > broadcast interlaced crap. That probably explains why vdr xinelibout > choked due to greedy de-interlacer that is pretty power consuming for > 1080i. Other channels such as Arte HD (arte > HD;ZDFvision:11362:hC23M5O0S1:S19.2E:22000:6210:6221=deu,6222=fra:6230:0:11120:1:1011:0) > > work OK. Hi. What card are you using to get DVB-S2 ? CPU power ? Dual-core ? GHz ? I have now AMD X2 4600 and DVB-T YLE HD is a bit jerky, sometimes, playing recordings from YLE HD is totally jerky. Wondering if getting quad-core 2.6GHz would help any. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Multiproto compile fails again
Seppo Ingalsuo wrote: > Hi, > > Lauri Tischler wrote: >> /usr/src/multiproto/v4l/cx25840-core.c:71: error: conflicting type >> qualifiers for 'addr_data' >> /usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h:41: >> error: previous declaration of 'addr_data' was here >> > Please try this found from linux-dvb ml: > > --- > > Now I found a little patch which brought me over this compile error: > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.24-rc4/2.6.24-rc4-mm1/broken-out/fix-jdelvare-i2c-i2c-constify-client-address-data.patch > Thanks, that cured that problem, up pops next problem --- CC [M] /usr/src/multiproto/v4l/ivtv-i2c.o /usr/src/multiproto/v4l/ivtv-i2c.c: In function 'ivtv_i2c_register': /usr/src/multiproto/v4l/ivtv-i2c.c:171: error: 'struct i2c_board_info' has no member named 'driver_name' make[3]: *** [/usr/src/multiproto/v4l/ivtv-i2c.o] Error 1 make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/multiproto/v4l' make: *** [all] Error 2 lassehome:/usr/src/multiproto# --- It seems that multiproto is really too broken to use. Grabbed and installed dvb-api-wrapper and normal v4l-dvb tree now it works, after I get my S2-board things maybe different. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Multiproto compile fails again
Upgraded to Debian Sid and Kernel 2.6.26 Multiproto fails once again. What's up duck ? lassehome:/usr/src/multiproto# make make -C /usr/src/multiproto/v4l make[1]: Entering directory `/usr/src/multiproto/v4l' creating symbolic links... Kernel build directory is /lib/modules/2.6.26-1-686/build make -C /lib/modules/2.6.26-1-686/build SUBDIRS=/usr/src/multiproto/v4l modules make[2]: Entering directory `/usr/src/linux-headers-2.6.26-1-686' CC [M] /usr/src/multiproto/v4l/cx25840-core.o In file included from /usr/src/multiproto/v4l/cx25840-core.c:42: /usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h: In function 'v4l2_i2c_drv_init': /usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h:197: warning: assignment from incompatible pointer type /usr/src/multiproto/v4l/cx25840-core.c: At top level: /usr/src/multiproto/v4l/cx25840-core.c:71: error: conflicting type qualifiers for 'addr_data' /usr/src/multiproto/v4l/../linux/include/media/v4l2-i2c-drv-legacy.h:41: error: previous declaration of 'addr_data' was here make[3]: *** [/usr/src/multiproto/v4l/cx25840-core.o] Error 1 make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.26-1-686' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/multiproto/v4l' make: *** [all] Error 2 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr: no signal
Alex Girchenko wrote: > Lauri, I've found only one manual so far: > http://www.linuxtv.org/vdrwiki/index.php/VDR_User%27s_Manual. In that page section '1.15 Parameters in the Setup menu' contains the information you are looking for, expect it is out-of-date, old. So you are better off by getting the Real Thing, The Source of VDR. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr: no signal
Alex Girchenko wrote: > Lauri, I've found only one manual so far: > http://www.linuxtv.org/vdrwiki/index.php/VDR_User%27s_Manual. It > doesn't contain a word on setup.conf. Also studied the entire wiki, > the man page. Could you please provide a link to the exact manual you > mean? TIA. File MANUAL should be included with your VDR-package, if not then.. Get the VDR-source vdr-1.6.0.tar.bz2 from http://www.cadsoft.de/vdr/download.htm untar to directory Go to generated directory vdr-1.6.0 and read MANUAL Also man-pages vdr.1 and vdr.5 contain usefull info ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr: no signal
Alex Girchenko wrote: > Thanks, you've saved my... night! :) > Is there any official description of all of the options in setup.conf? > Can't find it on the wiki. RTFM, it's all in the MANUAL ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVD subtitles with xineliboutput Media Player
From the README I understand that Mediaplayer uses settings from VDR to select subtitles. It does not seem to work, I have subtitles in VDR set as Finnish but whenever I start a DVD it plays english subtitles, need to select correct subtitles with subtitlekey on remote. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] PLaying video with xineliboutput Media Player
Grabbed testclip of shuttle takeoff, 1920x1080 resolution
VDR log shows
---
Jul 17 17:45:28 vdr3 vdr: [5831] [xine..put]
cPlaylist::EscapeMrl('/video/ksc_062707_sts117_launch_1080i.mpg')
Jul 17 17:45:28 vdr3 vdr: [5831] [xine..put] -->
'/video/ksc_062707_sts117_launch_1080i.mpg'
Jul 17 17:45:28 vdr3 vdr: [5831] [input_vdr] PLAYFILE (Loop: 0, Offset: 0s,
File:
goom:width=720,height=576,fps=25 file:/video/ksc_062707_sts117_launch_1080i.mpg)
---
Does this mean that Media Player rapes the wideo to 720x576 resolution
and then stuffes it to display.
How to force FullHD resolution ?
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Forcing channel to device (Solved)
Lauri Tischler wrote: > I'm trying to force one DVB-T channel on VHF to particular card. > I have three DVB-T cards in system, only card 2 is capable > to tune to VHF frequency, so I want to set this channel > to use allways card 2, I did set CA value in channel.conf to > 2 but still it chooses other cards. I fell into an old off-by-one trick. DVB-cards are numbered starting from 0 CA-positions are numbered starting from 1 Defining card 2 as fixed card requires 3 in channels.conf ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine tvtime parameters explained
Goga777 wrote: > is it good for 1080i/720p channels ? Well, it works, I can't say, yet, how good it is. Local provider, YLE, is broadcasting HD (1280x720) on VHF-channel 8. My VDR shows the picture fine. It is only testpicture, colorbars, eventually they will broadcast Bejing Olympics there. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Forcing channel to device
I'm trying to force one DVB-T channel on VHF to particular card. I have three DVB-T cards in system, only card 2 is capable to tune to VHF frequency, so I want to set this channel to use allways card 2, I did set CA value in channel.conf to 2 but still it chooses other cards. What's up duck ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon & h.264 dvb-s2 channels - some information is missing
Rolf Ahrenberg wrote: > On Sun, 13 Jul 2008, Lauri Tischler wrote: > >> With DVB-T those are ok, but missing are >> Transmission --- >> Modulation --- >> Coderate --- (H) --- (L) >> Guard--- >> and Bandwith is reported as 7Mhz, should be 8Mhz > > The current femon plugin doesn't support multiproto, but for my > knowledge multiproto DVB API should be compatible with old DVB API and > therefore these fields should still be working. Does your channels.conf > contain correct values for these entries? There are differences between 1.4.x and 1.7.0 This is from 1.7.0 YLE TV1;YLE:56200:A0B8C23D23G8I0M64P0T8Y0:T:3:512:650=eng,651=dut:2321:0:17:8438:4097:0 YLE TV2;YLE:56200:A0B8C23D23G8I0M64P0T8Y0:T:3:513:660=fin:2321:0:33:8438:4097:0 MTV3;MTV Oy:65800:A0B8C23D23G8I0M64P0T8Y0:T:3:305:561=fin:817:0:49:8438:8193:0 This is from 1.4.3 YLE TV1;YLE:56200:I0C23D23M64B8T8G8Y0:T:3:512:650=eng,651=dut:2321:0:17:8438:4097:0 YLE TV2;YLE:56200:I0C23D23M64B8T8G8Y0:T:3:513:660=fin:2321:0:33:8438:4097:0 MTV3;MTV Oy:65800:I0C23D23M64B8T8G8Y0:T:3:305:561=fin:817:0:49:8438:8193:0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] femon & h.264 dvb-s2 channels - some information is missing
Goga777 wrote: > Hi > > I'm using the latest femon + vdr 170 + h.264 patch. If I will watch h264 > dvb-s2 channels than some information in femon is > missing - > > Apid - 0 > Spid - 0 > Aspect ratio - reserved > Frame rate - 0.00 Hz > Video format - unknown > Resolution - 0x0 > > Information about audio stream - #0 > bitrate - free (0 kbit/s) > mpeg layer - 0 > sampling frequency - reserved With DVB-T those are ok, but missing are Transmission --- Modulation --- Coderate --- (H) --- (L) Guard--- and Bandwith is reported as 7Mhz, should be 8Mhz ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Femon odd
Goga777 wrote: >> Using Femon 1.6.1 with VDR 1.7.0 and multiproto shows >> odd parameter values, maybe Femon needs a patch ? > > what do you mean - odd ? There's some missing parameters, I wrote about this > on this week Odd, as strange, ie. Bandwidth is reported as 7Mhz when it should be 8Mhz and some parameters are just missing. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Femon odd
Using Femon 1.6.1 with VDR 1.7.0 and multiproto shows odd parameter values, maybe Femon needs a patch ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xine tvtime parameters explained
Trying to google for manual, info or article where all parameters for xine tvtime command are explained, what they do, why, etc. No luck yet, any pointers ?? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
Lauri Tischler wrote: > VDR User wrote: >> On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: >>> What 'FF mod card' are you referring to ? >> There's a hardware hack to allow the full transport stream to be >> passed by the Nexus. By default it doesn't so when there's heavy >> load, a lot of packets are dropped. >> >>> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T >>> cards, in near future I will get some S2 capable card. >>> So, what tree should I use for VDR 1.7.xx ? >> For a stock Nexus-s, you can use any tree. V4L with the vdr api >> wrapper patch, or *multiproto*. > > Hmmm.. compile error > > CC [M] /usr/src/multiproto/v4l/em28xx-audio.o > In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39: > include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a > function) > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in > initializer not of integer type > /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization > for 'index') > make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1 > make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 > make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic' > make[1]: *** [default] Error 2 > make[1]: Leaving directory `/usr/src/multiproto/v4l' > otoh the v4l-dvb tree compiles just fine but multiproto does not. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
VDR User wrote: > On Thu, Jul 10, 2008 at 4:13 AM, Lauri Tischler <[EMAIL PROTECTED]> wrote: >> What 'FF mod card' are you referring to ? > > There's a hardware hack to allow the full transport stream to be > passed by the Nexus. By default it doesn't so when there's heavy > load, a lot of packets are dropped. > >> I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T >> cards, in near future I will get some S2 capable card. >> So, what tree should I use for VDR 1.7.xx ? > > For a stock Nexus-s, you can use any tree. V4L with the vdr api > wrapper patch, or *multiproto*. Hmmm.. compile error CC [M] /usr/src/multiproto/v4l/em28xx-audio.o In file included from /usr/src/multiproto/v4l/em28xx-audio.c:39: include/sound/core.h:281: error: 'SNDRV_CARDS' undeclared here (not in a function) /usr/src/multiproto/v4l/em28xx-audio.c:58: error: array index in initializer not of integer type /usr/src/multiproto/v4l/em28xx-audio.c:58: error: (near initialization for 'index') make[3]: *** [/usr/src/multiproto/v4l/em28xx-audio.o] Error 1 make[2]: *** [_module_/usr/src/multiproto/v4l] Error 2 make[2]: Leaving directory `/usr/src/linux-headers-2.6.24-19-generic' make[1]: *** [default] Error 2 make[1]: Leaving directory `/usr/src/multiproto/v4l' ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] multiproto_plus is ancient
Goga777 wrote: >> Any chance of having an upgrade to multiproto_plus tree ? >> I understand that multiproto_plus is the _only_ tree >> sanctioned by Klaus. > > why ? The regular multiproto can work with vdr 1700 too. If you don't have > FF mod card it's no any sense to use > multiproto_plus Hmmm, would somebody plse explain those requirements for dumb old me. What 'FF mod card' are you referring to ? I have basic Hauppauge NEXUS-S FF card and a pair of Hauppauge NOVA-T cards, in near future I will get some S2 capable card. So, what tree should I use for VDR 1.7.xx ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] multiproto_plus is ancient
Any chance of having an upgrade to multiproto_plus tree ? I understand that multiproto_plus is the _only_ tree sanctioned by Klaus. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput, libextract and Media Player
Loaded latest xineliboutput from cvs, compiled and installed, it did complain about old libextract, says that 0.5.20 is needed, xbuntu has 0.5.18, might this be the reason for not working dvd subtitle menus in Media Player ? I would need to rape Xbuntu distro then and insert libextract from Debian Lenny or Sid. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Finnish DVB-C channel "Nelonen HD" - h264
JJussi wrote: > Maybe 2x "Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz" is not enough.. Umm.. why does the log say 1596 MHz ? model name : Intel(R) Core(TM)2 CPU 6400 @ 2.13GHz stepping: 6 cpu MHz : 1596.000 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Which DVB-S Card to buy in Germany
Matthias Fechner wrote: > Hi, > > I have here an old VDR system running and my DVB-S cards are stopping to > work now (VDR 1.6 and 2xDVB-S cards). > It starts with a lot of distortions and then they stops to record > completely. I have only 0 minute records for my new timers. > > In the log file I have: > Jul 6 14:25:24 video vdr: [10063] ERROR: video data stream broken > Jul 6 14:25:31 video vdr: [19846] ERROR: video data stream broken > Jul 6 14:25:55 video vdr: [10063] ERROR: video data stream broken > Jul 6 14:26:02 video vdr: [19846] ERROR: video data stream broken > Jul 6 14:26:26 video vdr: [10063] ERROR: video data stream broken > > If VDR records on the second DVB card everything is fine. > > I'm quite sure that this a hardware issue. > The cards I habe installed currently are: > 02:07.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) > 02:09.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01) I think your dish has moved or coaxial is broken. btw, the SAA 7146 is the controller on the card, not the type of the card, like Hauppauge NEXUS-S or Technotrend ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Brian wrote: > Lauri Tischler wrote: >> Igor wrote: >> >>> could you explain please how it's possible to connect 3 cards in VDR to 3 >>> LNB's for Hotbird, Sirius, Astra for example >>> with DiSEq-Cswitch >> Simple diagram, using quad-lnb's, input of lnbs are called as >> HB-1, HB-2, HB-3, HB-4 >> SI-1, SI-2, S1-3, SI-4 >> AS-1, AS-2, AS-3, AS-4 >> >>Diseqc-switch 1 >> ++ >> ||--- HB-1 >> Card1 -||--- SI-1 >> ||--- AS-1 >> ||--- free >> ++ >> >>Diseqc-switch 2 >> ++ >> ||--- HB-2 >> Card2 -||--- SI-2 >> ||--- AS-2 >> ||--- free >> ++ >> >>Diseqc-switch 3 >> ++ >> ||--- HB-3 >> Card3 -||--- SI-3 >> ||--- AS-3 >> ||--- free >> ++ >> >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> > Hi, does that really work, or am I misunderstanding a quad-LNB? I though the > the 4 outputs of a quad LNB are > hi/V lo/V hi/H and Lo/H. Or is that a quattro LNB? > So what you are saying is that a quad LNB can supply any of the 4 > "freqs/polarization" down any of its 4 connections? > Any if required the same signal down all 4 connections? Should work, because twin or quad or octal lnbs actually have multiple tuners inside the lnb. Typically twin, quad or octal lnbs are used when there are several settopboxes in the house. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Mattia Rossi wrote: > On Wed, 21 May 2008 16:57:33 +0400 > Igor <[EMAIL PROTECTED]> wrote: > > --- snip - >> could you explain please how it's possible to connect 3 cards in VDR >> to 3 LNB's for Hotbird, Sirius, Astra for example with DiSEq-Cswitch >> > > Hmm, using this switch ? > http://www.spaun.de/?lang=en&modul=products&product=842379&productname=SBK9935NF Good God NO, just a simple 4 input diseqc-switch, one for each card, price something like 10-30€ each ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Igor wrote: > could you explain please how it's possible to connect 3 cards in VDR to 3 > LNB's for Hotbird, Sirius, Astra for example > with DiSEq-Cswitch Simple diagram, using quad-lnb's, input of lnbs are called as HB-1, HB-2, HB-3, HB-4 SI-1, SI-2, S1-3, SI-4 AS-1, AS-2, AS-3, AS-4 Diseqc-switch 1 ++ ||--- HB-1 Card1 -||--- SI-1 ||--- AS-1 ||--- free ++ Diseqc-switch 2 ++ ||--- HB-2 Card2 -||--- SI-2 ||--- AS-2 ||--- free ++ Diseqc-switch 3 ++ ||--- HB-3 Card3 -||--- SI-3 ||--- AS-3 ||--- free ++ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Igor wrote: >> Jean-Claude Repetto wrote: >>> Lauri Tischler a Иcrit : >>>> Jean-Claude Repetto wrote: >>>>> Klaus Schmidinger wrote : >>>>>> Plain vanilly VDR assumes that every DVB-S card can receive all >>>>>> satellites. >>>>>> >>>>>> Klaus >>>>>> >>>>> I hope this will be configurable in VDR 1.8 ! >>>>> The LNB type should also be configurable for each DVB card (I am still >>>>> using a Full-band LNB on my motorized dish). >>>> There used to be 'sourcecaps patch' somewhere, dig it up and >>>> fix it to work with 1.7.0. >>>> >>> Yes, I know, but I think this should be supported by VDR in the standard >>> version. Lots of people have two dishes pointing to different satellites. >> It is supported by using multi-input lnb's and diseqc-switches :) >> > > could you explain please how it's possible to connect 3 cards in VDR to 3 > LNB's for Hotbird, Sirius, Astra for example > with DiSEq-Cswitch - take 3 pc of 4-1 diseqc switch, one for each card - use quad-lnb's on each dish crossconnect all lnb's to all diseqc-switches ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Jean-Claude Repetto wrote: > Lauri Tischler a écrit : >> Jean-Claude Repetto wrote: >>> Klaus Schmidinger wrote : >>>> Plain vanilly VDR assumes that every DVB-S card can receive all satellites. >>>> >>>> Klaus >>>> >>> I hope this will be configurable in VDR 1.8 ! >>> The LNB type should also be configurable for each DVB card (I am still >>> using a Full-band LNB on my motorized dish). >> There used to be 'sourcecaps patch' somewhere, dig it up and >> fix it to work with 1.7.0. >> > > Yes, I know, but I think this should be supported by VDR in the standard > version. Lots of people have two dishes pointing to different satellites. It is supported by using multi-input lnb's and diseqc-switches :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no channel update on vdr 1.7.0
Jean-Claude Repetto wrote: > Klaus Schmidinger wrote : >> Plain vanilly VDR assumes that every DVB-S card can receive all satellites. >> >> Klaus >> > > I hope this will be configurable in VDR 1.8 ! > The LNB type should also be configurable for each DVB card (I am still > using a Full-band LNB on my motorized dish). There used to be 'sourcecaps patch' somewhere, dig it up and fix it to work with 1.7.0. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Lauri Tischler wrote:
> Lauri Tischler wrote:
>> Halim Sahin wrote:
>>> Hi,
>>> On So, Apr 20, 2008 at 11:44:24 +0300, Lauri Tischler wrote:
>>>> Any particular requirement for kernel version,
>>>> i'm running 2.6.18-5-k7 (debian etch)at the moment ?
>>> HMM this kernel is too old!
>>> I think you need min 2.6.22 or better!
>>> I have tested it with 2.6.24 with gcc 4.2 and had no errors.
>> OK, upgrading to debian lenny, that has 2.6.24-5.
>> There will be interesting times ahead ;)
>
> Well, upgraded and compiled.
After updating Debian Lenny, multiproto_plus does not compile
anymore, after 'make clean; make' I get a lot of errors
---
vdr2:~/multiproto_plus# make
make -C /root/multiproto_plus/v4l
make[1]: Entering directory `/root/multiproto_plus/v4l'
creating symbolic links...
Kernel build directory is /lib/modules/2.6.24-1-686/build
make -C /lib/modules/2.6.24-1-686/build
SUBDIRS=/root/multiproto_plus/v4l modules
make[2]: Entering directory `/usr/src/linux-headers-2.6.24-1-686'
CC [M] /root/multiproto_plus/v4l/flexcop-pci.o
In file included from :1:
/root/multiproto_plus/v4l/config-compat.h:787:1: error:
./linux/version.h: Too many levels of symbolic links
In file included from /root/multiproto_plus/v4l/flexcop-common.h:12,
from /root/multiproto_plus/v4l/flexcop-pci.c:10:
/root/multiproto_plus/v4l/compat.h:8:5: warning: "LINUX_VERSION_CODE" is
not defined
/root/multiproto_plus/v4l/compat.h:8:26: warning: "KERNEL_VERSION" is
not defined
/root/multiproto_plus/v4l/compat.h:8:40: error: missing binary operator
before token "("
/root/multiproto_plus/v4l/compat.h:13:5: warning: "LINUX_VERSION_CODE"
is not defined
/root/multiproto_plus/v4l/compat.h:13:27: warning: "KERNEL_VERSION" is
not defined
---
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7 compile error
oleg roitburd wrote: > 2008/4/24 Lauri Tischler <[EMAIL PROTECTED]>: >> dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': >> dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' >> dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' >> dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' >> make: *** [dvbdevice.o] Error 1 > > No Problem. You need vdr patch for newer multiproto > (vdr-1.7.0-multiproto-update.diff) Thanks, now running vdr-1.7 + multiproto_plus. Time to start hunting for FullHD tv-set and some suitable S2 and/or H.264 iron. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.7 compile error
oleg roitburd wrote: > 2008/4/24 Lauri Tischler <[EMAIL PROTECTED]>: > >> vdr2:~/vdr-1.7.0# locate compiler.h >> /usr/src/linux-headers-2.6.24-1-686/include/linux/compiler.h >> /usr/src/linux-headers-2.6.24-1-common/include/linux/compiler.h > > you need to copy compiler.h to your multiproto tree > cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler.h > /root/multiproto_plus/linux/include/linux/ OK, this still remains... dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' make: *** [dvbdevice.o] Error 1 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.7 compile error
g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS4\" -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DCONFDIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" -DLOCDIR=\"./locale\" -I/usr/include/freetype2 -I/root/multiproto_plus/linux/include dvbdevice.c In file included from dvbdevice.c:17: /root/multiproto_plus/linux/include/linux/dvb/video.h:27:28: error: linux/compiler.h: No such file or directory dvbdevice.c: In member function 'bool cDvbTuner::SetFrontend()': dvbdevice.c:271: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:286: error: 'struct dvbfe_info' has no member named 'delivery' dvbdevice.c:307: error: 'struct dvbfe_info' has no member named 'delivery' make: *** [dvbdevice.o] Error 1 file compiler.h exists there vdr2:~/vdr-1.7.0# locate compiler.h /usr/src/linux-headers-2.6.24-1-686/include/linux/compiler.h /usr/src/linux-headers-2.6.24-1-common/include/linux/compiler.h ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Multiproto with 1.4-1.6
Does VDR 1.4 - 1.6 work with multiproto drivers ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Lauri Tischler wrote: > Halim Sahin wrote: >> Hi, >> On So, Apr 20, 2008 at 11:44:24 +0300, Lauri Tischler wrote: >>> Any particular requirement for kernel version, >>> i'm running 2.6.18-5-k7 (debian etch)at the moment ? >> HMM this kernel is too old! >> I think you need min 2.6.22 or better! >> I have tested it with 2.6.24 with gcc 4.2 and had no errors. > > OK, upgrading to debian lenny, that has 2.6.24-5. > There will be interesting times ahead ;) Well, upgraded and compiled. Does command 'hg pull http://jusst.de/hg/multiproto_plus' keep directory multiproto_plus current ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Halim Sahin wrote: > Hi, > On So, Apr 20, 2008 at 11:44:24 +0300, Lauri Tischler wrote: >> Any particular requirement for kernel version, >> i'm running 2.6.18-5-k7 (debian etch)at the moment ? > > HMM this kernel is too old! > I think you need min 2.6.22 or better! > I have tested it with 2.6.24 with gcc 4.2 and had no errors. OK, upgrading to debian lenny, that has 2.6.24-5. There will be interesting times ahead ;) BTW, What are actual benefits for running multiproto, other then having fun at bleeding edge. I dont have S2-cards or odd USB-devices, yet. Just old NEXUS-S and NOVA-T PCI-cards. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Magnus Hörlin wrote: > Lauri Tischler wrote: >> Halim Sahin wrote: >> >>> Hi, >>> install the linux-headers package coresponding to your running kernel. >>> e. G. linux-headers-2.6.24-1-686. >>> you can get the running kernel's version by typing uname -r >>> >>> check out the multiproto drivers by typing >>> hg clone http://just.dde/hg/multiproto_plus. >>> >> What's hg ? Not in debian :( >> >> vdr2:~# hg clone http://just.dde/hg/multiproto_plus >> -bash: hg: command not found >> vdr2:~# apt-get install hg >> Reading package lists... Done >> Building dependency tree... Done >> E: Couldn't find package hg >> > apt-get install mercurial OK, loaded, does not compile. CC [M] /root/multiproto_plus/v4l/videodev.o /root/multiproto_plus/v4l/videodev.c:491: error: unknown field 'dev_attrs' specified in initializer /root/multiproto_plus/v4l/videodev.c:491: warning: initialization from incompatible pointer type /root/multiproto_plus/v4l/videodev.c:492: error: unknown field 'dev_release' specified in initializer /root/multiproto_plus/v4l/videodev.c:492: warning: missing braces around initializer /root/multiproto_plus/v4l/videodev.c:492: warning: (near initialization for 'video_class.subsys') /root/multiproto_plus/v4l/videodev.c:492: warning: initialization from incompatible pointer type make[3]: *** [/root/multiproto_plus/v4l/videodev.o] Error 1 Any particular requirement for kernel version, i'm running 2.6.18-5-k7 (debian etch)at the moment ? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Halim Sahin wrote: > Hi, > install the linux-headers package coresponding to your running kernel. > e. G. linux-headers-2.6.24-1-686. > you can get the running kernel's version by typing uname -r > > check out the multiproto drivers by typing > hg clone http://just.dde/hg/multiproto_plus. What's hg ? Not in debian :( vdr2:~# hg clone http://just.dde/hg/multiproto_plus -bash: hg: command not found vdr2:~# apt-get install hg Reading package lists... Done Building dependency tree... Done E: Couldn't find package hg ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR and "multiproto" - which driver to use?
Klaus Schmidinger wrote: > On 04/12/08 15:42, Manu Abraham wrote: >> If that looks hard, i can push a tree which is a result of the above >> outlined steps. > > Thanks a lot for providing http://jusst.de/hg/multiproto_plus. Any instructions somewhere how to stuff that into stock kernel (debian)? I really don't want to compile the total kernel. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] TNT cards advice
Niko Mikkila wrote: >> A last question, with DVB-S, I'm needing two cards if I want to see two >> different channels because the channels could be on differents >> transponders. But is it true with DVB-T ? In others words: if I want to >> see 3 differents channels, do I really need 3 DVB-T tuners ? > > Basically the same rule applies. You'll need as many tuners as there are > different transponders that you want to receive simultaneously. For > example, if there are four transponders, but all the channels that you > commonly watch are on two of them, you'll only need two tuners (even if > you wathed 10 channels from those two transponders simultaneously). In DVB-T the 'transponders' are usually called 'bouquets', with one DVB-T card you can receive/records all channels on that bouquet. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Event info in log
Klaus Schmidinger wrote: > On 02/19/08 17:20, Lauri Tischler wrote: >> Event info has disappeared. In ver 1.4.x it is >> >> Feb 19 18:00:20 vdr vdr: [28242] channel 2 (YLE TV2) event Ti >> 19.02.2008 18:00-18:23 'Oikea kysymys' status 4 >> Feb 19 18:01:14 vdr vdr: [28242] channel 5 (YLE Teema) event Ti >> 19.02.2008 18:01-18:02 'Katsaus tulevaan' status 4 >> Feb 19 18:02:28 vdr vdr: [28242] channel 5 (YLE Teema) event Ti >> 19.02.2008 18:02-18:16 'opettaja.tv: Opinto-ohjaus' status 4 >> >> In ver. 1.5.x it is not, at least in 1.5.12 and 1.5.15 >> >> Log level ? or some other def ? > > Works fine here: > > Feb 19 17:14:41 video vdr: [31355] channel 1009 (ZDF) event Tue 19.02.2008 > 17:15-17:45 (VPS: 19.02 17:15) 'hallo deutschland' status 4 > > Note that this is only logged or channels that have timers. Ach, that was it, thanks.. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Event info in log
Event info has disappeared. In ver 1.4.x it is Feb 19 18:00:20 vdr vdr: [28242] channel 2 (YLE TV2) event Ti 19.02.2008 18:00-18:23 'Oikea kysymys' status 4 Feb 19 18:01:14 vdr vdr: [28242] channel 5 (YLE Teema) event Ti 19.02.2008 18:01-18:02 'Katsaus tulevaan' status 4 Feb 19 18:02:28 vdr vdr: [28242] channel 5 (YLE Teema) event Ti 19.02.2008 18:02-18:16 'opettaja.tv: Opinto-ohjaus' status 4 In ver. 1.5.x it is not, at least in 1.5.12 and 1.5.15 Log level ? or some other def ? -- [EMAIL PROTECTED] * Using HTML-mail is like breaking wind in a church * 60.2N 24.7E * it is not illegal, just extremely bad manners * ___ 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?
Ludwig Nussel wrote: > Klaus Schmidinger wrote: >>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. > > It would be pity if that means that the stable version stays at > 1.6.0 and doesn't receive any more bugfixes though. Bugs ? The VDR is the only bugfree software known. You must not mix features and bugs. ___ 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?
Klaus Schmidinger wrote: >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 - if it works without any devel-type drivers, just with standard kernel as delivered with debian etch ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDTV - 2B or not 2B
Alasdair Campbell wrote: > Lauri Tischler wrote: >> Füley István wrote: >>>> Oops, that's really not so good... one can't comment about HDTV with a >>>> resolution which is not full HDTV : 1920x1080... >>> Ok, this means that my setup is a low-end instead of being "average" as I >>> stated before, therefore my considerations about HDTV was totally wrong. >>> >>> But to buy a 1000+ Euro TV set? That's another reason for me to stay SD. >> Not really, FullHD also means large, minimum 42", it is quite senseless >> to to watch good picture on a postcard, so you start at €1500 > > You forgot to add the €20,000 building an extension to your house, if > you don't want your living room to be dominated by a 42" diagonal piece > of plastic. Thats peanuts, considering you spend the same amount for cables alone http://www.pearcable.com/sub_products_anjou_sc.htm ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HDTV - 2B or not 2B
Füley István wrote: >> Oops, that's really not so good... one can't comment about HDTV with a >> resolution which is not full HDTV : 1920x1080... > > Ok, this means that my setup is a low-end instead of being "average" as I > stated before, therefore my considerations about HDTV was totally wrong. > > But to buy a 1000+ Euro TV set? That's another reason for me to stay SD. Not really, FullHD also means large, minimum 42", it is quite senseless to to watch good picture on a postcard, so you start at €1500 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
Jan Exner wrote: > But there are more people like Klaus who are quite happy with hardware > decoding, and I am grateful he works the way he does. Hear, hear... Thankfully no need for totally bloated X-stuff or framebuffers or such.. Just plain minimal text/consolebased system. VDR _is_ just a Set-Top-Box ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
Füley István wrote: > PCI-Express has nothing to do with PCI, they're different slots. > I'm selling hardware, and as I said before, current motherboards does > not have 5 PCI slots. > The last boards with 5 PCI slots were these: Asus P5P800, with AGP port, > socket 775 on board 10/100 LAN, DDR 1 support. Similar is Asrock AM2NF3-VSTA, 5 PCI, 1 AGP Socket AM2, lan 10/100 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
Klaus Schmidinger wrote: > Does anybody have a recommendation for such a board? Asrock ALiveNF5SLI-1394 has seven pci-slots - 1 x PCI Express x 16 slot (White) - 2 x PCI Express x 8 slots (Yellow; for NVIDIA® SLI™ only) - 1 x PCI Express x1 slot - 3 x PCI slots ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
Klaus Schmidinger wrote: > From the pictures and description I also don't see any optical > SPDIF output to which I could connect my Dolby-Digital decoder. > AFAIK the HDMI connector also provids the digital audio, but > that would go to the tv set - how would it go to the DD decoder? http://www.octavainc.com/HDMI%20distribution%20amp_splitter%202%20port.html There are others too... ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
Pasi Kärkkäinen wrote: > Btw afaik some countries are broadcasting SD content H.264 encoded.. norway > for example? Estonia sends all in mpeg-4, i think... > Eesti DVB-T teenus hakkab tööle järgmiste parameetritega: > Modulatsiooni tüüp: COFDM > Modulatsiooniskeem: 64 QAM > Kandvate arv: 8k > Veaparanduskood: 2/3 > Kaitseintervall, olenevalt piirkonna vajadustele: 1/16 või 1/8 > Hierarhiline modulatsioon: Ei kasutata > Modulatsiooni parameeter alfa: 1 > Ühesageduslik võrk (SFN): Kasutuses piirkonniti > Kasutatavad sagedusala: UHF IV ja V ala, kanalid 21-69, sagedustel: 470 - 862 > MHz > Kanali ribalaius: 8 MHz > Transpordivoog: MPEG-2 > Video pakkimistüüp: MPEG-4 AVC > Audio pakkimistüüp: MPEG-1 layer 2; Dolby-E and AC3 (läbijooks) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features ? Was: [ANNOUNCE] vdr-xine-0.8.0 plugin
Klaus Schmidinger wrote: > On 11/14/07 17:24, Lauri Tischler wrote: >> [EMAIL PROTECTED] wrote: >>> "Graziano Pavone" <[EMAIL PROTECTED]> writes: >>> >>> [...] >>>> And you wouldn't mind applying a huge patch on VDR to achieve this >>>> goal? >>>> >>>> This feature is so interesting that I certainly wouldn't mind, even if it >>>> would a very good feature to be included in the 1.5 vdr release... :) >>> imho that's a feature that must be in 1.5 ! >>> as with the smart channel management. >>> >>> utf8 and subtitles are great achievements, what's next ? :-) >> You have to ask Santa-Klaus ;) > > H.264 will only become interesting (to me) once there are hardware > devices that can replay it (aka "Full Featured DVB cards"). > I am not interested in software players that might not even run > on my 450 MHz VDR. Reminds me of old electronics magazine 'Byte', there was one fellow, Steve Ciarcia, with all kind of hardware projects. He allways said 'the most efficient compiler is solder' -- If it's worth doing, it's worth doing in hardware. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features ? Was: [ANNOUNCE] vdr-xine-0.8.0 plugin
[EMAIL PROTECTED] wrote: > "Graziano Pavone" <[EMAIL PROTECTED]> writes: > > [...] >> And you wouldn't mind applying a huge patch on VDR to achieve this goal? >> >> This feature is so interesting that I certainly wouldn't mind, even if it >> would a very good feature to be included in the 1.5 vdr release... :) > > imho that's a feature that must be in 1.5 ! > as with the smart channel management. > > utf8 and subtitles are great achievements, what's next ? :-) You have to ask Santa-Klaus ;) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.11 segfaults at startup
Mika Orajärvi wrote: > Hi, > I tried starting vdr without existing setup.conf and by default it seems > that Sans Serif is used. But it seems that I don't have that either since > Vdr still segfaults, now with following backtrace. By the way, is "fc-list" > the correct way to check if certain font is available or not? According to > fc-list I don't have Sans Serif.. If you are using Debian, try to install ttf-dejavu package, that has Sans Serif ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Max 4 DVB Devices on VDR?
Morfsta wrote: > Hi, > > I have just added a Nova-T 500 device to my VDR stable setup (1.4.7) > and now have 5 frontends: - > > [ 29.735000] DVB: registering frontend 0 (ST STV0299 DVB-S)... > [ 29.955000] DVB: registering frontend 1 (ST STV0299 DVB-S)... > [ 29.976000] DVB: registering frontend 2 (Conexant CX22702 DVB-T)... > [ 30.129000] DVB: registering frontend 3 (DiBcom 3000MC/P)... > [ 30.634000] DVB: registering frontend 4 (DiBcom 3000MC/P)... > > The problem I have is that the fifth frontend doesn't work in VDR > (i.e. I can only tune to 2 DVB-T stations simultaneously). If I move > my DVB-TTPCI device to the 5th in the setup I then don't get any > output via the mpeg2 decoder either, proving that the 5th device is > also not being picked up. > > Is there a restriction of frontends in VDR and if so, how can I up it? Try to increase MAXDVBDEVICES in dvbdevice.h ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.11 segfaults at startup
Mika Orajärvi wrote: > Hi! > > I’m trying to update vdr 1.4.x to 1.5.11. But my vdr keeps segfaulting every > time when it’s started. It takes about 2-3 s after starting the vdr to the > segfault. I’ve tried running it only with xine-plugin (0.8.0) so far and > without any patches on top of vdr. And i’m running vdr on Ubuntu Dapper. > > GDB gives following backtrace, any ideas? It seems to be something related > to fonts,.. but beyond that I have no idea. VDR does crash if you dont have selected font available. I can crash my 1.5.11 everytime when in OSD I select font which I dont have, I tryed with 'small font'. Then I need to manually edit 'FontSml' to existing font, Sans Serif. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.5.11 & subtitling problems
Rolf Ahrenberg wrote: > On Tue, 6 Nov 2007, Reinhard Nissl wrote: > >> The problem for this issue is in cRemux::cRemux(): >> new cRingBufferLinear(RESULTBUFFERSIZE, IPACKS, false, "Result"); >> IPACKS needs to be replaced by SUBTITLE_PACKS too. Otherwise a packet >> larger than IPACKS (up to SUBTITLE_PACKS) cannot be read near the end of >> the buffer which holds reading the buffer and will finally let the >> buffer run full. > > Thanks. I made the necessary modification and haven't noticed any > freezes afterwards. I can confirm that. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no locales ??
Lauri Tischler wrote: > Nov 7 12:25:58 vdr2 vdr: [1407] VDR version 1.5.11 started > Nov 7 12:25:58 vdr2 vdr: [1407] switched to user 'root' > Nov 7 12:25:58 vdr2 vdr: [1407] found 0 locales in ./locale > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'deu,ger' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'slv,slo' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'ita' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'dut,nla,nld' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'por' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'fra,fre' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'nor' > Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'fin,smi' > > directory vdr-1.5.11/locale has a bunch of locales > variable LANG has been set to fi_FI > Am I missing something ?? Well, my error, locales were old, I had only [EMAIL PROTECTED] regenerated localestuff, works now, just need to fix that remux buffer overflow ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] no locales ??
Nov 7 12:25:58 vdr2 vdr: [1407] VDR version 1.5.11 started Nov 7 12:25:58 vdr2 vdr: [1407] switched to user 'root' Nov 7 12:25:58 vdr2 vdr: [1407] found 0 locales in ./locale Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'deu,ger' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'slv,slo' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'ita' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'dut,nla,nld' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'por' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'fra,fre' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'nor' Nov 7 12:25:58 vdr2 vdr: [1407] no locale for language code 'fin,smi' directory vdr-1.5.11/locale has a bunch of locales variable LANG has been set to fi_FI Am I missing something ?? Why is language code for finnish defined as fin,smi shouldnt it be fin,suo ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] osdtetetext plugin
that plugin is ancient. Is there somewhere a plugin which compiles under 1.4.6 or so. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
