| |
| |
| |
|
Page: 1 2
Comments:
<0> hello all
<1> hi
<0> xine is gpl right? does that exlude it for use in embedded systems then? ie - if i want to use xinelib?
<1> well it does not "exclude" it
<1> as long as you provide the sources of what you link xine-lib with, under a gpl compatible license, you should be fine
<1> or was it just gpl? hm not sure ianal
<0> hrm
<0> so basically everything has to be gpl'd
<2> GPL-compatible, I think...
<0> thats a bit of a pain for us :/....might have to look at another route...its just that xine has a IDirectFBVideoProvider cl*** apparantly
<0> we are currently using mplayer, and writing data to shared memory where we pick it up and work with it
<0> could have avoided that if i could use xine, bt ti think that the gpl bit makes this hard
<1> jkp, "basically everything", just the linked stuff, everything that it's used "at an arm length", as in, executed rather than linked, is not needed
<0> hm
<0> this is a hard one
<0> our main binary is compiled python
<0> but its going to call into directfb, via a module we have written that wraps it
<0> now, in theory, i wont have to "link" into xine directly, rather access it via a python module
<0> but i think that equates to the same pretty much
<0> so that leaves us back ad the shm model
<1> python module is considered a link, as it does not runw ithout it
<1> *run without
<0> yup
<0> shm it is then
<0> thats what we do with mplayer and it works ok, just lots of memcpying :)
<3> I thought GPL == if you modify the GPL'ed code it has to be give out, and you have to provide source for the GPL stuff you do use. If you link with xine-lib and have to give it out, doesn't that mean any proprietary application on Linux has to be given out since it would link with glibc, kernel, etc?
<1> glibc is not GPL, it's LGPL, and that makes a difference (that's why nothing links it statically of proprietary applications)
<1> kernel is not linked against apps, only against kernel modules, and those are usually not distributed at all (nvidia builds the module on users' machines)
<3> So any time you link with a GPL'd library or program, you have to give your source away?
<1> you can link a GPL program with a proprietary library if you add a clause to the GPL for that program
<1> if the program does not add that clause, you cannot redistribute the program linked to that library
<1> if you create a proprietary program and link it to a GPL library (like xine-lib), you have to release the sources of the program if you distribute the binary
<3> Wow
<1> if you just use it internally (custom-made software) you don't need to
<1> but as soon as you distribute the binary, GPL enters the scene
<3> That is nasty :/
<1> readline for instance is GPL
<3> What is readline?
<1> a GNU library used for commandline editing, it's what bash uses for instance
<3> mplayer is also GPL?
<1> iirc
<3> Let me ask an unrelated question -- I use kaffeine player which uses xine-lib. I want to play files over kio_slaves (i.e. smb://) but xine-lib (obviously) doesn't support that. Can xine-lib read from a socket or would it be best to create a temp file and have it fetching in the background while xine-lib reads from it?
<1> kaffeine should take care of the kioslaves bridge
<3> Right, but it doesn't. So if I wanted to add that functionality, what might be the most intelligent way to interface with xine-lib ?
<1> err what you mean it doesn't?
<1> i'm pretty sure kaffeine has the kioslave bridge in current versions
<3> I compiled 0.8.0 and I tried to play from smb:// and I got an error that xine-lib didn't understand smb://
<1> hrm might be kaffeine trying to be smart and thinking xine is able to access smb:// by itself (it used to be, currently it's broken)
<3> Oh xine-lib used to be able to do that?
<3> I also tried with ftp://
<3> And that did not work :
<3> :/
<4> hmm
<4> xine for some reason doesnt load the codecs after i give it the path and restart it
<2> !hello is hello
<5> The operation succeeded.
<2> hello
<2> !hello
<5> hello is hello, _ds
<2> !xine
<5> No idea.
<2> !xine is version 1.1.2
<5> OK.
<2> !xine-ui is version 0.99.4
<5> OK.
<2> !gxine is version 0.5.7
<5> OK.
<4> !xine is version 0.0.0
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> !xine is version 0.0.0
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> !xine ver
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> !xine help
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> wtf!
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> !xine quit
<5> p0t_: Whoops, something went wrong - tell _ds!
<4> **** this
<5> p0t_: Whoops, something went wrong - tell _ds!
<6> hi doods
<5> Hoxzer: Whoops, something went wrong - tell _ds!
<6> !tell _ds
<5> Hoxzer: Whoops, something went wrong - tell _ds!
<6> tell _ds
<5> Hoxzer: Whoops, something went wrong - tell _ds!
<6> k
<5> Hoxzer: Whoops, something went wrong - tell _ds!
<1> hrm, i have the little impression that ds didn't set it up correctly
<5> Flameeyes: Whoops, something went wrong - tell _ds!
<1> xinebot, shut the hell up
<5> Flameeyes: Whoops, something went wrong - tell _ds!
<1> like this
<5> Flameeyes: Whoops, something went wrong - tell _ds!
<2> test...
<2> 'Bot setup in progress. Needs testing - somebody say something :-)
<1> something
<5> Flameeyes: Whoops, something went wrong - tell _ds!
<2> Hmm. :-|
<2> Test again...
<1> something else
<1> oh wow now it works :P
<2> And the reason's a bit odd...
<2> It was complaining about "doUnknown" and throwing a backtrce.
<2> So I added "doUnknown" as a default capability.
<2> Right... let's see if other things are working properly.
<2> !xine
<5> xine is version 1.1.2, _ds
<2> Anything useful to teach it?
<2> !xine-lib is version 1.1.2
<5> OK.
<2> !xine-ui
<5> Somebody said xine-ui is version 0.99.4, _ds
<2> !forget xine
<5> OK.
<2> !xine is use xine-lib, xine-ui and gxine to be told the current versions
<5> OK.
<1> _ds, i'm not sure what to do about the textrel patch... it's an important fix, but someone said there are problems with win32codecs (on xine-devel), still since i merged it in gentoo i had no bug at all about w32codecs
<2> Also unsure... probably needs to be brought up on -devel.
<1> i think i asked what the problem is but i don't have any reply, will try to re-ask later
<1> that basically is the last patch, and it's currently applied in gentoo and pardus... no user reported issues in gentoo, and i suppose i would have knew if cartman had troubles in pardus
<1> oh i'll drop polyp driver sometime later, probably pointless to leave there anyway, especially considering distros are moving to pulseaudio 0.9, and the pulse plugin "somewhat" works.. i'll also refine pulse plugin, but for that probably i need to close my currenct contract
<2> Fine... just don't kill it until well after the release of etch :-)
<1> err you mean not before next year? :P
<1> actually it's polyp/pulse's author who asked me to kill it, as anyway that works only with polyp 0.7
<2> ... hmm, I can't seem to find any relevant packages...
<1> yeah it's not diffuse
<1> i've added it to gentoo just a couple of days ago, freebsd is still at 0.7 but no other support added
<1> it stood still for an year or so
<1> jcdutton, can you give me access to admin bugs on xine's sf.net project by chance? :)
<7> why does xine give errors sometimes when kaffeine goes to next track in playlist saying device is busy
<1> audio device unavailable? sometimes alsa device is left after a few moments after the stream stopped
<7> doesnt happen every time
<7> but its really annoying
<7> any way to stop it?
<1> make sure alsa backend uses non-exclusive access
<7> how would i do that
<1> depends on your alsa settings and your card
<7> ac97 i believe
<1> ac97 is the codec
<7> oh
<7> well its integrated sound
<2> No help. I have two ac97-capable devices here: one's the on-board nForce3-250 device, the other's an Audigy 4.
<7> oh
<2> Open a terminal, run "lspci"; you're looking for "multimedia audio controller".
<7> Intel Corporation 82801AA AC'97 Audio (rev 02)
<2> "cat /proc/asound/pcm" will provide more info.
<2> 01-00: Intel ICH : NVidia CK8S : playback 1 : capture 1
Return to
#xine
or
Go to some related
logs:
#web
#debian
#gentoo
gentoo fsck.vfat
linux disasembler
xorg XF86DGANoDirectVideoMode nvidia
pyton mysql debian module mysqldb
vmnet0 device not found
#gentoo
Gentoo laptop hwoto
|
|