3 ms·
I'll be interested to see how this all works once I get my devices. Because its not relying on the processing power of the device in question, I wonder why it
by ChikkaChiChi 13y ago
I'll be interested to see how this all works once I get my devices. Because its not relying on the processing power of the device in question, I wonder why it wouldn't work on any device running Chrome.
I did notice during the Presser that the Chrome browser had two cast icons; one in the bottom right he keyed in on, and one where normal extensions go.
- dragonwriter 13y ago> I'll be interested to see how this all works once I get my devices. Because its not relying on the processing power of the device in question, I wonder why it wouldn't work on any device running Chrome. As others have pointed out on the thread, the limiting factor is probably the need to encode video on the sending device for the casting Chrome tabs feature, which probably is going to be an issue on low-end Chromebooks (but, I would imagine, would also be a feature on low-end devices running Windows Chrome.) It may be that it relies on Chrome features that don't exist on low-end chromebooks (and, if it involves licensed technology, it may be something that isn't licensed for low-end Chromebooks.)
- ChikkaChiChi 13y agoIf when in local mode its leaving the rendering up to the initiating device, I can definitely see that being a limiting factor. Perhaps the reason it's in 'beta' then is that DIAL doesn't have the provisions in place for low end unit to unit, low latency performance. Hopefully enabling this on the lower end devices amps up the usefulness even further.