Originally Posted by jriver
On our board, Yaobing just posted this addition to the instructions:
If you have not previously turned on DLNA option in MC, you should turn it on. Go to Tools > Options, and select Media Network. Check the checkbox "Use Media Network to share this library and enable DLNA", and restart MC.
It's possible this was what stopped you.
We're still working out the problems in both code and instructions. Thanks for your patience.
I did set up to use Media Server and enabled DLNA when it was determined that was part of the required configuration and now the Ceton works okay in SD form Standard View. Sadly the remote is dodgy and intemittent moving from cable channel to another channel... please spare telling me to turn off WMC. We have been down that road as you know.
I understand JRiver feelsk WMC is source of all evil. But Ceton support is enabled through WMC, WMC is a bit of bogeyman for you guys. but because WMC enables the Ceton as it is currently being supported and disabling it is not an option.,I would appreciate you not blaming my remote problems on that. The remote works fine now Theater View for ATSC with latest build... it is not surpsing that Cable and the remote are dodgy as this stage.
As I posted on Interact HD Cable is completely blocky, pixelated and unusable on my box at least. Others maybe doing better.
Now, it could be becasue it is a network tuner and it is not optimized code yet. I am not griping we are very early on and what I see is quite promising. What JR MC can actually do today would be usable for SD Cable but I never watch SD cable.. I have confidence when you guys focus on something, things happen and I applaud you jumping in with both feet. I would not suggest anyone go out and buy a Ceton today based on what JR can do with it. Next week maybe.
I am excited and curious to see if LAV and, madVR are going to play with Cable.. Can't really check it at the moment as I have my Nividia card out for the time being do a bug in Nvidia's driver on some Comcast encodes, mostly commercials.
That bug took me a long time isolate. Over a year actually because it was content dependent. One thought they fixed it but it kept coming back. The intel iGPU does not have the bug. Weird, I though it was decoder or renderer problem and turned out it has been in the Nvidia driver off an on for some time. I duplicated it with two different Nvidia Card models and multiple drivers.
Jim, perhaps we have different assesments of what constitutes Alpha, Beta and what is essentially a proof of concept. I have no gripes about where we are now. I am plesed to have anything and I am sure Yaobing will work magic over the coming days and weeks. Right now it is a Work In Progess and I am trying to provide useful feedback at Interact in the Ceton TV thread.
I really don't want to get in the dog house over there again for telling you exactly what I am experiencing . I don't think those kind of timeouts are productive.Edited by gtgray - 3/12/13 at 10:22pm