Re: [vdr] error compiling vdr-xine
Thanks a lot, that works serge -Oorspronkelijk bericht- Van: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Namens Reinhard Nissl Verzonden: zondag 13 januari 2008 21:01 Aan: VDR Mailing List Onderwerp: Re: [vdr] error compiling vdr-xine Hi, serge pecher schrieb: > I did install ffmpeg, xine-lib 1.2, and xine-ui to get vdr-xine working. > > After searching a bit I achieve to compile the 3 first one, but I have > an error with make plugins. Input_vdr.h is missing. > > I can't find that file on my system. > > The make process tell me to patch xine-lib, but in the INSTALL file of > the plugin it is written that you don't need to patch if using xine-lib 1.2 > > Any idea ? xine-lib-1.2-hg requires vdr-xine-0.8.1, which knows about the renamed input_vdr.h (it's now called vdr.h). Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ 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] Fwd: xineliboutput and WSS aspect ratio
Hello Gentlemen, i sent sent following email Petri Hintukainen and then found this mailing list, which looks like it could be a better forum for my questions. Cheers, Raphael. -- Forwarded Message -- Subject: xineliboutput and WSS aspect ratio Date: Monday 14 January 2008 09:38 From: Raphael Coeffic <[EMAIL PROTECTED]> To: Petri Hintukainen <[EMAIL PROTECTED]> Hi Petri, i'm using at home VDR with your xineliboutput plugin for a few month, which is really a good software in my opinion. The TV card i'm using is a Hauppauge PVR 250 (analog with hardware encoder, no decoder). As the card is able to embed VBI data (Teletext, WSS, etc...), i am wondering if i could use that information to set the correct cropping / aspect ratio. The story begun as i noticed that the autocrop post plugin included with xineliboutput had a pretty hard time detecting letterbox 16:9 format on my host. During 16:9 broadcasts, it does most of the time just nothing. Then, maybe once every 10s, it would enable cropping during 1s and immediatly switch back to 4:3 format. That's why i thought, i could use the Wide Screen Signal (WSS) to detect 16:9 letterbox without using the autodetection feature included in the autocrop plugin (which would save some CPU time, and surely work better at my place). Concerning the VBI data, i will embed them into the MPEG TS, as specified by EN 301 775 (done in "pvrinput" VDR plugin). Then, i could decode those VBI data in xineliboutput. Now, this is where your help would be very usefull for me: i have no idea how to go further from there. Do you have some suggestions, how i could set the correct cropping parameters from within the xine frontend? Thanks Raphael. --- -- Dipl. Inf. Raphael Coeffic iptelorg GmbH Am Borsigturm 11 13507 Berlin Germany [EMAIL PROTECTED] www.iptelorg.com T +49-30-3251-3218 F +49-30-6908-8248 ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Rotor patch for 1.5.12
Hy Sorry for late reply. I dont know why but when apliing the patch dvbdevice.h not geting patched so i modified manual and now its working. About functionality i wil post later beacause i'am at work. I will be to your tester and 10x again. Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] Plugin request: remote control
Hi, If someone has talent, will and free time then it would be really nice to have a plugin that could show remote control in graphical format (skins). From each used button there is a thin line and a label describing the meaning of the button. The plugin should be possible to call from VDR itself naturally but also from any plugin. Lines and labels are naturally updated according to the plugin. Hopefully someone else finds this kind of feature important i.e. I'm not the only one who don't remember the meaning of the buttons (mainly numbers) in different context (VDR's record editing, DVD plugin, mplayer plugin etc. etc.). Br, Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] streamdev-client multiple servers
Hi all, Having finally found some time for a major upgrade to my VDR setup I stumbled upon this issue, which has probably come up already, but googling and a search in an archive of this ML did not yield a quick solution... Is there a patch for allowing streamdev-client to connect (using VTP) to multiple streamdev-server's? Current code AFAIK only handles one IP for the VTP server. What I actually want is to have streamdev-client support for querying a list of servers (in some order) for a given channel, and then connecting to a suitable one if several were found. If not, would you guys say its feasible/desirable? Regards, Pjotr P.S. Yes, I know I could probably do it serially, but that is not an option from the scalability point of view due to latency for forwarding VTP streams... P.P.S. Cloning streamdev-client multiple times is also not that practical I guess... Can plugins be instantiated multiple times? ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] H.264 VPID's
Hi, ShorTie schrieb: > Been playing with this genpix, hd and xine. Pretty much got everything > running except for 1 thing seems to be hiding from me. > > For vdr to be able to tune to a hd channel I need to add 1 to the > vpid’s which I do in my nscan/convert/pad10 no biggie. > > The problem is that when I tune away from a hd channel vdr rights back > to the channels.conf with the normal vpid not the vpid+1 like I had. > > Thus I can’t tune back to that channel till i manually change the > channels.conf back again. > > I’m I missing a setting somewhere? No -- looks like your service provider announces the stream as MPEG2. Please ask your service provider to fix this issue. Try the attached patch as workaround meanwhile. It doesn't change vpid anymore to MPEG2 once you've changed it to H.264 manually. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] --- ../vdr-1.5.12-dvbs2-other/pat.c 2008-01-01 22:55:18.0 +0100 +++ pat.c 2008-01-14 20:07:30.0 +0100 @@ -343,7 +343,10 @@ void cPatFilter::Process(u_short Pid, u_ switch (stream.getStreamType()) { case 1: // STREAMTYPE_11172_VIDEO case 2: // STREAMTYPE_13818_VIDEO - Vpid = stream.getPid(); + if (VPID_IS_H264(Channel->Vpid())) + Vpid = VPID_TO_H264(stream.getPid()); + else + Vpid = stream.getPid(); break; case 3: // STREAMTYPE_11172_AUDIO case 4: // STREAMTYPE_13818_AUDIO ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] streamdev-client multiple servers
Hi, 2008/1/14, Pjotr Kourzanov <[EMAIL PROTECTED]>: >Is there a patch for allowing streamdev-client to connect (using VTP) to > multiple streamdev-server's? Current code AFAIK only handles one IP for the > VTP server. What I actually want is to have streamdev-client support for > querying a list of servers (in some order) for a given channel, and then > connecting to a suitable one if several were found. it's easy. You don't need any patch ;-) http://www.vdr-wiki.de/wiki/index.php/Streamdev-plugin#Streamdev-client_mit_mehreren_Verbindungen_oder_Servern Small translation Copy a libvdr-streamdev-client.so.$(APIVERSION) to libvdr-streamdev-client2.so.$(APIVERSION). Start a vdr with both clients, and define for each client a IP of server. Пока Олег ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] BUG: DVB-T and DVB-S[2] do not work with VDR & multiproto
Reinhard Nissl wrote: > Hi, > > Morfsta schrieb: > > >>> Please report the debug output here for further investigation. >>> >> Attached are two files - tuning to the same DVB-T channel using either >> system and the Philips frontend... vdr-1.4.x shows the channel fine, >> 1.5.12 does not. >> >> Hope this helps and thanks again for your assistance. >> > > Hmm, the translation layer doesn't work correctly. It doesn't > translate new bandwidth value 1 to old bandwidth value 0, > although there exists code to do this translation, and it should > get called as the other translations happen correctly. > > As a result the old driver uses a bandwidth of 7 MHz instead of 8 > MHz. > > While copying the code here to ask for help in searching the bug, > it seems that I found the bug -- a missing break in the DVB-T > case ;-) > > Please try the attached patch. > > Bye. > > > > ___ > vdr mailing list > vdr@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr > Big thanks guys, works here too! Finally I can put my S2-3200 in my "production" server. /Magnus H ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr with DVB-S2 patch and TT3200
Hi all, first of all thanks a lot to Klaus Schmidinger for his great work but also to Manu Abraham, Marco Schlüßler and Reinhard Nissl for taking up the DVB-S2 challenge! I have a DVB-S based vdr running as server for recordings and streamdev-server for remote live-view. Now I was playing around with the latest multiproto drivers from Manu to tune some DVB-S2 channelson my TT3200. This is working with (Manu's) szap, but unfortunately not with vdr. I applied the latest version of Reinhards DVB-S2 + h264 patch, but I can't record or stream any DVB-S2 channels (no matter if they are h264 or mpeg2). h264 on DVB-S works fine (i.e. BBC HD) and I also haven't got any rejects from the patch or errors during compile. Here what happens if I tune to ProSieben HD: ProSieben HD;ProSiebenSat.1:12722:hC23M5S1Z35:S19.2E:22000:10255+255:0;259=deu:0:0:10200:1:1119:0 Jan 14 22:14:37 vdr dvb_frontend_ioctl: DVBFE_GET_INFO Jan 14 22:14:37 vdr dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Jan 14 22:14:37 vdr vdr: [11966] set DVB-S2 Jan 14 22:14:46 vdr vdr: [11966] frontend 2 timed out while tuning to channel 3142, tp 112722 Jan 14 22:14:46 vdr vdr: [11966] set DVB-S2 Jan 14 22:14:46 vdr dvb_frontend_ioctl: DVBFE_GET_INFO Jan 14 22:14:46 vdr dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Jan 14 22:14:52 vdr vdr: [11966] set DVB-S Jan 14 22:14:52 vdr dvb_frontend_ioctl: DVBFE_GET_INFO Jan 14 22:14:52 vdr dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2 Any ideas what could be wrong? Thanks, Christian ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] vdr + h264
Hi, is it correct that h264 is written as PES via PlayVideo() ? For decoding with ffmpeg it would be useful to have a PROGRAM_STREAM_MAP in front of a new video stream. -- Stefan Lucke ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr + h264
Hi, Stefan Lucke schrieb: > is it correct that h264 is written as PES via PlayVideo() ? > > For decoding with ffmpeg it would be useful to have a > PROGRAM_STREAM_MAP in front of a new video stream. Basically not a bad idea, but where do you put it in live streaming? Or after a seek in VDR's recording player? Mplayer does some nice tests to determine PES vs. ES. It has just not been extended to detect H.264 in the same way. H.264 uses a limited start code set compared to MPEG1/2 so it should be easy to detect the content, due to the distribution of start codes. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] vdr + h264
On Tuesday 15 January 2008, Reinhard Nissl wrote: > Hi, > > Stefan Lucke schrieb: > > > is it correct that h264 is written as PES via PlayVideo() ? > > > > For decoding with ffmpeg it would be useful to have a > > PROGRAM_STREAM_MAP in front of a new video stream. > > Basically not a bad idea, but where do you put it in live > streaming? I think it should be transmitted first, after a stream reset. A basic PSM that maps from PES 0x01e0 to h264 could look like: unsigned char psm_map_0xe0_to_h264 [] = { 0x00, 0x00, 0x01, 0xbc, 0x00, 0x10, // psm length 0x00, 0x00, // unknown 0x00, 0x00, // info length // info data here 0x00, 0x04 // map length // map data here 0x1b, 0xe0, 0x00, 0x00 // h264 map entry / NO map info 0x00, 0x00, 0x00, 0x00 // crc32 }; That is inspired by ffmpegs: libavformat/mpeg.c mpegps_psm_parse() line ~220 . > Or after a seek in VDR's recording player? By above, it's just (pinned) at the beginning of the file. Don't know if we should expect changes in between (but all bad things happen). > > Mplayer does some nice tests to determine PES vs. ES. It has just > not been extended to detect H.264 in the same way. Aren't users beeing told to feed mplayer with PSM too ? > H.264 uses a > limited start code set compared to MPEG1/2 so it should be easy > to detect the content, due to the distribution of start codes. > -- Stefan Lucke ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] contact to femon plugin developer
Hello Rolf, do you speak german? > On Sat, 12 Jan 2008, Sebastian Dellit wrote: >> is there a possibility to contact the femon-plugin developer? I want >> to give any feature request for make the femon plugin accessible for >> braille users. > The necessary contact information can be found in plugin's source > package. You means in the README file? All right. I have only visit the homepage of the plugin. There are no contact information. :-( > A few years ago I had an idea to provide audible tone that varies > according to current signal level. Unfortunately, I encountered some > problems while implementing it and the feature never saw the daylight: The idea sounds good. > - I couldn't get the live tv video and signal tone work at the same >time, when using budget cards and full featured card as tv out. > - DVB drivers signal strength and signal-to-noise values works correctly >only for a few cards. There're plenty of cards that provides inverted >or zero strengt values. > However, I implemented several SVDRP commands into the plugin and those > commands can be used to provide the above mentioned functionality via > an external application in a similar manner as in 'femonspeak'. [1] Femonspeak soundss also good. I will look on this. > If you'll have a neat idea about new features, just drop me an email. I hope my idea is simple. many Any users use a braille display and speech to access the vdr. Is it possible to create a femon skin which show the information in plain text on the OSD? E. g. the developer of the lastfm-plugin has include a function. You can change between graphic and text display. If you select the text version all informations (title, track etc.) can read with an braille display. The plugin also use a function to select the refresh rate of the display. If you select "0" you can always refresh the display manual. The femon plugin IMHO needs a simular function. What do you means? It is possible? -- Best regards Sebastian ICQ: 264706583 | MSM: [EMAIL PROTECTED] | Skype: sebo_de | Yahoo: de_sebo E-Mail: [EMAIL PROTECTED] | Web: www.blindzeln.de ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr