subject:"\[android\-developers\] Re\: RTSP and MMS \- mediaplayer shenanigans"

[android-developers] Re: RTSP and MMS - mediaplayer shenanigans

2009-02-15 Thread Rob Franz

No it's a cookie that you get upon passage of username and login.
That auth token is part of the URL that you get when a channel is selected.

If you enter that URL into a web browser within Windows, it'll pop up
Windows media player and play the URL - I can confirm that.

Will see if there's a way around this.

-Rob

On Sun, Feb 15, 2009 at 12:17 AM, Marco Nelissen marc...@android.comwrote:

When you say 'cookie', do you mean a real cookie, or are you referring to
the auth token in the URL you mentioned earlier?
Have you tried entering that URL into a freshly launched webbrowser on your
desktop, and did it work?
Either way, I'm pretty sure that OpenCore is not going to work with an MMS:
URL.

On Sat, Feb 14, 2009 at 7:55 PM, Rob Franz rob.fr...@gmail.com wrote:

Yes - I get through the authentication and that works with no problems -
after the authentication (and you get a cookie) you can select a channel to
listen to, which are just HTTP gets. You just pass the cookie each time.
When you send the get, you'll get the address of an mms:// feed.

On Sat, Feb 14, 2009 at 9:09 PM, Marco Nelissen marc...@android.comwrote:

Doesn't that certain satellite radio online streaming audio service
require that you authenticate in some way before accessing the stream?

On Sat, Feb 14, 2009 at 4:55 PM, Rob Franz rob.fr...@gmail.com wrote:

It's hard to say what's being rejected... I have tried putting rtsp://
instead of mms:// but that doesn't seem to work.
Basically I'm trying to emulate another program that runs on Windows
that logs into a certain satellite radio online streaming audio service
(should be pretty easy to guess what it is :) and initiates a streaming
audio session when a user picks a channel. It's RTSP with a RTP payload
which mediaplayer should support.

It's just a question of getting the data and playing it. Unfortunately
the media player doesn't seem to throw up meaningful log information...

On Sat, Feb 14, 2009 at 1:16 PM, Dave Sparks
davidspa...@android.comwrote:

I'm pretty sure that OpenCore is going to reject the mms URI.

On Feb 13, 8:57 pm, Rob Franz rob.fr...@gmail.com wrote:
I believe this is WMA on the other end. Does this present a problem?

On Feb 13, 2009 11:13 PM, Rob Franz rob.fr...@gmail.com wrote:

Hi all
I'm trying to get an RTSP stream going with a verified source - I
know
there's something on the other end in this case.

However, the format of the URL is like this:

mms://

a757.l1265761171.c12657.g.lm.akamaistream.net/D/757/12657/v0001/reflector:61171?auth=daEdLa4adcAc2aoc1bYceclcFcQdfbwckcA-bjLJ8.-b4-NvGjptD

I admit I'm new to RTSP in general but I think I understand how it
works - for my purposes, all I need to do is pass the RTSP URL to the
mediaPlayer.setDataSource() method, prepare it, and start. That
should be pretty much it, if I understand correctly.

No matter what I do, I always get Prepare failed.:
status=0xFFFC ,etc. I try to modify different things, but I can
never prepare the stream, and so I can't start it.

Does the above URL qualify as an rtsp stream (i.e. remove the mms and
put in rtsp)?

As I understood it, RTSP obsoleted MMS, and MMS has been completely
phased out, but apparently some services are still passing out that
URL.

Anyone seen anything like this before?

Thanks

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: RTSP and MMS - mediaplayer shenanigans

2009-02-14 Thread Dave Sparks


I'm pretty sure that OpenCore is going to reject the mms URI.

On Feb 13, 8:57 pm, Rob Franz rob.fr...@gmail.com wrote:
 I believe this is WMA on the other end.  Does this present a problem?

 On Feb 13, 2009 11:13 PM, Rob Franz rob.fr...@gmail.com wrote:

 Hi all
 I'm trying to get an RTSP stream going with a verified source - I know
 there's something on the other end in this case.

 However, the format of the URL is like this:

 mms://
 a757.l1265761171.c12657.g.lm.akamaistream.net/D/757/12657/v0001/reflector:61171?auth=daEdLa4adcAc2aoc1bYceclcFcQdfbwckcA-bjLJ8.-b4-NvGjptD

 I admit I'm new to RTSP in general but I think I understand how it
 works - for my purposes, all I need to do is pass the RTSP URL to the
 mediaPlayer.setDataSource() method, prepare it, and start.  That
 should be pretty much it, if I understand correctly.

 No matter what I do, I always get Prepare failed.:
 status=0xFFFC ,etc. I try to modify different things, but I can
 never prepare the stream, and so I can't start it.

 Does the above URL qualify as an rtsp stream (i.e. remove the mms and
 put in rtsp)?

 As I understood it, RTSP obsoleted MMS, and MMS has been completely
 phased out, but apparently some services are still passing out that
 URL.

 Anyone seen anything like this before?

 Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send email to
android-developers-unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~--~~~~--~~--~--~---

[android-developers] Re: RTSP and MMS - mediaplayer shenanigans

2009-02-14 Thread Marco Nelissen

Doesn't that certain satellite radio online streaming audio service require
that you authenticate in some way before accessing the stream?

On Sat, Feb 14, 2009 at 4:55 PM, Rob Franz rob.fr...@gmail.com wrote:

It's hard to say what's being rejected... I have tried putting rtsp://
instead of mms:// but that doesn't seem to work.
Basically I'm trying to emulate another program that runs on Windows that
logs into a certain satellite radio online streaming audio service (should
be pretty easy to guess what it is :) and initiates a streaming audio
session when a user picks a channel. It's RTSP with a RTP payload which
mediaplayer should support.

It's just a question of getting the data and playing it. Unfortunately the
media player doesn't seem to throw up meaningful log information...

On Sat, Feb 14, 2009 at 1:16 PM, Dave Sparks davidspa...@android.comwrote:

I'm pretty sure that OpenCore is going to reject the mms URI.

On Feb 13, 8:57 pm, Rob Franz rob.fr...@gmail.com wrote:
I believe this is WMA on the other end. Does this present a problem?

On Feb 13, 2009 11:13 PM, Rob Franz rob.fr...@gmail.com wrote:

Hi all
I'm trying to get an RTSP stream going with a verified source - I know
there's something on the other end in this case.

However, the format of the URL is like this:

mms://

a757.l1265761171.c12657.g.lm.akamaistream.net/D/757/12657/v0001/reflector:61171?auth=daEdLa4adcAc2aoc1bYceclcFcQdfbwckcA-bjLJ8.-b4-NvGjptD

No matter what I do, I always get Prepare failed.:
status=0xFFFC ,etc. I try to modify different things, but I can
never prepare the stream, and so I can't start it.

Does the above URL qualify as an rtsp stream (i.e. remove the mms and
put in rtsp)?

As I understood it, RTSP obsoleted MMS, and MMS has been completely
phased out, but apparently some services are still passing out that
URL.

Anyone seen anything like this before?

Thanks

[android-developers] Re: RTSP and MMS - mediaplayer shenanigans

2009-02-14 Thread Rob Franz

On Sat, Feb 14, 2009 at 9:09 PM, Marco Nelissen marc...@android.com wrote: