Ken Moffat wrote: > I think the real question is whether people using k3b, such as > Baho, and anyone using dvd::rip, can get those to successfully use > transcode. For people using transcode on the command line, I suspect > that transcode commands which use ffmpeg will still be problematic.
I've always thought this type of code is non-transparent. char *lavc_param_ffmpeg_datadir = "/usr/share/ffmpeg"; Why is the programmer defining a character pointer as a string? I know it's done all the time, but that isn't right. A better construct is: const char lavc_param_ffmpeg_datadir[] = "/usr/share/ffmpeg"; Looking at the code in open source gives a tremendous variation in quality. It ranges from very good to very bad. Of course I've seen some commercial code where it never gets a review and it is generally worse. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
