Log in

[giladani]

Hi John,

I saw the new APIs that were released, and I wanted to make sure that I follow.
If I user
var pulisher = TB.initPublisher();


- When is the publisher 'ready' for me to connect him to the finish? Should I just listen to "accessAllowed"? Is that enough?
-I assume that I can use the same publisher to publishe session A, then unpublish session A and publish session B, is that correct?

Regarding the camera & mic testing:
- I noted the new APIs, this is great. but regarding camera testing: Can I trust the "devicesDetectedHandler" to provide a selected camera object (i.e. event.selectedCamera.status) to provide the correct camera status? I know that before when it was called from the device panel, it might have sent "unknown" status sometimes...


Thanks,
Gil.

[song]

Hi,

When you do var publisher = TB.initPublisher('divId'), you create a publishing window on the browser. This allows user to look at themselves and do necessary makeup, change webcam/audio settings, etc. Then when they are ready, you can do session.publish(publisher)

I would assume you have a button, so users click on it to connect when they are ready.
Yes that is correct. You can use that to publish to session A and to sessionB

You can trust devicesDetectedHandler. You might have gotten 'unknown' status if flash detected a device but did not know what it is.

[giladani]

Another question.... The new & old Apis for flash dialog events and allow/deny. Now connected to publisher instead of session, right?
But these events may dispatch befor I get the chance to register - so what happens if I don't register fast enough? I do plan to register as the first thing. Before detect devices.


Gil.

[giladani]

And... the publishH264 - this was per sessionConnected event, should't that be for a publisher now?

Gil.

[jtsai]

If you register right afterwards, then allow/deny events will always be on time to be called. We have code in the swf to make sure this happens. Also, for publishH264, since we built it off the previous publisher, it will wait until you join the session to display the information.

John

[giladani]

Hi John,

This is my code:

Code: Select all


 var publish_properties = {
         //reportMicLevels : true,
         publishAudio : true,
         microphoneEnabled : true,
         microphoneGain : 100,
         publishVideo : true,
         mirror : true,
         
         width:  cam_width,                 //156,
         height: (cam_width / 4) * 3 ,       //117,
         
         //encodedWidth : remote_cam_width,  // 1..640
         //encodedHeight : (remote_cam_width / 4) * 3,  // 1..640
         
         wmode : "opaque", // Needed for Faceboook
         style: {
            backgroundImageURI: Drupal.settings.open_tok.my_background_img
         }
   };
var publisher = TB.initPublisher(api_key, "myCam", publish_properties);
publisher.addEventListener("accessAllowed", accessAllowedHandler);

function accessAllowedHandler(event) {
      my.publisher.detectDevices();
}

function devicesDetectedHandler(event) {


   if (event.cameras.length < 1) {
       console.warn('No cameras');   
        return false;
    }
   console.log(event);
   console.log("camera is " + event.selectedCamera.status);
}



I do see myself in the camera, but I get 'inactive' state.

[giladani]

I think that I found the problem. If you call the detect devices right after "allow" handler, then it says the camera is inactive. If you just wait 1 second, it works.

Gil.

[giladani]

John,

Assuming that my publisher is not connected to any session.

What's the revert API call to TB.initPublisher() ??
How do I remove it from my DOM?

[ankur]

http://www.tokbox.com/opentok/api/tools ... ml#destroy