Re: [vdr] Watching VDR recordings and live TV on mobile
I have never tried Live TV on the mobile, but this should be possible via the Streamdev VDR Plugin: https://projects.vdr-developer.org/projects/plg-streamdev/files Even N9 had enough CPU to to stream just fine, I made many years ago a simple qt ui + ported sxfe and it's dependencies to it for testing. Mika ___ vdr mailing list vdr@linuxtv.org https://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr atsc support
Thanks for the replies, I will be traveling now, but I will test those once coming back. I will then report my findings. Mika On 03/25/2016 09:50 PM, Pridvorov Andrey wrote: > Hi all. > > В Пт, 25/03/2016 в 13:39 -0700, Timothy D. Lenz пишет: >> >> On 3/25/2016 11:55 AM, Joerg Bornkessel wrote: >>> >>> Am 24.03.2016 um 07:35 schrieb Mika Laitio: >>>> >>>> Does anybody know whether there is a working ATSC vdr-plugin >>>> available somewhere? >>>> >>>> I found some old discussions from the some ATSC plug-in from the >>>> mailing list pointing to http://www.fepg.org/ but from those I >>>> got >>>> an impression that plug-in is not actively maintained? >>>> >>>> So fat I have tested that I can scan and look the channels fine >>>> with the Kaffeine and WinTV-HVR-950Q, but in the long run I would >>>> be more interested on running the VDR in normal way on background >>>> server. >>>> >>>> Mika >>>> >>> ATSC is supported in the Core VDR. >>> Iam kontakted the Maintainer Alex Lasnier a lot of month ago for an >>> update for the >>> vdr-plugin-atscepg >>> This plugin is definitely dead on upstream since 2010 and is not >>> supported by the Maintainer anymore. >>> Anyway... >>> The maintainer has give me access to his privat git for some local >>> fixes by him self. >>> I dont remeber for this link. >>> You can download the latest version atscepg-0.3.0 from fepg.org >>> and you need an aditional patch from my dev webspace to get the >>> latest >>> fixes from him. >>> >>> https://dev.gentoo.org/~hd_brummy/distfiles/atscepg-0.3.0_vdr-1.7.1 >>> 3.tbz >>> >>> also you have to disable -std=c++11 support on latest gcc versions >>> to >>> fix c++11 issues on compiletime. >>> >>> I have this tested only for compile as i dont have access to atsc >>> conten >>> t. >>> >>> Cheers >>> >>> /dev/joerg >>> ___ >> I have been using this plugin for years. Haven't touched the computer >> in >> years as far as updating kernal or vdr. It says the version for ATSC >> 0.3.0hg. I think the main use of the plugin is channel scanning to >> find >> what channels are active. But For me it segfaults 95% of the time. >> Seems >> like maybe something in the stream. Because every so often, It works >> just fine. I can scan over and over no problem. But most of the time >> it >> segfaults as soon as you tell it to scan. > > For channels scan you can try my fork of reelchannelscan plugin, I use > it with vdr-2.2.0. I can't receive ATSC, so it's not tested. See on > russian forum: > http://linuxdvb.org.ru/wbb/index.php?page=Thread=27266#post27266 > > >> >> Another problem I have here in Tucson is the broadcasters don't know >> what a standard is. There is some flag the don't set to tell vdr >> there >> is guide data, so it's not collected even though a cheap converter >> box >> has no problem with it. But then they are doing good to put up more >> then >> a day or 2 of data anyway and PBS for awhile put in stream what was >> posted at all the web sites, but then made up their own guide and >> you >> had to go to a local web site to get the real guide. >> >> Also, several of our channels are broadcast from 2 locations on >> different frequencys, but carry the same data. VDR doesn't know how >> to >> handle that, so you have to delete one of the entries. My old sony >> tv >> and others have the same problem. They see the second copy and pick >> some >> new number based on the frequancy number instead of the assigned >> number. >> A bit of a pain. Looks like it might be fixed in newer high end tv's >> (and the old cheap converter box also had no problem with dupe >> channel >> numbers.) >> > > For channels with same pids you can try my patch, see > http://linuxdvb.org.ru/wbb/index.php?page=Thread=26833#post2683 > > > >> ___ >> vdr mailing list >> vdr@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > > > Best regards. > > ___ > 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] vdr atsc support
Does anybody know whether there is a working ATSC vdr-plugin available somewhere? I found some old discussions from the some ATSC plug-in from the mailing list pointing to http://www.fepg.org/ but from those I got an impression that plug-in is not actively maintained? So fat I have tested that I can scan and look the channels fine with the Kaffeine and WinTV-HVR-950Q, but in the long run I would be more interested on running the VDR in normal way on background server. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] MRE: TBS6285 slow onscreen menu
At the beginning, drivers was buggy, and I could't use dvb-t *AND* dvb-s2 cards at the same time. I worked with TBS support during several weeks to fix the problem : they even sent to me USB card to check if problem was from PCI-E or from driver, etc...). At the end, they fixed their driver and all was OK. Technical support is really excellent ! Hi, do you know are the fixed drivers you have now been released somewhere or merged to upstream kernel? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7 - 2.1 upgrade tips (FHS)
On 11/04/2013 11:58 PM, Timothy D. Lenz wrote: To me, dumping files all over the drives is messy, sloppy, and bad practice. Always has been and always will be. Someone just wants to copy MS stupidity into linux. Maybe so, but as that is supported it would be good if there are clean install instructions for doing that. I tried that once put found out that at least some of the plugins failed to install correctly for me and I needed to do symlinks, etc. to be able to start vdr properly. Maybe it was just my fault but I can try to test with newest version of everything once I get to place where I have that vdr 2.0 system running. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] half-viewed recordings, can they be moved at the top of the list?
I don't think it's difficult to do right at all to be honest. You can just make user-defined thresholds so the the user can decide himself how many mins or % of the total recording triggers the partial-view and viewed flags. For example one guy might want: not-viewed: 5% viewed partial-viewed: 5%+ viewed viewed: 95%+ viewed and another guy could customize it differently such as 10%, 10%+, 99%+... This way the user gets the 3 flags and gets to decide when they're triggered. I think this would satisfy the majority/most users with low difficulty to implement. Percentages would not work well as 5% is much more from 20 minute recording than 2 hour movie. But a little related to this, I think it would be great if there could be some kind of short cut for command that one could use after watching the recording to cut away end of the recording. So when ending texts start, one key press would just cut rest away and also stop the viewing. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] half-viewed recordings, can they be moved at the top of the list?
On 01/06/2013 12:31 PM, cedric.dew...@telfort.nl wrote: Hi All, Sometimes I watch a TV show halfway. Then I let VDR shutdown my PC. Then I would like to watch the rest of the show. Then I have to go to the list of TV shows, and find the correct one again. In my opinion it would be easyer for me if the half-watched shows are placed at the top of the list with TV shows. Does such an option exist? How should recordings in a sub-folder be handled? Should those be moved to the top of the list, or copied, or a shortcut be made? I would like to see a shortcut. Maybe by extending the current functionality of 0 key that can be used for sorting the recordings either by name or date. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] UPnP/DLNA media server plugin for the VDR
On 01/04/2013 07:48 PM, Brian-Imap wrote:
Hi,
this looks to be pretty interesting.
So where exactly does it fit in between XVDR, VNSI, streamdev, etc.
I just bought a Samsung smart TV, haven't found a single DLNA
music server that it could receive music from (sure I've heard about
updating the headers that are sent from the server), still none of them
worked with the TV.
Seems I could watch VDR directly on the TV without any kind of Set-Top
box inbetween with this plugin.
Samung has some bug's in their handling of upnp messages and therefore a
MediaTomp requires for example a small patch so that samsung tv is able
to show the media listing and play the recordings.
I patched the Mageia's mediatomb-0.12.1-4.mga2.src.rpm version with the
attached patch (found somewhere from the net) and at least Samsung 6305
with newest software works now ok with mediatomb.
Mika
diff -ruN mediatomb.orig/tombupnp/upnp/src/genlib/net/uri/uri.c mediatomb/tombupnp/upnp/src/genlib/net/uri/uri.c
--- mediatomb.orig/tombupnp/upnp/src/genlib/net/uri/uri.c 2012-06-06 23:01:22.0 +0200
+++ mediatomb/tombupnp/upnp/src/genlib/net/uri/uri.c 2012-06-07 08:22:01.0 +0200
@@ -1042,7 +1042,8 @@
out-path_type = REL_PATH;
}
-if( ( ( begin_hostport + 1 ) max ) ( in[begin_hostport] == '/' )
+//parse hostport only if scheme was found
+if( ( begin_hostport 0 ) ( ( begin_hostport + 1 ) max ) ( in[begin_hostport] == '/' )
( in[begin_hostport + 1] == '/' ) ) {
begin_hostport += 2;
@@ -1059,6 +1060,12 @@
out-hostport.text.size = 0;
out-hostport.text.buff = 0;
begin_path = begin_hostport;
+
+//remove excessive leading slashes (fix for Samsung Smart TV 2012)
+while( ( ( begin_path + 1 ) max ) ( in[begin_path] == '/' ) ( in[begin_path + 1] == '/') ) {
+begin_path++;
+}
+
}
begin_fragment =
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.30
From the log I can see that the driver apparently makes DVB-S/DVB-S2 available under adapter1/frontend0 and tries to provide DVB-T on adapter1/frontend1. But if it does so, it tells the application that it can provide DVB-S/DVB-S2 *and* DVB-T at the *same* time - which apparently isn't the case. Yes, you are correct. If I use frontend0 for DVB-S, I can't use frontend 1 at a same time for DVB-T. I will try in the evening to build the latest drivers myself to check whether both frontends are still created also with that one. Are there some other cards/drivers available with similar limitation where only a single frontend0 is created? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.30
On 09/10/2012 05:05 PM, Klaus Schmidinger wrote: VDR developer version 1.7.30 is now available at I tried to use for a first time with VDR the HVR-4000's multible delivery systems under same frontend feature that was introduced in 1.7.23. (HVR-4000 has DVB-T and DVB-S/S2 in the same card but only one of these delivery systems can work at a time.) In addition I have normal hvr-1300 DVB-T only tuner. If I connect cable only to HVR-4000, I can not get DVB-T channels visible with VDR. (but dvb apps like scan will work from the command line). The error looks similar than somebody else reported at a time when 1.7.23 was released but now I would expect of having new enough kernel running. My system info and logs are following: 1) Kernel version: 3.3.8-desktop-2.mga2 DVB API version is 5.5 (grep DVB-API) include/linux/dvb/version.h:#define DVB_API_VERSION 5 include/linux/dvb/version.h:#define DVB_API_VERSION_MINOR 5 2) tree /dev/dvb/ /dev/dvb/ ├── adapter0 │ ├── demux0 │ ├── dvr0 │ ├── frontend0 │ └── net0 └── adapter1 ├── demux0 ├── demux1 ├── dvr0 ├── dvr1 ├── frontend0 ├── frontend1 ├── net0 └── net1 3) VDR log which indicates device or resource busy error for adapter1/fronend1 device. Sep 17 23:51:34 localhost vdr: [15256] VDR version 1.7.30 started Sep 17 23:51:34 localhost vdr: [15256] codeset is 'UTF-8' - known Sep 17 23:51:34 localhost vdr: [15256] found 28 locales in ./locale Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-xineliboutput.so.1.7.30 Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-osdteletext.so.1.7.30 Sep 17 23:51:34 localhost vdr: [15256] loading plugin: ./PLUGINS/lib/libvdr-skinsoppalusikka.so.1.7.30 Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/setup.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/sources.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/diseqc.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/scr.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/channels.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/timers.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/svdrphosts.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/remote.conf Sep 17 23:51:34 localhost vdr: [15256] loading /home/lamikr/misc/vdr/vdr.git/keymacros.conf Sep 17 23:51:34 localhost vdr: [15257] video directory scanner thread started (pid=15256, tid=15257) Sep 17 23:51:34 localhost vdr: [15258] video directory scanner thread started (pid=15256, tid=15258) Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'A - ATSC' Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'C - DVB-C' Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'S - DVB-S' Sep 17 23:51:34 localhost vdr: [15256] registered source parameters for 'T - DVB-T' Sep 17 23:51:34 localhost vdr: [15256] probing /dev/dvb/adapter0/frontend0 Sep 17 23:51:34 localhost vdr: [15256] creating cDvbDevice Sep 17 23:51:34 localhost vdr: [15256] new device number 1 Sep 17 23:51:34 localhost vdr: [15259] epg data reader thread started (pid=15256, tid=15259) Sep 17 23:51:34 localhost vdr: [15259] reading EPG data from /storagedisc/video/epg.data Sep 17 23:51:34 localhost vdr: [15258] video directory scanner thread ended (pid=15256, tid=15258) Sep 17 23:51:34 localhost vdr: [15256] frontend 0/0 provides DVB-T with QPSK,QAM16,QAM64 (Conexant CX22702 DVB-T) Sep 17 23:51:34 localhost vdr: [15256] probing /dev/dvb/adapter1/frontend0 Sep 17 23:51:34 localhost vdr: [15256] creating cDvbDevice Sep 17 23:51:34 localhost vdr: [15256] new device number 2 Sep 17 23:51:34 localhost vdr: [15261] tuner on frontend 0/0 thread started (pid=15256, tid=15261) Sep 17 23:51:34 localhost vdr: [15261] cTimeMs: using monotonic clock (resolution is 1 ns) Sep 17 23:51:34 localhost vdr: [15262] section handler thread started (pid=15256, tid=15262) Sep 17 23:51:34 localhost vdr: [15257] video directory scanner thread ended (pid=15256, tid=15257) Sep 17 23:51:34 localhost vdr: [15256] frontend 1/0 provides DVB-S,DVB-S2 with QPSK (Conexant CX24116/CX24118) Sep 17 23:51:34 localhost vdr: [15265] section handler thread started (pid=15256, tid=15265) Sep 17 23:51:34 localhost vdr: [15264] tuner on frontend 1/0 thread started (pid=15256, tid=15264) Sep 17 23:51:34 localhost vdr: [15259] epg data reader thread ended (pid=15256, tid=15259) Sep 17 23:51:39 localhost vdr: [15256] ERROR (dvbdevice.c,1058): /dev/dvb/adapter1/frontend1: Device or resource busy Sep 17 23:51:39 localhost vdr: [15256] found 2 DVB devices Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Quiet times...
On 08/08/2012 06:08 PM, VDR User wrote Honestly, I don't care about the Olympics at all. I hate that every channel gives it so much coverage instead of reporting real important news. Will be glad when it's over. Well, I am also glad that they are over but for different reason. (even all good things needs to stop in the end) But, wow, I must say that what a great Olympics there has been. Lucky are those who have been able to attend in live. After this all real and important news (= depsessing war and economic crisis stuff) will fill up all of the channels. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Please share your systemd (Upstart) service file
On 06/28/2012 08:02 PM, VDR User wrote: On Thu, Jun 28, 2012 at 12:01 AM, Ludwig Nussel ludwig.nus...@suse.de wrote: That would be a nice feature -- worth suggesting for the big `after 2.0 is released` redesign(?). But, there may be plugins which need to be initialized with certain values. Although, maybe it's possible to have those be reinitialized within vdr? Yeah, I would like to have option to pass path to plugin config file for vdr-executable. Then somebody could write simple ui app for configuting it via ui based on to plugins it finds from the PLUGINS dir. In the case of systemd, it's no need to have this vdr has died, unload and load kernel module loop in the runvdr script, as those can be specified also as a pre and post commands in systemd. Mika ___ 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] toggle between recordings sort order with 0 key
On 06/06/2012 10:13 AM, Klaus Schmidinger wrote: The next developer version of VDR will contain sorting of recordings. You will be able to toggle between sorting by date or alphabetically, and that setting will be stored separately for each folder. When sorted by date, folders will still be in alphabetical order and will come first. Sounds great. I have also found out that sometimes it's useful to be able to sort also by recordings length/size. It will help if you are lack of space or want to clean up some couple of seconds/minutes recordings one may have made mistakenly. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Bad choices of USB cards
Also I wold welcome advice, which from those rather cheap USB cards works without any problems on stock linux kernel. Hi, I just bought 19 euro Fujitech DVT Pro DVB-T usb stick which seems to use Realtek RTL2832U chipset. USB stick also includes small remote control, but I have not tested yet whether that can be used from linux. lsusb shows the device as: 1d19:1101 Dexatek Technology Ltd. DK DVB-T Dongle Driver is not in the mainline kernel, but driver version which builded ok with 3.3.6-desktop-2.mga2 (mageia) kernel was available in git://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0.git. According to it's readme the same chipset is also in use with following other usb sticks: DIKOM USB-DVBT HD (ID 1b80:d394) NILOX DVB-T Stick N15 (ID 1b80:d393) TRUST 16738 (ID 0bda:2832) TERRATEC Cinergy T Stick BLACK (ID 0ccd:00a9) TX Hollywood DVTB (ID 1d19:1101) DIGIVOX mini II v3.0 (ID 1d19:1101) Installation for me was easy operation with steps written down below: 1) git clone git://github.com/tmair/DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0.git 2) cd DVB-Realtek-RTL2832U-2.2.2-10tuner-mod_kernel-3.0.0/RTL2832-2.2.2_kernel-3.0.0 3) changed KDIR from makefile: -KDIR = /usr/src/kernels/`uname -r` +KDIR =/usr/src/linux-`uname -r` 4) Make 5) Make install 6) Plug the usb stick: -- dvb_usb_rtl2832u module gets loaded 7) scan channels: scan -5 -o vdr /usr/share/dvb/dvb-t/fi-Kerimaki channels.conf Scan util had from dvb-apps-1.1.1-8.hg1465.1.mga2 had some problems and to be able to find out all channels, I needed to split the /usr/share/dvb/dvb-t/fi-Kerimaki scan frequence file to multiple smaller ones each containing single line. I do not have any idea whether somebody is working at the moment for trying to get this driver pushed to mainline kernel. At least for me it has now worked ok for 1 week. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [PATCH] toggle between recordings sort order with 0 key
Hi
Attached is a patch which allows to toggle the sort order
of recordings in the recording menu with vdr-1.7.27 between
- name
- date
- recording length
by pressing 0 key. At least I have found this to be very useful
feature when trying to find a just made recording from which you
do not know/remember the exact name to search from the long list of
recordings.
The thing I do not like in the patch is that the user must know this 0
key as all 4 colors are already reserved in VDR for other functions in
recordings menu. (play, go to beginning, delete and info).
But I do not know any better way to handle this at the moment.
Patch got inspiration from
http://www.u32.de/vdr-1.3.37-simple_record_sort-0.1.diff
originally submitted by Walter Koch some years ago.
Mika
From d15458f012c5463648ee25b163284f1db14d5f1c Mon Sep 17 00:00:00 2001
From: Mika Laitio lam...@pilppa.org
Date: Sun, 20 May 2012 19:45:40 +0300
Subject: [PATCH] toggle between recordings sort order with 0 key
By default the recordings are sorted in the
recordings menu in alphabetical order just like
previously. But now the user can toggle between
following sorting rules by pressing the 0 key:
- sort by recordings name
- sort by recordings date
- sort by recordings length
Patch got inspiration from
http://www.u32.de/vdr-1.3.37-simple_record_sort-0.1.diff
originally submitted by Walter Koch.
Signed-off-by: Mika Laitio lam...@pilppa.org
---
menu.c | 11 +++
recording.c | 30 +-
recording.h |2 ++
3 files changed, 42 insertions(+), 1 deletion(-)
diff --git a/menu.c b/menu.c
index ad1cac3..4fcb16d 100644
--- a/menu.c
+++ b/menu.c
@@ -2470,6 +2470,17 @@ eOSState cMenuRecordings::ProcessKey(eKeys Key)
case kInfo:
case kBlue: return Info();
case k1...k9: return Commands(Key);
+ case k0: SortingRule++;
+ if (SortingRule = 3)
+SortingRule = 0;
+ if (SortingRule == 0)
+ Skins.Message(mtInfo, tr(Sorting recordings by name));
+ else if (SortingRule == 1)
+ Skins.Message(mtInfo, tr(Sorting recordings by date));
+ else
+ Skins.Message(mtInfo, tr(Sorting recordings by length));
+ Set(true);
+ return osContinue;
case kNone: if (Recordings.StateChanged(recordingsState))
Set(true);
break;
diff --git a/recording.c b/recording.c
index e1f7ec9..42d554d 100644
--- a/recording.c
+++ b/recording.c
@@ -68,6 +68,7 @@
bool VfatFileSystem = false;
int InstanceId = 0;
+int SortingRule = 0;
cRecordings DeletedRecordings(true);
@@ -842,7 +843,21 @@ int cRecording::GetResume(void) const
int cRecording::Compare(const cListObject ListObject) const
{
cRecording *r = (cRecording *)ListObject;
- return strcasecmp(SortName(), r-SortName());
+ int ret;
+
+ switch(SortingRule) {
+// sort by recording name
+case 0:
+default:ret = strcasecmp(SortName(), r-SortName());
+break;
+// sort by recording date that is stored in BaseFileName
+case 1: ret = strcasecmp(BaseFileName(), r-BaseFileName());
+break;
+// sort by recording length
+case 2: ret = (LengthInSeconds() r-LengthInSeconds());
+break;
+ }
+ return ret;
}
const char *cRecording::FileName(void) const
@@ -860,6 +875,19 @@ const char *cRecording::FileName(void) const
return fileName;
}
+const char *cRecording::BaseFileName(void) const
+{
+ const char *s;
+ const char *fullname;
+
+ fullname = FileName();
+ s = strrchr(fullname, '/');
+ if (s)
+return s + 1;
+ else
+return fullname;
+}
+
const char *cRecording::Title(char Delimiter, bool NewIndicator, int Level) const
{
char New = NewIndicator IsNew() ? '*' : ' ';
diff --git a/recording.h b/recording.h
index 5f94ee2..37e970f 100644
--- a/recording.h
+++ b/recording.h
@@ -26,6 +26,7 @@
extern bool VfatFileSystem;
extern int InstanceId;
+extern int SortingRule;
void RemoveDeletedRecordings(void);
void AssertFreeDiskSpace(int Priority = 0, bool Force = false);
@@ -118,6 +119,7 @@ public:
virtual int Compare(const cListObject ListObject) const;
const char *Name(void) const { return name; }
const char *FileName(void) const;
+ const char *BaseFileName(void) const;
const char *Title(char Delimiter = ' ', bool NewIndicator = false, int Level = -1) const;
const cRecordingInfo *Info(void) const { return info; }
const char *PrefixFileName(char Prefix);
--
1.7.10
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr remote
On 04/14/2012 06:15 AM, Torgeir Veimo wrote: Looks like the new remote from reelmedia is specially made for VDR, with all labels corresponding to the correct keys. It would certainly yield a better WAF for the VDR box. Says programmable, but does any insiders know if can be programmed to control volume and on/off for a TV, without any 'mode change'? Seems to be a bit steep at €49 at their website though: http://www.reel-multimedia.com/de/shop_zubehoer_tastatur.php http://www.satberlin.de/media/images/popup/reel-fernbedienung_new.jpg http://www.cyberport.de/mall/1/pic/zbild0/zbild0-278219C416-107_600.JPG Do you know does it include a some kind of usb irda receiver or is there some place where to buy that kind of things that would be compatible with that remote? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Local frontend - using XBMC strm vs vdr-sxfe
Yep I did know about these, but XBMC provides a much richer experience for DVD, Blu-ray playback. e.g., cataloguing and display of a library, automatic display framerate switching etc. I thought blu-ray is dead format not supported by Linux movie players. Does XBMC support it somehow? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.26
Damn, too late for today... :-) Just finished the noepg-plugin-skeleton at So according to README this plug-in replaces the noepg.patch. What is the functionality/purpose of this noepg patch/plugin? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.24
Because 1.6.0 was released a long time ago, and we want a new stable version soon? :) I agree, 1.7 devel versions have many nice improvements like the support for hvr-4000's multiple frontends in same adapter. Even thought most active users in this mail list very likely uses developer versions, there are probably lot of users still using stable 1.6.0 and would also prefer to run the Next stable once released. But I hope that the mentioned real client-server redesign that could handle many simultaneous clients watching different streams would be then the main goals next version after that. Current way of doing it at least with xineliboutput is just too complex and error prone. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wanted VDR xineliboutput client
On 10/23/2011 06:02 PM, JJussi wrote: Because this is just client.. Just vdr-sxfe what is capable play with VDPAU... Still I need to solve some problems at server end.. Get vdr-1.7 + skinsoppalusikka + epgsearch + some other plugins to install them to same machine.. Maybe I need to pick every piece from them original location and try to compile everything from source code. Maybe a following script is useful for automatizing the build process a bit. I always use it when ever the new version of vdr plugins have entered to git tree. As there are always couple of system specific config files, the script copies those from my previous vdr-installation dir. In addition the launch command in runvdr line is following: VDRCMD=$VDRPRG --lirc -w 15 -c /home/lamikr/dvb/vdr/vdr.git -v /video -P'xineliboutput --local=none --remote=37890 --video=vdpau' -Pepgsearch -P'osdteletext -d /home/lamikr/dvb/vdr/vdr.git/plugins/osdteletext' -Pskinsoppalusikka -Pfemon -P'live -p 8080' -P'vdrrip -p /usr/bin/mplayer -e /usr/bin/mencoder' vdr-server-build.sh--- git clone git://projects.vdr-developer.org/vdr.git vdr.git cd vdr.git git checkout -b lamikr cp ../vdr-old.git/channels.conf . cp ../vdr-old.git/remote.conf . cp ../vdr-old.git/svdrphosts.conf . cp ../vdr-old.git/runvdr . mkdir plugins cp -ax ../vdr-old.git/plugins/xineliboutput plugins mkdir -p PLUGINS/lib chmod a+x runvdr cd PLUGINS/src git clone git://projects.vdr-developer.org/xineliboutput.git xineliboutput git clone git://projects.vdr-developer.org/vdr-plugin-osdteletext.git osdteletext git clone git://projects.vdr-developer.org/vdr-plugin-epgsearch.git epgsearch git clone git://projects.vdr-developer.org/vdr-plugin-live.git live git clone git://projects.vdr-developer.org/vdr-plugin-infosatepg.git infosatepg git clone git://projects.vdr-developer.org/vdr-plugin-vdrrip.git vdrrip git clone git://projects.vdr-developer.org/vdr-plugin-markad.git markad wget -c http://www.saunalahti.fi/~rahrenbe/vdr/femon/files/vdr-femon-1.7.10.tgz tar -xvzf vdr-femon-1.7.10.tgz ln -s femon-1.7.10 femon #skinsoppalusikka wget -c http://www.saunalahti.fi/~rahrenbe/vdr/soppalusikka/files/vdr-skinsoppalusikka-1.7.3.tgz tar -xvzf vdr-skinsoppalusikka-1.7.3.tgz ln -s skinsoppalusikka-1.7.3 skinsoppalusikka mkdir -p ../../themes cp -d skinsoppalusikka/themes/*.theme ../../themes/ mkdir -p ../../plugins/skinsoppalusikka cp -d ../../../vdr-old.git/plugins/skinsoppalusikka/*.xpm ../../plugins/skinsoppalusikka/ cd ../.. make make plugins - Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Wanted VDR xineliboutput client
I bought 2 years ago Zotac IONITX-A-E motherboard which came with atom CPU and nvidia gpu, at that time it cost about 200 euro. I use it only for web browsing, vdr-client (with vdr-xineliboutput) and music listening purposes and for that kind of things the device works like a charm. With SD material the cpu load is about 10-20 %, when I have VDPAU support enabled. (I think it was about 60-80% without VDPAU.) I made the small case myself and have I have 12 fan running in it in the slowest speed and the case/cpu/gpu temperatures remains under 50 c. Suspend/resume works ok at least with Mandriva 2010.2. (I have configured from the gnome control center the device to suspend if nobody is using it for 3 hours) The only problem I have at the moment is a good infrared or bt remote controller for the device. I currently have Ione Scorpius P20 keyboard with internal mouse, but it's quality is not very good. I have considered of switching it to prodige NanoX or some USB/infrared remote if somebody could suggest a good one... Mika On 10/16/2011 02:02 PM, JJussi wrote: Hi! Any suggestions for small, powerful, quiet, FullHD VDR client? So, I search machine what would act as VDR-client, using xineliboutput with FullHD resolution and machine would have DVI or HDMI connection + optical audio. Of course remote control is needed too! ;-) -- JJussi ___ 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] ERROR: video data stream broken
As much as I like the EPG scan, I usually have it turned off because I think the driver gets rather unstable when VDR often switches channels and maybe hits transponders that don't carry any signal. What's especially unstable is the CAM situation. I have two CAMs in my VDR (connected to budget cards) and quite often the connection to the CAMs is lost, to a point where not even a CAM reset (from the Setup/CAM menu) helps any more. I have to pull the CAM, wait a few seconds and then insert it again. When the driver is in such an unstable state, a recording on that device will usually fail, and VDR performs an emergency exit. I have also a pay-tv card and I am seeing a similar kind of problems with one finish pay-tv channel (Nelonen Pro). Quite often that channel seems to freeze about every 5 min. In such a cases the channel is watchable only after vdr is restarted. (either vdr crasher or emergeny exit itself) I have found out that I can speed up the vdr restart in this way: 1) switch to other channel in different frequency (either in dvb-t in same card or dvb-s in other dvb card) 2) switch back to problematic channel -- vdr will either emergency exit or die 3) Once runvdr script restarts vdr, the channel is again watchable and works for a couple of minutes just fine I do not know whether the signal quality is causing the problems or are there differences in the data send. - channels from finish MTV3 works always without problems, while the problematic channels are from finish Sanoma Oy. - working channels from MTV3 seems to have better signal quality than the problematic channels from Nelonen... (They are in different muxes and I live about 90 km from the nearest tv base station link) There are however also a days when even the nelonen pro works just fine. (for example vdr restarted itself every 5 min when I watched finish baseball final on sunday but on the same evening the eurobean champ basketball final showed up just fine.) Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.21
On 09/09/2011 10:19 PM, Reinhard Nissl wrote: Hi, Am 09.09.2011 16:54, schrieb Klaus Schmidinger: Since you're saying that the problem is related to the dxr3 plugin I guess I won't see any error with my TT-S2 6400. I switch to 1.7.21 from 1.7.17 and see that teletext subtitles appear now for example on Das Erste HD. No matter which OSD size I setup in vdr-xine (e. g. 720x576, 1280x720 or 1920x1080), the subtitles are never positioned correctly and vdr-xine complains very often like that: vdr-xine: new OSD(-152, 0) requested with coordinates out of range I noticed a little different problem with vdr-sxfe (from xineliboutput). If I first watch some channel on vdr-sxfe client from the small window, the subtitles are positioned ok for me. But once I click the window for full screen mode, the subtitle position and size are not re-calculated and this causes that subtitles are shown in the middle of the screen. To fix this, I need to switch for another channel and then switch back to original channel. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [Patch] crashes with old recordings without info file
I have some old recordings made on 2005 which does not have info file.
This caused vdr 1.7.17 to crash because
in tools.c line 1194 there is no check whether the file parameter passed
is NULL or not. Real cause for the crash is in the vdrrip plugins which
should handle the case where the info file does not exist on
setLengthVDR method on movie.c.
Anyway, it's propably good idea also to has the NULL check's in vdr's
own code. Patches attached for tools.c and recording.c.
#0 0x7640e8ff in getdelim () from /lib64/libc.so.6
#1 0x004fcd48 in getline (this=0x7fffde30, f=0x0) at
/usr/include/bits/stdio.h:118
#2 cReadLine::Read (this=0x7fffde30, f=0x0) at tools.c:1194
#3 0x004cc383 in cRecordingInfo::Read (this=0xc29bc0, f=0x0) at
recording.c:419
#4 0x7fffef0397a0 in cMovie::setLengthVDR() () from
./PLUGINS/lib/libvdr-vdrrip.so.1.7.17
#5 0x7fffef03af00 in cMovie::cMovie(char const*, char const*) ()
from ./PLUGINS/lib/libvdr-vdrrip.so.1.7.17
#6 0x7fffef0367d7 in cMenuVdrripMovie::cMenuVdrripMovie(char
const*, char const*) () from ./PLUGINS/lib/libvdr-vdrrip.so.1.7.17
#7 0x7fffef03807d in cMenuVdrripEncode::ProcessKey(eKeys) () from
./PLUGINS/lib/libvdr-vdrrip.so.1.7.17
[lamikr@tinka Prisma:_Einstein_ja_kaiken_teoria]$ ls -la
2005-04-21.20\:58.50.99.rec/
total 1338080
drwxr-xr-x 2 76 76 4096 2008-05-17 17:48 ./
drwxr-xr-x 3 76 76 4096 2008-05-17 17:46 ../
-rw-r--r-- 1 76 76 1369418800 2008-05-17 17:48 001.vdr
-rw-r--r-- 1 76 76 727968 2008-05-17 17:48 index.vdr
-rw-r--r-- 1 76 76 4 2008-05-17 17:48 resume.vdr
-rw-r--r-- 1 76 76441 2008-05-17 17:48 summary.vdr
From ef2f4122b44abbc4cae7876bb8566ed95151cdf5 Mon Sep 17 00:00:00 2001
From: Mika Laitio lam...@pilppa.org
Date: Sun, 3 Apr 2011 13:06:55 +0300
Subject: [PATCH 1/2] NULL pointer check to cReadline.read in tools.c
Signed-off-by: Mika Laitio lam...@pilppa.org
---
tools.c | 22 --
1 files changed, 12 insertions(+), 10 deletions(-)
diff --git a/tools.c b/tools.c
index d03595e..c09a9b0 100644
--- a/tools.c
+++ b/tools.c
@@ -1191,18 +1191,20 @@ cReadLine::~cReadLine()
char *cReadLine::Read(FILE *f)
{
- int n = getline(buffer, size, f);
- if (n 0) {
- n--;
- if (buffer[n] == '\n') {
-buffer[n] = 0;
-if (n 0) {
- n--;
- if (buffer[n] == '\r')
- buffer[n] = 0;
+ if (f != NULL) {
+ int n = getline(buffer, size, f);
+ if (n 0) {
+n--;
+if (buffer[n] == '\n') {
+ buffer[n] = 0;
+ if (n 0) {
+ n--;
+ if (buffer[n] == '\r')
+ buffer[n] = 0;
+ }
}
+return buffer;
}
- return buffer;
}
return NULL;
}
--
1.7.3.4
From 18385a3641f8fb6003824462b0e982edbf248f93 Mon Sep 17 00:00:00 2001
From: Mika Laitio lam...@pilppa.org
Date: Sun, 3 Apr 2011 13:12:20 +0300
Subject: [PATCH 2/2] NULL pointer check for file at cRecordingInfo::Read(FILE
*f)
Signed-off-by: Mika Laitio lam...@pilppa.org
---
recording.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/recording.c b/recording.c
index 02a6e61..07528a2 100644
--- a/recording.c
+++ b/recording.c
@@ -412,7 +412,7 @@ void cRecordingInfo::SetFramesPerSecond(double
FramesPerSecond)
bool cRecordingInfo::Read(FILE *f)
{
- if (ownEvent) {
+ if (f ownEvent) {
cReadLine ReadLine;
char *s;
int line = 0;
--
1.7.3.4
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Patch] crashes with old recordings without info file
I wonder who is actually calling cRecordingInfo::Read(FILE *f) with
a NULL pointer? In VDR's own code all calls to that function are
made sure to get a non-NULL pointer:
Yes, the real reason is in the vdrrip plugin that I cloned from
http://projects.vdr-developer.org/git/
It has this kind of code which always assumes that info file always exist.
void cMovie::setLengthVDR() {
char *infoFile = NULL;
asprintf(infoFile, %s%s, Dir, OldRecording ? /info.vdr :
/info);
dsyslog ([vdrrip] reading recording info %s ,infoFile);
cRecordingInfo *crec = new cRecordingInfo(Dir);
FILE *f = fopen(infoFile, r);
if (crec-Read(f)) {
I just thought that it would be good to fix that in vdr code also.
But I think putting the metod now private will also quarantee NULL
pointer check :-)
Mika
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] dynamite plugin
- what about being able to use aliases like /dev/dvb/dvb_s2_card_one with the -D arg ? (tho it's not really important) - what about a github tree of vdr with your patch already applied ? Maybe - shouldn't be too bad. :) Maybe just adding a patch branch to http://projects.vdr-developer.org/git/?p=vdr.git;a=summary ? It could also contain some other known patches for 17.7, like the vdr-1.7.17-updatemarks-2.diff or vdr-1.7.17-updatemarks-3.diff... Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput subtitle crop
Looks correct, at least for DVB subtitles. Did you test only with DVB subtitles or also with teletext subtitles ? How can I see whether the channel is sending teletext or dvb subtitles? MIka ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Request: E parameter in channels.conf for epg scan
The second thing is the tuning. Get next channel on this transponder sounds simple, but actually deciding whether a channel is tuneable involves 17 different rules that get checked against each device, plus probing the CAM whether the channel can be decoded by the CAM. I think that part is even slower than the whole channel list. But after all, there are more important things that need work, than speeding up such special cases. I agree, I have one vdr-server + 3 active xineliboutput clients. Nowadays each of the clients are sharing the same channel list because I have felt it to be too hacky to put multiple vdr instances to run on that vdr-server. It would really be nice to have some kind of server interface to vdr so that one vdr instance could really support multiple clients with different dvb tuners in case there are some of them still unused. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Unwatchable channels (vdr-xine, dxr3, vlc, mplayer)
with vdr 1.7.16 and reelbox plugin (eHD) this channels are ok in live tv (even with some BER with my dish, Warszawa seemed to be weaker, i also got UNC's there but no real problems, only a small picture distortion some times) And Reinhard also sees them ok with vdr-xine, while I still have problems both with vdr-xine and the dxr3 :-/ I have used to have problems for watching some pretty weak signal DVB-T channels also which seemed always lost the log after 5 minute usage, until vdr killed and restarted itself. The problem went away for me after I changed from the vdr settings the EPG scan mode to newer or something like that. (I am not near to my vdr at the moment, so I can not check the exact location and text for this menu in the vdr.) Can you test, whether the same thing could help also you? I am running 2 card system - hauppauge hvr-1300 dvb-t connected - hauppauge hvr-4000 dvb-s connected dvb-t not connected because vdr does not support using both the dvb-s and t from the hvr-4000. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev CVS - recent tarball?
Personally I don't care if it's called CVS, SVN or git. However I wouldn't want to loose the history, so I'd need someone with access to the internal CVS structures. Unfortunately the vdr-developer.org admins are not very responsive ATM. And of course I'd need to be in the mood for this sort of task. My spare time is very limited - I prefer spending it with coding. I have pretty good experiences for turning the svn repository to git repository with svngit. (Basically you just checked out the code from svn with svngit and you had the git repository with svn history) Maybe there is a similar kind of tool also for the cvs, I just have not newer used it. And of course you would now need the cvs access to streamdev :-( Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev CVS - recent tarball?
am getting some compile errors. Frank Schmirler says the current CVS contains fixes for that, but the CVS server at vdr-developer.org is down. Does anyone have a recent CVS checkout they wouldn't mind sending me? streamdev is the last thing I need to finally upgrade from VDR 1.4.7 :) unfortunately the problems on www/streamdev.vdr-developer.org persist. Until the problems have been resolved current snapshots plus a patch fixing http://www.linuxtv.org/pipermail/vdr/2010-September/023520.html are available from http://vdr.schmirler.de. Any changes that streamdev would move to using git repositories in http://projects.vdr-developer.org ? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr.git tree usage for building multiple vdr versions
Hi I have now mostly used http://projects.vdr-developer.org/git/ as a link for cloning the vdr and all plugins I have wanted to use for building new vdr versions. So I could for example build 1.7.10 by using commands #git clone git://projects.vdr-developer.org/vdr.git #cd vdr.git #git checkout vdr-1.7.10 and then go to plugins/src dir and download all plugins there and then finally build everything by using normal #make #make plugins What I would however like to do is to use same vdr git tree for building multiple vdr versions by using something like #make O=../build-1.7.13 #make plugins O=../build-1.7.13 So that I could just use one vdr.git source tree and jump inside of it to different versions. When building kernel I already can do that by using a commands like: #git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git #git checkout v2.6.34-rc1 #mkdir ../build-2.6.34-rc1 #make xconfig O=../build-2.6.34-rc1 #make O=../build-2.6.34-rc1 #git checkout another version... Has anybody doing something like that with vdr? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vdpau crop
If I watch vdr-sxfe just from a small window, the subtitle and text are positioned correctly with a good looking font size to bottom of the screen. But if I watch finish yle 1 channel which uses dvb subtitles from fullscreen vdr-sxfe, the subtitle font is small and text is positioned about to middle of the screen. (Left position is correct) Have you tried to change the subtitles decoder from VDR to xine? Anyway, the problem is that the resolution and position information of subtitles is 720x576. If your output resolution differs from that, the subtitles are misplaced. The attached patch might help you as it should scale the subtitles osd always to 720x576 (found it on my hd and it comes with per?valotakuu :) when using VDR's subtitles decoders. Thanks, it seems that you do not even need to drive fast away with car's lights blinking, as the patch worked nicely and fonts seemed to scale nicely between fullscreen and small screen. Hopefully this can be merged to xineliboutput repo. Mika___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput vdpau crop
Couple of issues I reported earlier (see below) have now merged to xineliboutput-plugin. [...] 1. Cropping is not reseted if I switch to 16:9 channel that has the same resolution as 4:3 channel that has turned on the cropping. 2. DVB subtitles are not positioned correctly during cropping if vdr-sxfe is used to show subtitles. Vertical alignment is about at half of the screen. Are you using vdpau ? Does the attached patch fix issue 2 ? I am also having problems with the subtitle text size and position with vdr-1.7.10 and latest xineliboutputs. (and your patch did not help.) With vdr-1.6.0, subtitles plugin and xineliboutput 1.0.4 things works ok. If I watch vdr-sxfe just from a small window, the subtitle and text are positioned correctly with a good looking font size to bottom of the screen. But if I watch finish yle 1 channel which uses dvb subtitles from fullscreen vdr-sxfe, the subtitle font is small and text is positioned about to middle of the screen. (Left position is correct) Usually if I change from small window to fullsize, the first subtitle text is showed with good looking font size and position in the bottom-left position but next subtitle texts after that are positioned in the middle-left. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
OK, i finally found the time to complete a VDR PC based on the ION board. The good news are: + 1080p plays back smoothly with xine/vdpau with very low CPU usage. + sound over HDMI works. + the streamdev-client plugin works - even with HD channels. + the xine plugin works fine - also with HD channels and HD recordings. I had to tweak a few config items. The not-so-good news are: + The fan is a bit loud and so far I have not found a silent replacement fan. + I originally set up the system as a diskless (nfsroot) system, but KDE 4 (I am using OpenSuSE 11.2) performs unbearably slow, so I was forced to install a hard disk. So, as it turns out, I do not need a DVB card in the PC (the server has 2 DVB-S cards and one DVB card). If I keep it that way, I really do not need the PCI slot, so I could use one of these passively cooled main boards http://geizhals.at/deutschland/a467665.html http://geizhals.at/deutschland/a439268.html I currently use this (actively cooled) main board: http://geizhals.at/deutschland/a455388.html Using a passively cooled main board would solve the fan noise problem. I also finally setted up my ion system. I have a similar kind of passive cooled zotac that you put in your links but found out that without any cooling it's temperature get still pretty hight 60-65 celcius. The included 4 inch fan was indeed pretty noisy, so I invested for a 8 inc fan and put that to my own made wooden case. (I first used old case from broken video, but that one had about 30 cm extra width, so I ended up making my own case) With this 8 inch fan, the cpu and mcu temperatures are now about 40 celcius. If you are interested, I put a picture on http://pilppa.org/home/blogs/index/1 For some reason the --video vdpau option for vdr-sxfe still does not work for me... (Using mandriva 2010 version of everything else except from own build vdr-1.7.10 and couple od days old xineliboutput plugin with latest fix being: Fixed generating lirc key release events) ). gdb crash log is below: (gdb) set args xvdr+tcp://192.168.3.11:37890 --video vdpau (gdb) run Starting program: /usr/local/bin/vdr-sxfe xvdr+tcp://192.168.3.11:37890 --video vdpau [Thread debugging using libthread_db enabled] vdr-sxfe 1.0.90-cvs (build with xine-lib 1.1.16, using xine-lib 1.1.16) Video driver: vdpau VDR Server: xvdr+tcp://192.168.3.11:37890 [New Thread 0x7fa4ab9af6f0 (LWP 10536)] [10536] [vdr-fe]GNOME screensaver disabled [New Thread 0x7fa4a3514910 (LWP 10545)] [10536] [vdr-fe]fe_xine_init: xine_open_video_driver(vdpau) failed Error initializing xine [Thread 0x7fa4a3514910 (LWP 10545) exited] Program received signal SIGSEGV, Segmentation fault. 0x7fa4aa5e2cad in pthread_mutex_lock () from /lib64/libpthread.so.0 Missing debug package(s), you should install: dbus-debug-1.2.16-2mdv2010.0.x86_64 dbus-glib-debug-0.82-1mdv2010.0.x86_64 faac-debug-1.28-3plf2010.0.x86_64 faad2-debug-2.7-1plf2009.1.x86_64 gcc-debug-4.4.1-4.1mnb2.x86_64 glib2.0-debug-2.22.2-2mdv2010.0.x86_64 glibc-debug-2.10.1-6.2mnb2.x86_64 lame-debug-3.98.2-1plf2009.0.x86_64 libalsa2-debug-1.0.21a-1mdv2010.0.x86_64 libcdio-debug-0.81-5mdv2010.0.x86_64 libdvdcss-debug-1.2.10-2plf2010.0.x86_64 libjpeg-debug-7-5mdv2010.0.x86_64 libogg-debug-1.1.4-2mdv2010.0.x86_64 libtheora-debug-1.1.0-1mdv2010.0.x86_64 libvorbis-debug-1.2.3-1mdv2010.0.x86_64 libx11-debug-1.2.2-2mdv2010.0.x86_64 libxau-debug-1.0.5-1mdv2010.0.x86_64 libxcb-debug-1.4-3.2mdv2010.0.x86_64 libxcursor-debug-1.1.10-1mdv2010.0.x86_64 libxdmcp-debug-1.0.3-1mdv2010.0.x86_64 libxext-debug-1.0.5-1mdv2010.0.x86_64 libxfixes-debug-4.0.3-5mdv2010.0.x86_64 libxinerama-debug-1.0.3-3mdv2010.0.x86_64 libxrandr-debug-1.3.0-2mdv2010.0.x86_64 libxrender-debug-0.9.4-5mdv2010.0.x86_64 pcre-debug-7.9-1mdv2010.0.x86_64 real-codecs-debug-1.2-4plf2010.0.x86_64 vcdimager-debug-0.7.23-9mdv2010.0.x86_64 xine-lib-debug-1.1.16.3-2plf2010.0.x86_64 zlib-debug-1.2.3-13mdv2010.0.x86_64 (gdb) bt #0 0x7fa4aa5e2cad in pthread_mutex_lock () from /lib64/libpthread.so.0 #1 0x7fa4a9a09773 in xine_list_video_output_plugins () from /usr/lib64/libxine.so.1 #2 0x0040cc80 in list_plugins_type (xine=0x1, msg=0x416993 Available video drivers:, list_func=0x7fa4a9a09740 xine_list_video_output_plugins) at xine_frontend.c:107 #3 0x0040cd57 in list_xine_plugins (fe=value optimized out, verbose=0) at xine_frontend.c:125 #4 0x00412648 in main (argc=value optimized out, argv=0x7fff415c6e08) at xine_frontend_main.c:749 Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
dto :-) zotac-A; Dual Core Atom, 32GB-SSD And over Christmas I managed to make it completely noiseless by installing a Accelero S1 cooler !!! http://www.schwanthalercomputer.de/advanced_search_result.php?keywords=accelero+S1x=0y=0 The mounting is somewhat unorthodox, but took me less than an hour to install. If someone is interested I try to put some photos somewhere. A pic showing how you have connected it to zotac would indeed be interesting. Now temperature stays below 60?C even with high load (h264 decoding or heli-X 3D simulation). I have a similar kind of passive cooled zotac that you put in your links but found out that without any cooling it's temperature get still pretty hight 60-65 celcius. Is this a single core? Do you have any other fan (power supply, case)? My experience was, that without any cooling the temperature kept rising. I stopped the experiment above 80?C when temperature was still rising even in idle desktop (ubuntu koala). Same with one core disabled on startup with maxcpus. Yes, the mine is also a dual core. I was following the temperatures sofar only from bios settings where it shows both the cpu and gpu. But for me it used to stay near to 65 without cooling. (I was however always booting to bios to check it) I used to use the board with the original cooler slowed down with a simple poti until recently. Much more silent with almost no change in temperatures compared to full speed cooling (below 40?C), I do not have a pc shop near to buy these poti's so I was planning to try to solder couple of resistors. From internet I also found that it could be easy to just switch couple of wires to slow down from 12w to 7w. All temperatures are from GPU since I don`t have patched the kernel and don't know how to access cpu temperature without that effort. But since they are connected thermally there should not be a big difference. Mandriva 2.6.31 kernels reports temp also incorrectly, I think I read somewhere that 2.6.32 kernels should have that fixed. Have not tried myself though.___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
Have you compiled vdr-xineliboutput with --enable-vdpau ? what does ./configure show and are you using xine-lib-1.2 HG with vdpau patch? xineliboutput configure shows vdpau in the list of enabled features but command vdr-sxfe -help does not list vdaup Available video drivers: xv raw SyncFB opengl xshm none xxmc fb xvmc Available audio drivers: alsa oss file none I have not build xine or vdpau libraries myself and are instead just using the mandriva 2010 ones. (backported version from vdapu thought) [lam...@localhost ~]$ rpm -qa | grep vdpau lib64vdpau1-0.3-1mdv2010.0 lib64vdpau-devel-0.3-1mdv2010.0 [lam...@localhost ~]$ rpm -qa | grep xine lib64xine-devel-1.1.16.3-2plf2010.0 lib64xine1-1.1.16.3-2plf2010.0 So would this xine version be new enough if I just patch the rpm with patch from somewhere or do I need to download the sources for newer xine version? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] LCD with vdr-1.7.x ?
graphlcd seems to not having been updated for a really long time... Is there something else (I like to use my Logitech G15 LCD keyboard). I have used lcdproc-plugin to get information from displayed channel, played mp3, etc. to lcd in antec fusion v2 silver. Newest version seems to be maintained at http://projects.vdr-developer.org/projects Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR frontend device: Xtreamer
Has anybode DLNA capable televisions for example from samsung or sony? It would be interesting to know would be easy to use those with vdr for watching live tv and recordings. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdpau setup steps for vdr client
I just bought a zotac ion motherboard and plan to harness it in the weekend as a ultimate super master dream vdr client for my 19 monitor :-) Sofar I have used to run vdr-xineliboutput in my clients and would like to do that also with this machine if possible. Currently my server runs vdr 1.6 but I plan to update that also to 1.7.10. Is there anything special steps/tweaking I need to do to get the client work nicely vdpau? - could things work with some of the distros almost out of the box already or do I need to - download build vdpay by myself - patch and build xinelib by myself - patch/build vdpau - etc... If somebody has some kind of step of step guide for the fastest and easiest steps for getting this done with disto, you could save my weekend :-) (New client so any distro will go... ) Have anybody done this btw in a diskless way where OS is booted from the server? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] strange issue with DVB-S2 and VDPAU
to upgrade. After the upgrade I had no sound at all on my system. As I saw, many others had this problem with Ubuntu 9.10. After a day and a half I managed to fix the sound (compiling alsa, etc), but the TS continuity error came back on vdr. Is ubuntu using Pulse Audio volume control? In many cases I like pulse way of allowing to manage and switch between multiple sound cards inputs and outputs even application by application but at least with Mandriva the old configs have been lost couple of times and I have needed to run both the alsaconfig and pulseaudio config for my system to get things working fine. I use spdif output and couple of times after system updates I have not had any sounds available. In those cases I have needed to: 1)alsamixer -c (-- unmute spdif output) 2)pulse-audio config (select spdif for default output channel instead of hdmi and check from the application view that apps running realized the config change. 3) check that my denon amplifier realized the config change by pressing auto button that forces it's to check both the digital and analog input... Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [OT] ARM based devices for VDR server and client
The goal is to have a VDR device which consumes the ???least possible??? amount of power. I heard that ARM based devices are good for this. Does anyone on this list have any experiences using ARM based devices? 1. Since the boards are mostly small one needs to use mostly USB devices, doesn???t one? 2. Is the performance high enough to playback SDTV? It should. 3. What about HDTV? I have N810 (Arm 2420 Omap) and tested the playback of sdtv with it by using the mplayer as a player which connected to VDR streamdev server. For a while the playback was good but then there were also moments where the playback or sounds get scattered. For fun I was also planning to build the vdr-sxfe for N810 but newer finished that one... (I was not able to find prebuild xine-libs and friends for Maemo, so I would have needed to build those and couple of other dependencies first and I did not had enough time for that) 4. Especially the Beagle Board [1][2] was covered a lot in the press. But it is not completely free, i. e. the specifications and the toolchain is not freely available, is not it [3]? Sorry, if I am wrong about this. Openembedded supports beagleboard among many other targets so you can use that to build toolchain, bootable image and applications for the beagleboard. (See the angstrom distribution for example) Mika___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] vdr-remoteosd-0.1.0 and vdr-svdrposd-0.1.0
I just published new releases of the plugins remoteosd and svdrposd (formerly svdrpext) on http://vdr.schmirler.de. The most important changes are the overdue gettext support for remoteosd and a major speedup of the remote menu in combination with the new svdrposd plugin. The remoteosd plugin provides access to the menu of an other VDR. Remoteosd relies on the svdrpservice plugin, which is also available from my website. I renamed the svdrpext plugin to svdrposd. The plugin publishes the textual contents of the OSD menu on SVDRP. In order to access the menu of a remote VDR using the remoteosd plugin, svdrposd or its successor svdrpext must be installed on the remote VDR. Hi, I got interested in from your plugins and tried to read throught your web page to get more info. So if I understood correctly the svdrpservice plugin provides the highway howto communicate from client to vdr server. But after that I get a little lost what are the cases where I should use your plugins... I mean currently I have 1 vdr server with dvb-t and dvb-c cards, xineliboutput server and streamdev server plugins running on it. Then from other client computers I can use either mplayer or xineliboutput client (vdr-sxfe) for connecting to this server for watching the tv. Currently my setup has however a that kind of limitation that all vdr-sxfe clients are forced to watch the same channel and whenever any of the clients change channel, the channel will be changed also to every other vdr-sxfe clients. I have read this could be somehow be avoided by running multiple vdr servers on the server machine and then forcing each client to connect to own vdr server port... Are your plugins meant for solving a that kind of multiple clients want to watch different channel problems or for which purpose your are using these plugins? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr-sxfe cvs version segfault with vdr 1.7.8
#0 0x7f6df3823208 in ?? () from /usr/lib64/libdbus-glib-1.so.2 #1 0x7f6df3818fd2 in ?? () from /usr/lib64/libdbus-glib-1.so.2 #2 0x7f6df3819b70 in dbus_g_proxy_call () from /usr/lib64/libdbus-glib-1.so.2 #3 0x0041306a in gnome_screensaver_control (enable=0) at tools/gnome_screensaver.c:93 This should be fixed in CVS now. Thanks, just tested and it worked now fine on my x86_64 system. Closing of vdr-sxfe (by mouse clicking the close icon in dialog title bar) has some problem. It will stop displaying the the video-stream but will not close the vdr-sxfe dialog itself. To close the app, I need to use killall -9 vdr-sxfe. killall vdr-sxfe without -9 will not work. Below is the gdb strace from that one. Lines after the [demux_vdr] PMT changed happens after I try to close the vdr-sxfe. [lam...@tinka vdr-1.7.8]$ gdb vdr-sxfe GNU gdb 6.8-6mdv2009.1 (Mandriva Linux release 2009.1) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-mandriva-linux-gnu... (gdb) run Starting program: /usr/local/bin/vdr-sxfe [Thread debugging using libthread_db enabled] vdr-sxfe 1.0.90-cvs (build with xine-lib 1.1.16, using xine-lib 1.1.16) VDR server not given, searching ... Found VDR server: host 192.168.3.101, port 37890 [New Thread 0x7f8eedab76f0 (LWP 12845)] [12845] [vdr-fe]GNOME screensaver disabled [New Thread 0x7f8ee5694950 (LWP 12858)] [New Thread 0x7f8ee29d6950 (LWP 12859)] [New Thread 0x7f8ee0cf6950 (LWP 12860)] [New Thread 0x7f8edc4f4950 (LWP 12861)] [New Thread 0x7f8edbafe950 (LWP 12862)] [New Thread 0x7f8edb130950 (LWP 12863)] [New Thread 0x7f8eda92f950 (LWP 12864)] [12845] [vdr-fe]Detected 2 CPUs [12845] [vdr-fe]Enabling FFmpeg multithreaded video decoding [12845] [input_vdr] Connecting (control) to tcp://192.168.3.101:37890 ... [12845] [input_vdr] Server greeting: VDR-1.7.8 xineliboutput-1.0.90-cvs READY [12845] [input_vdr] Connected (control) to tcp://192.168.3.101:37890 [12845] [input_vdr] Connecting (data) to pipe:///home/lamikr/vdr/vdr-1.7.8/plugins/xineliboutput/pipes.12021/pipe.0 [12845] [input_vdr] Data stream connected (PIPE) [New Thread 0x7f8ed9f0c950 (LWP 12866)] [New Thread 0x7f8ed94f0950 (LWP 12867)] [New Thread 0x7f8ed8cef950 (LWP 12868)] [12845] [demux_vdr] Using decoder libmpeg2 for mpeg2 video [12845] [demux_vdr] Using decoder FFmpeg for H.264 video [New Thread 0x7f8ed84ee950 (LWP 12869)] Press Esc to exit [New Thread 0x7f8ed7ced950 (LWP 12870)] Detaching after fork from child process 12871. Detaching after fork from child process 12872. [12869] [demux_vdr] Got PAT, PMT pid = 132, program = 132 [12869] [demux_vdr] PMT changed [Thread 0x7f8ed84ee950 (LWP 12869) exited] [Thread 0x7f8ed8cef950 (LWP 12868) exited] [Thread 0x7f8ed94f0950 (LWP 12867) exited] [12845] [input_vdr] Connections closed. Terminating... [Thread 0x7f8ed9f0c950 (LWP 12866) exited] Detaching after fork from child process 12889. [12870] [vdr-fe]Keyboard thread terminated [Thread 0x7f8ed7ced950 (LWP 12870) exited] [Thread 0x7f8eda92f950 (LWP 12864) exited] [Thread 0x7f8edb130950 (LWP 12863) exited] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-sxfe cvs version segfault with vdr 1.7.8
I tried today use vdr-1.7.8 with the latest cvs version of xineliboutput but the client is segfaulting for me once it has found the vdr server. Is the same happening also for others or is there some known xineliboutput revision that works with 1.7.8? (mplayer + streamdev server seemed to work for me with 1.7.8) I pasted the gdb strace below: [lam...@tinka vdr-1.7.8]$ gdb vdr-sxfe GNU gdb 6.8-6mdv2009.1 (Mandriva Linux release 2009.1) Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-mandriva-linux-gnu... (gdb) run Starting program: /usr/local/bin/vdr-sxfe [Thread debugging using libthread_db enabled] vdr-sxfe 1.0.90-cvs (build with xine-lib 1.1.16, using xine-lib 1.1.16) VDR server not given, searching ... Found VDR server: host 192.168.3.101, port 37890 [New Thread 0x7f6df47b26f0 (LWP 27010)] Program received signal SIGSEGV, Segmentation fault. 0x7f6df3823208 in ?? () from /usr/lib64/libdbus-glib-1.so.2 Missing debug package(s), you should install: dbus-debug-1.2.4.4permissive-2mdv2009.1.x86_64 dbus-glib-debug-0.80-1mdv2009.1.x86_64 gcc-debug-4.3.2-5mnb2.x86_64 glib2.0-debug-2.20.1-1mdv2009.1.x86_64 glibc-debug-2.9-0.20081113.5mnb2.x86_64 libjpeg-debug-6b-44mdv2009.1.x86_64 libx11-debug-1.2.1-1.2mdv2009.1.x86_64 libxau-debug-1.0.4-1mdv2009.1.x86_64 libxcb-debug-1.2-1mdv2009.1.x86_64 libxcursor-debug-1.1.9-3mdv2009.1.x86_64 libxdmcp-debug-1.0.2-6mdv2009.1.x86_64 libxext-debug-1.0.5-2mdv2009.1.x86_64 libxfixes-debug-4.0.3-4mdv2009.1.x86_64 libxinerama-debug-1.0.3-2mdv2009.1.x86_64 libxrandr-debug-1.3.0-1mdv2009.1.x86_64 libxrender-debug-0.9.4-4mdv2009.1.x86_64 pcre-debug-7.8-3mdv2009.1.x86_64 xine-lib-debug-1.1.16.3-1plf2009.1.x86_64 zlib-debug-1.2.3-13mdv2009.1.x86_64 (gdb) bt #0 0x7f6df3823208 in ?? () from /usr/lib64/libdbus-glib-1.so.2 #1 0x7f6df3818fd2 in ?? () from /usr/lib64/libdbus-glib-1.so.2 #2 0x7f6df3819b70 in dbus_g_proxy_call () from /usr/lib64/libdbus-glib-1.so.2 #3 0x0041306a in gnome_screensaver_control (enable=0) at tools/gnome_screensaver.c:93 #4 0x00407c7b in sxfe_display_open (this_gen=0x9fd120, xpos=value optimized out, ypos=0, width=0, height=0, fullscreen=0, hud=0, modeswitch=0, modeline=0x4164f0 , aspect=1, keyfunc=0, no_x_kbd=0, gui_hotkeys=value optimized out, video_port=0x0, scale_video=value optimized out, field_order=0, aspect_controller=0x0, window_id=-1) at xine_sxfe_frontend.c:1243 #5 0x00411c88 in main (argc=value optimized out, argv=0x7fffa411ed18) at xine_frontend_main.c:710 (gdb) Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] A new possibility for lower power high performance VDR
I have myself thinked about the possibility of running vdr/xineliboutput client on low end systems that just have usb 2.0 but not any graphic cards or free pci slots available. Has anybody experiences from the usb vga or usb dvi graphic card adapters like these? http://gizmodo.com/gadgets/adapter/usb-to-dvi-adapter-expands-screen-space-without-adding-video-cards-316944.php http://www.ipcmax.com/product_info.php?products_id=1238 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr 1.7.4 xineliboutput
did you check it with dvb-s2 h264 hdtv channels too ? At least arte worked for me about 1 or 2 week ago released xineliboutput cvs version. I however noticed it to be a little unstable in my system. (crashed much easier than 1.0.4 with 1.6.0) Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.0 S2API - Channels not Available
Due to an attempt on OS upgrade and thus kernel upgrade I'm grudgingly (it worked for me for months with no issues so why would I want to change it for now?) trying to make the transition from multiproto to S2API. I have two DVB-T cards and a NOVA-S2-HD (HVR4000 lite). I have downloaded a vanilla vdr-1.7.0 applied the h264 patch and the s2api patch and install S2API from Steven Toth's mercurial repository. Can you try with vdr-1.7.4, that's the first version from vdr 1.7x series that i got working with s2api and hvr-4000. I have testeed it with streamdev server plugin and mplayervlc. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.4
VDR developer version 1.7.4 is now available at Something made the hvr-4000 to work with this version of driver. With exactly same drivers and channel.conf file and streamdev-plugin and mplayer, the vdr-1.7.3 is not able to tune dvb-s channels but vdr-1.7.4 works :-) Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] PMT in multiple TS packet bug
I did check the TS stream with dvbsnoop and it is not containing corrupted TS packets. Apparently VDR is able to parse the PMT the first time the data buffer is used. Then, it seems to loose the sync inside the payload. I have attached a raw TS capture (~10M) containing the PMT pid 132 which is revealing the problem. http://alexw.org.lu/upload/pmt.pid.132.ts Could this patch help with vdr-1.7.3? http://article.gmane.org/gmane.linux.vdr/39097 Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] about the hvr-4000 tuning problems
I have following in my channel conf for dvb-t and dvb-s channels: YLE TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 Concerning Arte, I've got that same setting in my channels.conf. And I'm able to see that channel instantly. Klaus, do you have any idea from which functions I should try to track more for finding the problem? I use a Hauppauge NOVA-HD-S2 and I've updated to the latest S2API drivers on the s2-liplianin repository. It uses the same kernel-driver as the HVR-4000. And I don't have any tuning problems at all on Hotbird 13.0, Astra 19.2, Astra 23.5 and Astra 28.2. This is with VDR 1.7.0 and my own S2API patch as well as with VDR 1.7.3. I have tried both with the s2-liblianin and v4l-dvb versions of the drivers and I do not see any differences. scan,szap,szap-s2,scan-s2 and vdr-1.6.0 works ok with all of them. It's just that neither vdr-1.7.0 with your patches or vdr-1.7.2 or vdr-1.7.3 without patches are working. By any chance, did you try disabling diseqc? Because I had tuning problems when I used standard diseqc values with no retries with my diseqc 1.0 switch. I had to use the following safe diseqc commands for my diseqc 1.0 configuration: I do not have diseqc in my system and I checked that at least the cDvbTuner::SetFrontEnd() method from dvbdevice.c detected that correctly and went to else part of the block. (=no diseqcs) When I try to change to a (not previously tuned with szap) dvb-s/s2 channel, vdr will just notice that the tunerStatus variable in Action() method is = 2, which means that tuned. It will never go to state 3 which means locked. With szap-s2,szap or vdr-1.6.0 I can however get the locks immediately. So I am wondering that what could be the most potential places in vdr code where I should try to make some changes to tuning/locking code for testing. Is it the cDvbTuner::SetFrontEnd method or is there also some other methods that are really interfacing with S2API and could affect to the tuning or locking? Mika # # port 1 S19.2E 11700 V 9750 t v W15 [E0 10 38 F0] W100 [E0 10 38 F0] W100 [E0 11 00] W100 A W15 t S19.2E 9 V 10600 t v W15 [E0 10 38 F1] W100 [E0 10 38 F1] W100 [E0 11 00] W100 A W15 T S19.2E 11700 H 9750 t V W15 [E0 10 38 F2] W100 [E0 10 38 F2] W100 [E0 11 00] W100 A W15 t S19.2E 9 H 10600 t V W15 [E0 10 38 F3] W100 [E0 10 38 F3] W100 [E0 11 00] W100 A W15 T # port 2 S13.0E 11700 V 9750 t v W15 [E0 10 38 F4] W100 [E0 10 38 F4] W100 [E0 11 00] W100 B W15 t S13.0E 9 V 10600 t v W15 [E0 10 38 F5] W100 [E0 10 38 F5] W100 [E0 11 00] W100 B W15 T S13.0E 11700 H 9750 t V W15 [E0 10 38 F6] W100 [E0 10 38 F6] W100 [E0 11 00] W100 B W15 t S13.0E 9 H 10600 t V W15 [E0 10 38 F7] W100 [E0 10 38 F7] W100 [E0 11 00] W100 B W15 T # port 3 S23.5E 11700 V 9750 t v W15 [E0 10 38 F8] W100 [E0 10 38 F8] W100 [E0 11 00] W100 A W15 t S23.5E 9 V 10600 t v W15 [E0 10 38 F9] W100 [E0 10 38 F9] W100 [E0 11 00] W100 A W15 T S23.5E 11700 H 9750 t V W15 [E0 10 38 FA] W100 [E0 10 38 FA] W100 [E0 11 00] W100 A W15 t S23.5E 9 H 10600 t V W15 [E0 10 38 FB] W100 [E0 10 38 FB] W100 [E0 11 00] W100 A W15 T # port 4 S28.2E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.2E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.2E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.2E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T S28.5E 11700 V 9750 t v W15 [E0 10 38 FC] W100 [E0 10 38 FC] W100 [E0 11 00] W100 B W15 t S28.5E 9 V 10600 t v W15 [E0 10 38 FD] W100 [E0 10 38 FD] W100 [E0 11 00] W100 B W15 T S28.5E 11700 H 9750 t V W15 [E0 10 38 FE] W100 [E0 10 38 FE] W100 [E0 11 00] W100 B W15 t S28.5E 9 H 10600 t V W15 [E0 10 38 FF] W100 [E0 10 38 FF] W100 [E0 11 00] W100 B W15 T Mika Regards, Niels Wagenaar ___ 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] about the hvr-4000 tuning problems
Hi I have tried to add some more printouts to dvbdevice.c for trying to understand why the vdr-1.7.x fails to tune to dvb-s or dvb-s2 channels. hvr-1300 is in /dev/dvb/adapter0 and hvr-4000 is in /dev/dvb/adapter1 I added printouts to SetFrontEnd() and Action() methods. In SetFrontEnd() method it seems that the code is at least always going to correct if/else block. (No, diseq, dvb-t, dvb-s or dvb-s2 depending on what channel I try to tune) If I watch dvb-t channel (which works), I can see a following logs: Action(): cardIndex: 0, tunerStatus: 1, NewStatus: 0 SetFrontEnd(): DVB-T, fd_frontend: 4, cardIndex: 0 Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 1 ... Action(): cardIndex: 0, tunerStatus: 2, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 frontend 0 regained lock on channel 1, tp 546 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 3, NewStatus: 31 ... If I instead try to tune to new dvb-s channel that I have not previously pre-tuned with szap or szap-s2 (for example arte), vdr will fail to show the channel and I can see a following: Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 31 Action(): cardIndex: 1, tunerStatus: 1, NewStatus: 31 Setup.DiSeqC == false SetFrontEnd(): DVB-S, fd_frontend: 6, cardIndex: 1 (frequency * 1000UL): 993000 channel.Modulation(): 9 channek.Srate() * 1000UL): 2200 channel.CoderateH(): 5 channel.Inversion(): 2 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 3 frontend 1 lost lock on channel 5, tp 110743 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 3 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 1 ... If I have pre-tuned for example to same arte with szap-s2, then vdr is able to show that channel, and I get a following output: Action(): cardIndex: 1, tunerStatus: 0, NewStatus: 1 Action(): cardIndex: 1, tunerStatus: 1, NewStatus: 3 Setup.DiSeqC == false Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 SetFrontEnd(): DVB-S, fd_frontend: 6, cardIndex: 1 (frequency * 1000UL): 993000 channel.Modulation(): 9 channek.Srate() * 1000UL): 2200 channel.CoderateH(): 5 channel.Inversion(): 2 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 2, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 frontend 1 regained lock on channel 5, tp 110743 Action(): cardIndex: 0, tunerStatus: 0, NewStatus: 0 Action(): cardIndex: 1, tunerStatus: 3, NewStatus: 31 ... I have following in my channel conf for dvb-t and dvb-s channels: YLE TV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0 Klaus, do you have any idea from which functions I should try to track more for finding the problem? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
Have you tried to compile vdr with the livebuffer patch? This makes xineliboutput work with VDR (at least 1.7.1). No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one? - http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch only for vdr-1.5 - VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3) - VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
In the bugtracker you'll find a patch which makes streamdev compile again. It comments out the PES output stuff which causes the problems until a clean solution is available. http://www.vdr-developer.org/mantisbt/view.php?id=506 Thanks, I applied that patch and streamdev build then fine for vdr-1.7.3 Here are my test results. (5 days old s2-liplianin, hvr-1300 for dvb-t and hvr-4000 for dvb-s/s2) 1) Watching and switching between DVB-T channels (both withing same mux or different muxes) worked ok just by giving commands like mplayer http://localhost:3000/TS/1 mplayer http://localhost:3000/TS/3 2) Watching of DVB-S and DVB-S2 worked most of the times if I did it in the following sequence - close vdr-1.7.3 - switch to dvb-s/dvb-s2 channel for example by using ./szap-s2/szap-s2 -a 1 -S 2 -c channels.conf arteHD - close szap-s2 with ctrl-c - launch vdr-1.7.3 - open same channel that was earlier szapped: mplayer http://localhost:3000/TS/6 If I did not pre-tuned s/s2 channel I wanted to watchfirst with szap, mplayer just showed in console: Connecting to server localhost[127.0.0.1]: 3000... Cache size set to 320 KBytes Cache fill: 0.00% (0 bytes) Sometimes I also needed to use szap-s2 multiple times for being able to watch s2 channels. On those failing cases mplayer showed Cache fill: 0.00% (0 bytes) TS file format detected. VIDEO MPEG2(pid=6210) AUDIO MPA(pid=6221) NO SUBS (yet)! PROGRAM N. 0 Stream not seekable! Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
No, and I am little confused where is the version I could try with vdr.1.7.x. I found out 3 candidates while googling, should I try one of these with vdr-1.7.3 or some other one? - http://home.vrweb.de/~bergwinkl.thomas, This page mentions the patch only for vdr-1.5 - VDR-Extensions-Patch-65/vdr-1.7.2_extensions.diff seems to include livebuffer patch (but has unfortunately also many other patches within same patch and wont propably apply with 1.7.3) - VDR-Extensions-Patch-65/plugin-patches/setup-0.3.1-livebuffer.diff You should be able to use the VDR Extensions Patch 65 (with VDR 1.7.2). I have not tried it soo far, as I am still running VDR 1.7.1. You can enable single pathes in the patch pack, so you don't have to apply them all. What's this patch pack? Do you mean the patch selection by commenting/uncommenting individual patches from Make.config.template that the vdr-1.7.2_extensions.diff modifies? Anyway, for vdr-1.7.3, the vdr-1.7.2_extensions.diff failed to apply in many places. For vdr-1.7.2 the patch applied as expected, but I have not yet tried the LiveBuffer/vdr-xineliboutput in there. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] S2-3200 vdr needed material ?
Q to all : The software output plugins had problems with 1.7.1 and 1.7.2 ( and perhaps 1.7.3?). Can anybody confirm that this problem still exists? Because the reason why I don't upgrade to newer editions, is because newer versions had problems with the vdr-xine and vdr-xineliboutput plugins. Seems still to have. At least xineliboutput-1.0.3 builded but failed to work with 1.7.3. (vdr-sxfe outputs lot of error messages when running). I did not test the cvs version but at least that also failed with vdr-1.7.2. latest streamdev from CVS failed to build again 1.7.3 (builded ok with 1.7.2 and could be used for showing data once if I just had first tuned to some channel with szap/szap-2 before launching vdr-1.7.2. This is probably a hvr-4000 S2API driver bug) Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
Try typecasting the first parameter, as in off_t headdrop = min(off_t(curpos - totwritten), off_t(totwritten * 2)); Klaus I think the compiler is not the problem (same version). Trying the next option. gcc (SUSE Linux) 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] Copyright (C) 2008 Free Software Foundation, Inc. I had same problem with gcc 4.3.2 on Mandriva. (x86_64 env) Adding off_t() typecasting for the first parameter as you suggested fixed it. Klaus do you remember to fix it for next version without patch? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.3
gcc (SUSE Linux) 4.3.1 20080507 (prerelease) [gcc-4_3-branch revision 135036] Copyright (C) 2008 Free Software Foundation, Inc. I had same problem with gcc 4.3.2 on Mandriva. (x86_64 env) Adding off_t() typecasting for the first parameter as you suggested fixed it. Klaus do you remember to fix it for next version without patch? If you're using the same compiler as I do, I don't see why such a typecast is necessary on your side, while on my side it compiles just fine. Are you using any different compiler options than me? At least not intentionally. I just - downloaded and extracted vdr-1.7.3.tar.bz2 - cp Make.config.template Make.config - added to Make.config: DVBDIR = ..path to my dvb-v4l driver sources) - make -- got the error Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Support for different frame rates? (Re: Frames per second PAL vs. NTSC)
I checked boxstar web-page (http://boxstar.sourceforge.net/index.html) and I have to say that the goal of the project is ambiguous. Hopefully the developer can actually do it. Do you mean ambitious? Yes, it is going to be a big challenge, but hopefully it'll get there one day. At least for now it seems to use vdr as a backend. Has anybody tested it. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
Hmm, the differences in my and your setup are
1) I have also hvr-1300 in my system (for dvb-t)
2) I modified the vdr sources instead of modifying the driver for
informing the system from the S2 capabilities (klaus explained also that
method in his 1.7.2 announcements). I can re-test this in another way once
the 2G_CAP patch is applied to v4l-dvb repository.
I applied Klaus latest patch to v4l-dvb source and changed
FE_CAN_2ND_GEN_MODULATION to FE_CAN_2G_MODULATION in dvbdevice.c.
Do you have MFE's version of v4l-dvb aswell ?
Yes, I have. I am actually now using 2 day old version from
http://linuxtv.org/hg/v4l-dvb which includes the FE_CAN_2G_MODULATION
flag support in driver.
And now I am finally able to watch the
HD content with my vdr 1.7.2 and streamdev server plugin by using mplayer
or vlc as a client with HVR-4000.
BUT there is somewhere bug in the vdr channel tuning because it seems that
if I want to watch dvb-s or dvb-s2 channels, I must first tune to correct
channel with vdr-1.6.0 or with szap-s2...
I tried to put step by step guide/notes how I got VDR172/h264 KIND of
working... Maybe you could get it working in similar way...
1) Build and install latest v4l-dvb drivers
2) Checkout s2-szap from http://mercurial.intuxication.org/hg/szap-s2
(I am using couple of weeks old version), and change INCLUDE line in
Makefile to point your v4l-dvb driver sources. I have for example
INCLUDE=-I/home/lamikr/dvb/drivers/20081231/v4l-dvb/linux/include
Then build it.
3) Add hd channel info to szap2 channels.conf With astra-28.2E I can
use following with szap2channels.conf
arteHD:11361:hC23M5O35S1:S19.2E:22000:6210:6230:0:11120:1:1011:0
4) Test whether tuning works with szap2, I use
[lam...@tinka szap-s2]$ ./szap-s2 -a 1 -S 2 -c szap2channels.conf arteHD
ERROR: invalid value for parameter ''
reading channels from file 'szap2channels.conf'
zapping to 1 'arteHD':
delivery DVB-S2, modulation 8PSK
sat 0, frequency 11361 MHz H, symbolrate 2200, coderate 2/3, rolloff
0.35
vpid 0x1842, apid 0x1856, sid 0x
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 1f | signal d000 | snr | ber | unc |
FE_HAS_LOCK
status 1f | signal c2c0 | snr 8b33 | ber | unc |
FE_HAS_LOCK
(I could then try to record and watch from command line by using commands:
# dvbstream -c 1 8192 -o test3.mpg
# vlc test3.mpg
)
4) Extract vdr-1.7.2 (I have cloned from unofficial vdr git repo)
5) Apply attached 2G modulation support patch for vdr-1.7.2 (due to flag
name change in official V4L-DVB drivers)
patch -p1 ../vdr172_v4ldvb_2g_modulation_support.patch
6) Apply h264 support patch for vdr-1.7.2 that has been earlier send to
mailing list:
patch -p1
../vdr-1.7.2-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff
7) download and configure latest dvbstreamdev plugin from cvs
- update plugins/streamdev/streamdevhosts.conf
- update svdrphosts.conf
- update runvdr
(VDRCMD=$VDRPRG --lirc -w 15 -c
/home/lamikr/dvb/vdr/vdr-git -Pstreamdev-server)
8) Include arteHD info to top of the vdr channels.conf
arte;ARD:10743:hC56M5O0S0:S19.2E:22000:401=2:402=deu,403=fra:404:0:28724:1:1051:0
arte
HD;ZDFvision:11361:hC23M16O35S1:S19.2E:22000:6210=27:6221=deu,6222=fra:6230:0:11120:1:1011:0
9) Make sure you have tuned to arteHD with szap-s2 and then closed szap
(see step 4)
10) launch vdr 1.7.2 with runvdr
11) watch arteHD with
vlc http://localhost:3000/TS/2
If I now would like to watch arte instead, I would need to close vdr,
szap first from command line and then re-launch vdr...
Btw... I now really envy the vdpay/nvidia cpu usage as with 780G
motherboard I have...
Tasks: 174 total, 3 running, 171 sleeping, 0 stopped, 0 zombie
Cpu(s): 55.4%us, 3.5%sy, 0.5%ni, 40.5%id, 0.0%wa, 0.0%hi, 0.2%si,
0.0%st
Mem: 1799896k total, 1779300k used,20596k free, 272416k buffers
Swap: 8185076k total, 176k used, 8184900k free, 728196k cached
PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND
8866 lamikr20 0 598m 57m 20m S 108 3.2 0:23.90 vlc
8854 root 20 0 214m 24m 4460 S2 1.4 0:01.12 vdr
5200 lamikr 9 -11 224m 5776 3848 S2 0.3 1:31.79 pulseaudio
diff --git a/dvbdevice.c b/dvbdevice.c
index e0b05a1..08dc63f 100644
--- a/dvbdevice.c
+++ b/dvbdevice.c
@@ -32,7 +32,7 @@
// unpatched driver. However, with an unpatched driver it will not support
// DVB-S2 hardware. If you have DVB-S2 hardware you need to either patch
// the driver or modify the line that uses this macro in
cDvbDevice::cDvbDevice().
-#define FE_CAN_2ND_GEN_MODULATION 0x1000
+#define FE_CAN_2G_MODULATION 0x1000
#define DO_REC_AND_PLAY_ON_PRIMARY_DEVICE 1
#define DO_MULTIPLE_RECORDINGS 1
@@ -491,7 +491,7 @@ cDvbDevice::cDvbDevice(int n)
if (fd_frontend = 0) {
if (ioctl(fd_frontend, FE_GET_INFO, frontendInfo) = 0) {
switch (frontendInfo.type) {
- case
Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
BUT there is somewhere bug in the vdr channel tuning because it seems that if I want to watch dvb-s or dvb-s2 channels, I must first tune to correct channel with vdr-1.6.0 or with szap-s2... I give up... thank for your answer. Well, in reality my family also still use vdr-1.6.0 for real (tm) tv watching as xine-sfxe client is much handier for my child to use than launching mplayer/vlc with correct channel url from the console. But hopefully the h264 acceleration support in radeonhd drivers as well as the xineliboutput support for vdr-1.7.x is not far away anymore. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
I do not see such a behavior with stb0899 based TT-3200 here. Arte and ArteHD work out of the box with VDR-1.7.2 using this repository: http://mercurial.intuxication.org/hg/s2-liplianin Sure, had to add 2g flag in stb0899 source though. Before using this repository it was hardly possible to tune to ArteHD. Ok, so one would need to find out what are the real S2API tuning specific code in vdr h264 extension patches so that I could find out why vdr fails to tune with hvr-4000. Or actually maybe the correct answer is to understand what is the difference between those two S2-API drivers. Ok, I made more tests. 1) s2-liplianin drivers. - checked out - applied S2 capability patches from v4l-dvb drivers to s2-liplianin http://www.linuxtv.org/hg/v4l-dvb/rev/0f6097dd419c http://www.linuxtv.org/hg/v4l-dvb/rev/3e5f56413191 - compiler and rebooted computer 2) rebuild vdr and streamdev plugin - make clean in vdr-git and vdr-git/PLUGINS/src/streamdev directories - changed driver path in vdr-git/Make.config DVBDIR = /home/lamikr/dvb/drivers/20090103/s2-liplianin/linux - copied compiler.h from kernel sources to /home/lamikr/dvb/drivers/20090103/s2-liplianin/linux/include/linux/ - make make plugins - launched vdr -- mplayer and vlc were still unable to show arte or arteHD channels until I used szap/szap-s2 first I am using 64 bit version of Linux in AMD/780G system... Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
unfortunately, it also don't tune to DVB-S channels (I have applied Klaus patch to the v4l-dvb sources). Hi Does hvr-4000 tune for you to dvb-s channels if you do not apply the h264 patch? That's the case for me. I send previously an email from similar experiences to http://www.mail-archive.com/vdr@linuxtv.org/msg08635.html Mika Thanks. it took me some time to find out that my HVR-4000 don't work for DVB-S(2) with vdr-1.7.2. Looks like you have to add the 2nd generation flag to your driver. Otherwise, vdr-1.7.2 doesn't assume that your card can do DVB-S2. For stb0899 it looks like this: ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HVR-4000, vdr-1.7.2 and v4l-dvb'hg ?
Does hvr-4000 tune for you to dvb-s channels if you do not apply the h264 patch? That's the case for me. I send previously an email from similar experiences to http://www.mail-archive.com/vdr@linuxtv.org/msg08635.html Unfortunately I can't tune either without the h264 patch. Hmm, the differences in my and your setup are 1) I have also hvr-1300 in my system (for dvb-t) 2) I modified the vdr sources instead of modifying the driver for informing the system from the S2 capabilities (klaus explained also that method in his 1.7.2 announcements). I can re-test this in another way once the 2G_CAP patch is applied to v4l-dvb repository. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] H.264 support for VDR-1.7.2
attached you'll find an updated patch for VDR-1.7.2. The patch includes the formerly released remux fix. Hi The patch causes some problems in my system. If I run vdr-1.7.2 without your patch I can watch both the dvb-t and dvb-s channels by connecting to streamdev server plugin locally by using following commands mplayer http://localhost:3000/TS/3 But if I apply your patch on top of vdr-1.7.2, I can only connect to dvb-t channels with mplayer/streamdev-server from hvr-1300. But opening of dvb-s or dvb-s2 channels from hvr-4000 will now fail. I have in my channels.conf YLETV1;YLE:546000:B8C23G8M64T8Y0:T:27500:512=2:650=fin:2321:0:17:8438:4097:0 YLETV2;YLE:546000:B8C23G8M64T8Y0:T:27500:513=2:660=fin:2321:0:33:8438:4097:0 SkyNews;BT:11597:vC56M5O0S0:S19.2E:22000:305+131=2:306=eng:579:0:28707:1:1026:0 When I launch vdr, it will printout [r...@tinka vdr-git]# ./runvdr vdr: no primary device found - using first device! In user.log I can see after a failed mplayer/streamdev-server connection a following log messages: Dec 28 02:27:59 tinka vdr: [9175] Streamdev: Accepted new client (HTTP) 127.0.0.1:57817 Dec 28 02:27:59 tinka vdr: [9450] receiver on device 2 thread started (pid=9166, tid=9450) Dec 28 02:27:59 tinka vdr: [9451] TS buffer on device 2 thread started (pid=9166, tid=9451) Dec 28 02:27:59 tinka vdr: [9449] streamdev-livestreaming thread started (pid=9166, tid=9449) Dec 28 02:27:59 tinka vdr: [9448] streamdev-writer thread started (pid=9166, tid=9448) Dec 28 02:28:11 tinka vdr: [9175] client (HTTP) 127.0.0.1:57817 has closed connection Dec 28 02:28:11 tinka vdr: [9175] streamdev: closing streamdev connection to 127.0.0.1:57817 Dec 28 02:28:11 tinka vdr: [9449] streamdev-livestreaming thread ended (pid=9166, tid=9449) Dec 28 02:28:11 tinka vdr: [9448] streamdev-writer thread ended (pid=9166, tid=9448) Dec 28 02:28:11 tinka vdr: [9175] buffer stats: 0 (0%) used Dec 28 02:28:11 tinka vdr: [9451] TS buffer on device 2 thread ended (pid=9166, tid=9451) Dec 28 02:28:11 tinka vdr: [9450] buffer stats: 0 (0%) used Dec 28 02:28:11 tinka vdr: [9450] receiver on device 2 thread ended (pid=9166, tid=9450) and mplayer outputs Playing http://localhost:3000/TS/3. Resolving localhost for AF_INET6... Couldn't resolve name for AF_INET6: localhost Resolving localhost for AF_INET... Connecting to server localhost[127.0.0.1]: 3000... Cache size set to 320 KBytes Cache fill: 0.00% (0 bytes) nop_streaming_read error : Resource temporarily unavailable Cache fill: 0.00% (0 bytes) When I instead open dvb-t channel succesfully I can instead see Playing http://localhost:3000/TS/2. Resolving localhost for AF_INET6... Couldn't resolve name for AF_INET6: localhost Resolving localhost for AF_INET... Connecting to server localhost[127.0.0.1]: 3000... Cache size set to 320 KBytes Cache fill: 7.50% (24576 bytes) TS file format detected. VIDEO MPEG2(pid=513) AUDIO MPA(pid=660) NO SUBS (yet)! PROGRAM N. 33 Stream not seekable! Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
and change scan.c so that it first tunes to DVB-S2, as in
/* set up list of delivery systems*/
//fe_delivery_system_t delset[]={SYS_DVBS,SYS_DVBS2};
fe_delivery_system_t delset[]={SYS_DVBS2,SYS_DVBS};
Ok, I did run some tests.
I am using following setup
- kernel 2.6.27.1
- v4l-dvb drivers just updated today from linuxtv.org
- szap-s2 just updated today from
http://mercurial.intuxication.org/hg/szap-s2
- scan-s2 updated today from
http://mercurial.intuxication.org/hg/scan-s2/
- hvr-1300 as /dev/dvb/adapter0
(frontend0 for dvb-t)
- hvr-4000 as /dev/dvb/adapter1
(frontend 0 for s/s2, frontend 1 for dvb-t)
- astra-19-2.conf for s2-channels
S 11362000 H 2200 2/3
S 10743750 H 2200 2/3
- chan.conf for szap-s2 (not in vdr format)
arteHD:11361:hC23M5O35S1:S19.2E:22000:6210:6230:0:11120:1:1011:0
I have lot of issues, so I try to report them with numbers...
1) scan-s2 will work if I first tune to arte HD for a while with szap-s2
- ./szap-s2 -a 1 -S 2 -c channels.conf arteHD
--- will immediately get lock
- ctrl-c to stop szap-s2
- ./scan-s2 -a 1 -5 -o vdr astra-19-2.conf
...
Network Name 'ASTRA'
parse_section, section number 1 out of 1...!
dumping lists (6 services)
arte
HD;ZDFvision:11361:hS1C23M5O35:S19.2E:22000:6210:6221=ger,6222=fra:6230:0:11120:1:1011:0
Simul
SD;IRT:11361:hS1C23M5O35:S19.2E:22000:6310:6320=ger:0:0:11130:1:1011:0
Simul
HD;IRT:11361:hS1C23M5O35:S19.2E:22000:6410:6420=ger:0:0:11140:1:1011:0
arte
HD;ZDFvision:10743:hS0C56M2:S19.2E:22000:6210:6221=ger,6222=fra:6230:0:11120:1:1051:0
Simul SD;IRT:10743:hS0C56M2:S19.2E:22000:6310:6320=ger:0:0:11130:1:1051:0
Simul HD;IRT:10743:hS0C56M2:S19.2E:22000:6410:6420=ger:0:0:11140:1:1051:0
If I would have let the szap-s2 running, I could have received the
channels also without astra-19-2.conf file by running
./scan-s2 -a 1 -5 -o vdr -c
2) After step (1) I can not newer use vdr-1.7.1 again for locking dvb-s
channels with vlc/streamdev plugin (dvb-t channels from hvr-1300 still
scans ok)
- launch vdr-1.7.1 (with latest Klaus s2-api patch for vdr-1.7.1)
- vlc http://localhost:3000/PES/18
I can get vlc/vdr-1.7.1 to work again with S-channels, if I first launch
vdr-1.6.0 and use use xine-liboutput to tune some S-channels.
3) I am not able to watch S2 channels with vdr-1.7.1/streamdev plugin/vlc
compination (I can not connect crt tv to my ff cards directly so I must
use plugin)
I have added following to vdr-1.7.1 channel.conf
arteHD;ZDFvision:11361:hS1C23M5O35:S19.2E:22000:6210:6221=ger,6222=fra:6230:0:11120:1:1011:0
SimulSD;IRT:11361:hS1C23M5O35:S19.2E:22000:6310:6320=ger:0:0:11130:1:1011:0
SimulHD;IRT:11361:hS1C23M5O35:S19.2E:22000:6410:6420=ger:0:0:11140:1:1011:0
With vlc http://localhost:3000/PES/channel-number I am able to tune only
the SimulSD channel, not arteHD or SimulHD
After trying these, I am again in situaion described in step (2)
and I must first use vdr-1.6.0/xine-liboutput to tune S channels
to get vdr-1.7.1 to be able to tune to them.
4) xine-liboutput plugin does not work with vdr-1.7.1 not even for dvb-t
or dvb-s channels, while streamdev-server/vlc compination works ok except
in case (2).
5) I can tune and watch arteHD with following commands from command line:
- szap_channels.conf
arteHD:11361:hC23M5O35S1:S19.2E:22000:6210:6230:0:11120:1:1011:0
- ./szap-s2 -a 1 -S 2 -c szap_channels.conf arteHD
- dvbstream -c 1 8192 -o test3.mpg
- vlc test3.mpg
Here are still the full outputs from scan-s2. First once using first
vdr-1.6.0 for tuning with old api to S-channels. And then
the succesfull case after firts using szap-s2 to tune artehd.
[lam...@tinka scan-s2]$ ./scan-s2 -a 1 -o vdr astra-19-2.conf
API major 5, minor 0
scanning astra-19-2.conf
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S2 11362000 H 2200 2/3 AUTO AUTO
initial transponder DVB-S 11362000 H 2200 2/3 AUTO AUTO
initial transponder DVB-S2 10743750 H 2200 2/3 AUTO AUTO
initial transponder DVB-S 10743750 H 2200 2/3 AUTO AUTO
-- Using DVB-S2
tune to: 11362:hS1C23:S0.0W:22000:
DVB-S IF freq is 1612000
WARNING: tuning failed!!!
tune to: 11362:hS1C23:S0.0W:22000: (tuning failed)
DVB-S IF freq is 1612000
WARNING: tuning failed!!!
-- Using DVB-S
tune to: 11362:hS0C23:S0.0W:22000:
DVB-S IF freq is 1612000
WARNING: tuning failed!!!
tune to: 11362:hS0C23:S0.0W:22000: (tuning failed)
DVB-S IF freq is 1612000
WARNING: tuning failed!!!
-- Using DVB-S2
tune to: 10743:hS1C23:S0.0W:22000:
DVB-S IF freq is 993750
WARNING: tuning failed!!!
tune to: 10743:hS1C23:S0.0W:22000: (tuning failed)
DVB-S IF freq is 993750
WARNING: tuning failed!!!
-- Using DVB-S
tune to: 10743:hS0C23:S0.0W:22000:
DVB-S IF freq is 993750
WARNING: tuning failed!!!
tune to: 10743:hS0C23:S0.0W:22000: (tuning failed)
DVB-S IF
Re: [vdr] VDR with S2API (update)
But for anybody who wants to use a beamer these FF-cards are full pain with there stupid outputs. I (and many others) want DVI/HDMI/Display-Port. And I want beamer that has a network card and can download and show the content downloaded from vdr server. I don't know whether they could connect to streamdev-server or xineliboutput server plugins. Struggling with xineouput or xineplugin or softdevice is a real pain. Same for direct AC3 output on SPDIF. I btw. played in this evening with N810 and checked whether the device was powerful enough for connecting to VDR and showing tv. It was as the compination of streamdev server on vdr and mplayer on N810 worked really well over wlan with following command on N810. mplayer http://my-vdr-server:3000/PES/channel-number With vdr-xine I was not yet as lucky, I build the xine-libs and vdr-sxfe with scratchbox but sofar at least Xv or xshm video outputs failed to work. I will need to investigate this furher... Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR with S2API (update)
BTW. Softdevice/play, vdr-xine and xineliboutput are able to play youtube divx etc. Is there btw any vdr-plugin for browsing you tupe content (like most watched, movie trailers, etc...) and playing them. Another nice plugin would be a something where you could select some of your recordings and then say that compress these to divx or dirac with these resolutions (Some recordings I would propably want to produce with 1 shot for original size , N810 screen size and 320x200 ipaq screen size. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput sxfe / xxmc / via / EPIA ML6000 : great !
Blah, only one PCI slot. Where are proper low-power MB's with 2 or more PCI slots for DVB-cards? Asrock A780FullDisplay without DisplayPort card AMD Athlon X4 3850e 2GB DDR2-800 DVD/RW 300W 80+ Green 1x Momentus 7200.3 250GB 2,5 3x WD Caviar Green 1TB 3,5 Terratec Diversity (Dual Tuner) USB DVB-T 2x extra Fans While recording two DVB-T channels ~ 60W (UPS tells it). The WD drives build up a RAID5. The A780 chipset is nice for low-power needs. Yes, I have AMD 780G also in my vdr server and in clients I am currently using the vdr-xineliboutput. What I have now tried to search for is a fast booting client for my old P700, that could boot automatically to X with dummy user and then launch the vdr-xineliboutput. The ideal would be that once bios checks have been done, rest of the boot would for getting X and vdr client running would take less than 30 seconds from the bios checking, but currently I am very far from that and I am not sure what would be the best option for the client. 1) local harddisk for booting and launching X and vdr-sxfe 2) nfs mount from server for booting and launching X and vdr-sxfe 3) local harddisk booting X and connecting to server with XDMCP. (would video and audio work over XDMCP from server?) 4) lpts5 where some apps would be run from server, while multimedia like vdr-sxfe would be run from client harddisk What kind of solutions what boottimes you have for the clients? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput not working
and appear to be dead. Don't know what I'm missing, but that's for another thread. I still have segfaults on xineliboutput and can't identify why. AFAIK, nothing changed except for multiproto S2API, and some cvs/hg compiled software. Anyhow, RadeonHD drivers seem to be much better than Catalyst. Yes, only big missing thing that comes to my mind is that linuxtv does not work due to missing yuv2/xv support. Same failure was also with catalyst drivers. I would need that for connecting my wii hvr-1300 or 4000 so that I can see the picture with lcd monitor. This used to work just fine with my 10 year old computer with integrated intel graphic card :-( Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput not working
On Sunday 02 November 2008 12:46:16 Artem Makhutov wrote: Hi, On Sat, Nov 01, 2008 at 05:48:07PM +0100, horchi wrote: Hi, i like to use the actual vdr 1.7.1 with the xineliboutput plugin. I don't need h264 or any HDTV this time. Has anybody vdr 1.7.1 with xineliboutput running properly? No, xineliboutput does not work for me too with 1.7.1. It worked fine with 1.7.0. Regards, Artem Well, I have vdr 1.7.0 + h264 patch + s2api patch + cvs xineliboutput + hg xine-lib 1.2 + svn ffmpeg + s2 api drivers v4l-dvb and xineliboutput is _NOT_ working fine. It segfaults upon startup. Every time, no matter the parameters I pass during startup. Even vdr-xine experinces the same problems (jittered image but sound ok) but no segfaults on startup. Only during play live stream :( It seems it has problems with OSD and overlay Xv on ATI 1250 Express but and this a big but :) it also has the same behavior with a Geforce 6600GT that I have laying around. Is it happening for you both with S and S2 channels? Many people including me have noticed corrupted image problems with xineliboutput with commercial ATI drivers. (I tested myself last time about 2 months ago) A workaround was to switch to console ctrl+alt+1 and then back to X with ctrl+alt+7. To get things really workign without problems I switched to radeonhd drivers. I have myself using vdr 1.6.0 as I had problems to get dvb-t channels to work with S2API patched vdr-1.7.0 and have only tested S2 from command line with a combination of following: 1) channels.conf arteHD:11361:hC23M5O35S1:S19.2E:22000:6210:6230:0:11120:1:1011:0 2) ./szap-s2 -a 1 -S 2 -c channels.conf artehd 3) dvbstream -c 1 8192 -o test3.mpg 4) vlc test3.mpg Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Two different types of DVB card
Can VDR handle two different types of DVB card at once? I've got two different makes of DVB-T card at the moment, which is fine because they share one channels.conf, but I'm thinking of replacing one with DVB-S for HD. Can VDR assign a different channels.conf to each card and merge the channels list for the EPG? You can add both the dvb-t and dvb-s channels to same channel.conf. VDR is smart enough to recognize for which channels it needs to use dvb-t and for which it needs to use dvb-s card. I am currenlty for example using hvr-1300 (dvb-t) and hvr-4000 (dvb-s) just fine with vdr-1.6.0. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64 ( 071020008 )
you are using the older patch use the attached one.
The fix-s2api-dvbs is not needed with this one.
I have some comment from these patches as I tried to investigate the code
to find out why it does not work with my hvr-1300 and hvr-4000 in
vdr-1.7.1 and xineliboutput. With vdr-1.7.0 version of these patches, the
hvr-4000 is able to scan dvb-s channels ok but hvr-1300 fails to scan
dvb-t channels.
One thing that looks suspicious is that the code in
dvbdevice.c function cDvbDevice::cDvbDevice(int n).
I have hvr-1300 (dvb-t) as a first device and hvr-4000
(dvb-t+dvb-s/s2) as a second device.
For hvr-1300 this method reports incorrect transport modes DVBS DSS,
when it should report DVBT. For hvr-4000 it is reporting
the DVBS2, so it is halfly correct. I think it should report DVBS2
DVBT as I am using s2-mfe drivers and thus 2 frontends created under
/dev/dvb/adapter1.
Oct 18 00:00:23 tinka vdr: [28627] device 1 provides: DVBS DSS
...
Oct 18 00:00:23 tinka vdr: [28627] device 2 provides: DVBS2
I think there are couple of bugs in the code.
1) frontend.h in dvb-b drivers defines following types:
typedef enum fe_delivery_system {
SYS_UNDEFINED,
SYS_DVBC_ANNEX_AC,
SYS_DVBC_ANNEX_B,
SYS_DVBT,
SYS_DVBS,
SYS_DVBS2,
SYS_DVBH,
SYS_ISDBT,
SYS_ISDBS,
SYS_ISDBC,
SYS_ATSC,
SYS_ATSCMH,
SYS_DMBTH,
SYS_CMMB,
SYS_DAB,
} fe_delivery_system_t;
But in vdr-code those are compared to stings defined in following array:
const char *DeliverySystems[] = {
DVBS,
DSS,
DVBS2,
DVBC,
DVBT,
DVBH,
ATSC,
NULL
};
So both the order and amount of strings compared is different and I
do not understand how this if (frontendType (1u i)) is planned to
work.
If I have understood correctly this bug does not however explain why
my hvr-1300 does not work, as in the end this for loop is only used for
trying to detect whether the frontend type is SYS_DVBS2. For other types
it will just printout informative debug.
2) Second problem that comes to my mind is that the code seems to assume
that there is only 1 frontend for every adapter available, so it will not
detect if card supports for example both dvb-t and dvb-s. I do not know
yet, which would be the best place for making changes to support both.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] epg scan makes dvb-t tuning work unreliable
Hi My system has hvr-1300 (adapter0 connected terrestrial antenna for for dvb-t) and hvr-4000 (adapter1 connected to satellite dish for dvb-s, dvb-t antenna unconnected.) Whether I use just vdr-1.4.7, 1.6.0, 1.6.0-2 or 1.7.0 with or without any plugin, I have noticed that the dvb-t playback usually breaks about after 5-10 minutes and only reliable way to retune is to shutdown the vdr (ctrl-c for runvdr script and) and then restart it again. I have observed same behaviour every time over many days and for vdr-1.6.0 the /var/log/user.log shows always a following types of lines to be repeated. Oct 14 02:36:25 tinka vdr: [1965] logger 0 filter thread ended (pid=1919, tid=1965) Oct 14 02:36:58 tinka vdr: [1928] changing pids of channel 819 from 163+163:92:0:41 to 163+163:92:65=ell:41 Oct 14 02:37:19 tinka vdr: [1924] frontend 0 lost lock on channel 1, tp 546 Oct 14 02:37:19 tinka vdr: [1924] frontend 0 regained lock on channel 1, tp 546 Oct 14 02:37:21 tinka vdr: [1924] frontend 0 lost lock on channel 1, tp 546 Oct 14 02:37:22 tinka vdr: [1924] frontend 0 regained lock on channel 1, tp 546 Oct 14 02:37:23 tinka vdr: [1924] frontend 0 lost lock on channel 1, tp 546 Oct 14 02:37:23 tinka vdr: [1924] frontend 0 regained lock on channel 1, tp 546 After googling some vdr discussions I found that somebody had a patch for disabling the epc scan due to similar types of problems. Therefore I went to configuration option setup/EPG/EPG Scan timeout (h) and changed it's value from 5 to 0. After that my vdr has now worked 15 hours without any problem. What does this EPG scan timeout do and should it be disabled by default if the system has dvb-t channels configured? Or is somebody seeing this problem or having a patch for fixing it? If I am using vdr for watching the dvb-s channels, things will work without problems even if this epg scan timeout is set. With vdr-1.7.0 I have used the liplianis multiproto tree and vdr 1.6.0 I have used with new dvb-v4l, S2 (http://linuxtv.org/hg/~stoth/s2/) and s2-mfe trees. (drivers from s2 and s2-mfe repositories works for me with vdr-1.6.0 when not trying S2 as the driver api is backward compatible) In addition I have tested with kaffeine with same drivers and there the system worked hours without losing the lock to dvb-t channel. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64 ( 071020008 )
[EMAIL PROTECTED]:/usr/local/src/vdr-1.7.1# make g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DUSE_CMDRECCMDI18N -DUSE_CMDSUBMENU -DUSE_CUTTIME -DUSE_DDEPGENTRY -DUSE_DOLBYINREC -DUSE_JUMPPLAY -DUSE_LIEMIKUUTIO -DUSE_PLUGINMISSING -DUSE_SETTIME -DUSE_WAREAGLEICON -DREMOTE_KBD -DVDR_USER=\vdr\ -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -DVIDEODIR=\/daten/Video/vdr/video.00\ -DCONFDIR=\/daten/Video/vdr/video.00\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -DUSE_PLUGINAPI -I/usr/include/freetype2 -I../s2-mfe/linux/include channels.c channels.c:70: error: 'NBC_QPSK' was not declared in this scope channels.c:71: error: '_8PSK' was not declared in this scope channels.c:72: error: '_16APSK' was not declared in this scope channels.c: In member function 'void cChannel::SetLinkChannels(cLinkChannels*)': channels.c:690: warning: format not a string literal and no format arguments make: *** [channels.o] Fehler 1 Any ideas? There has been renamings in the driver about 7 days ago which break the vdr patch. For example _8PSK -- PSK_8 See following patch for details: http://linuxtv.org/hg/~stoth/s2-mfe/rev/d1c25e26799f Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] CCID smart card interface support for sc?
If I enable my subscription with my provider again, that uses irdeto2, will it work? I can not say for sure whether irdeto2 works with sc and smartcard, there however seems to be also a irdeto library in sc. The smart card that I have subscribed uses conax. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [linux-dvb] [PATCH] S2API for vdr-1.7.0 (04-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)
On Sun, 5 Oct 2008, Mika Laitio wrote: Hello All, Today I finished the patch for DVB-S, DVB-S2, DVB-T and DVB-C support using S2API in combination with VDR 1.7.0. I've tested my code on DVB-S, DVB-S2 and DVB-T transports and they were all successful. DVB-C is untested (don't have a DVB-C option where I live) but it should work in *THEORY* ;) DVB-S and DVB-S2 were tested on a Hauppauge WinTV-NOVA-HD-S2 card. DVB-T was tested on a Gigabyte GT-U7000-RH USB device. I used the latest v4l pull and viewing was very stable with both DVB devices. I also didn't had any problems any more when switching between DVB-S(2) and DVB-T, but it can be that this patch will *NOT* work correctly on MFE DVB devices like the HVR-3000 or HVR-4000 (I had to do some hacking because strangely, DVB-T transports were offered to my DVB-S DVB device). Since I can't test this, I hope others can tell me if it works or not. Enclosed are two patches. The clean patch is for a clean VDR 1.7.0 source tree patched with Reinhard's vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 patch. The patched patch is for those who have used Edgar (gimli) Hucek's patch for VDR 1.7.0. In theory it should also work with my last send patch. Hi I tried your patch and vdr fails to show dvb-t channels for me while dvb-s channels works ok. I have tested with a following setup: - vdr-1.7.0 + vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff + vdr-1.7.0-s2api-04102008-clean.patch - latest s2-mfe installed for 2.6.27-rc8 - card-0: hvr-1300 (dvb-t, terrestrial cable connected) - card-1: hvr-4000 (dvb-t, dvb-s, dvb-s2, only satellite cable connected) [EMAIL PROTECTED] ~]$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 120 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 4 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 5 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 3 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 7 2008-10-05 10:56 net0 [EMAIL PROTECTED] ~]$ ls -la /dev/dvb/adapter1/ total 0 drwxr-xr-x 2 root root 200 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 68 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 84 2008-10-05 10:56 demux1 crw-rw+ 1 lamikr video 212, 69 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 85 2008-10-05 10:56 dvr1 crw-rw+ 1 lamikr video 212, 67 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 83 2008-10-05 10:56 frontend1 crw-rw+ 1 lamikr video 212, 71 2008-10-05 10:56 net0 crw-rw+ 1 lamikr video 212, 87 2008-10-05 10:56 net1 I also tried to connect the terrestrial cable to hvr-4000, but it did not change anything. If I use tzap, dvbstream and mplayer compination for hvr-1300 or if I use vdr-1.7.0 with liplianis multiptoto drivers, then also dvb-t channels works ok. Mika ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb And here is the output from syslog after trying to switch channel: Oct 5 12:43:20 tinka vdr: [21353] switching to channel 1 Oct 5 12:43:21 tinka vdr: [21446] transfer thread ended (pid=21353, tid=21446) Oct 5 12:43:21 tinka vdr: [21353] buffer stats: 0 (0%) used Oct 5 12:43:21 tinka vdr: [21486] transfer thread started (pid=21353, tid=21486) Oct 5 12:43:21 tinka vdr: [21448] TS buffer on device 1 thread ended (pid=21353, tid=21448) Oct 5 12:43:21 tinka vdr: [21447] buffer stats: 0 (0%) used Oct 5 12:43:21 tinka vdr: [21447] receiver on device 1 thread ended (pid=21353, tid=21447) Oct 5 12:43:21 tinka vdr: [21487] receiver on device 1 thread started (pid=21353, tid=21487) Oct 5 12:43:21 tinka vdr: [21488] TS buffer on device 1 thread started (pid=21353, tid=21488) Oct 5 12:43:22 tinka vdr: [21357] frontend 0 timed out while tuning to channel 1, tp 706 Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() FE_SET_PROPERTY Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() properties.num = 1 Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() properties.props = 42682d00 Oct 5 12:43:22 tinka kernel: dtv_property_process_set() Oct 5 12:43:22 tinka kernel: dtv_property_dump() tvp.cmd= 0x0002 (DTV_CLEAR) Oct 5 12:43:22 tinka kernel: dtv_property_dump() tvp.u.data = 0x Oct 5 12:43:22 tinka kernel: dtv_property_process_set() Flushing property cache Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() FE_SET_PROPERTY Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() properties.num = 6 Oct 5 12:43:22 tinka kernel: dvb_frontend_ioctl_properties() properties.props = 42682d00 Oct 5 12:43:22 tinka kernel: dtv_property_process_set() Oct 5 12:43:22 tinka kernel: dtv_property_dump
Re: [vdr] [PATCH] S2API for vdr-1.7.0 (05-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)
Enclosed are two patches. The clean patch is for a clean VDR 1.7.0 source tree patched with Reinhard's vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 patch. The patched patch is for those who have used the patch from 04-10-2008. I'm about to begin setting up my new VDR with DVB-S2 support, so I was wondering - where is the ultimate S2API driver source? http://linuxtv.org/hg/v4l-dvb/ http://linuxtv.org/hg/~stoth/s2/ http://linuxtv.org/hg/~stoth/s2-mfe/ - s2api with multifrontend support Steve can you comment the differences between s2 and s2-mfe trees and whether those are planned to be compined in near future? To my understanding the only difference between s2 and s2-mfe branches is the support for hvr-4000 style of devices. So: - s2: -- would support only 1 frontend for 1 card at a time. Therefore one would need to select during the driver loading time whether to want to use hvr-4000 in DVB-S/S2 mode or in DVB-T mode. So in dev-tree following are available: [EMAIL PROTECTED] vdr-1.7.0]# ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 120 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 4 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 5 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 3 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 7 2008-10-05 10:56 net0 - s2-mfe: -- can create multiple fronends for single card eventhoughg only one of those can in reality to be used simultaneously. Thus one does not need to select between DVB-S/S2 mode and DVB-T mode during the driver load time. So following nodes are available: [EMAIL PROTECTED] vdr-1.7.0]# ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 200 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 68 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 84 2008-10-05 10:56 demux1 crw-rw+ 1 lamikr video 212, 69 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 85 2008-10-05 10:56 dvr1 crw-rw+ 1 lamikr video 212, 67 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 83 2008-10-05 10:56 frontend1 crw-rw+ 1 lamikr video 212, 71 2008-10-05 10:56 net0 crw-rw+ 1 lamikr video 212, 87 2008-10-05 10:56 net1 Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [linux-dvb] [PATCH] S2API for vdr-1.7.0 (04-10-2008 - quickhack for DVB-S(2), DVB-T and DVB-C)
Hello All, Today I finished the patch for DVB-S, DVB-S2, DVB-T and DVB-C support using S2API in combination with VDR 1.7.0. I've tested my code on DVB-S, DVB-S2 and DVB-T transports and they were all successful. DVB-C is untested (don't have a DVB-C option where I live) but it should work in *THEORY* ;) DVB-S and DVB-S2 were tested on a Hauppauge WinTV-NOVA-HD-S2 card. DVB-T was tested on a Gigabyte GT-U7000-RH USB device. I used the latest v4l pull and viewing was very stable with both DVB devices. I also didn't had any problems any more when switching between DVB-S(2) and DVB-T, but it can be that this patch will *NOT* work correctly on MFE DVB devices like the HVR-3000 or HVR-4000 (I had to do some hacking because strangely, DVB-T transports were offered to my DVB-S DVB device). Since I can't test this, I hope others can tell me if it works or not. Enclosed are two patches. The clean patch is for a clean VDR 1.7.0 source tree patched with Reinhard's vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff.bz2 patch. The patched patch is for those who have used Edgar (gimli) Hucek's patch for VDR 1.7.0. In theory it should also work with my last send patch. Hi I tried your patch and vdr fails to show dvb-t channels for me while dvb-s channels works ok. I have tested with a following setup: - vdr-1.7.0 + vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff + vdr-1.7.0-s2api-04102008-clean.patch - latest s2-mfe installed for 2.6.27-rc8 - card-0: hvr-1300 (dvb-t, terrestrial cable connected) - card-1: hvr-4000 (dvb-t, dvb-s, dvb-s2, only satellite cable connected) [EMAIL PROTECTED] ~]$ ls -la /dev/dvb/adapter0/ total 0 drwxr-xr-x 2 root root 120 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 4 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 5 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 3 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 7 2008-10-05 10:56 net0 [EMAIL PROTECTED] ~]$ ls -la /dev/dvb/adapter1/ total 0 drwxr-xr-x 2 root root 200 2008-10-05 10:56 ./ drwxr-xr-x 4 root root 80 2008-10-05 10:56 ../ crw-rw+ 1 lamikr video 212, 68 2008-10-05 10:56 demux0 crw-rw+ 1 lamikr video 212, 84 2008-10-05 10:56 demux1 crw-rw+ 1 lamikr video 212, 69 2008-10-05 10:56 dvr0 crw-rw+ 1 lamikr video 212, 85 2008-10-05 10:56 dvr1 crw-rw+ 1 lamikr video 212, 67 2008-10-05 10:56 frontend0 crw-rw+ 1 lamikr video 212, 83 2008-10-05 10:56 frontend1 crw-rw+ 1 lamikr video 212, 71 2008-10-05 10:56 net0 crw-rw+ 1 lamikr video 212, 87 2008-10-05 10:56 net1 I also tried to connect the terrestrial cable to hvr-4000, but it did not change anything. If I use tzap, dvbstream and mplayer compination for hvr-1300 or if I use vdr-1.7.0 with liplianis multiptoto drivers, then also dvb-t channels works ok. Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64
here are the vdr S2API patches for vdr 1.7.1 + extensions 64 patch and also for the vanilla vdr 1.7.1. What is the purpose of this extension 64 patch? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PATCH] S2API for vdr-1.7.1 vanilla and extensions patch 64
i forgott write that the ext64 patch sits on top off : vdr 1.7.1 + extensions 64 + the h264 patch. With h264 patch, do you mean that vdr-1.7.0-h264-syncearly-framespersec-audioindexer-fielddetection-speedup.diff has been ported somewhere for vdr-1.7.1? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] CCID smart card interface support for sc?
I though that it would mean that I could connect the card to VDR by using the sc plugin, but I was wrong as sc plugin seems to only support smart cards that has serial port or serial port over usb support, like phoenix card readers. So I think there would be 3 options 1) Install newcs daemon (as it can read also CCID cards. I want however avoid this as there is no sources available for it. 2) Create virtual serial port driver over CCID library 3) Modify smartcard.c from sc plugin to support also the CCID cards. Has anybody worked with items 2 or 3 earlier? Ok, attached is a patch for sc plugin to support CCID smart card readers. The patch is not originally from me but I modified it to work with sc code available in sc trunk. So far I have tested it with vdr-1.7.0 and liblianis multifrontend drivers with the pay channels that I have subscribed (and thus have the smart card key) I have not tested yet with s2 api version of vdr as I have still problems to watch even free channels with my card when using vdr-1.7.0 or 1.7.1 with s2 api patches in place. (and without having any plugins) Attachment contains the patch and in addition also the modified files in their final form. Code is simply using #ifdefs for places where CCID and serial interface differs instead of trying to abstract common c++ base class that both the serial and ccid implementations could inherit. Mika vdr_sc_plugin_ccid_smartcard_support.tar.bz2 Description: ccid smart card reader support for vdr sc plugin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Black Screen with vdr 1.7.1
Hi, in these days I tried new version of vdr 1.7.1 with the lastest version of S2API. I have an ss2 and a HVR-4000 card in my system. I compiled and I installed correctly the lasted driver version (s2-mfe first, then i tried s2 tree) but when I start vdr 1.7.1, it remains in black screen even if I can see the osd. I applied every patch posted in this ml. I also tried vdr 1.7.0 patched and this version work. Why vdr 1.7.1 remain black while vdr 1.7.0 works? With vdr-1.7.0 + S2, I have also been able to watch dvb-s channels (with hdr-4000) but not dvb-t (with hvr-1300). With vdr-1.7.1 both dvb-t and dvb-s channels fails also for me. This is a summary of my system: Debian Etch Core 2 Duo E6750 Skystar 2 HVR-4000 vdr with softdevice and femon I have AMD X2-4850E and using 64 bit version of Linux. How about you, are you using 32 or 64 bit version? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] how to prevent xineplayer to go in slow-motion mode
if I get short drop outs on a channel (NO Signal for example) the video goes on in normal speed, but after 3 or 4 further drop-outs the sound disappears and the video is in some kind of slow motion. I have to switch to another channel and back to get picture and sound normal. When I am using vdr-xineliboutput (latest version from svn) with vdr 1.7.0, I am also seeing the sound often disappear when I watch tv over wlan, while picture looks ok. Sometimes the vdr-sxfe is able to fix it itself after a some seconds of waiting, but usually the fastest way is to re-switch to same channel Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] CCID smart card interface support for sc?
I was planning to use my digi tv viewing card with VDR by installing the sc-plugin. My understanding this is legal as I would still need to use my real viewing card. The card reader I have seems to support the CCID interface, therefore I found the tools needed for communication from http://pcsclite.alioth.debian.org/ccid.html I installed the pcscd daemon that in my understanding uses libusb for communincating with the smart card. After that the pcsc_scan was able to printout correct info from my card. I though that it would mean that I could connect the card to VDR by using the sc plugin, but I was wrong as sc plugin seems to only support smart cards that has serial port or serial port over usb support, like phoenix card readers. So I think there would be 3 options 1) Install newcs daemon (as it can read also CCID cards. I want however avoid this as there is no sources available for it. 2) Create virtual serial port driver over CCID library 3) Modify smartcard.c from sc plugin to support also the CCID cards. Has anybody worked with items 2 or 3 earlier? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [v4l-dvb-maintainer] [Wanted] dvb-ttpci maintainer
The basic democratic rules should integrate the community and not only two multiproto developers. Any way, my compromise for this problem is: Manu Abraham and Steven Toth should work on one of the API's (together) and then decide which is the better solution for the new upcoming standards! I agree with those who think that kernel/linuxtv should not try to maintain both the multiproto and S2API in the long run, that would just make a chaos. So only one API (preferrable backward compatible) would be the best option. I also like that now there is a big push for getting many drivers back to single v4l-dvb tree instead of tens of different development trees that makes it impossible for distros to compine a working solution for most of the cards. As a follower of this email list, I however also have small concern whether the vote between multiproto and s2api was really fair. There were not any discussion from the API calls and structures used in different proposals. It did not also help that Mauro who as a final decision maker with commit rights to v4l-dvb publicly announced over one month earlier working for S2API instead of multiproto. http://www.linuxtv.org/pipermail/linux-dvb/2008-August/028313.html But some decision must be made so that the train can get forward and my understanding is that both the S2API and multiproto API can be used for that. So in that sense I am happy that the work for getting drivers back from tens of different development trees back to v4l-trunk has started. The real win-win solution at least for the co-operation point of view would be if S2API and Multiproto could somehow be compined for making one superiour DTV API. But as there has not been any emails discussing the details of these two API's I do not know whether it makes sense from technology point of view. (As the technically best API should always win in Linux...) I hope people could still have some energy for commenting this? Mika ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
