Manually submit the video after record a video using Ziggeo recorder

Lam H Nguyen

• January 07, 2022 06:34

Hi Ziggeo team,

Could you please inform me if there is a way to record a video using Ziggeo recorder without uploading the video immediately after clicking on the Stop button? We would like the user to view the playbacks and re-record the video on local before uploading the video.

Will localplayback help to solve this? If yes, how do we upload the recorded video using localplayback? Please note that we are using react-ziggeo: 4.5.0 with ziggeo-client-sdk: 2.36.12.

0

• 

  Carlos Sillero

  • January 07, 2022 22:57

  Hi Lam,

  Thanks for your query.

  Unfortunately  there is no method to save the video without uploading first to our Servers.

  The best practice would be to use  the 'localplayback' parameter which allows the user to check the video while its uploaded in the background, but it also shows the redo option with it. So if the user is not satisfied, it will allow them to re-record and you can also control the number of re-attempts you want to give to the user. We consider only the final recording that we receive for invoicing purpose. 

  If you need help adding the 'localplayback' parameter to your App let me know.

   

   

  0
• 

  Lam H Nguyen

  • January 09, 2022 16:08
  • Edited

  Hi Carlos,

  Thank you for the response. Luckily we've experienced the 'localplayback' parameter.

  1. Is there any approach that we can use to detect or even display the uploading, verifying, and processing progress when using the 'localplayback' parameter? It is required to avoid the users interrupting the uploading process.

  2. If I redo the video while my first attempt video is being uploaded, how do I detect the latest attempt is completely uploaded while using the 'localplayback' parameter?

  0
• 

  Bane

  • January 10, 2022 05:50

  Hi Lam,

  1. That should be easy to do. You can hook into our events: https://ziggeo.com/docs/sdks/javascript/browser-interaction/events and listen to: uploading, verified and processing or processed events.

  I do wish to mention that once the verified event fires, you do not really have to wait for processing events, it is fine if you completely remove the recorder at that time, or if you redirect your users to another page. Once verified the processing will happen regardless of what happens on page.

  2. In terms of the second point, that should be simple to do, however would depend if I understood you correctly. If you wish to just stop your code within the other events working, you could listen to the rerecord event. Once it fires, you know that your user discarded the previous video and they are about to record a new one.

  How this is implemented greatly depends on your overall code, however one very simple way of doing it would be to just keep a variable in global scope and have all events check on it as they are running to see if they should stop or not.

  0
• 

  Lam H Nguyen

  • January 18, 2022 09:43

  Hi Bane.

  We have implemented the localplayback parameter. However, using this param will not return the duration of the latest video after either the videoattach or recordersubmit requested.

  How can we get the latest duration of the latest video (if it is re-recorded)?

  

  0
• 

  Bane

  • January 18, 2022 17:16

  Hi Lam,

  The r39 should refresh the cached values at every stage when we get some data about the video back from the servers. This should make it possible to get the new data even if it is a re-recording.

  That said, I should point out that in some cases we can not safely know the the length until the video is processed on the servers.

  The best case would always be to listen to the verified event, however if your customer is still on page and processing event finish, you should at that time have the info about the duration.

  This is of course true only for r39 since prior revisions would not always update the video data even if fresh data was received in some response.

  0
• 

  Lam H Nguyen

  • February 07, 2022 09:40

  Hi Bane,

  As we read in this post, r39 will be pointed as the new stable revision https://ziggeo.canny.io/changelog/2022-january-update.

  Could you please inform us which version will be used in ziggeo-client-sdk and when will r39 will be updated to the react-ziggeo?

  0
• 

  Bane

  • February 07, 2022 23:45

  Hi Lam,

  You are correct, we are now using r39 as stable. In React that is determined by

  https://github.com/Ziggeo/react-ziggeo/blob/master/package.json#L76

  At the moment that is:

  ```

  "ziggeo-client-sdk": "2.36.12"

  ```

  You could manually change that value to use r39 if you wanted (or any other revision really) and use it.

  You can see more details about the change here: https://github.com/Ziggeo/react-ziggeo#upgrade-ziggeo-sdk

  The React SDK has already been updated with the ZiggeoAudioRecorder and ZiggeoAudioPlayer components, so if you update to r39 you will be able to use them right away :)

  0
• 

  Natasha Calleia

  • February 10, 2022 15:46

  Hi Lam, I'm following up to let you know that we released a new version of react-ziggeo (4.6.0) which was built using r39. :)

  0
• 

  Lam H Nguyen

  • February 10, 2022 17:34

  Hi Natasha,

  That is great to know. Thank you for updating me. 

  0

Please sign in to leave a comment.