Stop audio javascript

The HTML element is used to embed sound content in documents. It may contain one or more audio sources, represented using the src attribute or the element: the browser will choose the most suitable one. It can also be the destination for streamed media, using a MediaStream.

The above example shows simple usage of the element. In a similar manner to the element, we include a path to the media we want to embed inside the src attribute; we can include other attributes to specify information such as whether we want it to autoplay and loop, whether we want to show the browser's default audio controls, etc.

The content inside the opening and closing tags is shown as a fallback in browsers that don't support the element.

This element's attributes include the global attributes.

A Boolean attribute: if specified, the audio will automatically begin playback as soon as it can do so, without waiting for the entire audio file to finish downloading.

If this attribute is present, the browser will offer controls to allow the user to control audio playback, including volume, seeking, and pause/resume playback.

This enumerated attribute indicates whether to use CORS to fetch the related audio file. CORS-enabled resources can be reused in the element without being tainted. The allowed values are:

Sends a cross-origin request without a credential. In other words, it sends the Origin: HTTP header without a cookie, X.509 certificate, or performing HTTP Basic authentication. If the server does not give credentials to the origin site [by not setting the Access-Control-Allow-Origin: HTTP header], the image will be tainted, and its usage restricted.

Sends a cross-origin request with a credential. In other words, it sends the Origin: HTTP header with a cookie, a certificate, or performing HTTP Basic authentication. If the server does not give credentials to the origin site [through Access-Control-Allow-Credentials: HTTP header], the image will be tainted and its usage restricted.

When not present, the resource is fetched without a CORS request [i.e. without sending the Origin: HTTP header], preventing its non-tainted used in elements. If invalid, it is handled as if the enumerated keyword anonymous was used. See CORS settings attributes for additional information.

A Boolean attribute used to disable the capability of remote playback in devices that are attached using wired [HDMI, DVI, etc.] and wireless technologies [Miracast, Chromecast, DLNA, AirPlay, etc]. See this proposed specification for more information.

A Boolean attribute: if specified, the audio player will automatically seek back to the start upon reaching the end of the audio.

A Boolean attribute that indicates whether the audio will be initially silenced. Its default value is false.

This enumerated attribute is intended to provide a hint to the browser about what the author thinks will lead to the best user experience. It may have one of the following values:

• none: Indicates that the audio should not be preloaded.
• metadata: Indicates that only audio metadata [e.g. length] is fetched.
• auto: Indicates that the whole audio file can be downloaded, even if the user is not expected to use it.
• empty string: A synonym of the auto value.

The default value is different for each browser. The spec advises it to be set to metadata.

The URL of the audio to embed. This is subject to HTTP access controls. This is optional; you may instead use the element within the audio block to specify the audio to embed.

Browsers don't all support the same file types and audio codecs; you can provide multiple sources inside nested elements, and the browser will then use the first one it understands:

We offer a substantive and thorough guide to media file types and the audio codecs that can be used within them. Also available is a guide to the codecs supported for video.

Other usage notes:

• If you don't specify the controls attribute, the audio player won't include the browser's default controls. You can, however, create your own custom controls using JavaScript and the HTMLMediaElement API.
• To allow precise control over your audio content, HTMLMediaElements fire many different events. This also provides a way to monitor the audio's fetching process so you can watch for errors or detect when enough is available to begin to play or manipulate it.
• You can also use the Web Audio API to directly generate and manipulate audio streams from JavaScript code rather than streaming pre-existing audio files.
• elements can't have subtitles or captions associated with them in the same way that elements can. See WebVTT and Audio by Ian Devlin for some useful information and workarounds.

A good general source of information on using HTML is the Video and audio content beginner's tutorial.

The element has no intrinsic visual output of its own unless the controls attribute is specified, in which case the browser's default controls are shown.

The default controls have a display value of inline by default, and it is often a good idea set the value to block to improve control over positioning and layout, unless you want it to sit within a text block or similar.

You can style the default controls with properties that affect the block as a single unit, so for example you can give it a border and border-radius, padding, margin, etc. You can't however style the individual components inside the audio player [e.g. change the button size or icons, change the font, etc.], and the controls are different across the different browsers.

To get a consistent look and feel across browsers, you'll need to create custom controls; these can be marked up and styled in whatever way you want, and then JavaScript can be used along with the HTMLMediaElement API to wire up their functionality.

Video player styling basics provides some useful styling techniques it is written in the context of , but much of it is equally applicable to .

You can detect when tracks are added to and removed from an element using the addtrack and removetrack events. However, these events aren't sent directly to the element itself. Instead, they're sent to the track list object within the element's HTMLMediaElement that corresponds to the type of track that was added to the element:

An AudioTrackList containing all of the media element's audio tracks. You can add a listener for addtrack to this object to be alerted when new audio tracks are added to the element.

Add an addtrack listener to this VideoTrackList object to be informed when video tracks are added to the element.

Add an addtrack event listener to this TextTrackList to be notified when new text tracks are added to the element.

For example, to detect when audio tracks are added to or removed from an element, you can use code like this:

This code watches for audio tracks to be added to and removed from the element, and calls a hypothetical function on a track editor to register and remove the track from the editor's list of available tracks.

You can also use addEventListener[] to listen for the addtrack and removetrack events.

The following example shows simple usage of the element to play an OGG file. It will autoplay due to the autoplay attributeif the page has permission to do soand also includes fallback content.

For details on when autoplay works, how to get permission to use autoplay, and how and when it's appropriate to use autoplay, see our autoplay guide.

This example specifies which audio track to embed using the src attribute on a nested element rather than directly on the element. It is always useful to include the file's MIME type inside the type attribute, as the browser is able to instantly tell if it can play that file, and not waste time on it if not.

This example includes multiple elements. The browser tries to load the first source element [Opus] if it is able to play it; if not it falls back to the second [Vorbis] and finally back to MP3:

Audio with spoken dialog should provide both captions and transcripts that accurately describe its content. Captions, which are specified using WebVTT, allow people who are experiencing hearing loss to understand an audio recording's content as the recording is being played, while transcripts allow people who need additional time to be able to review the recording's content at a pace and format that is comfortable for them.

If automatic captioning services are used, it is important to review the generated content to ensure it accurately represents the source audio.

The element doesn't directly support WebVTT. You will have to find a library or framework that provides the capability for you, or write the code to display captions yourself. One option is to play your audio using a element, which does support WebVTT.

In addition to spoken dialog, subtitles and transcripts should also identify music and sound effects that communicate important information. This includes emotion and tone. For example, in the WebVTT below, note the use of square brackets to provide tone and emotional insight to the viewer; this can help establish the mood otherwise provided using music, nonverbal sounds and crucial sound effects, and so forth.

Also it's a good practice to provide some content [such as the direct download link] as a fallback for viewers who use a browser in which the element is not supported:

• MDN Subtitles and closed caption Plugins
• Web Video Text Tracks Format [WebVTT]
• WebAIM: Captions, Transcripts, and Audio Descriptions
• MDN Understanding WCAG, Guideline 1.2 explanations
• Understanding Success Criterion 1.2.1 | W3C Understanding WCAG 2.0
• Understanding Success Criterion 1.2.2 | W3C Understanding WCAG 2.0

• Web media technologies
  • Media container formats [file types]
  • Guide to audio codecs used on the web
• Web Audio API
• HTMLAudioElement
• Learning area: Video and audio content
• Cross-browser audio basics

Video liên quan