[vdr] vdr 1.4.7 + mp3-0.10.0
Hi, When I click on encode dvd from vdrrip plugin menu, I have this error: vdr[6891] general protection eip:80e6531 esp:bff26120 error:0 gdb stacktrace: $ gdb ./vdr core.6891 [...] Loaded symbols for /lib/tls/i686/cmov/libnss_files.so.2 Core was generated by `/vdr/VDR/vdr -w 60 -v /storage/recordings -L /vdr/VDR/PLUGINS/lib -d -c /storag'. Program terminated with signal 11, Segmentation fault. #0 0x080e6531 in cOsdMenu::AddSubMenu (this=0xb46049b8, SubMenu=0x) at osdbase.c:490 490 subMenu-Display(); (gdb) bt #0 0x080e6531 in cOsdMenu::AddSubMenu (this=0xb46049b8, SubMenu=0x) at osdbase.c:490 #1 0x080d8f97 in cMenuMain::ProcessKey (this=0xb46049b8, Key=kOk) at menu.c:3241 #2 0x08130b56 in main (argc=52, argv=0xbff26614) at vdr.c:1042 Current language: auto; currently c++ (gdb) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.4.7 + mp3-0.10.0
nevermind schrieb: When I click on encode dvd from vdrrip plugin menu, I have this error: How is this related to mp3-plugin (as mentioned in the subject)? Regards -- Stefan Huelswitt s.huelsw...@gmx.de | http://www.muempf.de/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.4.7 + mp3-0.10.0
Stefan Huelswitt s.huelswitt at gmx.de writes: How is this related to mp3-plugin (as mentioned in the subject)? Sorry I made a mistake !! wrong copy paste on the subject :( The correct is : vdr 1.4.7 + vdrrip-0.3.0 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDRAdmin-AM for VDR 1.7.4
Hallo, Andreas Mair schrieb: Hello! Sure, there are plans to support vdr 1.7.4 but I didn't have the time to setup vdr 1.7.4, do some recordings and modify VDRAdmin-AM. But if you want you can provide some v1.7.4 recording folders but with empty .ts files. Please send them personal email. Ich habe eine Aufzeichnung angegangen. Die Verzeichnisstruktur ist, wie es bei mir in /var/vdr/video liegt. Gruß, Artem rtl-vdr-1.7.4.tar.gz Description: GNU Zip compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.0 S2API - Channels not Available
Hi, Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. On booting the kernel loads all the modules and I see the various frontends and when I start VDR it loads all of the relevant firmware okay. When I start VDR it won't show any of the FTA channels on DVB-T or DVB-S (not even tried S2!) and all I get is Channel Not Available. I wish VDR were more descriptive in why the channels are not available! :-) Apologies if this has been asked before, but is there anything I'm missing? Is the problem that I took my channels.conf from my multiproto VDR and something has now changed in the format? It would be good to get this working as my old OS is now messy and really needs a clean build with a shiny new kernel and I can't patch up to date multiproto with the old HVR4000 patches (a few FAILS which I guess I could fix, but might take some time as they don't look that trivial) and an older version of multiproto from HG doesn't compile on the new kernel! Can anyone point me in the right direction on what might be going on? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Well, even using *any* version 1.7.x in a productive environment is a risk ;-) [SNIP] S2API was necessary for HDTV channels, and recording HDTV channels only makes sense in TS. The PES recording of HDTV broadcasts was never officially supported by VDR. The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 13:38, schreef Ales Jurik: -- SNIP -- Hi, Hello! I have it working with some dirty hacks (reelvdr svn 10388 - the latest with hdplayer). But for the problem with sending AC3 sound to ac3dec (with -a ac3dec) I didn't have enough time to solve. With sound over HDMI it could be used. Would you be filling to upload the patch to the ML or send it to me directly? I use sound over HDMI anyway since I redirect the sound from my Plasma to my receiver. Ales Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ehd vs normal dvi output
Hi, How is the picture quality with the eHD compared to using just x11 and and DVI connected to a flatpanel? Is there a big difference? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote:
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger
klaus.schmidin...@cadsoft.de wrote:
Well, even using *any* version 1.7.x in a productive environment
is a risk ;-)
[SNIP]
S2API was necessary for HDTV channels, and recording HDTV channels
only makes sense in TS. The PES recording of HDTV broadcasts was never
officially supported by VDR.
The other problem is that I don't think anyone has got VDR 1.7.4
working with the eHD yet, which is my output device... :-( So it seems
everywhere I look at the moment I am stuck. :-(
Here are patches for eHD and vdr-1.7.4. I've tested it only for a little time
as I didn't have enough time (now I revert back to vdr-1.7.0 with
multiproto).
Included are two patches - first is for reelbox plugin. In file
ReelBoxDevice.c patch solves the audio problem (vdr is sending audio with
zero trackid and reelbox plugin cancel such streams). In setupmenu.c is
solved the problem with saving config and in VideoPlayerPipHd.c the include
solves for me compile problem in amd64 linux.
In the patch for vdr in part of device.c is patch from Klaus for subtitles and
rest is very quick and dirty patch for osd to compile with reelbox plugin. It
mostly revert the vdr osd to 1.7.0 version of files, but it seems to be
working at minimum with default STTNG skin, other skins are not tested.
Enjoy,
BR,
Ales
diff -ru vdr-1.7.4.orig/config.h vdr-1.7.4/config.h
--- vdr-1.7.4.orig/config.h 2009-01-06 17:56:27.0 +0100
+++ vdr-1.7.4/config.h 2009-02-01 20:47:21.611262480 +0100
@@ -192,11 +192,11 @@
void StoreLanguages(const char *Name, int *Values);
bool ParseLanguages(const char *Value, int *Values);
bool Parse(const char *Name, const char *Value);
- cSetupLine *Get(const char *Name, const char *Plugin = NULL);
void Store(const char *Name, const char *Value, const char *Plugin = NULL, bool AllowMultiple = false);
void Store(const char *Name, int Value, const char *Plugin = NULL);
public:
// Also adjust cMenuSetup (menu.c) when adding parameters here!
+ cSetupLine *Get(const char *Name, const char *Plugin = NULL);
int __BeginData__;
char OSDLanguage[I18N_MAX_LOCALE_LEN];
char OSDSkin[MaxSkinName];
diff -ru vdr-1.7.4.orig/device.c vdr-1.7.4/device.c
--- vdr-1.7.4.orig/device.c 2009-01-25 12:10:56.0 +0100
+++ vdr-1.7.4/device.c 2009-02-01 20:35:04.203264160 +0100
@@ -1304,8 +1304,9 @@
if (!dvbSubtitleConverter)
dvbSubtitleConverter = new cDvbSubtitleConverter;
tsToPesSubtitle.PutTs(Data, Length);
- if (const uchar *p = tsToPesSubtitle.GetPes(Length)) {
- dvbSubtitleConverter-Convert(p, Length);
+ int l;
+ if (const uchar *p = tsToPesSubtitle.GetPes(l)) {
+ dvbSubtitleConverter-Convert(p, l);
tsToPesSubtitle.Reset();
}
return Length;
diff -ru vdr-1.7.4.orig/font.h vdr-1.7.4/font.h
--- vdr-1.7.4.orig/font.h 2007-06-23 12:09:14.0 +0200
+++ vdr-1.7.4/font.h 2009-02-01 20:47:21.611262480 +0100
@@ -36,6 +36,12 @@
private:
static cFont *fonts[];
public:
+ enum { NUMCHARS = 256 };
+ typedef uint32_t tPixelData;
+ struct tCharData {
+ tPixelData width, height;
+ tPixelData lines[1];
+ };
virtual ~cFont() {}
virtual int Width(uint c) const = 0;
/// Returns the width of the given character in pixel.
diff -ru vdr-1.7.4.orig/osdbase.h vdr-1.7.4/osdbase.h
--- vdr-1.7.4.orig/osdbase.h 2007-11-03 15:50:52.0 +0100
+++ vdr-1.7.4/osdbase.h 2009-02-01 20:47:21.611262480 +0100
@@ -84,9 +84,7 @@
class cOsdMenu : public cOsdObject, public cListcOsdItem {
private:
- static cSkinDisplayMenu *displayMenu;
static int displayMenuCount;
- static int displayMenuItems;
char *title;
int cols[cSkinDisplayMenu::MaxTabs];
int first, current, marked;
@@ -97,6 +95,7 @@
bool hasHotkeys;
protected:
void SetDisplayMenu(void);
+ static int displayMenuItems;
cSkinDisplayMenu *DisplayMenu(void) { return displayMenu; }
const char *hk(const char *s);
void SetCols(int c0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
@@ -123,6 +122,7 @@
public:
cOsdMenu(const char *Title, int c0 = 0, int c1 = 0, int c2 = 0, int c3 = 0, int c4 = 0);
virtual ~cOsdMenu();
+ static cSkinDisplayMenu *displayMenu;
virtual bool NeedsFastResponse(void) { return subMenu ? subMenu-NeedsFastResponse() : cOsdObject::NeedsFastResponse(); }
int Current(void) const { return current; }
void Add(cOsdItem *Item, bool Current = false, cOsdItem *After = NULL);
diff -ru vdr-1.7.4.orig/osd.c vdr-1.7.4/osd.c
--- vdr-1.7.4.orig/osd.c 2009-01-16 15:34:32.0 +0100
+++ vdr-1.7.4/osd.c 2009-02-01 20:47:21.611262480 +0100
@@ -379,13 +379,14 @@
if (strncmp(Xpm[i + 1], s, c) == 0) {
if (i == NoneColorIndex)
NoneColorIndex = MAXNUMCOLORS;
- SetIndex(x, y, (IgnoreNone i NoneColorIndex) ? i - 1 : i);
+ SetIndexFast(x, y, (IgnoreNone i
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wednesday 04 of February 2009, Morfsta wrote: On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Well, even using *any* version 1.7.x in a productive environment is a risk ;-) [SNIP] S2API was necessary for HDTV channels, and recording HDTV channels only makes sense in TS. The PES recording of HDTV broadcasts was never officially supported by VDR. The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( Hi, I have it working with some dirty hacks (reelvdr svn 10388 - the latest with hdplayer). But for the problem with sending AC3 sound to ac3dec (with -a ac3dec) I didn't have enough time to solve. With sound over HDMI it could be used. Ales Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 13:22, schreef Morfsta: -- SNIP -- The other problem is that I don't think anyone has got VDR 1.7.4 working with the eHD yet, which is my output device... :-( So it seems everywhere I look at the moment I am stuck. :-( This is indeed correct. The eHD (which I have in use also) seems to be very stable in 1.7.0. The versions 1.7.3 and 1.7.4 didn't give me any audio. Hopefully this will be fixed soon. Because this is the only thing keeping me from using VDR 1.7.4 :) Should VDR-1.7.0 be reporting my DVB-T frontends as DVBT when it starts up? Is there perhaps a capability flag in the driver that has not been setup for the devices that I am using? I compared the channel settings of BBC ONE in VDR with multiproto version and s2api version that I am running and they are exactly the same. I have that too, nothing to get worried about it. The DVB-T device gives out wrong supported transports (like DVBS) but the code/patch will only lock DVB-T transports with DVB-T devices. At least, during my testing ;) @Niels, which DVB-T devices are you using successfully with VDR-1.7.0 so that I can compare them with my own drivers? It seems strange though that scan-s2 successfully finds all the channels but VDR won't play them. I still think it's a problem with the channel.conf. For fun, please try using the old and default scan for DVB-T. Because I used the old dvb-scan with the option to output for VDR on my Gigabyte GT-U7000-RH based DVB-T adapter to scan for KPN Digitenne bouquets (location Zwolle/Apeldoorn). Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. Sorry to double post but as an update I removed all DVB-T channels and then rescanned them using scan-s2 from http://mercurial.intuxication.org/hg/scan-s2/. It found all the channels on my transmitter. Also DVB-S channels seem to be working fine, not tried S2 yet. The new format for DVB-T presented is: - BBC ONE;BBC:73:I999B8C34D34M16T2G32Y0:T:27500:600:601=eng,602=eng:0:0:4165:9018:4101:0 which is now accepted by VDR. However, I get a black screen when tuning to them. In user.log I see: - Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter0/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 1 provides: DVBS DSS Feb 4 10:38:08 morfsta vdr: [18344] tuner on device 1 thread started (pid=18340, tid=18344) Feb 4 10:38:08 morfsta vdr: [18345] section handler thread started (pid=18340, tid=18345) Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter1/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 2 provides: DVBS DSS Feb 4 10:38:08 morfsta vdr: [18347] tuner on device 2 thread started (pid=18340, tid=18347) Feb 4 10:38:08 morfsta vdr: [18348] section handler thread started (pid=18340, tid=18348) Feb 4 10:38:08 morfsta vdr: [18340] probing /dev/dvb/adapter2/frontend0 Feb 4 10:38:08 morfsta vdr: [18340] device 3 provides: DVBS DVBS2 Feb 4 10:38:08 morfsta vdr: [18340] device 3 forced to frontendType SYS_DVBS2 Feb 4 10:38:08 morfsta vdr: [18350] tuner on device 3 thread started (pid=18340, tid=18350) Feb 4 10:38:09 morfsta vdr: [18351] section handler thread started (pid=18340, tid=18351) which is funny because devices 0 and 1 are DVB-T: [ 12.497993] DVB: registering adapter 0 frontend -858993460 (Philips TDA10045H DVB-T)... [ 12.554597] DVB: registering adapter 1 frontend -858993460 (Conexant CX22702 DVB-T)... [ 12.594872] DVB: registering adapter 2 frontend 0 (Conexant CX24116/CX24118)... then when VDR starts tuning I see: Feb 4 10:38:18 morfsta vdr: [18344] frontend 0 timed out while tuning to channel 1, tp 642 Feb 4 10:39:18 morfsta vdr: [18347] frontend 1 timed out while tuning to channel 1, tp 642 Feb 4 10:39:21 morfsta vdr: [18344] frontend 0 timed out while tuning to channel 1, tp 642 Any suggestions? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Op Wo, 4 februari, 2009 10:16, schreef Morfsta: Hi, Goodmorning! Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. You might want to try Igor's repo http://mercurial.intuxication.org/hg/s2-liplianin) since Steve's hasn't been updated for over 3 months. This however won't fix your problem perse. On booting the kernel loads all the modules and I see the various frontends and when I start VDR it loads all of the relevant firmware okay. When I start VDR it won't show any of the FTA channels on DVB-T or DVB-S (not even tried S2!) and all I get is Channel Not Available. I wish VDR were more descriptive in why the channels are not available! :-) Did you install mine S2API patch from 7-10 for VDR 1.7.0? Because this is the latest version and this has been tested with DVB-T, DVB-S, DVB-S2 and DVB-C. And with succes! ;) BTW, you might want to increase the logging for VDR or check the logfiles in /var/log what VDR has thrown out (Ubuntu uses /var/log/user.log for instance). My best guess is an frontend timeout error. This means that a timeout (duh!) occured when tuning to the selected channel. This can mean a reception problem (not likely, but good to point out) or a problem in your channels.conf. Apologies if this has been asked before, but is there anything I'm missing? Is the problem that I took my channels.conf from my multiproto VDR and something has now changed in the format? The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. It would be good to get this working as my old OS is now messy and really needs a clean build with a shiny new kernel and I can't patch up to date multiproto with the old HVR4000 patches (a few FAILS which I guess I could fix, but might take some time as they don't look that trivial) and an older version of multiproto from HG doesn't compile on the new kernel! Best to say, multiproto is not needed to get it al working. I've got the same kind of config as you ( NOVA-HD-S2 and a Gigabyte USB stick for DVB-T) and it works very good with S2API. Can anyone point me in the right direction on what might be going on? See the above ;) Thanks Regards, Niels Wagenaar ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 9:39 AM, Niels Wagenaar n.wagen...@xs4all.nl wrote: Goodmorning! Morning Niels, thanks for getting back to me so quickly! You might want to try Igor's repo http://mercurial.intuxication.org/hg/s2-liplianin) since Steve's hasn't been updated for over 3 months. This however won't fix your problem perse. OK, done that. Did you install mine S2API patch from 7-10 for VDR 1.7.0? Because this is the latest version and this has been tested with DVB-T, DVB-S, DVB-S2 and DVB-C. And with succes! ;) Specifically I have installed: vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff vdr-1.7.0-s2api-07102008-h264-clean.patch the only other plugin I am using at this stage is the reelbox plugin output which seems to work fine. BTW, you might want to increase the logging for VDR or check the logfiles in /var/log what VDR has thrown out (Ubuntu uses /var/log/user.log for instance). My best guess is an frontend timeout error. This means that a timeout (duh!) occured when tuning to the selected channel. This can mean a reception problem (not likely, but good to point out) or a problem in your channels.conf. Now I have recompiled it all and when I run VDR I get: - vdr: error while reading '/video/config6/channels.conf' in /var/log/user.log I see: - Feb 4 10:06:01 morfsta vdr: [17791] loading /video/config6/channels.conf Feb 4 10:06:01 morfsta vdr: [17791] ERROR: unknown parameter key 'A' Feb 4 10:06:01 morfsta vdr: [17791] ERROR: error in /video/config6/channels.conf, line 2 Line 2 is a DVB-T channel: - BBC ONE;BBC:73000:A0B8C34D34G32I0M16P0T2Y0:T:27500:600:601=eng,602=eng:0:0:4 165:9018:4101:0 This channel works fine in vdr-1.7.0 with multiproto and there are definitely no reception problems as all DVB-T and DVB-S channels works fine with previous implementation (which I have kept in a seperate parition obviously!). The Multiproto channels.conf should be interchangeable with S2API. But *some* modulation types didn't exist in S2API when I wrote the patches and you need to check this for yourself. You need to check the settings (Red button to edit in the TV Channels overview) and see if they are indeed correct and change them accordinly. My best guess, is that the modulation types are wrong. It seems that the channels.conf isn't interchangeable as the multiproto channels.conf now seems to be rejected and I can't even start VDR now. Perhaps the leading A is now unsupported in the options, is there a way I could possibly modify the file to remove this stuff? See the above ;) Any more ideas? ;-) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On 04.02.2009 11:41, Morfsta wrote: ...[ tunig problems ] Any suggestions? Have you considered trying VDR 1.7.4? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
I still think it's a problem with the channel.conf. For fun, please try using the old and default scan for DVB-T. Because I used the old dvb-scan with the option to output for VDR on my Gigabyte GT-U7000-RH based DVB-T adapter to scan for KPN Digitenne bouquets (location Zwolle/Apeldoorn). Tried this, again finds all the channels but when put into VDR no video appears (however I do see the programme listings in the EPG). Any more ideas? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
On Wed, Feb 4, 2009 at 10:58 AM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Have you considered trying VDR 1.7.4? Klaus, 1.7.4 works fine with S2API and DVB-T here Looks like there might be a problem in your patch somewhere Niels, but not sure where? I would still prefer to use 1.7.0 if possible, as expected a ton of plugins don't compile with 1.7.4... :-( ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] VDRAdmin-AM for VDR 1.7.4
Hello,
On Wed, Feb 04, 2009 at 09:08:17AM +0100, Andreas Mair wrote:
Hello!
Sure, there are plans to support vdr 1.7.4 but I didn't have the time
to setup vdr 1.7.4, do some recordings and modify VDRAdmin-AM.
I have attached a patch with makes vdradmin-am able to playback the new .ts
recorings and also the old ones.
I am not an regexp expert, so there could be a nicer way to do this.
Regards, Artem
--- vdradmind.pl.old 2009-02-04 19:48:12.0 +0100
+++ vdradmind.pl 2009-02-04 19:52:29.0 +0100
@@ -4830,8 +4830,8 @@
my $data;
$title =~ s/ /_/g;
$title =~ s/~/\//g;
-Log(LOG_DEBUG, rec_stream: find $CONFIG{VIDEODIR}/ -follow -regex \$CONFIG{VIDEODIR}/$title\_*/\\(\_/\\)?-$month-$day\\.$hour.$minute\\...\\...\\.rec/...\\.vdr\);
-my @files = `find $CONFIG{VIDEODIR}/ -follow -regex $CONFIG{VIDEODIR}/$title\_*/\\(\_/\\)?-$month-$day\\.$hour.$minute\\...\\...\\.rec/...\\.vdr | sort -r`;
+Log(LOG_DEBUG, rec_stream: find $CONFIG{VIDEODIR}/ -follow -regex \$CONFIG{VIDEODIR}/$title\_*/\\(\_/\\)?-$month-$day\\.$hour.$minute..?.?...\\.rec/\\(...\\.vdr\\|.\\.ts\\)\);
+my @files = `find $CONFIG{VIDEODIR}/ -follow -regex $CONFIG{VIDEODIR}/$title\_*/\\(\_/\\)?-$month-$day\\.$hour.$minute..?.?...\\.rec/\\(...\\.vdr\\|.\\.ts\\) | sort -r`;
foreach (@files) {
chomp;
Log(LOG_DEBUG, findVideoFiles: found ($_)\n);
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-1.7.4 S2API and DVB-C ??
On 04/02/2009 19:26, Simon Baxter wrote: Hi Does vdr-1.7.4, ts recordings and and the S2API work under DVB-C? I can't see why it wouldn't? Dum question - where can I find the S2API repository? I just pulled the latest v4l-dvb from linuxtv.org, but I get vdr compiling errors requesting version 5. I think it should compile with that but you need to make sure it is using those headers. I changed line 24 of my Makefile to this: INCLUDES = -I/data/downloads/v4l-dvb/linux/include -I/usr/src/linux/include -I/usr/include/freetype2 Where /data/downloads/v4l-dvb is where you got the latest v4l-dvb tree. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rewind and Skip buttons
Hi, These buttons, the ones with the diode like pictures on them, dont seem to have enum entries in keys.h, is that correct? I see that green/yellow can be used for these functions, but what is the philosophy for what goes in the enum. Just curious. -- Scott ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Skip buttons
On 04.02.2009 21:11, Scott wrote: Hi, These buttons, the ones with the diode like pictures on them, dont seem to have enum entries in keys.h, is that correct? I see that green/yellow can be used for these functions, but what is the philosophy for what goes in the enum. Just curious. What about kPlay, kPause, kStop, kRecord, kFastFwd, kFastRew, kNext, kPrev, ? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. Can you try with vdr-1.7.4, that's the first version from vdr 1.7x series that i got working with s2api and hvr-4000. I have testeed it with streamdev server plugin and mplayervlc. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xine for vdr-0.7.4 doesn't patch
Hi I'm trying to patch the latest xine-lib sources supplied on http://home.vrweb.de/rnissl/ I see the patching mechanism has been changed in this version - and I now get this error: [r...@freddy development]# ls xine-lib AUTHORS ChangeLog COPYING CREDITS doc lib Makefile.am NEWS README TODO autogen.sh configure.ac COPYING.LIB debian include m4 misc posrc win32 [r...@freddy development]# patch -d. -p0 --dry-run ~/vdr-1.7.4/PLUGINS/src/xine/patches/xine-lib.patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? The text leading up to this was: -- |diff --git a/configure.ac b/configure.ac |--- a/configure.ac |+++ b/configure.ac -- File to patch: ^C It was: diff -Nurp ../xine-cvs/xine-lib/configure.ac xine-lib/configure.ac --- ../xine-cvs/xine-lib/configure.ac 2008-03-06 20:06:29.0 +0100 +++ xine-lib/configure.ac 2008-03-10 21:05:50.0 +0100 etc now it's: diff --git a/configure.ac b/configure.ac --- a/configure.ac +++ b/configure.ac Has the desired mechanism changed, and the INSTALL file not been updated?? Thanks Simon ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine for vdr-0.7.4 doesn't patch
I'm trying to patch the latest xine-lib sources supplied on http://home.vrweb.de/rnissl/ I see the patching mechanism has been changed in this version - and I now get this error: [r...@freddy development]# patch -d. -p0 --dry-run ~/vdr-1.7.4/PLUGINS/src/xine/patches/xine-lib.patch can't find file to patch at input line 4 Perhaps you used the wrong -p or --strip option? to patch xine-lb, create a symlink from xine-lib pointing to 'b': ln -s xine-lib b then run patch again. Cheers Mike Thanks - so the INSTALL has not been updated, or the wrong patch file went out then Cheers Simon ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
