You Are Here:

Community: Developer Discussion Boards

#1 Old A Player for streaming - 2006-07-17, 11:19

Join Date: May 2006
Posts: 48
Paranoid_Android
Offline
Registered User
Hi everyone.
I've a mobile that supports streaming via RTSP.
I want to do streaming via bluetooth. I wrote a midlet that get the InputStream from a rfcomm connection and I wrote a custom DataSource to handle the stream.
Everything works fine except that if I create the player with Manager.createPlayer(datasource) the player read the entire stream before playing even if i've written the custom datasource.
That's not what I want.I want the player to begin playing before the end..i want streaming.
What have I to do? Have I to write also a Player or there's a way to use the same specific player that the mobile uses for RTSP??


Please help me.Thank you.
Paranoid Android
Reply With Quote

#2 Old Re: A Player for streaming - 2006-07-17, 13:21

Join Date: Dec 2005
Posts: 1,696
Location: Europe/Poland/Warsaw
peterblazejewicz
Offline
Super Contributor
hi,

from Java Developer Lib nokia doc:
Quote:
Content buffering
For non-streamable media, the whole content is loaded into a buffer when a player is created using InputStream or using the HTTP or HTTPS protocols. When a player is created using ‘file’ or the RTSP protocol, the whole content is not buffered but played directly from the source.
Quote:
Streaming
RTSP

The implementation supports Real Time Streaming Protocol (RTSP). RTSP player can be created by using the Manager.createPlayer method with the locator starting "rtsp://".

A RTSP network access point must be set from RealPlayer, or Player.prefetch throws MediaException with the error code -39. RTSP connections always use the default access point set in Real Player. Depending on the product and operator configuration, a default access point may be set automatically.

A 3G network connection is recommended to achieve smooth streaming

The playable content types can be queried dynamically by calling Manager.getSupportedContentTypes( "rtsp" ).
doesn't it mean that with current j2me implementation on nokia phones we cannot stream from byte input stream and we are forced to use either "file" or rtsp protocols?

hth,
regards,
Peter
Reply With Quote

#3 Old Re: A Player for streaming - 2006-07-17, 13:50

Join Date: May 2006
Posts: 48
Paranoid_Android
Offline
Registered User
Yes. I knew it already. But i thought that writing a custom datasource for the stream you want to handle can help.
But now I'm afraid that it doesn't depend only on the datasource but also on the player.
I mean that maybe,even if i've a custom datasource for my stream,i cannot stream if I don't use an appropriate player implementation that doesn't buffer but that streams directly.
In this case I've wasted time writing a custom datasource.

It's bad that there isn't a way to stream what I want to stream and not only rtsp streams or streams coming from a FileConnection.:(
An idea is to write a custom player,extending the BasicPlayer but I think it's pretty hard to do and I don't even know where to start :S
Is there anyone that knows how to achieve that??

Thank you.
Reply With Quote
Reply « Previous Thread | Next Thread »
Display Modes
Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules

You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Forum Jump
Similar Threads
Thread Thread Starter Forum Replies Last Post
Create 3GP player with J2ME for Mobile dexxa05 Mobile Java Media (Graphics & Sounds) 53 2008-03-27 20:52

Rate This

 
Bookmark this page: DeliciousDiggFacebookGoogleYahooStumbleUponRedditDiigoTechnocratiTwitter  Share this page Share this page Print this Page Print this page Invite a friend Invite a friend
京ICP备05048969号    Email Newsletters Press Terms & Conditions Privacy Policy Sitemap Contact Us © 2009 Nokia 
RDF Facets: qdcZidentifierQSxhttpE3aE2fE2fdiscussionE2eforumE2enokiaE2ecomE2fforumE2fshowthreadE2ephpE3ftE3d134434X qdcZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qdcZtypeQUqfntypeZCommunityContentQ qdcZtypeQUqfntypeZE44iscussionQ qdcZtypeQUqfntypeZE44iscussionContentQ qdcZtypeQUqfntypeZE52esourceQ qdcZtypeQUqfntypeZWebpageQ qdcZtypeQUqmarsZManagedE52esourceQ qdcZtypeQUqwebZInformationE52esourceQ qdcZtypeQUqwebZPageQ qdcZtypeQUqwebZE52esourceQ qdcZtypeQUqrdfsZE52esourceQ qfnZtopicQUqfnTopicZentertainmentQ qfnZtopicQUqfnTopicZj2meQ qfnZtopicQUqfnTopicZjavaQ qfnZtopicQUqfnTopicZmediaQ qfnZtypeQUqfntypeZCommunityContentQ qfnZtypeQUqfntypeZE44iscussionQ qfnZtypeQUqfntypeZE44iscussionContentQ qfnZtypeQUqfntypeZE52esourceQ qfnZtypeQUqfntypeZWebpageQ qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX qrdfZtypeQUqfnZE45E78cludedFromGeneralE4cistingsQ qrdfZtypeQUqfntypeZCommunityContentQ qrdfZtypeQUqfntypeZE44iscussionQ qrdfZtypeQUqfntypeZE44iscussionContentQ qrdfZtypeQUqfntypeZE52esourceQ qrdfZtypeQUqfntypeZWebpageQ qrdfZtypeQUqmarsZManagedE52esourceQ qrdfZtypeQUqwebZInformationE52esourceQ qrdfZtypeQUqwebZPageQ qrdfZtypeQUqwebZE52esourceQ qrdfZtypeQUqrdfsZE52esourceQ