Hi Philip,
Unfortunately I am not that familiar with the creation of the plugin to be able to give you precise details if something would not be possible. Based on the conversations so far and what I saw, it should be possible to do it.
In general our system can be contacted over REST API in order to get the list of videos, get data about the video, or anything else just the same. Now while in my tests so far I did manage to communicate with our servers, the problem for me is that I was not able to find a cross over from the API to the actual Bubble interface, nor to get events from our embeddings to fire Bubble events - which I believe @Bubbleboy was able to do.
So if you know how to combine the events that fire on our embedding (like “verified”) to be detected by Bubble you are golden as you should be able to do anything.
In general if you were adding the pure HTML code to your Bubble app you could specify the hd profile yourself as well.
Example (in v2) would be:
<ziggeorecorder
ziggeo-width="640"
ziggeo-height="480"
ziggeo-video-profile="123456789">
</ziggeorecorder>
- of course if your token was 123456789 and in case you were mentioning key, it would need an underscore in front of it just as shown in the v1 code you posted.
PS: I just check out the create your plugin and looking at it I presume that something like this would be needed for a base:
<link rel="stylesheet" href="//assets-cdn.ziggeo.com/_*_VERSION_*_-_*_REVISION_*_/ziggeo.css" />
<script src="//assets-cdn.ziggeo.com/_*_VERSION_*_-_*_REVISION_*_/ziggeo.js"></script>
<script>
ZiggeoApi.V2.Application({
token:"_*_APPLICATION TOKEN_*_",
webrtc: _*_USE WEBRTC (BOOL)_*_,
webrtc_streaming: _*_USE WEBRTC STREAMING (BOOL)_*_,
auth: _*_USE AUTH TOKENS (BOOL)_*_
});
</script>
- Details:
_*_VERSION_*_ - there is v1 and v2 ziggeo.js file. v1 holds both v1 and v2 codes while v2 holds only v2 app codes
_*_REVISION_*_ - Bubble to Ziggeo plugin is using our stable revision. This is recommended for production, however I guess that you would want to allow people to choose their own revision.
https://ziggeo.com/docs/sdks/javascript/version-history
_*_APPLICATION TOKEN_*_ - application token
_*_USE WEBRTC (BOOL)_*_ - if WebRTC should be used. For v2 embeddings this is true by default and recommended option (experience and future wise).
_*_USE WEBRTC STREAMING (BOOL)_*_ - available in never revisions only (not in stable) - data is uploaded to our servers during recording, making uploading seem faster and improving overall experience (we do not yet have live streaming however working on that 
).
_*_USE AUTH TOKENS (BOOL)_*_ - by default we go with minimal approach, so auth tokens are not enabled for v2, so you need to specifically set them as enabled when creating v2 app.
Now the reason why I would recommend the above is because v2 app is much better approach just as using v2 embeddings is. Now of course, if someone was to choose to use v1 instead (as many are still using), you would need to use a different approach:
<link rel="stylesheet" href="//assets-cdn.ziggeo.com/_*_VERSION_*_-_*_REVISION_*_/ziggeo.css" />
<script src="//assets-cdn.ziggeo.com/_*_VERSION_*_-_*_REVISION_*_/ziggeo.js"></script>
<script>
ZiggeoApi.token = "_*_APPLICATION TOKEN_*_";
ZiggeoApi.Config.webrtc = _*_USE WEBRTC (BOOL)_*_;
</script>
- it has auth tokens turned on by default and it does not have WebRTC streaming option available.
** I would still suggest using v2 app and embeddings for any new developments
Hope this helps for further discussion and just to mention, we would offer referral bonus partnership from our side for anyone building the plugin, and of course would help with details needed from our side
Regards,
Bane
