KMediaInfoMediaParser & KFFMpegMediaParser don't use configuration for location of "ffmpeg" and "ffprobe"

[wzur]

KMediaInfoMediaParser & KFFMpegMediaParser don't use configuration to specify location of cmdPath="ffmpeg", $ffprobeBin="ffprobe
which leads to sh: ffprobe: command not found if ffprobe is not in a standard PATH (like /usr/bin/ffmpeg)

I noticed such configuration has been introduced for other components, and it would be useful if these two classes utilised that, too.

[kaltura-hooks]

Hi @wzur,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

• Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
  please provide as much details as possible.
• Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
  If self hosted, are you using the RPM or deb install?
• Packages installed.
  When using RPM, paste the output for:

    # rpm -qa \"kaltura*\"

For deb based systems:

    # dpkg -l \"kaltura-*\"

• If running a self hosted ENV - provide the MySQL server version used
• If running a self hosted ENV - is this a single all in 1 server or a cluster?
• If running a self hosted ENV, while making the problematic request, run:

    # tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

• When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

[wzur]

Before I created this issue, I've checked the master branch of KMediaInfoMediaParser class, and the problematic area is the same as with installed PHP code in our installation.

This is a general issue, not connected with RPM or Debian installation and as such information requested automaticaly by the hook is not particularly helpful.

[anatolkaltura]

Hi @wzur
You are right, will be fixed

[anatolkaltura]

Fixed - added configuration option for ffmpeg/ffprobe retrieval