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
Copy file name to clipboardExpand all lines: articles/media-services/azure-media-player/azure-media-player-api-methods.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
---
2
2
title: Azure Media Player API Methods
3
-
description: The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight or any other supported playback technologies.
3
+
description: The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight, or any other supported playback technologies.
4
4
author: IngridAtMicrosoft
5
5
ms.author: inhenkel
6
6
ms.service: media-services
@@ -11,11 +11,11 @@ ms.date: 03/16/2020
11
11
12
12
# API #
13
13
14
-
The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight or any other supported playback technologies.
14
+
The Azure Media Player API allows you to interact with the video through JavaScript, whether the browser is playing the video through HTML5 video, Flash, Silverlight, or any other supported playback technologies.
15
15
16
16
## Referencing the player ##
17
17
18
-
To use the API functions, you need access to the player object. Luckily this is easy to get. You just need to make sure your video tag has an ID. The example embed code has an ID of `vid1`. If you have multiple videos on one page, make sure every video tag has a unique ID.
18
+
To use the API functions, you need access to the player object. Luckily it is easy to get. You just need to make sure your video tag has an ID. The example embed code has an ID of `vid1`. If you have multiple videos on one page, make sure every video tag has a unique ID.
19
19
20
20
`var myPlayer = amp('vid1');`
21
21
@@ -24,7 +24,7 @@ To use the API functions, you need access to the player object. Luckily this is
24
24
25
25
## Wait until the player is ready ##
26
26
27
-
The time it takes Azure Media Player to set up the video and API will vary depending on the playback technology being used (HTML5 will often be much faster to load than Flash or Silverlight). For that reason, the player's 'ready' function should be used to trigger any code that requires the player's API.
27
+
The time it takes Azure Media Player to set up the video and API will vary depending on the playback technology being used. HTML5 will often be much faster to load than Flash or Silverlight. For that reason, the player's 'ready' function should be used to trigger any code that requires the player's API.
28
28
29
29
```javacript
30
30
amp("vid_1").ready(function(){
@@ -56,7 +56,7 @@ Now that you have access to a ready player, you can control the video, get value
56
56
```
57
57
58
58
## Registering for events ##
59
-
Events should be registered for directly after initializing the player for the first time to ensure all events are appropriately reported to the application. This should be done outside of the ready event.
59
+
Events should be registered directly after initializing the player for the first time to ensure all events are appropriately reported to the application, and should be done outside of the ready event.
60
60
61
61
```javacript
62
62
var myPlayer = amp("vid_1", myOptions, function(){
Copy file name to clipboardExpand all lines: articles/media-services/azure-media-player/azure-media-player-error-codes.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@ ms.date: 03/13/2020
10
10
11
11
# Error codes #
12
12
13
-
When playback can not start or has stopped, an error event will be fired and `error()` function will return a code and an optional message, which is to help the app developer get more details. `error().message`is not the message displayed to the user. The message displayed to the user is based on `error().code` bits 27-20, see table below.
13
+
When playback can't start or has stopped, an error event will be fired and the `error()` function will return a code and an optional messageto help the app developer get more details. `error().message`isn't the message displayed to the user. The message displayed to the user is based on `error().code` bits 27-20, see table below.
14
14
15
15
```javascript
16
16
@@ -70,15 +70,15 @@ Describe details of the error, bits 27-20 provide a high level, bits 19-0 provid
| srcPlayerMismatchUnknown |0x0600000| Generic no matching tech player to play the source |
81
-
| srcPlayerMismatchFlashNotInstalled |0x0600001|Flash plugin is not installed, if installed the source may play. *OR* Flash 30 is installed and playing back AEScontent. Ifthis is the case, please try a different browser. Flash30 is unsupported today as of June 7th. See [known issues](azure-media-player-known-issues.md) for more details. Note: If 0x00600003, both Flash and Silverlight are not installed, if specified in the techOrder.|
81
+
| srcPlayerMismatchFlashNotInstalled |0x0600001|Flash plugin isn't installed, if installed the source may play. *OR* Flash 30 is installed and playing back AES content. If this is the case, please try a different browser. Flash 30 is unsupported today as of June 7th. See [known issues](azure-media-player-known-issues.md) for more details. Note: If 0x00600003, both Flash and Silverlight are not installed, if specified in the techOrder.|
82
82
| srcPlayerMismatchSilverlightNotInstalled | 0x0600002 | Silverlight plugin is not installed, if installed the source may play. Note: If 0x00600003, both Flash and Silverlight are not installed, if specified in the techOrder. |
83
83
| | 0x00600003 | Both Flash and Silverlight are not installed, if specified in the techOrder. |
Copy file name to clipboardExpand all lines: articles/media-services/azure-media-player/azure-media-player-known-issues.md
+16-16Lines changed: 16 additions & 16 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,17 +16,17 @@ The current release has the following known issues:
16
16
17
17
- Incorrectly configured encoders may cause issues with playback
18
18
- Streams with timestamps greater than 2^53 may have playback issues.
19
-
- Mitigation: Use 90kHz video and 44.1kHz audio timescales
20
-
- No autoplay on mobile devices without user interaction. This is blocked by the platform.
19
+
- Mitigation: Use 90-kHz video and 44.1-kHz audio timescales
20
+
- No autoplay on mobile devices without user interaction. It's blocked by the platform.
21
21
- Seeking near discontinuities may cause playback failure.
22
22
- Download of large presentations may cause UI to lockup.
23
-
-Cannot automatically playback same source again after presentation ended.
24
-
- To replay a source after it has ended, it is required to set the source again.
23
+
-Can't automatically play back same source again after presentation ended.
24
+
- To replay a source after it has ended, it's required to set the source again.
25
25
- Empty manifests may cause issues with the player.
26
26
- This issue can occur when starting a live stream and not enough chunks are found in the manifest.
27
27
- Playback position maybe outside UI seekbar.
28
-
- Event ordering is not consistent across all techs.
29
-
- Buffered property is not consistent across techs.
28
+
- Event ordering isn't consistent across all techs.
29
+
- Buffered property isn't consistent across techs.
30
30
- nativeControlsForTouch must be false (default) to avoid "Object doesn't support property or method 'setControls'"
31
31
- Posters must now be absolute urls
32
32
- Minor aesthetic issues may occur in the UI when using high contrast mode of the device
@@ -39,26 +39,26 @@ The current release has the following known issues:
39
39
40
40
## AzureHtml5JS ##
41
41
42
-
-If in the DVR window of Live content, and content finishes, timeline will continue to grow until seek to the area or reaching the end of the presentation.
42
+
-In the DVR window of Live content, when content finishes the timeline will continue to grow until seeking to the area or reaching the end of the presentation.
43
43
- Live presentations in Firefox with MSE enabled has some issues
44
-
- Assets that are audio or video only will not play back via the AzureHtml5JS tech.
44
+
- Assets that are audio or video only won't play back via the AzureHtml5JS tech.
45
45
- If you'd like to play back assets without audio or video, you can do so by inserting blank audio or video using the [Azure Media Services Explorer tool](https://aka.ms/amse)
46
46
- Instructions on how to insert silent audio can be found [here](https://azure.microsoft.com/documentation/articles/media-services-advanced-encoding-with-mes/#silent_audio)
47
47
48
48
## Flash ##
49
49
50
-
- AES content does not playback in Flash version 30.0.0.134 due to a bug in Adobe's caching logic. Adobe has fixed the issue and released it in 30.0.0.154
50
+
- AES content does not play back in Flash version 30.0.0.134 due to a bug in Adobe's caching logic. Adobe has fixed the issue and released it in 30.0.0.154
51
51
- Tech and http failures (such as 404 network timeouts), the player will take longer to recover than other techs.
52
-
- Click on video area with flashSS tech will not play/pause the player.
53
-
-Infinite spinner can occur when player is stuck in the case where end user has Flash installed but does not give permission to load on the site. Player thinks plugin is available (as it is installed) and thinks plugin is running the content as JavaScript code has been sent but the browser settings have blocked plugin from executing until user accepts prompt to allow plugin. This can occur in all browsers.
52
+
- Click on video area with flashSS tech won't play/pause the player.
53
+
-If the user has Flash installed but doesn't give permission to load it on the site, infinite spinning can occur. This is because the player thinks the plugin is installed and available and it thinks the plugin is running the content. JavaScript code has been sent but the browser settings have blocked the plugin from executing until the user accepts the prompt to allow the plugin. This can occur in all browsers.
54
54
55
55
## Silverlight ##
56
56
57
57
- Missing features
58
58
- Tech and http failures (such as 404 network timeouts), the player will take longer to recover than other techs.
59
59
- Safari and Firefox on Mac playback with Silverlight requires explicitly defining `"http://` or `https://` for the source.
60
60
- If an API is missing for this tech, it will generally return null.
61
-
-Infinite spinner can occur when player is stuck in the case where end user has Silverlight installed but does not give permission to load on the site. Player thinks plugin is available (as it is installed) and thinks plugin is running the content as JavaScript code has been sent but the browser settings have blocked plugin from executing until user accepts prompt to allow plugin. This can occur in all browsers.
61
+
-If the user has Flash installed but doesn't give permission to load it on the site, infinite spinning can occur. This is because the player thinks the plugin is installed and available and it thinks the plugin is running the content. JavaScript code has been sent but the browser settings have blocked the plugin from executing until the user accepts the prompt to allow the plugin. This can occur in all browsers.
62
62
63
63
## Native HTML5 ##
64
64
@@ -76,7 +76,7 @@ The current release has the following known issues:
76
76
## Google ##
77
77
78
78
- Multiple encoding profiles in the same manifest has some playback issues in Chrome and is not recommended.
79
-
- Chrome cannot playback HE-AAC with AzureHtml5JS. Follow details on the [bug tracker](https://bugs.chromium.org/p/chromium/issues/detail?id=534301).
79
+
- Chrome cannot play back HE-AAC with AzureHtml5JS. Follow details on the [bug tracker](https://bugs.chromium.org/p/chromium/issues/detail?id=534301).
80
80
- As of Chrome v58, widevine content must be loaded/played back via the https:// protocol otherwise playback will fail.
81
81
82
82
## Mozilla ##
@@ -85,11 +85,11 @@ The current release has the following known issues:
85
85
86
86
## Apple ##
87
87
88
-
- Safari on Mac often enables Power Saver mode by default with the setting "Stop plug-ins to save power", which blocks plugins like Flash and Silverlight when they believe it is not in favor to the user. This block does not block the plugin's existent, only capabilities. Given the default techOrder, this may cause issues when attempting to playback
88
+
- Safari on Mac often enables Power Saver mode by default with the setting "Stop plug-ins to save power", which blocks plugins like Flash and Silverlight when they believe it is not in favor to the user. This block does not block the plugin's existent, only capabilities. Given the default techOrder, this may cause issues when attempting to play back
89
89
- Mitigation 1: If the video player is 'front and center' (within a 3000 x 3000 pixel boundary starting at the top left corner of the document) it should still play.
90
90
- Mitigation 2: Change the techOrder for Safari to be ["azureHtml5JS", "html5"]. This mitigation has implication of not getting all the features that are available in the FlashSS tech.
91
91
- PlayReady content via Silverlight may have issues playing back in Safari.
92
-
- AES and restricted token content does not playback using iOS and older Android devices.
92
+
- AES and restricted token content does not play back using iOS and older Android devices.
93
93
- In order to achieve this scenario, a proxy must be added to your service.
94
94
- Default skin for iOS Phone shows through.
95
95
- iPhone playback always occurs in the native player fullscreen.
@@ -101,7 +101,7 @@ The current release has the following known issues:
101
101
102
102
## Older Android ##
103
103
104
-
- AES and restricted token content does not playback using iOS and older Android devices.
104
+
- AES and restricted token content does not play back using iOS and older Android devices.
105
105
- In order to achieve this scenario, a proxy must be added to your service.
0 commit comments