Re: [vdr] [ANNOUNCE] 0.1.0
Hi Rene, how do you start the xineliboutput plugin? To get a true color osd, you have to start it with --hud. I think this is your problem... If this is not working, you could also try to use softhddevice as output plugin. softhddevice supports true color anyway, so you could see if you have another issue maybe... Cheers Louis PS: sorry for the html mail, damn new gmx webinterface :-) Gesendet: Mittwoch, 20. März 2013 um 23:55 Uhr Von: René linu...@hertell.com An: VDR Mailing List vdr@linuxtv.org Betreff: Re: [vdr] [ANNOUNCE] 0.1.0 Hi Louis, I tried the plugin on vdr 1.7.41, but i don't get the OSD working (osd is blank). I run my vdr on Ubuntu, and I use xineliboutput. Could it be some libraries that i'm missing? Regards, René On 13.03.2013 16:52 , Stefan Braun wrote: Hi, One additional technical remark: the skin uses intensively the eMenuCategory enumeration introduced in VDR 1.7.34 to determinate which menu has to be displayed and if this menu should be displayed narrowly or in default style. So plugins like epgsearch or extrecmenu which replace VDR menus also have to set correct MenuCategories to be displayed correctly by the skin. In the newest versions of these plugins this is already implemented, so you should use always the latest git version of these plugins. One remaining issue with older plugins which are not already adapted to this new behaviour is the following: in plugins with dedicated setup menus which inherit from cMenuSetupPage the menu category mcSetup is set by the constructor of VDRs cMenuSetupPage, but this category should only be used by the main setup menu from VDR (which is diplayed narrow by default in the skin). To solve this, in the constructors of these plugin menus a different menu category (for instance mcSetupPlugins) has to be set via a call to SetMenuCategory: SetMenuCategory(mcSetupPlugins); Cheers Louis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr -- René Hertell Mäntytie 19 00270 Helsinki Finland TEL: +358 (0)9 135 1477 GSM: +358 (0)50 64 447 Fax: +358 (0)9 135 4001 VOIP: r...@voip.hertell.com ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr[http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
On 21 March 2013 09:04, Teemu Suikki tsui...@zuik.org wrote: I have mysterious problem with some channels.. All seem to be on S13.0E, but on different transponders. According to http://en.kingofsat.net/pos-13E.php page, Disney Channel HD Italia is DVB-S2, 8PSK, SR 29900. However, I seem to have DVB-S, QPSK, SR 27500 in my channels.conf. Is the transponder sending incorrect data, or what is going on? What card(s) are you using? I have seen problems with TT-S2-3200 on other mailing lists / forums. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
On 21.03.2013 10:04, Teemu Suikki wrote: Hi! I have mysterious problem with some channels.. All seem to be on S13.0E, but on different transponders. According to http://en.kingofsat.net/pos-13E.php page, Disney Channel HD Italia is DVB-S2, 8PSK, SR 29900. However, I seem to have DVB-S, QPSK, SR 27500 in my channels.conf. I have tried editing the channel directly to channels.conf, while vdr stopped. Also I have tried editing it inside vdr, from channel list - edit.. After the edit, channels shows fine for a few seconds, but then VDR updates it back to old values and channel stops showing! Mar 21 10:41:53 yavdr vdr: [16964] edited channel 179 Disney Ch. HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701: 919,93B,9CD:4128:318:7501:0 Mar 21 10:41:56 yavdr vdr: [16964] switching to channel 179 Here's the result of a test I ran on my VDR (TT S2-6400). I took your original channel entry and set the CA parameter to 0 (since I don't have a CAM/Smartcard for that channel), created a new channel and switched to it: newc Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 chan 3364 250 3364 Disney Ch.HD The PIDs and CA-IDs were changed automatically: Mar 21 12:11:23 vdr2 vdr: [29620] new channel 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=eng@106:701:0:4128:318:7501:0 Mar 21 12:11:32 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:34 vdr2 vdr: [29626] changing pids of channel 3364 from 164+164=27:0;416=ita@106,417=eng@106:0:701 to 164+164=27:0;416=ita@106,417=und@106:0:701 Mar 21 12:11:34 vdr2 vdr: [29626] changing caids of channel 3364 from 0 to 919,93B,9CD Mar 21 12:11:34 vdr2 vdr: [29620] retuning due to modification of channel 3364 Mar 21 12:11:34 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:34 vdr2 vdr: [29620] info: Channel not available! lstc 3364 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M5O0S1:S13.0E:29900:164=27:0;416=ita@106,417=und@106:701:919,93B,9CD:4128:318:7501:0 A few seconds later, the transponder data was changed: Mar 21 12:11:53 vdr2 vdr: [29626] changing transponder data of channel 3364 from 12207:HC34M5O0S1:S13.0E:29900 to 12207:HC34M2S0:S13.0E:27500 Mar 21 12:11:53 vdr2 vdr: [29620] retuning due to modification of channel 3364 Mar 21 12:11:53 vdr2 vdr: [29620] switching to channel 3364 Mar 21 12:11:53 vdr2 vdr: [29620] info: Channel not available! lstc 3364 250 3364 Disney Ch.HD;SkyItalia:12207:HC34M2S0:S13.0E:27500:164=27:0;416=ita@106,417=und@106:701:919,93B,9CD:4128:318:7501:0 You may want to use a tool like dvbsnoop and check what is broadcast in the NIT of that provider. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Intermittent hangs when start playing a channel
On 18.03.2013 19:10, Andrey Pavlenko wrote: Hi, I've submitted an issue against the XVDR plugin, but seems it's VDR but not XVDR issue. Can someone, please, look at this https://github.com/pipelka/vdr-plugin-xvdr/issues/103? That recording plays just fine on my TT S2-6400 with VDR 1.7.41. Klaus ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] frontend invalid argument / frequency X out of range
On 18.03.2013 17:08, Dominic Evans wrote:
Running vdr 1.7.41
I have previously seen this issue on earlier development snapshots,
but had simply ignored it as I was running development code. However,
as we near 2.0, I thought I might query it on the mailing list.
In my syslog I occasionally see an error related to my DVB-S frontend
attempting to tune to an unusually high frequency:
Mar 18 16:51:43 ion vdr: [11405] ERROR: frontend 2/0: Invalid argument
Mar 18 16:51:43 ion kernel: [153047.448733] DVB: adapter 2 frontend 0
frequency 89399000 out of range (95..215)
There's no obviously bad entry in my channels.conf that would cause this:
$ awk -F: '/S28.2E/{print $2}' /etc/vdr/channels.conf | sort -n | uniq
| tr '\n' ', '
10714,10729,10743,10758,10773,10788,10802,10817,10832,10847,10861,10876,10891,10906,10920,10935,10964,10993,11023,11052,11126,11222,11223,11259,11261,11307,11343,11344,11390,11426,11469,11488,11507,11526,11546,11565,11584,11603,11623,11661,11680,11719,11739,11758,11778,11797,11817,11836,11856,11875,11895,11914,11934,11973,11992,12012,12031,12051,12090,12109,12148,12168,12187,12207,12226,12246,12265,12285,12304,12324,12343,12363,12382,12460,12480,12523,12559,12560,12606,12643
So I presume it is happening during a 'search for transponders' or an
epg update scan?
Maybe faulty data in the NIT?
You could start debugging this by adding some printouts to
cNitFilter::Process(),
around line 133, where the transponder frequency is decoded.
I do have an LNB pointed at S28.2E, too, and my channels.conf contains these
transponders:
10714,10729,10743,10758,10773,10788,10802,10817,10832,10847,10861,10876,10891,10906,10920,10935,11222,11223,11259,11261,11307,11343,11344,11390,11426,11469,11488,11507,11526,11546,11565,11584,11603,11604,11623,11681,11719,11739,11758,11778,11797,11817,11836,11856,11875,11895,11914,11934,11973,11992,12012,12031,12051,12070,12090,12109,12148,12168,12187,12207,12226,12246,12265,12285,12304,12324,12343,12363,12382,12460,12480,12523,12559,12560,12606,12643
I never had the error message you've posted, though.
What kind of DVB adapters are you using?
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
2013/3/21 Klaus Schmidinger klaus.schmidin...@tvdr.de: Mar 21 12:11:53 vdr2 vdr: [29626] changing transponder data of channel 3364 from 12207:HC34M5O0S1:S13.0E:29900 to 12207:HC34M2S0:S13.0E:27500 Mar 21 12:11:53 vdr2 vdr: [29620] retuning due to modification of channel Hi, ok, thanks for the confirmation! I tried dvbsnoop. It returns correct values (dvb-s2, sr 29900).. See below. Then I tried scan-s2 -c from the command line, and interestingly it reports correct SR 29900 but dvb-s, not dvb-s2.. Weird? - Transport_stream_ID: 7500 (0x1d4c) Original_network_ID: 64511 (0xfbff) [= Sky Italia | Sky Italia Spa.] reserved_1: 15 (0x0f) Transport_descriptor_length: 54 (0x0036) (...) DVB-DescriptorTag: 67 (0x43) [= satellite_delivery_system_descriptor] descriptor_length: 11 (0x0b) Frequency: 19007128 (= 12.20698 GHz) Orbital_position: 304 (= 13.0) West_East_flag: 1 (0x01) [= EAST] Polarisation: 0 (0x00) [= linear - horizontal] Kind: 1 (0x01) [= DVB-S2] Roll Off Faktor: 0 (0x00) [= Alpha 0.35] Modulation_type: 2 (0x02) [= 8PSK] Symbol_rate: 2723840 (= 29.9000) FEC_inner: 3 (0x03) [= 3/4 conv. code rate] -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
A bit more into this..
I tried dvbsnooping different satellites, I noticed some difference.
This is from Thor, 1.0W:
---
Transport_stream_ID: 4 (0x0004)
Original_network_ID: 70 (0x0046) [= 1 degree W | Telenor]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 191 (0x00bf)
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 17967360 (= 11.22900 GHz)
Orbital_position: 16 (= 1.0)
West_East_flag: 0 (0x00) [= WEST]
Polarisation: 0 (0x00) [= linear - horizontal]
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0 (0x00)
Modulation_type: 1 (0x01) [= QPSK]
Symbol_rate: 2379776 (= 24.5000)
FEC_inner: 5 (0x05) [= 7/8 conv. code rate]
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 30 (0x1e)
service_ID: 418 (0x01a2)[ -- refers to PMT program_number]
service_type: 1 (0x01) [= digital television service]
(other sid's follow, cut away for clarity)
But this faulty transponder in S13E:
Transport_stream_ID: 7500 (0x1d4c)
Original_network_ID: 64511 (0xfbff) [= Sky Italia | Sky Italia Spa.]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 54 (0x0036)
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 39 (0x27)
service_ID: 4117 (0x1015)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital
television service]
(other sid's follow, cut away for clarity)
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 19007128 (= 12.20698 GHz)
Orbital_position: 304 (= 13.0)
West_East_flag: 1 (0x01) [= EAST]
Polarisation: 0 (0x00) [= linear - horizontal]
Kind: 1 (0x01) [= DVB-S2]
Roll Off Faktor: 0 (0x00) [= Alpha 0.35]
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2723840 (= 29.9000)
FEC_inner: 3 (0x03) [= 3/4 conv. code rate]
So.. DVB-DescriptorTag's 65 and 67 appear in opposite order! Could it
be that VDR has transponder data still uninitialized when it is
scanning the service id, because 67 is not arrived yet?
--
Teemu Suikki
http://www.z-power.fi/
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] frontend invalid argument / frequency X out of range
Hey Klaus, On 21 March 2013 12:26, Klaus Schmidinger klaus.schmidin...@tvdr.de wrote: On 18.03.2013 17:08, Dominic Evans wrote: So I presume it is happening during a 'search for transponders' or an epg update scan? Maybe faulty data in the NIT? You could start debugging this by adding some printouts to cNitFilter::Process(), around line 133, where the transponder frequency is decoded. Thanks. I'll give this a try. What kind of DVB adapters are you using? http://www.linuxtv.org/wiki/index.php/Technisat_SkyStar_USB_HD ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
On 21.03.2013 14:07, Teemu Suikki wrote:
A bit more into this..
I tried dvbsnooping different satellites, I noticed some difference.
This is from Thor, 1.0W:
---
Transport_stream_ID: 4 (0x0004)
Original_network_ID: 70 (0x0046) [= 1 degree W | Telenor]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 191 (0x00bf)
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 17967360 (= 11.22900 GHz)
Orbital_position: 16 (= 1.0)
West_East_flag: 0 (0x00) [= WEST]
Polarisation: 0 (0x00) [= linear - horizontal]
Kind: 0 (0x00) [= DVB-S]
fixed ('00'): 0 (0x00)
Modulation_type: 1 (0x01) [= QPSK]
Symbol_rate: 2379776 (= 24.5000)
FEC_inner: 5 (0x05) [= 7/8 conv. code rate]
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 30 (0x1e)
service_ID: 418 (0x01a2)[ -- refers to PMT program_number]
service_type: 1 (0x01) [= digital television service]
(other sid's follow, cut away for clarity)
But this faulty transponder in S13E:
Transport_stream_ID: 7500 (0x1d4c)
Original_network_ID: 64511 (0xfbff) [= Sky Italia | Sky Italia Spa.]
reserved_1: 15 (0x0f)
Transport_descriptor_length: 54 (0x0036)
DVB-DescriptorTag: 65 (0x41) [= service_list_descriptor]
descriptor_length: 39 (0x27)
service_ID: 4117 (0x1015)[ -- refers to PMT program_number]
service_type: 25 (0x19) [= advanced codec HD digital
television service]
(other sid's follow, cut away for clarity)
DVB-DescriptorTag: 67 (0x43) [=
satellite_delivery_system_descriptor]
descriptor_length: 11 (0x0b)
Frequency: 19007128 (= 12.20698 GHz)
Orbital_position: 304 (= 13.0)
West_East_flag: 1 (0x01) [= EAST]
Polarisation: 0 (0x00) [= linear - horizontal]
Kind: 1 (0x01) [= DVB-S2]
Roll Off Faktor: 0 (0x00) [= Alpha 0.35]
Modulation_type: 2 (0x02) [= 8PSK]
Symbol_rate: 2723840 (= 29.9000)
FEC_inner: 3 (0x03) [= 3/4 conv. code rate]
So.. DVB-DescriptorTag's 65 and 67 appear in opposite order! Could it
be that VDR has transponder data still uninitialized when it is
scanning the service id, because 67 is not arrived yet?
I just checked, but VDR doesn't parse the service_list_descriptor. So it
shouldn't
matter whether it comes before or after the
satellite_delivery_system_descriptor.
Klaus
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Audio problem on Channel 4 HD on Freeview
The last two times I looked at Channel 4 HD on Freeview (DVB-T2) there was a strange problem with the audio. All the ambient sounds and background music were there but voices were very muffled. One time was a film and the other was a US drama series (Revenge). The same channel on Freesat (DVB-S2) was OK. This was on a remote client using xineliboutput + vdr-sxfe with analogue stereo audio. I just tried it on my main TV (also using vdr-sxfe but connecting to VDR on localhost) with HDMI audio, and the sound was normal on that, but it was a British cookery show. I don't know yet whether the difference was because of the type of programme or the respective PC's audio settings. I tried changing the stereo mix settings in VDR's xineliboutput plugin config, but one setting didn't do anything and the other turned it into a loud, harsh noise. Is this just the wrong audio stream being selected (I didn't think of trying to find an alternative stream at the time) or the player discarding channels instead of downmixing into stereo? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR's UpdateChannels destroys channel information
Guess what, problem solved.. My channels config had TID 7501, but the real TID is 7500.. I have no idea how this could have been changed, though? And I thought that the channel wouldn't show at all, if TID is not correct? Anyway, with TID changed to 7500, I can enable UpdateChannels and vdr won't touch the transponder data anymore. Still a bit odd that it updated the transponder data.. S13E does not have TID 7501 in any transponder, so where did the updated data come from? -- Teemu Suikki http://www.z-power.fi/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU command
Hi all,
I made a tiny patch to extend the SVDRP VOLU command.
Up until now VDR only had an option to _toggle_ the current audio muted status,
but no options to force the audio muted status on or off. I want to mute the
audio via SVDRP and unmute it again later.
My usecase: I'm running mpd on the same host as VDR, if I start playing music
with mpd from my tablet I can mute VDR automatically with a shell script and
unmute it again after stopping the music.
Using the (already implemented) VOLU 0 command also mutes the audio, but the
previous audio volume gets lost, so you cannot unmute audio again and return to
the previous volume.
Best regards
Sebastian
--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 20:30:53.440746278 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the
range\n
0...255). If the special options '+' or '-' are given, the volume
will\n
be turned up or down, respectively. The option 'mute' will toggle the\n
- audio muting. If no option is given, the current audio volume level
will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn
muting\n
+ off. If no option is given, the current audio volume level will be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,10 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) ==
0)(!cDevice::PrimaryDevice()-IsMute()))
+cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) ==
0)(cDevice::PrimaryDevice()-IsMute()))
+cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 20:30:53.440746278 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the range\n
0...255). If the special options '+' or '-' are given, the volume will\n
be turned up or down, respectively. The option 'mute' will toggle the\n
- audio muting. If no option is given, the current audio volume level will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn muting\n
+ off. If no option is given, the current audio volume level will be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,10 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) == 0)(!cDevice::PrimaryDevice()-IsMute()))
+cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) == 0)(cDevice::PrimaryDevice()-IsMute()))
+cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU command
Hi Sebastian Frei, with ... (!cDevice::PrimaryDevice()-IsMute())) is the command not recognized and the string Unknown option: MuteON will return, when you call svdr more than one with MuteON. Hardy ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU command
Hi Hardy,
yes you are right.
This one should be better:
--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 21:58:34.226895799 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the
range\n
0...255). If the special options '+' or '-' are given, the volume
will\n
be turned up or down, respectively. The option 'mute' will toggle the\n
- audio muting. If no option is given, the current audio volume level
will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn
muting\n
+ off. If no option is given, the current audio volume level will be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,12 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) == 0)
+if (!cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) == 0)
+if (cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;
Best regards
Sebastian
Am Donnerstag, 21. März 2013, 21:40:06 schrieb Hardy Flor:
Hi Sebastian Frei,
with ... (!cDevice::PrimaryDevice()-IsMute())) is the command not
recognized and the string Unknown option: MuteON will return, when you
call svdr more than one with MuteON.
Hardy
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 21:58:34.226895799 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the range\n
0...255). If the special options '+' or '-' are given, the volume will\n
be turned up or down, respectively. The option 'mute' will toggle the\n
- audio muting. If no option is given, the current audio volume level will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn muting\n
+ off. If no option is given, the current audio volume level will be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,12 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) == 0)
+if (!cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) == 0)
+if (cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU command
Why can't you use the HITK svdrp command sending the MUTE key?
# svdrpsend hitk mute
- Magnus
From: sebast...@familie-frei.net
To: vdr@linuxtv.org
Date: Thu, 21 Mar 2013 22:03:50 +0100
Subject: Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU
command
Hi Hardy,
yes you are right.
This one should be better:
--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 21:58:34.226895799 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the range\n
0...255). If the special options '+' or '-' are given, the volume will\n
be turned up or down, respectively. The option 'mute' will toggle the\n
- audio muting. If no option is given, the current audio volume level will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn muting\n
+ off. If no option is given, the current audio volume level will be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,12 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) == 0)
+ if (!cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) == 0)
+ if (cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;
Best regards
Sebastian
Am Donnerstag, 21. März 2013, 21:40:06 schrieb Hardy Flor:
Hi Sebastian Frei,
with ... (!cDevice::PrimaryDevice()-IsMute())) is the command not
recognized and the string Unknown option: MuteON will return, when you
call svdr more than one with MuteON.
Hardy
___
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
Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the SVDRP VOLU command
Hi Magnus,
I want to mute VDR when I start playing music. If I use the VOLU MUTE or the
HITK MUTE command, I can't be sure that I'll really mute VDR. If it was muted
before VDR becomes unmuted.
The existing SVDRP commands only toggle the status but I can't set the muted
status to an absolute value.
Sebastian
Magnus Sirwiö sir...@hotmail.com schrieb:
Why can't you use the HITK svdrp command sending the MUTE key?
# svdrpsend hitk mute
- Magnus
From: sebast...@familie-frei.net
To: vdr@linuxtv.org
Date: Thu, 21 Mar 2013 22:03:50 +0100
Subject: Re: [vdr] Patch: Add 'MUTEON' and 'MUTEOFF' options to the
SVDRP VOLU command
Hi Hardy,
yes you are right.
This one should be better:
--- vdr-1.7.41/svdrp.c 2013-02-17 14:17:36.0 +0100
+++ vdr-1.7.41.mute/svdrp.c 2013-03-21 21:58:34.226895799 +0100
@@ -317,12 +317,13 @@
UPDR\n
Initiates a re-read of the recordings directory, which is the
SVDRP\n
equivalent to 'touch .update'.,
- VOLU [ number | + | - | mute ]\n
+ VOLU [ number | + | - | mute | muteon | muteoff ]\n
Set the audio volume to the given number (which is limited to the
range\n
0...255). If the special options '+' or '-' are given, the volume
will\n
be turned up or down, respectively. The option 'mute' will toggle
the\n
- audio muting. If no option is given, the current audio volume level
will\n
- be returned.,
+ audio muting, 'muteon' will turn muting on, 'muteoff' will turn
muting\n
+ off. If no option is given, the current audio volume level will
be\n
+ returned.,
QUIT\n
Exit vdr (SVDRP).\n
You can also hit Ctrl-D to exit.,
@@ -1609,6 +1610,12 @@
cDevice::PrimaryDevice()-SetVolume(-VOLUMEDELTA);
else if (strcasecmp(Option, MUTE) == 0)
cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEON) == 0)
+ if (!cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
+ else if ((strcasecmp(Option, MUTEOFF) == 0)
+ if (cDevice::PrimaryDevice()-IsMute()))
+ cDevice::PrimaryDevice()-ToggleMute();
else {
Reply(501, Unknown option: \%s\, Option);
return;
Best regards
Sebastian
Am Donnerstag, 21. März 2013, 21:40:06 schrieb Hardy Flor:
Hi Sebastian Frei,
with ... (!cDevice::PrimaryDevice()-IsMute())) is the command not
recognized and the string Unknown option: MuteON will return, when
you
call svdr more than one with MuteON.
Hardy
___
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
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR form packages
There is somewhere repo of developer, FernetMenta, but I think those source should perfectly fit XBMC plugin I've updated the plugin: http://anonscm.debian.org/gitweb/?p=pkg-vdr-dvb/vdr-plugin-vnsiserver.git;a=summary But I this is still considered unstable, so right now this is no candidate to be uploaded to Debian. Tobias ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] 0.1.0
Hi Louis, I start xineliboutput with the following line xineliboutput --local=none --remote=37890 --primary --fullscreen I tried to add --hud but it did not work. To had to remove first --fullscreen because vdr did not start, but to the end i had the same problem: no osd :-( I tried to install softhddevice, but i could not get it to compile due to missing libraries etc. If you know which packages is needed in Ubuntu, then it would be great to get help with this :-) Regards, René On 21.03.2013 12:33 , Stefan Braun wrote: Hi Rene, how do you start the xineliboutput plugin? To get a true color osd, you have to start it with --hud. I think this is your problem... If this is not working, you could also try to use softhddevice as output plugin. softhddevice supports true color anyway, so you could see if you have another issue maybe... Cheers Louis PS: sorry for the html mail, damn new gmx webinterface :-) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] 0.1.0
On Thu, Mar 21, 2013 at 4:12 PM, René linu...@hertell.com wrote: I tried to install softhddevice, but i could not get it to compile due to missing libraries etc. If you know which packages is needed in Ubuntu, then it would be great to get help with this :-) Why don't you use `apt-file search` to identify the packages which contain the files you're missing? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] skin nOpacity 0.1.0
On 22.03.2013 2:10 , VDR User wrote: On Thu, Mar 21, 2013 at 4:12 PM, René linu...@hertell.com wrote: I tried to install softhddevice, but i could not get it to compile due to missing libraries etc. If you know which packages is needed in Ubuntu, then it would be great to get help with this :-) Why don't you use `apt-file search` to identify the packages which contain the files you're missing? I'm running a manually compiled vdr, and the ubuntu-version i run does not have the softhddevice plugin :-( René ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] skin nOpacity 0.1.0
On Thu, Mar 21, 2013 at 6:11 PM, René linu...@hertell.com wrote: I tried to install softhddevice, but i could not get it to compile due to missing libraries etc. If you know which packages is needed in Ubuntu, then it would be great to get help with this :-) Why don't you use `apt-file search` to identify the packages which contain the files you're missing? I'm running a manually compiled vdr, and the ubuntu-version i run does not have the softhddevice plugin :-( Are you saying there's some special ubuntu version of the VDR plugins source? Anyways, when you try compiling, you likely have errors like some file.pc is missing. So you can do `apt-file search file.pc` to find the package that file belongs to, and then install the package. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
