Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Dev

having problems with upnp on a netgear mp101

 

 

MythTV dev RSS feed   Index | Next | Previous | View Threaded


simon at koala

Oct 28, 2007, 3:08 PM

Post #1 of 11 (2721 views)
Permalink
having problems with upnp on a netgear mp101

my mp101 (which used to work) is now saying unsupported format when i
try to play any music. it used to work.

so i turned on logging for upnp and see almost not messages.
i see some initialisation stuff at the start; but nothing when the mp101
connects to my backend.

my first questions is: is this expected?
my second question is: does anybody have any idea what has changed?

will i have to go in with a debugger?

Regards
--
simon

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


dburr at virginbroadband

Oct 28, 2007, 4:44 PM

Post #2 of 11 (2615 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

On Sun, 2007-10-28 at 22:08 +0000, Simon Kenyon wrote:
> my mp101 (which used to work) is now saying unsupported format when i
> try to play any music. it used to work.
>
> so i turned on logging for upnp and see almost not messages.
> i see some initialisation stuff at the start; but nothing when the mp101
> connects to my backend.
>
> my first questions is: is this expected?
> my second question is: does anybody have any idea what has changed?

Sounds like you may be having the same problem as I am:
http://www.gossamer-threads.com/lists/mythtv/dev/296413

The advantage that you have is that yours was actually known to work at
some stage in the past. I have unsuccessfully tried SVN revisions
14251, 14666 and 14722 although Denon 4306 support was reported to work
in changeset 14268. Do you know what the most recent revision that has
worked with your MP101 is? Hopefully that can provide us with a
starting point to track down the change which introduced the breakage.

I myself have had a bit of a fiddle with libs/libmythupnp/upnpdevice.cpp
to see if enabling the MediaReceiverRegistrar would help (it didn't).
The only other functional changes that I can see from changeset 14250
are:
* the code that writes out a <deviceList> for embedded devices was
commented out
* some of the protocol strings changed from "*" to "DLNA.ORG...."

Are you able to try reversing the above changes one at a time to see if
they help?

DB

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


lukas.kasprowicz at online

Oct 29, 2007, 12:39 AM

Post #3 of 11 (2610 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

Am Montag 29 Oktober 2007 00:44:08 schrieb Daniel Burr:
> I myself have had a bit of a fiddle with libs/libmythupnp/upnpdevice.cpp
> to see if enabling the MediaReceiverRegistrar would help (it didn't).
> The only other functional changes that I can see from changeset 14250
> are:
> * the code that writes out a <deviceList> for embedded devices was
> commented out
> * some of the protocol strings changed from "*" to "DLNA.ORG...."
>
> Are you able to try reversing the above changes one at a time to see if
> they help?

Hi,

I have not seen the previous discussions. Maybe you should try something like:

r12892.

This is a revision that worked with the devices mentioned in the wiki. It
seems when looking at the page there where no devices added.

Lukas
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


simon at koala

Oct 29, 2007, 2:47 AM

Post #4 of 11 (2624 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

On Mon, 2007-10-29 at 09:39 +0200, Lukas K wrote:
> > Are you able to try reversing the above changes one at a time to see if
> > they help?
>
> Hi,
>
> I have not seen the previous discussions. Maybe you should try something like:
>
> r12892.
>
> This is a revision that worked with the devices mentioned in the wiki. It
> seems when looking at the page there where no devices added.

i will build another backend and try binary search for the break.
--
simon

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


dburr at virginbroadband

Oct 31, 2007, 5:16 PM

Post #5 of 11 (2588 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

On Sun, 2007-10-28 at 22:08 +0000, Simon Kenyon wrote:
> my mp101 (which used to work) is now saying unsupported format when i
> try to play any music. it used to work.
>
> so i turned on logging for upnp and see almost not messages.
> i see some initialisation stuff at the start; but nothing when the mp101
> connects to my backend.

I found the problem that I was having. In MythXML::GetMusic(),
sBasePath had no value which caused the QFile::exists test to fail and
return a 404 error. The reason for this was that I had a setting for
MusicLocation with my FE hostname but not with my BE hostname. However,
uPnP used to work for you so you're probably not having the same
problem.

I found that "tcpdump -X ether host <hostname>" was helpful to determine
what was failing. Can you see any 404 errors being returned?

DB

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


simon at koala

Dec 11, 2007, 1:20 AM

Post #6 of 11 (2451 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

Daniel Burr wrote:
> On Sun, 2007-10-28 at 22:08 +0000, Simon Kenyon wrote:
>
>> my mp101 (which used to work) is now saying unsupported format when i
>> try to play any music. it used to work.
>>
>> so i turned on logging for upnp and see almost not messages.
>> i see some initialisation stuff at the start; but nothing when the mp101
>> connects to my backend.
>>
>
> I found the problem that I was having. In MythXML::GetMusic(),
> sBasePath had no value which caused the QFile::exists test to fail and
> return a 404 error. The reason for this was that I had a setting for
> MusicLocation with my FE hostname but not with my BE hostname. However,
> uPnP used to work for you so you're probably not having the same
> problem.
>
> I found that "tcpdump -X ether host <hostname>" was helpful to determine
> what was failing. Can you see any 404 errors being returned?
>
> DB
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>
>
that is not my problem. it has a good value on my master backend.

however, i am confused by this line in the log:

UPnp::Eventing::NotifySubscriber( 192.168.1.4:-7456 ) : 3 Variables

as i don't have a 192.168.0.0 network here (it is 195.7.61.0)
so whom is it notifying?

will try to work my way through this code this evening to see what is
going on.
--
simon
_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


stuart at xnet

Apr 5, 2008, 4:02 PM

Post #7 of 11 (2248 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

Simon Kenyon wrote:
> Daniel Burr wrote:
>> On Sun, 2007-10-28 at 22:08 +0000, Simon Kenyon wrote:
>>
>>> my mp101 (which used to work) is now saying unsupported format when i
>>> try to play any music. it used to work.
>>>
>>> so i turned on logging for upnp and see almost not messages.
>>> i see some initialisation stuff at the start; but nothing when the mp101
>>> connects to my backend.
>>>
>> I found the problem that I was having. In MythXML::GetMusic(),
>> sBasePath had no value which caused the QFile::exists test to fail and
>> return a 404 error. The reason for this was that I had a setting for
>> MusicLocation with my FE hostname but not with my BE hostname. However,
>> uPnP used to work for you so you're probably not having the same
>> problem.
>>
>> I found that "tcpdump -X ether host <hostname>" was helpful to determine
>> what was failing. Can you see any 404 errors being returned?
>>
>> DB
>>
>> _______________________________________________
>> mythtv-dev mailing list
>> mythtv-dev [at] mythtv
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>>
>>
> that is not my problem. it has a good value on my master backend.
>
> however, i am confused by this line in the log:
>
> UPnp::Eventing::NotifySubscriber( 192.168.1.4:-7456 ) : 3 Variables
>
> as i don't have a 192.168.0.0 network here (it is 195.7.61.0)
> so whom is it notifying?
>
> will try to work my way through this code this evening to see what is
> going on.
> --
> simon
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>

Simon, did you ever get your MP101 music client to work with mythtv's
UPNP server?

I have recently upgraded to .21 and saw some improvement w.r.t. watching
UPNP served up videos on a Sigma/Sayabs based client. However, the
Netgear MP101 music client is still acting funny. It sill is offering
up videos along with music. My guess is that normal UPNP appliances
identify them selves and rely on the server not to offer up media beyond
the client's capabilities. If you avoid these land mines (I think the
client will lock up if you try to play videos) you can get to two lists.
A play list and an album list. I am not sure how the play list works.
What is found is played then the MP101 stops. It certainly isn't all
the available music and there doesn't appear a way to change it. The
album list is severely broken. I can only see the first album title
which is repeated over and over again. There must also be some sort of
communication problem as jumping forward to see how long the album list
might be results in a lock up.

I don't think these are Negear MP101 problems as I believe I have seen
no such problems while running Twonkyvision.

...thanks.

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


jmblack256 at gmail

Apr 5, 2008, 5:48 PM

Post #8 of 11 (2243 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

>
> >
> > as i don't have a 192.168.0.0 network here (it is 195.7.61.0)
> > so whom is it notifying?
>
I remember seeing something about UPNP and limiting it to certain ranges,
192.168.xxx.xxx, 10.xxx.xxx.xxx, etc. You may want to verify this is the
issue you are seeing, the UPNP code not liking the subnet you are running
on. It would seem to match up with your logs and make sense that it sees
that its running on seemingly a public internet IP and not wanting to serve
on that network. I may be barking up the wrong tree, I have not investigated
this at all, but this may point you in the right direction.

jmblack


simon at koala

Apr 6, 2008, 2:45 AM

Post #9 of 11 (2219 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

On Sat, 2008-04-05 at 18:02 -0500, stuart wrote:
> Simon, did you ever get your MP101 music client to work with mythtv's
> UPNP server?
>
> I have recently upgraded to .21 and saw some improvement w.r.t. watching
> UPNP served up videos on a Sigma/Sayabs based client. However, the
> Netgear MP101 music client is still acting funny. It sill is offering
> up videos along with music. My guess is that normal UPNP appliances
> identify them selves and rely on the server not to offer up media beyond
> the client's capabilities. If you avoid these land mines (I think the
> client will lock up if you try to play videos) you can get to two lists.
> A play list and an album list. I am not sure how the play list works.
> What is found is played then the MP101 stops. It certainly isn't all
> the available music and there doesn't appear a way to change it. The
> album list is severely broken. I can only see the first album title
> which is repeated over and over again. There must also be some sort of
> communication problem as jumping forward to see how long the album list
> might be results in a lock up.
>
> I don't think these are Negear MP101 problems as I believe I have seen
> no such problems while running Twonkyvision.

the mp101 used to work with twonkyvision (haven't tried for a while)
but it cannot get music from myth. i'll rebuild with the latest svn
(been putting that off while the qt4 stuff settled down) and give it
another try. but i'm not holding my breath.
--
simon

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


simon at koala

Apr 6, 2008, 2:48 AM

Post #10 of 11 (2228 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

On Sat, 2008-04-05 at 18:48 -0600, jm black wrote:
> >
> > as i don't have a 192.168.0.0 network here (it is
> 195.7.61.0)
> > so whom is it notifying?
>
> I remember seeing something about UPNP and limiting it to certain
> ranges, 192.168.xxx.xxx, 10.xxx.xxx.xxx, etc. You may want to verify
> this is the issue you are seeing, the UPNP code not liking the subnet
> you are running on. It would seem to match up with your logs and make
> sense that it sees that its running on seemingly a public internet IP
> and not wanting to serve on that network. I may be barking up the
> wrong tree, I have not investigated this at all, but this may point
> you in the right direction.

interesting.
my home net *is* a public internet (i have half a class C - being doing
this ole internet stuff for quite a while now :-)). but there is a
transparent bridging firewall between it and the rest of the internet.
will have a look at the UPNP code to see what is going on

regards and thanks for the info.
--
simon

_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev


stuart at xnet

Apr 8, 2008, 5:48 AM

Post #11 of 11 (2175 views)
Permalink
Re: having problems with upnp on a netgear mp101 [In reply to]

Simon Kenyon wrote:
> On Sat, 2008-04-05 at 18:48 -0600, jm black wrote:
>> >
>> > as i don't have a 192.168.0.0 network here (it is
>> 195.7.61.0)
>> > so whom is it notifying?
>>
>> I remember seeing something about UPNP and limiting it to certain
>> ranges, 192.168.xxx.xxx, 10.xxx.xxx.xxx, etc. You may want to verify
>> this is the issue you are seeing, the UPNP code not liking the subnet
>> you are running on. It would seem to match up with your logs and make
>> sense that it sees that its running on seemingly a public internet IP
>> and not wanting to serve on that network. I may be barking up the
>> wrong tree, I have not investigated this at all, but this may point
>> you in the right direction.
>
> interesting.
> my home net *is* a public internet (i have half a class C - being doing
> this ole internet stuff for quite a while now :-)). but there is a
> transparent bridging firewall between it and the rest of the internet.
> will have a look at the UPNP code to see what is going on
>
> regards and thanks for the info.
> --
> simon

No, I'm running on a 192.168.x.x network. And just verified some of the
same problems on a PopCorn Hour box (another Syabas/SigmaDesig base
box). One of the most annoying features is the album list. I see the
1st album then the 2nd, then the 2nd over and over again. It repeat
over 20 time. My MP101 box would have never gotten that far as there is
also some sort of time out effecting both boxes. Getting more data is
paramount to locking up the session between the Mythtv box and it's UPNP
clients. And I don't think I have ever been been able to play music
using the album menu on either client.

I know mythth UPNP is still under development. But shouldn't we move
this thread to mythtv-users?

...thanks



_______________________________________________
mythtv-dev mailing list
mythtv-dev [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

MythTV dev RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.