You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need to use Video.FFMPEG in windows store apps please help me how could I use
it in there or if any update on it.
I have seen some portable solutions for AFORGE on internet but there is nothing
regarding this specific "Video.FFMPEG". Please see if you guys can help me with
this.
Original issue reported on code.google.com by zamir...@gmail.com on 3 Mar 2014 at 11:42
The text was updated successfully, but these errors were encountered:
Dear Zamir,
I ported AForge.NET to portable class libraries a while ago, and the result is
available here: https://github.com/cureos/aforge
I have not yet attempted to port "Video.FFMPEG" for several reasons, one
crucial being that it requires quite some rewriting to also make the C++ based
FFMPEG code adapted to PCL, or at least to the respective Windows Store and
Windows Phone 8 targets.
I have noticed some attempts to port the FFMPEG code to Windows Store
(https://ffmpegwinrtarm.codeplex.com/), which is at least a start. To also make
this code available to a WinStore application, you would need to switch the
C++/CLI code in "Video.FFMPEG" to its C++/CX equivalent. Some work of course,
but I am sure it can be done within a reasonable timeframe.
I do not have the time or incentive to look further at this right now, but if
someone (you, perhaps, Zamir?) would be interested in doing the necessary work
I would be more than happy to incorporate it in my Portable AForge.NET fork.
Just to have a placeholder, I have also copied this communication to the
Portable AForge.NET issues list. You'll find it here:
https://github.com/cureos/aforge/issues/5
Best regards,
Anders
anders at cureos dot com
Original comment by cureos...@gmail.com on 31 Mar 2014 at 10:47
Original issue reported on code.google.com by
zamir...@gmail.com
on 3 Mar 2014 at 11:42The text was updated successfully, but these errors were encountered: