Single Device Replaces Three In My Connected Living Room

Posted Posted in Miracast, Play To, Windows 8.1

 

I’m all about the Connected Home (as the title of this blog implies). My Living Room Home Theater system up until yesterday consisted of a circa 2010 Samsung 52 inch TV, an ancient Sony 5.1 Receiver, an Xbox 360 used solely as a Media Center Extender, a WDTV Live Hub which I used for DLNA Play To streaming, a Netgear PTV3000 for Miracast, an Apple TV for You tube, Hulu, Netflix, etc., a cable DVR and a first generation Samsung Blu Ray player. Separately, I have a pair of Sonos Play 5 speakers. A few days ago, the ancient Samsung Blue Ray player started groaning and screeching and it was the final incentive to replace it with something newer.

I did some Internet research and decided that the Samsung BD-F5900 would certainly improve my movie experience several fold. I downloaded the user manual and was even more impressed. While Samsung is likely to have a replacement model any day now, the $99 on sale price (at Best Buy no less) and the local availability drove me out in the 2 degree weather to purchase the device.

My intention was to replace an aging Blu Ray player, but what I got was a whole lot more.

No where on the box, the device itself, or in the user guide does the term DLNA appear. The BD-F5900 works perfectly as a Play To target. HD movies even play across the network smoothly. I can now move the WDTV Live Hub out of my Living Room (it is still a great NAS device).

playto samsung bd

The user guide mentions Samsung’s proprietary All Share multiple times, and mentions Miracast once.

add wireless display samsung bd

Miracast works perfectly. My Netgear PTV3000 can move upstairs to the bedroom TV or travel with me.

I can also use my iPhone with the PlugPlayer App as a small remote controller (the manual refers to similar functionality only working with s Samsung branded phone).

Last but not least, I had been using the Apple TV as a device to watch YouTube, etc. and not for Airplay of late (since the arrival on Miracast on Windows 8.1). I’d been watching some Amazon Prime Instant Movies on my Surface and using Miracast to display on the TV, (and didn’t have any app direct on a device that accessed this). Amazon is one of the apps available (along with 100+ others including the other big names like Netflix, Hulu, etc.) on the BD-F5900. Streams at 1080p HD smoothly and looks great. I’ll put the Apple TV away for now.

Bottom line, I’ve now got one device that replaces three and have removed some of the clutter in my living room.

In related news, there is rumor of a Microsoft Surface branded Miracast dongle via an FCC filing. Interesting development to say the least. It will be interesting to see what price point this launches with (if it launches). Stand alone Miracast adapters like Netgear’s PTV3000 and Actiontec’s Screen Beam are selling for $65-70. I guess I feel really good having purchased the Samsung BD player for $99 and getting everything but the kitchen sink included.

PhotoWeaver has functionality cut from Win 8.1 Photos App

Posted Posted in Play To, Windows 8.1

The PhotoWeaver App is free for a limited time. If you are one of the people complaining about the great stuff Microsoft ripped out of the Windows 8.1 Photos App like Facebook and Flickr integration and the ability to Play To your DLNA DMR device because Microsoft decided to not implement the Play To contract, grab this one while it is free.

 

weaver1

 

As you can see above, you can include Facebook, Flickr, Google+, and SkyDrive content.

weaver2

Play To works as it should from PhotoWeaver.

How to Use Non Certified Play To Devices in Windows 8.1

Posted Posted in Play To, Windows 8.1

If you read my blog posts this Spring on enabling legacy DMR’s in Windows 8.0, you know that you had to create individual entries and modify them for each device you have in your home.

Gabe Frost from Microsoft has just shared a single Registry key that will enable all your legacy Digital Media Renderers to appear on the Charms/Devices/Play tab in Windows 8.1.

HKEY_LOCAL_MACHINE\Software\Microsoft\PlayTo with a DWORD ShowNonCertifiedDevices with value 1 will enabled all your legacy Digital Media Renderers. Without this modification, Windows Store Apps won’t be able to use the Play function to send content to your non certified devices.

I have an older Samsung TV which without this registry key, is not capable of sending mp4’s on my hard drive to my TV using the Device/Play Charm. You can see below that it appears as TV, Not Windows Certified.

play2

 

As before, your first step is to insure your device works as expected on the Classic Desktop with your Photos, Music, and Videos (depending on the device, not all would be appropriate).

Fire up regedit.exe by typing regedit.exe on the Start screen, acknowledge UAC and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft

Create a NEW key by right clicking Microsoft and name it PlayTo

play3

play-4

Once the key is created, right click it and create a new DWord

play-5

 

 

The new Dword should be named ShowNonCertifiedDevices. After you have created the key, right click, edit and change the value from 0 to 1.

play-6

End result: My non certified Samsung TV shows up in the Play menu from the Devices Charm and successfully can send to my TV.

play7

 

Note: You alternatively could use HKEY_CURRENT_USER\Software\Microsoft\PlayTo with a DWORD ShowNonCertifiedDevices with value 1 which would limit functionality on a per user basis.

Use Non MSFT Certified Legacy DMRs with W8 Device Charm

Posted Posted in DLNA, Play To, Windows 8

 

My last post detailed the process to add Microsoft non certified devices to the list of supported “Play To” devices in Windows 8 Modern UI Start Screen Apps so that they appeared in the Charms/Devices menu. Once again, if you experiment with this, you will need to verify that your device is a DMR (digital media renderer) that works from the classic desktop explorer/libraries interface by right clicking an asset and verifying Play To appears and that you can successfully send the media to the device).

I already knew my circa 2009 Samsung LN52B750 series TV was not the greatest Play To client (which is why I have been using the WDTV LIVE Hub) but I wanted to enable it to see what kind of results I would get. The LNB Samsung TV series is neither certified by the DLNA.org folks or by Microsoft (just as my Sonos speakers are not certified by either organization).

In DLNA years, 2009 is ancient, and in TV cycle years, prehistoric. Samsung stops issuing firmware updates after 9-12 months so there was really not much hope of improving the DLNA experience after that time. Aggravating, but true. So for most people, the iffy DLNA experience (due to codec and transcoding support) the Microsoft decision to not show these uncertified devices is justified. It would be a support nightmare. But, if you are a geek and accustomed to tinkering with the registry, etc., once again, enabling these devices let you experiment.

Again, this is for geek enthusiasts only and unsupported. Backup your registry and the subkey before you begin. Proceed at your own risk.

Note: I performed this exercise on my Surface Pro and Surface RT with success.

To add the TV to the whitelist, once again, from the Network window, I right clicked the media icon for the TV and accessed the properties.

samsung

Since the DeviceShims registry already listed Samsung Electronics,all I needed to do was add the subkey for Samsung DTV DMR and the 32 bit dword IsLegacyDMR and set the hex value to 1. I did have to take ownership of the Samsung Electronics key and give local users full control in order to perform this modification.

Next step was to reboot.

Concurrent with my experimentation with non MSFT certified DLNA DMR’s, I also was looking to be able to play MKV files and had downloaded the trial of Cyberlink’s Power DVD Mobile from the Windows 8 App Store. (I’ll have more to say about this app soon, but I had a WOW experience; it’s one awesome program).

I opened  my Avatar MKV and it played beautifully on the Surface Pro. Now the moment of truth, could I send to my Samsung TV through the Devices menu. You can see in the screen capture below that both my TV and WDTVLiveHub are available from the Devices charm.

cyberlink1

The answer is a big YES. My Surface Pro displayed the following:

 

cyberlink2

And the output to the TV worked perfectly.

on-tv

The picture looked great and there was no lagging/glitching (and sound was in sync – I run audio from the TV out to a home theater system via Digital Optical SPDIF). I won’t say it was a good as watching the original Blue Ray, but close. This same TV has had trouble with mp4’s using Play To where it doesn’t correctly handle the aspect ratio at times. And when I set still digital images via the Device charm, they displayed beautifully.

Use MSFT Uncertified Play To devices with W8 Metro Apps

Posted Posted in DLNA, Play To, Surface

 

Today I’m one step closer to giving up my iPad as my Surface RT can now perform one more task on my must have list. Full DLNA Play To sharing from the Charms bar/Devices for non Microsoft certified devices was a biggie on my list.

A little history: In Windows 7, Microsoft introduced Play To which used the DLNA spec to let me send media from my computer to a DLNA DMR. I had so so results with my 2009 Samsung TV due to poor transcoding support, but great results with my WDTV Live Hub and my SONOS speakers. The so-so experience on my TV and the not wonderful experience on other device by many many people caused Microsoft to rethink their strategy for Windows 8 and come up with their own certification process for devices to “insure” a good experience. This translated into a restrictive policy for Windows 8 Start Screen/Metro/Modern UI Apps where only MS certified devices would appear in an applications Settings: Devices menu. What this meant for me was that I could no longer send music to my SONOS speakers from these Apps, although I could do so from the classic Desktop-Explorer-Libraries view. I certainly was annoyed and disappointed. To me, this meant that Microsoft was going down the closed eco-system route and emulating Apple. DLNA is an open standard, and there are tiered requirements. MS was seeking to bulletproof the experience, but in the process left many of us hanging. I certainly wished for, and expressed my desire for, an advanced user setting to “Show non MS certified devices”, and I still think that is the necessary change that Microsoft needs to make.

Others in the geek world wanted a way to use their non certified devices and Rafael Rivera came up with a way for x86 based Windows 8 computers to do just this. He didn’t find a way to do this on Surface RT. And that’s where I most wanted this functionality. Note: The information that follows applies to Windows 8/Windows RT and I have tested on my Surface RT, my Surface Pro, and a Windows 8 desktop.

So I started looking at the registry. What I am about to describe works on both my Surface and Surface RT tablets but it is the only way so far to enable this functionality on RT.

Before you start,verify that your device supports Play To in the classic desktop/explorer/libraries interface. To do this, right click a supported media file in a classic library and verify the Play To menu appears and that you can successfully send to your target device and it plays the media you selected.

There is an interesting key in the registry:

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders

\DAFUPnPProvider\Plugins\DlnaMetadataProvider\DeviceShims]

When expanded, it shows devices from just a few companies.

 

providers

Why only five vendors?

If you export the DeviceShims reg key, things get interesting. For example, specific vendors and specific devices have entries, such as:

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders

\DAFUPnPProvider\Plugins\DlnaMetadataProvider\DeviceShims\ONKYO]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders

\DAFUPnPProvider\Plugins\DlnaMetadataProvider\DeviceShims\ONKYO\HT-R690]
"IsLegacyDMR"=dword:00000001

 

Do you find the IsLegacyDMR an interesting dword? If you look at the entire exported key, it is one of those AHA moments.

What follow is for geeks only. Use at your own risk. Back up your registry and back up the specific key. And use what follows entirely at your own risk. Obviously you will want to at least use the touch/type keyboard for this process.

First, the DeviceShims key is “protected” and you will need to take ownership and give yourself full control.

1. Right click the DeviceShims key, then click Permissions.

2. Click the Advanced tab, then click the Change hyperlink next to the Owner. You can use your Microsoft account for this.

3. Apply

4. Give users (pcname\username) full control

5. Reboot

Second, you will need to determine the exact information on the device(s) you want to empower to use the Start Screen Play To functionality.

1. Go to the classic desktop and classic explorer

2. Find your device in the network list

3. Right click the device and select properties

4. You will need the Manufacturer and the Model, case sensitive. In the example below, the Manufacturer is Sonos, Inc. and the Model is Sonos Play:5

devprops

 

Third, You need to create the registry values for your device(s).

1. Create a new key under DeviceShims with the manufacturer (Sonos, Inc. in my example)

2. Under the just created key, create a new subkey for the model (Sonos Play:5 in my example).

3. Create a 32 bit dword IsLegacyDMR and set the HEX value to 1

 

If you export the key, the newly created value would look like

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders\DAFUPnPProvider\Plugins\DlnaMetadataProvider\DeviceShims\Sonos, Inc.]

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Device Association Framework\InboxProviders\DAFUPnPProvider\Plugins\DlnaMetadataProvider\DeviceShims\Sonos, Inc.\Sonos PLAY:5]
"IsLegacyDMR"=dword:00000001

4. Reboot

End result:

success

Here’s my Surface RT happily sending the output of the PRadio App (Pandora) to my Sonos.