I had to request a refund (and thus unable to submit a review and have to simply put this in the comments) for my multi\u002Dcode purchase for several reasons:\u000a\u000a1) Several recordings were \u0022lost\u0022 to the servers and even though support worked for two+ weeks, they were unable to recover the recordings. So with \u0022semi\u002Dreliable\u0022 recordings, there was no way I could trust my webinars to the system.\u000a2) While the CNAME worked great, I had to \u0022hack\u0022 the Chrome Extension (extract the code / fork the code / add my own domain to the authorized list / repackage the extensions / and reinstall the forked extension) in order to get it to work.\u000a3) The inability of people to come to the webinars on any browser other than Chrome to have a positive experience. Firefox and Safari have major UI and connection issues for participants.\u000a4) I never tested meetings or any of the other options, I just needed it for webinars where I share a screen and teach live coding. (not that demanding... but still ran into issues.)\u000a\u000aOn the other hand, the support always seemed to be on top of it and following up on issues. I did like the \u0022calendar view\u0022 but clicking on a list of attendees made some seriously impossible to navigate UI windows to pop up. I had high hopes for this product, but couldn\u0027t get past the lost recordings which wasted my time having to go re\u002Drecord and process. I do use other redundant recording solutions, but the Chrome Extension for VidThere interfered with the backup recordings so I would have to rely on their own recordings.

Question

I had to request a refund (and thus unable to submit a review and have to simply put this in the comments)  for my multi\u002Dcode purchase for several reasons:\u000a\u000a1) Several recordings were \u0022lost\u0022 to the servers and even though support worked for two+ weeks, they were unable to recover the recordings.  So with \u0022semi\u002Dreliable\u0022 recordings, there was no way I could trust my webinars to the system.\u000a2) While the CNAME worked great, I had to \u0022hack\u0022 the Chrome Extension (extract the code / fork the code / add my own domain to the authorized list / repackage the extensions / and reinstall the forked extension) in order to get it to work.\u000a3) The inability of people to come to the webinars on any browser other than Chrome to have a positive experience. Firefox and Safari have major UI and connection issues for participants.\u000a4) I never tested meetings or any of the other options, I just needed it for webinars where I share a screen and teach live coding. (not that demanding... but still ran into issues.)\u000a\u000aOn the other hand, the support always seemed to be on top of it and following up on issues. I did like the \u0022calendar view\u0022 but clicking on a list of attendees made some seriously impossible to navigate UI windows to pop up.  I had high hopes for this product, but couldn\u0027t get past the lost recordings which wasted my time having to go re\u002Drecord and process.  I do use other redundant recording solutions, but the Chrome Extension for VidThere interfered with the backup recordings so I would have to rely on their own recordings.

Vidthere

Share Vidthere

Related questions