Binary Tools Paths: Thoroughly confused or bug?
Posted: Tue Feb 19, 2013 11:53 am
OK, I must be missing something, but I for the life of me am unable to change the paths of certain binaries such as mecoder, mplayer, ffmpeg. I want to assess performance of my own compiled versions vs UMS versions now included (2.4.2). I've tried using explicit paths to my binaries such as:
However, debug log shows the path as:
Seems "./" is hard-coded or am I missing something?
Seems absolute path does work on ffmpeg (which I absolutely needed to set since the UMS bundled version requires i386 libs that are impractical for me to replace on my 86_64 system).
Thanks in advance!
Code: Select all
mplayer_path = /usr/local/bin/mplayerCode: Select all
DEBUG 2013-02-18 18:48:43.885 [main] Launching: .//usr/local/bin/mplayerSeems absolute path does work on ffmpeg (which I absolutely needed to set since the UMS bundled version requires i386 libs that are impractical for me to replace on my 86_64 system).
Thanks in advance!