[prev in list] [next in list] [prev in thread] [next in thread]
List: helix-open-discuss
Subject: Re: [hxdiscuss] realone error via RTSP
From: dkotian3 () vsnl ! net
Date: 2003-08-07 0:13:56
Message-ID: 200308070013.h770DuF27441 () webmail2 ! vsnl ! net
[Download RAW message or body]
Thanks,
Do I need need CVS access to build the executables, what is
this .buildrc for.
When I try to run build on Linux, it says no such file or directory
message. python,etc. is there.
What is the [helix} tag in .buildrc for ?
Thanks and Regards
Deepak
jgordon@real.com wrote
Yes. Python is required for building on all platforms.
Please read and follow the client build guide at
https://common.helixcommunity.org/2002/devdocs/quickstart
and be sure you have all the required tools.
https://common.helixcommunity.org/2002/devdocs/buildtools
Deepak Kotian wrote:
> Any inputs on this one please
> ----- Original Message -----
> From: <dkotian3@vsnl.net>
> To: <lacy@grapevine.net>
> Cc: <discuss@open.helixcommunity.org>
> Sent: Wednesday, August 06, 2003 4:42 AM
> Subject: Re: [hxdiscuss] realone error via RTSP
>
>
>
>>Hi,
>>
>>But, do we need python utiliy to build splay on Windows , because
>>when I run the build batch file, it says python not found.
>>
>>I had set the SYSTEM_ID.
>>Any inputs on this .
>>
>>Thanks and Regards
>>Deepak
>>
>>
>>lacy@grapevine.net wrote
>>I presently have little or no problem building in msvs or with ribosome
>>with my w98SE setup.
>>
>>If pressed further I would be happy to post my config settings etc.
>>IMHO, the site still is not
>>clear on using win98 and its '/' '\' path delineators.
>>
>>Henry Ping wrote:
>>
>>>Win98 is not recommended OS for developing Helix DNA Client, even MS
>>>officially deprecate Win98. W2K or WinXP are preferred OS for Windows.
>>>
>>>Yes, Helix DNA Client is supported on Linux with gcc2.95 or gcc3.2.
>>>You can choose whichever the platform you feel comfortable with and
>>>build splay.exe with the following options:
>>>branch: hxclient_1_0_kittyhawk_2003-02-21
>>>target: splay.exe
>>>profile: helix-client-all-defines
>>>
>>>Unfortunately, our mpeg1 renderer source is not published in Helix
>>>due to licensing issue, but you probably don't need the actual
>>>renderer anyway since the player never gets the data, you can use the
>>>null renderer(datatype/null/renderer) which claims most datatypes to
>>>isolate the problem without actual rendering.
>>>
>>>-->Henry
>>>
>>>At 01:07 AM 8/5/2003 +0530, Deepak Kotian wrote:
>>>
>>>>Thanks Henry, I will check with splay.exe
>>>>I have downloaded the the Entire CVS helix client and after
>>>>setting all the Environment variable, I get this error
>>>>"Out of environment space" when I run build. I am using Windows 98
>>>>O.S. Can one give a reason for this.
>>>>I guess, I do not need python for Windows.
>>>>
>>>>Is helix client is supported on Linux, basically would it
>>>>help if I debug it on Linux. What rendrer would it use on Linux.
>>>>Could one please let me know.
>>>>
>>>>Thanks and Regards
>>>>Deepak
>>>>
>>>>
>>>>----- Original Message -----
>>>>From: "Henry Ping" <ping@real.com>
>>>>To: "Deepak Kotian" <dkotian3@vsnl.net>;
>>>><discuss@open.helixcommunity.org> Sent: Monday, August 04, 2003
>>>>10:58 PM Subject: Re: [hxdiscuss] realone error via RTSP
>>>>
>>>>
>>>>
>>>>>The player state during the startup can be described as:
>>>>>connecting - DNS lookup and establish connection between the client
>>>>>and the server
>>>>>loading - buffering to satisfy source's preroll after the client
>>>>>sends PLAY request
>>>>>playing - playback starts after preroll is fullfilled
>>>>>
>>>>>There are too many factors could cause the failure between the
>>>>>client and the server(i.e. an extra hidden CR/LF in headers).
>>>>>Especially you are developing a custom server. debugging the Helix
>>>>>DNA Client(splay.exe) may provide some clues on what's wrong in
>>>>>your server or the client itself.
>>>>>
>>>>>-->Henry
>>>>>
>>>>>At 12:04 AM 8/4/2003 +0530, Deepak Kotian wrote:
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I am still getting this error from RealOne Client inspite of
>>>>>>adding RTP-info and others which we have discussed earlier.
>>>>>>Also, I have to mention on more thing.
>>>>>>This error comes on some machines and on some machines
>>>>>>it does not go ahead of "Connecting" message on the top
>>>>>>bar.
>>>>>>What is the sigficance of "Connecting" followed by "Loading"
>>>>>>on the top menu bar and after that I get this error.
>>>>>>
>>>>>>Could someone please explain this varied behaviour. Also, do I need
>>>>>>to do some setting for RTSP on RealOne client to work.
>>>>>>Please let me know.
>>>>>>We have tried MPEG1 Video ES and MPEG1 Audio ES, but
>>>>>>seems to be OK till now via RTSP/RTP.
>>>>>>Any pointers please.
>>>>>>
>>>>>>Thanks and Regards
>>>>>>Deepak
>>>>>>
>>>>>>
>>>>>>
>>>>>>----- Original Message -----
>>>>>>From: "Deepak Kotian" <dkotian3@vsnl.net>
>>>>>>To: <discuss@open.helixcommunity.org>
>>>>>>Sent: Friday, July 25, 2003 10:20 PM
>>>>>>Subject: [hxdiscuss] realone error via RTSP
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>> We have implemented RFC 2250 for RTP video payload in our
>>>>>>> server We get connecting and Loading message on top of
>>>>>>> realone. But somehow we get this error on the RealOne player,
>>>>>>> is there a way I can debug this and get more detailed
>>>>>>> information of the error, so that I know what is wrong on the
>>>>>>> server or otherwise. I get the play reqest from the server as
>>>>>>> well. This is the SDP file which we are using for reference.
>>>>>>>*****
>>>>>>>v=0
>>>>>>>o=- xyz 1 1 LAN IP4 192.168.2.50
>>>>>>>s=xyz Streaming
>>>>>>>m=video 6970 RTP/AVP 32
>>>>>>>a=rtpmap:32 MPV/90000
>>>>>>>c=IN IP4 192.168.8.50
>>>>>>>a=control:rtsp://192.168.8.50/XYZ.mpeg
>>>>>>>t=0 0
>>>>>>>*****
>>>>>>> Any help on this would be greatly help us in using RealOne
>>>>>>>faster.
>>>>>>>
>>>>>>>Thanks and Regards
>>>>>>>Deepak
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>--------------------------------------------------------------------
>>
>>-------
>>
>>>>-
>>>>
>>>>>>----
>>>>>>
>>>>>>
>>>>>>
>>>>>>>------------------------------------------------------------------
>>
>>---
>>
>>>>>>>To unsubscribe, e-mail:
>>>>>>>discuss-unsubscribe@open.helixcommunity.org For additional
>>>>>>>commands, e-mail: discuss-help@open.helixcommunity.org
>>>>>>
>>>>>>-------------------------------------------------------------------
>>
>>--
>>
>>>>>>To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
>>>>>>For additional commands, e-mail:
>>>>>>discuss-help@open.helixcommunity.org
>>>>>
>>>>>
>>>>>--------------------------------------------------------------------
>>
>>-
>>
>>>>>To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
>>>>>For additional commands, e-mail:
>>>>>discuss-help@open.helixcommunity.org
>>>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
>>>For additional commands, e-mail: discuss-help@open.helixcommunity.org
>>
>>-----
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
>>For additional commands, e-mail: discuss-help@open.helixcommunity.org
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
>>For additional commands, e-mail: discuss-help@open.helixcommunity.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
> For additional commands, e-mail: discuss-help@open.helixcommunity.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
For additional commands, e-mail: discuss-help@open.helixcommunity.org
---------------------------------------------------------------------
To unsubscribe, e-mail: discuss-unsubscribe@open.helixcommunity.org
For additional commands, e-mail: discuss-help@open.helixcommunity.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic