Post

2 followers Follow
0
Avatar

r31 has been released

Our r31 has been moved from developer preview to the officially released version. This means that it is a fully functional new revision that you can check out and use if you are interested in any of the new features it brings.

I will mention only the most important ones, however the list with more details can be found within our documentation here.

 

If you are using v1, the r31 will allow you to leave your code as is and actually fully utilize v2 in the background. This option is great for anyone that does not have a team of developers that can help with the switch to v2.

We do of course recommend switching to v2 instead when you get a chance since that would make you remove the connector layer that translates v1 to proper v2 codes for you.

 

While most of the changes done are mentioned on the above page here are some of the interesting ones:

  1. Our player now supports subtitles based on the audio transcription within your account.
  2. We heard your requests and made `processing` and `processed` events fire always.
  3. Simulators can be run efficiently for both recording and uploads (not over Flash)
  4. We have added new parameters to help you force the orientation of the mobile device
  5. We also made it possible to force the resolution*
  6. Accessibility is something we want to make better. As such we have made it possible for anyone to go through the player or recorder and utilize their controls.

* Some browser versions might actually require us to specify one of the resolutions in which case our system matches your input with the browser requirements / limitations and uses the best match.

Have you already tried it? Let us know how much you like it in the comments :)

Bane

Please sign in to leave a comment.

4 comments

0
Avatar

I've been unable to use r31. My 'verify' code doesn't seem to fire with it. I can use r30 and all is fine. I've even double-checked by placing a simple alert('test') in the verify function but that fails to fire. Can you see whats wrong?

I use the verified function to show the submit button when video is ready.

Below are the relevant code chunks

{!! HTML::style('https://assets-cdn.ziggeo.com/v2-r31/ziggeo.css') !!}
{!! HTML::script('https://assets-cdn.ziggeo.com/v2-r31/ziggeo.js') !!}

My submit button (hidden on page load)

<button type="submit" class="btn btn-primary  btn-block"  id="sendvideo" name="sendvideo" >Send to Kijiji</button>




        <ziggeorecorder
            ziggeo-custom-covershots
            ziggeo-early-rerecord
            id="ziggeo-recorder"
            ziggeo-manualsubmit="true"
            title="mytitle"
            description="mydescription"
            expiration-days="14">
        </ziggeorecorder>

    
    
    
<script type="text/javascript">
    
    window.onload=function(){
    document.getElementById("sendvideo").style.display='none';
    }
    
    var app = new ZiggeoApi.V2.Application({
        token:"aXXXXXXXXXXXXXXX",
        webrtc_streaming: true
    });

    ZiggeoApi.Events.on("system_ready", function() {
        var element = document.getElementById('ziggeo-recorder');
        var recorder = ZiggeoApi.V2.Recorder.findByElement(element);
        
        recorder.on('verified', function() {
            document.getElementById("sendvideo").style.display='inline';
            document.getElementById("videotoken").value = "" + recorder.get('video') + "";
          });

    });
</script>

Todd Thompson 0 votes
0
Avatar

I see. There is a small part of code that would need to be switched for everything to work just fine.

Based on the code I believe that your tests were done over v1-stable/ziggeo.js and v2-r31/ziggeo.js.

The difference is in the revision, however also in the v1- and v2- file prefix. What happens is that v1 has codes for v1 and v2 while v2- prefixed revisions hold only v2 codes.

Because of this the v1 code like

ZiggeoApi.Events.on("system_ready", function() 

would not work - since v2 does not recognize that v1 code.

Hope this makes sense, of course lets see the good stuff - the code that will make it work :)

You have this code:

var app = new ZiggeoApi.V2.Application({
token:"aXXXXXXXXXXXXXXX",
webrtc_streaming: true
});

Now we will use it. I suggest changing "app" to "ziggeo_app" or another such name, since that will make it easier to recognize it in the code, especially on more complex projects.

Also just to mention, "webrtc_streaming" will make uploads faster, however protocol will subject the quality to the network bandwidth. This is one of the implementations related to live recording and playback where that is considered as needed. If you require quality all the time, then I would suggest turning it to false.

* Just mentioning it since it is good factor to consider.

OK, now really to the codes :)

Change the system_ready event into the following code:

    //info: https://ziggeo.com/docs/sdks/javascript/browser-interaction/application-events
    app.on("ready", function() {
        var element = document.getElementById('ziggeo-recorder');
        var recorder = ZiggeoApi.V2.Recorder.findByElement(element);
        
        recorder.on('verified', function() {
            document.getElementById("sendvideo").style.display='inline';
            document.getElementById("videotoken").value = "" + recorder.get('video') + "";
          });

    });

* As you can see the change is only at the very top, all the rest should be as it was and work just fine.

This should work now, of course please let us know how it goes :)

Bane 0 votes