Universal Media Server | Forum

My UMS 2.6.0 is detecting a Popcorn Hour but I don't have that media player.
I have an Asus O!Play HDP-R1. It does indeed have a custom firmware based on a AC Ryan Playon HD (AMP r9).
Am I missing anything by UMS detecting the wrong renderer?
Cheers

Nope you're not missing anything.
UMS detects the render based on various info in the messages exchanged during startup. Your Asus most likely sends info that is to similar to the Popcorn and thus identifies it as such,
If it wouldn't have been seen as a popcorn it would have been "unknown render"...

I see.
I don't want to bug you much more but I am a bit curious: if I ain't missing anything, then why did you guys create all those renderer profiles in the first place?
Cheers

So the reason media renderer profiles are created is the fact that not all devices are made the same. For example, some can play mkv's natively others can't. UMS needs these profiles so it can best decide on the correct renderer that your going to use, if not it will use the default (Unknown Device) or if it matches another renderer it will use that. I can attempt to make you a config if you provide me with some info. go here viewtopic.php?f=9&t=556 and do me up a debug log set on trace so i can have a look at what your Asus sends UMS and i'll attempt to get a renderer config for you.

Thanks Prime.
I will post my media player's debug logs later today.
Cheers
EDIT: just ran a trace while trying to use the UPNP feature on my player.
As stated before, my player is a Asus O!Play HDP-R1 but it is running a custom firmware named AMP r9.
This custom firmware can be found here http://moservices.org/forum/viewtopic.php?f=12&t=1030.
The AMP firmware is a stripped down version of a AC Ryan Playon HD firmware without the user interface (just the core).
Then we need to add a skin so that the player works, otherwise it will not present any TV interface.
Currently there are 3 major skins:
- the original AC Ryan Playon HD that came with the hacked firmware
- Asus O!Play HD2
- iconBIT HDS42L
Now this is very important:
These skins are not simple UI skins. The skins are bundles of files that change not only the look and feel of the player.
Actually these 3 players (ACRyan, Asus and iconBIT) are similar but do have some differences in features, bugs, etc.
By changing the skin on my player, I am actually not only loading a new UI but also loading a set of features that are similar but not equal.
What I mean is, a trace with skin A may actually look different than a trace with skin B.
So, here is a link to a AMP r9 running iconBIT HDS42L skin
Maybe tomorrow I can install Playon HD skin and grab a trace. Who knows if it looks different than the trace with iconBIT skin...
Oh, and thanks a bunch for any help you can give me .
Cheers
EDIT2: just noticed that debug.log states 2 renderers (192.168.1.92 and 192.168.1.254).
My Asus media player is 192.168.1.92. The other supposed renderer is my Thomson Router TG-784N which also supports UPNP.

Just post the debug log and i will try to help, i don't think it will matter what skin you have. It won't take long quicker you post it, the quicker i can get a .conf to you

Hi Optimus_prime.
Thanks for your reply.
I have already posted a link to a trace file on my dropbox on my earlier post.
Apparently I didn't make it clear enough.
So, here is the link to a trace file of my Asus HDP-R1 running AMP r9 with iconBIT skin:
https://dl.dropbox.com/u/14343707/UMS/u ... conbit.zip
Let me find some time so that I can post a trace of it running ACRyan's skin.
It will be interesting to see if it looks any different .
Thanks in advance.
Cheers

Found some time to try the ACRyan Skin.
Here is a trace file.
https://dl.dropbox.com/u/14343707/UMS/u ... 9_pohd.zip
Thanks a bunch
Cheers

Hi Optimus_prime. Any news on this? Thanks

Sorry about this, i've been slack and focusing on some other things. Do us a favour, move the popcorn renderer .conf out of the C:\Program Files (x86)\Universal Media Server\renderers folder. Then rerun UMS on trace. I have a a feeling if it doesn't get picked up by UMS as a "realtek" device (there's a .conf with the same info as yours) it will give a bit more information. I think somehow the popcorn render config got written and detect's it first instead of the correct "Realtek" one.