Page 1 of 1
Error opening configuration file ./ffmpeg.cfg: No such file.
Posted: 27. Oct 2013, 09:15
by Bart
Hi, I'm trying to create an avi file from a DVD using k3b and transcode on SalixOS KDE 14.0.1. Trancode is version 1.1.7 taken from Slackbuild.org (transcode-1.1.7-i486-2_SBo). As soon as I launch k3b I get the following error:
Error opening configuration file. / Ffmpeg.cfg: No such file or directory
I can not understand if it is a bug in ffmpeg or in transcode. ffmpeg is installed: ffmpeg-0.11.2-i486-1gv
Thanks
Re: Error opening configuration file ./ffmpeg.cfg: No such f
Posted: 27. Oct 2013, 11:58
by gapan
I don't know about transcode, I have never used it. But ffmpeg definitely does not need any kind of configuration file. Also, I'm not sure if k3b is compiled with the options that are needed to do what you want. As it comes from Slackware, it probably isn't (codecs issues).
Why don't you use Handbrake?
Re: Error opening configuration file ./ffmpeg.cfg: No such f
Posted: 27. Oct 2013, 14:39
by Bart
gapan wrote:I don't know about transcode, I have never used it. But ffmpeg definitely does not need any kind of configuration file. Also, I'm not sure if k3b is compiled with the options that are needed to do what you want. As it comes from Slackware, it probably isn't (codecs issues).
Why don't you use Handbrake?
I don't know it.

Having k3b I thought using that. It seems like k9copy...
Re: Error opening configuration file ./ffmpeg.cfg: No such f
Posted: 27. Oct 2013, 15:01
by gapan
Well, try Handbrake. It's the better tool for the job.
Re: Error opening configuration file ./ffmpeg.cfg: No such f
Posted: 27. Oct 2013, 17:10
by Bart
gapan wrote:Well, try Handbrake. It's the better tool for the job.
Of course I will test it, thanks. The fact is that K3b uses Transcode as default encoder. K3b, being a "native" package in SalixOS 14.0.1, I wondered why there were not also Transcode. There is not even in the various repositories of Salix. Also if ffmpeg does not have any configuration files I can not explain the error reported. Reading on different forum I saw that it is a fairly common problem but I can not understand what package creates this issue.