2016-05-31, 21:17
(2016-05-31, 20:39)timstephens24 Wrote: It's posts like that that put us in this situation.
We are already in the situation,so it's time to settle all the misunderstanding.
(2016-05-31, 20:39)timstephens24 Wrote: It's posts like that that put us in this situation.
(2016-05-31, 21:08)ArieS Wrote: movie78 & hdmkv, I just received the D34010WYK from the same ebay seller as you guys. Did you have to update the BIOS on yours?
(2016-05-31, 21:17)movie78 Wrote: We are already in the situation,so it's time to settle all the misunderstanding.+1. I think we can at least agree that the way MVC on Windows is being supported now isn't the right way. I mean we don't even know if keeping support alive via this one-way, non dev-involved thread has has sustainability, or if we're leading more users interested, excited about it into an eventual dead end?
(2016-06-01, 14:13)hdmkv Wrote: @Statikk, thanks. Someone had mentioned this a while ago, but there doesn't appear any work on MVC itself left to do. The chapter skip/seeking w/TrueHD MVC MKV's maybe, or is this more related to overall Kodi 17 master alpha? Other issues also seem to be Kodi 17 Alpha related. Don't know, just speculating, as we don't have any insights from @afedchin himself.
What I'd hope is MVC soon gets merged into mainline Kodi 17 so it at least has a more assured life going forward. If it can't be soon, again would be nice to know the plan. Think my frustration stems from all the conversation since the 'incident' just being one way (like talking to a wall). MVC w/Windows has been the most exciting thing to happen w/Kodi, maybe other than Kodi on Pi2/3 and Shield, that additional dev interest and support would be great.
(2016-06-01, 20:14)Statikk Wrote: I agree with you guys on this being the most amazing feature to hit Kodi in ages. I started using Kodi way back when it was XBMP...before the name change to XBMC. When high def content hit and my orginal XBOX was no longer able to play things I moved on. It wasn't until the addition of MVC 3D that I could finally get everything I wanted from Kodi again and it brought me back. I didn't want multiple boxes for different things and I wanted the same solution on both TVs. I can finally have that now thanks to this build. It would be great to hear that afedchin's hard work has paid off and will make it into Kodi 17. I wonder who makes the call on that.
(2016-06-01, 20:22)hdmkv Wrote: @movie78 or anyone else, is Launcher4Kodi working for you as expected? For me, for initial boot-up, even from my D34010WYK NUC completely powered off, it works fine going right into Kodi. But, if I power off using my Harmony Ultimate, the NUC doesn't really seem turned off... the blue power light stays on.
Then, next time when I power on via remote, I get no picture and have to physically turn the NUC off by holding the power button down for 2-3 secs, then press to power it back up. At this point, Windows tries to auto-repair itself as PC wasn't shut down properly.
I'm wondering if I should set Kodi's shutdown function to 'Suspend' instead of 'Power off system'. Latter doesn't seem to be working, at least w/these MVC builds. Or, maybe the issue has something to do with the IR function for power for D34010WYK in Harmony's database.
(2016-06-01, 21:09)timstephens24 Wrote: Shutdown from my Harmony would always suspend for me, so I have a Powershell shutdown script in my hotbar, so part of the "shutdown" of the Harmony is to press Win + 8 where I put the script shortcut.
(2016-06-01, 20:22)hdmkv Wrote: @movie78 or anyone else, is Launcher4Kodi working for you as expected? For me, for initial boot-up, even from my D34010WYK NUC completely powered off, it works fine going right into Kodi. But, if I power off using my Harmony Ultimate, the NUC doesn't really seem turned off... the blue power light stays on.
Then, next time when I power on via remote, I get no picture and have to physically turn the NUC off by holding the power button down for 2-3 secs, then press to power it back up. At this point, Windows tries to auto-repair itself as PC wasn't shut down properly.
I'm wondering if I should set Kodi's shutdown function to 'Suspend' instead of 'Power off system'. Latter doesn't seem to be working, at least w/these MVC builds. Or, maybe the issue has something to do with the IR function for power for D34010WYK in Harmony's database.