Re: [vdr] Advice from native speakers needed: To bisect or to halve?
Hi Klaus, On 02/05/15 16:56, Klaus Schmidinger wrote: The question now is: is bisect the right word here, which a native English speaker would use? Or should it rather be halve? Or something completely different? IMHO all these fancy words are a bit overblown. I am not a native English speaker but I consistently use the English version of software where available. So I suggest to keep it simple and use words that even I can understand. ;-) Instead of to bisect or to halve I would use to cut in half. Of course, it it *has to be* a single word, then http://www.answers.com/Q/What_is_the_opposite_of_doubling_a_number suggests halving. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [PLUGIN] recsearch - a simple search for recordings
On 01/19/14 13:53, Stephan Loescher wrote:
Would it be possible (as a new feature) to filter/search/sort for
recordings by recording-lifetime and/or if it is SD or HD?
I had the same problem (long time ago).
As a simple solution, I wrote a small python script
that creates folders with virtual recordings
(symbolic links to the real recordings).
The tool creates /video/Surround, /video/HD
and /video/Surround+HD. Inside each of them
there is the same subfolder structure as under
/video, except that they contain only the corresponding
subset.
Here is the source:
import os
import shutil
import sys
video_dir = /video
def linkto(root, name):
components = []
for root_component in root.split('/')[2:]:
components.append(root_component)
if root_component.startswith('%'):
break
source = os.path.join(video_dir, '/'.join(components))
target = os.path.join(video_dir, name, '/'.join(components))
target_parent = os.path.join(video_dir, name, '/'.join(components[:-1]))
if not os.path.exists(target_parent):
os.makedirs(target_parent)
os.symlink(source, target)
for subdir in (Surround, HD, Surround+HD):
path = os.path.join(video_dir, subdir)
if os.path.exists(path):
shutil.rmtree(path)
os.mkdir(path)
surround_dirs = []
hd_dirs = []
surround_hd_dirs = []
for root, dummy_dirs, files in os.walk(video_dir, followlinks=True):
if '%' in root and (info in files or info.vdr in files):
surround = False
hd = False
for line in open(os.path.join(root, info if info in files else
info.vdr)):
if line.startswith(X ):
if 5.1 in line:
surround = True
elif high definition Video in line:
hd = True
if surround:
surround_dirs.append(root)
if hd:
hd_dirs.append(root)
if surround and hd:
surround_hd_dirs.append(root)
for root in surround_dirs:
linkto(root, Surround)
for root in hd_dirs:
linkto(root, HD)
for root in surround_hd_dirs:
linkto(root, Surround+HD)
Cheers, Carsten.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Makefile variable names LCLBLD and PLGCFG
On 03/17/13 13:00, Klaus Schmidinger wrote: On 17.03.2013 12:46, Ville Skyttä wrote: Hello, Should probably have spoken earlier, but is there any particular reason for the ugly and hard to read Makefile variable names LCLBLD and PLGCFG? I suppose they're short for LOCALBUILD and PLUGINCONFIG, but why do they have to be short for anything, it's not like we're running out of space for their names anywhere, is it? Besides, I don't think LCLBLD describes what its effects are very well, INPLACE would sounds better to me. The ship may already have sailed for plgcfg in vdr.pc as it's being used by many plugin Makefiles already, but I believe the attached patches should be safe for 2.0.0. I'm afraid it's too late for that. I do not understand why it should be too late. 2.0 is not out yet. But if they really cannot have readable names, at least I would not provide a default, but let the makefile issue a message that they must be set (as I suggested in the other thread). Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.9.4 plugin
Hi,
On 03/16/11 20:29, Reinhard Nissl wrote:
I'm pleased to announce maintenance release 0.9.4.
is there something newer available?
In partcular, something that works with VDR 1.7.40?
With VDR 1.7.40 (under OpenSUSE 12.3) I get:
*** Plugin xine:
WARNING: plugin xine is using an old Makefile!
g++ -g -O3 -Wall -Werror=overloaded-virtual -Wno-parentheses -fPIC
-D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
-D_LARGEFILE64_SOURCE -c -D_GNU_SOURCE -DPLUGIN_NAME_I18N='xine'
-DFIFO_DIR=\/tmp/vdr-xine\ -DVERIFY_BITMAP_DIRTY=0 `pkg-config
--cflags libxine` -I/home/cko/vdr-1.7.40/include xineDevice.c
xineDevice.c: In member function 'virtual void
PluginXine::cXineDevice::StillPicture(const uchar*, int)':
xineDevice.c:1203:36: error: 'class cPatPmtParser' has no member named
'PmtPid'
xineDevice.c:1403:1: warning: narrowing conversion of
'(vdr172::cRemux::IsFrameH264(Data, Length) ? 10 : 183)' from 'int' to
'uchar {aka unsigned char}' inside { } is ill-formed in C++11 [-Wnarrowing]
make[1]: *** [xineDevice.o] Error 1
You can
find it on my homepage as usual:
http://home.vr-web.de/~rnissl
Not any more.
http://home.vr-web.de in general and http://home.vr-web.de/~rnissl
seems to be gone.
Cheers,
Carsten.
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Virtual VDR directories for surround and HD recordings.
Hi,
I have been thinking for a while about virtual VDR directories
holding symbolic links to recordings that are stored elsewhere
using different sort criteria.
I have been a VDR user since 2000
http://www.tvdr.de/cgi-bin/vdr-counter.pl?action=shownumber=3
and I have recorded a lot since then (9245 recordings),
so some kind of structure is required to find things quickly.
For example, I have top level folders for various genres in my
/video directory. So far, I decide after recording and cutting
into which folder I move the recording.
It might be better to have them all on one big RAID and
create symbolic links in /video, so I can find an action comedy
both in /video/Action and in /video/Comedy.
Regarding the genre, I have managed without that feature.
However, many German TV stations are now broadcasting
in HD, sometimes with 5.1 surround sound.
It is really hard to find these high quality recordings directly
among my 9245 recordings.
So I have written a little Python tool that creates virtual
recordings in a different folder structure from my real
recordings using symbolic links.
This is done by creating top level folders /video/Surround,
/video/HD, /video/Surround+HD and linking matching
recordings into these keeping the original folder structure
intact.
Maybe somebody else finds this useful, so I am attaching
the code. It only considers recordings that are cut
(having a % in the name). Please note that the tool
removes any existing folders /video/Surround,
/video/HD, /video/Surround+HD before re-creating them.
Use at your own risk.
Carsten.
import os
import shutil
import sys
video_dir = /video
def linkto(root, name):
components = []
for root_component in root.split('/')[2:]:
components.append(root_component)
if root_component.startswith('%'):
break
source = os.path.join(video_dir, '/'.join(components))
target = os.path.join(video_dir, name, '/'.join(components))
target_parent = os.path.join(video_dir, name, '/'.join(components[:-1]))
if not os.path.exists(target_parent):
os.makedirs(target_parent)
os.symlink(source, target)
for subdir in (Surround, HD, Surround+HD):
path = os.path.join(video_dir, subdir)
if os.path.exists(path):
shutil.rmtree(path)
os.mkdir(path)
surround_dirs = []
hd_dirs = []
surround_hd_dirs = []
for root, dummy_dirs, files in os.walk(video_dir, followlinks=True):
if '%' in root and (info in files or info.vdr in files):
surround = False
hd = False
for line in open(os.path.join(root, info if info in files else info.vdr)):
if line.startswith(X ):
if 5.1 in line:
surround = True
elif high definition Video in line:
hd = True
if surround:
surround_dirs.append(root)
if hd:
hd_dirs.append(root)
if surround and hd:
surround_hd_dirs.append(root)
for root in surround_dirs:
linkto(root, Surround)
for root in hd_dirs:
linkto(root, HD)
for root in surround_hd_dirs:
linkto(root, Surround+HD)
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.28
On 07/09/12 22:30, Klaus Schmidinger wrote: On 09.07.2012 19:06, Carsten Koch wrote: but I noticed that the LCARS skin sometimes fails to show the recording name in the progress display (the one that shows up when you press OK during playback). I don't think this is related, because these are totally different code areas. Is this problem reproducible? Not really. I was hoping it might be related to the recording name (length or content), but when the problem occured again, I stopped and re-started the playback and then the name display was OK. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] VDR developer version 1.7.28
On 07/09/12 18:57, Joerg Bornkessel wrote: LCARS is the new default skin of VDR. It requires at least a 4bpp (16 color) full screen OSD, but you can still operate it if your OSD can handle only fewer colors (in which case you may want to switch to the ST:TNG or Classic VDR skin). * QA Notice: Package triggers severe warnings which indicate that it *may exhibit random runtime failures. * skinlcars.c:518:39: warning: passing NULL to non-pointer argument 2 of ‘cString ChannelString(const cChannel*, int)’ [-Wconversion-null] I do not know if that is related, but I noticed that the LCARS skin sometimes fails to show the recording name in the progress display (the one thet shows up when you press OK during playback). Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Why is VDR appending :S23.5E: entries to my channels.conf?
On 05/01/12 11:29, Klaus Schmidinger wrote: If you send me your channels.conf (without the S23.5E channels), diseqc.conf and setup.conf I could try to reproduce this here. I have upgraded to vdr-1.7.27, copied diseqc.conf and sources.conf from there into my config directory and removed the wirbelscan plugin. I also removed all non-:S19.2E: entries again from my channels.conf. So far, only one channel has been added and it is not an S23.5E entry: Multytext;BetaDigital:11420:HC56M2S0:S19.2E:22000:0:0:0:0:4792:1:1015:0 If the problem reoccurs, I'll send you the requested files. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Small python script to rearrange channels.conf.
Hi,
I wrote a small python script that helps me
keep my channels.conf tidy.
The scripts assumes that I have
(among others) channel groups
:HDTV, :Deutschsprachig,
:(auch)Englisch, :Verschiedenes,
:Astra Radio and :new channels
at the end.
It moves all radio channels from
all groups into :Astra Radio.
It moves channels that have
a HD in their name from :new channels
to :HDTV.
It moves channels that have
geman sound from :new channels
to :Deutschsprachig.
It moves channels that do not have
german sound, but english sound
from :new channels to :(auch)Englisch.
All other new channels are moved from
:new channels to :Verschiedenes.
It ignores all non-S19.2E channels
(see my other posting).
Finally, all channel groups are sorted
alphabetically.
The script/program is a filter, so
you can do things like
python sort_channels.py channels.confchannels.new
Cheers,
Carsten.
import sys
import string
channel_info = {}
sections = []
for line in sys.stdin:
stripped_line = line.strip()
if stripped_line.startswith(':'):
sections.append(stripped_line)
channel_info[sections[-1]] = []
else:
channel_info[sections[-1]].append(stripped_line)
radio_channels = []
for section in sections:
tv_channels = []
for line in channel_info[section]:
fields = line.split(':')
if fields[3] == S19.2E:
if fields[5] == '0': # VPID = 0 = radio channel
radio_channels.append(line)
else:
tv_channels.append(line)
channel_info[section] = tv_channels
channel_info[:Verschiedenes] += channel_info[:Astra Radio]
channel_info[:Astra Radio] = radio_channels
for line in channel_info[:new channels]:
fields = line.split(':')
if HD in fields[0]:
channel_info[:HDTV].append(line)
elif =deu in fields[6]:
channel_info[:Deutschsprachig].append(line)
elif =eng in fields[6]:
channel_info[:(auch)Englisch].append(line)
else:
channel_info[:Verschiedenes].append(line)
channel_info[:new channels] = []
for section in sections:
print section
for line in sorted(channel_info[section], key=string.lower):
print line
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] probs with new ZDF HDchannels
On 05/01/12 23:16, Carsten Koch wrote: However, with that xine-lib, xine-ui now shows some of the buttons (vcd, dvb) twice, leaving no more room for the vdr button. I have found no solution for that yet. I have now. I noticed that the new version creates a new plugin directory /usr/lib64/xine/plugins/2.1. The previous one was using /usr/lib64/xine/plugins/2.0. It seems that xine-ui was loading from both, so I removed the old one. Now all is OK. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Why is VDR appending :S23.5E: entries to my channels.conf?
Hi, my dish is directed at Astra 19.2E. However, many of the new entries VDR automatically appends to the end of my channels.conf are :S23.5E:!? I have recently removed all :S23.5E: lines, but they came back immediately: cko/vdrconfig fgrep :S23.5E: channels.conf | wc 152 352 16541 cko/vdrconfig fgrep :S19.2E: channels.conf | wc 12662774 122268 Does anyone know why I am getting :S23.5E: entries in a :S19.2E:-only setup? Is this a bug or am I missing somerhing? I am using vdr-1.7.26. Thanks in advance for any hint, Carsten. cko/vdrconfig fgrep :S23.5E: channels.conf Sky Nostalgie,Nostalgie;SKY:11719:hC910I0M2O35S1:S23.5E:27500:1535=2:1536=deu@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:516:133:3:0 Sky Hits,SkyHits;SKY:11719:hC910I0M2O35S1:S23.5E:27500:1023=2:1024=deu@3,1025=eng@3;1027=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:41:133:3:0 Disney Cinemagic,DisneyCin;SKY:11719:hC910I0M2O35S1:S23.5E:27500:1279=2:1280=deu@3,1281=eng@3;1283=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:25:133:3:0 MGM;SKY:11719:hC910I0M2O35S1:S23.5E:27500:511=2:512=deu@3,513=eng@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:515:133:3:0 Sky Sport News,SportNews;SKY:11719:hC910I0M2O35S1:S23.5E:27500:255=2:256=deu@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:17:133:3:0 ???:11719:hC910I0M2O35S1:S23.5E:27500:255=2:256=deu@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:241:133:3:0 Sky Cinema,Cinema;SKY:11797:hC34I0M2O35S1:S23.5E:27500:511=2:512=deu@3,513=eng@3;515=deu@106:32:1702,1722,1833,1834,1836,9C4,9C7,9AF,1861:10:133:2:0 Sky Cinema +1,Cinema1;SKY:11797:hC34I0M2O35S1:S23.5E:27500:1791=2:1792=deu@3,1793=eng@3;1795=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,98C,1861:11:133:2:0 Sky Cinema +24,Cinema24;SKY:11797:hC34I0M2O35S1:S23.5E:27500:2303=2:2304=deu@3;2307=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:43:133:2:0 Sky Action,Action;SKY:11797:hC34I0M2O35S1:S23.5E:27500:767=2:768=deu@3,769=eng@3;771=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:9:133:2:0 Sky Comedy,Comedy;SKY:11797:hC34I0M2O35S1:S23.5E:27500:2559=2:2560=deu@3,2561=eng@3;2563=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:8:133:2:0 Sky Emotion,Emotion;SKY:11797:hC34I0M2O35S1:S23.5E:27500:2815=2:2816=deu@3,2817=eng@3;2819=deu@106:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:20:133:2:0 445 - 20|30:11797:hC34I0M2O35S1:S23.5E:27500:3071=2:3072=deu@3,3073=eng@3;3075=deu@106:0:1702,1722,1833,1834,9C4,9C7,9AF,1861:251:133:2:0 376 - 16|00:11797:hC34I0M2O35S1:S23.5E:27500:3583=2:3584=deu@3;3587=deu@106:0:1702,1722,1833,1834,9C4,9C7,9AF,1861:264:133:2:0 Das Erste;ARD:11836:hC56I0M2S0:S23.5E:27500:101=2:102=deu@3,103=mis@3;106=deu@106:104;105=deu:0:28106:1:1101:0 Bayerisches FS Süd;ARD:11836:hC56I0M2S0:S23.5E:27500:201=2:202=deu@3,203=mis@3;206=deu@106:204:0:28107:1:1101:0 hr-fernsehen;ARD:11836:hC56I0M2S0:S23.5E:27500:301=2:302=deu@3,303=mis@3:304:0:28108:1:1101:0 Bayerisches FS Nord;ARD:11836:hC56I0M2S0:S23.5E:27500:201=2:202=deu@3,203=mis@3;206=deu@106:204:0:28110:1:1101:0 WDR Köln;ARD:11836:hC56I0M2S0:S23.5E:27500:601=2:602=deu@3,603=mis@3:604:0:28111:1:1101:0 SWR Fernsehen BW;ARD:11836:hC56I0M2S0:S23.5E:27500:801=2:802=deu@3,803=mis@3;806=deu@106:804:0:28113:1:1101:0 .;SKY:11875:hC56I0M2S0:S23.5E:27500:0:0:0:0:123:133:14:0 Fox HD;SKY:11875:hC56I0M2S0:S23.5E:27500:511=27:0;515=deu@106,516=eng@106:32:1833,9C4:124:133:14:0 Sky Select HD,SelectHD;SKY:11875:hC56I0M2S0:S23.5E:27500:767=27:0;771=deu@106,772=eng@106:32:1833,9C4:120:133:14:0 BLUE MOVIE HD,BMHD;SKY:11875:hC56I0M2S0:S23.5E:27500:1023=27:0;1027=deu@106:32:1833,9C4:121:133:14:0 .;SKY:11875:hC56I0M2S0:S23.5E:27500:0:0:0:0:122:133:14:0 Sky Cinema HD,CinemaHD;SKY:11914:hC34I0M2S0:S23.5E:27500:1279=27:0;1283=deu@106,1284=eng@106:32:1833,1834,9C4,9C7,9AF,1861:131:133:6:0 Discovery HD,DiscHD;SKY:11914:hC34I0M2S0:S23.5E:27500:1023=27:0;1027=deu@106:32:1833,1834,9C4,9C7,9AF,1861:130:133:6:0 Eurosport HD,EurospHD;SKY:11914:hC34I0M2S0:S23.5E:27500:1535=27:0;1539=deu@106:32:1833,1834,9C4,9C7,9AF,1861:132:133:6:0 Sky Sport HD 1,SportHD 1;SKY:11914:hC34I0M2S0:S23.5E:27500:767=27:0;770=deu@106,771=deu@106,772=eng@106:32:1833,1834,9C4,9C7,9AF,1861:129:133:6:0 Sky Sport HD 2,SportHD 2;SKY:11992:hC34I0M2S0:S23.5E:27500:1023=27:0;1027=deu@106:32:1833,1834,9C4,9C7,9AF,1861:114:133:13:0 Disney Cinemagic HD,DisneyCinHD;SKY:11992:hC34I0M2S0:S23.5E:27500:255=27:0;259=deu@106,260=eng@106:32:1833,1834,9C4,9C7,9AF,1861:111:133:13:0 NatGeo HD,NatGeoHD;SKY:11992:hC34I0M2S0:S23.5E:27500:511=27:0;515=deu@106,516=eng@106:32:1833,1834,9C4,9C7,9AF,1861:112:133:13:0 History HD,HistHD;SKY:11992:hC34I0M2S0:S23.5E:27500:767=27:0;771=deu@106,772=eng@106:32:1833,1834,9C4,9C7,9AF,1861:113:133:13:0 Sky Sport 1,Sport1;SKY:12031:hC910I0M2O35S1:S23.5E:27500:2047=2:2048=deu@3,2049=deu@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:221:133:4:0 Sky Sport 2,Sport2;SKY:12031:hC910I0M2O35S1:S23.5E:27500:2303=2:2304=deu@3,2305=deu@3:32:1702,1722,1833,1834,9C4,9C7,9AF,1861:222:133:4:0 Sky Bundesliga,Sky
Re: [vdr] Can VDR record only new episodes of shows?
On Fri, 2011-06-03 at 08:28 -0400, John Klimek wrote: ... For example, I don't want to record every single episode of a certain show, but instead I just want the new episodes. That's one of the things VDRAdmin-AM can do for you. Where new is defined as one that you have not recorded yet. Carsten, ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Compressing VDR recordings without losing quality.
Hi, I have been using VDR for over 10 years now, so I currently have ~4TB of VDR recordings. Some of them are SDTV/MPEG2, many of the newer recordings are HDTV/H.264. I wonder if there is an easy way to recompress all recordings that are not already H.264 into H.264 files, making them a lot smaller without losing any quality. Since my HTPC is using the graphics card anyway, I do not rely on the vdr GUI. As long as the result can be played with xine and mplayer, it would be fine. Would it be easy to write a small script that goes through all recordings, finds out whether the recording is MPEG2, determines the H.264 bitrate that produces approximately the same quality and calls mencoder to convert it? Has somebody already done that? Any pointers welcome! Thanks, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] 10 Year Anniversary of VDR
I have been using (and making some humble contributions to) VDR since June 7th, 2000. So it is going to be another 4 months until I can celebrate my 10 Year Anniversary of VDR. It has always been a pleasure. Thanks, Klaus! Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Setting up an nfsroot VDR system with an atom ION main board (was: Recommendation for new hd vdr system).
On Thu, 2009-12-24 at 17:12 +0100, Carsten Koch wrote: ... + 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. Just in case anyone wants to try to set up an nfsroot VDR system with that main bord, here is what I had to do to make it work: In general, it is much easier now to set up an nfsroot system, than it was a few years ago. I attached a hard disk to the PC and installed OpenSUSE 11.2 on it normally. All to one partition, no swap. I re-built the kernel: cd /usr/src/linux gunzip /proc/config.gz.config make oldconfig make all I copied the whole disk partition over to the server, then mounted it from there as /atom. I created a new initrd for nfsroot: mkinitrd -f nfs -D eth0 /atom See the mkinitrd man page. I copied that initrd and the kernel to the server, activated a dhcp server and a tftp server with pxelinux. My /tftpboot/pxelinux.cfg/01-00-e0-4c-00-17-3f file contains: DEFAULT vmlinuz-2.6.31.5-0.1-desktop initrd=initrd-2.6.31.5-0.1-desktop root=192.168.25.6:/nfsroot/atom ip=192.168.25.30:192.168.25.6:192.168.25.4:255.255.255.0:atom:eth0:none TIMEOUT 1 I changed /nfsroot/atom/etc/ftsab so root is mounted via nfs: 192.168.25.6:/nfsroot/atom / nfs exec,rw 0 0 in /nfsroot/atom/etc/sysconfig/network/ifcfg-eth0 I set STARTMODE='nfsroot' (I read that somewhere. No idea if it is really required) After that, the system started to boot via the network. I have another system that works fine this way, but the atom system failed to mount the nfs root during boot. There seems to be a timing problem with the network driver. I worked around that by patching boot/83-mount.sh in the initrd. I put a sleep 2 before the mount command. (I tried sleep 1, but that was not enough. YMMV). Note that the initrd is a gzipped cpio archive in NEWC format. I unpacked the old archive using gunzip initrd-2.6.31.5-0.1-desktopinitrd.cpio mkdir initrd cd initrd cpio -i ../initrd.cpio I re-packed the modified archive using cpio -t ../initrd.cpio /tmp/list cpio -H NEWC -o /tmp/list ../new.cpio gzip -9 ../new.cpio Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
On Fri, 2009-12-25 at 13:02 +, Tony Houghton wrote: On Thu, 24 Dec 2009 17:12:56 +0100 Carsten Koch carstenkochelsd...@web.de wrote: + 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. Another idea: if there's a spare USB (2.0 High Speed) port you could use a memory stick instead of NFS. Good idea. I suppose this one http://geizhals.at/deutschland/a439283.html should be sufficient. I wonder if that's going to be faster (no seek times) or slower than my hard disk. The only remaining advantage of an nfsroot system being that I can turn the power off without needing to shut the system down. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
On Sat, 2009-11-14 at 21:23 +0100, Carsten Koch wrote: ... I was thinking along the same lines and I have just bought an ION board. The main board comes with a CPU and with GeForce 9400 graphics, so that will be cheaper than the sum of a normal board + CPU + GeForce 9400 graphics. 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. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FF/RW problems with xine
On Fri, 2009-10-09 at 21:07 +0200, Carsten Koch wrote: On Fri, 2009-10-09 at 11:37 -0700, Timothy D. Lenz wrote: With some recordings FF/RW doesn't work correctly. The video/audio stops and when you hit play again, it has moved to the new a new location. Some recordings work, some don't. I saw that, too. It has to do with the channel. I record WAS IST WAS TV for my kids from Nickelodeon. On these recordings, FF/FR never works, which makes it kind of hard to cut these recordings. I checked again with 1.7.10. (tried cutting a WAS IST WAS TV recording today) The bug is still there. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Recommendation for new hd vdr system.
On Sat, 2009-11-14 at 13:17 +0100, Luca Olivetti wrote: Hello, Now that I have an hd tv set, I'm looking at revamping my ageing vdr system for hd. Oh, and I want it to be really cheap ;-) I was thinking along the same lines and I have just bought an ION board. The main board comes with a CPU and with GeForce 9400 graphics, so that will be cheaper than the sum of a normal board + CPU + GeForce 9400 graphics. Here in Germany, there are only two Atom boards with 1 PCI slot and GeForce 9400 graphics: http://geizhals.at/deutschland/?cat=mb1ppga_ddrxf=597_GeForce+9400~489_1 All you need in addition to that is some memory, the DVB-S2 card and a case. Cases start at 30 Euros: http://geizhals.at/deutschland/?cat=gehitxv=esort=pxf=534_Mini-ITX~549_220 Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR can no longer be compiled with the current driver from http://linuxtv.org/hg/v4l-dvb.
On Sun, 2009-06-14 at 13:49 +0200, Klaus Schmidinger wrote: ... If you use a full featured DVB card for replay you need the DVB driver version from http://linuxtv.org/hg/v4l-dvb The driver had its API version changed on 2009-10-19 17:08:05: --- v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/version.h 2009-06-21 02:25:44.0 +0200 +++ v4l-dvb-f6680fa8e7ec/linux/include/linux/dvb/version.h 2009-10-19 17:08:05.0 +0200 @@ -24,6 +24,6 @@ #define _DVBVERSION_H_ #define DVB_API_VERSION 5 -#define DVB_API_VERSION_MINOR 0 +#define DVB_API_VERSION_MINOR 1 #endif /*_DVBVERSION_H_*/ @Klaus, are you planning to adapt VDR and release a new version this weekend? Cheers, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FF/RW problems with xine
On Fri, 2009-10-09 at 11:37 -0700, Timothy D. Lenz wrote: With some recordings FF/RW doesn't work correctly. The video/audio stops and when you hit play again, it has moved to the new a new location. Some recordings work, some don't. I saw that, too. It has to do with the channel. I record WAS IST WAS TV for my kids from Nickelodeon. On these recordings, FF/FR never works, which makes it kind of hard to cut these recordings. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] xxv-1.4 - Stable release
On Sat, 2009-07-11 at 17:13 +0200, Andreas Brachold wrote: ... XXV means Xtreme eXtension for VDR and is a central service for the administration of the VDR and his environment. Looks very much like vdradmind. Can anyone summarize the differences between xxv and vdradmind? Thanks, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] error compiling vdr 1.7.7 (frontend.h - '__u8' does not name a type)
On Mon, 2009-06-01 at 13:38 +0200, Klaus Schmidinger wrote: ... posted earlier in this thread I found that this --- dvbdevice.h 2009/05/08 13:33:46 2.5 +++ dvbdevice.h 2009/06/01 11:20:32 @@ -10,6 +10,7 @@ #ifndef __DVBDEVICE_H #define __DVBDEVICE_H +#include sys/mman.h // FIXME: workaround for broken linux-dvb header files #include linux/dvb/frontend.h #include linux/dvb/version.h #include device.h alone fixes the problem (tested with the latest driver from http://linuxtv.org/hg/v4l-dvb). No, it does not. At least not here (SuSE 11.1, 64-bit, vdr 1.7.8, v4l-dvb-af3d28c7ef19). I am getting g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/home/cko/vdrconfig\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 -I/usr/src/v4l-dvb-af3d28c7ef19/linux/include vdr.c In file included from dvbdevice.h:14, from vdr.c:45: /usr/src/v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/frontend.h:92: error: '__u8' does not name a type /usr/src/v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/frontend.h:93: error: '__u8' does not name a type /usr/src/v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/frontend.h:98: error: '__u8' does not name a type /usr/src/v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/frontend.h:99: error: '__u8' does not name a type /usr/src/v4l-dvb-af3d28c7ef19/linux/include/linux/dvb/frontend.h:361: error: '__u8' does not name a type make: *** [vdr.o] Error 1 cko/vdr-1.7.8 I worked around it by inserting a typedef unsigned char __u8; after the #include sys/mman.h // FIXME: workaround for broken linux-dvb header files in dvbdevice.h. With that, vdr compiles without errors. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] ExtRecMenu-Plugin 1.1
On Thu, 2009-05-28 at 14:37 +0300, Petri Helin wrote: On Wed, May 27, 2009 at 5:54 PM, Carsten Koch carstenkochelsd...@web.de wrote: I like the ExtRecMenu plugin very much. In particular, I love the fact that it shows me the length of my recordings and that it allows me to display recordings in alphabetical (and chronological) order. ... There is also a test version of version 1.2: http://www.vdrportal.de/board/thread.php?threadid=75295threadview=0hilight=hilightuser=0page=1 You could try it out. I did. It did not compile either. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr-xine-0.9.2 plugin does not support cutting.
Reinhard, you have done an amazing job with the xine plugin. It works very well and considering xine's complexity, I can appreciate the hard work that must have been required to get both the infrastructure in xine and the plugin itself working as well as it does today. I noticed, however, that it is extremely hard to use VDRs cutting function with it. For example, when I use the '7' and '9' keys to jump to the previous/next cut mark, or when I use the '4' and '6' keys to fine-position a cut mark, the video image is not updated, so I am basically forced to navigate in complete darkness. Is that a known bug? Does it happen only in my setup (TT-budget S2-3200, GeForce 9500GT with VDPAU)? Is there a configuration option I can tweak to fix it? Thanks in advance for any hints, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] ExtRecMenu-Plugin 1.1
On Mon, 2007-10-22 at 19:32 +0200, Martin Prochnow wrote: ... Screenshots and Download: http://martins-kabuff.de/extrecmenu_en.html I like the ExtRecMenu plugin very much. In particular, I love the fact that it shows me the length of my recordings and that it allows me to display recordings in alphabetical (and chronological) order. There have been no new releases for almost 2 years now. Has anyone tried to make the old version work with vdr 1.7.7? Klaus, are there any plans to put these two nice features into the main recordings menu? At least the channels menu does provide an alphabetically ordered display, so why not the recordings menu? Cheers, Carsten, ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.7.7 compile problem with gcc 4.4
On Wed, 2009-05-27 at 16:40 +0200, gimli wrote: ... have compile errors with gcc 4.4. The attached patch makes vdr 1.7.7 compileable. I wonder if it would not be better to make as many things as possible const rather than casting existing consts away. I my code, I am trying to make everything const that I do not have to change. It allows the compiler to make additional optimizations and it is safer (protects against unintended modifications). Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
Hi, I would like to get a HDTV VDR system started. I have the following hardware to play with: gigabyte m55plus s3g main board (nVidia GeForce 6100 / nForce 430) with Athlon 64 3500+, 1GB RAM GeForce 9500GT card with 1GB RAM 2 TT-budget S2-3200 DVB S2 cards I have installed OpenSuse 11.1 on it, which comes with vdr 1.6.0, the xine 0.8.2 plugin and dvb-1.1.0_CVS20080331-1.48. Is there a getting started with HDTV VDR FAQ somewhere? My first 3 questions questions are * Will a new VDR version be released today? The latest I could find is 1.7.7 (3 weeks old). * Where do I find the right DVB driver? * How do I configure LIRC, so it works with the S3-3200 and the remote control included with it? Thanks in advance for any hints, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
On Sun, 2009-05-24 at 16:49 +0300, Anssi Hannula wrote: Klaus Schmidinger wrote: http://linuxtv.org/hg/v4l-dvb should work, but you'll still need the patch from ftp://ftp.cadsoft.de/vdr/Developer/v4l-dvb-header-fix.diff because the header files apparently are still broken :-( This commit should've fixed them: http://linuxtv.org/hg/v4l-dvb/rev/dba0b6fae413 What error are you getting? Without that patch I am getting g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/home/cko/vdrconfig\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\ -I/usr/include/freetype2 -I/usr/src/v4l-dvb/linux/include dvbdevice.c In file included from dvbdevice.c:13: /usr/src/v4l-dvb/linux/include/linux/videodev2.h:64:28: error: linux/compiler.h: No such file or directory In file included from /usr/include/netinet/in.h:24, from /usr/include/arpa/inet.h:23, from config.h:13, from channels.h:13, from device.h:13, from dvbdevice.h:15, from dvbdevice.c:10: /usr/include/stdint.h:41: error: conflicting declaration 'typedef long int int64_t' /usr/include/linux/types.h:98: error: 'int64_t' has a previous declaration as 'typedef __s64 int64_t' /usr/include/stdint.h:56: error: conflicting declaration 'typedef long unsigned int uint64_t' /usr/include/linux/types.h:96: error: 'uint64_t' has a previous declaration as 'typedef __u64
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
On Sun, 2009-05-24 at 16:13 +0200, Carsten Koch wrote: ... With the patch I am getting g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/home/cko/vdrconfig\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\-I/usr/include/freetype2 -I/usr/src/v4l-dvb/linux/include audio.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/home/cko/vdrconfig\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\-I/usr/include/freetype2 -I/usr/src/v4l-dvb/linux/include channels.c g++ -g -O2 -Wall -Woverloaded-virtual -Wno-parentheses -c -DREMOTE_KBD -DLIRC_DEVICE=\/dev/lircd\ -DRCU_DEVICE=\/dev/ttyS1\ -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -DVIDEODIR=\/video\ -DCONFDIR=\/home/cko/vdrconfig\ -DPLUGINDIR=\./PLUGINS/lib\ -DLOCDIR=\./locale\-I/usr/include/freetype2 -I/usr/src/v4l-dvb/linux/include dvbdevice.c In file included from dvbdevice.c:13: /usr/src/v4l-dvb/linux/include/linux/videodev2.h:64:28: error: linux/compiler.h: No such file or directory I did a cd /usr/src/v4l-dvb/linux/include/linux ln -s /usr/src/linux-2.6.27.21-0.1/include/linux/compiler.h . that fixed it. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Newbee questions about HDTV VDR system with TT-budget S2-3200.
On Sun, 2009-05-24 at 13:22 +0200, Ales Jurik wrote:
you don't need lirc, try plugin remote (http://www.escape-
edv.de/endriss/vdr/). It seems to be easier to setup and works without
problems.
I got lirc to work first, then I read your message and
tried the remote plugin.
Very nice. No daemons to configure, etc.
I'll stick to the remote plugin.
I had to make the attached patch (inspired by a similar
patch I found using google) to make the remote control
work that came with my card.
Carsten.
diff -rc v4l-dvb-41d2c77ae71f/linux/drivers/media/common/ir-keymaps.c /usr/src/v4l-dvb/linux/drivers/media/common/ir-keymaps.c
*** v4l-dvb-41d2c77ae71f/linux/drivers/media/common/ir-keymaps.c Sun May 24 05:46:01 2009
--- /usr/src/v4l-dvb/linux/drivers/media/common/ir-keymaps.c Sun May 24 15:31:23 2009
***
*** 1761,1766
--- 1761,1819
EXPORT_SYMBOL_GPL(ir_codes_hauppauge_new);
+ /* TT remotes. */
+
+ IR_KEYTAB_TYPE ir_codes_tt_3200[IR_KEYTAB_SIZE] = {
+ /* Keys 0 to 9 */
+ [ 0x0c ] = KEY_0,
+ [ 0x03 ] = KEY_1,
+ [ 0x04 ] = KEY_2,
+ [ 0x05 ] = KEY_3,
+ [ 0x06 ] = KEY_4,
+ [ 0x07 ] = KEY_5,
+ [ 0x08 ] = KEY_6,
+ [ 0x09 ] = KEY_7,
+ [ 0x0a ] = KEY_8,
+ [ 0x0b ] = KEY_9,
+
+ [ 0x18 ] = KEY_MUTE,
+ [ 0x01 ] = KEY_POWER, /* system power */
+
+ [ 0x02 ] = KEY_SHUFFLE, /* exchanging arrow circle */
+ [ 0x1a ] = KEY_TV, /* TV/Radio Music */
+
+ [ 0x26 ] = KEY_VOLUMEDOWN,
+ [ 0x19 ] = KEY_TEXT,
+ [ 0x25 ] = KEY_VOLUMEUP,
+
+ [ 0x0d ] = KEY_UP,
+ [ 0x11 ] = KEY_DOWN,
+ [ 0x0e ] = KEY_LEFT,
+ [ 0x10 ] = KEY_RIGHT,
+ [ 0x0f ] = KEY_ENTER, /* OK */
+
+ [ 0x24 ] = KEY_CHANNELDOWN, /* ch- */
+ [ 0x13 ] = KEY_EXIT,
+ [ 0x23 ] = KEY_CHANNELUP, /* ch+ */
+
+ [ 0x14 ] = KEY_RED,
+ [ 0x15 ] = KEY_GREEN,
+ [ 0x16 ] = KEY_YELLOW,
+ [ 0x17 ] = KEY_BLUE,
+
+ [ 0x3a ] = KEY_RECORD,
+ [ 0x3b ] = KEY_PLAY,
+ [ 0x3c ] = KEY_STOP,
+ [ 0x12 ] = KEY_INFO, /* i */
+
+ [ 0x3d ] = KEY_REWIND, /* */
+ [ 0x3e ] = KEY_PAUSE, /* || */
+ [ 0x3f ] = KEY_FASTFORWARD, /* */
+ [ 0x22 ] = KEY_EPG,
+ };
+
+ EXPORT_SYMBOL_GPL(ir_codes_tt_3200);
+
IR_KEYTAB_TYPE ir_codes_npgtech[IR_KEYTAB_SIZE] = {
[ 0x1d ] = KEY_SWITCHVIDEOMODE, /* switch inputs */
[ 0x2a ] = KEY_FRONT,
diff -rc v4l-dvb-41d2c77ae71f/linux/drivers/media/dvb/ttpci/budget-ci.c /usr/src/v4l-dvb/linux/drivers/media/dvb/ttpci/budget-ci.c
*** v4l-dvb-41d2c77ae71f/linux/drivers/media/dvb/ttpci/budget-ci.c Sun May 24 05:46:01 2009
--- /usr/src/v4l-dvb/linux/drivers/media/dvb/ttpci/budget-ci.c Sun May 24 15:34:16 2009
***
*** 252,257
--- 252,267
else
budget_ci-ir.rc5_device = rc5_device;
break;
+ case 0x1019:
+ /* For the TT 3200 bundled remote */
+ ir_input_init(input_dev, budget_ci-ir.state,
+ IR_TYPE_RC5, ir_codes_tt_3200);
+
+ if (rc5_device 0)
+ budget_ci-ir.rc5_device = IR_DEVICE_ANY;
+ else
+ budget_ci-ir.rc5_device = rc5_device;
+ break;
default:
/* unknown remote */
ir_input_init(input_dev, budget_ci-ir.state,
diff -rc v4l-dvb-41d2c77ae71f/linux/include/media/ir-common.h /usr/src/v4l-dvb/linux/include/media/ir-common.h
*** v4l-dvb-41d2c77ae71f/linux/include/media/ir-common.h Sun May 24 05:46:01 2009
--- /usr/src/v4l-dvb/linux/include/media/ir-common.h Sun May 24 14:06:54 2009
***
*** 148,153
--- 148,154
extern IR_KEYTAB_TYPE ir_codes_encore_enltv[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_encore_enltv2[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_tt_1500[IR_KEYTAB_SIZE];
+ extern IR_KEYTAB_TYPE ir_codes_tt_3200[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_fusionhdtv_mce[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_behold[IR_KEYTAB_SIZE];
extern IR_KEYTAB_TYPE ir_codes_behold_columbus[IR_KEYTAB_SIZE];
___
vdr mailing list
vdr@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to keep the channel list tidy automatically (was: Timeouts and lost locks)
On Sat, 2009-05-23 at 11:47 +0200, Klaus Schmidinger wrote: ... You could also remove all unwanted channels from your list and set DVB/Update channels to names and PIDs. Then the EPG scan would only switch through the desired transponders. I believe there is room for improvement. Of course I want *all* channels I can use and I want new channels, too, if can use them. And I do not want to go through my list of channels manually all the time, find those that I cannot view and delete them manually. I believe VDR could do a much better (more thorough, less error-prone) job at that than I ever could. Here is a list of improvements that would greatly help maintaining a clean and useful channel list: 1) When VDR does its EPG scan, it switches to all channels anyway. Why not test each channel and see if it actually delivers data? If it does, set a new configuration field to 0. If it does not, increment that field by one. Lets call this field the absent value. The reason why we do not get any data does not matter. Maybe the channel is temporarily not broadcasting. Maybe it has ceased to exist. Maybe I do not have a cam for it. Maybe I have a suitable cam, but no subscription. 2) When zapping, automatically skip channels that have an absent value of 5 (maybe that value should be configurable). 3) Do not display channels anywhere that have an absent value of 5 (maybe that value should be configurable. If you set it to zero, all useless channels will show up again). 4) A cleanup run could remove all channels that have an absent value that exceeds a certain number (maybe 50). 5) You could define additional criteria that would increment the absent value during an EPG scan. For example: 5a) the channel does not broadcast one of the audio languages that I have configured as the set of languages that I can understand. 5b) the channel broadcasts video, but with less than 1 Mbit/s. (That would get rid of all those advertising channels which only broadcast slide shows). Cheers, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to turn a DVD into a regular VDR recording.
My DVD player is not working at the moment, so I want to watch a DVD on my VDR system in the living room. In an earlier message on this list, somebody said that the DVD plugin is not working, so I did not waste any time trying. Also, my VDR PC does not have a DVD ROM anyway. What I did, was: 1) I turned the DVD into a MPEG file using mplayer. Directly from a DVD ROM this can be done using mplayer -dumpstream dvd://1 If the DVD has already been ripped to an ISO image, this can be done using mplayer -dvd-device path_to.iso -dumpstream dvd://1 mplayer creates an MPEG file called stream.dump. 2) I created a Video directory for the recording: mkdir -p /video/%Name_of_the_movie/2009-03-01.00.00.00.99.rec 3) I used genindex 0.1.3 to split the file into VDR recording files and to create the index: genindex -r -i stream.dump -d /video/%Name_of_the_movie/2009-03-01.00.00.00.99.rec -s 1024 At least for the one DVD I tries so far, this worked fine. I also like the fact that I do not have to insert the DVD disk every time I want to watch the movie. It is nice to have it integrated seamlessly into my recordings. I guess most of this could have been done with the mplayer plugin as well, but AFAIK the mplayer plugin does not allow me to choose audio tracks, it requires a high system load for re-encoding and it reduces the quality during re-encoding. Just wanted to share my experience with the list. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr on PS3
Clemens Kirchgatterer wrote: i can see many of us are seeking for the right hardware for vdr, so i am. i want to start some discussion about the upcoming Sony PS3 as an vdr client on steroids. as it will support linux out of the box, it seams logical to, at least, think about it. I like the idea. Has anybody gotten VDR to run on the PS3 in the meantime? Apparently, there is a commercial vdr system for the PS3 available now. http://playtvps3.com It's a bit hard to find concrete technical information on the above web site, but it seems that this a DVB-T box and it costs 100 Euros. Not really exciting. I am looking for a silent, SAT-HDTV capable, inexpensive system. Would the PS3 be a good base for that? Any other suggestions? Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR Development
Davide Cavalca wrote: ... I'm neither Klaus not a regular of this list, but I think you're not being fair here: Klaus has every right to say he won't develop on a community tree; it is, after all, his own free time. BTW, if I remember well, Klaus has coded several features (i.e. subtitles) he himself said he didn't use. Like it or not, VDR is a cathedral-style project: this has led to higher code quality and very good stability, at the expense of a slower development pace and the lack of some bleeding-edge features in the mainline. If you want those features, you can use a patch posted on this list (e.g. for hdtv, sourcecaps) or use a plugin (e.g. for teletext subtitles). Many distributions include those patches or provide a way for the user to easily appy them. Of course, you're also free to develop your own patches for new features: if they're good enough, I'm sure they'll eventually find their way into the mainline, as it happened, e.g., with the shutdown handling rewrite some time ago. You say you want to fork it: what would you accomplish with that? It's not as if the code would magically write itself. I've yet to see a single prospective developer say if it were forked I'd write X. (And, BTW, there's nothing forbidding him to write X in form of a patch and post it on this list.) On the other hand, by forking you'd probably lose Klaus, who has written by himself the majority of VDR code and knows it like no one else. Finally, I personally fail to see why people switching to MythTV is a bad thing; VDR is not a religion, I think everyone should use whichever software he thinks suits best his needs. I'm very happy with VDR and won't be switching anytime soon. Davide, I have been following VDR development since June 2000 and I have been subscribed to this list since January 2002. I could not have put it better than you did above. I totally agree with everything you said. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] epg2timers 1.5.2a.
Brian wrote: a question about this version. In earlier versions you had a variable called episode, and I set the value of that to in my source file. Now you just add the string ~EPISODE to very programm name (if I understand the source correctly. You are mostly right. In epg2timers = 1.4.5, asking VDR to configure the episode name by adding ~EPISODE to the timer entry was configurable. In 1.5.2, I changed it, so epg2timers automatically uses ~EPISODE for short recordings up to an hour. For me, that works perfectly almost all the time. How do you like it? If you dont, I guess I can make the threshold configurable (default = 60 minutes) and you can set it to 0 to disable it. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] epg2timers 1.5.2a.
Manfred Schmidt-Voigt wrote: ... OK, no problem, this is the patch ... Thanks! I have simplified this and put it in. Attached is all I have so far for 1.5.2b. Can you please try it out and see if it still does what you wanted? Carsten. epg2timers_1.5.2a_1.5.2b.patch.bz2 Description: application/bzip ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] epg2timers 1.5.2a.
Manfred Schmidt-Voigt wrote: ... My question: Are there any plans to support also the extended information like actor, director, year of first appearence, etc? We can get these infos just by setting jl_format=3, but it's not decoded by epg2timer.cxx. Sounds like an interesting idea. No, I am not actively enhancing epg2timers at the moment. I have another very time-consuming project this year. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
Klaus Schmidinger wrote: ... Should there be a stable version 1.6.0 now, based on what's in version 1.5.14, but without DVB-S2 or even H.264 support? Yes or No? My (selfish) vote is No. I do like the fact that 1.5.14 raises some expectation of DVB-S2 support in the (official or distribution's) kernel. So, for me only a DVB-S2 capable VDR 1.6.0 makes any sense. Therefore, I vote NO to a 1.6.0 without DVB-S2. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Straw poll: stable version 1.6.0 now?
Andrey Kuzmin wrote: ... I don't think that it is a good time to lose valuable Klaus's time for releasing supporting new stable version Absolutely right! A 1.6.0 release now will only slow down progress. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Thank you for all the good work and have a nice vacation!
Klaus Schmidinger wrote: ... I'll be on vacation for the next three weeks, so there won't be anything new in a while ;-) :-) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Technotrend S2-3200 HDTV-S2 supprt (was: [EMAIL PROTECTED])
Hi Klaus, Klaus Schmidinger wrote: ... Could you tell us which card did you buy, I would like to buy the same Technotrend S2-3200 HDTV-S2 I bought two of these to replace my old budget cards which were destroyed by lightning. Is yours working for you (at least in DVB-S mode) now? Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to change Pro7 SAT1 Channels via Menu
Helmut Auer wrote: ... 2) Look for the new channel entries at the end of your list and move them to the desired position. The second one is a no go - tell an old man how he should move channel 2000 to channel 2 ;) There should be an option to enter the desired number for the channel. Yeah, I know, it is another weak point in VDRs GUI. I personally do not care much, because I know how to use a text editor. ;-) However, there is a shortcut: If you want to move channel 2000 to position 2, go to channel 2000 in the channel list, press Mark (blue), press 2 and then OK. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Lightning destroyed my 4 DVB-S cards, what should I replace them with?
Torgeir Veimo wrote: ... A full features card still uses much less CPU however, and can automatically reclock the output based on the timing of the input DVB stream. If you're not replacing any other component at this time I'd stick with FF cards, Thanks! No, I guess I would like to keep the hardware that survived as it is, so perhaps it would be best to replace my broken FF cards 1:1 by TT-premium S-2300s and my broken budget cards 1:1 by TT-budget S2-3200. Does anyone have actual experience with a TT-premium S-2300 and or a TT-budget S2-3200? Do both run smoothly now? Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Lightning destroyed my 4 DVB-S cards, what should I replace them with?
I had 1 FF and 2 budget cards in one PC, 1 FF card in the other. All 4 were destroyed by lightning this morning during a thunderstorm. What are the best cards to replace them with? In an earlier post, Klaus wrote that he is working on HDTV support and that he is using a TT-budget S2-3200. Would that be a good model to replace my 2 budget cards with? Does the driver work reliably now? Is there a supported FF HDTV card? If no, would the TT-premium S-2300 be the best choice? Should I still buy a FF card at all or does xine or softdevice work just as reliably by now? Thanks for any hints! :-) Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] remoteosd / multi-box question
Simon Baxter wrote: ... Is there a way to refresh recording directories without restarting VDR? touch /video/.update ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Is there a way to give inode entries a higher cache priority than data in the linux kernel?
Matthias Schniedermeyer wrote: ... 1) Is there a bug in the linux kernel that makes it spin up the disk needlessly even if the data are still in the cache? ... I haven't tried or read it myself, but this: Documentation/laptop-mode.txt might contain the information you need. Correct. Interesting information. I'll try it out. Thanks, Matthias! Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Re: replay stuttering
Kartsa wrote: Kartsa kirjoitti: I have been running vdr now for a couple days with #define PLAYERBUFSIZE MEGABYTE(64) in dvbplayer.c and for now it seems like better as in no stuttering. But I am still testing it. Okey, I've had this setting in action for a week or so now and it is definitely better. There is still sometimes some stuttering but it is so suttle that it is barely noticeable. With MEGABYTE(1) the video occasionally stopped for a second and then stuttered for about 5 seconds and then resumed normal operation (with lesser cpu it could be stuttering to the end of the recording). As mentioned earlier in this thread, I had also sometimes noticed a similar effect video halts for a few seconds, then resumes and stutters for a few seconds. After recommending it to you, I have also increased PLAYERBUFSIZE to 64MB and I have not noticed the problem ever since. So there is a high probability that increasing PLAYERBUFSIZE improves matters. Maybe it should not be fixed, though, since a machine with very little RAM may suffer from thrashing if the VDR footprint is increased that much. I wonder if it should be configurable or if there would be an automatic way of determining the right size (i.e. start with 1 MB, then double it on every stutter and remember the value in the setup.conf file). Could the chosen file system be causing this? I use LVM creating one partition on two disks and then I create one xfs on that partition. The disks are sata as mentioned earlier. I do not think so. Maybe S.M.A.R.T., maybe hardware, but not the file system. I am using XFS on individual (mostly PATA) disks over NFS. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Re: replay stuttering (was: FF card A/V sync - in progress?)
Kartsa wrote: I've tested the new fw also and no sync problems has occurred. Although I was hoping that this would have corrected my stuttering problem also. Every now and then replayed video stops for a second or so and begins stuttering for some seconds and then continues normally. With earlier fw it usually caused A/V sync problem but now syncing is fine. This is not repeatable meaning that the problem does not occur if I rewind (or jump) and replay the same moment. Some time ago I had a PIII 550MHz system and in it the stuttering could continue indefinitely (or in the end of the recording :). After an upgrade of hw (new mb and amd 3000+ sempron) the stuttering lasts only a few seconds. From the symptoms you describe it seems very likely that your system has a bottleneck between VDR and the data. Is your VDR reading from local disks or via NFS? Are other things running on your machine that could make your disks busy? Do you have DMA enabled on your disks? BTW: I am also experiencing the same problems every now and then. I have S.M.A.R.T. enabled on all my disks and I am wondering if these hickups come from automatic self diagnostics? Maybe larger replay buffers in VDR would help? I am _assuming_ that this line #define PLAYERBUFSIZE MEGABYTE(1) in dvbplayer.c defines the buffer size? Klaus, can you confirm this? Kartsa, since the problem occurs quite often in your setup: Could you try to change the above line to #define PLAYERBUFSIZE MEGABYTE(64) and let us know if the problem still occurs? Thanks, Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] epg2timers 1.4.5.
epg2timers is a tool that allows you to use the web EPG at http://tvtv.de to program VDR from anywhere in the world simply by clicking on the things you want vdr to record in the http://tvtv.de listings. I have changed the epg2timers version number to match the VDR version number I tested it with. This should make it easy for you to find out what VDR version epg2timers works with. Of course, this does not mean epg2timers cannot work with other vdr versions. Simply try it out. epg2timers version 1.4.5 is now available in Klaus' Tools directory at ftp://ftp.cadsoft.de/pub/people/kls/vdr/Tools/epg2timers-1.4.5.tar.bz2 Changes since epg2timers 1.3.17: 1.3.32 17-Sep-2005 Update channel map. Implement support for multiple satellites. 1.4.5 16-Jan-2007 Update channel map. See the README file included with the distribution. Note that http://tvtv.de keeps changing the names of their channel logo images, which epg2timers uses to determine the channel an EPG entry belongs to. So, unfortunately, I have to keep changing the map and it will never be complete, since I do not have a lot of time chasing after channels I do not / cannot watch. Contributions are always welcome and maybe in the future I'll change the algorithm so the channel map will be based on a plain text channel name somewhere in the HTML code of the merkliste page. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Best DVB-S card
Glyn Edwards wrote: ... I've been looking at the Nexus-S because it is fully featured and I don't have any spare PCI slots left. With a FF card I could remove the DXR3. If your VDR PC works fine with the DXR3, I would not recommend a fully featured DVB-S card. It is more expensive than a budget card and its firmware is still not mature. See the long thread about FF card A/V sync in this mailing list. It also crashes if you tune into HDTV channels. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] FF card A/V sync - in progress?
VDR User wrote: ... Logic still says that if mplayer can play vdr recordings just fine without losing sync, but vdr can't, the problem is with vdr, not the firmware. That's only correct if you ignore specifications. Maybe VDR is behaving according to the specified interface and the firmware fails. Maybe mplayer is working around firmware bugs by behaving differently - which may or may not be according to the specified interface. What we can agree upon is the fact that the problem *can* be solved within the application program. IMHO, the fact that mplayer works where VDR does not proves just that, but not more. However, if VDR behaves 100% according to specification, the problem *should* be solved in the driver and/or firmware, because that would fix all programs that also behave 100% according to specification and fail. If fixing it where it should be fixed turns out to be too difficult, it might still be a good idea to fix it in VDR. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Recording video clips automatically with correct naming of recordings.
I noticed today that Deluxe Music is labelling every song individually in the now and next EPG entries. I had been hoping such a feature would be provided by music channels. Congratulations to Deluxe for providing accurate program information. Would it not be extremely nice if one could ask VDR to record every song individually to a correctly named recording? I have not yet checked whether the now EPG entry changes at the exact right moment. If it does, it should be easy to automatically create a timer entry for it and delete any older timer entry for the same channel. I wonder if they would mind. If they do, I guess they could provide slighly less accurate program information. I wonder if that could be easily fixed with noad. Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: AW: [vdr] Doubling my available VDR disk space without cost or loss of convenience.
Guido Fiala wrote: ... Sounds like the core computer of the USS-Enterprise - How many Terra-Quads are this? ;-) Actually, according to http://www.kasper-online.de/en/docs/startrek/ncc1701d.htm the Enterprise D has a mere 630.000 Kiloquads. But seriously: My VDR system started out in June 2000 with a 9GB SCSI disk in a 150 MHz PentiumPro system. Disk space has increased a bit since then, but in another 6 years all of that will fit into a single disk and that will not be the largest disk you can buy for a home computer, either. Neither is my VDR system even close to the largest one. I believe that Matthias Schniedermeier has so many disks in his house that the house no longer requires a separate heating system. ;-) Carsten. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: AW: [vdr] Doubling my available VDR disk space without cost or loss of convenience.
Carsten Koch wrote: ... Actually, according to http://www.kasper-online.de/en/docs/startrek/ncc1701d.htm the Enterprise D has a mere 630.000 Kiloquads. Sorry, wrong link. I meant this one: http://www.ex-astris-scientia.org/misc/artikel-computer.htm ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
