Re: [vdr] VDR 1.7.16 FF card crashes
Am Mittwoch, den 09.02.2011, 22:13 +0200 schrieb - -: Hello! I upgraded my VDr system from 1.6.0 to 1.7.16. After upgrade, I found that my FF card (fujitsu-siemens dvb-c) crashes almost every time when I exit from a recording playback. It won't tune anymore. Usually OSD still works but sometimes it also crashes. Only way to recover is to restart VDR and reload kernel module. I'm using latest fw for ff card. Have you tried this firmware: http://escape-edv.de/endriss/firmware/ ? But even with that firmware you must not switch to a DVB-S2 Channel, since that will crash your card in any case. Ps. For some reason sc plugin doesn't work either with ff card even I have forced to transfer mode from sc plugin menu and started it with -B switches. Maybe it is related to this crash? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr cpu usage
Am Mittwoch, den 20.10.2010, 11:44 +0200 schrieb Theunis Potgieter: Hi mailing list, perhaps this question was asked on other forums before (maybe even in a different language). Google failed to bring up search results for vdr idle cpu usage. I have vdr 1.7.14 running with the only plugins dummydevice and streamdev-server, no client is currently connected and on my Pentium 3 machine 1GHz, it uses between 10% ~ 15% cpu idling. This is also after a restart of vdr and tuning to a channel that has got no video and audio. So now my question is, why would vdr use even more than 1% cpu usage, compared to other services like mediatomb that if not in use is about 0.1%. Is this a requirement that vdr uses this much all the time? It is definitly not VDR itself, but rather one of the plugins. My VDR (1.7.15) with several Plugins (skinenigmang,femon,streamdev-server,xine) consumes less than 1% CPU when idle (but tuned to a valid station), and less than 5% when a xine client is connected (HD Channel!) CPU is a Core 2 6600 (2.4 Ghz) -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Cutting HD Recordings
Hello, recently, i tried to cut a TS recording with VDR 1.7.12. Cutting it works ok, but when i replay it, there is a short distortion when it runs across the cut. On my production system, that is equipped with a Reel eHD, the problem is worse, because the eHD is completely confused when it crossed a cut. To get it back in sync, i need to jump forward or backward. Since this occurs only with HD recordings, i assume that VDR make some kind of mistake when it created the cutted version. -- Falk Spitzberg ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Rewind and Fast Forward problems
Am Donnerstag, den 04.03.2010, 11:20 +0200 schrieb Jaakko Hyvätti: Hi, I guess this must be an error in my setup, maybe channels.conf, or something similar, but just cannot find it.. I recently went from 1.6.0 to 1.7.12 and now 1.7.13, and all my old and new recordings alike either cannot be rewinded or fast forwarded. One way works, and another does not, one way works in some recordings and the other in the rest of them. What happens is that when you rewind (or ff), it looks good and goes backwards, but then when you go to play, it starts at the place you started the rewind. Also, while rewinding, if you have the status bar on, the time does not count at all, and the green bar only moves little if at all. That sounds similar to a problem that i've seen: When you play a recording for a while and then, let's say after 30 Minutes, jump forward one minute, the first jump effectively goes back a few minutes, subsequent forward jumps then really go forward. I thought this problem is related to the reelbox plugin (i am using a reel eHD), but now i think that VDR sometimes loses track about it's actual position. Tried to search this list.. But still baffled and thankful for any help. I'm in Finland, Helsinki, Welho Cable network. Example of a channel that does not work: MTV3 D;MTV Oy:282000:C0M128:C:6900:305=2:561=fin:817:0:49:42249:2:0 My conf: http://www.iki.fi/hyvatti/dvb/vdr-17-setup.txt Regards, jaakko.hyva...@iki.fi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ERROR: driver buffer overflow on device 1
Am Dienstag, den 23.02.2010, 20:49 +0200 schrieb Josce: vdr-1.7.12 + reelbox + 2 Anysee E30C USB devices Sadly quite often my vdr stops working, with the following error: localhost vdr: [2626] buffer usage: 70% (tid=2625) localhost vdr: [2626] buffer usage: 80% (tid=2625) localhost vdr: [2626] buffer usage: 90% (tid=2625) localhost vdr: [2626] buffer usage: 100% (tid=2625) localhost vdr: [2626] ERROR: driver buffer overflow on device 1 localhost vdr: [2626] ERROR: driver buffer overflow on device 1 (repeated over and over again) Does it happen on all channels? I have the same problem, but only with HD channels. When i switch to a different channel. the problem goes away until it comes up after a while. I assume that the hdplayer on the eHD card gets stuck. Just killing vdr and reloading the DVB driver doesn't fix this. I have to reboot the machine to get everything working again. Now I was wondering, when this happens how can I make vdr exit with say exit code 9, so that I can make the runvdr reboot the machine. Thanks, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 10 Year Anniversary of VDR
Congratulatiosn Klaus and all the other developers. I'm using VDR since mid 2001 and never found a better way to watch TV. Falk Am Freitag, den 19.02.2010, 17:09 +0100 schrieb Klaus Schmidinger: It has been exactly 10 years since version 0.01 of VDR (originally named OSM - On Screen Menu) was released. I want to use the occasion to thank everybody who has contributed to VDR, but also those who simply use VDR in their every day life. I for one couldn't imagine watching tv without VDR any more. Special thanks go to the people running the VDR-Portal (www.vdr-portal.de). Originally I intended to release version 2.0 of VDR at the 10th anniversary, but as ever so often, I ran out of time. But I'm still on it - stability comes before deadlines ;-) I hope you don't think I'm blowing my own horn here, I just didn't want the date to pass by without a remark... Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Dolby audio on DasErste
Am Montag, den 01.02.2010, 16:52 +0100 schrieb Thomas Grünig: Hi Falk, I had this problem too and found a solution in vdr-portal.de: Goto setup/DVB and set Audio languages to 0. For me it works fine. Good trick. Works fine. Thanks! Assuming you speak german, here is the link to the vdr-portal-page: http://www.vdr-portal.de/board/thread.php?threadid=69467 Tom Am 01.02.2010 14:22, schrieb Falk Spitzberg: Hello, I asked for this topic a while back. When i select Dolby audio, VDR uses the Dolby digital track on all channels but DasErste. I know that they name their dolby track non standard and i know that i can edit the channels.conf to name the pid correctly. But for other reasons i need to turn on automatic PID update, and now I have to select the Dolby track manually, each time when i switch to that channel, because the automatic update overwrites my manual change. Is there another possibility to tell VDR to use the dd Track although it has a non standard name? Any help is greatly appreciated. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Dolby audio on DasErste
Hello, I asked for this topic a while back. When i select Dolby audio, VDR uses the Dolby digital track on all channels but DasErste. I know that they name their dolby track non standard and i know that i can edit the channels.conf to name the pid correctly. But for other reasons i need to turn on automatic PID update, and now I have to select the Dolby track manually, each time when i switch to that channel, because the automatic update overwrites my manual change. Is there another possibility to tell VDR to use the dd Track although it has a non standard name? Any help is greatly appreciated. -- Falk Spitzberg E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Cannot replay recordings on FF card if recorded with s2 card
Am Mittwoch, den 25.11.2009, 08:48 +0100 schrieb Matthias Fechner: Hi, I have now replaced my primary video with a nice Atom board and inserted there a Tevii S470 card. Output is via HDMI and the xineliboutput plugin. It is working really great, thanks a lot for the really fantastic software! But I have now a big problem. I upgraded now from vdr 1.7.2 to 1.7.10. If I record now a normal PAL movie I cannot replay it with my FF card on my old TV. Sound is stuck and picture as well. I had a similar problem with vdr 1.7.9 and went then back to 1.7.2 which solved the problem. But now I cannot switch back to an older version because xine will not work then without patching a ot of stuff. Is there a know issue with vdr newer 1.7.2 and replay on a FF (TechnoTrend Rev 1.3) card? You need a new driver/firmware for your FF card to support TS playback. The latest v4l drivers include the correct version. I have the same card and it works just fine with VDR 1.7.9. Bye, Matthias -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Tuner switch when timer starts recording
Am Sonntag, den 22.11.2009, 13:34 +0100 schrieb Klaus Schmidinger: On 18.11.2009 08:40, Falk Spitzberg wrote: Hello, With VDR 1.7.9 i often notice that VDR switches the live TV to a different receiver card, when a timer starts recording, although the second card is available. This causes a short interrupt in live TV. My system has two DVB cards, an old FF and a Tevii S470, and an eHD. Sample situation 1: the only activity is live TV on ZDF. Now a timer starts recording from RTL 2, which interrupts the live program for a short moment. Sample situation 2: the only activity is live TV on RTL. Now a timer starts recording from RTL 2. Nothing happens, because VDR correctly shares the transponder with live TV. I would understand when VDR switches live TV from the DVB-S2 card to the DVB-S card when it needs to tune a different transponder for a DVB-S2 recording, but since it can do DVB-S recordings from any card, there is no reason to switch live TV for such recordings. When recording, VDR tries to preserve devices that provide multiple delivery systems: imp = 2; imp |= GetClippedNumProvidedSystems(2, device[i]) - 1; // avoid cards which support multiple delivery systems Then it would be a good idea to prefer those cards for live view. See device.c, cDevice *cDevice::GetDevice(const cChannel *Channel, int Priority, bool LiveView). Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Hi Klaus (and others) the replay problem is probably fixed. It was located in the hdplayer program that runs on the eHD. The fixed version should be available soon. Thanks to the guy who is known as reel_schorsch on the VDR-Portal. Falk Am Montag, den 07.09.2009, 19:25 +0200 schrieb Klaus Schmidinger: On 07.09.2009 14:41, Falk Spitzberg wrote: Am Montag, den 07.09.2009, 15:29 +0300 schrieb Antti Hartikainen: On Mon, Sep 07, 2009 at 02:24:48PM +0200, Günter Greschenz wrote: Maybe it's ok if I use this opportunity to ask if somebody could point me to a complete idiot's guide to installing the eHD software I've sent some stuff with private mail. Should help you to bring it up within a few minutes. hi, could you send it to me also ? i'm very interested in this card :-) thanks, gg I'm also interested to see this information. Wouldn't it be good idea to publish it on the list, it would be more useful for the people who are looking for the information =) Let me see if it works for Klaus. Once he has his eHD running using the stuff that I've collected, i'll publish it either here or in the VDR portal. Falk, thanks a lot for the guidelines - I really appreciate it! However, I sure won't be able to test this before next weekend, mabe even later, since I first have to debug the fast forwarding in SF2 recordings problem. So you might as well just post them on the ML for others to try. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Tuner switch when timer starts recording
Hello, With VDR 1.7.9 i often notice that VDR switches the live TV to a different receiver card, when a timer starts recording, although the second card is available. This causes a short interrupt in live TV. My system has two DVB cards, an old FF and a Tevii S470, and an eHD. Sample situation 1: the only activity is live TV on ZDF. Now a timer starts recording from RTL 2, which interrupts the live program for a short moment. Sample situation 2: the only activity is live TV on RTL. Now a timer starts recording from RTL 2. Nothing happens, because VDR correctly shares the transponder with live TV. I would understand when VDR switches live TV from the DVB-S2 card to the DVB-S card when it needs to tune a different transponder for a DVB-S2 recording, but since it can do DVB-S recordings from any card, there is no reason to switch live TV for such recordings. Falk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Am Samstag, den 05.09.2009, 15:09 +0200 schrieb Klaus Schmidinger: On 03.09.2009 12:10, Falk Spitzberg wrote: Am Mittwoch, den 02.09.2009, 08:49 -0700 schrieb VDR User: Sounds like your question is more appropriate for the vendors customer support of that product. Definitly not, because my question ist only about the VDR core. I am just trying to find out what VDR does different when it transfers data to a device in live TV compared to replay from disk. That's completely independent from any device that's in use. Maybe that the eHD card is the only output device that crashes on VDR TS replays. The following is related to recent developer versions of VDR 1.7.x. In live mode (i.e. Transfer Mode, since the eHD has no tuner) the TS data stream is written into a ring buffer by the receiving device (e.g. a DVB-S(2) card) and from there it is sent to the output device (the eHD plugin) through a call to PlayTs(). In this case every TS packet is sent to the output device separately. During replay data is read from disk and stored in a ring buffer that holds entire frames, which are just a sequence of TS packets that make up one video frame (including audio). The output device's PlayTs() is called with an entire frame. The only real difference between live mode and replay I can see is that in live mode TS packets are sent individually to the output device, while in replay mode larger blocks of data are sent. However, I don't see why this would cause the problems you observe. AFAIK the Reel plugin requires several patches to the core VDR code, so there may well be things I simply don't know of, because I haven't looked into the Reel code (yet). Maybe it's ok if I use this opportunity to ask if somebody could point me to a complete idiot's guide to installing the eHD software I've sent some stuff with private mail. Should help you to bring it up within a few minutes. (meaning the necessary software that goes into the eHD itself, as well as the latest version of their plugin). I know, I could search for this myself, but I'm sure there's somebody out there who knows exactly where to find these ;-) Maybe I'll find the time to actually bring up my eHD and adapt the plugin to the latest developer version of VDR... Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Am Donnerstag, den 03.09.2009, 07:57 -0700 schrieb VDR User: On Thu, Sep 3, 2009 at 3:10 AM, Falk Spitzbergp...@spitzberg.de wrote: Am Mittwoch, den 02.09.2009, 08:49 -0700 schrieb VDR User: Sounds like your question is more appropriate for the vendors customer support of that product. Definitly not, because my question ist only about the VDR core. I am just trying to find out what VDR does different when it transfers data to a device in live TV compared to replay from disk. That's completely independent from any device that's in use. Maybe that the eHD card is the only output device that crashes on VDR TS replays. How do you know the problem isn't a bug in the eHD driver or stream parser/decoder? I don't know. But what is wrong about my attempt to find out what VDR does different during replay vs. live TV. I did never say that VDR does something wrong. I just asked a question. Too bad that nobody can answer it. -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Am Mittwoch, den 02.09.2009, 08:49 -0700 schrieb VDR User: Sounds like your question is more appropriate for the vendors customer support of that product. Definitly not, because my question ist only about the VDR core. I am just trying to find out what VDR does different when it transfers data to a device in live TV compared to replay from disk. That's completely independent from any device that's in use. Maybe that the eHD card is the only output device that crashes on VDR TS replays. -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Replay Problems with Extension HD
Does really nobody have an idea ?? Am Donnerstag, den 27.08.2009, 11:46 +0200 schrieb Falk Spitzberg: Hello, Users of the Reel Extension HD card will know that there are Problems when TS recordings are replayed. These Problems seem to be limited to some stations like Pro7 and even with these stations to movies that are broadcastest with DD 5.1 audio. Now my question: What is different between Live TV and Replay. Of course the obvious difference is the data source (file opposed to DVB device). But what else is different? I am wondering, because i watched a movie without problems, while the recording that was done while i watched it live, cannot be replayed. After a few minutes, the hdplayer on the Extension card dies. -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Replay Problems with Extension HD
Hello, Users of the Reel Extension HD card will know that there are Problems when TS recordings are replayed. These Problems seem to be limited to some stations like Pro7 and even with these stations to movies that are broadcastest with DD 5.1 audio. Now my question: What is different between Live TV and Replay. Of course the obvious difference is the data source (file opposed to DVB device). But what else is different? I am wondering, because i watched a movie without problems, while the recording that was done while i watched it live, cannot be replayed. After a few minutes, the hdplayer on the Extension card dies. -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Dolby Audio not used
Hello, i am using VDR-1.7.0 with one TT FF Card, one TT-S2 3600 and a Reel eHD. The entire system runs fairly stable, with one little problem: Although i've selected Use Dolby Digital, VDR does not automatically select the DD audio track on Das Erste. On all other stations that transmit DD 2.0 permanently (ZDF, RTL, SAT1, PRO7) VDR automatically selects the DD audio, no matter if DD 2.0 or DD 5.1 is active. I can manually select DD audio and that works. When i switch to a different station and then back to Das Erste VDR falls back to the stereo audio. Any idea what i am missing? Thanks Falk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Prolem with TT s2-3600
Hello, i am lost with my TT Connect S2-3600. It used to work, but after a teporary switch to kernel 2.6.30 i can't get it up anymore. I am back on kernel 2.6.27.23 (SuSE) and the S2-Liplianin driver package. All modules built fine and are installed correctly. A FullFeatured card that is also there, works without problems. When i connect the USB box, it get the following error: usb 3-5: new high speed USB device using ehci_hcd and address 2 usb 3-5: configuration #1 chosen from 1 choice usb 3-5: New USB device found, idVendor=0b48, idProduct=3007 usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-5: Product: TT-USB2.0 usb 3-5: Manufacturer: TechnoTrend dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state. pctv452e_power_ctrl: 1 dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Technotrend TT Connect S2-3600) pctv452e: I2C error -121; AA 02 A0 01 14 - 55 02 A0 00 00. dvb-usb: MAC address: 88013657b0d0 pctv452e_frontend_attach Enter BUG: unable to handle kernel NULL pointer dereference at IP: [8049b393] __mutex_lock_slowpath+0x34/0xa2 PGD 132d59067 PUD 1365b8067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /sys/devices/pci:00/:00:1d.7/usb3/3-5/bmAttributes CPU 0 Modules linked in: stb0899(N) dvb_usb_pctv452e(N+) dvb_usb(N) lirc_serial(N) lir c_dev(N) snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device tun hdshm(N) af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq fuse loop dm_mod tda8083(N) stv0299(N) ves1x93(N) dvb_ttpci(N) dvb_core(N) saa7146_v v(N) videodev(N) v4l1_compat(N) v4l2_compat_ioctl32(N) saa7146(N) snd_hda_intel videobuf_dma_sg(N) videobuf_core(N) snd_pcm snd_timer ttpci_eeprom(N) snd_page_a lloc snd_hwdep i2c_i801 snd ohci1394 e1000e button soundcore i2c_core ieee1394 r tc_cmos pcspkr intel_agp rtc_core sr_mod rtc_lib cdrom sg uhci_hcd ehci_hcd sd_m od crc_t10dif usbcore edd ext3 mbcache jbd fan ide_pci_generic ide_core ata_gene ric ahci pata_jmicron libata scsi_mod dock thermal processor thermal_sys hwmon Supported: No Pid: 3994, comm: modprobe Tainted: G 2.6.27.23-0.1-default #1 RIP: 0010:[8049b393] [8049b393] __mutex_lock_slowpath+0x34/ 0xa2 RSP: 0018:880132ca9b90 EFLAGS: 00010246 RAX: RBX: a03d9708 RCX: 0002 RDX: RSI: 880132ca9c18 RDI: a03d970c RBP: a03d970c R08: 880132ca9ca7 R09: 0001 R10: R11: R12: 8801385fa740 R13: a03d9710 R14: a03d96d0 R15: FS: 7f7b741746f0() GS:80a40080() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 00013a16f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 3994, threadinfo 880132ca8000, task 8801385fa740) Stack: a03d9710 880132ca9cc8 a03d79f0 880132ca9ca7 a03d96d0 0002 880132ca9c18 a03d96d0 8049b33f a0190519 Call Trace: [8049b33f] mutex_lock+0xa/0xb [a0190519] i2c_transfer+0x56/0xd1 [i2c_core] [a03d6252] i2c_read+0x48/0x67 [stb0899] [a03d62bf] Read8Direct+0x4e/0x99 [stb0899] [a03d7569] stb0899_attach+0x139/0x348 [stb0899] [a03cfa3a] pctv452e_frontend_attach+0x5e/0x206 [dvb_usb_pctv452e] [a03c8e94] dvb_usb_adapter_frontend_init+0x33/0xf5 [dvb_usb] [a03c89ab] dvb_usb_device_init+0x4de/0x5c7 [dvb_usb] [a00f78e0] usb_probe_interface+0x1a8/0x1df [usbcore] [803e65b7] really_probe+0xdd/0x1e5 [803e67a4] __driver_attach+0x46/0x6d [803e5d82] bus_for_each_dev+0x44/0x78 [803e5686] bus_add_driver+0xf4/0x224 [803e6962] driver_register+0x9c/0x103 [a00f7af7] usb_register_driver+0x7e/0xe0 [usbcore] [a019a01b] pctv452e_usb_init+0x1b/0x5c [dvb_usb_pctv452e] [80209041] _stext+0x41/0x110 [80260f76] sys_init_module+0xa0/0x1ba [8020bfbb] system_call_fastpath+0x16/0x1b [7f7b73cfa76a] 0x7f7b73cfa76a Code: 6f 04 53 48 89 fb 48 89 ef 4c 8d 6b 08 48 83 ec 20 65 4c 8b 24 25 00 00 00 00 e8 03 0d 00 00 48 8b 53 10 4c 89 2c 24 48 89 63 10 48 89 22 48 89 54 24 08 48 83 ca ff 4c 89 64 24 10 48 89 d0 87 RIP [8049b393] __mutex_lock_slowpath+0x34/0xa2 RSP 880132ca9b90 CR2: ---[ end trace 2a7a22f5799b2d7c ]--- usb 3-5: USB disconnect, address 2 Any ideas? -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Prolem with TT s2-3600
Am Mittwoch, den 15.07.2009, 11:21 +0200 schrieb Thomas Netousek: ich kenn mich zwar nicht aus und darum poste ich es auch nicht auf der mailingliste, aber dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state. sagt mir, dass einmal Strom abschalten bei der TT helfen koennte ?! Glaub mir, das habe ich als erstes probiert. Der Fehler kommt immer, egal, ob die Box warm- oder kalt gestartet wurde. Aber trotzdem Danke für den Hinweis. Thomas Falk Spitzberg wrote: Hello, i am lost with my TT Connect S2-3600. It used to work, but after a teporary switch to kernel 2.6.30 i can't get it up anymore. I am back on kernel 2.6.27.23 (SuSE) and the S2-Liplianin driver package. All modules built fine and are installed correctly. A FullFeatured card that is also there, works without problems. When i connect the USB box, it get the following error: usb 3-5: new high speed USB device using ehci_hcd and address 2 usb 3-5: configuration #1 chosen from 1 choice usb 3-5: New USB device found, idVendor=0b48, idProduct=3007 usb 3-5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 usb 3-5: Product: TT-USB2.0 usb 3-5: Manufacturer: TechnoTrend dvb-usb: found a 'Technotrend TT Connect S2-3600' in warm state. pctv452e_power_ctrl: 1 dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer. DVB: registering new adapter (Technotrend TT Connect S2-3600) pctv452e: I2C error -121; AA 02 A0 01 14 - 55 02 A0 00 00. dvb-usb: MAC address: 88013657b0d0 pctv452e_frontend_attach Enter BUG: unable to handle kernel NULL pointer dereference at IP: [8049b393] __mutex_lock_slowpath+0x34/0xa2 PGD 132d59067 PUD 1365b8067 PMD 0 Oops: 0002 [1] SMP last sysfs file: /sys/devices/pci:00/:00:1d.7/usb3/3-5/bmAttributes CPU 0 Modules linked in: stb0899(N) dvb_usb_pctv452e(N+) dvb_usb(N) lirc_serial(N) lir c_dev(N) snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device tun hdshm(N) af_packet ipv6 cpufreq_conservative cpufreq_userspace cpufreq_powersave acpi_cpufreq fuse loop dm_mod tda8083(N) stv0299(N) ves1x93(N) dvb_ttpci(N) dvb_core(N) saa7146_v v(N) videodev(N) v4l1_compat(N) v4l2_compat_ioctl32(N) saa7146(N) snd_hda_intel videobuf_dma_sg(N) videobuf_core(N) snd_pcm snd_timer ttpci_eeprom(N) snd_page_a lloc snd_hwdep i2c_i801 snd ohci1394 e1000e button soundcore i2c_core ieee1394 r tc_cmos pcspkr intel_agp rtc_core sr_mod rtc_lib cdrom sg uhci_hcd ehci_hcd sd_m od crc_t10dif usbcore edd ext3 mbcache jbd fan ide_pci_generic ide_core ata_gene ric ahci pata_jmicron libata scsi_mod dock thermal processor thermal_sys hwmon Supported: No Pid: 3994, comm: modprobe Tainted: G 2.6.27.23-0.1-default #1 RIP: 0010:[8049b393] [8049b393] __mutex_lock_slowpath+0x34/ 0xa2 RSP: 0018:880132ca9b90 EFLAGS: 00010246 RAX: RBX: a03d9708 RCX: 0002 RDX: RSI: 880132ca9c18 RDI: a03d970c RBP: a03d970c R08: 880132ca9ca7 R09: 0001 R10: R11: R12: 8801385fa740 R13: a03d9710 R14: a03d96d0 R15: FS: 7f7b741746f0() GS:80a40080() knlGS: CS: 0010 DS: ES: CR0: 8005003b CR2: CR3: 00013a16f000 CR4: 06e0 DR0: DR1: DR2: DR3: DR6: 0ff0 DR7: 0400 Process modprobe (pid: 3994, threadinfo 880132ca8000, task 8801385fa740) Stack: a03d9710 880132ca9cc8 a03d79f0 880132ca9ca7 a03d96d0 0002 880132ca9c18 a03d96d0 8049b33f a0190519 Call Trace: [8049b33f] mutex_lock+0xa/0xb [a0190519] i2c_transfer+0x56/0xd1 [i2c_core] [a03d6252] i2c_read+0x48/0x67 [stb0899] [a03d62bf] Read8Direct+0x4e/0x99 [stb0899] [a03d7569] stb0899_attach+0x139/0x348 [stb0899] [a03cfa3a] pctv452e_frontend_attach+0x5e/0x206 [dvb_usb_pctv452e] [a03c8e94] dvb_usb_adapter_frontend_init+0x33/0xf5 [dvb_usb] [a03c89ab] dvb_usb_device_init+0x4de/0x5c7 [dvb_usb] [a00f78e0] usb_probe_interface+0x1a8/0x1df [usbcore] [803e65b7] really_probe+0xdd/0x1e5 [803e67a4] __driver_attach+0x46/0x6d [803e5d82] bus_for_each_dev+0x44/0x78 [803e5686] bus_add_driver+0xf4/0x224 [803e6962] driver_register+0x9c/0x103 [a00f7af7] usb_register_driver+0x7e/0xe0 [usbcore] [a019a01b] pctv452e_usb_init+0x1b/0x5c [dvb_usb_pctv452e] [80209041] _stext+0x41/0x110 [80260f76] sys_init_module+0xa0/0x1ba [8020bfbb] system_call_fastpath+0x16/0x1b
Re: [vdr] Problem: VDR seems to change the channel after long time viewing via VLC over xineliboutput
Am Mittwoch, den 08.07.2009, 12:35 +0200 schrieb Kai Kronschnabel: Hy experts, config: Core2Duo, same on Atom 330, 2GB, all new, OnBoard Intel VGA, same with ext. nvidia 8400 or 9600 (this is not the problem) VDR 1.7.8, Technisat Skystart HD2, s2-liplianin, xineliboutput Debian 5 2.6.26-2-686 i686 No local frontend, stream only to VLC 0.9.9 on Windows-Vista problem: After running the VLC client for about 5 to 8 hours the picture freeze and after restart VLC is runs only seconds. If I start vdr from the commandline this happends after the message now tuned to source ... transponder ... It seems to me that after some hours VDR forgotts that there is a client that need the channel exclusive. now tuned to source ... transponder ... is not seen after the first hours running vdr, except I manually change a channel via SVDRP. I have to restart VDR to get a usable system back for some hours. Try to disable EPG scan. Menu - Settings - EPG - EPG Scan timeout A value of 0 disables the EPG Scan. If it is enabled VDR runs an EPG scan after x hours of user inactivity. Am I right here? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdrconvert-vdr-1.7.0+
Am Sonntag, den 05.07.2009, 06:51 -0400 schrieb hu_emulator: Thank you for your help. Replaced vdr2dvd.sh with your, renamed to vdr2dvd.sh, rebooted. But still getting the following error: --- new File: '/video0/iso/tmp/vdr2dvd/9137/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.vTpfbc/001[1].mpa' summary of created media files: Video (m2v): 209 Frames 00:00:06.970 '/video0/iso/tmp/vdr2dvd/9137/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.v$ Audio 0 (mp2): 290 Frames 00:00:06.9600/0/0/0 '/video0/iso/tmp/vdr2dvd/9137/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.v$ Audio 1 (mp2): 290 Frames 00:00:06.9600/0/0/0 '/video0/iso/tmp/vdr2dvd/9137/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.v$ = 1,123,980 bytes written... - we have 7361 warnings/errors. done...1 collection(s) processed @ 00:01:33.544 Enter do_transcode Enter do_prepare_titelmenu Enter do_mplex ERROR : Keine Audiospuren NOTICE : exit! Aufruf /usr/local/bin/postvdr2dvd.sh mit parameter : 05-07-2009 01:29:04 : Session /usr/local/bin/vdr2dvd.sh Exit what is the primary language in your dvb stream? Is ist en(glish)? if it is NOT de (german) then try to change in line 153: . DVDUSESTREAMS=dpid1:ac3+de apid1:mp2 de to . DVDUSESTREAMS=dpid1:ac3+en apid1:mp2 en or what ever the correct code of your language is. Just a shot into the dark. Falk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdrconvert-vdr-1.7.0+
Am Freitag, den 03.07.2009, 18:03 -0400 schrieb hu_emulator: I am still waiting for anyone to help on this. If you have a known working vdr2dvd.sh that works with projectX could you please make it available. Or if you have one that works with vdrsync I can use that too. Thank you in advance, I have attached vdr2dvdTS.sh. This is known to work with ProjectX. No guarantee. - Original Message - From: hu_emulator hu_emula...@hotmail.com To: VDR Mailing List vdr@linuxtv.org Sent: Sunday, June 28, 2009 9:32 AM Subject: Re: [vdr] vdrconvert-vdr-1.7.0+ Heres my final errors: - add frames Audio PTS: first packet 06:58:29.361, last packet 08:42:03.105 Video PTS: start 1.GOP 06:58:29.768, end last GOP 08:37:00.640 - adjusting audio at video-timeline - src_audio: MPEG-1, Layer2, 48000Hz, stereo, 160kbps, noCRC @ 00:00:00.000 ^M2 %^M3 %^M4 %^M5 %^M6 %^M7 %^M8 %^M9 %^M10 %^M11 %^M12 %^M13 %^M14 %^M15 %^M16 %^M17 %^M18 %^M19 %^M20 %^M21 %^M22 %^M23 %^M24 %^M25 %^M26 %^M27 %^M28$ --- new File: '/video0/iso/tmp/vdr2dvd/11498/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.mKDQY1/001[1].mpa' summary of created media files: Video (m2v): 209 Frames 00:00:06.970 '/video0/iso/tmp/vdr2dvd/11498/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.mKDQY1/001.mpv' Audio 0 (mp2): 290 Frames 00:00:06.9600/0/0/0 '/video0/iso/tmp/vdr2dvd/11498/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.mKDQY1/001.mpa' Audio 1 (mp2): 290 Frames 00:00:06.9600/0/0/0 '/video0/iso/tmp/vdr2dvd/11498/%Day_the_Earth_Stood_Still_(All_Day)_/VDRSYNC.mKDQY1/001[1].mpa' = 1,123,980 bytes written... - we have 3687 warnings/errors. done...1 collection(s) processed @ 00:01:43.382 Enter do_transcode Enter do_prepare_titelmenu Enter do_mplex ERROR : Keine Audiospuren NOTICE : exit! Aufruf /usr/local/bin/postvdr2dvd.sh mit parameter : 28-06-2009 09:20:47 : Session /usr/local/bin/vdr2dvd.sh Exit Any suggestions? Thanks, - Original Message - From: Falk Spitzberg p...@spitzberg.de To: VDR Mailing List vdr@linuxtv.org Sent: Friday, June 26, 2009 4:19 AM Subject: Re: [vdr] vdrconvert-vdr-1.7.0+ Am Freitag, den 26.06.2009, 09:43 +0200 schrieb Falk Spitzberg: Am Donnerstag, den 25.06.2009, 21:50 +0200 schrieb Martin Gansser: I have also tested your patch with vdrconvert-0.2.0 but with a few Extensions in vdr2dvd.sh. The final error message in vdr2dvd.log says, that no audio traces exists. Oops, i compared my hacked version with the wrong file. Here a diff against the original vdr2dvd.sh from vdrconvert-0.2.1 My hack assumes that you are using ProjectX. Sorry for the confusion! Falk Diff file attached Am Mittwoch, den 24.06.2009, 17:41 -0400 schrieb hu_emulator: I edited your changes and when I run vdrconvert with the new vdr2dvd.sh it errors out. Could you post or make available your vdr2dvd.sh? What kind of error do you get? ___ 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 -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ 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 mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de vdr2dvdTS.sh.bz2 Description: application/bzip ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdrconvert-vdr-1.7.0+
Am Donnerstag, den 25.06.2009, 21:50 +0200 schrieb Martin Gansser: I have also tested your patch with vdrconvert-0.2.0 but with a few Extensions in vdr2dvd.sh. The final error message in vdr2dvd.log says, that no audio traces exists. Oops, i compared my hacked version with the wrong file. Here a diff against the original vdr2dvd.sh from vdrconvert-0.2.1 My hack assumes that you are using ProjectX. Sorry for the confusion! Falk Am Mittwoch, den 24.06.2009, 17:41 -0400 schrieb hu_emulator: I edited your changes and when I run vdrconvert with the new vdr2dvd.sh it errors out. Could you post or make available your vdr2dvd.sh? What kind of error do you get? ___ 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] vdrconvert-vdr-1.7.0+
Am Mittwoch, den 24.06.2009, 17:41 -0400 schrieb hu_emulator:
I edited your changes and when I run vdrconvert with the new vdr2dvd.sh it
errors out. Could you post or make available your vdr2dvd.sh?
What kind of error do you get?
- Original Message -
From: Falk Spitzberg p...@spitzberg.de
To: VDR Mailing List vdr@linuxtv.org
Sent: Wednesday, June 24, 2009 5:59 AM
Subject: Re: [vdr] vdrconvert-vdr-1.7.0+
Am Dienstag, den 23.06.2009, 19:23 -0400 schrieb hu_emulator:
Does anyone have a modded vdrconvert script that will convert the new .ts
files that vdr-1.7.0+ now saves?
I have changes only for the conversion to DVD, here the diff between the
standard- and the TS version of vdr2dvd.sh:
1124c1121
local vdrfiles=`$LS $i/[0-9]*.vdr`
---
local vdrfiles=`$LS $i/[0-9]*.ts`
1175c1172
nice -n ${PRIO} cat $i/[0-9]*.vdr
${UniqueDir[Number]}/1.vdr
---
nice -n ${PRIO} cat $i/[0-9]*.ts
${UniqueDir[Number]}/1.vdr
cap.sh also needs a change, which works for all conversions
1124c1121
local vdrfiles=`$LS $i/[0-9]*.vdr`
---
local vdrfiles=`$LS $i/[0-9]*.ts`
1175c1172
nice -n ${PRIO} cat $i/[0-9]*.vdr
${UniqueDir[Number]}/1.vdr
---
nice -n ${PRIO} cat $i/[0-9]*.ts
${UniqueDir[Number]}/1.vdr
Hope, it helps.
Thanks
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
Falk Spitzberg
Tel: +49 5242 901626
E-Mail: p...@spitzberg.de
___
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
--
Falk Spitzberg
Tel: +49 5242 901626
E-Mail: p...@spitzberg.de
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdrconvert-vdr-1.7.0+
Am Dienstag, den 23.06.2009, 19:23 -0400 schrieb hu_emulator:
Does anyone have a modded vdrconvert script that will convert the new .ts
files that vdr-1.7.0+ now saves?
I have changes only for the conversion to DVD, here the diff between the
standard- and the TS version of vdr2dvd.sh:
1124c1121
local vdrfiles=`$LS $i/[0-9]*.vdr`
---
local vdrfiles=`$LS $i/[0-9]*.ts`
1175c1172
nice -n ${PRIO} cat $i/[0-9]*.vdr
${UniqueDir[Number]}/1.vdr
---
nice -n ${PRIO} cat $i/[0-9]*.ts
${UniqueDir[Number]}/1.vdr
cap.sh also needs a change, which works for all conversions
1124c1121
local vdrfiles=`$LS $i/[0-9]*.vdr`
---
local vdrfiles=`$LS $i/[0-9]*.ts`
1175c1172
nice -n ${PRIO} cat $i/[0-9]*.vdr
${UniqueDir[Number]}/1.vdr
---
nice -n ${PRIO} cat $i/[0-9]*.ts
${UniqueDir[Number]}/1.vdr
Hope, it helps.
Thanks
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
--
Falk Spitzberg
Tel: +49 5242 901626
E-Mail: p...@spitzberg.de
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] ExtensionHD and VDR 1.7.6
Hello, i recently built a vdr-1.7.6 + reelbox pluging, following the vdr-wiki for VDR DVB-S2 on OpenSuse. Everything was build properly, but unfortunately the eHD freezes after a few Minutes (not only when replaying recordings, but also with live TV). I know that there are some problems concerning the new TS format of VDR. Does anyone have a solution for this problem? I don't like the idea to use VDR 1.7.0 or an even older version. Any help is greatly appreceated. -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] ExtensionHD and VDR 1.7.6
Am Donnerstag, den 28.05.2009, 17:50 +0300 schrieb Josce: Falk Spitzberg wrote: Hello, i recently built a vdr-1.7.6 + reelbox pluging, following the vdr-wiki for VDR DVB-S2 on OpenSuse. Everything was build properly, but unfortunately the eHD freezes after a few Minutes (not only when replaying recordings, but also with live TV). I know that there are some problems concerning the new TS format of VDR. Does anyone have a solution for this problem? I don't like the idea to use VDR 1.7.0 or an even older version. Any help is greatly appreceated. Hello, I installed vdr-1.7.6 + reelbox plugin a week ago using: http://www.vdr-wiki.de/wiki/index.php/OpenSUSE_VDR_DVB-S2#openSUSE_VDR_DVB-S2_-_Teil2.1:_eHD which propably is the one you are refering to. Then I applied the vdr-1.7.6-1.7.7.diff patch which worked except that I had to change the osd.h file a little for the patch to run without complaints. There is some memory leak problem with vdr-1.7.7 but Klaus is looking into it, see: http://www.linuxtv.org/pipermail/vdr/2009-May/020636.html I got it also up an running with VDR-1.7.7 in the meantime. And I finally tested with 1.7.0 wich is known to work pretty stable with the eHD. All three versions show the same problem. It works for a few Minutes and then the eHD freezes. Since this happens with three different sofware setups, and because the eHD is always kompletly dead (it needs a power off to restart), i also suspected a hardware problem. I placed a Fan next to the card and, guess what, ... it works for more than an hour right now... and still running. Reelbox plugin still occasionally freezes, but so it has always done. The reelbox plugin is of course a joke and I deeply regret buying the card from Reel-Multimedia. Hopefully the VDPAU is more promising. BR, Josce ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR-1.7.7 Video aspect ratios
Am Montag, den 04.05.2009, 14:13 +0200 schrieb Nicolas Huillard:
Rolf Ahrenberg a écrit :
On Sun, 3 May 2009, Tomas Berglund wrote:
Do you mean aspect ratio 2.21:1 ?
+const char *VideoAspectString[] = { 4:3,
+16:9,
+2.21:9
+ };
Besides of that typo, there're plenty of video aspect ratios missing:
1:1, 12:11, 10:11, 16:11, 40:33, 24:11, 20:11, 32:11, 80:33, 18:11,
15:11, 64:33, 160:99, 3:2, 2:1.
16:10 is also a common device aspect ratio these days ;-)
It may be a common aspect ratio for display devices, but not for video
material. Movies and TV shows are mostly produced in 4:3, 16:9 or
2.21:1.
The OSD should adopt to the size of the video material. If that is
scaled to some non TV screen size, the OSD is scaled by the same factor.
Anyway, I'm not very fond of this new interface addition. After a little
playing with xineliboutput plugin in the past, the OSD scaling to video
size is a total mess and hence the HUD mode was developed, where the
OSD resolution is the same as the output resolution and the video is
scaled to that resolution. I'd strongly suggest to implement
cDevice::GetOSDSize(), so the output plugins can correctly set their
OSD resolution with minimal scaling artefacts.
I strongly second that. Add the fact that some (most ?) of the channels
here mess / cheat with aspect ratio / resolution, and I currently (VDR
1.6, SDTV, xineliboutput) have a unextricable aspect/resolution/OSD
problem. I'm not even trying to solve it...
I'd also suggest the maximum OSD size is 1920x1200 instead of 1920x1080,
as this 16:10 resolution is very common in computer land. That's also
the maximum a DVI single link can output.
--
Falk
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Where do you live and what kind of broadcast do you receive?
Country: Germany Transmission: DVB-S(DVB-S2 on Test system) Encoding: MPEG-2 for SD, h.264 for HD Falk ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Forthcoming VDR Release To Support VDPAU (???)
Am Dienstag, den 10.03.2009, 11:08 +0100 schrieb Klaus Schmidinger: On 03/10/09 10:54, Morfsta wrote: On Mon, Mar 9, 2009 at 11:34 PM, Klaus Schmidinger klaus.schmidin...@cadsoft.de wrote: Why should any special output device get support in VDR core, if I'm permanently being pestered to remove even support for DVB devices from the core code? Is core VDR still being developed? I'm currently working on making it ready for HDTV. Hi Klaus, i am using VDR since it's first days, but wasn't active in the list for several years. I've experimented with HDTV and VDR 1.7.4. Looks quite promising. Will it have native support for the eHD card or will the Reel - plugin still be needed in future versions? Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Crash VDR-1.7.4
I am using vdr-1.7.4, driver se-liplianin, Two DVB-S cards (TT S2-3600 USB and a FF Technotrend ) For several hours everything went fine including several recordings. When the last recording ended, suddely video and audio showed almost only distortions. VDR itself still reacted properly to remote control input, but audio/video did'restore. This is an extract from the log: Mar 9 22:17:00 linuxvdr vdr: [4483] recording thread ended (pid=18876, tid=4483) Mar 9 22:17:00 linuxvdr vdr: [26685] TS buffer on device 2 thread ended (pid=18876, tid=26685) Mar 9 22:17:00 linuxvdr vdr: [26684] buffer stats: 112612 (5%) used Mar 9 22:17:00 linuxvdr vdr: [26684] receiver on device 2 thread ended (pid=18876, tid=26684) Mar 9 22:17:00 linuxvdr vdr: [18876] buffer stats: 212440 (4%) used Mar 9 22:17:00 linuxvdr vdr: [18876] timer 2 (6 2136-2217 'Die Simpsons') stop Mar 9 22:17:01 linuxvdr vdr: [18876] cleaning up schedules data Mar 9 22:18:29 linuxvdr vdr: [18876] deleting timer 2 (6 2136-2217 'Die Simpsons') Mar 9 22:18:51 linuxvdr vdr: [18885] frontend 1 timed out while tuning to channel 53, tp 111362 Mar 9 22:18:58 linuxvdr vdr: [7926] buffer usage: 70% (tid=7924) Mar 9 22:18:58 linuxvdr vdr: [7926] buffer usage: 60% (tid=7924) Mar 9 22:18:58 linuxvdr vdr: [7926] buffer usage: 70% (tid=7924) Mar 9 22:18:58 linuxvdr vdr: [7926] buffer usage: 80% (tid=7924) Mar 9 22:18:59 linuxvdr vdr: [7926] buffer usage: 90% (tid=7924) Mar 9 22:18:59 linuxvdr vdr: [7926] buffer usage: 100% (tid=7924) Mar 9 22:19:03 linuxvdr vdr: [7926] ERROR: driver buffer overflow on device 1 Mar 9 22:19:07 linuxvdr vdr: [7924] ERROR: skipped 11 bytes to sync on TS packet on device 1 Mar 9 22:19:07 linuxvdr vdr: [7926] ERROR: driver buffer overflow on device 1 Mar 9 22:19:11 linuxvdr vdr: [7924] ERROR: skipped 11 bytes to sync on TS packet on device 1 Mar 9 22:19:12 linuxvdr vdr: [7926] ERROR: driver buffer overflow on device 1 Mar 9 22:19:15 linuxvdr vdr: [7924] ERROR: skipped 11 bytes to sync on TS packet on device 1 Mar 9 22:19:18 linuxvdr vdr: [7926] ERROR: driver buffer overflow on device 1 Mar 9 22:19:22 linuxvdr vdr: [7924] ERROR: skipped 11 bytes to sync on TS packet on device 1 Mar 9 22:19:23 linuxvdr vdr: [7926] ERROR: driver buffer overflow on device 1 -- Falk Spitzberg Tel: +49 5242 901626 E-Mail: p...@spitzberg.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
