vdr

vdr@linuxtv.org

2 participants
6731 discussions

vdr crashes when replaying zero length recording
by Torgeir Veimo 14 Mar '12

14 Mar '12

I've seen this a lot lately. due to tuning problems with my nova-t 500s, I've gotten frequent zero length recordings. Playing back these either using the xine plugin, or xineliboutput, causes VDR to crash and restart. I'm using yavdr with only trivial modifications. -- -Tor

4 9

remote.conf question
by Arturo Martinez 13 Mar '12

13 Mar '12

I have a remote control that on pressing a single specific key it sends two keys at once 0000000080010051 00 KEY_3 VRC-1100 000000008001004c 00 KEY_5 VRC-1100 Can I use this key somehow in vdr´s remote.con (to assign a command in the even that KEY_3 and KEY_5 are received at once)

1 0

Theses Client/Server VDR
by fnu 12 Mar '12

12 Mar '12

Hi there, following the discussion regarding Client/Server the last couple of day, I'm honestly horrified. What I did realize where super complex ideas, hacks, bottomline a solution from developers for developers. I got the imagination some want to keep out normal users, inventing VDR to death, because only a few users are able to handle it. Since Apple pretty much come with a TV solution this year, expectations of users will change in terms of GUI & usability. And not only Apple, even Ubuntu does invent in the same direction on their UbuntuTV. There's no need to copy these solutions, but the need to be prepared to these fast changing expectations. To think about the details of VDR, a good and stable solution, which I love to use since over 10 years now. I don't have any issues to run a complete VDR on Client and Server, the binary is small, so what. My dream of a Client/Server VDR solution is: - 1+n VDRs do find themselfs seemless w/o user interaction within a network - 1+n VDRs do elect/define a principle, which become the leader of the pack, preferably that one with (the most) DVB devices - The principle becomes the central point of VDR operation - Timers set on whether Client/Server VDR, is handled by the principle centrally - Recordings are also handled centrally on the principle, the clients do have seemless access to it - It doesn't matter if the clients do have their own disks - But if needed principle can use this addional disk space on clients and each client does also have seemless access - DVB devices can be added and removed dynamically to each of the VDRs, but principle stay responsible for all DVB devices within network - Plugins can be added/removed dynamically via OSD or a Web-Interface - The VDR pack or rather the principle can be controlled/programmed by a cloud service from all over the world. - Setting up one of these VDRs may only be possible for experienced user, but es soon as they're up and running, you're little children could hanle them. Just my vision for a smart client/server VDR solution. Cheers fnu

6 9

Local frontend - using XBMC strm vs vdr-sxfe
by Dominic Evans 11 Mar '12

11 Mar '12

Hi all, Running vdr-sxfe as a local frontend using a pipe _should_ be as fast (if not faster) than using XBMC over an http://localhost streamdev connection. However, I seem to find the opposite to be the case. vdr-sxfe still struggles with HD content, has pops and clicks in the audio, crashes out every now again and generally has inferior playback. On my main frontend I have VDR running full time in the background with no local frontend running. Then I have a bare-bones X11 configured with a simple .xinitrc that flips between running vdr-sxfe and xbmc (as I prefer it for watching DVDs etc.). For both frontends I am using VDPAU. I have to use vdr-sxfe to interact with the menus, auto skip adverts in recordings, do cutting, etc. But I'm increasingly finding myself using XBMC and just a directory full of .strm files that point at streamdev TS links, when I want to watch a live HD broadcast. Does anyone have vdr-sxfe running flawlessly as a local frontend for HD content? I just wish I could have the full VDR OSD, but within XBMC :) Cheers, Dom

9 16

[ANNOUNCE] VDR developer version 1.7.26
by Klaus Schmidinger 11 Mar '12

11 Mar '12

VDR developer version 1.7.26 is now available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.26.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.tvdr.de/vdr/Developer/vdr-1.7.25-1.7.26.diff MD5 checksums: eb57398e44935ecb0bfc532bdfead312 vdr-1.7.26.tar.bz2 62e0f39e2c53ec2b5abd3ebb0e00ce3d vdr-1.7.25-1.7.26.diff WARNING: ======== This is a *developer* version. Even though *I* use it in my productive environment. I strongly recommend that you only use it under controlled conditions and for testing and debugging. The changes since version 1.7.25: - Now checking for NULL in cOsd::AddPixmap() (suggested by Christoph Haubrich). - Fixed the German translation of "VDR will shut down in %s minutes" (thanks to Frank Neumann). - The replay progress display is now turned on whenever a mark is toggled (not only when one is set). - Toggling a mark now restarts the timeout of the replay progress display. - Fixed a possible race condition with the SVDRP commands CLRE and PUTE, where EPG data from the transponder could be handled even though it shouldn't be handled for 10 seconds. - Added some missing member initializations in cBitmap. - Improved displaying the play mode in the ST:TNG skin. - Made the ST:TNG skin the default in case the user selected skin is not available. - Improved displaying signal strength and quality in the ST:TNG skin's channel display. - Fixed switching devices to the transponders of VPS recordings in case there are only bonded devices. The cDevice's "avoid device" mechanism has been replaced by using "occupied". - Fixed selecting devices for the EPG scan in case the primary device is bonded with an other one. - Removed the calls to EITScanner.UsesDevice(this) from dvb[hs]ddevice.c, because the code following these calls is only executed if LiveView is true, which is never the case when the EITScanner switches to a channel. - Removed the obsolete function cEITScanner::UsesDevice(). If a plugin has used this function to find out whether a call to its cStatus::ChannelSwitch() function was due to a live channel switch, it can use that function's new parameter LiveView. Any plugins that implement cStatus::ChannelSwitch() need to add the parameter 'bool LiveView' to that function. - Fixed parsing channel data in case the audio pid is 0. On channels that only broadcast Dolby Digital audio there were sometimes log entries like "changing pids of channel ... from ... to ..." with no apparent difference between the old and new set of pids. - Fixed checking pids in case a channel has only Dolby Digital audio. - The Green button in the "Edit timer" menu can now be used to toggle between single shot and repeating timers. This is the same as pressing '0' when the "Day" field is selected, but it works at any time (and is more obvious). - Revoked "If the first event in a schedule has a table id of 0x00, any incoming EIT data for that schedule from the DVB stream will be completely ignored". - Added a new plugin interface for implementing EPG handlers. + A plugin can implement an EPG handler by creating an object derived from cEpgHandler and implementing the necessary member functions. + The special handling of events with table id 0x00 has been dropped. For backwards compatibility EPG events with table ids lower than 0x4E will be treated as if they had a table id of 0x4E, and the new plugin 'epgtableid0' can be used to have them handled like in previous versions. + The default table id for a newly created cEvent has been changed to 0xFF, which is higher than any normal table id that is broadcast in the EIT data. See PLUGINS.html, section "Electronic Program Guide" for more information. Have fun! Klaus

6 9

noepg-plugin
by Lars Hanisch 10 Mar '12

10 Mar '12

Don't want to hijack the announce-thread... :) Am 10.03.2012 20:26, schrieb Mika Laitio: >> Damn, too late for today... :-) >> Just finished the noepg-plugin-skeleton at > > So according to README this plug-in replaces the noepg.patch. > What is the functionality/purpose of this noepg patch/plugin? First it's just an example for the new interface. On the other hand it will help those who import epg "the old way" (SVDRP or other plugins) and don't want to mix it with the DVB-epg until there are enough epg-plugins to replace them. Since the starttimes of extern epg-sources sometimes don't match the DVB times it can lead to double entries. That was avoided with the noepg-patch which deactivated DVB-epg for selected channels. Lars. > > Mika > > _______________________________________________ > vdr mailing list > vdr(a)linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >

1 1

Re: [vdr] Local frontend - using XBMC strm vs vdr-sxfe
by Simon Baxter 09 Mar '12

09 Mar '12

On Fri, Mar 9, 2012 at 1:59 AM, Dominic Evans <oldmanuk(a)gmail.com> wrote: > > > I just wish I could have the full VDR OSD, but within XBMC :) > Yeah, shame about that. It's unfortunate the development on XMBC isn't anywhere as active or mature as VDR. I recently got really lazy and installed yavdr-0.4 after 7 years running everything from sources. It's simplicity of use is great. I use xineliboutput to watch DVDs, movies and live/recordings of ATSC HD and only use XBMC for all the web content (freecable, hulu etc). Works pretty well (apart from some regular xbmc crashing - which I really must look into at some point).

1 0

STNG Schedule Now and Next Column Widths
by Dominic Evans 09 Mar '12

09 Mar '12

Using the STNG skin at 1920x1080 (with the font size slightly reduced from default), the columns on the Now and Next pages of the Schedule don't currently adjust their width, but simply allocate all the extra space to the final column containing the title. See http://i.imgur.com/TKvGy.jpg for an example capture (1920x1080) Ideally the channels column would be auto-sized to display the full channel name, as these tend to be a max of 20 characters it would be useful to be able to see the whole thing.

1 1

Segfault in dvbhddevice
by Richard Scobie 08 Mar '12

08 Mar '12

For the past few weeks, I have been running the current 1.7.XX version of vdr with an S2-6400 card, using only one tuner, which is connected to a 4 x 1 diseqc switch, without any problems. The startup command has been: /usr/local/bin/vdr -L /home/rs/vdr/PLUGINS/lib -D 1 -P dvbhddevice -P femon -v /mnt/storage/video -s /usr/local/bin/pm & Today I replaced my LNB's with dual output ones, with the second output connected to a second 4 x 1 disecq switch, which is connected to the second tuner on the S2-6400 card. I removed the "-D 1" from the startup command and I am now finding that sometimes vdr crashes on startup, with the following error: Mar 7 17:40:46 atom kernel: [ 12.257270] vdr[755]: segfault at 0 ip 00007fd3118426d0 sp 00007fffcbf98968 error 4 in libvdr-dvbhddevice.so.1.7.25[7fd311835000+18000] If I then run the vdr startup command again, it starts OK. Please let me know if there is any other information I can provide - the current version I am using is vdr 1.7.25. Regards, Richard

5 8

Patch suggestion: Force CAM reset before upcoming recording
by Heikki Manninen 06 Mar '12

06 Mar '12

I have a number of different Conax CAM modules from different manufacturers and all of them disappear from VDR after a couple of days running. Hitting CAM reset on the CI menu will bring it back "online". Naturally all Conax channel recordings will fail silently as a result of this until the CAM has been brought back up. Switching to an encrypted channel just gives the standard "channel not available" message. This happens (for me) with Satelco DVB-C card with Satelco CI. From what I understand, this seems to be a common problem though I'm not sure whether it is limited to Satelco devices only. Would it be possible to force CAM reset on all CI slots when VDR is trying to start recording non-FTA channel? -- Heikki M

6 12

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr