Displaying 4 results from an estimated 4 matches for "mediatrack".
Did you mean:
mediatracks
2010 Feb 02
0
handling multitrack Ogg
...der whether we need to introduce an explicit "track ID" into
> Ogg, which will define a fixed order independent of the parsing system
> and will allow us in JavaScript to directly address tracks.
>
> For example, the current draft looks something like this:
>
> interface MediaTrack {
> readonly attribute DOMString title;
> readonly attribute DOMString type;
> readonly attribute DOMString role;
> readonly attribute DOMString lang;
> attribute boolean enabled;
> ...
> };
> interface MediaTracks {
> readonly attribute unsigned long leng...
2010 Feb 02
9
handling multitrack Ogg
...ng video quality.
I now wonder whether we need to introduce an explicit "track ID" into
Ogg, which will define a fixed order independent of the parsing system
and will allow us in JavaScript to directly address tracks.
For example, the current draft looks something like this:
interface MediaTrack {
readonly attribute DOMString title;
readonly attribute DOMString type;
readonly attribute DOMString role;
readonly attribute DOMString lang;
attribute boolean enabled;
...
};
interface MediaTracks {
readonly attribute unsigned long length;
getter MediaTrack item(in unsign...
2010 Feb 02
9
handling multitrack Ogg
...ng video quality.
I now wonder whether we need to introduce an explicit "track ID" into
Ogg, which will define a fixed order independent of the parsing system
and will allow us in JavaScript to directly address tracks.
For example, the current draft looks something like this:
interface MediaTrack {
readonly attribute DOMString title;
readonly attribute DOMString type;
readonly attribute DOMString role;
readonly attribute DOMString lang;
attribute boolean enabled;
...
};
interface MediaTracks {
readonly attribute unsigned long length;
getter MediaTrack item(in unsign...
2010 Feb 02
9
handling multitrack Ogg
...ng video quality.
I now wonder whether we need to introduce an explicit "track ID" into
Ogg, which will define a fixed order independent of the parsing system
and will allow us in JavaScript to directly address tracks.
For example, the current draft looks something like this:
interface MediaTrack {
readonly attribute DOMString title;
readonly attribute DOMString type;
readonly attribute DOMString role;
readonly attribute DOMString lang;
attribute boolean enabled;
...
};
interface MediaTracks {
readonly attribute unsigned long length;
getter MediaTrack item(in unsign...