Enfold or Slider Revolution conflict showing Vimeo video in slider

I have an issue resulting in a huge error log file. It’s significant as the most recent error log I deleted was upwards of 17 GB and increased to that size quickly. When I delete the file, it quickly grows again.
I’m running the current version of all plugins and the theme. I’ve built out a dev environment that includes Enfold, a Child, and Slider Revolution only. This way, the issue is isolated. This environment also was a proof case to show it is not related to any other plugin. It’s either the theme or Slider Revolution. (This issue is happening with two sites with the same setup, playing a Vimeo video.)
Please visit http://slide.spidercreations.net, take a look at the Console log errors and you’ll see the issue. I’m using Slider Revolution to display a looping Vimeo video on an Enfold theme. Normally this has not been an issue. Yesterday, we noticed a huge error_log file in the root of the website. Resulted in some space issues on the server and somehow it broke the database connection. (Not sure it is connected, but that’s what happened.)
If I switch from a Vimeo video to a different slider with just rotating image slides, the console errors go away. Seeing this is how I narrowed the issue down to Vimeo…
For the Vimeo ID in the slider settings, I’ve tried both 283786395?loop=1, and just 283786395. (Previously I needed the ?loop=1 to get the video to loop, but that may no longer be needed.

This is what the error log is full of as an example:

https://[website]/wp-content/uploads/dynamic_avia/avia-footer-scripts-0e59c074e6a135e47ab71ef11d02d98f---5e4b356ca4bc6.js
else if(e=='ready'&&t){i.call(null,r)};return a},removeEvent:function(e){if(!this.element){return!1};var t=this,i=t.element,o=i.id!==''?i.id:null,a=u(e,o);if(e!='ready'&&a){n('removeEventListener',e,i)}}};function n(e,i,t){if(!t.contentWindow.postMessage){return!1};var n=JSON.stringify({method:e,value:i});t.contentWindow.postMessage(n,o)};function a(e){var i,r;try{i=JSON.parse(e.data);r=i.event||i.method}catch(p){};if(r=='ready'&&!t){t=!0};if(!(/^https?:\/\/player.vimeo.com/).test(e.origin)){return!1};if(o==='*'){o=e.origin};var u=i.value,d=i.data,a=a===''?null:i.player_id,s=l(r,a),n=[];if(!s){return!1};if(u!==undefined){n.push(u)};if(d){n.push(d)};if(a){n.push(a)};return n.length>0?s.apply(null,n):s.call()};function s(i,t,o){if(o){if(!e[o]){e[o]={}};e[o][i]=t}

Here is a screenshot of the console – https://pasteboard.co/IWP4NlY.jpg

Can you please take a look? I also have the Theme Punch looking at this issue.
Using the most current versions of both, and removing any custom CSS does not solve the issue. (The development environment is clean installs.)
I also have Theme Punch looking at this and they have the same information you do. Both of you have admin access to the dev environment.

Steve