[Zip][Portable] New package: Gyan.FFmpeg version 5.1.2

[SpecterShell]

• Resolves Package Request: ffmpeg #859

• Have you signed the Contributor License Agreement?
• Have you checked that there aren't other open pull requests for the same manifest update/change?
• Have you validated your manifest locally with winget validate --manifest <path>?
• Have you tested your manifest locally with winget install --manifest <path>?
• Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

---

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

   

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @SpecterShell,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[Trenly]

@Msftbot .zip

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Hello @SpecterShell,

The package manager bot determined that the metadata was not compliant.

Please verify the manifest file is compliant with the package manager 1.2 manifest specification.
Make sure the ID is of the form publisher.appname and that the folder structure is manifests\partition\publisher\appname\version.
Note: The path and "PackageIdentifier" are case sensitive.
Be sure to use a tool like VSCode to make sure the manifest YAML syntax is correct.

You could also try our Windows Package Manager Manifest Creator or the YamlCreate script.

For details on the specific error, see the details link below in the build pipeline.

Template: msftbot/validationError/manifest/metadata

[ItzLevvie]

@msftbot .zip

[KaranKad]

As this build is officially promoted by ffmpeg site should we change PackageIdentifier to FFmpeg.FFmpeg?

[SpecterShell]

As this build is officially promoted by ffmpeg site should we change PackageIdentifier to FFmpeg.FFmpeg?

FFmpeg promotes two different builds:

https://www.gyan.dev/ffmpeg/builds/
https://github.com/BtbN/FFmpeg-Builds/releases

So I use this complicated PackageIdentifier in case another one would be added to winget-pkgs repo as well.
Don't worry. I have added a moniker ffmpeg so that if user types winget install ffmpeg it will install this one by default.

[stephengillie]

@wingetbot waivers Add Validation-Executable-Error

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

/AzurePipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[mstevens83]

After installation this does not work for me. It seems like the aliases are incorrect.
@rlaphoenix reported the same issue but it seems his post got deleted?

[sitiom]

After installation this does not work for me. It seems like the aliases are incorrect. @rlaphoenix reported the same issue but it seems his post got deleted?

@mstevens83 Works fine.

[mstevens83]

Works fine.

Not for me.

It seems like this got added to my PATH: C:\Users\steven89\AppData\Local\Microsoft\WinGet\Packages\Gyan.FFmpeg_Microsoft.Winget.Source_8wekyb3d8bbwe\
But the exe's live 2 folders deeper:
C:\Users\steven89\AppData\Local\Microsoft\WinGet\Packages\Gyan.FFmpeg_Microsoft.Winget.Source_8wekyb3d8bbwe\ffmpeg-5.1.2-full_build\bin

I noticed an issue #95349 was filed for this, I'll join the conversation over there.

[rlaphoenix]

After installation this does not work for me. It seems like the aliases are incorrect. @rlaphoenix reported the same issue but it seems his post got deleted?

I deleted as I moved discussion to #95349 and I invite you guys to as well.