Re: MSE WebM/VP9 enabled on nightly
ilde...@gmail.com writes: > > That's great news. Does it mean we can expect to see VP9 working in > Firefox 37? Even on Linux? Cause as for Firefox 35 on UBuntu 14.10 I > still MSE and VP9 disabled here: http://www.youtube.com/html5 The plan for MSE has changed a bit since Anthony's post. We are currently looking at MSE support enabled for Firefox 37 on Windows and Mac OS X, limited to YouTube initially, and MP4 only. Linux and VP9 support will follow. For testing, MSE support can be enabled on current nightly and aurora using prefs: media.mediasource.enabled Codec support can be enabled or disabled via prefs: media.mediasource.mp4.enabled media.mediasource.webm.enabled -- http://bluishcoder.co.nz ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: MSE WebM/VP9 enabled on nightly
On Friday, October 24, 2014 at 5:06:22 PM UTC+2, Anthony Jones wrote: > I just wanted to give a heads up to everyone that we enabled Media > Source Extensions on nightly for WebM/VP9. This brings Adaptive > Streaming capability to Firefox video playback. The feature is not > complete so the pref will automatically turn off when it gets to > beta/release if we do nothing. > > You can check on YouTube by right clicking the playing video and > selecting "Stats for nerds" which should appear above the "About the > HTML5 player" option. If you see "DASH: yes" then you are now living in > the future. > > This affects YouTube but may also affect sites that use MSE with > WebM/VP9 but it could also affect sites that use MSE but fail to check > codec compatibility. > > Please file any (unfiled) issues you experience as blocking bug 1083588. > Don't expect it to be perfect and if you run into trouble you can set > media.mediasource.enabled to false in your about:config > > Anthony That's great news. Does it mean we can expect to see VP9 working in Firefox 37? Even on Linux? Cause as for Firefox 35 on UBuntu 14.10 I still MSE and VP9 disabled here: http://www.youtube.com/html5 Thanks. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: MSE WebM/VP9 enabled on nightly
On 2014年10月27日 18:30, Bobby Holley wrote: > This issue is off-topic for this thread. Please file a bug and CC a build > peer. > Sorry, will do. TIA > On Mon, Oct 27, 2014 at 10:06 AM, ishikawa wrote: > >> > Sorry for top-posting: >> > >> > The error mentioned about the missing files was again observed on a PC >> > which has C-C tree refreshed this morning. >> > >> > The error for one of the file is as follows: >> > >> > make[4]: *** No rule to make target >> > >> > '/new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/media/libvpx/vp9/decoder/vp9_thread.c', >> > needed by 'vp9_thread.o'. Stop. >> > make[4]: *** Waiting for unfinished jobs >> > GrContext.o >> > /new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/config/recurse.mk:74: >> > recipe for target 'media/libvpx/target' failed >> > >> > If I recall correctly, after fixing this bug by temporarily copying >> > vp9_thread.o from |common| directory, >> > I would get error of the other missing file. >> > >> > I am not sure why others don't encounter this bug. Maybe different >> > mozconfig >> > setup. >> > >> > TIA >> > >> > On 2014年10月25日 14:00, ISHIKAWA,chiaki wrote: >>> > > On 2014/10/24 13:46, Anthony Jones wrote: > >> I just wanted to give a heads up to everyone that we enabled Media > >> Source Extensions on nightly for WebM/VP9. This brings Adaptive > >> Streaming capability to Firefox video playback. The feature is not > >> complete so the pref will automatically turn off when it gets to > >> beta/release if we do nothing. > >> > >> You can check on YouTube by right clicking the playing video and > >> selecting "Stats for nerds" which should appear above the "About the > >> HTML5 player" option. If you see "DASH: yes" then you are now living > >> in > >> the future. > >> > >> This affects YouTube but may also affect sites that use MSE with > >> WebM/VP9 but it could also affect sites that use MSE but fail to check > >> codec compatibility. > >> > >> Please file any (unfiled) issues you experience as blocking bug > >> 1083588. > >> Don't expect it to be perfect and if you run into trouble you can set > >> media.mediasource.enabled to false in your about:config > >> > >> Anthony >>> > > >>> > > >>> > > Hi, >>> > > >>> > > Just reporting what I observed after a source refresh half a day ago. >>> > > >>> > > I noticed during C-C TB compilation >>> > > a file under common needs to be copied to encoder, another one to >>> > > decoder >>> > > directory . >>> > > I am talking about files below these directories. >>> > > mozilla/media/libvpx/vp9/{common,encoder,decoder} >>> > > >>> > > But since C-C was in such a disarray in terms of compilation lately, >> > etc., >>> > > and the source was refreshed just before this compilation effort, >>> > > I am not sure if the configuration was quite correct. >>> > > I failed to write down a memo exactly which files were >>> > > copied. I thought I was logging it using script, but did not. >>> > > I clobbered and then tried to see how it would work out, and then was >>> > > side-tracked by bug 1088497 >>> > > >>> > > I can compare the directory to report what files were copied >>> > > if no such bugs have been filed yet and you are not aware of the issue. >>> > > (I tried to see which one by timestamp, but python client.py checkout >>> > > seems to give same timestamps to all the files and so I am not sure >>> > > which >>> > > ones were copied. cp or Emacs's filecopy seems to preserve the >>> > > timestamp. >>> > > That is good sometimes, but annoying sometimes.) >>> > > >>> > > But then again, I am not entirely sure if it was a temporal hiccup after >>> > > the source refresh. >>> > > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: MSE WebM/VP9 enabled on nightly
This issue is off-topic for this thread. Please file a bug and CC a build peer. On Mon, Oct 27, 2014 at 10:06 AM, ishikawa wrote: > Sorry for top-posting: > > The error mentioned about the missing files was again observed on a PC > which has C-C tree refreshed this morning. > > The error for one of the file is as follows: > > make[4]: *** No rule to make target > > '/new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/media/libvpx/vp9/decoder/vp9_thread.c', > needed by 'vp9_thread.o'. Stop. > make[4]: *** Waiting for unfinished jobs > GrContext.o > /new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/config/recurse.mk:74: > recipe for target 'media/libvpx/target' failed > > If I recall correctly, after fixing this bug by temporarily copying > vp9_thread.o from |common| directory, > I would get error of the other missing file. > > I am not sure why others don't encounter this bug. Maybe different > mozconfig > setup. > > TIA > > On 2014年10月25日 14:00, ISHIKAWA,chiaki wrote: > > On 2014/10/24 13:46, Anthony Jones wrote: > >> I just wanted to give a heads up to everyone that we enabled Media > >> Source Extensions on nightly for WebM/VP9. This brings Adaptive > >> Streaming capability to Firefox video playback. The feature is not > >> complete so the pref will automatically turn off when it gets to > >> beta/release if we do nothing. > >> > >> You can check on YouTube by right clicking the playing video and > >> selecting "Stats for nerds" which should appear above the "About the > >> HTML5 player" option. If you see "DASH: yes" then you are now living in > >> the future. > >> > >> This affects YouTube but may also affect sites that use MSE with > >> WebM/VP9 but it could also affect sites that use MSE but fail to check > >> codec compatibility. > >> > >> Please file any (unfiled) issues you experience as blocking bug 1083588. > >> Don't expect it to be perfect and if you run into trouble you can set > >> media.mediasource.enabled to false in your about:config > >> > >> Anthony > > > > > > Hi, > > > > Just reporting what I observed after a source refresh half a day ago. > > > > I noticed during C-C TB compilation > > a file under common needs to be copied to encoder, another one to decoder > > directory . > > I am talking about files below these directories. > > mozilla/media/libvpx/vp9/{common,encoder,decoder} > > > > But since C-C was in such a disarray in terms of compilation lately, > etc., > > and the source was refreshed just before this compilation effort, > > I am not sure if the configuration was quite correct. > > I failed to write down a memo exactly which files were > > copied. I thought I was logging it using script, but did not. > > I clobbered and then tried to see how it would work out, and then was > > side-tracked by bug 1088497 > > > > I can compare the directory to report what files were copied > > if no such bugs have been filed yet and you are not aware of the issue. > > (I tried to see which one by timestamp, but python client.py checkout > > seems to give same timestamps to all the files and so I am not sure which > > ones were copied. cp or Emacs's filecopy seems to preserve the timestamp. > > That is good sometimes, but annoying sometimes.) > > > > But then again, I am not entirely sure if it was a temporal hiccup after > > the source refresh. > > > > Just an observation. > > > > TIA > > > > > > > > TIA > > > ___ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: MSE WebM/VP9 enabled on nightly
Sorry for top-posting: The error mentioned about the missing files was again observed on a PC which has C-C tree refreshed this morning. The error for one of the file is as follows: make[4]: *** No rule to make target '/new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/media/libvpx/vp9/decoder/vp9_thread.c', needed by 'vp9_thread.o'. Stop. make[4]: *** Waiting for unfinished jobs GrContext.o /new-hd1/extra/ishikawa/TB-3HG/NEW-COMMSRC/mozilla/config/recurse.mk:74: recipe for target 'media/libvpx/target' failed If I recall correctly, after fixing this bug by temporarily copying vp9_thread.o from |common| directory, I would get error of the other missing file. I am not sure why others don't encounter this bug. Maybe different mozconfig setup. TIA On 2014年10月25日 14:00, ISHIKAWA,chiaki wrote: > On 2014/10/24 13:46, Anthony Jones wrote: >> I just wanted to give a heads up to everyone that we enabled Media >> Source Extensions on nightly for WebM/VP9. This brings Adaptive >> Streaming capability to Firefox video playback. The feature is not >> complete so the pref will automatically turn off when it gets to >> beta/release if we do nothing. >> >> You can check on YouTube by right clicking the playing video and >> selecting "Stats for nerds" which should appear above the "About the >> HTML5 player" option. If you see "DASH: yes" then you are now living in >> the future. >> >> This affects YouTube but may also affect sites that use MSE with >> WebM/VP9 but it could also affect sites that use MSE but fail to check >> codec compatibility. >> >> Please file any (unfiled) issues you experience as blocking bug 1083588. >> Don't expect it to be perfect and if you run into trouble you can set >> media.mediasource.enabled to false in your about:config >> >> Anthony > > > Hi, > > Just reporting what I observed after a source refresh half a day ago. > > I noticed during C-C TB compilation > a file under common needs to be copied to encoder, another one to decoder > directory . > I am talking about files below these directories. > mozilla/media/libvpx/vp9/{common,encoder,decoder} > > But since C-C was in such a disarray in terms of compilation lately, etc., > and the source was refreshed just before this compilation effort, > I am not sure if the configuration was quite correct. > I failed to write down a memo exactly which files were > copied. I thought I was logging it using script, but did not. > I clobbered and then tried to see how it would work out, and then was > side-tracked by bug 1088497 > > I can compare the directory to report what files were copied > if no such bugs have been filed yet and you are not aware of the issue. > (I tried to see which one by timestamp, but python client.py checkout > seems to give same timestamps to all the files and so I am not sure which > ones were copied. cp or Emacs's filecopy seems to preserve the timestamp. > That is good sometimes, but annoying sometimes.) > > But then again, I am not entirely sure if it was a temporal hiccup after > the source refresh. > > Just an observation. > > TIA > > > > TIA > ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: MSE WebM/VP9 enabled on nightly
On 2014/10/24 13:46, Anthony Jones wrote: I just wanted to give a heads up to everyone that we enabled Media Source Extensions on nightly for WebM/VP9. This brings Adaptive Streaming capability to Firefox video playback. The feature is not complete so the pref will automatically turn off when it gets to beta/release if we do nothing. You can check on YouTube by right clicking the playing video and selecting "Stats for nerds" which should appear above the "About the HTML5 player" option. If you see "DASH: yes" then you are now living in the future. This affects YouTube but may also affect sites that use MSE with WebM/VP9 but it could also affect sites that use MSE but fail to check codec compatibility. Please file any (unfiled) issues you experience as blocking bug 1083588. Don't expect it to be perfect and if you run into trouble you can set media.mediasource.enabled to false in your about:config Anthony Hi, Just reporting what I observed after a source refresh half a day ago. I noticed during C-C TB compilation a file under common needs to be copied to encoder, another one to decoder directory . I am talking about files below these directories. mozilla/media/libvpx/vp9/{common,encoder,decoder} But since C-C was in such a disarray in terms of compilation lately, etc., and the source was refreshed just before this compilation effort, I am not sure if the configuration was quite correct. I failed to write down a memo exactly which files were copied. I thought I was logging it using script, but did not. I clobbered and then tried to see how it would work out, and then was side-tracked by bug 1088497 I can compare the directory to report what files were copied if no such bugs have been filed yet and you are not aware of the issue. (I tried to see which one by timestamp, but python client.py checkout seems to give same timestamps to all the files and so I am not sure which ones were copied. cp or Emacs's filecopy seems to preserve the timestamp. That is good sometimes, but annoying sometimes.) But then again, I am not entirely sure if it was a temporal hiccup after the source refresh. Just an observation. TIA TIA ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
MSE WebM/VP9 enabled on nightly
I just wanted to give a heads up to everyone that we enabled Media Source Extensions on nightly for WebM/VP9. This brings Adaptive Streaming capability to Firefox video playback. The feature is not complete so the pref will automatically turn off when it gets to beta/release if we do nothing. You can check on YouTube by right clicking the playing video and selecting "Stats for nerds" which should appear above the "About the HTML5 player" option. If you see "DASH: yes" then you are now living in the future. This affects YouTube but may also affect sites that use MSE with WebM/VP9 but it could also affect sites that use MSE but fail to check codec compatibility. Please file any (unfiled) issues you experience as blocking bug 1083588. Don't expect it to be perfect and if you run into trouble you can set media.mediasource.enabled to false in your about:config Anthony ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform