Hello,
I have discovered that France Television is free to air in DVB on Atlantic Bird 5W. Does anyone have an initial tuning file for this satellite please?
TIA Tony
On 03/05/05, tony tony@tgds.net wrote:
Hello,
I have discovered that France Television is free to air in DVB on Atlantic Bird 5W. Does anyone have an initial tuning file for this satellite please?
Are you sure it's in digital ? I think it's analog (but I am a little bit confusing now with Telecom 2B 5W ?).
Are you sure it's in digital ?
Yes, digital dvb: http://www.lyngsat.com/ab3.html (11591 V)
I think it's analog (but I am a little bit confusing now with Telecom 2B 5W ?).
Yes, analog secam: http://www.lyngsat.com/ab3.html
Guy
Hi.
I've just setup my WinTV NovaT on a new (2.2Ghz) shuttle PC and built the xine-plugin components.
I created a new channels.conf file with scan and ran up VDR
On some channels I get screens and screens of information like : FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126 FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126 FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126 FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126 FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970
I gather each specific XXXX number refers to capability needed on those specific channels??
any ideas?
Le mardi 03 mai 2005 à 14:21 +0200, Guy Roussin a écrit :
Are you sure it's in digital ?
Yes, digital dvb: http://www.lyngsat.com/ab3.html (11591 V)
I think it's analog (but I am a little bit confusing now with Telecom 2B 5W ?).
Yes, analog secam: http://www.lyngsat.com/ab3.html
France Television got some heat (I put some on) from people paying licence fee and not being able to see their channels free to air. They are getting more heat with the roll out of DVB-T (TNT) not being available everywhere so they took the plunge... The private channels should follow soon too from the rumours - market share any one...
So 5 years after Italy, Germany, Spain... France now has free to air DVB-S (at least for public service channels).
I am playing with FC4 so szap and scan are not plying nice with me which is why I asked for an initial tuning file.
Cheers
Tony
tony wrote:
Hello,
I have discovered that France Television is free to air in DVB on Atlantic Bird 5W. Does anyone have an initial tuning file for this satellite please?
In a similar case (for Astra and Hotbird), I have simply taken the transponder data from http://www.lyngsat.com, run them through a trivial script and put the result into my channels. conf file. So now I have one entry like this
-:12731:h:S13.0E:27500:0:0:0:0:30108:0:0:0
for every transponder. If I am not mistaken, VDR will fill in the rest automatically.
Carsten.
Le mardi 03 mai 2005 à 16:51 +0200, Carsten Koch a écrit :
-:12731:h:S13.0E:27500:0:0:0:0:30108:0:0:0
Where did you get the 30108?
My problem is that I'm not getting a lock with szap. I have made channel.conf files and all that in the past (years ago it seems...) with the -o vdr flag and everything. Forgotten it all and starting as a false debutant now =;-D
Tony
tony wrote:
Le mardi 03 mai 2005 à 16:51 +0200, Carsten Koch a écrit :
-:12731:h:S13.0E:27500:0:0:0:0:30108:0:0:0
Where did you get the 30108?
My script started with 30000 and added 1 for every transponder. I was hoping sid>=30000 would not match any existing service ID, so vdr would never overwrite these seed entries.
Carsten.
Hi,
Simon Baxter wrote:
I've just setup my WinTV NovaT on a new (2.2Ghz) shuttle PC and built the xine-plugin components.
I created a new channels.conf file with scan and ran up VDR
On some channels I get screens and screens of information like : FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126
I gather each specific XXXX number refers to capability needed on those specific channels??
any ideas?
Hhm, each of these locations checks, whether a PES packet starts with the byte sequence 00 00 01, and fails as the packets don't.
If you are using a recent VDR (1.3.20 and higher), please have a look at the attached patch. It fixes the so called class cPesAssembler.
Does the problem disappear if you record such a channel and then play the 001.vdr file directly with xine?
Can you provide me a sample recording (~ 5 MB)?
Bye.
I was using vdr-1.3.1, and getting those errors. I've just compiled 1.3.23 and don't ALTHOUGH......
I'm doing the testing via a DEBUG_OSD=1 compile and a 'shell' because I have a slow running X problem at the moment.
1) The problem _may_ not be happenning now in version 1.3.23, although until I resolve my slow x problem I can't be sure
2) The Makefile in 1.3.23 no longer has the tags for DEBUG_OSD. Has this now been removed? I added : ifdef DEBUG_OSD DEFINES += -DDEBUG_OSD NCURSESLIB = -lncurses endif
to the Makefile, but the OSD shell-text OSD doesn't startup when I start vdr now??? Has this been removed??
Thanks
Simon ----- Original Message ----- From: "Reinhard Nissl" rnissl@gmx.de To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Tuesday, May 03, 2005 10:06 PM Subject: Re: [vdr] xine-vdr NovaT "FIXME: xineDevice.c:1160"
Hi,
Simon Baxter wrote:
I've just setup my WinTV NovaT on a new (2.2Ghz) shuttle PC and built the xine-plugin components.
I created a new channels.conf file with scan and ran up VDR
On some channels I get screens and screens of information like : FIXME: xineDevice.c:1160 FIXME: xineDevice.c:970 FIXME: xineDevice.c:1126
I gather each specific XXXX number refers to capability needed on those specific channels??
any ideas?
Hhm, each of these locations checks, whether a PES packet starts with the byte sequence 00 00 01, and fails as the packets don't.
If you are using a recent VDR (1.3.20 and higher), please have a look at the attached patch. It fixes the so called class cPesAssembler.
Does the problem disappear if you record such a channel and then play the 001.vdr file directly with xine?
Can you provide me a sample recording (~ 5 MB)?
Bye.
Dipl.-Inform. (FH) Reinhard Nissl mailto:rnissl@gmx.de
--------------------------------------------------------------------------------
--- ../vdr-1.3.23-orig/device.c 2005-02-27 14:55:15.000000000 +0100 +++ device.c 2005-05-01 22:59:18.869069399 +0200 @@ -27,6 +27,7 @@ private: uint32_t tag; int length; int size;
- bool hasFragment; bool Realloc(int Size);
public: cPesAssembler(void); @@ -39,6 +40,7 @@ public: void Put(uchar c); void Put(const uchar *Data, int Length); bool IsPes(void);
- bool HasFragment(void); };
cPesAssembler::cPesAssembler(void) @@ -57,6 +59,12 @@ void cPesAssembler::Reset(void) { tag = 0xFFFFFFFF; length = 0;
- hasFragment = false;
+}
+bool cPesAssembler::HasFragment(void) +{
- return hasFragment || length > 0;
}
bool cPesAssembler::Realloc(int Size) @@ -67,6 +75,7 @@ bool cPesAssembler::Realloc(int Size) if (!data) { esyslog("ERROR: can't allocate memory for PES assembler"); length = 0;
hasFragment = false; size = 0; return false; }@@ -77,6 +86,7 @@ bool cPesAssembler::Realloc(int Size) void cPesAssembler::Put(uchar c) { if (!length) {
hasFragment = true;@@ -985,7 +997,7 @@ int cDevice::PlayPes(const uchar *Data, return 0; } int Result = 0;
- if (pesAssembler->Length()) {
- if (pesAssembler->HasFragment()) { // Make sure we have a complete PES header: while (pesAssembler->Length() < 6 && Length > 0) { pesAssembler->Put(*Data++);
--------------------------------------------------------------------------------
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--------------------------------------------------------------------------------
No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.3 - Release Date: 03/05/2005
Simon Baxter wrote:
I was using vdr-1.3.1, and getting those errors. I've just compiled 1.3.23 and don't ALTHOUGH......
I'm doing the testing via a DEBUG_OSD=1 compile and a 'shell' because I have a slow running X problem at the moment.
- The problem _may_ not be happenning now in version 1.3.23, although
until I resolve my slow x problem I can't be sure
- The Makefile in 1.3.23 no longer has the tags for DEBUG_OSD. Has
this now been removed? I added : ifdef DEBUG_OSD DEFINES += -DDEBUG_OSD NCURSESLIB = -lncurses endif
to the Makefile, but the OSD shell-text OSD doesn't startup when I start vdr now??? Has this been removed??
The OSD DEBUG has been removed for quite some time (after vdr-1.3.6 if I recall correctly). It has been replaced by a plugin called skincurses which is located in <vdr-dir>/PLUGINS/src.
André.
Thanks!
How do I use it?
I've tried :
[root@media vdr-1.3.23]# ./vdr -P'xine -r' -t TTY vdr: can't access terminal: TTY
----- Original Message ----- From: "André Weidemann" Andre.Weidemann@web.de To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Wednesday, May 04, 2005 10:11 AM Subject: Re: [vdr] xine-vdr NovaT "FIXME: xineDevice.c:1160"
Simon Baxter wrote:
I was using vdr-1.3.1, and getting those errors. I've just compiled 1.3.23 and don't ALTHOUGH......
I'm doing the testing via a DEBUG_OSD=1 compile and a 'shell' because I have a slow running X problem at the moment.
- The problem _may_ not be happenning now in version 1.3.23, although
until I resolve my slow x problem I can't be sure
- The Makefile in 1.3.23 no longer has the tags for DEBUG_OSD. Has this
now been removed? I added : ifdef DEBUG_OSD DEFINES += -DDEBUG_OSD NCURSESLIB = -lncurses endif
to the Makefile, but the OSD shell-text OSD doesn't startup when I start vdr now??? Has this been removed??
The OSD DEBUG has been removed for quite some time (after vdr-1.3.6 if I recall correctly). It has been replaced by a plugin called skincurses which is located in <vdr-dir>/PLUGINS/src.
André.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.3 - Release Date: 03/05/2005
got it - vdr -P'skincurses'
Seems to be stable and no of the FIXME errors.....
now to fix my slow X problem...
Thanks again ----- Original Message ----- From: "Simon Baxter" linuxtv@nzbaxters.com To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Wednesday, May 04, 2005 10:39 AM Subject: Re: [vdr] xine-vdr NovaT "FIXME: xineDevice.c:1160"
Thanks!
How do I use it?
I've tried :
[root@media vdr-1.3.23]# ./vdr -P'xine -r' -t TTY vdr: can't access terminal: TTY
----- Original Message ----- From: "André Weidemann" Andre.Weidemann@web.de To: "Klaus Schmidinger's VDR" vdr@linuxtv.org Sent: Wednesday, May 04, 2005 10:11 AM Subject: Re: [vdr] xine-vdr NovaT "FIXME: xineDevice.c:1160"
Simon Baxter wrote:
I was using vdr-1.3.1, and getting those errors. I've just compiled 1.3.23 and don't ALTHOUGH......
I'm doing the testing via a DEBUG_OSD=1 compile and a 'shell' because I have a slow running X problem at the moment.
- The problem _may_ not be happenning now in version 1.3.23, although
until I resolve my slow x problem I can't be sure
- The Makefile in 1.3.23 no longer has the tags for DEBUG_OSD. Has this
now been removed? I added : ifdef DEBUG_OSD DEFINES += -DDEBUG_OSD NCURSESLIB = -lncurses endif
to the Makefile, but the OSD shell-text OSD doesn't startup when I start vdr now??? Has this been removed??
The OSD DEBUG has been removed for quite some time (after vdr-1.3.6 if I recall correctly). It has been replaced by a plugin called skincurses which is located in <vdr-dir>/PLUGINS/src.
André.
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.308 / Virus Database: 266.11.3 - Release Date: 03/05/2005
_______________________________________________ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Simon Baxter wrote:
Thanks!
How do I use it?
I've tried :
[root@media vdr-1.3.23]# ./vdr -P'xine -r' -t TTY vdr: can't access terminal: TTY
The error probably occurs because you need to sepcify /dev/tty12 or something similar instead of TTY. Just for testing you don't need this I'd say. The TTY is only needed if you start vdr from a script and you need a terminal afterwards to be able to control it via keyboard.
For the skincurses plugin... I'd use -P skincurses on the command line...
André.
PS: this site is not yet complete... but it is always a good starting point: http://www.linuxtv.org/vdrwiki/index.php/Main_Page
PPS: please do not top-quote... makes it difficult to follow up
Can anyone send me their remote.conf for the Hauppauge Nova-T card, which uses the mini-din connected IR sensor?
Can this card be used under LIRC? Or do all the buttons work under the in-built sensor and DVB drivers?
Thanks
Simon
"Simon Baxter" linuxtv@nzbaxters.com writes:
Can anyone send me their remote.conf for the Hauppauge Nova-T card, which uses the mini-din connected IR sensor?
Mini-din? I have Nova-T and IR sensor is connected with 2.5 or 3.5 mm plug. It appears in /dev/input/event0 (uses modules input and evdev), but those are loaded at least for me automatically.
Can this card be used under LIRC? Or do all the buttons work under the in-built sensor and DVB drivers?
For mine all except power-butto work with vdr+remote plugin ok. Loading order of modules matter, if I load dvb-ttpci before dvb-ttpci-budget-ci remote does not work.
(Not answering what you asked, but answering still in hope this might help...)
-
André Weidemann -
Carsten Koch -
FAVRE Grégoire -
Guy Roussin -
Markku Tavasti -
Reinhard Nissl -
Simon Baxter -
tony