Re: [vdr] Switching time
I don't know if this helps but I'm using the xine plugin, not xinelibout. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API
Is ther a problem with vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup patch fom Reinhard Nilsl ? Could this patch be included in vdr-1.7.2 like S2API patch? yes, it will be great Goga ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Switching time
Hi Alex, Switching time with softdevice is great! I have tested all available soft output plugins but softdevice was the fastest regarding switching time. On my machine p4 2400 it is faster than my ff Card. I am using an skystar2 rev 2.6b with softdevice from cvs! HTH. halim ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
Attached is an updated version of the patch to make VDR use
the S2API. Dominik Strasser reported that he got log entries like
Dec 6 18:39:02 VDR vdr: [4102] ERROR: frontend 0: Das Argument ist ungültig
Dec 6 18:39:02 VDR kernel: DVB: adapter 0 frontend 1935763502 symbol rate 0
out of range (451875..723)
and I now also get
Dec 7 13:03:26 vdr2 vdr: [3441] ERROR: frontend 0: Invalid argument
Dec 7 13:03:26 vdr2 kernel: DVB: adapter 0 frontend 0 symbol rate 0 out of
range (500..4500)
when trying to tune to a DVB-S2 channel.
The attached patch logs the value put into the DTV_SYMBOL_RATE slot,
and it appears to be fine. Why the value falls back to 0 when tuning
is currently totally unclear (as is the large frontend value in Dominik's
case).
Any help in debugging this would be appreciated.
Note the comment in my initial posting about the patch to the driver required
for detecting DVB-S2 (or modifiy the line using FE_CAN_2ND_GEN_MODULATION in
cDvbDevice::cDvbDevice()).
Klaus
===
RCS file: ./RCS/CONTRIBUTORS
retrieving revision 2.17
diff -u -b -r2.17 ./CONTRIBUTORS
--- ./CONTRIBUTORS 2008/09/06 14:49:19 2.17
+++ ./CONTRIBUTORS 2008/12/06 11:24:12
@@ -2375,3 +2375,12 @@
Winfried Köhler [EMAIL PROTECTED]
for fixing wrong value for TableIdBAT in libsi/si.h
+
+Igor M. Liplianin [EMAIL PROTECTED]
+ for a patch that was used to convert VDR to the S2API driver API
+
+Niels Wagenaar [EMAIL PROTECTED]
+ for a patch that was used to convert VDR to the S2API driver API
+
+Edgar Hucek [EMAIL PROTECTED]
+ for a patch that was used to convert VDR to the S2API driver API
===
RCS file: ./RCS/HISTORY
retrieving revision 2.31
diff -u -b -r2.31 ./HISTORY
--- ./HISTORY 2008/09/14 13:45:45 2.31
+++ ./HISTORY 2008/12/07 10:51:20
@@ -5832,6 +5832,11 @@
- Removed unneeded include files linux/dvb/dmx.h und time.h from remux.h
(reported by Tobias Grimm).
-2008-09-14: Version 1.7.2
+2008-12-07: Version 1.7.2
- Added a note about 'Id' being obsolete to the description of cDevice::PlayAudio().
+- Switched to the new S2API driver API, which was decided to become the official
+ DVB API in the kernel (based on patches from Igor M. Liplianin, Niels Wagenaar
+ and Edgar Hucek).
+- The cDvbTuner::IsTunedTo() function now also checks the symbol rate in case of
+ DVB-S and DVB-C.
===
RCS file: ./RCS/channels.c
retrieving revision 2.3
diff -u -b -r2.3 ./channels.c
--- ./channels.c 2008/07/06 12:59:41 2.3
+++ ./channels.c 2008/12/06 15:45:34
@@ -21,114 +21,86 @@
// --- Channel Parameter Maps
const tChannelParameterMap InversionValues[] = {
- { 0, DVBFE_INVERSION_OFF, trNOOP(off) },
- { 1, DVBFE_INVERSION_ON, trNOOP(on) },
- { 999, DVBFE_INVERSION_AUTO },
+ { 0, INVERSION_OFF, trNOOP(off) },
+ { 1, INVERSION_ON, trNOOP(on) },
+ { 999, INVERSION_AUTO },
{ -1 }
};
const tChannelParameterMap BandwidthValues[] = {
- { 5, DVBFE_BANDWIDTH_5_MHZ, 5 MHz },
- { 6, DVBFE_BANDWIDTH_6_MHZ, 6 MHz },
- { 7, DVBFE_BANDWIDTH_7_MHZ, 7 MHz },
- { 8, DVBFE_BANDWIDTH_8_MHZ, 8 MHz },
- { 999, DVBFE_BANDWIDTH_AUTO },
+ { 6, 600, 6 MHz },
+ { 7, 700, 7 MHz },
+ { 8, 800, 8 MHz },
{ -1 }
};
const tChannelParameterMap CoderateValues[] = {
- { 0, DVBFE_FEC_NONE, trNOOP(none) },
- { 12, DVBFE_FEC_1_2, 1/2 },
- { 13, DVBFE_FEC_1_3, 1/3 },
- { 14, DVBFE_FEC_1_4, 1/4 },
- { 23, DVBFE_FEC_2_3, 2/3 },
- { 25, DVBFE_FEC_2_5, 2/5 },
- { 34, DVBFE_FEC_3_4, 3/4 },
- { 35, DVBFE_FEC_3_5, 3/5 },
- { 45, DVBFE_FEC_4_5, 4/5 },
- { 56, DVBFE_FEC_5_6, 5/6 },
- { 67, DVBFE_FEC_6_7, 6/7 },
- { 78, DVBFE_FEC_7_8, 7/8 },
- { 89, DVBFE_FEC_8_9, 8/9 },
- { 910, DVBFE_FEC_9_10, 9/10 },
- { 999, DVBFE_FEC_AUTO },
+ { 0, FEC_NONE, trNOOP(none) },
+ { 12, FEC_1_2, 1/2 },
+ { 23, FEC_2_3, 2/3 },
+ { 34, FEC_3_4, 3/4 },
+ { 35, FEC_3_5, 3/5 },
+ { 45, FEC_4_5, 4/5 },
+ { 56, FEC_5_6, 5/6 },
+ { 67, FEC_6_7, 6/7 },
+ { 78, FEC_7_8, 7/8 },
+ { 89, FEC_8_9, 8/9 },
+ { 910, FEC_9_10, 9/10 },
+ { 999, FEC_AUTO },
{ -1 }
};
const tChannelParameterMap ModulationValues[] = {
- { 0, DVBFE_MOD_NONE,trNOOP(none) },
- { 4, DVBFE_MOD_QAM4,QAM4 },
- { 16, DVBFE_MOD_QAM16, QAM16 },
- { 32, DVBFE_MOD_QAM32, QAM32 },
- { 64, DVBFE_MOD_QAM64, QAM64 },
- { 128, DVBFE_MOD_QAM128, QAM128 },
- { 256, DVBFE_MOD_QAM256, QAM256 },
- { 512, DVBFE_MOD_QAM512, QAM512 },
- {1024, DVBFE_MOD_QAM1024, QAM1024 },
- { 1, DVBFE_MOD_BPSK,BPSK },
- { 2, DVBFE_MOD_QPSK,QPSK },
- { 3, DVBFE_MOD_OQPSK, OQPSK },
- { 5, DVBFE_MOD_8PSK,8PSK },
- { 6, DVBFE_MOD_16APSK, 16APSK },
- { 7, DVBFE_MOD_32APSK, 32APSK },
- { 8, DVBFE_MOD_OFDM,
Re: [vdr] Falsche PTS im PES-Stream beim Spulen in Videoaufnahmen
Hi, Reinhard Nissl schrieb: I came across the same issue when I coded vdr-xine. My understanding of FF-cards is that they use PTS only to synchronize audio and video streams, and not to determine the absolute replay time. As a result the frames are simply output one after another according to their coded display duration. I just posted a related question on the VLC ML, maybe the cause of my problem is the same, that the PTS information does not represent the absolute position in the recording. Here is a copy: playing video files, recorded by VDR, results in strange values of the current position/length indicator on the standard VLC interface. So the indicator shows an offset of e.g. 10h. and a length of 10:45, although the whole recording only takes 45min. I uploaded a sample of 6 sec. to http://fabian-wolter.de/001.vdr (6MB), where the indicator shows 5:31:21 / 5:31:27 when the recording starts playing. Normally that doesn't bother me, since the slider works properly. It starts leftmost and ends rightmost. But now I want to use libvlc to play these files and I'm wondering where to get the right timing information to implement a slider on my interface. The libvlc_MediaPlayerTimeChanged event gives me the current position with the offset named above. Same with libvlc_media_player_get_length. Regards, Fabian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
On Sun, Dec 7, 2008 at 3:06 PM, Klaus Schmidinger [EMAIL PROTECTED] wrote: On 07.12.2008 13:21, Klaus Schmidinger wrote: Attached is an updated version of the patch to make VDR use the S2API. Dominik Strasser reported that he got log entries like Dec 6 18:39:02 VDR vdr: [4102] ERROR: frontend 0: Das Argument ist ungültig Dec 6 18:39:02 VDR kernel: DVB: adapter 0 frontend 1935763502 symbol rate 0 out of range (451875..723) and I now also get Dec 7 13:03:26 vdr2 vdr: [3441] ERROR: frontend 0: Invalid argument Dec 7 13:03:26 vdr2 kernel: DVB: adapter 0 frontend 0 symbol rate 0 out of range (500..4500) when trying to tune to a DVB-S2 channel. The attached patch logs the value put into the DTV_SYMBOL_RATE slot, and it appears to be fine. Why the value falls back to 0 when tuning is currently totally unclear (as is the large frontend value in Dominik's case). Any help in debugging this would be appreciated. Some more info: apparently the problem only happens if a DVB-S2 card (a TT-budget S2 3200 in my case) is (attempted to be) tuned to a DVB-S2 channel after the driver has been freshly loaded. Once the card has been tuned to a DVB-S channel, subsequent tuning to DVB-S2 channels works fine. That scenario works fine with scan-s2 utility. Now I'm unsure whether this is a VDR bug or a driver bug... Where is the origin of frontend value? I think its VDR internal and is not received from the driver... Klaus ___ 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 with S2API (update)
On 07.12.2008 18:40, gimli wrote: Hi Klaus, just one question. Do you also use a budget system ? If so, how do you watch TV with vdr 1.7.1 and later ;) since xineliboutput is completly broken with it. Currently I still have a FF DVB card for replaying, which, in the long run, will be replaced by an eHD card. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] OT: Alice homeTV and vdr
Dear list, can you please share your experiences of using Alice homeTV [3] with vdr. Some more information [4] and [5]. 1. How is the quality [1]? 2. Does it work with the iptv plugin [2]? If not, what are you using? Thanks a lot, Paul [1] http://gutenburger.de/index.php?option=com_contentview=articleid=569:hansenet-laesst-gratis-fernsehencatid=56:video-downloadItemid=76 (German) [2] http://www.saunalahti.fi/~rahrenbe/vdr/iptv/ [3] http://www.alice-dsl.de/kundencenter/export/de/residential/alice_hometv/uebersicht.html (German) [4] http://www.ip-phone-forum.de/showthread.php?t=168118 (German) [5] http://www.ard-digital.de/14028_1 (German) signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT: Alice homeTV and vdr
Hi, Paul Menzel schrieb: Dear list, can you please share your experiences of using Alice homeTV [3] with vdr. Some more information [4] and [5]. 1. How is the quality [1]? 2. Does it work with the iptv plugin [2]? If not, what are you using? In theory it should work with the iptv plugin. Alice is using usual IP-Multicast (MPEG-TS, H264, IGMP) to transmit the cannels. For Video on Demand they are using RTSP with MPEG-TS + H264. But you need an VLAN enabled network or you need to have 2 network cards, as the HomeTV is only available on a dedicated port on dsl-modem. I have not tired it out with VDR, I could watch HomeTV with VLC. Regards, Artem ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
