ffmpeg 0.5 and xine-lib 1.1.16.3
ffmpeg 0.5 and xine-lib 1.1.16.3
Hmmm ...
These pets were built on my Puppy 4.1 daemon and may need to be installed
together. Provided for your convenience. I do not intend to maintain this
unless I borked something up. Tested over a fresh Puppy 4.1 and seems to
work fine for me.
1. ffmpeg 0.5 stable release
[download]
Description: ffmpeg 0.5 "Bike Shed" March 3, 2009 official release.
If you install this pet and uses xine-lib shared apps, you will have
to update xine-lib or some codecs will not work properly, ex: avc1.
configure notes:
--prefix=/usr --disable-debug --enable-shared --enable-gpl
--enable-libmp3lame --enable-libvorbis --enable-pthreads
--enable-postproc --enable-swscale
2. xine-lib-1.1.16.3 release
[full download]
[english download]
Description: xine-lib 1.1.16.3 release
Shared xine-lib compiled against ffmpeg 0.5
configure notes:
configure --prefix=/usr --with-external-ffmpeg --disable-gnomevfs
3. gxine 0.5.901
[download]
Description: Not a required install. Existing versions will work just fine.
This version of gxine was compiled against xine-lib 1.1.16.3. There's
already one listed on puppy package manager. I'm using this since the
fullscreen mode works for me with the patched jwm.
configure notes:
configure --prefix=/usr --disable-mozjs --disable-ffjs --without-hal
--without-dbus
And before someone asks, I should mentioned that libamr (for 3gp) is not
compiled in as it is deemed non-gpl'ed.
Rgds
These pets were built on my Puppy 4.1 daemon and may need to be installed
together. Provided for your convenience. I do not intend to maintain this
unless I borked something up. Tested over a fresh Puppy 4.1 and seems to
work fine for me.
1. ffmpeg 0.5 stable release
[download]
Description: ffmpeg 0.5 "Bike Shed" March 3, 2009 official release.
If you install this pet and uses xine-lib shared apps, you will have
to update xine-lib or some codecs will not work properly, ex: avc1.
configure notes:
--prefix=/usr --disable-debug --enable-shared --enable-gpl
--enable-libmp3lame --enable-libvorbis --enable-pthreads
--enable-postproc --enable-swscale
2. xine-lib-1.1.16.3 release
[full download]
[english download]
Description: xine-lib 1.1.16.3 release
Shared xine-lib compiled against ffmpeg 0.5
configure notes:
configure --prefix=/usr --with-external-ffmpeg --disable-gnomevfs
3. gxine 0.5.901
[download]
Description: Not a required install. Existing versions will work just fine.
This version of gxine was compiled against xine-lib 1.1.16.3. There's
already one listed on puppy package manager. I'm using this since the
fullscreen mode works for me with the patched jwm.
configure notes:
configure --prefix=/usr --disable-mozjs --disable-ffjs --without-hal
--without-dbus
And before someone asks, I should mentioned that libamr (for 3gp) is not
compiled in as it is deemed non-gpl'ed.
Rgds
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Thats excellent Patriot does ffmpeg/xinelibs come with the dev files?
Thanks again
ttuuxxx
Thanks again
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
Thanks for this Patriot.
Can anyone tell me how to compile against it properly? Unlike the older versions it has a subfolder of header files for each ffmpeg library. When I try to compile something (dvdstyler) against it, it fails because it can't find the header files. I tried just moving them all out of their subfolders, and it compiled OK, but then the executable ended up dependent on the .so.51 libraries as well as the .so.52 libraries... except it actually wanted the .so.52 libraries for both... I don't know
Wait... maybe I just need to delete the header files from puppy's inbuilt ffmpeg first. I'll try that when I get a chance.
Can anyone tell me how to compile against it properly? Unlike the older versions it has a subfolder of header files for each ffmpeg library. When I try to compile something (dvdstyler) against it, it fails because it can't find the header files. I tried just moving them all out of their subfolders, and it compiled OK, but then the executable ended up dependent on the .so.51 libraries as well as the .so.52 libraries... except it actually wanted the .so.52 libraries for both... I don't know
Wait... maybe I just need to delete the header files from puppy's inbuilt ffmpeg first. I'll try that when I get a chance.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
yes delete puppies original headers first (maybe move them offsite for safe keeping, just for a backup)disciple wrote:
Wait... maybe I just need to delete the header files from puppy's inbuilt ffmpeg first. I'll try that when I get a chance.
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
But do you know how I'm supposed to tell it to look in those subfolders for all the headers? Or do you think it would know, and just got confused by something in the old headers?
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
- ttuuxxx
- Posts: 11171
- Joined: Sat 05 May 2007, 10:00
- Location: Ontario Canada,Sydney Australia
- Contact:
Well if the new package you are using had them in the default locations, all should be well, make sure there isn't any leftovers in /usr/lib/pkgconfig from the previous version and also delete the old la,so libsdisciple wrote:But do you know how I'm supposed to tell it to look in those subfolders for all the headers? Or do you think it would know, and just got confused by something in the old headers?
ttuuxxx
http://audio.online-convert.com/ <-- excellent site
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
http://samples.mplayerhq.hu/A-codecs/ <-- Codec Test Files
http://html5games.com/ <-- excellent HTML5 games :)
- technosaurus
- Posts: 4853
- Joined: Mon 19 May 2008, 01:24
- Location: Blue Springs, MO
- Contact:
the code name "bike shed" reminded me of an old issue in software development.... It refers to having the biggest debates over the smallest issues.
Start at http://www.bikeshed.com and follow the rabbit hole back to the original discussions.
I wish I had remembered it when Warren was doing 4.2. It may have helped put things into perspective.
Start at http://www.bikeshed.com and follow the rabbit hole back to the original discussions.
I wish I had remembered it when Warren was doing 4.2. It may have helped put things into perspective.
Check out my [url=https://github.com/technosaurus]github repositories[/url]. I may eventually get around to updating my [url=http://bashismal.blogspot.com]blogspot[/url].
Hmmm .....
It's been a while since I did this and I've been using them since I made the binaries. Currently, on puppy 4.12 with ffmpeg 0.5 + xine-lib 1.16.3 + stock gxine 0.5.9 ... Didn't quite like the tray feature in newer gxine ...
The dependencies between gxine and ffmpeg is through xine-lib. If only ffmpeg is updated, it will bork certain xine-lib's functions and further affects certain gxine functions. The best is to have matching binaries, ffmpeg -> xine-lib -> gxine. That's why I've provided the pets as such ...
To be clear, they were made to fulfill my requirements and I have encountered zero problems with it. If they do not fulfill yours, then the sources are freely available .....
To advanced users/developers:
If you're having issues with ffmpeg headers (like your compiled apps got confused with the headers), look for /usr/lib/ffmpeg (typo correction: should be /usr/include/ffmpeg). If its there, then its the older ffmpeg headers. Some apps looked in there and then skip checking for newer ones. New ffmpeg have changed the folders (from what I've seen). Remove that folder (or make a backup) and try compiling your apps again ...
To others:
I'm interested to know what kind of realmedia / flv files borks gxine. My rm+ra+rmvb and flv files all plays just fine ... If you have a problematic sample media, please open another thread and point me to it ...
Rgds
._.
It's been a while since I did this and I've been using them since I made the binaries. Currently, on puppy 4.12 with ffmpeg 0.5 + xine-lib 1.16.3 + stock gxine 0.5.9 ... Didn't quite like the tray feature in newer gxine ...
The dependencies between gxine and ffmpeg is through xine-lib. If only ffmpeg is updated, it will bork certain xine-lib's functions and further affects certain gxine functions. The best is to have matching binaries, ffmpeg -> xine-lib -> gxine. That's why I've provided the pets as such ...
To be clear, they were made to fulfill my requirements and I have encountered zero problems with it. If they do not fulfill yours, then the sources are freely available .....
To advanced users/developers:
If you're having issues with ffmpeg headers (like your compiled apps got confused with the headers), look for /usr/lib/ffmpeg (typo correction: should be /usr/include/ffmpeg). If its there, then its the older ffmpeg headers. Some apps looked in there and then skip checking for newer ones. New ffmpeg have changed the folders (from what I've seen). Remove that folder (or make a backup) and try compiling your apps again ...
To others:
I'm interested to know what kind of realmedia / flv files borks gxine. My rm+ra+rmvb and flv files all plays just fine ... If you have a problematic sample media, please open another thread and point me to it ...
Rgds
._.
Last edited by Patriot on Wed 02 Sep 2009, 12:56, edited 1 time in total.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
I went through the exercise of testing ffmpeg 0.5 and latest xine-lib awhile back. However got very patchy results testing my collection of video and audio files.
You need a collection of files to test on, a representative selection of what users will have. Such as .flv, .avi, .rm, .wmv, .ram, etc.
My old ffmpeg is the only one that plays them all nicely.
Hmmm, maybe I should upload my test suite.
You need a collection of files to test on, a representative selection of what users will have. Such as .flv, .avi, .rm, .wmv, .ram, etc.
My old ffmpeg is the only one that plays them all nicely.
Hmmm, maybe I should upload my test suite.
[url]https://bkhome.org/news/[/url]
I came across this problem myself using ffmpeg, and also using the GIMP and cinepaint under "dingo". You see I prefer portable versions of these utilities and therefore prefered to put the libraries in a subdirectory rather than ubdate /lib or /usr/lib. The way I tried this was to create a script that updated LD_LIBRARY_PATH to include the "LIB" subdirectory.
disciple
But do you know how I'm supposed to tell it to look in those subfolders for all the headers? Or do you think it would know, and just got confused by something in the old headers?
Suppose you have a directory ./ffmpeg and have copied the so files to
./ffmpeg/lib then you can have a script to run ffmpeg executable:
Code: Select all
#!/bin/sh
MYDIR=`basename $0`
cd $MYDIR
export LD_LIBRARY_PATH="$LD_LIBRARY_PATH:$MYDIR/lib"
./ffmpeg "$@"
For the record, all I had to do was delete /usr/include/ffmpeg, then it automatically found the new headers.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Also, just in case anyone else tries including this in an .sfs addon - any files that are also in the livecd will not work - the ones from the livecd will show up. This includes the pkgconfig files and symlinks like libavcodec.so, so you'll actually need a .pet or whatever anyway, to provide these files. And if you create them manually you have to run ldconfig afterwards.
Do you know a good gtkdialog program? Please post a link here
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Classic Puppy quotes
ROOT FOREVER
GTK2 FOREVER
Hi
I installed these packages (only 1 & 2 because 3 is not must).
Before the installation i could use ffmpeg apart from mp4 to mp3 conversation.
After the installation when i launch ffmpeg a got this message:
ffmpeg: relocation error: /usr/lib/libavdevice.so.52: symbol snd_pcm_htimestamp, version ALSA_0.9 not defined in file libasound.so.2 with link time reference
I use puppy 4.00 full install.
Could you help me please?
Have you got any idea what is the issue what i have to do?
Thank you
Jani
I installed these packages (only 1 & 2 because 3 is not must).
Before the installation i could use ffmpeg apart from mp4 to mp3 conversation.
After the installation when i launch ffmpeg a got this message:
ffmpeg: relocation error: /usr/lib/libavdevice.so.52: symbol snd_pcm_htimestamp, version ALSA_0.9 not defined in file libasound.so.2 with link time reference
I use puppy 4.00 full install.
Could you help me please?
Have you got any idea what is the issue what i have to do?
Thank you
Jani
Hmmm .....
@jani
It seems that there's an ALSA dependencies that is not met with in puppy 4.0 ..... I believe that puppy 4.0 is using kernel 2.6.21.7 but with an older alsa-1.0.15 ... To resolve this, you will need to upgrade alsa to at least version 1.0.16 (the one used in puppy 4.12) or the latest 1.0.21 ...
I don't remember off hand but puppy 4.00 kernel could be configured differently and my alsa driver upgrade pet would not work properly ... If you need any help with alsa upgrade, please pm me .....
Rgds
@jani
It seems that there's an ALSA dependencies that is not met with in puppy 4.0 ..... I believe that puppy 4.0 is using kernel 2.6.21.7 but with an older alsa-1.0.15 ... To resolve this, you will need to upgrade alsa to at least version 1.0.16 (the one used in puppy 4.12) or the latest 1.0.21 ...
I don't remember off hand but puppy 4.00 kernel could be configured differently and my alsa driver upgrade pet would not work properly ... If you need any help with alsa upgrade, please pm me .....
Rgds
Hi Patriot.
You are right my kernel is 2.6.21.7.
But i don't know my ALSA version. I don't know how can i check it.
(you know i am not a linux expert just an open mind user; may be the the version of alsamixer? it is 1.0.14)
Could you help me how can i upgrade the ALSA libs/progs? to the proper version?
Thank you
Jani
You are right my kernel is 2.6.21.7.
But i don't know my ALSA version. I don't know how can i check it.
(you know i am not a linux expert just an open mind user; may be the the version of alsamixer? it is 1.0.14)
Could you help me how can i upgrade the ALSA libs/progs? to the proper version?
Thank you
Jani
Hmmm .....
I've made some checks and finally found a suitable symvers to use ... Please go to my alsa-1020 thread here and get the alsa-3in1-k26217-pre-1020 pet package made specifically for puppy 4.00 and puppy 3.01 ...
After installing the alsa upgrade, open a terminal and use alsaconf to reconfigure your soundcard ... I would suggest that you boot using a LiveCD with pfix=ram to try it out first ...
Rgds
I've made some checks and finally found a suitable symvers to use ... Please go to my alsa-1020 thread here and get the alsa-3in1-k26217-pre-1020 pet package made specifically for puppy 4.00 and puppy 3.01 ...
After installing the alsa upgrade, open a terminal and use alsaconf to reconfigure your soundcard ... I would suggest that you boot using a LiveCD with pfix=ram to try it out first ...
Rgds