LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   A Full-Featured Multimedia Slackware (https://www.linuxquestions.org/questions/slackware-14/a-full-featured-multimedia-slackware-692094/)

Woodsman 12-21-2008 03:24 PM

A Full-Featured Multimedia Slackware
 
I posted a short mini guide called A Full-Featured Multimedia Slackware. I would be grateful for comments and suggestions to improve the piece.

I am not much of a GTK/Xfce user and I could use help in that area.

A Full-Featured Multimedia Slackware

Thanks much!

ErV 12-21-2008 04:46 PM

Quote:

Originally Posted by Woodsman (Post 3383228)
I posted a short mini guide called A Full-Featured Multimedia Slackware. I would be grateful for comments and suggestions to improve the piece.

Mention of Kaffeine would be nice. To my experience it works very well when people just want to insert and play a dvd.

XavierP 12-21-2008 06:20 PM

Kaffeine is my favourite DVD player - supports the DVD menus which MPlayer and variants do not do.

Woodsman 12-21-2008 07:35 PM

Quote:

Mention of Kaffeine would be nice.
Quote:

Kaffeine is my favourite DVD player
Updated. Thanks!

vdemuth 12-22-2008 12:31 AM

Would be even better if all the references you make to the different software requirements were active hyperlinks. Still, a very good guide.

rc nai 12-22-2008 02:55 AM

I'm on xfce at the moment. I tried to find a good burner for xfce and I found xfburn. After a few hours of trying to make it work, I gave up. I failed to get it to read and burn audio files(.wav and .mp3) and it froze a lot on me. Killing the process id didn't work either and I had to restart the computer to get rid of it. And also most importantly, I couldn't get it do multisession data writing.

I finally came across X-CD-Roast and it got the job done. As far as I know, X-CD-Roast uses cdrtools such as cdrecord. It can write data, audio, capable of doing multisession recordings, and all other great stuff.

Oh yea and I forgot to mention...that's a really cool guide you have there. I know nothing about kde or k3b. I heard from rumors that you can use k3b on xfce 4.4.*. I haven't tried it yet, but when I do I'll be sure to check back at your guide. I'm bookmarking your page if you don't mind, hehe.

Woodsman 12-22-2008 02:35 PM

Quote:

Would be even better if all the references you make to the different software requirements were active hyperlinks.
I thought about that but wanted to keep the guide generic. Still, most people trying to build Slackware into a multimedia machine are likely to be new people rather than veteran Slackers. Links to the build scripts and complete packages might be a good idea, but the challenge there is the links change every Slackware release. Perhaps I'll add links to slackbuilds.org and slacky.eu. People who want complete packages can try the latter.

Quote:

I'm on xfce at the moment. I tried to find a good burner for xfce and I found xfburn . . . I finally came across X-CD-Roast and it got the job done.
The Zenwalk folks use Brasero. I don't know if that is a good selection, but Zenwalk is an Xfce-only Slackware derivative distro.

fcaraballo 12-22-2008 02:44 PM

Woodsman:

Nice guide. Just a few minor things with the digiKam part. imlib2 has not been a dependency of kipi-plugins for some time now and dcraw is not a dependency of digiKam or kipi-plugins, since libkdcraw includes its own version of dcraw. Also, sqlite is now included with digiKam itself. I would make reference somewhere that if users wish to compile against the sqlite included with Slackware 12.2, that they will need to add '--without-included-sqlite3' to their configure. The digiKam slackbuild at SBo uses this option by default.

rc nai:

xfburn just came out with version 0.4.0. They may have fixed the issues you have been having with it. Might be worth another look.

Frank

Woodsman 12-22-2008 07:39 PM

Quote:

Just a few minor things with the digiKam part. imlib2 has not been a dependency of kipi-plugins for some time now and dcraw is not a dependency of digiKam or kipi-plugins, since libkdcraw includes its own version of dcraw. Also, sqlite is now included with digiKam itself. I would make reference somewhere that if users wish to compile against the sqlite included with Slackware 12.2, that they will need to add '--without-included-sqlite3' to their configure. The digiKam slackbuild at SBo uses this option by default.
Updated. Thank you!

Woodsman 12-26-2008 01:26 AM

I want to thank everybody for your feedback. I hope the short guide helps others. Perhaps some day I'll add direct links to the build scripts or packages, but for now I think a decent foundation exists.

Thanks again!

DavidHindman 12-29-2008 09:27 AM

I never thought I'd see multimedia "just working right" on Slackware. It took an evening for me to find and install the "Basic Support" packages. The transcode SlackBuild for 12.2 didn't compile properly, so I used a version for 12.1 and it seems to work okay. Great writeup!

Woodsman 12-29-2008 02:25 PM

Hmm. I just updated transcode the other day in my 12.2 box and the package built without errors. On the other hand, I haven't built the multimedia support from scratch in a long time. Perhaps that would be a good way to test my guide. :)

DavidHindman 12-29-2008 03:28 PM

Woodsman, if it helps, this is part of the console output from the 12.2 slackbuild for transcode-1.0.7. The install was on a near virgin Slack 12.2.

And to answer the obvious question, I did install 12.2 packages in the recommended order (binary packages from slacky.eu when available, otherwise built from packages at slackbuilds.org. I threw in a couple of ldconfigs for good measure.

Code:

checking for pkgconfig support for libavcodec... yes
checking how to determine LIBAVCODEC_CFLAGS... pkg-config
checking libavcodec/avcodec.h usability... yes
checking libavcodec/avcodec.h presence... yes
checking for libavcodec/avcodec.h... yes
checking how to determine LIBAVCODEC_LIBS... pkg-config
checking for avcodec_thread_init in -lavcodec... no

----------------------------------------
Summary for transcode 1.0.7:
----------------------------------------

core options
----------------------------------------
static AV-frame buffering      yes
network (sockets) streams      yes
NUV format support            yes
experimental xio              no
Default xvid export            xvid4
A52 default decoder            yes

libavcodec
----------------------------------------
headers                        -I/usr/local/include
libraries
build
version
statically linked

hardware support
----------------------------------------
v4l/v4l2                      yes
OSS                            no
bktr                          no
sunau                          no

optional package support
----------------------------------------
IBP                            no
X11                            yes
libmpeg2                      yes
libpostproc                    no
freetype2                      yes
avifile                        no
lame                          yes
ogg                            yes
vorbis                        yes
theora                        yes
libdvdread                    yes
pvm3                          no
libdv                          yes
libquicktime                  yes
lzo                            yes
a52                            yes
libmpeg3                      no
libxml2                        yes
mjpegtools                    no

sdl                            yes
libfame                        no
imagemagick                    no
libjpeg                        yes
bsdav                          no
iconv                          yes

ERROR: requirement failed: cannot link against libavcodec
libavcodec can be found in the following packages:
  libavcodec  http://www.ffmpeg.org/

ERROR: option '--enable-libpostproc' failed: cannot compile libpostproc/postpro
libpostproc/postprocess.h can be found in the following packages:
  libpostproc  http://www.ffmpeg.org/

ERROR: option '--enable-libpostproc' failed: cannot link against libpostproc
libpostproc can be found in the following packages:
  libpostproc  http://www.ffmpeg.org/

Please see the INSTALL file in the top directory of the
transcode sources for more information about building
transcode with this configure script.

Edit to Add: I forgot that after the transcode slackbuild failed, I'd rebuilt ffmpeg from a recent subversion snapshot and left it installed that way. So to confirm my complaint, I uninstalled that version, reinstalled the package ffmpeg-20081214-i686-1sl.tgz and tried again. The outcome was essentially the same. (Sorry for the complication, that's what happens when you're installing stuff manually.)

Woodsman 12-29-2008 05:17 PM

All of the referenced files are part of ffmpeg. I am not software guru with respect to understanding the nuances of software, but I would consider rebuilding and reinstalling ffmpeg. I used the build script from www.slackbuilds.org.

Note: there is a small bug with building ffmpeg. The bug is being remedied in the slackbuild script but is not yet uploaded. The ffmpeg configure file is hard-coded to look for a TEMPDIR variable. If you use /tmp as your temporary working directory then run the build script like this: TEMPDIR=/tmp sh ffmpeg.SlackBuild.

Of course, then try again to build transcode.

DavidHindman 12-29-2008 06:48 PM

Quote:

Originally Posted by Woodsman (Post 3390899)
All of the referenced files are part of ffmpeg. I am not software guru with respect to understanding the nuances of software, but I would consider rebuilding and reinstalling ffmpeg. I used the build script from www.slackbuilds.org.

Note: there is a small bug with building ffmpeg. The bug is being remedied in the slackbuild script but is not yet uploaded. The ffmpeg configure file is hard-coded to look for a TEMPDIR variable. If you use /tmp as your temporary working directory then run the build script like this: TEMPDIR=/tmp sh ffmpeg.SlackBuild.

Of course, then try again to build transcode.

I slackbuilt ffmpeg with that workaround and reinstalled it. The transcode slackbuild then completed without error.

What's clear to me now is that the packages called out in the writeup all need to be built with compatible options. Mixing multimedia packages from different sources runs the risk of incompatible build options. If I did it all over again, I'd just get all the packages from slackbuilds.org and not try to mix in packages from other sources.

Thanks again.


All times are GMT -5. The time now is 12:00 AM.