Re: [vdr] next features?
And as long as there isn't at least a (graphics) card that supports decoding the good old MPEG2 in a quality that is at least as good as that of the FF DVB cards, as well as decoding H.264/HDTV in *hardware*, this whole area has next to no priority for me. I am not interested in software decoding this stuff - I don't want to have an extra heater in my living room ;-) That is interesting thread to read, thanks to Morfsta that said that many others wanted to say already long time ago :) I think that Morfsta's main point isn't any specific feature of VDR like HD support. The point is VDR's development model itself. It is closed now. Patches are not the answer to this problem. Developers have to be very motivated to maintain patches from version till version. As you see, MUCH patches are already died, not because nobody wants them, because it's hard to maintain them for years. Klaus, you are doing the great job! But I think VDR now is much more than your own hobby/job/lack of software for your personal needs and hardware. Big part of VDR's community also want to own it. By ownership I mean here decision making and commiting to CVS/SVN/HG. Current development model looks like dictatorship model :) If you allow to commit improvements to VDR by other authorized devs, such things as UTF8 support were in VDR since 1.3.* I think :) I belive VDR and VDR's community will gain a lot from this. Imagine if Linus Torvalds were the only man, who were decision maker in kernel's development. I belive linux never become so popular because of being always 2 steps backward of current community's needs. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] next features?
The point is that Klaus has very strict demands on code quality, and many patches never get up to that quality level. Thanks to that strictness, the VDR sources are relatively clean and straight implemented, and we're pleased with frequent rock-solid so-called 'developer' releases. That is very good point for end user to know that he compiled ideal source. There is some lack of very useful features, but the source is ideal. Sorry for sarcasm :)) Big part of VDR's community also want to own it. By ownership I mean here decision making and commiting to CVS/SVN/HG. I've never seen an open source project where everyone is allowed write access to software repositories. There's always a very small group of people with write access, and any changes go through a strict review process before they're accepted. I've also told about this, about the group of authorized developers. But my point was not only authorized developers. My point was make more than one decision maker. I was really disappointed reading Klaus's decision not to do anything in H264 field only because he don't needed it (at least now). And this was not the only one feature that what denied or delayed because of this reason (remember how much time takes migration to 2.6.* kernels ;) In the end, what we could really need, are some developers that are persistent enough to develop their patches to a point where Klaus agrees to take over the patch as it is, without the need to do it any better. How developer should be motivated to do his job, if there will be exam of his skills at the end by only one man with his own vision of quality of code and what is needed for project and what not? ;) As I see there are people in this group who wants to participate in this development. But the rules of this process should be more clear and open. IMHO. And the only thing that I think that could help in VDR development is a public bug tracking system, where bugs and feature requests could be developed to quality patches. Exactly. And also voting system, what features are more needed for community, what less. But o.t.o.h. what stops us from doing this in the mailing list? IMHO this will not work good, because of much reasons like you have to track mailing list and so on, it will be easier to to check such bugtracking/voting system from time to time. P.S. Again, nothing personal. I'm only talking about the process. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR 1.5.12 text2skin: how to compile?
Hi, I've googled and tried all patches I could find to build text2skin against 1.5.10 (11 and 12 too), but still could not build text2skin plugin. Any how-to's or working patches? Thanks! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.12 text2skin: how to compile?
I've used every version of the current vdr developer tree and haven't needed an updated text2skin patch since 1.5.4. Try the attached patch. Hello! Thanks for your quick response. Still no luck, please tell me, what I'm missing: 1) wget ftp://ftp.cadsoft.de/vdr/Developer/vdr-1.5.12.tar.bz2 2) successfully applied your vdr-1.5.4-text2skin.diff to VDR 3) getting text2skin from CVS to PLUGINS/src folder: cvs -d:pserver:[EMAIL PROTECTED]:/var/cvsroot login cvs -d:pserver:[EMAIL PROTECTED]:/var/cvsroot co text2skin 4) sed -i Makefile -e 's/VDRVERSION/APIVERSION/' in text2skin folder 5) make REMOTE=LIRC CPUOPT=pentium-mmx PARALLEL=PARALLEL_64_MMX make plugins getting build error: make[1]: Entering directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='text2skin' -I/usr/include/freetype2 -I../../../include -I../../../../DVB/linux/include -I../../../../DVB/include -I. -o text2skin.o text2skin.c text2skin.c: In member function ‘virtual bool cText2SkinPlugin::Start()’: text2skin.c:28: ошибка: некорректное преобразование из ‘char*’ в ‘int’ text2skin.c:28: ошибка: при инициализации 1 -го аргумента ‘void cText2SkinStatus::SetLanguage(int)’ make[1]: *** [text2skin.o] Ошибка 1 make[1]: Leaving directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' *** failed plugins: text2skin Error message is in russian, it's about type casting... My system is Ubuntu 7.10 with latest apt-get upgrade Thanks! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR 1.5.12 text2skin: how to compile?
I don't know why it fails (I'm using VDR 1.5.12 with text2skin currently, on Gentoo, so it is possible to compile it). but to get the errors in English build by typing 'LANG=C make' (i.e. change the LANG variable during compile). That way you'll may get more answers, I don't know how many of the programmer guys here now Russian =) Hope you get it to compile, Thanks for hint! English error message is: ake[1]: Entering directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' g++ -Wall -Woverloaded-virtual -O2 -g -c -DHAVE_IMAGEMAGICK -DHAVE_FREETYPE -D_GNU_SOURCE -DPLUGIN_NAME_I18N='text2skin' -I/usr/include/freetype2 -I../../../include -I../../../../DVB/linux/include -I../../../../DVB/include -I. -o text2skin.o text2skin.c text2skin.c: In member function 'virtual bool cText2SkinPlugin::Start()': text2skin.c:28: error: invalid conversion from 'char*' to 'int' text2skin.c:28: error: initializing argument 1 of 'void cText2SkinStatus::SetLanguage(int)' make[1]: *** [text2skin.o] Error 1 make[1]: Leaving directory `/ego/vdr/33/vdr-1.5.12/PLUGINS/src/text2skin' *** failed plugins: text2skin ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR, Ubuntu upstart
Hi! I'm looking how to solve such issue: when I run runvdr script in terminal window of my Ubuntu 7.10 (with russian UTF8 locale), OSD shows correct russian EPG, channel lists, etc... But when I run vdr using upstart's script: exec /ego/vdr/_runvdr console output respawn the only language I could see is english, russian texts are replaced with ??? May be anyone could advice right direction to move? Thanks! ___ 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?
What are chances that multiproto will be merged to kernel in the nearest time (1-2 months?) If chances are big, I don't think that it is a good time to lose valuable Klaus's time for releasing supporting new stable version that will freeze another stable 1.8 with multiproto support till 2009 :) So my vote is is NO in this case ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR, Ubuntu upstart
Answering myself. I've changed script to: console output respawn script LANG=ru_RU.UTF-8 export LANG /ego/vdr/_runvdr end script and everyting works now Hi! I'm looking how to solve such issue: when I run runvdr script in terminal window of my Ubuntu 7.10 (with russian UTF8 locale), OSD shows correct russian EPG, channel lists, etc... But when I run vdr using upstart's script: exec /ego/vdr/_runvdr console output respawn the only language I could see is english, russian texts are replaced with ??? May be anyone could advice right direction to move? Thanks! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] XXV UTF-8
Hi! I'm trying to setup XXV (latest SVN version). Everything seems to run OK, except I could not see russian EPG and channel list. Texts look like: tr tdTitle/td td#xd0;#x9b;#xd0;#xa3;#xd0;#xa7;#xd0;#xa8;#xd0;#x98;#xd0;#x95; #xd0;#x9a;#xd0;#x98;#xd0;#x9d;#xd0;#x9e;#xd0;#xa2;#xd0;#xa0;#xd0;#xae;#xd0;#x9a;#xd0;#x98;#x2d;2007/td /tr so they are HTML encoded. How to fix that? My system is Ubuntu 7.10 with russian locale, VDR 1.5.12 ___ 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? - Result!
In any case - thanks to Klaus that community were involved in this process. IMHO feature requests polls will also be useful. As we see now, teletext subtitles are also important feature for many of VDR users, may be there are others too :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] XXV UTF-8
XXV has'nt at present UTF8 support, this feature is planned but not released. Only latin1 charset work up to the present. as VDR is UTF-8 now and as I see there are much chances that there will be new stable 1.6 with UTF-8 soon, please move this feature higher in your list :) XXV looks really great, looking forward starting to use it. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR Development
But! Coordinating such a Team is some thing that needs time, for itselfe. But all thouse discussions, about the priority of a feature should be done befor coding starts. May be it worth just to try and see if there is a problem here at all? ;-) I belive problem here is a bit different. There is no any good will to make this project more open. It's the direct path to become obsolete. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Minimal VDR install
I usually start by installing the latest version of ubuntu on one computer and then duplicate that directory for every client. Completely diskless clients booting through PXE or iSCSI from single image or from dedicated images from server are also worth to try. This work fast on gigabit networks with dedicated network cards on server per client. Haven't tried this with VDR yet, planning in future. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] xxv-1.3 - Feature release (1.4 rc)
Please add to readme or anywhere that mysql DB should be created as UTF8, --utf8 option is not enough to enable utf support for XXV, and this is non obvious for non experienced users. In any case, thanks that XXV finally supports utf8! Read the full announcement : http://xxv.berlios.de/content/view/43/1/ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] xxv-1.3 - Feature release (1.4 rc)
There is still one issue for me: http://binitex.com/jet/20090420-i7x-194kb.jpg It seems that long names are truncated. The problem is that even short names in Russian are truncated, may be because every cyrillic character is 2 bytes length in utf8. Could you point please to the line in code where truncation occurs, I'll try to adjust the length. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] xxv-1.3 - Feature release (1.4 rc)
This happens if you run vdr with --vfat then VDR cuts the recording name. Please check another screen shot http://binitex.com/jet/20090421-28m-192kb.jpg This is the same channel. Channel name is truncated in tree, recordings are in different place. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [Announce] xxv-1.3 - Feature release (1.4 rc)
Thanks! I've changed 10 to 40 to fix my issue new WebFXTreeItem(?% escape(chop(ch.0,10)) %?, ?cmd=programamp;data=?% ch.1 %?)); ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] Can I disable pause live tv altogher?
If there's any intention to add live tv caching then ram should definitely be available to the user as a storage option. Although I don't really care about the feature, I don't mind if my ram is being used whereas I absolutely don't want a harddrive constantly running for it. Btw, I haven't paid more then $20 for 2x2GB sticks of ram in ages, though I always take advantage of MIR's on them. I actually have 8GB sitting new in the packaging but didn't want to pass up some great deals. :) RAM + HDD = SSD Overheating, spinning... it's something from dinosaurs' era :)) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD output - your current favourites
And what DVB cards that support HD and are supported by current kernel drivers are in favorites now? I have a few VDR boxes and all of them now are using Nvidia cards and vdpau. I output the audio/video to my nice fancy tv with DVI-HDMI cables. It works great. I'm not sure what you're really asking though when you say what setup is ideal. That completely depends on _your_ needs wants but the only people I know with 'juddery' playback only experience it because the video card they have doesn't really have enough horsepower for the higher end hd content. Which could be solved by simply buying a different inexpensive video card. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] HD output - your current favourites
I don't keep a list of dvb cards drivers but you should know that dvb cards don't care if you're watching sdtv, hdtv, or whatever else. They don't care if the stream is mpeg2, mpeg4, etc. The only thing that is important is whether or not your dvb card supports the method the stream is broadcast (ie: modulation, fec, etc). The only exception is if you want to use a full featured, or in others words a card with an onboard mpeg decoder. In that case the onboard decoder needs to support whatever encoding is used in the stream (ie: mpeg2, mpeg4). So old WinTV Nexus DVB-S is enough for those experiments? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] How to remove double quotes in names for sharing in samba?
What I'm trying to do is to make a samba network share to /video folder to watch recordings from windows PCs. Everything works, BUT... Many EPG titles from my provider contain double quotes, so recordings look like TITLE_IN_RUSSIAN . When file names countains , samba converts this to something like _324CDE35 , so share contains unreadable directory names. I haven't found any way to force samba to deal with double quotes, so looking now for any way to force VDR to remove double quotes from recording names. One obvious way is to make a shell script that removes , but in this case it's not clear when to execute it, I mean how to know that recording finished. Any other ideas how to walk around this issue? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] How to remove double quotes in names for sharing in samba?
VDR option --vfat removes special characters from recording file names. That's exactly what I needed, thanks a lot! ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
