Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Reinhard Nissl wrote: Hi, Jörg Knitter schrieb: I'm currently using xineliboutput for my other client (on a standard PC), so this would be my first choice, but I've no problem to switch back to vdr-xine (which I used in the past - with the network patch... I moved to xineliboutput just because I don't want to patch xine-lib everytime anymore..) A nice feature that vdr-xine has over xineliboutput, is that it automatically sets itself as the primary device when a connection comes, and when the connection is closed it restores the previous primary device. This way I can either watch locally with the dxr3-plugin or remotely with vdr-xine. I experienced the same with xineliboutput. A very interesing feature of xinelibout is the ability to control deinterlacing, color settings etc. from within the VDR OSD in the plug-in´s settings. Furthermore, xineliboutput has a function that cuts and scales letterboxed 16:3 to anamorph 16:9, there is an audio equalizer and much more... Well, that's the cleaner approach of suppling an own frontend. I didn't want to write an own frontend. But my xine plugin has to act like a frontend within any other frontend and therefore requires some xine-lib patches to prevent deadlocks. I may have misunderstood what you meant with frontends, but xineliboutput *can* be used with other xine frontends, such as xine-ui, without patching xine-lib. -- Anssi Hannula ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Hi Reinhard 2007/11/13, Reinhard Nissl [EMAIL PROTECTED]: Are there any problems in submitting the needed patch to the mainstream xine-lib distribution? The problem is that small parts of the patch would break binary compatibility in xine-lib-1.1.x. This is no problem if a distribution decides to include the patch and recompiles all applications which use xine-lib-1.1.x. I still do provide those patches as not all people are willing to switch to xine-lib-1.2 (hg) which is still in development, contains the patches and therefore works out of the box. This is a very good news. As soon as 1.2 version will be stable it will be much more easy to use vdr-xine. Picture quality seems better to me in vdr-xine than in xineliboutput, so I'll be happy to go back to vdr-xine, I just didn't want to do all the patching anymore (expecially because it was needed both on client and servers in my networked enviroment). The new network feature is a big step forward (finding the network-patch for every new release was a pain), but xine-lib patch was still needed... Does it mean that a linux distro that include xine-lib-1.2 will be able to connect to a networked VDR-xine installation without the need of anything else apart from xine? I only have Skystar2/Airstai2 budget cards, so it's not an issue for me. A feature that allows to watch different channels on clients at the same time (without using multiple vdr installations and streamdev) would definetely make me switch back to vdr-xine :) And you wouldn't mind applying a huge patch on VDR to achieve this goal? This feature is so interesting that I certainly wouldn't mind, even if it would a very good feature to be included in the 1.5 vdr release... :) Thanks Graziano ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
On Wednesday 14 November 2007 13:19:39 Pasi Kärkkäinen wrote: On Tue, Nov 13, 2007 at 03:41:05PM +0100, alexw wrote: On Tuesday 13 November 2007 15:16:32 Graziano Pavone wrote: Hi, Using my PS3 as a vdr client is also my target. But I experienced bad (de-)interlacing when watching SD TV using SD output (even with right resolution). I am now waiting the new HV xorg driver to have more control on the video than the already available fb blit mechanism. I did rewrite the fb driver of xinelib to enhace it with ps3 blit functionality and virtual fb but it did not improve the output quality. By the way, the PS3 have a colorspace issue to display the OSD with proper color palette under the fb. (X is not affected by this) Actually I am using streamdev and xineliboutput together. Xineliboutput is good to pilot the server side from any linux based system. Streamdev + FF card + vdr is the best deal for client device (I am using this solution over wifi and it works like a charm) Streamdev + m3u patch is ideal to use VLC with playlist and allow Win OS to access the TV programs. Hi, I would like to use my PS3 as vdr client as well. I'm currently using xineliboutput for my other client (on a standard PC), so this would be my first choice, but I've no problem to switch back to vdr-xine (which I used in the past - with the network patch... I moved to xineliboutput just because I don't want to patch xine-lib everytime anymore..) Can you give more details of what are you using on your PS3? Thanks, Graziano Sure, Standard FC 7 (I will soon upgrade it to FC 8) modified version of iwconfig to allow wpa-psk(2) to work Xine-lib cvs (v1.1.6) vdr-sxfe or vdr-fbfe as needed The PS3 is connected to a SD TV set. As you can see it is not something complicated. Apparently when trying the same thing with HD (720p/1080p) television gives better result. (talking about picture quality) To enhance the picture quality on a SD TV you can deinterlace in sw before displaying the picture. The drawback is that an interlaced source is de-interlaced then interlaced again to coop with PAL standard. If you do that (deinterlace, then interlace again) you lose half of the framerate if you're using normal plugins for deinterlacing.. interlaced tv is 50/60 fields/sec, and after deinterlacing you usually end up with 25/30 frames/sec.. half of the motion/movement information just disappeared. end result is that your live video (series,sports,news) starts to look like jerky and shaky.. If you have interlaced output best option would be to display each field as it comes in (1:1).. then you would get best possible quality. If you have progressive display device, then best option is to use full-fps deinterlacing, meaning 50 fields/sec ends up 50 frames/sec, or even 100 frames/sec containing all the motion/movement info.. -- Pasi ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, I did test 1:1 output (PAL 720x576 - 720x576) but due to bad VSYNC the output is shaky. The kernel API provided for the vsync is not working very well with SD content. Unfortunately I do not have a progressive display. Rgds, Alex ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
mike lewis [EMAIL PROTECTED] writes: Hi, I've used vdr-xine, and I've used xinelibout for vdr. I've just ogt a general question, as they both seem to have similar functionality (or at least they both satisfy my need for a software client head to vdr. What's the driver for vdr-xine? I've heard people say xinelibout is better because it is more stable. But, whats the reality? If you've used both you should be able to compare them, shouldn't you ? I've also used both. Now i'm only using xineliboutput because (just facts, no attack !) - it has support for network without patching for longer - it doesn't require me to recompile libxine - network features are more advanced - i can have more that one frontend watching/sharing the same channel. - now i just aptitude install libxine1-xvdr to install the client side. Obviously the two plugins are both great plugins. And, Reinhard you do a really good job providing patches for vdr xine ! Thanks a lot. I guess the hidden question was have you ever considered to merge the two projects ?, wasn't it ? :) My question would be: one vdr, one xineliboutput plugin, 2 dvb cards, 2 independant frontends displaying different channels(+osd and stuff) without streamdev, has it been considered ? :) -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
On Nov 13, 2007 7:12 PM, [EMAIL PROTECTED] wrote: mike lewis [EMAIL PROTECTED] writes: Hi, I've used vdr-xine, and I've used xinelibout for vdr. I've just ogt a general question, as they both seem to have similar functionality (or at least they both satisfy my need for a software client head to vdr. What's the driver for vdr-xine? I've heard people say xinelibout is better because it is more stable. But, whats the reality? If you've used both you should be able to compare them, shouldn't you ? Well no, as I used them in the past and my media box died; and my memory isn't all that good.. so now I'm re-assessing my new solution based on running linux on a ps3; and I can't compare them until I've installed them both... Which is basically what I want to avoid ;-). I've also used both. Now i'm only using xineliboutput because (just facts, no attack !) - it has support for network without patching for longer - it doesn't require me to recompile libxine - network features are more advanced - i can have more that one frontend watching/sharing the same channel. - now i just aptitude install libxine1-xvdr to install the client side. Yes, the support for users like me on something like ubuntu is one reason why i'm likely to go down the path xinelibout. Obviously the two plugins are both great plugins. And, Reinhard you do a really good job providing patches for vdr xine ! Thanks a lot. I guess the hidden question was have you ever considered to merge the two projects ?, wasn't it ? :) Well no, my question probably should have been: whats the difference between the two plugins; if I'm using either simply as a software headend (similar to softdevice, but not permanently on) is their any feature which would drive the selection of xinelibout over vdr-xine? My question would be: one vdr, one xineliboutput plugin, 2 dvb cards, 2 independant frontends displaying different channels(+osd and stuff) without streamdev, has it been considered ? :) I think the answer there is to use one vdr per head-end. Thanks for jumping on board the QA session! hehe.' Mick ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
On Tuesday 13 November 2007 13:50:42 mike lewis wrote: On Nov 13, 2007 7:12 PM, [EMAIL PROTECTED] wrote: mike lewis [EMAIL PROTECTED] writes: Hi, I've used vdr-xine, and I've used xinelibout for vdr. I've just ogt a general question, as they both seem to have similar functionality (or at least they both satisfy my need for a software client head to vdr. What's the driver for vdr-xine? I've heard people say xinelibout is better because it is more stable. But, whats the reality? If you've used both you should be able to compare them, shouldn't you ? Well no, as I used them in the past and my media box died; and my memory isn't all that good.. so now I'm re-assessing my new solution based on running linux on a ps3; and I can't compare them until I've installed them both... Which is basically what I want to avoid ;-). I've also used both. Now i'm only using xineliboutput because (just facts, no attack !) - it has support for network without patching for longer - it doesn't require me to recompile libxine - network features are more advanced - i can have more that one frontend watching/sharing the same channel. - now i just aptitude install libxine1-xvdr to install the client side. Yes, the support for users like me on something like ubuntu is one reason why i'm likely to go down the path xinelibout. Obviously the two plugins are both great plugins. And, Reinhard you do a really good job providing patches for vdr xine ! Thanks a lot. I guess the hidden question was have you ever considered to merge the two projects ?, wasn't it ? :) Well no, my question probably should have been: whats the difference between the two plugins; if I'm using either simply as a software headend (similar to softdevice, but not permanently on) is their any feature which would drive the selection of xinelibout over vdr-xine? My question would be: one vdr, one xineliboutput plugin, 2 dvb cards, 2 independant frontends displaying different channels(+osd and stuff) without streamdev, has it been considered ? :) I think the answer there is to use one vdr per head-end. Thanks for jumping on board the QA session! hehe.' Mick ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr Hi, Using my PS3 as a vdr client is also my target. But I experienced bad (de-)interlacing when watching SD TV using SD output (even with right resolution). I am now waiting the new HV xorg driver to have more control on the video than the already available fb blit mechanism. I did rewrite the fb driver of xinelib to enhace it with ps3 blit functionality and virtual fb but it did not improve the output quality. By the way, the PS3 have a colorspace issue to display the OSD with proper color palette under the fb. (X is not affected by this) Actually I am using streamdev and xineliboutput together. Xineliboutput is good to pilot the server side from any linux based system. Streamdev + FF card + vdr is the best deal for client device (I am using this solution over wifi and it works like a charm) Streamdev + m3u patch is ideal to use VLC with playlist and allow Win OS to access the TV programs. If you want to start developping good SD support for the PS3 I would be pleased to provide some help. Cheers, Alex ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Hi, Using my PS3 as a vdr client is also my target. But I experienced bad (de-)interlacing when watching SD TV using SD output (even with right resolution). I am now waiting the new HV xorg driver to have more control on the video than the already available fb blit mechanism. I did rewrite the fb driver of xinelib to enhace it with ps3 blit functionality and virtual fb but it did not improve the output quality. By the way, the PS3 have a colorspace issue to display the OSD with proper color palette under the fb. (X is not affected by this) Actually I am using streamdev and xineliboutput together. Xineliboutput is good to pilot the server side from any linux based system. Streamdev + FF card + vdr is the best deal for client device (I am using this solution over wifi and it works like a charm) Streamdev + m3u patch is ideal to use VLC with playlist and allow Win OS to access the TV programs. Hi, I would like to use my PS3 as vdr client as well. I'm currently using xineliboutput for my other client (on a standard PC), so this would be my first choice, but I've no problem to switch back to vdr-xine (which I used in the past - with the network patch... I moved to xineliboutput just because I don't want to patch xine-lib everytime anymore..) Can you give more details of what are you using on your PS3? Thanks, Graziano ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
2007/11/13, Luca Olivetti [EMAIL PROTECTED]: Note that 0.8.0 has network support built-in. I know but you still have to patch and recompile xine-lib... Are there any problems in submitting the needed patch to the mainstream xine-lib distribution? A nice feature that vdr-xine has over xineliboutput, is that it automatically sets itself as the primary device when a connection comes, and when the connection is closed it restores the previous primary device. This way I can either watch locally with the dxr3-plugin or remotely with vdr-xine. I only have Skystar2/Airstai2 budget cards, so it's not an issue for me. A feature that allows to watch different channels on clients at the same time (without using multiple vdr installations and streamdev) would definetely make me switch back to vdr-xine :) ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
On Tuesday 13 November 2007 15:51:06 Graziano Pavone wrote: Sure, Standard FC 7 (I will soon upgrade it to FC 8) modified version of iwconfig to allow wpa-psk(2) to work Xine-lib cvs (v1.1.6) vdr-sxfe or vdr-fbfe as needed I'm using Ubuntu, with wired ethernet. connection So both framebuffer and xorg with xineliboutput are working? Did you compile them yourself, or there are binaries qavailable for Fedora? What about CPU usage. Is the PS3 able to display everything smoothly (with and without the OSD)? I am compiling everything myself because I need to apply some patch to enable new features. (kernel side, library side). But if you want to avoid hacking the system you need to find a ppc repository containing VDR packages, especially xinelibouput plugin. Yes, the PS3 is able to display both video and OSD smoothly. As I said earlier the SD picture quality is really not optimum. May be someone can comment 720p or 1080p outputs? The PS3 is connected to a SD TV set. As you can see it is not something complicated. Apparently when trying the same thing with HD (720p/1080p) television gives better result. (talking about picture quality) To enhance the picture quality on a SD TV you can deinterlace in sw before displaying the picture. The drawback is that an interlaced source is de-interlaced then interlaced again to coop with PAL standard. My PS3 is connected to a 720p display, so this should not be a problem... if it's not a problem for CPU usage... You are a lucky guy ;-) Is your TV able to upscale SD content or do you plan to do the up-scaling job in software? I did put this project on hold until better fb or xv support is popping up ;-) May be you will also be interested to have a look here: http://forums.ps2dev.org/viewtopic.php?t=8364postdays=0postorder=ascst art=0 thanks for all the informations!! You're welcome. Ciao, Graziano ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Le mardi 13 novembre 2007 à 14:50 +, Darren Salt a écrit : - it doesn't require me to recompile libxine Neither does vdr-xine (if you're using xine-lib-1.2). affirmative! I am running xine-lib-1.2 and vdr-xine 0.8.0 at last no more messing with patching xine-lib My problems: - something is turning down PCM volume on startup (not xine because when I run xine alone the volume isn't changed) - I have strange xine lockups which I think may be related to the version of the openchrome driver I am running - they are window manager related such as switching from one desktop to another when live TV is running and moving TV windows around Cheers Tony -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Luca Olivetti schrieb: En/na Graziano Pavone ha escrit: I'm currently using xineliboutput for my other client (on a standard PC), so this would be my first choice, but I've no problem to switch back to vdr-xine (which I used in the past - with the network patch... I moved to xineliboutput just because I don't want to patch xine-lib everytime anymore..) A nice feature that vdr-xine has over xineliboutput, is that it automatically sets itself as the primary device when a connection comes, and when the connection is closed it restores the previous primary device. This way I can either watch locally with the dxr3-plugin or remotely with vdr-xine. I experienced the same with xineliboutput. A very interesing feature of xinelibout is the ability to control deinterlacing, color settings etc. from within the VDR OSD in the plug-in´s settings. Furthermore, xineliboutput has a function that cuts and scales letterboxed 16:3 to anamorph 16:9, there is an audio equalizer and much more... With kind regards Jörg Knitter ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Darren Salt [EMAIL PROTECTED] writes: - it doesn't require me to recompile libxine Neither does vdr-xine (if you're using xine-lib-1.2). oh, good to know, i'll give it a try then. Cheers -- ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Hi, Graziano Pavone schrieb: 2007/11/13, Luca Olivetti [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Note that 0.8.0 has network support built-in. I know but you still have to patch and recompile xine-lib... Are there any problems in submitting the needed patch to the mainstream xine-lib distribution? The problem is that small parts of the patch would break binary compatibility in xine-lib-1.1.x. This is no problem if a distribution decides to include the patch and recompiles all applications which use xine-lib-1.1.x. I still do provide those patches as not all people are willing to switch to xine-lib-1.2 (hg) which is still in development, contains the patches and therefore works out of the box. A nice feature that vdr-xine has over xineliboutput, is that it automatically sets itself as the primary device when a connection comes, and when the connection is closed it restores the previous primary device. This way I can either watch locally with the dxr3-plugin or remotely with vdr-xine. I only have Skystar2/Airstai2 budget cards, so it's not an issue for me. A feature that allows to watch different channels on clients at the same time (without using multiple vdr installations and streamdev) would definetely make me switch back to vdr-xine :) And you wouldn't mind applying a huge patch on VDR to achieve this goal? 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] [ANNOUNCE] vdr-xine-0.8.0 plugin
On Oct 24, 2007 8:00 AM, Reinhard Nissl [EMAIL PROTECTED] wrote: Hi, I'm pleased to announce the long awaited release 0.8.0, which integrates the vdr-xine-network patch. You can find it on my homepage: http://home.vr-web.de/~rnissl Hi Reinhard, I've used vdr-xine, and I've used xinelibout for vdr. I've just ogt a general question, as they both seem to have similar functionality (or at least they both satisfy my need for a software client head to vdr. What's the driver for vdr-xine? I've heard people say xinelibout is better because it is more stable. But, whats the reality? Mike ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Hi, Luca Olivetti schrieb: Is it possible that newer version generate more traffic/are more sensible to network latencies? Yes, at least in the buffer monitoring phase, which was introduced with 0.7.7. Try to set it to 0 in vdr-xine's setup menu. I'll need some time to provide a proper fix for this issue. 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] [ANNOUNCE] vdr-xine-0.8.0 plugin
En/na Reinhard Nissl ha escrit: Hi, Luca Olivetti schrieb: Is it possible that newer version generate more traffic/are more sensible to network latencies? Yes, at least in the buffer monitoring phase, which was introduced with 0.7.7. Try to set it to 0 in vdr-xine's setup menu. That was it! Thank you. Incidentally, that was the only parameter I didn't touch ;-) Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
En/na Luca Olivetti ha escrit: En/na Reinhard Nissl ha escrit: Hi, I'm pleased to announce the long awaited release 0.8.0, which integrates the vdr-xine-network patch. You can find it on my homepage: I finally upgraded to this version (from 0.7.6 + network patches, I think I tried some other version but with similar problems as this one), but using it from the network (I cannot try it locally, so I don't know if it applies), live tv stutters (i.e. plays smooth for around a second, stops or slows down for a moment, plays for a second, stops, and so on). Recordings are not affected by this problem (or so it seems). The same version of xine (20070829224000, downloaded from your page, with the patches in vd-xine) on the client against streamdev-server plays smoothly. Mmmh, I usually use wifi, now I tried with a wired connection and it seems to work fine. 0.7.6 worked fine with wifi though (even with marginal reception, with at least 5Mbps available as reported by kwifimonitor), and where I usually need it there's no wired connection available. Is it possible that newer version generate more traffic/are more sensible to network latencies? Bye -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
En/na Reinhard Nissl ha escrit: Hi, I'm pleased to announce the long awaited release 0.8.0, which integrates the vdr-xine-network patch. You can find it on my homepage: I finally upgraded to this version (from 0.7.6 + network patches, I think I tried some other version but with similar problems as this one), but using it from the network (I cannot try it locally, so I don't know if it applies), live tv stutters (i.e. plays smooth for around a second, stops or slows down for a moment, plays for a second, stops, and so on). Recordings are not affected by this problem (or so it seems). The same version of xine (20070829224000, downloaded from your page, with the patches in vd-xine) on the client against streamdev-server plays smoothly. -- Luca ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] [ANNOUNCE] vdr-xine-0.8.0 plugin
Hi, I'm pleased to announce the long awaited release 0.8.0, which integrates the vdr-xine-network patch. You can find it on my homepage: http://home.vr-web.de/~rnissl Excerpt from HISTORY: 2007-10-24: Version 0.8.0 - Frame duration was not set correctly in xine-lib for H.264 frames, causing frame drops an non fluent playback. - Added network patch (thanks to Tobias Grimm for supplying it). Although I had planned to optimize it to just use one port and only two sockets, I decided to release it in its current state instead of waiting further years. I've just modified it to use a more xine-like MRL netvdr://host:port#demux:mpeg_pes where port is optional (defaults to 18701). The fifo MRL should now be written vdr://tmp/vdr-xine/stream#demux:mpeg_pes, although a single slash will still work, too. - Updated et_EE.po (thanks to Arthur Konovalov for supplying the file). - Fixed a bug in vdr-xine's buffer handling for live TV mode which got most noticeable when switching back from a H.264 channel to a MPEG2 channel, especially when the machine was not capable of playing the H.264 stream in real time. As the buffer was not cleared when switching channels, old H.264 data was sent to xine instead of new MPEG2 data, which caused xine to incorrectly switch to H.264 mode. This behavior could lead to a crash in FFmpeg later. - Fixed OSD handling in vdr-xine as certain subtitles could cause a memory corruption in xine (thanks to Arthur Konovalov for providing sample recordings). Enjoy. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl mailto:[EMAIL PROTECTED] ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
