videoporama cannot find mjpegtools

English Multimedia
1

I have installed (via YaST) both videoporama and mjpegtools. I can see that mjpegtools 1.9.0-3.1 is installed. The lavrec and lavplay
are also in the /usr/bin directory. However, the videoporama cannot find the mjpegtool and the videoporama is unable to do any thing.The videoporama seems to be the program that can do what I want to be done. But am puzzled by the problem that videoporama cannot see the mjpegtools in my computer.
Any help that the forum can provide (with respect to either mjpegtools or videoporama or how to solve this puzzle) will be greatly appreciated.

Thanks. Sheo

2

It is a nice story, but we need some facts.

When you say: “the videoporama cannot find the mjpegtoo”, how do you know? When there are any messages, please show these messages!

3

Hi Henk van Velden,
Thanks for your message. I appreciate your time. When I start videoporama the first message that I get is that MJpegTools not found. It find every other things, like (FFmpeg SOX) installed and correctly configured. But not the MJpegtoos (despite YaST finding that they are installed) and I find many executables starting with yuv* and lav* are in the /usr/bin directory.

Then, I reconfigure the videoporama. Unfortunately, the same result.

Thanks again for your help.

Sheo

4

Hi Henk van Velden,

After sending to you a reply to your message, I found these further details. These details further elaborate my previous reply. I found that:

I have these
lav2avi.sh* lav2wav* lav2yuv* lavaddwav* lavinfo* lavpipe* lavplay* lavrec*
lavtc.sh* lavtrans* lavvideo* yuv2lav*
yuv2lav* yuvcorrect* yuvdeinterlace* yuvfps* yuvkineco*
yuvplay* yuvsplittoppm* yuvycsnoise*
yuv4mpeg* yuvcorrect_tune* yuvdenoise* yuvinactive* yuvmedianfilter* yuvscaler* yuvtoppm*
in /usr/bin

But I do not have xlav v4l v4l-conf lav2dfilter and mpeg2enec and anec and mplex directory anywhwere.

I also have several files related encoder.py in /usr/lib64

For your convenience, my earlier short reply was the following:

Thanks for your message. I appreciate your time. When I start videoporama the first message that I get is that MJpegTools not found. It find every other things, like (FFmpeg SOX) installed and correctly configured. But not the MJpegtoos (despite YaST finding that they are installed) and I find many executables starting with yuv* and lav* are in the /usr/bin directory.

Then, I reconfigure the videoporama. Unfortunately, the same result.

Thanks again for your help.

Sheo

5

One caution, is when it comes to multimedia on openSUSE, try not to mix your application repositories.

Hence for example, do not install applications from videolan and also from Packman, as the packagers of those two repositories do not have an agreement as to where they will locate codecs, and hence it is not uncommon for applictions from each to be incompatible with each other. There is also a lot of duplication in applications packaged by each, which in fact are not the same as they put and look for codecs in different directories.

Since Packman is the larger of those two repositories (ie of Packman and Videolan) my recommendation is to only use Packman, and replace every package packaged by Videolan on your system with only those packaged by Packman.

Also, if the are Novell/SuSE-GmbH packaged applications with Packman packaged equivalents, replace any of the Novell/SuSE-GmbH packaged apps with their Packman packaged equivalents.

One can tell applications packaged by packman by the “pm” in the version number.

I also recommend you keep your active repository list in your software manager limited to ONLY the following 4 (and no other) repositories: OSS, Non-OSS, Update and Packman. The 1st 3 are official Novell / SuSE-GmbH repositories, and the last one is Packman, the largest 3rd Party repository. The quality of rpms packaged by those 4 repositories are very good. Do NOT keep other repositories in your software package manager unless you really really understand the risks and how to both identify and recover from problems.

If you MUST obtain an application from another repository which is NOT one of those 4, then add the 5th repository, install the application, and remove the 5th repository.

That simple approach will save a LOT of trouble.

My view is the best way to solve a dependency or repository functionality problem, is to never encounter one.

Good luck!

6

And when you try to follow the good advice of oldcpu above and need comment on the repos you have, please post the output of

zypper lr -d