-
-
Notifications
You must be signed in to change notification settings - Fork 326
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ffmpeg 5.1 bindings #208
Comments
On it! |
I think it will take a bit of time as seems upgrading to Windows 11 and VS2022 again brought instability with no expiation. After I solve it I am going to build full CI/CD pipeline and start to look for replacement for CppSharp as it feels like it dying project - maybe I wrong - I'll reach Autor first. As I already made a lot of hacks to make it work and that is not a good idea for a long run. |
@iamcarbon which version of runtime you are using? As I think I have discard legacy tail in targets - it definitely will simplify support. As even NET 5.0 is not supported. |
We’re on .NET 6.0.
I would strongly consider dropping all legacy targets and only targeting net6.0 for maintainability.
…Sent from my iPhone
On Jul 29, 2022, at 2:49 AM, Ruslan Balanukhin ***@***.***> wrote:
@iamcarbon which version of runtime you are using? As I think I have discard legacy tail in targets - it definitely will simplify support. As even NET 5.0 is not supported.
And I have even older versions: netstandard2.1;netstandard2.0;net472;net45;net40.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.
|
Okay got it - as it seems to be directions - and I should push others.
New macroses came now as well - as I have to recall what I did 5 years back then in the parsing part and now it all is new. |
To keep updated - I'll publish new package today or tomorrow. |
I listed updated package. |
ffmpeg 5.1 was released on July 22nd. As usual, updated bindings are always appreciated.
https://ffmpeg.org/index.html#news
The text was updated successfully, but these errors were encountered: