Re: [vdr] Wakeup methods

2008-02-11 Thread Detlef Heine
Kartsa schrieb:
 Rainer Zocholl kirjoitti:
 [EMAIL PROTECTED](Kartsa)  10.02.08 10:37
   
 What different wakeupmethods are there? I've built a few vdr boxes and
 I've been forced to use different motherboards and they do not all
 work the same. I've used nvram-wakeup on some and acpi on others when
 nvram-wakeup has not worked. Now I have Biostar 945GZ 775 SE with
 which I'm having trouble in starting on timers.
 
 What problems? Be spezific.
   
 At the time writing I was not really asking help, just qurious what 
 methods people use. This is why I did not put any detailed info. Maybe I 
 should not have mentioned about problems I at that time.
 
 Now I see that I should have added more info because I'm not yet happy 
 with my settings. I would have used acpi and it was my first attempt but 
 the board did not wake up.
 
 from vdr-shutdown.sh
 ---
 file=/var/lib/vdr/acpi-wakeup
 rm -f $file
 if [ ${1:-0} -gt 0 -a -e /proc/acpi/alarm ] ; then
 date -d 1970-01-01 UTC $1 sec -$delay min +%Y-%m-%d %H:%M:%S  $file
 fi
 exec sudo /sbin/shutdown -h now
 
 
 and from halt.local (this is what is instructed in vdr README.package)
 
 #!/bin/bash
 wakeupfile=/var/lib/vdr/acpi-wakeup
 trap rm -f $wakeupfile EXIT
 if [ -s $wakeupfile -a -w /proc/acpi/alarm ] ; then
 echo -n Setting ACPI wakeup for next VDR timer:  ; cat $wakeupfile
 cat $wakeupfile  /proc/acpi/alarm
 fi
 ---
 But it does not wake up. And this is not a very old mb. So I assume I am 
 doing something wrong or not doing something I should.
 I got it to boot up using nvram-wakeup with reboot option (after guess 
 helper). But as said nvram should be obsolete and replaced by acpi.
 
 On another mb (4CoreDual-Sata23) I used
 ---
 newtime=$(($1 - delay*60 ))   # delay minutes earlier
 echo $newtime  /sys/class/rtc/rtc0/wakealarm
 ---
 which did the trick.
 
 On biostar there were no /sys/class/rtc
 
 So I tried from http://www.vdr-wiki.de/wiki/index.php/ACPI_Wakeup (as 
 someone mentioned in this thread)
 
 --
 #!/bin/bash
 
 # Startet dem Rechner nach 3 min ueber acpi neu. 
 
 min=`date +%M`
 nextmin=`expr $min + 3`
 nextboot=`date +%Y-%m-%d %H:$nextmin:00`
 echo $nextboot  /proc/acpi/alarm
 
 echo Aktuelle Zeit: `date +%Y-%m-%d %H:%M:%S`
 echo Starte Rechner neu um: `cat /proc/acpi/alarm`
 echo Fahre Rechner nun runter. 
 
 busybox poweroff
 #/usr/bin/poweroff.pl
 #poweroff 
 ---
 
 I  can read germany but I do not understand it :). But understood that I 
 could use that script to test acpi. Well this did not work. I did check 
 that the time was actually written in /proc/acpi/alarm. Still not waking up.
 
 So where do I go here? Do I use nvram-wakeup which IMHO is not good 
 because of the reboot.
 
 \\Kartsa
 
 ___
 vdr mailing list
 vdr@linuxtv.org
 http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
 
Hallo,
yum MUST disable RTC-Wakeup in the BIOS of your motherboard. In my case I MUST 
write the wakeuptime 
twice:

example:

if [ ! -z $1 ]; then
   newtime=$(($1 - 60 ))   # 1 minutes earlier
   logger VDR-Timer: $1
   logger BIOS-Timer: $newtime
   echo $(/bin/unix2iso8601 -u $newtime) /proc/acpi/alarm
   echo $(/bin/unix2iso8601 -u $newtime) /proc/acpi/alarm
   logger ACPI-Read: $(cat /proc/acpi/alarm)
else
   logger VDR-Timer: keine Zeitübergabe
fi


dhe.
-- 
 __\/__
 .  / ^  _ \  .
 |\| (o)(o) |/|
   #.OOOo--oo--oOOO.---#
   #   #
   # [EMAIL PROTECTED]   #
   #   #
   #_Oooo._#
 .oooO   (   )
 (   )) /
  \ ((_/
   \_)

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.7.22

2011-12-05 Thread Detlef Heine

- The new setup options LNB/Device n connected to sat cable can be
used to define
which DVB-S devices are connected to the same sat cable and are
therefore bonded.
This obsoletes the LNBSHARE patch. Users of the LNBSHARE patch will need
to newly
set up their sat devices with the above options.


Hello Klaus,
I have much trouble with the new added Feature from above.
My vdr have a S2-6400 card and 1 cable with an splitter for the 2 frondends.
I have set up the options correctly. But, specifically on Pro7, the 
picture and sound freeze after some seconds. The vdr-log show in this 
moment lines like this:


Dec  5 19:24:31 hd-vdr vdr: [1628] changing pids of channel 1435 from 
511+511=2:512=deu@3;515=deu@106:0:32 to 
511+511=2:512=deu@3,513=eng@3;515=deu@106:0:32
Dec  5 19:24:31 hd-vdr vdr: [1628] changing pids of channel 1440 from 
2815+2815=2:2816=deu@3;2819=deu@106:0:32 to 
2815+2815=2:2816=deu@3,2817=eng@3;2819=deu@106:0:32
Dec  5 19:24:51 hd-vdr vdr: [1628] changing pids of channel 1512 from 
767+767=27:0;771=deu@106,772=eng@106:0:32 to 
767+767=27:0;771=deu@106,772=eng@106:0:32
Dec  5 19:24:51 hd-vdr vdr: [1628] changing pids of channel 1513 from 
1023+1023=27:0;1027=deu@106:0:32 to 1023+1023=27:0;1027=deu@106:0:32
Dec  5 19:24:52 hd-vdr vdr: [1628] changing pids of channel 1514 from 
1279+1279=27:0;1283=deu@106:0:32 to 1279+1279=27:0;1283=deu@106:0:32
Dec  5 19:24:52 hd-vdr vdr: [1628] changing pids of channel 1511 from 
511+511=27:0;515=deu@106,516=eng@106:0:32 to 
511+511=27:0;515=deu@106,516=eng@106:0:32
Dec  5 19:25:12 hd-vdr vdr: [1628] changing pids of channel 1444 from 
767+767=27:0;771=deu@106,772=eng@106:0:32 to 
767+767=27:0;771=deu@106,772=eng@106:0:32
Dec  5 19:25:12 hd-vdr vdr: [1628] changing pids of channel 1442 from 
1023+1023=27:0;1027=deu@106:0:32 to 1023+1023=27:0;1027=deu@106:0:32
Dec  5 19:25:13 hd-vdr vdr: [1628] changing pids of channel 1441 from 
1279+1279=27:0;1283=deu@106:0:32 to 
1279+1279=27:0;1283=deu@106,1284=eng@106:0:32
Dec  5 19:25:13 hd-vdr vdr: [1628] changing pids of channel 1443 from 
1535+1535=27:0;1539=deu@106:0:32 to 1535+1535=27:0;1539=deu@106:0:32


With the LNBSHARE patch and vdr-1.7.21 I had no problems like this.

How can I fix this?

Thanks, Detlef.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] [ANNOUNCE] VDR developer version 1.7.22

2011-12-07 Thread Detlef Heine

Am 06.12.2011 18:42, schrieb Klaus Schmidinger:


Do you have only two deivces that share a cable, or is there
a third one? There is a bug with more than two devices that
share one cable.

Please try this:

--- dvbdevice.c 2011/12/03 15:24:27 2.48
+++ dvbdevice.c 2011/12/06 17:38:18
@@ -1126,7 +1126,7 @@
if (cDevice *Device2 = cDevice::GetDevice(d)) {
if (cDvbDevice *DvbDevice1 = dynamic_castcDvbDevice *(Device1)) {
if (cDvbDevice *DvbDevice2 = dynamic_castcDvbDevice *(Device2)) {
- if (!DvbDevice2-Bond(DvbDevice1))
+ if (!DvbDevice1-Bond(DvbDevice2))
return false; // Bond() has already logged the error
}
else

Klaus

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



It´s the same. But I think the 3rd device is the problem. I had used a 
very ugly plugin. Without this plugin everything is OK.

Thank you for your quick response.

Detlef.

___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] integrating jumpplay-patch

2014-03-31 Thread Detlef Heine

On my recordings the last mark is everytime correct.
And the playback stops there. Everything is fine.
I think the idea of Peter are great.

Detlef.

Am 31.03.2014 11:59, schrieb Matthias Fechner:

Am 31.03.14 11:39, schrieb Peter Münster:

What about integrating the jumpplay-patch
(http://www.vdr-wiki.de/wiki/index.php/Jumpplay-patch) into the
VDR developer version?


I wish the patch whould not stop the playback on the last mark, as the
last mark is in many cases not correct.


Gruß,
Matthias

attachment: detlef_heine.vcf

smime.p7s
Description: S/MIME Cryptographic Signature
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


[vdr] issue with vdr-plugin-graphlcd

2018-11-05 Thread Detlef Heine
Hello,

I have an issue with vdr-plugin-graphlcd. I can easily compile everything. But 
when I start VDR, I
get the following:

/usr/sbin/vdr --grab=/tmp --no-kbd --shutdown=vdr-shutdown.sh
--plugin=dvbhddevice --plugin=graphlcd -l 3.7
/usr/include/c++/8/bits/basic_string.h:1039:
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::const_reference
std::__cxx11::basic_string<_CharT, _Traits,
_Alloc>::operator[](std::__cxx11::basic_string<_CharT, _Traits,
_Alloc>::size_type) const [with _CharT = char; _Traits =
std::char_traits; _Alloc = std::allocator;
std::__cxx11::basic_string<_CharT, _Traits, _Alloc>::const_reference =
const char&; std::__cxx11::basic_string<_CharT, _Traits,
_Alloc>::size_type = long unsigned int]: Assertion '__pos <= size()' failed.


System:
 Fedora 28
 gcc-8.2.1-4.fc28.x86_64
 gcc-c++-8.2.1-4.fc28.x86_64
 vdr-2.2.0-14.fc28.x86_64 (from Fedora)
 graphlcd-base (https://projects.vdr-developer.org/git/graphlcd-base.git/)
 vdr-plugin-graphlcd 
(https://projects.vdr-developer.org/git/vdr-plugin-graphtftng.git/)

Any idea?

Greetings, kuppe.
<>

signature.asc
Description: OpenPGP digital signature
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr


Re: [vdr] TT S2 6400 IR Remote

2018-09-16 Thread Detlef Heine
Here it is:

remote-ir.Up 00010001000E
remote-ir.Down   000100010012
remote-ir.Menu   000100010028
remote-ir.Ok 000100010010
remote-ir.Back   000100010014
remote-ir.Left   00010001000F
remote-ir.Right  000100010011
remote-ir.Red000100010015
remote-ir.Green  000100010016
remote-ir.Yellow 000100010017
remote-ir.Blue   000100010018
remote-ir.0  00010001000D
remote-ir.1  000100010004
remote-ir.2  000100010005
remote-ir.3  000100010006
remote-ir.4  000100010007
remote-ir.5  000100010008
remote-ir.6  000100010009
remote-ir.7  00010001000A
remote-ir.8  00010001000B
remote-ir.9  00010001000C
remote-ir.Info   000100010013
remote-ir.Pause  000100010056
remote-ir.Stop   000100010036
remote-ir.Record 000100010054
remote-ir.FastFwd000100010057
remote-ir.FastRew000100010055
remote-ir.Next   000100010031
remote-ir.Prev   000100010048
remote-ir.Power  000100010002
remote-ir.Channel+   000100010024
remote-ir.Channel-   000100010025
remote-ir.Volume+000100010026
remote-ir.Volume-000100010027
remote-ir.Mute   000100010019
remote-ir.Audio  00010001001B
remote-ir.Channels   000100010032
remote-ir.Recordings 000100010047
remote-ir.Setup  00010001001C
remote-ir.User0  000100010022
remote-ir.User1  000100010003
remote-ir.User2  00010001001A
remote-ir.User3  000100010023


Am 13.09.18 um 12:27 schrieb Richard Scobie:
> If there is anyone using the TT S2 6400 with the supplied IR receiver,
> remote and the "remote" plugin, could they please post a few lines from
> the remote.conf file?
> 
> Thanks,
> 
> Richard
> 
> ___
> vdr mailing list
> vdr@linuxtv.org
> https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr



signature.asc
Description: OpenPGP digital signature
___
vdr mailing list
vdr@linuxtv.org
https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr