vdr

vdr@linuxtv.org

2 participants
6731 discussions

terratec cinergy t2 remote control
by Borghart 20 Jun '05

20 Jun '05

hi! Is there anybody in this list, who is using the terratec cinergy t2 box, and has all keys of the remote control running? In my setup 'xev' says nothing when i press one of the colored keys. what do i have to do to get these keys working? regards, borghart

1 0

Re: [vdr] How to change the resolution?
by Jukka Tastula 19 Jun '05

19 Jun '05

On Monday 20 June 2005 01:16, Norm Dressler wrote: > Ok -- does it sound like I"m on the right track though? NTSC (29fps - I > did find a patch for the fps) 544x480 and I get messed up video that > looks like horz or vert sync is way off. Yes, if your dvd player does not support a resolution like that then you will have to re-encode it to a standard resolution like 640x480 or 720x480. You will need an mpeg2 encoder for this job. > I'm simply making a single movie on a dvd -- no menu or anything. It > works in all my computers, my kid's cheap dvd but not my home theatre. Have a look at http://mightylegends.zapto.org/dvd/dvdauthor_howto.php for all your dvd authoring needs. It amounts to quite a bit of work in the end but it's the only way other than getting a player that supports non-standard resolutions. You'll have so much fun with interlacing you didn't think it was possible before :)

1 0

How to change the resolution?
by Norm Dressler 19 Jun '05

19 Jun '05

Hi all, I had at one point changed the resolution of how my recordings were being saved -- they are now 544x480. My primary DVD player won't play this resolution though -- I get vertical sync issues. Ironically, my daugher's $39 Wal-Mart DVD player will play them but my home theatre setup won't! The resolution is all that I can see being the problem. I want to make it true NTSC with 648x486. I also want to try some of the other NTSC sizes like 720x486 and 720x540. Can someone point to where I can find this and whether it would be difficult to change? Thanks Norm

3 3

Re: [vdr] Re: [PATCH] "Natural" menu cursor 0.01
by C.Y.M 19 Jun '05

19 Jun '05

Patrick Gleichmann wrote: > Hi, > thanks for this bug report. > I really like this patch and would like to know if there is a fix for vdr-1.3.26 available? @Klaus: Would you consider adding this functionality to core vdr (wrap around menus)? Best Regards, C.Y.M.

6 16

Warnings with Xine Plugin and vdr-1.3.27
by C.Y.M 19 Jun '05

19 Jun '05

There are a few new warnings when building the Xine plugin with vdr-1.3.27. ccache g++ -g -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" `xine-config --cflags` -I../../../include -I../DVB/include xine.c ccache g++ -g -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" `xine-config --cflags` -I../../../include -I../DVB/include xineDevice.c In file included from xineDevice.c:8: ../../../include/vdr/osd.h:280: warning: `virtual void cOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int, bool)' was hidden xineOsd.h:49: warning: by `virtual void PluginXine::cXineOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int)' ccache g++ -g -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" `xine-config --cflags` -I../../../include -I../DVB/include xineLib.c In file included from xineLib.c:7: ../../../include/vdr/osd.h:280: warning: `virtual void cOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int, bool)' was hidden xineOsd.h:49: warning: by `virtual void PluginXine::cXineOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int)' ccache g++ -g -O2 -Wall -Woverloaded-virtual -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='"xine"' -DFIFO_DIR=\"/tmp/vdr-xine\" `xine-config --cflags` -I../../../include -I../DVB/include xineOsd.c In file included from xineOsd.c:4: ../../../include/vdr/osd.h:280: warning: `virtual void cOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int, bool)' was hidden xineOsd.h:49: warning: by `virtual void PluginXine::cXineOsd::DrawBitmap(int, int, const cBitmap&, unsigned int, unsigned int)' Best Regards, C.

2 2

VDR developer version 1.3.27
by Klaus Schmidinger 19 Jun '05

19 Jun '05

VDR developer version 1.3.27 is now available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.27.tar.bz2 A 'diff' against the previous version is available at ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.3.26-27.diff The changes since version 1.3.26: - Fixed handling 'page down', which was broken in version 1.3.26 (thanks to Udo Richter). - Modified page scrolling behaviour (based on a suggestion by Patrick Gleichmann). - The new setup option "OSD/Scroll wraps" can be used to activate wrapping around in menu lists (based on a suggestion by Patrick Gleichmann). - Removed the NPTL check at startup, since several users have reported that VDR now runs fine with NPTL. - Fixed handling VPS timers, so that they only record if the event they are assigned to actually has the given VPS time. - Disabled cVideoRepacker in remux.c, because it has caused several problems during recording. If you want to test (and maybe debug) it, activate the line //#define TEST_cVideoRepacker in remux.c. - When drawing a bitmap to the OSD, the existing palette of the target can now be replaced with the new one instead of adding the new entries (thanks to Andreas Regel). The DVB driver I am currently using can be found at ftp://ftp.cadsoft.de/vdr/Developer/linux-dvb.2004-12-26.tar.bz2 which is the CVS 'HEAD' version from 2004-12-26, made available as a complete archive for your convenience. Of course, you can also use any newer driver version. Have fun! Klaus PS: Since I'll be going on vacation there won't be anything new before July 13.

1 0

Hauppauge Nexus S plus Terratec Cinergy 1200 DVB-T PCI
by Olaf Meltzer 19 Jun '05

19 Jun '05

Hi! The a.m. cards are correctly working together. But now I realized, that DVB-T card channels not allways were reachable immediatly after booting. It seemed -- I'm not quite sure -- that this problem depended from the last channel seen before shutdown. If this had been a DVB-S channel, after the next boot DVB-T channels were off. Now I provided a link to the second firmware-file too, and the problem seems to be gone. I found no docs, how to configure these two cards correctly, but the naming scheme looks like this _is_ the way. /usr/lib/hotplug/firmware/dvb-ttpci-01.fw -> /usr/lib/hotplug/firmware/dvb-ttpci-01.fw-261d and now /usr/lib/hotplug/firmware/dvb-ttpci-02.fw -> /usr/lib/hotplug/firmware/dvb-ttpci-01.fw-261c Am I right so far? Greetings -- Olaf Meltzer

1 0

repost: [vdr] [Patch] Re: Time jumps
by Sergei Haller 19 Jun '05

19 Jun '05

repost for the thread [vdr] [PATCH] time warp ---------- Forwarded message ---------- From: Sergei Haller <Sergei.Haller(a)math.uni-giessen.de> Organization: University of Giessen * Germany To: VDR List <vdr(a)linuxtv.org> Date: Thu, 2 Jan 2003 00:19:18 +0100 (CET) Subject: [vdr] [Patch] Re: Time jumps [...] Anyway, here is a small implementation of the cMJD::SetSystemTime() method. This one just uses adjtime for small clock drifts and old behaviour (jump) for bigger drifts. (again, I'm sorry, but my vdr box is still broken, that's why I can't try it out directly in vdr, but this function should cleanly fit in 1.1.20's eit.c) -------------------------------------- #include <stdio.h> #include <stdlib.h> #include <time.h> #include <sys/time.h> /* these are for emulating vdr source only */ #define bool int #define true 1 #define false 0 #define isyslog printf #define esyslog printf time_t mjdtime; /* Note that adjtime speeds up or slows down the system clock by just 500 usec per second. That means, a difference of 1 second is done after ~33 minutes and a diff of 30 seconds after ~16.6 hours should this value become a setup parameter? */ #define MAXADJTIME 30 // seconds /* this is a modified cMJD::SetSystemTime() from eit.c */ bool SetSystemTime(void) { time_t loctim, diff; struct timeval delta; loctim = time(NULL); /* system time in seconds since epoch */ diff = mjdtime - loctim; if ( abs(diff) > 0 ) { isyslog("System Time = %s (%ld)\n", ctime(&loctim), loctim); isyslog("Local Time = %s (%ld)\n", ctime(&mjdtime), mjdtime); } if ( abs(diff) > MAXADJTIME ) { if (stime(&mjdtime) < 0) esyslog("ERROR while setting system time: %m\n"); return true; } else if ( abs(diff) > 0 ) { delta.tv_sec = diff; delta.tv_usec = 0; if (adjtime(&delta, NULL) < 0) esyslog("ERROR while adjusting system time: %m\n"); return true; } return false; } int main(void) { bool result; mjdtime = time(NULL) + 20 ; /* adjust the time by +20 seconds */ result = SetSystemTime(); return result; } -------------------------------------- c ya Sergei -- -------------------------------------------------------------------- -?) eMail: Sergei.Haller(a)math.uni-giessen.de /\\ -------------------------------------------------------------------- _\_V Be careful of reading health books, you might die of a misprint. -- Mark Twain

1 0

Problem with cVideoRepacker in 1.3.26
by Rene Jahn 19 Jun '05

19 Jun '05

Hello, i found following messages this morning in my syslog: Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: found system start code: stream seems to be scrambled or not demultiplexed Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: skipped 5617 bytes to sync on next picture Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: found system start code: stream seems to be scrambled or not demultiplexed Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: skipped 24 bytes to sync on next picture Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: found system start code: stream seems to be scrambled or not demultiplexed Jun 16 07:29:43 engine vdr[7492]: cVideoRepacker: skipped 24 bytes to sync on next picture Jun 16 07:29:45 engine vdr[7492]: ERROR: unknown picture type '6' Jun 16 07:29:45 engine vdr[7492]: cVideoRepacker: found system start code: stream seems to be scrambled or not demultiplexed Jun 16 07:29:45 engine vdr[7492]: cVideoRepacker: skipped 24 bytes to sync on next picture Jun 16 07:29:47 engine vdr[7492]: ERROR: result buffer overflow, dropped 2052 out of 2052 byte Jun 16 07:29:47 engine last message repeated 17 times I found the messages after i tried to use the picture-in-picture plugin(I have two nexus-s rev 2.3 ff cards in my system). The plugin didn't show a clear picture because the dvb driver crashed with my second card. The picture of the card was ambiguous. A reload of the dvb driver solved the problem(for some hours). I think it's a driver problem but maybe it's possible to catch above error?

3 4

channels.conf DVB-T Hamburg in VDR-WIKI partly wrong
by Olaf Meltzer 18 Jun '05

18 Jun '05

Hi, using the channels list from VDR-WIKI regarding Hamburg I found some errors. The bouquets frequency containing the following stations, is definitely wrong. Bayerisches FS:530000:... MDR:530000:... NDR FS NDS:530000:... NDR FS HH:... NDR FS SH:530000:... NDR FS MVP:530000:... I can read out some of the required data to establish the correct entries of a channels.conf, but not all, with the Windows application Cinergy Digital. I receive the complete set of stations under Windows without errors. The correct frequency of the above bouquet is 205500. But I presume, some of the other data might be still wrong, since even when I use those data, which I can read out under Windows, there is no receiption. I can read out frequency, VID, AID, and PID. And filling in / verify these data, I get the following lines for the bouquet. I broke lines here only for posting. Please correct this. :DVB-T Hamburg (wrong) Bayern (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4929:4930:4932:0:34:0:0:0 MDR (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4913:4914:4916:0:100:0:0:0 NDR NDS (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4881:4882:4884:0:129:0:0:0 NDR HH (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4881:4882:4884:0:130:0:0:0 NDR SH (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4881:4882:4884:0:131:0:0:0 NDR MVP (terr) :205500:I0C23D12M16B8T8G4Y0:T:27500:4881:4882:4884:0:132:0:0:0 WDR (terr) :205500:I0C23D0M64B8T8G8Y0:T:27500:4897:4898:4900:0:262:0:0:0 hr-fernsehen:754000:I0B8C23D0M64T8G8Y0:T:27500:4673:4674:4676:0:65:0:0:0 MDR:754000:I0B8C23D0M64T8G8Y0:T:27500:4657:4658:4660:0:100:0:0:0 NDR FS NDS:754000:I0B8C23D0M64T8G8Y0:T:27500:4625:4626:4628:0:129:0:0:0 WDR Is anybody able to verify this, or can give me the correct data? Another bouquet (hr-fernsehen, MDR, NDR FS NDS, WDR), which the VDR-WIKI locates in Hamburg, is actually receiptable here, but with weak signalstrength. It belongs to some region in the neighbourhood, possibly Niedersachsen, but not to Hamburg. Greetings -- Olaf Meltzer -- Olaf Meltzer, Im Fliederbusch 31, 22589 Hamburg Telefon +49-40-871146 Mobil +49-179-3669047 Fax: +49-40-871146 Email: olaf.meltzer(a)gmx.de

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

vdr