Downloads:
3,424
Downloads of v 3.25.0.0:
420
Last Update:
26 Jun 2015
Package Maintainer(s):
Software Author(s):
- Microsoft Corporation
Tags:
amsexplorer amse ams azure media explorer encoding streaming- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Azure Media Services Explorer
This is not the latest version of Azure Media Services Explorer available.
- 1
- 2
- 3
3.25.0.0 | Updated: 26 Jun 2015
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
3,424
Downloads of v 3.25.0.0:
420
Maintainer(s):
Software Author(s):
- Microsoft Corporation
Azure Media Services Explorer 3.25.0.0
This is not the latest version of Azure Media Services Explorer available.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
Deployment Method: Individual Install, Upgrade, & Uninstall
To install Azure Media Services Explorer, run the following command from the command line or from PowerShell:
To upgrade Azure Media Services Explorer, run the following command from the command line or from PowerShell:
To uninstall Azure Media Services Explorer, run the following command from the command line or from PowerShell:
Deployment Method:
This applies to both open source and commercial editions of Chocolatey.
1. Enter Your Internal Repository Url
(this should look similar to https://community.chocolatey.org/api/v2/)
2. Setup Your Environment
1. Ensure you are set for organizational deployment
Please see the organizational deployment guide
2. Get the package into your environment
Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)-
Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download
-
Open Source
-
Download the package:
Download - Follow manual internalization instructions
-
-
Package Internalizer (C4B)
-
Run: (additional options)
choco download amsexplorer --internalize --version=3.25.0.0 --source=https://community.chocolatey.org/api/v2/
-
For package and dependencies run:
choco push --source="'INTERNAL REPO URL'"
- Automate package internalization
-
Run: (additional options)
3. Copy Your Script
choco upgrade amsexplorer -y --source="'INTERNAL REPO URL'" --version="'3.25.0.0'" [other options]
See options you can pass to upgrade.
See best practices for scripting.
Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.
If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:
choco upgrade amsexplorer -y --source="'INTERNAL REPO URL'" --version="'3.25.0.0'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
- name: Install amsexplorer
win_chocolatey:
name: amsexplorer
version: '3.25.0.0'
source: INTERNAL REPO URL
state: present
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
chocolatey_package 'amsexplorer' do
action :install
source 'INTERNAL REPO URL'
version '3.25.0.0'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
cChocoPackageInstaller amsexplorer
{
Name = "amsexplorer"
Version = "3.25.0.0"
Source = "INTERNAL REPO URL"
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'amsexplorer':
ensure => '3.25.0.0',
provider => 'chocolatey',
source => 'INTERNAL REPO URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
4. If applicable - Chocolatey configuration/installation
See infrastructure management matrix for Chocolatey configuration elements and examples.
This package was approved by moderator ferventcoder on 28 Dec 2015.
Azure Media Services Explorer is a tool for Windows that does upload, download, process, encode, package, and stream assets and live channels with Azure Media Services. Source code is also provided.
A general description is available here and there is a recent blog post on live encoding and Explorer.
Contact: [email protected]
#NOTE: Please remove any commented lines to tidy up prior to releasing the package, including this one
# REMOVE ANYTHING BELOW THAT IS NOT NEEDED
# Auto Uninstaller should be able to detect and handle registry uninstalls (if it is turned on, it is in preview for 0.9.9).
$ErrorActionPreference = 'Stop'; # stop on all errors
$packageName = 'amsexplorer'
# registry uninstaller key name is the key that is found at HKLM:\Software\Windows\CurrentVersion\Uninstall\ THE NAME
$registryUninstallerKeyName = 'amsexplorer' #ensure this is the value in the registry
$msiProductCodeGuid = '{insert it here}'
$shouldUninstall = $true
$local_key = "HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
# local key 6432 probably never exists
$local_key6432 = "HKCU:\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$machine_key6432 = "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\$registryUninstallerKeyName"
$file = @($local_key, $local_key6432, $machine_key, $machine_key6432) `
| ?{ Test-Path $_ } `
| Get-ItemProperty `
| Select-Object -ExpandProperty UninstallString
if ($file -eq $null -or $file -eq '') {
Write-Host "$packageName has already been uninstalled by other means."
$shouldUninstall = $false
}
# The below is somewhat naive and built for EXE installers
#$installerType = 'EXE'
#$silentArgs = '/S'
#$validExitCodes = @(0)
#if (!(Test-Path $file)) {
# Write-Host "$packageName has already been uninstalled by other means."
# $shouldUninstall = $false
#}
# The below is somewhat naive and built for MSI installers
$installerType = 'MSI'
# The Product Code GUID is all that should be passed for MSI, and very FIRST,
# because it comes directly after /x, which is already set in the
# Uninstall-ChocolateyPackage msiargs (facepalm).
$silentArgs = "$msiProductCodeGuid /qn /norestart"
# https://msdn.microsoft.com/en-us/library/aa376931(v=vs.85).aspx
$validExitCodes = @(0, 3010, 1605, 1614, 1641)
# Don't pass anything for file, it is ignored for msi (facepalm number 2)
# Alternatively if you need to pass a path to an msi, determine that and use
# it instead of $msiProductCodeGuid in silentArgs, still very first
$file = ''
if ($shouldUninstall) {
Uninstall-ChocolateyPackage -PackageName $packageName -FileType $installerType -SilentArgs $silentArgs -validExitCodes $validExitCodes -File $file
}
## OTHER HELPERS
## https://github.com/chocolatey/choco/wiki/HelpersReference
#Uninstall-ChocolateyZipPackage
#Uninstall-BinFile # Only needed if you added one in the installer script, choco will remove the ones it added automatically.
#remove any shortcuts you added
Log in or click on link to see number of positives.
- amsexplorer.3.25.0.0.nupkg (2ffef8f37607) - ## / 57
- AMSExplorerSetup_v3.25.0.0.exe (27a3e65d14c9) - ## / 57
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Add to Builder | Version | Downloads | Last Updated | Status |
---|---|---|---|---|
Azure Media Services Explorer 5.4.4.0 | 362 | Monday, July 12, 2021 | Approved | |
Azure Media Services Explorer 5.4.3.0 | 92 | Wednesday, June 23, 2021 | Approved | |
Azure Media Services Explorer 5.4.2.1 | 78 | Monday, June 7, 2021 | Approved | |
Azure Media Services Explorer 5.3.0.1 | 165 | Thursday, February 11, 2021 | Approved | |
Azure Media Services Explorer 4.3.4.0 | 570 | Friday, January 11, 2019 | Approved | |
Azure Media Services Explorer 3.28.0.0 | 883 | Thursday, September 3, 2015 | Approved | |
Azure Media Services Explorer 3.27.0.0 | 420 | Monday, July 27, 2015 | Approved | |
Azure Media Services Explorer 3.26.0.0 | 434 | Saturday, July 11, 2015 | Approved | |
Azure Media Services Explorer 3.25.0.0 | 420 | Friday, June 26, 2015 | Approved |
This update brings the following features and improvements :
- Update to Dynamic Manifest Filters (using the REST API)
- New controls to set timings in Day/Hour/Min/Sec with a slider for asset filters (Raw mode still possible)
- Asset filter reads now the manifest to determine the content duration, scale and timestamp offset. Tested with live streams and archives
- Supported FourCC codecs are listed, track filtering sample has been updated
- New icons, and a way to edit the filters from the menus
- Fix a critical display/performance issue with the asset grid
This package has no dependencies.
Ground Rules:
- This discussion is only about Azure Media Services Explorer and the Azure Media Services Explorer package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Azure Media Services Explorer, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.