Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
On Fri, 21 Mar 2008 12:00:02 +0100 Niko Mikkila <[EMAIL PROTECTED]> wrote: > All XvMC implementations that I know of have poor deinterlacing, which > makes them pretty useless for decoding interlaced video. Your > description suggests that openchrome just drops the other field, so > you lose half of both the vertical resolution and temporal definition > (50 fields/s -> 25 frames/s). Continuous small skips (at regular or > seemingly random intervals) could also be caused by a refresh-rate > mismatch, but if Xv is ok, this is not the main problem in your case. Hmm, it seems that I've not understood something... I assumed that if I don't say anything about deinterlacing, then the (s-video) output would be interlaced. This apparently isn't true, they do something (strange) to the video, because putting deinterlacing on (bob-deinterlacing) produces quite nice results! (well, 40-50% CPU usage, and a little-bit of jerking, 1/s, but the ticker is very sharp now). But shouldn't the device be able to send completely non-deinterlaced stuff to the tv-out? Maybe the unichrome chip does something, but can that something be turned off? Anyway, thanks for the info, it led me to a bit more tolerable results :-) -- Best Regards, Timo [EMAIL PROTECTED] FABRICATI DIEM, PVNK. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
On Wed, 19 Mar 2008 00:00:15 +0200 Timo Laitinen <[EMAIL PROTECTED]> wrote: > > > although not perfectly (rapid motion, such as news tickers, are > > > jumpy with xxmc on openchrome when HW acceleration is on, not sure > > > why) > > > > Sounds like an X problem to me, though it could just possibly be to > > do with xine-lib's xxmc support. > > Yes, could be an X (openchrome) problem, could be xxmc or the HW > decoding, I'm a bit at loss with it at the moment. With Xv the quality > is just fine (but CPU at around 60-70%, a bit too touchy for other > activity). The xxmc is somewhat blurry and jumping a bit with the > tickers, with CPU at 30%. Any similar experience/solutions anyone? The > hardware is CN700 (EPIA EN-12000). All XvMC implementations that I know of have poor deinterlacing, which makes them pretty useless for decoding interlaced video. Your description suggests that openchrome just drops the other field, so you lose half of both the vertical resolution and temporal definition (50 fields/s -> 25 frames/s). Continuous small skips (at regular or seemingly random intervals) could also be caused by a refresh-rate mismatch, but if Xv is ok, this is not the main problem in your case. Regards, Niko Mikkilä ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
On Mon, 17 Mar 2008 22:41:15 +0100 Darren Salt <[EMAIL PROTECTED]> wrote: > I demand that Timo Laitinen may or may not have written... > > > Aaargh, forgot to change the vdr Digest from the subject to > > something reasonable... sorry about the noise... Here's the same > > with a bit more identifiable subject. > > You forgot to correct the In-Reply-To header. ;-) ... > > I'm inclined to believe the latter: you keep forgetting. :-) Well, I'd put the header problem somewhere between "didn't even think of it" and "can't do it with my emailer" (at least after a quick check and a couple of attempts), sorry... > > although not perfectly (rapid motion, such as news tickers, are > > jumpy with xxmc on openchrome when HW acceleration is on, not sure > > why) > > Sounds like an X problem to me, though it could just possibly be to > do with xine-lib's xxmc support. Yes, could be an X (openchrome) problem, could be xxmc or the HW decoding, I'm a bit at loss with it at the moment. With Xv the quality is just fine (but CPU at around 60-70%, a bit too touchy for other activity). The xxmc is somewhat blurry and jumping a bit with the tickers, with CPU at 30%. Any similar experience/solutions anyone? The hardware is CN700 (EPIA EN-12000). Well, maybe I should actually start another thread on this (with proper headers on the replys :-) ), or maybe at openchrome or xine... > > So (wrote he hoping), would things get better (regarding my quality > > problems) if I changed to 1.1.2? > > Hopefully not ? unless you mean 1.2, in which case you'll see much > the same as 1.1 hg wrt xxmc. I was (not really that optimistically) thinking that maybe the <<1.1.3 meant something horrible happens at higher versions... but I wasn't really expecting a positive answer on that. And it does seem that not much has happened with xine xxmc recently. > Basically, if you upgrade xine-lib to a newer ABI-compatible version, > you won't need to rebuild plugins (except just the once to get them > using the new plugin directory naming scheme when you upgrade past > 1.1.10.1). Ok, thanks for the info, maybe I'll try a newer version at some stage... -- Best Regards, Timo [EMAIL PROTECTED] FABRICATI DIEM, PVNK. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
I demand that Timo Laitinen may or may not have written... > Aaargh, forgot to change the vdr Digest from the subject to something > reasonable... sorry about the noise... Here's the same with a bit more > identifiable subject. You forgot to correct the In-Reply-To header. ;-) > On Mon, 17 Mar 2008 12:00:02 +0100 > Darren Salt <[EMAIL PROTECTED]> wrote: >> I demand that Timo Laitinen may or may not have written... >> [snip] >>> Just tackled with this one myself... at least if you used the e-tobi >>> repositories. There was a strange requirement for the library version, I >>> think it was something like libxine => 1.1.12 libxine << 1.1.13. >> Highly unlikely. > ... >>> Compilation went well with libxine 1.1.17 and the plugin and the >>> frontends work fine. >> 1.1.17? Did you get that from... I don't know, probably late next year? >> :-) > Oops, it seems my time machine had a programming glitch... Or, > alternatively, I still haven't learned NOT to trust my memory... I'm inclined to believe the latter: you keep forgetting. :-) > So, actually looking at it, it had Build-Depends > libxine-dev (<< 1.1.3), libxine-dev (>= 1.1.2) The specific versioning shouldn't be there. That sort of thing only belongs in the Depends header, and should be generated at build time. > I removed all version requirements, compiled it against libxine 1.1.7. (in > Ubuntu Gutsy) But, still, it works, :-) > although not perfectly (rapid motion, such as news tickers, are jumpy with > xxmc on openchrome when HW acceleration is on, not sure why) Sounds like an X problem to me, though it could just possibly be to do with xine-lib's xxmc support. >> That *is* the general form, though, and it's to do with the name of >> xine-lib's plugins directory and how the plugin build scripts get the >> directory name. > So (wrote he hoping), would things get better (regarding my quality > problems) if I changed to 1.1.2? Hopefully not ‒ unless you mean 1.2, in which case you'll see much the same as 1.1 hg wrt xxmc. > or to 1.1.11? Or is it just so that if it works at all, it's ok? Basically, if you upgrade xine-lib to a newer ABI-compatible version, you won't need to rebuild plugins (except just the once to get them using the new plugin directory naming scheme when you upgrade past 1.1.10.1). -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Use more efficient products. Use less. BE MORE ENERGY EFFICIENT. You can never tell which way the train went by looking at the tracks. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
Aaargh, forgot to change the vdr Digest from the subject to something reasonable... sorry about the noise... Here's the same with a bit more identifiable subject. br, Timo --- On Mon, 17 Mar 2008 12:00:02 +0100 Darren Salt <[EMAIL PROTECTED]> wrote: > > I demand that Timo Laitinen may or may not have written... > > [snip] > > Just tackled with this one myself... at least if you used the e-tobi > > repositories. There was a strange requirement for the library > > version, I think it was something like libxine => 1.1.12 libxine << > > 1.1.13. > > Highly unlikely. ... > > Compilation went well with libxine 1.1.17 and the plugin and the > > frontends work fine. > > 1.1.17? Did you get that from... I don't know, probably late next > year? :-) > Oops, it seems my time machine had a programming glitch... Or, alternatively, I still haven't learned NOT to trust my memory... So, actually looking at it, it had Build-Depends libxine-dev (<< 1.1.3), libxine-dev (>= 1.1.2) , I removed all version requirements, compiled it against libxine 1.1.7. (in Ubuntu Gutsy) But, still, it works, although not perfectly (rapid motion, such as news tickers, are jumpy with xxmc on openchrome when HW acceleration is on, not sure why) > That *is* the general form, though, and it's to do with the name of > xine-lib's plugins directory and how the plugin build scripts get the > directory name. So (wrote he hoping), would things get better (regarding my quality problems) if I changed to 1.1.2? or to 1.1.11? Or is it just so that if it works at all, it's ok? -- Best Regards, Timo [EMAIL PROTECTED] FABRICATI DIEM, PVNK. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
I demand that Timo Laitinen may or may not have written... [snip] > Just tackled with this one myself... at least if you used the e-tobi > repositories. There was a strange requirement for the library version, I > think it was something like libxine => 1.1.12 libxine << 1.1.13. Highly unlikely. That *is* the general form, though, and it's to do with the name of xine-lib's plugins directory and how the plugin build scripts get the directory name. As of 1.1.11, though, things will start getting better in this respect since the naming of the directory will use the same information that libtool uses for generating the library soname, and directories for older versions (which match the same soname major number) will be looked in. It's not *perfect* (that would involve use of details of which exported symbols were added when to decide exactly where the plugin should go), but it's a lot better than having to rebuild just because of a newer xine-lib :-) [snip] > Compilation went well with libxine 1.1.17 and the plugin and the frontends > work fine. 1.1.17? Did you get that from... I don't know, probably late next year? :-) -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + Output *more* particulate pollutants. BUFFER AGAINST GLOBAL WARMING. In charity there is no excess. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] xineliboutput and ubuntu 7.10 (Gutsy)
> I have installed 1.5.17 (i think) of vdr (from the experimental apt > repository) however I can't get xineliboutput compiled as it's > complaining that it can't find a valid libxine. It looks like the > dependencies are quite specific in what they want. Hi, Just tackled with this one myself... at least if you used the e-tobi repositories. There was a strange requirement for the library version, I think it was something like libxine => 1.1.12 libxine << 1.1.13. If anyone knows what is so terribly wrong with later libxine, please let me know... What I did, was I just edited out the latter requirement from the debian/control file, and a couple of others (can't remember what they were, but there were about 4-5 files in the debian directory with the requirement setting). Compilation went well with libxine 1.1.17 and the plugin and the frontends work fine. -- Best Regards, Timo [EMAIL PROTECTED] FABRICATI DIEM, PVNK. ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] xineliboutput and ubuntu 7.10 (Gutsy)
I have installed 1.5.17 (i think) of vdr (from the experimental apt repository) however I can't get xineliboutput compiled as it's complaining that it can't find a valid libxine. It looks like the dependencies are quite specific in what they want. Will try to provide more info tomorrow when I'm at work and can check better, but has anyone else resolved this? -- Latest news on http://www.streetcredo.org.uk/rob Rob Davis ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
