Quote:
MickJT wrote:
Need testers.
FFmpeg - For now, set high stack
This is great!
I've modified ffmpegGUI to recognize this version number. The version number doesn't follow, what at least used to be, the standard version number scheme for ffmpeg. Unfortunatly that causes ffmpegGUI to crash. I've made the version routine a bit more flexible so it doesn't crash and I modified to recognise this version as valid. Other version numbers should produce a warning but allow you to continue.
I did a little playing around and it appears this verison of ffmpeg doesn't know how to handle Amiga paths properly unless I'm missing something.
For example:
ffmpeg -i jws.mpeg jws.avi
works as expected as long as the videos are in the current directory, but...
ffmpeg -i ram:jws.mpeg jws.avi
produces the followiing error message:
"ram:jws.mpeg: No such file or directory"
Did a bit more playing and my suspision was right. It's looking for unix style paths. The following works:
ffmpeg -i /ram/jws.mpeg jws.avi
That makes it a bit tough to use with ffmpegGUI and file requesters.
You can type the paths into ffmpegGUI manually though and it will work.
ffplay of course has the same issue. What would it take to fix this in ffmpeg?
Edited by ktadd on 2010/7/4 9:41:51