-
-
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 6.0 bindings #241
Comments
Okay, I'll dig into. |
I also vote for ffmpeg 6.0 bindings but I don't agree to dropping .NET Standard 2.0 as it is still widely used for libraries. For example legacy .NET Core 3.1 and .NET 5.0 projects cannot reference net6.0 target. Change from net45 -> net462 is ok but nuget package already has net472 target.
I guess So my suggestion is we have these targets:
If we would like minimal targets in nuget package, I think these targets will be sufficient:
Note that References: |
I'll drop only outdated frameworks - they mostly used by China users - might be fragmentation in packages but I'll try to avoid |
While we wait for V6 bindings, what's involved in releasing a 5.1.2 build? |
Releasing makes no sense as there is no change in API , but I'll create
packages as some bug fixes have to be done.
…On Tue, Mar 7, 2023 at 2:19 AM miltontaylor ***@***.***> wrote:
While we wait for V6 bindings, what's involved in releasing a 5.1.2 build?
—
Reply to this email directly, view it on GitHub
<#241 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5FPTINA5EW244SFBZZBWLW22EJNANCNFSM6AAAAAAVLMTV3I>
.
You are receiving this because you commented.Message ID: <Ruslan-B/FFmpeg.
***@***.***>
|
Ok great... thanks
________________________________
From: Ruslan Balanukhin ***@***.***>
Sent: Tuesday, March 7, 2023 8:50:27 PM
To: Ruslan-B/FFmpeg.AutoGen ***@***.***>
Cc: Milton Taylor ***@***.***>; Comment ***@***.***>
Subject: Re: [Ruslan-B/FFmpeg.AutoGen] ffmpeg 6.0 bindings (Issue #241)
Releasing makes no sense as there is no change in API , but I'll create
packages as some bug fixes have to be done.
On Tue, Mar 7, 2023 at 2:19 AM miltontaylor ***@***.***> wrote:
While we wait for V6 bindings, what's involved in releasing a 5.1.2 build?
—
Reply to this email directly, view it on GitHub
<#241 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5FPTINA5EW244SFBZZBWLW22EJNANCNFSM6AAAAAAVLMTV3I>
.
You are receiving this because you commented.Message ID: <Ruslan-B/FFmpeg.
***@***.***>
—
Reply to this email directly, view it on GitHub<#241 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKQ3G5VQL7Z2OSWAADASTFLW24AGHANCNFSM6AAAAAAVLMTV3I>.
You are receiving this because you commented.Message ID: ***@***.***>
|
@miltontaylor v5.1.2 is available - net v6.0 |
Great! Thankyou.
Is it a big step to ffmpeg6?
…________________________________
From: Ruslan Balanukhin ***@***.***>
Sent: Thursday, March 16, 2023 5:53:29 AM
To: Ruslan-B/FFmpeg.AutoGen ***@***.***>
Cc: Milton Taylor ***@***.***>; Mention ***@***.***>
Subject: Re: [Ruslan-B/FFmpeg.AutoGen] ffmpeg 6.0 bindings (Issue #241)
@miltontaylor<https://github.com/miltontaylor> v5.1.2 is available - net v6.0
—
Reply to this email directly, view it on GitHub<#241 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AKQ3G5SW6KP2YUKUVOICA2LW4IF2TANCNFSM6AAAAAAVLMTV3I>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Appears to be working - testing now - I'll publish packages tomorrow if no issues found. |
Any update on this? |
I published packages, basics are working fine |
Thank you very much, I look forward to getting into it now. |
It looks like we've got a new build of ffmpeg this week. This is a request, when time allows, to port the new bindings! As usual, many thanks for maintaining this project.
We may also want to consider bringing the minimum .NET framework target from net45 -> net462 to match Microsoft's support policy and target net6.0 directly (instead of .NETStandard 2.0/2.1).
If .NETFramework is ever dropped, this also opens up the possibility of replacing [DllImport] with [LibraryImport] in the future.
The text was updated successfully, but these errors were encountered: