by acroyear » Mon Oct 24, 2016 1:44 pm
Yes, this is caused because Chrome in a recent update changed how Chromecast works, and code written for the older way (which used an extension, now permanently disabled by Google) stopped working. This happened *just* after the 6.0 upgrade. The app will need to be fixed to work with the new way (it may just be a tiny change, I couldn't say). I'm sure that's on the future "6.1" upgrade, but there's been little feedback on when that is coming.
--
Joe Shelby
http://subfiresuite.com/
http://subfireplayer.net/