Re: [vdr] Translation question en -> fr
Hi, Another possibility in French would be "complet". In particular I would translate "full name" as "nom complet". Cheers, Chris Le 02/07/2017 à 15:31, Tobi a écrit : See changes of 2.3.7: - The option "Setup/Miscellaneous/Show channel names with source" can now be set to "type" or "full" to show either the type or the full name of the source (thanks to Martin Wache). On 02.07.2017 12:44, Bernard Jaulin wrote: Hello Franck, Thank you, but when this message did appear ? Regards, BJA. Le dim. 2 juil. 2017 à 12:40, fnu mailto:v...@auktion.hostingkunde.de>> a écrit : Hi Bernard, __ __ Klaus does translate this into german word "alles", "tout" in french. __ __ Cheers Frank __ __ *Von:*vdr [mailto:vdr-boun...@linuxtv.org <mailto:vdr-boun...@linuxtv.org>] *Im Auftrag von *Bernard Jaulin *Gesendet:* Sonntag, 2. Juli 2017 12:15 *An:* VDR Mailing List mailto:vdr@linuxtv.org>> *Betreff:* [vdr] Translation question en -> fr __ __ Hello, __ __ For a better translation, did someone can explain to me what is this msgid and the context. __ __ > msgid "full" __ __ Regards, __ __ BJA. __ __ __ __ __ __ ___ vdr mailing list vdr@linuxtv.org <mailto:vdr@linuxtv.org> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How setup VDR to import external EPG data (XMLTV file)
Hello i have got a rpi2 + dvb-t tuner that run under openelec 6 and VDR for the TV. This system work well and i would now import external EPG data... i read several thread about xmltv2vdr and it isn't so clear for me : - i was thinking of download xmltv file from internet (kazer.org for france) with a cron task - and use xmltv2vdr to import the downloaded file into VDR Is it possible to do like this ? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-2.0.6 crashes at recording start with divide error
On 12/10/14 16:42, Klaus Schmidinger wrote:
> On 12.10.2014 16:30, Chris Mayo wrote:
>> I occasionally see vdr crashing when a recording starts like this:
>>
>> kernel: traps: recording[352] trap divide error ip:4cfeff sp:7fc8e9523e00
>> error:0 in vdr[40+156000]
>> runvdr[300]: Floating point exception
>>
>> $ gdb /usr/bin/vdr
>> (gdb) disass /m 0x4cfeff
>>
>> 1514in remux.c
>> 0x004cfee6 <+870>:mov0x290(%rbx),%rsi
>> 0x004cfeed <+877>:xor%edx,%edx
>> 0x004cfeef <+879>:mov0x284(%rbx),%ecx
>> 0x004cfef5 <+885>:mov0xc(%rbx),%eax
>> 0x004cfefc <+892>:add0xc(%rsi),%ecx
>> 0x004cfeff <+895>:div%ecx
>> 0x004cff08 <+904>:mov%eax,%ecx
>>
>> Point to this in remux.c?
>> 1514: uint32_t Delta = ptsValues[0] / (framesPerPayloadUnit +
>> parser->IFrameTemporalReferenceOffset());
>
> This should fix it:
>
> --- remux.c 2014/03/08 15:10:24 2.75.1.5
> +++ remux.c 2014/04/13 13:59:21 2.75.1.6
> @@ -1511,7 +1511,12 @@
> for (int i = 0; i < numPtsValues; i++)
> ptsValues[i] = ptsValues[i + 1] - ptsValues[i];
> qsort(ptsValues, numPtsValues, sizeof(uint32_t),
> CmpUint32);
> - uint32_t Delta = ptsValues[0] / (framesPerPayloadUnit
> + parser->IFrameTemporalReferenceOffset());
> + int Div = framesPerPayloadUnit;
> + if (framesPerPayloadUnit > 1)
> + Div += parser->IFrameTemporalReferenceOffset();
> + if (Div <= 0)
> + Div = 1;
> + uint32_t Delta = ptsValues[0] / Div;
> // determine frame info:
> if (isVideo) {
>if (abs(Delta - 3600) <= 1)
>
> Klaus
>
Many thanks. Patch applied. Will take at least a few weeks to be confident of a
difference.
I guess I should have googled the line of code,
http://www.vdr-portal.de/board17-developer/board97-vdr-core/p1194836-frameratenerkennung-ab-version-2-0-6/
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-2.0.6 crashes at recording start with divide error
I occasionally see vdr crashing when a recording starts like this: kernel: traps: recording[352] trap divide error ip:4cfeff sp:7fc8e9523e00 error:0 in vdr[40+156000] runvdr[300]: Floating point exception $ gdb /usr/bin/vdr (gdb) disass /m 0x4cfeff 1514in remux.c 0x004cfee6 <+870>: mov0x290(%rbx),%rsi 0x004cfeed <+877>: xor%edx,%edx 0x004cfeef <+879>: mov0x284(%rbx),%ecx 0x004cfef5 <+885>: mov0xc(%rbx),%eax 0x004cfefc <+892>: add0xc(%rsi),%ecx 0x004cfeff <+895>: div%ecx 0x004cff08 <+904>: mov%eax,%ecx Point to this in remux.c? 1514: uint32_t Delta = ptsValues[0] / (framesPerPayloadUnit + parser->IFrameTemporalReferenceOffset()); I don't know how to make it happen. Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR2 ATSC audio channels
Solved. Used ChannelUpdate=2 in the setup.conf and VDR figured out the correct type, 0x81 in this case. -- _ Chris Florian |TXIO Corporation|www.txio.ca <http://www.txio.ca> | 1.416.414.6378 _ ___ 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
[vdr] VDR2 ATSC audio channels
Hello, I recently had a problem with the audio of a live ATSC TV stream from VDR to XBMC using vnsi. One of the vnsi developers identified the problem a patched vnsi with a work around (http://forum.xbmc.org/showthread.php?tid=160951). I am also experiencing the same problem with VDR recordings, but this time I was told that this had to be fixed at the VDR end of things. If I make a recording and check the .ts file with ffmpeg, it shows: Stream #0:0[0x21]: Video: mpeg2video (Main) ([2][0][0][0] / 0x0002), yuv420p, 1920x1080 [SAR 1:1 DAR 16:9], 17700 kb/s, 29.97 fps, 29.97 tbr, 90k tbn, 59.94 tbc Stream #0:1[0x24](eng): Audio: mp1 ([4][0][0][0] / 0x0004), 0 channels, s16 Stream #0:2[0x25](fre): Audio: mp3 ([4][0][0][0] / 0x0004), 0 channels, s16 But the streams should be AC3. My channels.conf for this channel looks like this: CBLT-DT Toronto HD;(null):509000:M10:A:0:49=2:52=eng@4,53=es@4;52=@106,53=@106:0:0:3:0:0:0 Not being an ATSC or mpegts expert...can anyone help? fedora 18 VDR 2.0.0 XBMC v13 alpha vnsi4 Hauppauge HVR-1600 -- _ Chris Florian |TXIO Corporation|www.txio.ca <http://www.txio.ca> | 1.416.414.6378 _ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] dvbhddevice Makefile missing $(LDFLAGS)
Been sitting on this for ages but in anticipation of 2.0: --- PLUGINS/src/dvbhddevice/Makefile.orig +++ PLUGINS/src/dvbhddevice/Makefile @@ -98,7 +98,7 @@ $(SOFILE): $(OBJS) libhdffcmd @$(MAKE) --no-print-directory -C libhdffcmd all - $(CXX) $(CXXFLAGS) -shared $(OBJS) libhdffcmd/libhdffcmd.a -o $@ + $(CXX) $(CXXFLAGS) $(LDFLAGS) -shared $(OBJS) libhdffcmd/libhdffcmd.a -o $@ install-lib: $(SOFILE) install -D $^ $(LIBDIR)/$^.$(APIVERSION) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] No output via xineliboutput with VDR 1.7.21
> Do you get the red "No Signal" text on black background? No, I get the "xine" splash screen instead. Sometimes with the VDR OSD on it... I am using xine-1.1, BTW. Perhaps this is relevant? > And as someone also suggested, make sure you have xineliboutput set as your > primary device in Settings/DVB. The value should be the amount of your > dvb devices + 1. OK, I'm assuming that you're talking about /etc/vdr/setup.conf here. And although I have PrimaryDVB = 2 in this file, I don't see how this can be seen as setting xineliboutput as my primary device. My xineliboutput configuration is: xineliboutput.Audio.Compression = 100 xineliboutput.Audio.Delay = 0 xineliboutput.Audio.Headphone = 0 xineliboutput.Audio.SoftwareVolumeControl = 0 xineliboutput.Audio.Speakers = Stereo 2.1 xineliboutput.Audio.Surround = 0 xineliboutput.Audio.Upmix = 0 xineliboutput.Audio.Visualization = goom xineliboutput.Audio.Visualization.GoomOpts = width=720,height=576,fps=25 xineliboutput.Decoder.PesBuffers = 250 Cheers, Chris P.S. Can you also CC any reply to me, please? Otherwise my mail client is going to start a new thread on the VDR list. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] No output via xineliboutput with VDR 1.7.21
> Please see the xineliboutput README for examples on using xine-ui with > xineliboutput. > Both vdr-sxfe and xine-ui can act as a front-end to xineliboutput. Not any more though, it would seem. Perhaps xineliboutput has not been maintained? Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No output via xineliboutput with VDR 1.7.21
> you must have an output "xineplug_inp_xvdr.so" then, you can play using > xine cmd line: > > xine xvdr://127.0.0.1:37890 FYI, I have been successfully using xineliboutput *for years* with VDR 1.6.x. The *only reason* I felt this worth reporting to the mailing list is because it has all stopped working after upgrading to VDR 1.7.x. YES, I have the xvdr plugin! $ ls -als /usr/local/lib/xine/plugins/1.29/*vdr* 460 -rwxr-xr-x 1 root root 463196 Nov 7 23:29 /usr/local/lib/xine/plugins/1.29/xineplug_inp_xvdr.so Geez! Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] No output via xineliboutput with VDR 1.7.21
> can you give output of this command's please? > > lsmod |grep dvb $ lsmod |grep dvb em28xx_dvb 16720 11 cxd2820r 22613 3 em28xx_dvb dvb_core 67728 2 em28xx_dvb,cxd2820r em28xx 66067 1 em28xx_dvb usbcore 94143 9 em28xx_dvb,em28xx,snd_usb_audio,uvcvideo,snd_usbmidi_lib,usbhid,uhci_hcd,ehci_hcd The adapter works fine with xine's native DVB plugin. (Provided VDR isn't already running, of course). > sudo ps auxww |grep vdr # ps auxww | grep vdr root 2484 0.0 0.0 5272 1372 ? S 20:30 0:00 /bin/bash /usr/sbin/runvdr vdr 2489 1.9 1.0 111368 22172 ? Sl 20:30 0:08 /usr/sbin/vdr --lirc --vfat --userdump -s vdr-shutdown.sh -P xineliboutput --local=none --remote=37890 -P remote -i /dev/input/dvb-nano-remote > sudo netstat -napt |grep vdr # netstat -napt |grep vdr tcp 0 0 0.0.0.0:6419 0.0.0.0:* LISTEN 2489/vdr tcp 0 0 0.0.0.0:37890 0.0.0.0:* LISTEN 2489/vdr tcp 0 0 127.0.0.1:37890 127.0.0.1:49042 ESTABLISHED 2489/vdr # netstat -napt |grep xine tcp 0 0 127.0.0.1:49124 127.0.0.1:37890 ESTABLISHED 5058/xine It all looks reasonable. I can even (sometimes) persuade elements of the OSD to appear in the xine-ui window by pressing buttons on my remote control. It's just that VDR doesn't appear to send any data. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] No output via xineliboutput with VDR 1.7.21
Hi, I have just tried installing VDR 1.7.21 (from Fedora RawHide), with the xineliboutput plugin from its git repository. I have managed to get xine to connect to VDR (I think - after I had added 127.0.0.1 to the allowed_hosts.conf file), but I am not receiving any output in the xine window. VDR seems to be processing events from my remote, and the channels all seem to have tuned in too - even the HD ones. But it's no good without either a picture or sound. Does anyone have any ideas, please? Thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVB-T2 tuning
> Here is what i did with 1.7 vdr. Yes, I know it works in vdr 1.7. And xine's DVB plugin tunes into the HD channels here too. The problem is that Fedora uses vdr 1.6, and this version doesn't work. So obviously the tuning code in vdr 1.7 is different somehow... Thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVB-T2 tuning
> I'm not aware of any DVB-T2 specific code in VDR 1.7.x AFAIK, DVB-T2 at least needs support for QAM_256. I don't think the DVB-T tuner in VDR 1.6 supports anything better than QAM_64, so adding QAM_256 would definitely be a start. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] DVB-T2 tuning
Hi, I'm assuming that VDR-1.7.x can tune into DVB-T2 channels, but it seems that Fedora 16 will still be using VDR-1.6.x. This is probably because VDR-1.7 is a development version, but I'd like to be able to use my PCTV 290e adapter in Fedora. So it looks like the DVB-T2 tuning parameters (QAM_256 support?) are going to need patching from 1.7 into 1.6. Can anyone point out the relevant code, please? I suspect that asking first will be faster... ;-). Thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xine with new AAC LATM support
Hi all, The AAC LATM patches have finally been merged to the xine-lib 1.2 branch. It still doesn't configure correctly for me on Fedora 15, but please feel free to test it out. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xine with new AAC LATM support
> Have your patches been merged yet? When will they be merged into the > xine-lib-1.2 tree? I don't know anyone still using 1.1 since 1.2 is > where the vdpau dev happens. Yes, the patches have now all been merged into the xine-lib tree: http://hg.debian.org/hg/xine-lib/xine-lib I suspect that the patches will also arrive in the 1.2 tree at some later point. However, xine-lib-1.2 doesn't build for me on Fedora 15 so I can't test it myself. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xine with new AAC LATM support
Hi, Just in case anyone is interested: There has been a sudden spike in xine development (1.1.19 branch), and AAC LATM audio should now be working with MPEG-TS streams. You will also need to be using FFmpeg >= 0.7. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.20 - Incorrect Progress Bar Times for Radio Programmes
On 27/08/11 15:24, Klaus Schmidinger wrote:
> On 27.08.2011 15:35, Chris Mayo wrote:
>> Progress bar display shows excessive times for radio programmes (no
>> video).
>>
>> A recording of about 5 minutes starts at 5:22:13 and ends at
>> 27404:47:54. The actual recording is fine. Recording is from BBC Radio 3
>> using DVB-T. ffmpeg -i shows:
>>
>> Input #0, mpegts, from '1.ts':
>>Duration: 00:05:06.12, start: 38666.622211, bitrate: 225 kb/s
>>Program 132
>> Stream #0.0[0x1b6](eng): Audio: mp2, 48000 Hz, stereo, s16, 192 kb/s
>>
>> I see the same playing with dvbhddevice or xineliboutput.
>>
>> Recordings made with previous versions of vdr (including 1.7.19 with
>> suggested reversion to 1.7.18 recording code) display correct times
>> playing with 1.7.20.
>
> Please try this patch:
>
> --- remux.c 2011/08/20 09:07:26 2.59
> +++ remux.c 2011/08/27 14:20:18
> @@ -840,7 +840,7 @@
> return Processed; // flush everything before this
> new payload
> if (framesPerSecond <= 0.0) {
> // frame rate unknown, so collect a sequence of PTS
> values:
> -if (numPtsValues < MaxPtsValues && numIFrames < 2)
> { // collect a sequence containing at least two I-frames
> +if (numPtsValues < 2 || numPtsValues < MaxPtsValues
> && numIFrames < 2) { // collect a sequence containing at least two I-frames
> const uchar *Pes = Data + TsPayloadOffset(Data);
> if (numIFrames && PesHasPts(Pes)) {
>ptsValues[numPtsValues] = PesGetPts(Pes);
>
>
> Apparently it got only a single PTS value and then was
> unable to calculate a difference.
> This patch fixed it for me (on the German radio channel
> ANTENNE BAYERN, which also showed the effect you reported).
>
> Klaus
>
That's fixed it for me too. Many thanks.
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.7.20 - Incorrect Progress Bar Times for Radio Programmes
Progress bar display shows excessive times for radio programmes (no video). A recording of about 5 minutes starts at 5:22:13 and ends at 27404:47:54. The actual recording is fine. Recording is from BBC Radio 3 using DVB-T. ffmpeg -i shows: Input #0, mpegts, from '1.ts': Duration: 00:05:06.12, start: 38666.622211, bitrate: 225 kb/s Program 132 Stream #0.0[0x1b6](eng): Audio: mp2, 48000 Hz, stereo, s16, 192 kb/s I see the same playing with dvbhddevice or xineliboutput. Recordings made with previous versions of vdr (including 1.7.19 with suggested reversion to 1.7.18 recording code) display correct times playing with 1.7.20. Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Trying to understand MPEG-TS (PMT, PES etc)
Hi, I am digging into DVB streams and TS demuxing, and I was wondering: is the PMT the *only* (reasonable) way to determine which codec a given PES is using, please? The TS demuxing code that I am reading (*cough* xine's) seems to have the idea that if it receives an audio or video PES with a PID that it hasn't seen before then it can "autodetect" the stream (somehow?!). But if it has to wait for the next PMT anyway to determine which codec to use then I'm not sure that I understand the point. Can anyone advise, please? My research into MPEG-TS has only revealed the following, with regards to PMTs: "Each elementary stream is labeled with a stream_type value." http://en.wikipedia.org/wiki/MPEG_transport_stream#PMT Thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FreeviewHD success with Nanostick 290e
> The signal from my aerial goes through an amplifier to another amplifier with four outputs! > I could probably do with a new aerial!! Interesting, it hadn't occurred to me to use an amplifier. Although the HD MUXs are all broadcasting at low power at the moment until Digital Switch-Over is finished, so it's possible that this problem will sort itself out then. But right now, it looks like my splitters degrade the HD signal to the point where the tuner refuses to lock. Maybe I could buy better splitters, or maybe putting splitters on coaxial cables is not as "plug and play" as I'd supposed and my tangled pile of wires was generating interference. One other point: your amplifier arrangement seems rather sophisticated. Are you *sure* it's sending the same amplified signal to each of its four outputs? This might explain why your 290e can't find the SD MUXs. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FreeviewHD success with Nanostick 290e
Laz, I've finally managed to tune my 290e in as well. I have discovered that I need to remove all of the 2-way splitters that I'd been using to connect everything up to the wall socket, and then w_scan and scandvb can find the HD signal. But my version of ffmpeg (0.6.3) is struggling to decode the stream and so I'm not getting any sound. The pictures are OK, though. So maybe it's just that this PC is slightly underpowered? (2x2.66GHz P4 Xeons with HT enabled). I'll try using a beefier machine tomorrow. And if I'm still getting a HD signal tomorrow, I'll know that my 2-way splitters really are the problem too :-). Although the loss of the splitters will be a problem in the long-term, because now I'm limited to only one DVB-T/T2 receiver. One problem at a time... Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] Compile fix for eepg-0.0.3 with g++ 4.6
Hi,
This patch fixes compilation of the eepg-0.0.3 plugin with g++ 4.6:
--- eepg.c.orig 2009-04-30 13:24:57.0 +0100
+++ eepg.c 2011-08-13 23:22:25.0 +0100
@@ -2684,7 +2684,7 @@
class cEIT2:public SI::EIT
{
public:
-cEIT2 (cSchedules::cSchedules * Schedules, int Source, u_char Tid, const
u_char * Data,
+cEIT2 (cSchedules * Schedules, int Source, u_char Tid, const u_char * Data,
bool OnlyRunningStatus = false);
// originally from libdtv, Copyright Rolf Hakenes
@@ -2773,7 +2773,7 @@
}
#endif /* NOEPG */
- cEIT2::cEIT2 (cSchedules::cSchedules * Schedules, int Source, u_char Tid,
const u_char * Data, bool OnlyRunningStatus)
+ cEIT2::cEIT2 (cSchedules * Schedules, int Source, u_char Tid, const u_char *
Data, bool OnlyRunningStatus)
: SI::EIT (Data, false) {
if (!CheckCRCAndParse ())
return;
Cheers,
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FreeviewHD channels.conf OK for xine, but not for VDR
Now xine isn't tuning into the HD channels again either. Maybe it's a problem with the transmitter, but I'm thinking that the DVB userspace doesn't have enough support for DVB-T2 yet. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] FreeviewHD channels.conf OK for xine, but not for VDR
Using scandvb with the "-o vdr" parameter is failing, but without it I get the following lines: BBC HD:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:17472 BBC One HD:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:17540 ITV1 HD:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:0:0:17604 Channel 4 HD:55400:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_AUTO:QAM_256:T Interesting. So xine is now receiving the stream via its DVB plugin, although it is also choking on the H.264 decoding. Still no luck getting the adapter's remote control working. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Failing to tune in Freeview HD channels
Hi, My 209e has arrived and is giving me all the normal Freeview channels. However, I'm unable to tune it into the HD ones. According to this site, the HD channels are all available on a separate MUX: http://www.ukfree.tv/txdetail.php?a=TQ339712 256QAM 32k 2/3 40Mb/s DVB-T2 MPEG4 50 BBC One HD (UK service without regions), 51 ITV 1 HD (ITV London), 52 Channel 4 HD London ads, 54 BBC HD, • as a digital multiplex transmitted on frequency C31 (554.0MHz) So I tried adding a new line to the uk-CrystalPalace file from dvb-apps: T 55400 8MHz 2/3 NONE QAM256 32k 1/32 NONE However, scandvb rejects the "32k" part and still refuses to tune in, although I do get the PIDs: 0x 0x4440: pmt_pid 0x0064 BBC -- BBC HD (running) 0x 0x44c4: pmt_pid 0x00c8 ITV -- ITV1 HD (running) 0x 0x4500: pmt_pid 0x012c CHANNEL FOUR -- Channel 4 HD (running) 0x 0x4484: pmt_pid 0x19c8 BBC -- BBC One HD (running) So it looks like I'm going to have to create entries in my channels.conf file manually. Does anyone have a working one that s/he could share, please? Thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] UK FreeviewHD and VDR
> I haven't pushed it upstream to Klaus, I think the preferable solution > is to do it as a plugin - search for the eepg plugin which incorporates > the parsing code. OK, thanks. Fedora 15 is still using VDR 1.6.x but the plugin looks small enough that I'm hoping it will work anyway :-). BTW, I see that eepg.c is using sscanf() with GNU-specific "%a[range]" tokens. Wouldn't it be more practical to use "%m[range]" tokens instead, c.f. the man page for sscanf from glibc: Since version 2.7, glibc also provides the m modifier for the same pur‐ pose as the a modifier. The m modifier has the following advantages: * It may also be applied to %c conversion specifiers (e.g., %3mc). * It avoids ambiguity with respect to the %a floating-point conversion specifier (and is unaffected by gcc -std=c99 etc.) * It is specified in the upcoming revision of the POSIX.1 standard. Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] UK FreeviewHD and VDR
Hi, I currently use VDR to watch Freeview in the UK, and it works great with a Hauppauge NOVA-T-USB2 adapter. However, this adapter isn't compatible with DVB-T2 and so I've now ordered a nanoStick T2 290e and have upgraded to the Linux 3.0.1 kernel in eager anticipation. My ultimate goal is to use VDR to watch FreeviewHD, exactly as I've already been using it to watch Freeview, except that I understand that the EPG for the HD channels has been compressed using proprietary Huffman tables. I've already found this web site: http://www.rst38.org.uk/vdr/ The patch here for VDR (with separate "drop in" files freesat.t1 and freesat.t2) looks interesting, and would seem to allow VDR to read the compressed EPG in a transparent way. However, it has obviously not been merged to VDR in over 2 years, which would suggest that the VDR developers have rejected it for some reason. Could someone tell me what the "recommended" approach is for parsing a Huffman-compressed EPG with VDR please? I suspect that I can integrate this patch into VDR manually, but this isn't a viable long-term solution. Thanks for any advice, Cheers, Chris P.S. Yes, I know that I am assuming that FreeSat and FreeviewHD are using the same proprietary Huffman tables. But I'm also under the impression that this assumption is not a bad one. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-1.7.18 with S2-6400 OSD oops
I'm getting a repeated (but not frequent or reproducible) oops that occurs when the OSD is already displayed and I do more OSD operations (quickly?). Recently the oopses have been written to syslog (because of some of the newer patches or firmware?) and I have attached one. This is my current set-up (I have had these oops all my time with the S2-6400 but this matches the attachment). Apologies if the problem is because of the way I have got things working. HW: 2 x Nova DVB-T 1 x S2-6400 connected to TV with HDMI SW: kernel: gentoo-sources-2.6.38-r6 but media drivers from (taken 20110419): http://www.aregel.de/file_download/6/linux-media.tar.bz2 plus the following patches (should be all the saa716x(_ff) ones) from http://powarman.dyndns.org/hgwebdir.cgi/v4l-dvb-saa716x/: 4475123e9fc6 e709142bc88b 6fbf3d86c62b e93c08705779 74e384b3b0aa e52e433285eb 5b3696587ffc 86ecc785a1d2 1d34d58f281c firmware: dvb-ttpremium-st7109-01_v0_2_11.zip dvb-ttpremium-fpga-01_v1_08.zip dvb-ttpremium-loader-01_v1_03.zip dvb-ttpci-01.fw-fb2624 vdr-1.7.18 dvbhddevice changeset: http://powarman.dyndns.org/hgwebdir.cgi/dvbhddevice/rev/fb6b1beedb72 Thanks for reading. Chris kernel: BUG: unable to handle kernel paging request at 7fef908c5160 kernel: IP: [] saa716x_phi_write+0x13/0x30 [saa716x_core] kernel: PGD 37c3d067 PUD 37c3a067 PMD 0 kernel: Oops: [#1] SMP kernel: last sysfs file: /sys/devices/pci:00/:00:0a.0/host0/target0:0:0/0:0:0:0/block/sda/dev kernel: CPU 0 kernel: Modules linked in: it87 hwmon_vid iptable_nat nf_nat nf_conntrack_ipv4 nf_defrag_ipv4 iptable_filter ipt_addrtype xt_NFQUEUE xt_conntrack nf_conntrack ip_tables x_tables snd_pcm_oss snd_mixer_oss isl6423 stv6110x stv090x snd_hda_codec_hdmi snd_hda_codec_realtek l64781 ir_lirc_codec snd_hda_intel tda1004x lirc_dev snd_hda_codec ir_sony_decoder budget snd_pcm ir_jvc_decoder ir_rc6_decoder rc_hauppauge radeon budget_ci ir_rc5_decoder ttm saa716x_ff drm_kms_helper budget_core snd_timer ir_nec_decoder snd saa7146 ttpci_eeprom rc_core saa716x_core drm dvb_core r8169 k8temp mii snd_page_alloc forcedeth i2c_nforce2 kernel: kernel: Pid: 2225, comm: vdr Tainted: GW 2.6.38-gentoo-r6 #1 kernel: RIP: 0010:[] [] saa716x_phi_write+0x13/0x30 [saa716x_core] kernel: RSP: :880037c2fd50 EFLAGS: 00010246 kernel: RAX: RBX: 88003d5a6000 RCX: 0016 kernel: RDX: 7fef908c5160 RSI: 000201a0 RDI: 88003c0e4000 kernel: RBP: 880037c2fdf8 R08: R09: kernel: R10: R11: dead00200200 R12: 88003d5a63a8 kernel: R13: 88003c0e4000 R14: 880037c2fd68 R15: 88003d5a6200 kernel: FS: 7fef99201720() GS:88003fc0() knlGS: kernel: CS: 0010 DS: ES: CR0: 8005003b kernel: CR2: 7fef908c5160 CR3: 37c3c000 CR4: 06f0 kernel: DR0: DR1: DR2: kernel: DR3: DR6: 0ff0 DR7: 0400 kernel: Process vdr (pid: 2225, threadinfo 880037c2e000, task 88003e11a150) kernel: Stack: kernel: a0132d78 00f9 88003e11a150 kernel: 88003e11a150 810580b0 880037c2fd80 880037c2fd80 kernel: 002f c0206fa2 7fffda003940 kernel: Call Trace: kernel: [] ? dvb_osd_ioctl+0x198/0x430 [saa716x_ff] kernel: [] ? autoremove_wake_function+0x0/0x30 kernel: [] ? dvb_usercopy+0xc3/0x1c0 [dvb_core] kernel: [] ? dvb_osd_ioctl+0x0/0x430 [saa716x_ff] kernel: [] ? cp_new_stat+0xe7/0x100 kernel: [] ? dvb_generic_ioctl+0x30/0x40 [dvb_core] kernel: [] ? do_vfs_ioctl+0x9c/0x560 kernel: [] ? sys_newstat+0x31/0x50 kernel: [] ? sys_ioctl+0x49/0x80 kernel: [] ? system_call_fastpath+0x16/0x1b kernel: Code: f0 00 00 48 8b 57 20 66 b8 2a 00 89 82 3c f0 00 00 30 c0 c3 0f 1f 40 00 85 c9 7e 27 81 c6 00 00 02 00 31 c0 0f 1f 40 00 4c 63 c0 <46> 8b 0c 02 41 89 f0 4c 03 47 20 45 89 08 83 c0 04 83 c6 04 39 kernel: RIP [] saa716x_phi_write+0x13/0x30 [saa716x_core] kernel: RSP kernel: CR2: 7fef908c5160 kernel: ---[ end trace a24157b3e9a22525 ]--- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] rotor plugin puzzling question
Hello,
ACK: this was clearly a bug ;-)
marti...@embl.de a écrit :
Is it just me or the newly released rotor plugin for vdr 1.7.9 needs the
following patch to the plugin itself in order to run (although it compiles
fine without it)
If the author reads these lines I would love to know why...
--- rotor.c.old 2006-06-14 23:44:27.0 +0200
+++ rotor.c 2006-06-14 23:46:43.0 +0200
@@ -96,7 +96,8 @@
continue;
if ((diseqc=Diseqcs.Get(source->Code(),12000,'h')) ||
(diseqc=Diseqcs.Get(source->Code(),12000,'v')) ||
(diseqc=Diseqcs.Get(source->Code(),12000,'l')) ||
(diseqc=Diseqcs.Get(source->Code(),12000,'r')))
{
- char *c=strdup(diseqc->Commands());
+ char *commandstring=strdup(diseqc->Commands());
+ char *c=commandstring;
while (c = strchr(c, '['))
{
char *e = strchr(++c, ']');
@@ -131,7 +132,7 @@
break;
}
}
- free(c);
+ free(commandstring);
I am not the author (nor even a user) but you are absolutely right.
You must free the pointer as returned by strdup; not one that you have
modified or incremented :(
So you need to keep a virgin copy of the pointer as you have done.
Cheers,
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xbmc-pvr (was - HD clients for vdr)
On Thu, Aug 20, 2009 at 6:15 PM, Goga777 wrote: >> >> eventually abandon xinelib. At the moment I just press a button on my >> >> remote to switch between xbmc and vdr-sxfe so I can have the best of >> >> both worlds. > > would you like to describe more details your installation - xbmc and vdr > please > > Goga > Hi. I'm trying to do just that. A separate install for vdr and xbmc. No integration for me now, since the plugins functionality is lost. A few methods are described here - http://www.xbmc.org/forum/showthread.php?t=47560. Perhaps Magnus can say for sure what method he uses. Cheers Cris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can't compile VDR
On Thu, Jan 15, 2009 at 2:50 AM, Chris Silva <2manybi...@gmail.com> wrote: > > Hi. > > Thanks for the help. Installing things from memory can get you into trouble. > > After writing the mail, read my notes and found the error... > > A simple > cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler.h > /usr/local/src/v4l-dvb/linux/include/linux/ > or > cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler.h > /usr/local/src/s2-liplianin/linux/include/linux/ > > solves it. > > Sorry for that. > > Now i'm having another error: > > etype2 -I/usr/local/src/s2-liplianin/linux/include tools.c > tools.c: In member function âssize_t cUnbufferedFile::Write(const > void*, size_t)â: > tools.c:1611: error: no matching function for call to âmin(long > unsigned int, off_t)â > make: *** [tools.o] Error 1 > > It seems to be caused by s2-liplianin drivers. > > Gonna try v4l-dvb. BTW, which repo is most up-to-date concerning > S2-3200 card? v4l-dvb or s2-liplianin? > > Thanks. > Well... VDR 1.7.0 compiles against v4l-dvb. VDR 1.7.3 still gives the error above. Any help is welcome. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can't compile VDR
On Thu, Jan 15, 2009 at 12:45 AM, user. vdr wrote: > On Wed, Jan 14, 2009 at 3:41 PM, Chris Silva <2manybi...@gmail.com> wrote: >> I'm having problems compiling VDR 1.7.0 and 1.7.3. >> >> This is the error: >> >> /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28: >> error: linux/compiler.h: No such file or directory >> In file included from >> /usr/local/src/s2-liplianin/linux/include/linux/videodev.h:16, >> from dvbdevice.c:13: > > Starting with the first error, try this: > cp /usr/src/linux/include/linux/compiler.h > /usr/local/src/s2-liplianin/linux/include/linux Hi. Thanks for the help. Installing things from memory can get you into trouble. After writing the mail, read my notes and found the error... A simple cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler.h /usr/local/src/v4l-dvb/linux/include/linux/ or cp /usr/src/linux-headers-$(uname -r)/include/linux/compiler.h /usr/local/src/s2-liplianin/linux/include/linux/ solves it. Sorry for that. Now i'm having another error: etype2 -I/usr/local/src/s2-liplianin/linux/include tools.c tools.c: In member function âssize_t cUnbufferedFile::Write(const void*, size_t)â: tools.c:1611: error: no matching function for call to âmin(long unsigned int, off_t)â make: *** [tools.o] Error 1 It seems to be caused by s2-liplianin drivers. Gonna try v4l-dvb. BTW, which repo is most up-to-date concerning S2-3200 card? v4l-dvb or s2-liplianin? Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minimal VDR install
On Mon, Jan 12, 2009 at 8:34 PM, Magnus Hörlin wrote: > Chris Silva wrote: >> Hi, folks. >> >> My current vdr is instaled over "normal" ubuntu desktop since forever. >> Now I want to try something similar starting with ubuntu server and >> reducing installed packages to the minimum. >> >> I found a similar ideia at this link: >> http://kuparinen.org/martti/comp/vdr/vdr.html >> >> Now for the questions: >> >> - Anyone with similar approach? >> - What is the minimum xorg needed? >> - Recommended settings? >> >> The ideia is to have a lightweight system installed on a usb pen >> (almost all files are read only, so no problem) and add one or more >> HDD drives to perform the recording. Those drivers will only work when >> a recording is scheduled. Thus reducing noise to the minimum. >> Currently I have almost no dB coming from my vdr box, except for the >> disks. >> >> I need to take in account other applications xorg needs. Like xine, >> mplyer, whatever. >> >> I really want to end up with a minimal/no noise fully working system. >> >> Thanks. >> >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr >> >> > I run "minimal" diskless ubuntu setups on a vdr server and three > clients. The basic "cli" install of ubuntu desktop is <600MB and on the > server there's not very much to add, just what's needed to compile vdr > and an nfs server. On the clients I just install xinit and xorg-driver > plus what's needed to compile xine. Then I start X with startx and > vdr-sxfe/xbmc/performous with the remote using .xinitrc/irexec. No gdm > or window manager, except for on my desktop client. And with a picoPSU > the clients run at <30W so they're silent all right. The server with > three hdd's and raid5 use a bit more but it's hidden away in the attic > so I can't hear it anyway. > I usually start by installing the latest version of ubuntu on one > computer and then duplicate that directory for every client. Then it's > just to boot that install for every client and add the rest of the > packages needed for that hardware (I have one intel, one nvidia and one > amd client so I can follow their respective X driver progress). > /Magnus H > Ubuntu desktop under <600MB? My standard Ubuntu install uses more than 1Gb. Do you have a non standard install procedure? Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Can't compile VDR
Hi. I'm having problems compiling VDR 1.7.0 and 1.7.3. This is the error: /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:64:28: error: linux/compiler.h: No such file or directory In file included from /usr/local/src/s2-liplianin/linux/include/linux/videodev.h:16, from dvbdevice.c:13: /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:560: error: field '__user' has incomplete type /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:560: error: expected ';' before '*' token /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:567: error: expected ';' before '*' token /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:569: error: variable or field '__user' declared void /usr/local/src/s2-liplianin/linux/include/linux/videodev2.h:569: error: expected ';' before '*' token In file included from dvbdevice.c:13: /usr/local/src/s2-liplianin/linux/include/linux/videodev.h:148: error: expected ';' before '*' token In file included from dvbdevice.c:17: /usr/local/src/s2-liplianin/linux/include/linux/dvb/video.h:162: error: expected ';' before '*' token /usr/local/src/s2-liplianin/linux/include/linux/dvb/video.h:195: error: expected ';' before '*' token dvbdevice.c: In member function 'virtual void cDvbDevice::StillPicture(const uchar*, int)': dvbdevice.c:1299: error: too many initializers for 'video_still_picture' dvbdevice.c:1299: error: invalid conversion from 'char*' to 'int32_t' dvbdevice.c:1305: error: too many initializers for 'video_still_picture' dvbdevice.c:1305: error: invalid conversion from 'char*' to 'int32_t' make: *** [dvbdevice.o] Error 1 Same error happens with s2-liplianin *and* v4l-dvb, with latest revisions. Tried googling for it, but no solution... Any thoughts? Thanks ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] OT question
On Mon, Jan 12, 2009 at 9:46 PM, Sascha Vogt wrote: > Hi Lucian, > > Lucian Muresan wrote: >> Sascha Vogt wrote: >>> Hi Lauri, >>> >>> Lauri Tischler wrote: Sascha Vogt wrote: > as my hardware is shipping (went for the ASUS M2N78Pro, GeForce 8300 > with an Athlon X2 4850e, hopefully that'll work with VDPAU and HD > videos) Couldn't find M2N78Pro, do you mean M3N78PRO ? >>> Sorry, you're right, meant the M3N78Pro. >> >> Does this board have at least headers for a parallel printer port? I >> can't find a hi-res picture of it, and docs do not mention it, so I fear >> I couldn't use my graphical VFD if I where to decide on this board in >> favour of some 8200-based still in ATX form factor. > Nope, sorry, I can't find any parallel ports on the port. There is an > internal COM Port available. I guess you'd need an USB<->parallel converter. > > Greetings > -Sascha- Or a COM < - > LPT converter and forget the USB drivers. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Minimal VDR install
Hi, folks. My current vdr is instaled over "normal" ubuntu desktop since forever. Now I want to try something similar starting with ubuntu server and reducing installed packages to the minimum. I found a similar ideia at this link: http://kuparinen.org/martti/comp/vdr/vdr.html Now for the questions: - Anyone with similar approach? - What is the minimum xorg needed? - Recommended settings? The ideia is to have a lightweight system installed on a usb pen (almost all files are read only, so no problem) and add one or more HDD drives to perform the recording. Those drivers will only work when a recording is scheduled. Thus reducing noise to the minimum. Currently I have almost no dB coming from my vdr box, except for the disks. I need to take in account other applications xorg needs. Like xine, mplyer, whatever. I really want to end up with a minimal/no noise fully working system. Thanks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] New Video Decode and Presentation API from NVidia
On Sun, Dec 14, 2008 at 3:18 PM, Gerald Dachs wrote: > Am Sun, 14 Dec 2008 16:55:52 +0200 > schrieb Lauri Tischler : > >> Andrew Herron wrote: >> > Hi, >> > >> > This ASUS board would be suitable; >> > >> > http://www.asus.com/products.aspx?modelmenu=1&model=2579&l1=3&l2=11&l3=812&l4=0 >> >> Too small, not enough pci-slots, minimum three pci-slots needed. >> Four or five pci-slots would be nice. > > And wrong cpu, I think I will buy this one: > http://www.phoronix.com/scan.php?page=article&item=nvidia_8200_mobos&num=3 > If I would need anyway a graphics card, then a big cooler would only > block a pci-e slot. The cpu socket is more near to the back side of the > motherboard than on many other mainboards. So I would get more space > between the cpu cooler and the cd rom drive in my S16T case. > > Gerald > Hi. I was thinking on getting this one: Gigabyte GA-E7AUM-DS2H with a VDPAU working GeForce 9400 integrated onboard. But the problem remains. I need at least 3 PCI slots. So, any suggestions on other boards with VDPAU *supported* chips? Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] HELP: Waiting for EPG in vdr-1.5.x
Hi everybody, I have a Hauppauge Nova-T500 DVB-Tand a TT fullfeature output DVB-S. I have tried everything that I know to get EPG but without success. I am using ubuntu 7.10, vdr-1.5.x and installed vdradmin-am 3.61 as well as xxv 1.10. I use a few plugins too. I live in Finland, any advice will be very much welcomed. regards, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Waiting for EPG in vdr-1.5x
Hi everybody, I have a Hauppauge Nova-T500 DVB-Tand a TT fullfeature output DVB-S. I have tried everything that I know to get EPG but without success. I am using ubuntu 7.10, vdr-1.5.x and installed vdradmin-am 3.61 as well as xxv 1.10. I use a few plugins too. I live in Finland, any advice will be very much welcomed. regards, Chris -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
Hi, No, i vote to wait for the DVD-S2 and maybe if Klaus can integrate H.264. regards, Chris On Sun, 2008-02-03 at 11:17 +0100, Klaus Schmidinger wrote: > There has been some controversy about my recent decision to > move forward and require the "multiproto" driver for VDR in > the developer version. It is also currently rather unclear > whether the current PES recording format can be kept to handle > HDTV, or whether it would make sense (or even be feasible) > to switch to TS (as suggested by the people from RMM). > > In order to take the edge of this, I was wondering if it would > make sense to revoke the switch to the "multiproto" driver and > go straight towards a stable version 1.6.0 with what is now in > version 1.5.14. This should satisfy all those who are eagerly awaiting > a new stable version, without forcing them to make the driver switch > now. > > If we decide to go that way, I would release a version 1.5.15 with > what could become the new stable, wait until like the end of the month > to see whether it still needs some minor fixes, and call it 1.6.0 then. > I know there are still some patches out there that some would expect > to go into the next stable version, but I actually want to prepare VDR > for HDTV before looking into these patches. > > So, here's the straw poll: > >Should there be a stable version 1.6.0 now, based on what's in >version 1.5.14, but without DVB-S2 or even H.264 support? > > Yes or No? > > 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] HDTV - 2B or not 2B
Hi Tony Grant wrote: > Has anyone tried VGA out at 1600x1050 on a FullHD (Sony Bravia for > example)? If so what does it look like. I've used a PC connected to a 40" Bravia via DVI and it was pretty damn good. If you sat far enough away you could use it comfortably as a monitor. Up close and the contrast on text would probably melt your retinas ;) Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xvid format
I have just started using vdr and the web based interface and I am very happy with the results. I wanted to ask what is the easiest way to get vdr recordings into xvid format? Cheers, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] no sound on output of TT-premium C-2300
How emberrasing, it wasn't the mixer settings, but apparently it is the dvd-plugin that doesn't work. since most channels here are encrypted on DVB-C and I primarily use it as an output device I tested the output using a dvd. now I found a non encrypted channel and suddenly the sound output on the dvb card worked. the problem with the analogue card however remains. how can I get vdr to accept the analogue channels the analoge card is on /dev/video1 could that be a problem? On 7/15/07, Stone <[EMAIL PROTECTED]> wrote: On 7/15/07, Chris F <[EMAIL PROTECTED]> wrote: > > Hi everyone, > > I've got a problem setting up a vdr system. > > I installed Debian Etch with a vanilla 2.6.21 kernel and vdr using the > e-tobi packages. > I used the development firmware (f12623) and also tried the firmware > from linuxtv.org > > Apart from the DVB-C FF card there is a WinTV PCI analogue TV-Card in > that I want to use to record analogue TV channels that are not broadcasted > in DVB-C. > > The system works so far, however the analogue sound output of the card > doesn't work and I have ne idea why. I hope someone who uses the same card > can help me out on that. This might be too obvious, but do you have "capture" enabled on the device in the alsamixer settings? My second problem is getting the analogue card to work. I installed the > analogue-tv plugin and using scantv I can find some channels, however if I > set up the channels.conf vdr doesn't add the channels to its list (i > stopped vdr before editing the channels.conf) > Whe can help me out on that ? > > Thanks in advance for any help you can give me. > > ___ 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
[vdr] no sound on output of TT-premium C-2300
Hi everyone, I've got a problem setting up a vdr system. I installed Debian Etch with a vanilla 2.6.21 kernel and vdr using the e-tobi packages. I used the development firmware (f12623) and also tried the firmware from linuxtv.org Apart from the DVB-C FF card there is a WinTV PCI analogue TV-Card in that I want to use to record analogue TV channels that are not broadcasted in DVB-C. The system works so far, however the analogue sound output of the card doesn't work and I have ne idea why. I hope someone who uses the same card can help me out on that. My second problem is getting the analogue card to work. I installed the analogue-tv plugin and using scantv I can find some channels, however if I set up the channels.conf vdr doesn't add the channels to its list (i stopped vdr before editing the channels.conf) Whe can help me out on that ? Thanks in advance for any help you can give me. Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Dual Tuner Cards
Hi Torgeir Veimo wrote: > The nova-t 500 is a PCI card, but has an internal USB bus. Is the hard-wired USB device the same as they sell separately? (WinTV-Nova-TD) I'm prepared to suffer a bit of weirdness while the drivers improve if I can free up a valuable PCI slot in my HTPC! Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Dual Tuner Cards
Hi Laz wrote: > I did read stuff a while back about people getting USB disconnects from > them at random but I've never seen that with mine. Are we saying that the Hauppauge USB dual tuner ones work? That would seriously make my day! Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Changing location of /srv/vdr
Thanks for the tip about VDR_OPTIONS. The Fedora package did not create /srv/vdr and I didn't want to use this location anyway as I currently record tv to another location and wanted to stick with that. Excellent software by the way! Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Changing location of /srv/vdr
I am running vdr on Fedora Core 6 and found that I couldn't start vdr as a service. I believe the problem is the fact that the default directory for vdr is /srv/vdr which doesn't exist and causes the service to hang. How do I change this default so vdr runs as a service? Many thanks, Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR timer + mplayer = VDR crash. Please fix!
Thursday, June 7, 2007, 5:29:23 PM, VDR wrote: > I compiled the current svn as suggested in that thread and it did not > help the problem. If you have 2 dvb cards (which many of us don't) > then you probably won't experience the problem. I have 2 cards but I added the budget just recently and VDR did not crash while running with just one FF card for months. > At any rate saying you fixed it somehow is great, ...for you anyways. > If the rest of us can't duplicate your magic then a proper fix is > required which is what I'm hoping will be the result of this thread. Since my FF card is in repair atm, I don't know if would be helpful if I play around with the VDR settings I recall to see if can force the crash again. If you guys want me to, I will do it as soon as the card arrives here. Atm my system runs with the budget cards and an old HW+ card. Dunno if the problem would occur in this situation, anyway. (probably not) -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR timer + mplayer = VDR crash. Please fix!
Thursday, June 7, 2007, 3:03:53 AM, VDR wrote: > If a timer is triggered while the mplayer plugin is in use, VDR > crashes. This has happened to me about a zillion times now and I'm > hoping somebody will fix this! You can use the mplayer plugin after a > timer is started no problem. Correct me if I'm wrong but mplayer > should never have to take control of the tuner in the first place > since it's not required to play a media file. Like I said last time this topic came up: I somehow got rid off the problem. I don't exactly remember the last thread about this problem and I didn't keep the mails - but wasn't there someone who also got rid off this problem by updating mplayer to a current SVN version? I thought it had something to do with VDR's DVB settings and stuff but I also updated mplayer. Currently I'm using MPlayer dev-SVN-r22825-4.1.2 and VDR does not crash when a timer triggers (or stops) while using mplayer. Well, at least here. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 1.5.x Shutdown
Monday, May 28, 2007, 9:46:12 PM, Udo wrote: > The shutdown script has always been a fire-and-forget script that did > not evaluate any return codes or output. The only change that landed > together with the VDR shutdown rewrite in 1.5.1 is that the script is > now called detached from VDR, so it can run in parallel and will not > terminate together with VDR. Some shutdown scripts may need to be adapted. > If you want to investigate: thread.c:SystemExec() is called with the new > parameter Detached=true. STDIN is redirected to /dev/null, STDOUT and > STDERR are same as VDR, all other FD's get closed as before. You can reproduce the problem pretty easy: If I use an 'empty' shutdown script that just starts with "#!/bin/sh" or bash or whatever, the script itself becomes a zombie. And if I use a script with just an empty line, "sh" becomes the zombie. So in either way, something is wrong and it can not be the script's fault. It would be helpful if someone could test this behavior. My assumption is that the problem occurs because of the missing wait call (if SystemExec is called 'detached'). I know, if VDR would wait in there, the script wouldn't run simultaneously. But if VDR never waits for the child's PID, the child's termination never gets handled and imho that's why the script remains as a zombie. waitpid( -1, &dummy, WNOHANG) called at some place later should do the trick. Or waitpid() explicitly for the child's PID, if we want to store the PID anywhere. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR: Mantis bug tracking and a forum
Hi Steffen Barszus wrote: > bugtracking is for sure a nice tool, but for vdr alone i don't see the > use of it. Often its one of the components which is making problems (a > plugin/patch) and these are on thousend different locations (vdrportal Perhaps using Launchpad would be an idea then? It can be taught about projects and products, so you could have a vdr project with various products registered underneath it (ie vdr and all the components), then bugs can all be tracked in one place and easily moved from the vdr product to another component. It's kinda a shame that so much work goes into the VDR community, but it's spread around the place and hard to keep track of. Hosting code branches on Launchpad (or at least mirroring them there), keeping bugs there and so on, would be very useful, imho. Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] 1.5.x Shutdown
Hi there, I recently updated from VDR 1.4.6 to 1.5.2. (with no problems so far, by the way :)) But today I noticed something which seems to me like a small bug in vdr's shutdown routines. My shutdown script checks for different running processes (or connections) and does not quit vdr if at least one of the tests returns true. But since 1.5.2 (or probably since 1.5.0) the shutdown script remains as a zombie in such cases until vdr actually quits. I haven't checked the sources yet, but I guess there's somewhere a call to close() (or pclose()) for the opened pipe(s) missing. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Bug/SegFault in vdr-1.4.6
Wednesday, May 16, 2007, 8:03:03 AM, Patrick wrote: > I guess you missed the correct "setting" which fixes that bug: You > bought a second DVB card. > _VDR_ crashes when starting a timer while mplayer-Plugin is running. > That's because vdr had to close the device to let mplayer open it. When > the recording starts, vdr tries to open the device but fails: > -> emergency restart -> close mplayer-Plugin -> quit mplayer. Well, maybe a second DVB card fixes the problem, but this surely wasn't what helped me. When I started with VDR half a year ago with one FF card, I had this trouble with timers/mplayer but then I changed some stuff during the time (settings, DVB drivers, newer mplayer version etc.) the problem was gone for good for months now. And I bought a second DVB card just two weeks ago. :) Hmm I really thought it had something to do with anything I changed within VDR's DVB settings. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Bug/SegFault in vdr-1.4.6
Wednesday, May 16, 2007, 12:37:35 AM, VDR wrote: > Another problem with crashing occurs when you are watching something > with the mplayer plugin and a timer is triggered. Results in a crash > every time here. I don't understand why it happens though because > playing something like a .avi doesn't (or shouldn't) require the tuner > to be in use... You're playing a file, not something from the dvb > stream! I noticed kind of the same problem in 1.4.x. As far as I can remember VDR crashed not just when a timer started but also when the timer was about to be completed. Anyway, I'm not exactly sure how I got rid off it since I've changed a lot of settings since then, but I think it has something to do with the DVB setting "Update channels" - even though I couldn't find any correlation when I checked the sources. Try setting "Update channels" to "no" and see if VDR still crashes while using mplayer when a timer starts. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] (OFFTOPIC) "EFF reveals plot to cripple European television"
Hi Klaus Schmidinger wrote: > IMHO this was a valuable piece of information Absolutely, since (if this insanity really happens) it means that projects like VDR are effectively dead in the water :( I find it hard to believe that TV networks will be happy with invalidating every piece of DVB hardware sold to date (and selling now), but it will all come down to how much pressure MPAA and friends can bring to bear on them. Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Sky+ Series Link
On Sat, Feb 03, 2007 at 11:31:40AM +0100, Rob Davis wrote: > I was playing with a Sky+ box over Christmas and was quite impressed > mainly with Series Link. > > What would be involved to get this implemented on VDR? I understand the > likelihood of reading the Sky UK epg streams is small - however I am > downloading a week or so worth of epg listings off xmltv. Is it > possible to do a quick search on the epg if a "record series" link is > requested? Hello, epgsearch plugin already does it, and it's far more powerful than Sky's attempt. Give it a whirl, if you liked Series Link, you'll love epgsearch's timer options :) -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Recordings sorting
Hi Inspired by the channel sorting thread, I'm wondering if there's any way to have vdr sort recordings by date rather than name? I would think that would be a more obvious default, but even if not, I would like to use it :) Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build failures on Ubuntu - gettid related
On Fri, Aug 18, 2006 at 12:15:49PM +0300, Ville Skytt? wrote:
> On Tue, 2006-08-15 at 14:52 +0200, Jens Auer wrote:
>
> _syscallX are not available for userspace in recent kernel headers
> (since April), this causes VDR compilation failures also with the
> current Fedora Core 6 test versions. More info:
> http://tinyurl.com/qaydh , http://lkml.org/lkml/2006/6/4/128
>
> The attached patch appears to work for me, and from a bit of Googling I
> get the impression that it should probably work with all kernel header
> sets since 2.4.20.
> --- thread.c~ 2006-06-02 16:51:39.0 +0300
> +++ thread.c 2006-08-18 01:26:24.0 +0300
> @@ -318,7 +318,5 @@
>
> -_syscall0(pid_t, gettid)
> -
> tThreadId cThread::ThreadId(void)
> {
> - return gettid();
> + return syscall(__NR_gettid);
> }
This works for me on Ubuntu, and is pretty much what I'd tried except
I used 224 instead of __NR_gettid. Can this be merged into vdr, Klaus?
--
Chris
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build failures on Ubuntu - gettid related
Hi C * Chris Elsworth ([EMAIL PROTECTED]) wrote: > I'm trying to get vdr-1.4.0 built on Ubuntu. I'm using the source from > the apt repository (apt-get source vdr). Not sure how much they differ, but I'm rebuilding packages from www.e-tobi.net and they seem to build ok. I'd guess that something about edgy's toolchain has changed enough that the packages won't build on dapper, or they're just broken atm ;) Cheers, -- Chris Jones [EMAIL PROTECTED] www.tenshu.net ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Build failures on Ubuntu - gettid related
On Tue, Aug 15, 2006 at 12:31:43PM +0200, Jens Auer wrote: > > Clearly I'm just missing a gettid definition, but does anyone know which > > Debian/Ubuntu package (they're basically the same) it's in? > > I have linux-kernel-headers 2.6.17-5.16 installed, I'm not sure where > > else to look. > On my Ubuntu System (Dapper with Ubuntu Kernel 2.6.15-26-686), the macro > _syscall0 is defined in /usr/include/asm-i386/unistd.h > and /usr/include/asm-x86_64/unistd.h. It comes with linux-kernel-headers > package. Hello Jens, Thanks for your reply. That's left me more baffled: [EMAIL PROTECTED]:~# grep -r syscall0 /usr/include/* [EMAIL PROTECTED]:~# grep -r gettid /usr/include/* /usr/include/asm-i386/unistd.h:#define __NR_gettid 224 /usr/include/asm-x86_64/unistd.h:#define __NR_gettid186 /usr/include/asm-x86_64/unistd.h:__SYSCALL(__NR_gettid, sys_gettid) /usr/include/bits/syscall.h:#define SYS_gettid __NR_gettid /usr/include/directfb/direct/system.h:pid_t direct_gettid(); [EMAIL PROTECTED]:~# What do you get for those commands? -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Build failures on Ubuntu - gettid related
Hello, I'm trying to get vdr-1.4.0 built on Ubuntu. I'm using the source from the apt repository (apt-get source vdr). I'm getting this: [EMAIL PROTECTED]:~/vdr-1.4.0# make g++ -fPIC -g -O2 -Wall -Woverloaded-virtual -c -DREMOTE_KBD -DLIRC_DEVICE=\"/dev/lircd\" -DRCU_DEVICE=\"/dev/ttyS1\" -D_GNU_SOURCE -DVIDEODIR=\"/video\" -DPLUGINDIR=\"./PLUGINS/lib\" thread.c thread.c:319: error: 'gettid' has not been declared thread.c:321: error: expected constructor, destructor, or type conversion before 'tThreadId' make: *** [thread.o] Error 1 [EMAIL PROTECTED]:~/vdr-1.4.0# If I comment out the line: _syscall0(pid_t, gettid) And change the gettid() call just below it into: return syscall(224); Then it builds, and seems to work fine. Clearly I'm just missing a gettid definition, but does anyone know which Debian/Ubuntu package (they're basically the same) it's in? I have linux-kernel-headers 2.6.17-5.16 installed, I'm not sure where else to look. thanks! -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: vdr suggestions & osd colour oddity (Chris Elsworth)
Hello Ilariu, I didn't think softdevice actually supported XVMC - I can't see any options for it in the Makefile to tweak. Only XV/DFB/VIDIX etc. The only output method I have compiled in is XV. (this is CVS checkout of softdevice). A quick grep through the source for 'xvmc' doesn't match anything either? Thanks, Chris On Wed, Aug 09, 2006 at 06:07:20PM +0100, Ilariu Raducan wrote: >Chris, > >From Your Xorg.0.log: > > (II) Loading extension XVideo > (II) Loading extension XVideo-MotionCompensation > (II) Loading extension X-Resource > >Notice XVideo-MotionCompensation (XVMC) > >That doesn't mean is used by the application, only that exists (which is >good) >If the application is built with it enabled then you may have problems. > >I see you have a NVIDIA card and XVMC is the most probable issue. > >Try to make sure softdevice is not compiled with XVMC enabled until this >extension is fixed. > >Regards. >Ilariu > >On 8/7/06, Chris Elsworth <[EMAIL PROTECTED]> wrote: > > Ilariu, > > Hm I don't think XvMC is enabled. It would say so in Xorg.0.log if it > was, right? A complete copy of my most recent X startup is here > http://spork.qfe3.net/~chris/vdr/Xorg.0.log > > No mention of XvMC that I can see, so I presume it's off. Config is: > http://spork.qfe3.net/~chris/vdr/xorg.conf > all fairly simple and almost the defaults. > > Chris > > On Mon, Aug 07, 2006 at 03:49:46PM +0100, Ilariu Raducan wrote: > >This also happened to me with vdr-xine if I tried to use xvmc video > output > >with NVIDIA. > > Maybe you need to check if you have xvmc enabled. > > > >On 8/7/06, Stefan Lucke <[EMAIL PROTECTED]> wrote: > > > > On Montag 07 August 2006 05:20, Chris Elsworth wrote: > > > On Sun, Aug 06, 2006 at 06:45:55PM -0700, CR wrote: > > > > Hi Chris, > > > > > > > > Chris Elsworth wrote: > > > > > > > > > Yes, I read the old mails and found the hue of 0 or 100 > > suggestion, > > > > > and tried it (see original mail I posted) and it didn't > work. I > > just > > > > > tried it again with softdevice from cvs to double check and > it > > didn't > > > > > have any effect, so maybe I'm running into a slightly > different > > > > > problem. > > > > > > > > > > Do you have any suggestions about how I might try to debug > it? > > > > > > > > Can you take a look at: > > > > > > > > http://www.flickr.com/photos/[EMAIL PROTECTED] > > > > @CR, I've seen this but I don't know whats the problem with your > setup > > or > > why our osd drawing is wrong in combination with nvidia cards. > > At which color depth is your X server running ? > > > > > > > > > > and let me know if your OSD looks like > > "softdevice_wrongoverlay1_software" > > > > or "softdevice_wrongoverlay_software" ? > > > > > > > > I think the problem lies in the code that alpha blends the > OSD with > > the > > > > video image. Changing the HUE setting for me had no effect > > either. I > > > > notice the OSD becomes "strange" once any video is > playing. Until > > then > > > > the OSD looks fine... > > > > > > Hello, > > > > > > Hmm, mine look different from all your examples. > > > > > > This is the pink, incorrect display: > > > http://spork.qfe3.net/~chris/vdr/snapshot4.png > > > > > > When changing to this channel, vdr says: > > > Aug 7 04:12:57 media vdr: [1191] [VideoOut]: 720x576 [90,0 > 540x576] > > -> 1024x768 [128,0 768x768] > > > > > > > > > This is a correct display: > > > http://spork.qfe3.net/~chris/vdr/snapshot5.png >
Re: [vdr] Re: vdr suggestions & osd colour oddity (Chris Elsworth)
Ilariu, Hm I don't think XvMC is enabled. It would say so in Xorg.0.log if it was, right? A complete copy of my most recent X startup is here http://spork.qfe3.net/~chris/vdr/Xorg.0.log No mention of XvMC that I can see, so I presume it's off. Config is: http://spork.qfe3.net/~chris/vdr/xorg.conf all fairly simple and almost the defaults. Chris On Mon, Aug 07, 2006 at 03:49:46PM +0100, Ilariu Raducan wrote: >This also happened to me with vdr-xine if I tried to use xvmc video output >with NVIDIA. >Maybe you need to check if you have xvmc enabled. > >On 8/7/06, Stefan Lucke <[EMAIL PROTECTED]> wrote: > > On Montag 07 August 2006 05:20, Chris Elsworth wrote: > > On Sun, Aug 06, 2006 at 06:45:55PM -0700, CR wrote: > > > Hi Chris, > > > > > > Chris Elsworth wrote: > > > > > > > Yes, I read the old mails and found the hue of 0 or 100 > suggestion, > > > > and tried it (see original mail I posted) and it didn't work. I > just > > > > tried it again with softdevice from cvs to double check and it > didn't > > > > have any effect, so maybe I'm running into a slightly different > > > > problem. > > > > > > > > Do you have any suggestions about how I might try to debug it? > > > > > > Can you take a look at: > > > > > > http://www.flickr.com/photos/[EMAIL PROTECTED] > > @CR, I've seen this but I don't know whats the problem with your setup > or > why our osd drawing is wrong in combination with nvidia cards. > At which color depth is your X server running ? > > > > > > > and let me know if your OSD looks like > "softdevice_wrongoverlay1_software" > > > or "softdevice_wrongoverlay_software" ? > > > > > > I think the problem lies in the code that alpha blends the OSD with > the > > > video image. Changing the HUE setting for me had no effect > either. I > > > notice the OSD becomes "strange" once any video is playing. Until > then > > > the OSD looks fine... > > > > Hello, > > > > Hmm, mine look different from all your examples. > > > > This is the pink, incorrect display: > > http://spork.qfe3.net/~chris/vdr/snapshot4.png > > > > When changing to this channel, vdr says: > > Aug 7 04:12:57 media vdr: [1191] [VideoOut]: 720x576 [90,0 540x576] > -> 1024x768 [128,0 768x768] > > > > > > This is a correct display: > > http://spork.qfe3.net/~chris/vdr/snapshot5.png > > > > And when changing to this channel, vdr says: > > Aug 7 04:13:29 media vdr: [1197] [VideoOut]: 720x576 [0,0 720x576] -> > 1024x768 [0,0 1024x768] > > > > > > Another incorrect: > > http://spork.qfe3.net/~chris/vdr/snapshot6.png > > > > And the log: > > Aug 7 04:14:35 media vdr: [1216] [VideoOut]: 704x576 [0,0 704x576] -> > 1024x768 [0,0 1024x768] > > > > > > Screenshots were made with ksnapshot. The only correlation I can make > > so far is that lower resolutions seem to present the problem? > > Can you try that without any skin / osd related plugin and with an > unpatched > (vanilla) vdr ? > What are your osd postions and size specs (setup -> osd) ? > > -- > Stefan Lucke > > ___ > 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 -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: vdr suggestions & osd colour oddity (Chris Elsworth)
On Mon, Aug 07, 2006 at 04:23:07PM +0200, Stefan Lucke wrote: > On Montag 07 August 2006 05:20, Chris Elsworth wrote: > > On Sun, Aug 06, 2006 at 06:45:55PM -0700, CR wrote: > > > Hi Chris, > > > > > > Chris Elsworth wrote: > > > > > > > Yes, I read the old mails and found the hue of 0 or 100 suggestion, > > > > and tried it (see original mail I posted) and it didn't work. I just > > > > tried it again with softdevice from cvs to double check and it didn't > > > > have any effect, so maybe I'm running into a slightly different > > > > problem. > > > > > > > > Do you have any suggestions about how I might try to debug it? > > > > > > Can you take a look at: > > > > > > http://www.flickr.com/photos/[EMAIL PROTECTED] > > @CR, I've seen this but I don't know whats the problem with your setup or > why our osd drawing is wrong in combination with nvidia cards. > At which color depth is your X server running ? > > > > > > > and let me know if your OSD looks like "softdevice_wrongoverlay1_software" > > > or "softdevice_wrongoverlay_software" ? > > > > > > I think the problem lies in the code that alpha blends the OSD with the > > > video image. Changing the HUE setting for me had no effect either. I > > > notice the OSD becomes "strange" once any video is playing. Until then > > > the OSD looks fine... > > > > Hello, > > > > Hmm, mine look different from all your examples. > > > > This is the pink, incorrect display: > > http://spork.qfe3.net/~chris/vdr/snapshot4.png > > > > When changing to this channel, vdr says: > > Aug 7 04:12:57 media vdr: [1191] [VideoOut]: 720x576 [90,0 540x576] -> > > 1024x768 [128,0 768x768] > > > > > > This is a correct display: > > http://spork.qfe3.net/~chris/vdr/snapshot5.png > > > > And when changing to this channel, vdr says: > > Aug 7 04:13:29 media vdr: [1197] [VideoOut]: 720x576 [0,0 720x576] -> > > 1024x768 [0,0 1024x768] > > > > > > Another incorrect: > > http://spork.qfe3.net/~chris/vdr/snapshot6.png > > > > And the log: > > Aug 7 04:14:35 media vdr: [1216] [VideoOut]: 704x576 [0,0 704x576] -> > > 1024x768 [0,0 1024x768] > > > > > > Screenshots were made with ksnapshot. The only correlation I can make > > so far is that lower resolutions seem to present the problem? > > Can you try that without any skin / osd related plugin and with an unpatched > (vanilla) vdr ? > What are your osd postions and size specs (setup -> osd) ? Hello, I tried with as few plugins as possible to maintain a working setup: softdevice remote And the problem persists. My usual plugins are the above plus pilotskin, femon, epgsearch, weather Here's my OSD settings from setup.conf OSDHeight = 486 OSDLanguage = 0 OSDLeft = 54 OSDMessageTime = 1 OSDSkin = sttng OSDTheme = cool OSDTop = 45 OSDWidth = 624 softdevice.OSDalphablend = 1 I've tried a few different skins and that doesn't make any difference. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: vdr suggestions & osd colour oddity (Chris Elsworth)
On Sun, Aug 06, 2006 at 06:45:55PM -0700, CR wrote: > Hi Chris, > > Chris Elsworth wrote: > > > Yes, I read the old mails and found the hue of 0 or 100 suggestion, > > and tried it (see original mail I posted) and it didn't work. I just > > tried it again with softdevice from cvs to double check and it didn't > > have any effect, so maybe I'm running into a slightly different > > problem. > > > > Do you have any suggestions about how I might try to debug it? > > Can you take a look at: > > http://www.flickr.com/photos/[EMAIL PROTECTED] > > and let me know if your OSD looks like "softdevice_wrongoverlay1_software" > or "softdevice_wrongoverlay_software" ? > > I think the problem lies in the code that alpha blends the OSD with the > video image. Changing the HUE setting for me had no effect either. I > notice the OSD becomes "strange" once any video is playing. Until then > the OSD looks fine... Hello, Hmm, mine look different from all your examples. This is the pink, incorrect display: http://spork.qfe3.net/~chris/vdr/snapshot4.png When changing to this channel, vdr says: Aug 7 04:12:57 media vdr: [1191] [VideoOut]: 720x576 [90,0 540x576] -> 1024x768 [128,0 768x768] This is a correct display: http://spork.qfe3.net/~chris/vdr/snapshot5.png And when changing to this channel, vdr says: Aug 7 04:13:29 media vdr: [1197] [VideoOut]: 720x576 [0,0 720x576] -> 1024x768 [0,0 1024x768] Another incorrect: http://spork.qfe3.net/~chris/vdr/snapshot6.png And the log: Aug 7 04:14:35 media vdr: [1216] [VideoOut]: 704x576 [0,0 704x576] -> 1024x768 [0,0 1024x768] Screenshots were made with ksnapshot. The only correlation I can make so far is that lower resolutions seem to present the problem? I have to use softdevice with software alpha blending; if I use pseudo, it only appears for one frame every second. I'm having trouble getting xineliboutput to build so I can test it. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr suggestions & osd colour oddity
On Sun, Aug 06, 2006 at 08:46:22AM +0200, Herbert Poetzl wrote: > > > > So my only issue to sort is the miscoloured OSD now. It turns a > > beautiful shade of pink when the problem occurs on my setup :) > > try to manually set the HUE to 0 or 100 instead of > the default 50, we had (and solved?) this problem some > time ago .. Hello Herbert, Yes, I read the old mails and found the hue of 0 or 100 suggestion, and tried it (see original mail I posted) and it didn't work. I just tried it again with softdevice from cvs to double check and it didn't have any effect, so maybe I'm running into a slightly different problem. Do you have any suggestions about how I might try to debug it? -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr suggestions & osd colour oddity
On Fri, Aug 04, 2006 at 04:26:19PM +0100, Chris Elsworth wrote: > > Chris Elsworth wrote: > > >When viewing a channel, pressing Up/Down currently changes channel; > > >would it be possible to allow these buttons to just show channel > > >information (with now/next in) for the previous/next channels, > > >allowing one to quickly view what is on the other channels? > > > > Why don't you use the schedule from main menu for it? There's a now/next > > display mode for that. You can also switch channels from there. > > Hm yes, that will actually do the job. I guess the only reason I ask > for the above is that I'm used to it, and found it a fairly nice way > of channel hopping (I'm migratin from Sky in the UK). PS: vdr-pilotskin (and vdr-pilot, but I didn't try that one) look like they do exactly what I'm after in this section :) hope tht helps anyone else who was looking for that functionality. -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr suggestions & osd colour oddity
On Fri, Aug 04, 2006 at 04:07:18PM +0200, Udo Richter wrote: > Chris Elsworth wrote: > >When viewing a channel, pressing Up/Down currently changes channel; > >would it be possible to allow these buttons to just show channel > >information (with now/next in) for the previous/next channels, > >allowing one to quickly view what is on the other channels? > > Why don't you use the schedule from main menu for it? There's a now/next > display mode for that. You can also switch channels from there. Hello Udo, Hm yes, that will actually do the job. I guess the only reason I ask for the above is that I'm used to it, and found it a fairly nice way of channel hopping (I'm migratin from Sky in the UK). > >I think it would also be nice if there were more than one > >rewind/fastforward speed, achievable by repeated pressing of the > >appropriate button; press ff once to ff at 2x speed, again for 4x > >speed, again for 8x speed? > > Setup -> Replay -> Multi speed mode Perfect! Don't know how I missed that one, you added it when I wasn't looking ;) Much appreciated, thanks very much. That does exactly what I want. So my only issue to sort is the miscoloured OSD now. It turns a beautiful shade of pink when the problem occurs on my setup :) thanks Udo, -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr suggestions & osd colour oddity
Hello! I've just started using vdr 1.4.0 in Ubuntu and I have to say I'm extremely impressed and very happy with it - very nice work, well done to the author :) I have a couple of things I'd like to suggest and wonder if they'd be up for consideration. When viewing a channel, pressing Up/Down currently changes channel; would it be possible to allow these buttons to just show channel information (with now/next in) for the previous/next channels, allowing one to quickly view what is on the other channels? ie, I could keep pressing Up to go through the channels, seeing what is on now and next, but without actually changing channel - then press OK to change the channel once I find one to watch. I think it would also be nice if there were more than one rewind/fastforward speed, achievable by repeated pressing of the appropriate button; press ff once to ff at 2x speed, again for 4x speed, again for 8x speed? I'd like to have a go at adding these features myself but I've not read much of the code yet. I'll see how much I can decipher in due course, but maybe someone already did these, or they're planned. I'm suffering a problem that I have no idea how to fix, however - I've read the list archives and noted a few months ago that some posts were made about oddly-coloured OSD when using softdevice and nvidia cards. I believe this is the same problem that I currently see too; it only seems to happen with low resolution broadcasts - when the resolution drops below 640x480 or thereabouts, the OSD turns "pink" for me. On any channel with a higher resolution than this it's ok. I'm using an NVidia 7600 connected to a TV using softdevice/xv. The NVidia natively directs output to the TV since it's the only output device connected, so X is running on it at 1024x768 without any other special configuration. Changing the softdevice/hue to either 0 or 100 as was suggested in those previous posts did not fix the problem for me - I was wondering if anyone else had any tips on what I might try to fix this. thanks very much for any replies & advice, -- Chris ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
