Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Why do we need to register for a new "appid"?

Given the relationship between the sender and receiver components of Chromecast in JW Player terms being a one-to-one relationship, and with JW having built and registered the receiver application already, I would expect the "appid" to simply be the JW application ID and so this should be defaulted/hidden within the code.

The option to change it would only make sense if you wanted to use JW Player as a sender with a non-JW receiver...

James Herrieven

9 Community Answers

Up Down

Andrew

JW Player Support Agent  
-1 rated :

Hi James,

Technically, we are an application using Chromecast, however the player is coming from your own web space. As per Google’s requirements:
https://developers.google.com/cast/docs/registration
Websites do need to be registered with the Chrome extension and do function as the “Sender” portion.

Up Down

jherrieven

User  
0 rated :

Andrew

Where specifically is this stated on the page you are linking me to?

I must be missing something rather fundamental...

As I understand it, the registration process (which incidentally costs $5) is primarily for those *developers* who are interested in building and publishing a cast *receiver* application.

Presumably JW has done this and your receiver is what is downloaded to the chromecast dongle when a sender app sends your "appid" as a reference.

Your receiver will then take instructions from the initiating sender app - which in this case is JW Player 6.9.

Now... I've already registered with the Google Cast Developer SDK and created an application.

The application ID is available immediately. It isn't however published until the following conditions are met:

> Your receiver must be hosted on secure servers supporting https (thats the URL you claim can be anything)
> You must add details about at least one sender application
> You must add a title
> You must add a description
> You must add an icon

All of this is related to creating and publishing a receiver application. Not something a web user who whats to enable Chromecast through JW Player should need to worry about.

My application ID in no way relates to JW Player or the JW receiver. I highly doubt that adding my "appid" to a JW setup is going to initiate the JW player receiver on my target device...

(unless of course... its all smoke and mirrors on your part and your sender application - JW Player - is ignoring what I put in and is just using your JW "appid" instead... but that just wouldn't make sense...)

James

Up Down

ms

User  
0 rated :

James,

just use the generic Chromecast default Appid (https://developers.google.com/cast/docs/receiver_apps#default) if you don't require additional UI elements:

appid:"chrome.cast.media.DEFAULT_MEDIA_RECEIVER_APP_ID"

Mike

Up Down

jherrieven

User  
0 rated :

Mike

Quite simply, I should not be needing to create a receiver application - I should be using the feature rich JW one - and as a JW embedder this should be transparent to me!

For completeness: Doing what you suggested may work in that a video could be cast - but it would mean the JW Player in Chrome would be casting to my wrapper for the "pre-built receiver application hosted by Google that is designed for streaming your audio and video content... you cannot customize any of the UI." - which would not give me the additional JW features they have made a big point of promoting.

James


Up Down

Andrew

JW Player Support Agent  
0 rated :

Hi James,

I’ve reached out to our dev team about this for some more clarification. This is currently a temporary process based on Google’s request to ensure users are reading Chromecast’s terms of service. We will be able to generate an App ID in the future for all who wish to use Chromecast.

Also, I’ve also confirmed that you should not be using a default app ID for this.

Hopefully that clears some things up. :)

Up Down

jherrieven

User  
0 rated :

Hi Andrew

Thanks for the response, but I'm not really buying it!

You're suggesting that Google have requested that your customers pay $5 and register a receiver application - which is not only quite complex, but also completely pointless - just so they can be sure these customers are reading the terms of service - which actually only you as the SDK user and application provider are bound by?

The fact of the matter is the only way a JW Player embed (sender application) will download the registered JW Player receiver on the target Chromecast device is for the sender to use *your* registered receiver application ID - "567gh231" - when it first makes a session request.

I think it's important you get this straight given all the buzz around your Chromecast support.

James

Up Down

kenny

User  
0 rated :

Dude, just spend the 5 bucks and spend 5 minutes signing up. It's pretty easy.

Up Down

jherrieven

User  
0 rated :

Dude - you just wasted 5 bucks!

Up Down

jherrieven

User  
0 rated :

Apologies @kenny - I misread your post.

As I'd said previously, I've already spent my five bucks, registered and published an application (nothing to do with JW), so I know what's involved and it's not a five minute job.

The point... and *the* answer to my original question is this:

You don't need to do this at all - the "appid" you type in is irrelevant. It's ignored.

The JW sender part of the application replaces whatever you type in with the proper one. The one that corresponds to the registered JW receiver part of the application.

The rest is just smoke and mirrors.

This question has received the maximum number of answers.