FFmpeg draft for SWscaler and deprecated img_convert
I've added a draft AVSWScale.cs file into the Tao.FFMpeg src folder.
The latest SVN builds of FFMpeg have removed the img_convert function completely, having previously been deprecated. Additionally, the sws_scale functions (Software Scaler) are now in a separate library from AVcodec.
Without this, when used against the latest FFMpeg from source, Tao.FFMpeg will cease to function for video.
This draft isn't perfect, the final image is coming out partially corrupted for some reason, but is a starting point.
There are some additional issues with the current AVCodec:
AVFrame in Tao.FFMpeg has been more fully fleshed out, but it is not working against the latest FFMpeg builds. If you need Tao.FFMpeg to work, comment out everything from all the array [] variables onwards. The critical portion here is the first 2-3 variables anyway.
Can you recommend a version
Can you recommend a version of FFmpeg that works best with the current Tao Framework? I'm interested in hacking on it but it'd be easier with a good starting point.
I'm currently using rev11463
I'm currently using rev11463 (avutil 49.6.0, avcodec 51.49.0, avformat 52.3.0) and although probably not everything is implemented, it works fine. However, Tao.FFmpeg build by default for avformat 51! I've made some preprocessor switches in AVFormat.cs to enable you to select the version you want.
Later versions have the
Later versions have the img_convert function completely removed and must use the sws_scaler instead. I haven't been able to fully convert the sws_scaler headers yet and had to resort to adding a wrapper call inside FFMpeg to get it to function.
Euan MacInnes
http://icarus.sourceforge.net
Windows, MacOSX, Linux C# project based off the Tao.Framework
Hi SeaEagle1. I see that you
Hi SeaEagle1. I see that you checked in an FFmpeg example that uses .NET 3.0 code. We may want to discuss this further since we are hopefully close to a new release. Many people (including myself) still use .NET 2.0 so the FFmpeg solution no longer fully builds.
For those of you who have been around Tao long enough may remember the similar issues we had moving from .NET 1.1 to 2.0.
What are peoples' thoughts on having .NET 3.0 code in SVN?
Personally I think Tao
Personally I think Tao should continue to target .Net 2.0:
a) most people still using .Net 2.0 out there.
b) anything higher is not viable until Mono supports it adequately.
Unlike the move from .Net 1.1 -> 2.0, which added significant functionality, I cannot think of any .Net 3.0 features that would apply to Tao (WPF? WCF?) .Net 3.5 "Linq to Objects" on the other hand is interesting, but doesn't really apply to the Tao.* APIs.
------
OpenTK
I agree. SeaEagle, you may
I agree. SeaEagle, you may want to move your example to a branch.
I just used WPF (which
I just used WPF (which somehow ended up being called .NET 3.0) for the gui, because it was in the test program that I had lying around. I'll see if I can make up a simple WinForms gui instead, shouldn't be too hard. I'll strip the project from the ffmpeg solution for now, so you don't have trouble with it (I thought VS just disables projects it doesn't recognize).
-double post-
-double post-