•   
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 12
  •   
chromecast
#76
(2013-07-28, 16:09)seamus5 Wrote:
(2013-07-28, 15:44)bubbleguuum Wrote:
(2013-07-28, 13:20)seamus5 Wrote: I've been trying to get this working on windows 7, I presume the issue is that the relative directories are structured for a linux install.

Anyone successfully used windows 7 and have some command line parameters to share?

Provided you installed all app.py dependencies, copy app.py where chrome.exe is installed, go to that directory, then:

python app.py <local ip> --chrome chrome.exe --name "LolCast receiver"

Perfect, that did the trick.

Anybody have any luck getting the play music app to work? Everything seems to work ok in youtube, but the cast icon doesn't seem to show in music for some reason.

The only app that works is youtube. leapcast is missing some stuff for Play Music (and SDK samples) to discover it and show the cast button. And even if it was discovered, it would still be missing some bits to work.
Reply
#77
Google Chromecast Root & Secure Boot Exploit




Source = http://www.engadget.com/2013/07/28/chrom...ideo-hack/
Reply
#78
That was quick Smile
Reply
#79
Well the need of chrome makes it a nogo for implementing it in XBMC. The original Google API is javascript (this wouldn't work out either because XBMC has no javascript interpreter). But as it seems with that python thingy it would be doable. But as said - the chrome dependency is a blocker.
AppleTV4/iPhone/iPod/iPad: HowTo find debug logs and everything else which the devs like so much: click here
HowTo setup NFS for Kodi: NFS (wiki)
HowTo configure avahi (zeroconf): Avahi_Zeroconf (wiki)
READ THE IOS FAQ!: iOS FAQ (wiki)
Reply
#80
https://github.com/entertailion/DIAL

Seems like an interesting project.
Reply
#81
(2013-07-29, 11:03)Memphiz Wrote: Well the need of chrome makes it a nogo for implementing it in XBMC. The original Google API is javascript (this wouldn't work out either because XBMC has no javascript interpreter). But as it seems with that python thingy it would be doable. But as said - the chrome dependency is a blocker.
What is the problem with chrome? Is it licensing? Is it unavailability on some platforms? Can it's functionality be reverse engineered in an open source way?
If I have helped you or increased your knowledge, click the 'thumbs up' button to give thanks :) (People with less than 20 posts won't see the "thumbs up" button.)
Reply
#82
Implementing the Chrome browser just to display a photo, or stream from a URL, seems a little excessive - hopefully there's a more lightweight solution that can be made to work without the Chrome baggage. If it's a dependency on Javascript, the v8 Engine is available separately, however most plugins already manage to access websites without the need for a full-blown JS engine.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#83
Actually, it doesn't rely on Chrome. It is actually a modified version of Google TV/Android

http://blog.gtvhacker.com/2013/chromecas...by-google/
http://www.engadget.com/2013/07/28/chrom...ideo-hack/

From their website:

"Is it really ChromeOS?

No, it’s not. We had a lot of internal discussion on this, and have concluded that it’s more Android than ChromeOS. To be specific, it’s actually a modified Google TV release, but with all of the Bionic / Dalvik stripped out and replaced with a single binary for Chromecast. Since the Marvell DE3005 SOC running this is a single core variant of the 88DE3100, most of the Google TV code was reused. So, although it’s not going to let you install an APK or anything, its origins: the bootloader, kernel, init scripts, binaries, are all from the Google TV."
Reply
#84
(2013-07-30, 04:30)MaliciousBoy Wrote: Actually, it doesn't rely on Chrome. It is actually a modified version of Google TV/Android

Chrome is a browser, Chrome OS is something else entirely. So far, the python implementations of Chromecast have had a dependency on Chrome (the browser) - not sure why, exactly, but maybe because it's loading web pages with embedded media (h264/vp8 streams etc.).
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Reply
#85
Chromecast is working albeit buggily with Google TV.
Reply
#86
There is now some more info on the decoding capabilities of the chip (named ARMADA 1500-mini):

-H.264 high profile @ Level 4.1, 4.2 and 5
-VC-1
-MPEG2/4
-WMV9 MP
-VP6/8 SD & HD
-DIVX-HD

-Dolby Digital (AC3)
-Dolby Digital Plus
-Dolby TrueHD
-DST HD-MA
-DTS digital surround
-DTS-HD
-AAC/AAC+
-WMA
-MPEG1 Layer 1/2/3, MPEG2 Layer 2, AC3, E-AC3, HE-AAC v1L2 & v2L4, MPEG2-LC
-MP3, MPEG audio
-AC3 & DTS encode over SPDIF

source
Reply
#87
(2013-07-31, 14:32)Mntz Wrote: There is now some more info on the decoding capabilities of the chip (named ARMADA 1500-mini):

-H.264 high profile @ Level 4.1, 4.2 and 5
-VC-1
-MPEG2/4
-WMV9 MP
-VP6/8 SD & HD
-DIVX-HD
...

Can anyone confirm if these actually work on the Google ChromeCast dongle?
It costs $2 (non-negotiable) to license an MPEG2 decoder, so I'd be surprised if that can be accomodated in a $35 device.
The audio codecs are also about $1 each.

I'm guessing the SoC can support these formats, but not all are enabled in the ChromeCast dongle.
Reply
#88
Google already signed with MPEG LA about licensing those codecs for it's product (be it ChromeOS, Chrome, Chromcast, Android, etc...), Marvell has signed also, so the license issue has been solved long time ago.

However, you cannot play MPEG-2 files from Chrome browser.

MKV files work, but no audio (at least on files I have here) and no SRT subtitles..
Reply
#89
I think Mpeg2 (MpegLA) patents has expried, any comments?
Reply
#90
Looks like Google already patched the "exploid" so root is no longer possible (through that method)
http://forum.xda-developers.com/showthre...?t=2387392
Reply
  •   
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 12
  •   
 
Thread Rating:
  • 6 Vote(s) - 3 Average



Logout Mark Read Team Forum Stats Members Help
chromecast36