Charmed Quark Systems, Ltd. - Support Forums and Community
Official 5.3 Beta Discussion Thread - Printable Version

+- Charmed Quark Systems, Ltd. - Support Forums and Community (
+-- Forum: General Discussion (
+--- Forum: Beta Discussions (
+--- Thread: Official 5.3 Beta Discussion Thread (/showthread.php?tid=10397)

RE: Thoughts for 5.3 - potts.mike - 10-13-2017

If you want to rework the media stuff please donÔÇÖt base it on the CQC repo. If people are into their media enough to seek out CQC then they are already invested in something and donÔÇÖt want to start over.

RE: Thoughts for 5.3 - Dean Roddey - 10-13-2017

Well, it wouldn't be 'based' on our repo. We'd still have the same standardized repo scheme. I was just talking about making ours such that people who aren't already committed to something else, and wanted the benefits of tight integration, would feel good using it. Remember, pro installation is the real goal ultimately, and we need that tight integration so that they can deliver a system that doesn't require manual intervention to manage media. If we could offer a solid media system and a solid automation system in one package, there could be a lot said for that.

That assumes that that sort of media management is still important to enough people of course. I kind of think it still is, at least the higher end where those pro installs would happen. And, even at the DIY level, I'd imagine that there are plenty of folks who just use J.River or DVD Profiler or My Movies because it was there, not because they are wedded to it.

Also, keep in mind that it wouldn't require starting over either, just a takeover of the existing content by our repo. Since we'd be updating it to deal cleanly with just files on disk, and we already know how to import metadata from those other systems, we could fairly easily convert them over.

RE: Thoughts for 5.3 - lesbib - 10-13-2017

I would add another vote for full Plex server support.

RE: Thoughts for 5.3 - dlmorgan999 - 10-14-2017

I also cast a vote for Plex server support.

RE: Thoughts for 5.3 - znelbok - 10-14-2017

Thinking outside the box a little (prompted by another post I made)

Microsoft have support for the Raspberry Pi with their Win10 IoT. What I would like to see is CQC using this somehow.

Use the Pi as a device server - it has USB ports and a serial port. A USB to serial adapter could be used for more serial ports.

It could also be used as a way to connect mic's for CQC voice.

Would be great to see it used as a dedicated IV viewer in some way.

RE: Thoughts for 5.3 - Dean Roddey - 10-15-2017

You should already be able to use it as an IV using WebRIVA I would think, right? It's extremely unlikely it would ever support the regular IV since I don't think that version of Win10 supports the Windows GUI, or it didn't back when this had been discussed earlier.

RE: Thoughts for 5.3 - znelbok - 10-15-2017

WebRIVA should work - I already have a system at work on a Pi starting chrome in fullscreen and launching a web page so its a no brainer for that. My thoughts were that you seem to code in c++ and that it may be possible to create a port for the Pi to create a dedicated IV.

I think I solved the Pi as a dedicated server issue - I use a bit of software called VirtualHere at work that creates a USB server on a Pi. Any PC can then connect to the USB device connected as if it were connected locally. This means a USB to serial, Kinect on USB or any other USB device can be connected via the network back to the master server. I should do a test at home and a write up about it here.

Anyway, my thought was more is there anyway to leverage the Win10 IoT for Pi with CQC.

RE: Thoughts for 5.3 - Dean Roddey - 10-15-2017

Any of use the Pi on the C++ side would have to be back end only stuff I guess.

RE: Thoughts for 5.3 - pjgregory - 10-15-2017

Well I will say it again, even though nothing ever seems to happen.  Proper DNLA support so that we can use modern, high quality media render devices such as the latest Oppo 4K Blu ray players or Smart TV's.  I, amd many others, have given up using CQC for its original purpose of controlling home cinemas and whole house media. Done properly, with support for Plex as a DLNA server, it would be a major improvement.  Use CQC to stream media from a local NAS or internet sources.  As you said in earlier post, this would work well for the pro-installers.  It shouldn't be so hard to do, given that the basic widgets are already there.  

I live in hope, but I surpose CQC Voice will win in the end.  After all Amazon Echo is obviously failing in the market place and the world is waiting for a CQC offering using obsolete hardware and home brewed microphones.


RE: Thoughts for 5.3 - Dean Roddey - 10-15-2017

And, as I've said before, it's not nearly so simple. Doing that will likely be the one significant thing we could get done in a release. To show up 5 months from now and the only thing we can claim is that you can use an Oppo instead of a Roku or you can use the (probably much slower) DLNA interface to a media manager that we already support via other means, though it would of course potentially let us support some new ones, that's a difficult sell. That's not a lot of payoff for the huge amount of work involved. I understand it would be nice, but nice doesn't necessarily pay the bills. Compare that to the payoff we will get from the WebRIVA work in this release, for example, and there's just not even a comparison.

The point of CQC Voice isn't that the Echo is failing, it's that it offers a VASTLY simpler and more secure voice control option, which is in fact a very significant advantage, assuming we can get the recognition level up sufficiently in larger spaces. If a pro installer can put in a system that doesn't require setting up AWS skills and managing that for every customer he has, and doesn't have to expose the customer's system to the outside world and be responsible for that, and doesn't have to do much setup, to get a nice set of really interactive voice control commands, there's a lot to be said for that. That's something that could potentially make a real difference. Not saying that's what we'll do, but it could make a vastly bigger difference than DLNA support.

And there's nothing home brewed about conference room microphones or conference room DSP systems, they are actually quite high endy devices. Or about the Kinect for that matter, which is a quite powerful device, though getting kind of old now. The Echo's advantage isn't in the hardware, which is pretty basic stuff, but on the server side and the deep neural network speech recognition capabilities.