From vishnuprasadmc at yahoo.com  Tue Feb  6 01:15:47 2007
From: vishnuprasadmc at yahoo.com (Vishnuprasad M.C.)
Date: Tue Feb  6 02:00:00 2007
Subject: [Helix-producer-dev] Helix Producer SDK - Some Licensing
	clarifications
Message-ID: <758592.12180.qm@web51109.mail.yahoo.com>

Dear Helix Team, 

Could you please clarify some doubts regarding licence. 

In our product, we need to encode media using Real Producer. 
For that we need all the components in the "bin" directory of Helix Producer SDK to be distributed along with our product. 
We just need the binaries with in this "bin" folder for encoding. 

Any particular licence is required for distributing these files with in "bin" folder ? 
If yes, what type of licence that we need to purchase? And what is its cost? Where do I obtain this licence? 

I have downloaded the SDK from "http://forms.helixcommunity.org/helix/producersdk/index.html" v10. 
But latest version (v11.0.1)is available in "https://helix-producer.helixcommunity.org/downloads".
Is there any difference between these two SDKs? Is separate licence required for distributing these two SDK files? 

About upgrade - shall we incorporate the latest SDK files along with our product on each release of new Producer SDK?

Regards, 
Vishnuprasad M.C.
 				
---------------------------------
 Here?s a new way to find what you're looking for - Yahoo! Answers 
From donaldsnowdy at hotmail.com  Thu Feb  8 09:31:20 2007
From: donaldsnowdy at hotmail.com (donald snowdy)
Date: Thu Feb  8 10:15:04 2007
Subject: [Helix-producer-dev] RE: Helix-producer-dev Digest, Vol 31, Issue 2
Message-ID: 

Hello Helix Community....

I have the same questions that Vishnuprasad has posted below, however, I do 
not see a response to his questions?

I am using the Helix Producer SDK in a custom application (C#.Net) that may 
be sold commercially.  I am using the Helix Producer SDK to run a job file 
(*.rpjf) to encode AVI files to a RealMedia (*.rm) files.

I need all the components in the "bin" directory of Helix Producer SDK 
(including the Helix Producer ActiveX Control) to be distributed along with 
our product.

Can you please clarify the Helix licensing?

Thank you.

Donald.

>From: helix-producer-dev-request@helixcommunity.org
>Reply-To: helix-producer-dev@helixcommunity.org
>To: helix-producer-dev@helixcommunity.org
>Subject: Helix-producer-dev Digest, Vol 31, Issue 2
>Date: 31 Jan 2007 03:56:44 -0800
>
>Send Helix-producer-dev mailing list submissions to
>	helix-producer-dev@helixcommunity.org
>
>To subscribe or unsubscribe via the World Wide Web, visit
>	http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>or, via email, send a message with subject or body 'help' to
>	helix-producer-dev-request@helixcommunity.org
>
>You can reach the person managing the list at
>	helix-producer-dev-owner@helixcommunity.org
>
>When replying, please edit your Subject line so it is more specific
>than "Re: Contents of Helix-producer-dev digest..."


>Today's Topics:
>
>    1. RE: About redisrtibutable components (Sujeet Kharkar)
>    2. Web Cams? (Greg Wright)
>    3. [Fwd: [Helix-producer-dev] Web Cams?] (SKHARKAR@real.com)
>    4. Producer SDK - Licensing clarifications (Vishnuprasad M.C.)
>    5. Build problems.... (Greg Wright)
>    6. Producer SDK for OS/X Tiger Intel -- 1st	Attempt (Paul Curtis)
>    7. Re: Build problems.... (Kinson Liu)
>    8. Re: Build problems.... (Greg Wright)
>    9. Solaris 10/11 x86 (open Solaris) Producer SDK? (Rick Wager)



>From: "Sujeet Kharkar" 
>To: vishnuprasadmc@yahoo.com, 
>helix-producer-dev@helixcommunity.org,helix-producer-dev@helixcommunity.org
>Subject: RE: [Helix-producer-dev] About redisrtibutable components
>Date: Fri, 19 Jan 2007 16:53:33 +0530
>
>mediasink.dll is distributed with helix producer SDK and is not distributed
>with helix producer plus and/or basic, so you should get it as part of SDK
>and SDK licensing should apply.
>
>Thanks,
>Sujeet
>
>
>-----Original Message-----
>From: helix-producer-dev-bounces@helixcommunity.org
>[mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of
>Vishnuprasad M.C.
>Sent: Friday, January 19, 2007 1:09 PM
>To: helix-producer-dev@helixcommunity.org;
>helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] About redisrtibutable components
>
>Dear Helix team,
>
>One dll named "mediasink.dll" is missing along with the Real Producer 11
>Basic. Due to this our product could not encode properly. Is it possible to
>distribute this component along with our product? Is there any licensing
>problem for this?
>
>Regards,
>Vishnuprasad M.C.
>
>
>
>
>
>__________________________________________________________
>Yahoo! India Answers: Share what you know. Learn something new
>http://in.answers.yahoo.com/
>_______________________________________________
>Helix-producer-dev mailing list
>Helix-producer-dev@helixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>
>





>From: Greg Wright 
>To: Helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] Web Cams?
>Date: Tue, 23 Jan 2007 17:25:54 -0800
>Anyone have any experience with what web cams are supported
>under linux for use with the producer? I want to order
>something cheap that I can use to work with video capture
>on my linux desktop box here.
>
>I am thinking that just about any USB one would do the trick,
>but I want to make sure first.
>
>--greg.
>
>
>





>From: SKHARKAR@real.com
>To: nmcconnell@real.com
>CC: Helix-producer-dev@helixcommunity.org
>Subject: [Fwd: [Helix-producer-dev] Web Cams?]
>Date: Tue, 23 Jan 2007 22:50:00 -0800 (PST)
>Forwarding your request to Neal, who might have used web cam's. Most of my
>capture experience is with Osprey cards.
>
>Thanks,
>Sujeet
>
>---------------------------- Original Message ----------------------------
>Subject: [Helix-producer-dev] Web Cams?
>From:    "Greg Wright" 
>Date:    Tue, January 23, 2007 5:25 pm
>To:      Helix-producer-dev@helixcommunity.org
>--------------------------------------------------------------------------
>
>Anyone have any experience with what web cams are supported
>under linux for use with the producer? I want to order
>something cheap that I can use to work with video capture
>on my linux desktop box here.
>
>I am thinking that just about any USB one would do the trick,
>but I want to make sure first.
>
>--greg.
>
>
>_______________________________________________
>Helix-producer-dev mailing list
>Helix-producer-dev@helixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>
>





>From: "Vishnuprasad M.C." 
>To: helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] Producer SDK - Licensing clarifications
>Date: Wed, 24 Jan 2007 07:09:13 +0000 (GMT)
>Dear Helix Team,
>
>Could you please clarify some doubts regarding licence.
>
>In our product, we need to encode media using Real Producer. For that we 
>need all the components in the "bin" directory of Helix Producer SDK to be 
>distributed along with our product. We just need the binaries with in this 
>"bin" folder for encoding.
>
>Any particular licence is required for distributing these files with in 
>"bin" folder ?
>If yes, what type of licence that we need to purchase? And what is its 
>cost? Where do I obtain this licence?
>
>I have downloaded the SDK from 
>"http://forms.helixcommunity.org/helix/producersdk/index.html" v10. But 
>latest version (v11.0.1)is available in 
>"https://helix-producer.helixcommunity.org/downloads". Is there any 
>difference between these two SDKs? Is separate licence required for 
>distributing these two SDK files?
>
>About upgrade - shall we incorporate the latest SDK files along with our 
>product on each release of new Producer SDK?
>
>Regards,
>Vishnuprasad M.C.
>
>
>---------------------------------
>  Here’s a new way to find what you're looking for - Yahoo! Answers





>From: Greg Wright 
>To: Helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] Build problems....
>Date: Mon, 29 Jan 2007 13:17:07 -0800
>So, is anyone having trouble building the producer lately?
>
>I have tried today on my linux and windows boxes and they
>die with, what seems, the same cvs error trying to check
>out some distribution libs. If I run the CVS command by hand
>I get:
>
>
>[~/ribosome]cvs -d 
>:ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout -r 
>"producer_11" win32-i386-vc7/p
>rotocol_dist/rtsp
>cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>cvs [checkout aborted]: could not find desired version 1.224 in 
>/cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>rdtclntlib.lib,v
>
>
>I don't know if it is a temporary cvs issue or some other problem.
>
>Here is my build setup:
>
>
>Build System (V2.4.4)
>time: Mon Jan 29 11:57:15 2007
>outfile: build.out
>branch: producer_11
>platform: win32-i386-vc7
>distribution/archive from: win32-i386-vc7
>build Type: debug
>build options: debug
>profile: 
>d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines
>cvs revision: producer_11
>copy target: debug
>target(s): toolsall
>
>I am using the same ~/.buildrc I use for client dev work.
>
>Are those dist libs suppose to be branched onto a 'producer_11' branch or
>something? It really doesn't look like they are, but, the nightly builds
>seem to work fine.
>
>Also, I would guess that I am using a BIF file that doesn't really need to
>checkout any of those distlibs to begin with....
>
>
>
>--greg.
>
>





>From: Paul Curtis 
>To: Helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] Producer SDK for OS/X Tiger Intel -- 1st 
>Attempt
>Date: Mon, 29 Jan 2007 16:25:35 -0500
>Mac OS/X 1.4.8 (Intel) with XCode 2.4
>Using built-in specs.
>Target: i686-apple-darwin8
>Configured with: /private/var/tmp/gcc/gcc-5363.obj~28/src/configure 
>--disable-checking -enable-werror --prefix=/usr --mandir=/share/man 
>--enable-languages=c,objc,c++,obj-c++ 
>--program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ 
>--with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib 
>--build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic 
>--program-prefix= --host=i686-apple-darwin8 --target=i686-apple-darwin8
>Thread model: posix
>gcc version 4.0.1 (Apple Computer, Inc. build 5363)
>
>The build.out is available at http://www.terrapin.com/build.out.zip
>
>Build System Menu
>Ribosome v2.4.4
>-> Current Directory: /Users/pcurtis/src
>[0] Set BIF branch (helix)
>[1] Set Target(s) (producersdk_installer)
>[2] Set Profile 
>(/Users/pcurtis/src/build/umakepf/helix-producer-all-defines)
>[3] run: build -trelease
>[4] Toggle make depend & makefiles (-e -n)
>[5] Toggle release (-trelease)
>[6] Toggle 'make clean'  (-c)
>[7] Toggle clobber (Dangerous!) (-C)
>[8] Toggle halt-on-error (-p green)
>[9] Toggle verbose mode (-v)
>[10] Toggle static build (-tnodll)
>[11] Checkout source for selected target now
>[12] Set Tag/Branch/Timestamp
>[13] Help Page (full help in build/doc/index.html)
>[14] run history: build -trelease
>[Q] Quit
>
>





>From: Kinson Liu 
>To: Greg Wright 
>CC: Helix-producer-dev@helixcommunity.org
>Subject: Re: [Helix-producer-dev] Build problems....
>Date: Mon, 29 Jan 2007 13:38:00 -0800
>FYI, rdtclntib.lib,v V1.224 is not found in the distribution repository. 
>Did it ever exist?
>
>Kinson
>
>Greg Wright wrote:
>>So, is anyone having trouble building the producer lately?
>>
>>I have tried today on my linux and windows boxes and they
>>die with, what seems, the same cvs error trying to check
>>out some distribution libs. If I run the CVS command by hand
>>I get:
>>
>>
>>[~/ribosome]cvs -d 
>>:ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout -r 
>>"producer_11" win32-i386-vc7/p
>>rotocol_dist/rtsp
>>cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>>cvs [checkout aborted]: could not find desired version 1.224 in 
>>/cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>>rdtclntlib.lib,v
>>
>>
>>I don't know if it is a temporary cvs issue or some other problem.
>>
>>Here is my build setup:
>>
>>
>>Build System (V2.4.4)
>>time: Mon Jan 29 11:57:15 2007
>>outfile: build.out
>>branch: producer_11
>>platform: win32-i386-vc7
>>distribution/archive from: win32-i386-vc7
>>build Type: debug
>>build options: debug
>>profile: 
>>d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines
>>cvs revision: producer_11
>>copy target: debug
>>target(s): toolsall
>>
>>I am using the same ~/.buildrc I use for client dev work.
>>
>>Are those dist libs suppose to be branched onto a 'producer_11' branch or
>>something? It really doesn't look like they are, but, the nightly builds
>>seem to work fine.
>>
>>Also, I would guess that I am using a BIF file that doesn't really need to
>>checkout any of those distlibs to begin with....
>>
>>
>>
>>--greg.
>>
>>_______________________________________________
>>Helix-producer-dev mailing list
>>Helix-producer-dev@helixcommunity.org
>>http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>







>From: Greg Wright 
>To: Kinson Liu 
>CC: Helix-producer-dev@helixcommunity.org
>Subject: Re: [Helix-producer-dev] Build problems....
>Date: Mon, 29 Jan 2007 13:57:22 -0800
>Kinson Liu wrote:
>>FYI, rdtclntib.lib,v V1.224 is not found in the distribution repository. 
>>Did it ever exist?
>
>I don't know. This is the first time I have ever tried to build
>the producer. If I just let ribosome grind away it eventually
>spits this out:
>
>[#-00001970][2007-01-29 13:39:24][472][ERROR] : Error during job threading: 
>Error in threaded call
>[#-00001971][2007-01-29 13:39:24][472][ERROR] : --- Build System Error 
>------------------------------------
>You have found a Ribosome bug.
>-----------------------------------------------------------
>--- Python Traceback --------------------------------------
>------------------------------------
>Traceback (most recent call last):
>   File "d:\cygwin\home\gwright\ribosome\build\bin\launcher.py", line 117, 
>in __runTool
>     tool.run()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 896, 
>in run
>     ShellToolApp().main()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 470, 
>in main
>     apply(self.menu[i][1], self.menu[i][2:])
>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 584, 
>in Build
>     self.build(self.flags)
>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 492, 
>in build
>     invoke_buildsystem(arg_list)
>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 111, 
>in invoke_buildsystem
>     app = buildapp.RunBuild(arg_list)
>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 102, 
>in RunBuild
>     app.main()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 196, 
>in main
>     self.run()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 384, 
>in run
>     self.get_files()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 657, 
>in get_files
>     self.checkout_files()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 954, 
>in checkout_files
>     int(os.environ.get("CHECKOUT_THREADS","2")))
>   File "d:\cygwin\home\gwright\ribosome\build\lib\chaingang.py", line 
>1009, in ProcessModules_grouped
>     ChainGang( newjobs, num ).run()
>   File "d:\cygwin\home\gwright\ribosome\build\lib\chaingang.py", line 530, 
>in run
>     raise err.error, self.error
>Build System Error: Error in threaded call
>-----------------------------------------------------------
>
>
>
>Since I am new to the producer I just want to make sure I am not
>doing something really wrong. Again, the build farm builds this
>same target just fine. Not sure what .buildrc file the build
>farm is using nowdays or any special options passed to ribosome.
>
>I will keep looking into it....
>--greg.
>
>
>>
>>Kinson
>>
>>Greg Wright wrote:
>>>So, is anyone having trouble building the producer lately?
>>>
>>>I have tried today on my linux and windows boxes and they
>>>die with, what seems, the same cvs error trying to check
>>>out some distribution libs. If I run the CVS command by hand
>>>I get:
>>>
>>>
>>>[~/ribosome]cvs -d 
>>>:ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout -r 
>>>"producer_11" win32-i386-vc7/p
>>>rotocol_dist/rtsp
>>>cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>>>cvs [checkout aborted]: could not find desired version 1.224 in 
>>>/cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>>>rdtclntlib.lib,v
>>>
>>>
>>>I don't know if it is a temporary cvs issue or some other problem.
>>>
>>>Here is my build setup:
>>>
>>>
>>>Build System (V2.4.4)
>>>time: Mon Jan 29 11:57:15 2007
>>>outfile: build.out
>>>branch: producer_11
>>>platform: win32-i386-vc7
>>>distribution/archive from: win32-i386-vc7
>>>build Type: debug
>>>build options: debug
>>>profile: 
>>>d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines
>>>cvs revision: producer_11
>>>copy target: debug
>>>target(s): toolsall
>>>
>>>I am using the same ~/.buildrc I use for client dev work.
>>>
>>>Are those dist libs suppose to be branched onto a 'producer_11' branch or
>>>something? It really doesn't look like they are, but, the nightly builds
>>>seem to work fine.
>>>
>>>Also, I would guess that I am using a BIF file that doesn't really need 
>>>to
>>>checkout any of those distlibs to begin with....
>>>
>>>
>>>
>>>--greg.
>>>
>>>_______________________________________________
>>>Helix-producer-dev mailing list
>>>Helix-producer-dev@helixcommunity.org
>>>http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>>
>>
>
>
>





>From: Rick Wager 
>To: helix-producer-dev@helixcommunity.org
>Subject: [Helix-producer-dev] Solaris 10/11 x86 (open Solaris) Producer 
>SDK?
>Date: Wed, 31 Jan 2007 04:56:59 -0700
>Hello All,
>
>I am new to this list and learning my way around the Helix community and 
>the building of the software.
>
>I have a strong interest in getting a working version of the producer SDK 
>for Solaris x86 (10 and/or OpenSolaris). Has anyone done this or is anyone 
>actively working on this?
>
>I am very willing to help with or take on this project but my efforts to 
>date have been less that successful.
>
>My progress to date:
>- CVS access set up, source code checked out
>- Learned how to use the build system ( I have to agree with other comments 
>I've seen here, the instructions are a bit out of date!)
>- Worked through numerous problems getting a compilation on the Solaris x86 
>platform with the Studio compilers, changing both source and build settings
>- Converted the threads implementation to be pthreads instead of Solaris 
>threads.
>- Managed to get producer.tgz and producersdk.tgz generated and 86 of 91 
>modules to build
>- I have a partially working executable of producer (prints help message 
>just fine :-) ), but it does nothing useful since it tends to core dump 
>and/or lacks codecs(?)
>
>At this point I'd like to avoid duplicating work that others may have 
>already done, or may be doing. And, if I continue on this project I think 
>some direction from someone who knows what is going on would make a huge 
>difference for my progress. Plus, I'd like to contribute the changes back 
>to the community at some point.
>
>Comments? Is there someone working on this that could use my help? Are 
>there any fundamental issues with a port to Solaris x86 that I am not aware 
>of?
>
>Thanks,
>Rick
>
>
>
>






>_______________________________________________
>Helix-producer-dev mailing list
>Helix-producer-dev@helixcommunity.org
>http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev

_________________________________________________________________
Valentine’s Day -- Shop for gifts that spell L-O-V-E at MSN Shopping 
http://shopping.msn.com/content/shp/?ctId=8323,ptnrid=37,ptnrdata=24095&tcode=wlmtagline


From kliu at real.com  Thu Feb  8 09:36:32 2007
From: kliu at real.com (Kinson Liu)
Date: Thu Feb  8 10:20:06 2007
Subject: [Helix-producer-dev] RE: Helix-producer-dev Digest, Vol 31, Issue
	2
In-Reply-To: 
References: 
Message-ID: <45CB5FA0.8060302@real.com>

Adding open-licensing@hc.org.

Kinson

donald snowdy wrote:
> Hello Helix Community....
>
> I have the same questions that Vishnuprasad has posted below, however, 
> I do not see a response to his questions?
>
> I am using the Helix Producer SDK in a custom application (C#.Net) 
> that may be sold commercially.  I am using the Helix Producer SDK to 
> run a job file (*.rpjf) to encode AVI files to a RealMedia (*.rm) files.
>
> I need all the components in the "bin" directory of Helix Producer SDK 
> (including the Helix Producer ActiveX Control) to be distributed along 
> with our product.
>
> Can you please clarify the Helix licensing?
>
> Thank you.
>
> Donald.
>
>> From: helix-producer-dev-request@helixcommunity.org
>> Reply-To: helix-producer-dev@helixcommunity.org
>> To: helix-producer-dev@helixcommunity.org
>> Subject: Helix-producer-dev Digest, Vol 31, Issue 2
>> Date: 31 Jan 2007 03:56:44 -0800
>>
>> Send Helix-producer-dev mailing list submissions to
>>     helix-producer-dev@helixcommunity.org
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>     http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>> or, via email, send a message with subject or body 'help' to
>>     helix-producer-dev-request@helixcommunity.org
>>
>> You can reach the person managing the list at
>>     helix-producer-dev-owner@helixcommunity.org
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of Helix-producer-dev digest..."
>
>
>> Today's Topics:
>>
>>    1. RE: About redisrtibutable components (Sujeet Kharkar)
>>    2. Web Cams? (Greg Wright)
>>    3. [Fwd: [Helix-producer-dev] Web Cams?] (SKHARKAR@real.com)
>>    4. Producer SDK - Licensing clarifications (Vishnuprasad M.C.)
>>    5. Build problems.... (Greg Wright)
>>    6. Producer SDK for OS/X Tiger Intel -- 1st    Attempt (Paul Curtis)
>>    7. Re: Build problems.... (Kinson Liu)
>>    8. Re: Build problems.... (Greg Wright)
>>    9. Solaris 10/11 x86 (open Solaris) Producer SDK? (Rick Wager)
>
>
>
>> From: "Sujeet Kharkar" 
>> To: vishnuprasadmc@yahoo.com, 
>> helix-producer-dev@helixcommunity.org,helix-producer-dev@helixcommunity.org 
>>
>> Subject: RE: [Helix-producer-dev] About redisrtibutable components
>> Date: Fri, 19 Jan 2007 16:53:33 +0530
>>
>> mediasink.dll is distributed with helix producer SDK and is not 
>> distributed
>> with helix producer plus and/or basic, so you should get it as part 
>> of SDK
>> and SDK licensing should apply.
>>
>> Thanks,
>> Sujeet
>>
>>
>> -----Original Message-----
>> From: helix-producer-dev-bounces@helixcommunity.org
>> [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of
>> Vishnuprasad M.C.
>> Sent: Friday, January 19, 2007 1:09 PM
>> To: helix-producer-dev@helixcommunity.org;
>> helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] About redisrtibutable components
>>
>> Dear Helix team,
>>
>> One dll named "mediasink.dll" is missing along with the Real Producer 11
>> Basic. Due to this our product could not encode properly. Is it 
>> possible to
>> distribute this component along with our product? Is there any licensing
>> problem for this?
>>
>> Regards,
>> Vishnuprasad M.C.
>>
>>
>>
>>
>>
>> __________________________________________________________
>> Yahoo! India Answers: Share what you know. Learn something new
>> http://in.answers.yahoo.com/
>> _______________________________________________
>> Helix-producer-dev mailing list
>> Helix-producer-dev@helixcommunity.org
>> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>
>>
>>
>
>
>
>
>
>> From: Greg Wright 
>> To: Helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] Web Cams?
>> Date: Tue, 23 Jan 2007 17:25:54 -0800
>> Anyone have any experience with what web cams are supported
>> under linux for use with the producer? I want to order
>> something cheap that I can use to work with video capture
>> on my linux desktop box here.
>>
>> I am thinking that just about any USB one would do the trick,
>> but I want to make sure first.
>>
>> --greg.
>>
>>
>>
>
>
>
>
>
>> From: SKHARKAR@real.com
>> To: nmcconnell@real.com
>> CC: Helix-producer-dev@helixcommunity.org
>> Subject: [Fwd: [Helix-producer-dev] Web Cams?]
>> Date: Tue, 23 Jan 2007 22:50:00 -0800 (PST)
>> Forwarding your request to Neal, who might have used web cam's. Most 
>> of my
>> capture experience is with Osprey cards.
>>
>> Thanks,
>> Sujeet
>>
>> ---------------------------- Original Message 
>> ----------------------------
>> Subject: [Helix-producer-dev] Web Cams?
>> From:    "Greg Wright" 
>> Date:    Tue, January 23, 2007 5:25 pm
>> To:      Helix-producer-dev@helixcommunity.org
>> -------------------------------------------------------------------------- 
>>
>>
>> Anyone have any experience with what web cams are supported
>> under linux for use with the producer? I want to order
>> something cheap that I can use to work with video capture
>> on my linux desktop box here.
>>
>> I am thinking that just about any USB one would do the trick,
>> but I want to make sure first.
>>
>> --greg.
>>
>>
>> _______________________________________________
>> Helix-producer-dev mailing list
>> Helix-producer-dev@helixcommunity.org
>> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>
>>
>>
>
>
>
>
>
>> From: "Vishnuprasad M.C." 
>> To: helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] Producer SDK - Licensing clarifications
>> Date: Wed, 24 Jan 2007 07:09:13 +0000 (GMT)
>> Dear Helix Team,
>>
>> Could you please clarify some doubts regarding licence.
>>
>> In our product, we need to encode media using Real Producer. For that 
>> we need all the components in the "bin" directory of Helix Producer 
>> SDK to be distributed along with our product. We just need the 
>> binaries with in this "bin" folder for encoding.
>>
>> Any particular licence is required for distributing these files with 
>> in "bin" folder ?
>> If yes, what type of licence that we need to purchase? And what is 
>> its cost? Where do I obtain this licence?
>>
>> I have downloaded the SDK from 
>> "http://forms.helixcommunity.org/helix/producersdk/index.html" v10. 
>> But latest version (v11.0.1)is available in 
>> "https://helix-producer.helixcommunity.org/downloads". Is there any 
>> difference between these two SDKs? Is separate licence required for 
>> distributing these two SDK files?
>>
>> About upgrade - shall we incorporate the latest SDK files along with 
>> our product on each release of new Producer SDK?
>>
>> Regards,
>> Vishnuprasad M.C.
>>
>>
>> ---------------------------------
>>  Here's a new way to find what you're looking for - Yahoo! Answers
>
>
>
>
>
>> From: Greg Wright 
>> To: Helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] Build problems....
>> Date: Mon, 29 Jan 2007 13:17:07 -0800
>> So, is anyone having trouble building the producer lately?
>>
>> I have tried today on my linux and windows boxes and they
>> die with, what seems, the same cvs error trying to check
>> out some distribution libs. If I run the CVS command by hand
>> I get:
>>
>>
>> [~/ribosome]cvs -d 
>> :ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout -r 
>> "producer_11" win32-i386-vc7/p
>> rotocol_dist/rtsp
>> cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>> cvs [checkout aborted]: could not find desired version 1.224 in 
>> /cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>> rdtclntlib.lib,v
>>
>>
>> I don't know if it is a temporary cvs issue or some other problem.
>>
>> Here is my build setup:
>>
>>
>> Build System (V2.4.4)
>> time: Mon Jan 29 11:57:15 2007
>> outfile: build.out
>> branch: producer_11
>> platform: win32-i386-vc7
>> distribution/archive from: win32-i386-vc7
>> build Type: debug
>> build options: debug
>> profile: 
>> d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines
>> cvs revision: producer_11
>> copy target: debug
>> target(s): toolsall
>>
>> I am using the same ~/.buildrc I use for client dev work.
>>
>> Are those dist libs suppose to be branched onto a 'producer_11' 
>> branch or
>> something? It really doesn't look like they are, but, the nightly builds
>> seem to work fine.
>>
>> Also, I would guess that I am using a BIF file that doesn't really 
>> need to
>> checkout any of those distlibs to begin with....
>>
>>
>>
>> --greg.
>>
>>
>
>
>
>
>
>> From: Paul Curtis 
>> To: Helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] Producer SDK for OS/X Tiger Intel -- 
>> 1st Attempt
>> Date: Mon, 29 Jan 2007 16:25:35 -0500
>> Mac OS/X 1.4.8 (Intel) with XCode 2.4
>> Using built-in specs.
>> Target: i686-apple-darwin8
>> Configured with: /private/var/tmp/gcc/gcc-5363.obj~28/src/configure 
>> --disable-checking -enable-werror --prefix=/usr --mandir=/share/man 
>> --enable-languages=c,objc,c++,obj-c++ 
>> --program-transform-name=/^[cg][^.-]*$/s/$/-4.0/ 
>> --with-gxx-include-dir=/include/c++/4.0.0 --with-slibdir=/usr/lib 
>> --build=powerpc-apple-darwin8 --with-arch=nocona --with-tune=generic 
>> --program-prefix= --host=i686-apple-darwin8 --target=i686-apple-darwin8
>> Thread model: posix
>> gcc version 4.0.1 (Apple Computer, Inc. build 5363)
>>
>> The build.out is available at http://www.terrapin.com/build.out.zip
>>
>> Build System Menu
>> Ribosome v2.4.4
>> -> Current Directory: /Users/pcurtis/src
>> [0] Set BIF branch (helix)
>> [1] Set Target(s) (producersdk_installer)
>> [2] Set Profile 
>> (/Users/pcurtis/src/build/umakepf/helix-producer-all-defines)
>> [3] run: build -trelease
>> [4] Toggle make depend & makefiles (-e -n)
>> [5] Toggle release (-trelease)
>> [6] Toggle 'make clean'  (-c)
>> [7] Toggle clobber (Dangerous!) (-C)
>> [8] Toggle halt-on-error (-p green)
>> [9] Toggle verbose mode (-v)
>> [10] Toggle static build (-tnodll)
>> [11] Checkout source for selected target now
>> [12] Set Tag/Branch/Timestamp
>> [13] Help Page (full help in build/doc/index.html)
>> [14] run history: build -trelease
>> [Q] Quit
>>
>>
>
>
>
>
>
>> From: Kinson Liu 
>> To: Greg Wright 
>> CC: Helix-producer-dev@helixcommunity.org
>> Subject: Re: [Helix-producer-dev] Build problems....
>> Date: Mon, 29 Jan 2007 13:38:00 -0800
>> FYI, rdtclntib.lib,v V1.224 is not found in the distribution 
>> repository. Did it ever exist?
>>
>> Kinson
>>
>> Greg Wright wrote:
>>> So, is anyone having trouble building the producer lately?
>>>
>>> I have tried today on my linux and windows boxes and they
>>> die with, what seems, the same cvs error trying to check
>>> out some distribution libs. If I run the CVS command by hand
>>> I get:
>>>
>>>
>>> [~/ribosome]cvs -d 
>>> :ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout 
>>> -r "producer_11" win32-i386-vc7/p
>>> rotocol_dist/rtsp
>>> cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>>> cvs [checkout aborted]: could not find desired version 1.224 in 
>>> /cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>>> rdtclntlib.lib,v
>>>
>>>
>>> I don't know if it is a temporary cvs issue or some other problem.
>>>
>>> Here is my build setup:
>>>
>>>
>>> Build System (V2.4.4)
>>> time: Mon Jan 29 11:57:15 2007
>>> outfile: build.out
>>> branch: producer_11
>>> platform: win32-i386-vc7
>>> distribution/archive from: win32-i386-vc7
>>> build Type: debug
>>> build options: debug
>>> profile: 
>>> d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines 
>>>
>>> cvs revision: producer_11
>>> copy target: debug
>>> target(s): toolsall
>>>
>>> I am using the same ~/.buildrc I use for client dev work.
>>>
>>> Are those dist libs suppose to be branched onto a 'producer_11' 
>>> branch or
>>> something? It really doesn't look like they are, but, the nightly 
>>> builds
>>> seem to work fine.
>>>
>>> Also, I would guess that I am using a BIF file that doesn't really 
>>> need to
>>> checkout any of those distlibs to begin with....
>>>
>>>
>>>
>>> --greg.
>>>
>>> _______________________________________________
>>> Helix-producer-dev mailing list
>>> Helix-producer-dev@helixcommunity.org
>>> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>>
>
>
>
>
>
>
>
>> From: Greg Wright 
>> To: Kinson Liu 
>> CC: Helix-producer-dev@helixcommunity.org
>> Subject: Re: [Helix-producer-dev] Build problems....
>> Date: Mon, 29 Jan 2007 13:57:22 -0800
>> Kinson Liu wrote:
>>> FYI, rdtclntib.lib,v V1.224 is not found in the distribution 
>>> repository. Did it ever exist?
>>
>> I don't know. This is the first time I have ever tried to build
>> the producer. If I just let ribosome grind away it eventually
>> spits this out:
>>
>> [#-00001970][2007-01-29 13:39:24][472][ERROR] : Error during job 
>> threading: Error in threaded call
>> [#-00001971][2007-01-29 13:39:24][472][ERROR] : --- Build System 
>> Error ------------------------------------
>> You have found a Ribosome bug.
>> -----------------------------------------------------------
>> --- Python Traceback --------------------------------------
>> ------------------------------------
>> Traceback (most recent call last):
>>   File "d:\cygwin\home\gwright\ribosome\build\bin\launcher.py", line 
>> 117, in __runTool
>>     tool.run()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 
>> 896, in run
>>     ShellToolApp().main()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 
>> 470, in main
>>     apply(self.menu[i][1], self.menu[i][2:])
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 
>> 584, in Build
>>     self.build(self.flags)
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 
>> 492, in build
>>     invoke_buildsystem(arg_list)
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\build_exe.py", line 
>> 111, in invoke_buildsystem
>>     app = buildapp.RunBuild(arg_list)
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 
>> 102, in RunBuild
>>     app.main()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 
>> 196, in main
>>     self.run()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 
>> 384, in run
>>     self.get_files()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 
>> 657, in get_files
>>     self.checkout_files()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\buildapp.py", line 
>> 954, in checkout_files
>>     int(os.environ.get("CHECKOUT_THREADS","2")))
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\chaingang.py", line 
>> 1009, in ProcessModules_grouped
>>     ChainGang( newjobs, num ).run()
>>   File "d:\cygwin\home\gwright\ribosome\build\lib\chaingang.py", line 
>> 530, in run
>>     raise err.error, self.error
>> Build System Error: Error in threaded call
>> -----------------------------------------------------------
>>
>>
>>
>> Since I am new to the producer I just want to make sure I am not
>> doing something really wrong. Again, the build farm builds this
>> same target just fine. Not sure what .buildrc file the build
>> farm is using nowdays or any special options passed to ribosome.
>>
>> I will keep looking into it....
>> --greg.
>>
>>
>>>
>>> Kinson
>>>
>>> Greg Wright wrote:
>>>> So, is anyone having trouble building the producer lately?
>>>>
>>>> I have tried today on my linux and windows boxes and they
>>>> die with, what seems, the same cvs error trying to check
>>>> out some distribution libs. If I run the CVS command by hand
>>>> I get:
>>>>
>>>>
>>>> [~/ribosome]cvs -d 
>>>> :ext:gwright@cvs.helixcommunity.org:/cvsroot/distribution checkout 
>>>> -r "producer_11" win32-i386-vc7/p
>>>> rotocol_dist/rtsp
>>>> cvs checkout: Updating win32-i386-vc7/protocol_dist/rtsp
>>>> cvs [checkout aborted]: could not find desired version 1.224 in 
>>>> /cvsroot/distribution/win32-i386-vc7/protocol_dist/rtsp/
>>>> rdtclntlib.lib,v
>>>>
>>>>
>>>> I don't know if it is a temporary cvs issue or some other problem.
>>>>
>>>> Here is my build setup:
>>>>
>>>>
>>>> Build System (V2.4.4)
>>>> time: Mon Jan 29 11:57:15 2007
>>>> outfile: build.out
>>>> branch: producer_11
>>>> platform: win32-i386-vc7
>>>> distribution/archive from: win32-i386-vc7
>>>> build Type: debug
>>>> build options: debug
>>>> profile: 
>>>> d:\cygwin\home\gwright\ribosome\build\umakepf\helix-producer-all-defines 
>>>>
>>>> cvs revision: producer_11
>>>> copy target: debug
>>>> target(s): toolsall
>>>>
>>>> I am using the same ~/.buildrc I use for client dev work.
>>>>
>>>> Are those dist libs suppose to be branched onto a 'producer_11' 
>>>> branch or
>>>> something? It really doesn't look like they are, but, the nightly 
>>>> builds
>>>> seem to work fine.
>>>>
>>>> Also, I would guess that I am using a BIF file that doesn't really 
>>>> need to
>>>> checkout any of those distlibs to begin with....
>>>>
>>>>
>>>>
>>>> --greg.
>>>>
>>>> _______________________________________________
>>>> Helix-producer-dev mailing list
>>>> Helix-producer-dev@helixcommunity.org
>>>> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>>>>
>>>
>>
>>
>>
>
>
>
>
>
>> From: Rick Wager 
>> To: helix-producer-dev@helixcommunity.org
>> Subject: [Helix-producer-dev] Solaris 10/11 x86 (open Solaris) 
>> Producer SDK?
>> Date: Wed, 31 Jan 2007 04:56:59 -0700
>> Hello All,
>>
>> I am new to this list and learning my way around the Helix community 
>> and the building of the software.
>>
>> I have a strong interest in getting a working version of the producer 
>> SDK for Solaris x86 (10 and/or OpenSolaris). Has anyone done this or 
>> is anyone actively working on this?
>>
>> I am very willing to help with or take on this project but my efforts 
>> to date have been less that successful.
>>
>> My progress to date:
>> - CVS access set up, source code checked out
>> - Learned how to use the build system ( I have to agree with other 
>> comments I've seen here, the instructions are a bit out of date!)
>> - Worked through numerous problems getting a compilation on the 
>> Solaris x86 platform with the Studio compilers, changing both source 
>> and build settings
>> - Converted the threads implementation to be pthreads instead of 
>> Solaris threads.
>> - Managed to get producer.tgz and producersdk.tgz generated and 86 of 
>> 91 modules to build
>> - I have a partially working executable of producer (prints help 
>> message just fine :-) ), but it does nothing useful since it tends to 
>> core dump and/or lacks codecs(?)
>>
>> At this point I'd like to avoid duplicating work that others may have 
>> already done, or may be doing. And, if I continue on this project I 
>> think some direction from someone who knows what is going on would 
>> make a huge difference for my progress. Plus, I'd like to contribute 
>> the changes back to the community at some point.
>>
>> Comments? Is there someone working on this that could use my help? 
>> Are there any fundamental issues with a port to Solaris x86 that I am 
>> not aware of?
>>
>> Thanks,
>> Rick
>>
>>
>>
>>
>
>
>
>
>
>
>> _______________________________________________
>> Helix-producer-dev mailing list
>> Helix-producer-dev@helixcommunity.org
>> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
> _________________________________________________________________
> Valentine's Day -- Shop for gifts that spell L-O-V-E at MSN Shopping 
> http://shopping.msn.com/content/shp/?ctId=8323,ptnrid=37,ptnrdata=24095&tcode=wlmtagline 
>
>
>
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev@helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>

-- 
------------------------------------------------------------------------
*Kinson Liu* | Software Development Engineer | RealNetworks, Inc. | 
kliu@real.com | 206.892.6177
From stevemc at real.com  Thu Feb  8 11:35:29 2007
From: stevemc at real.com (Steve McMillen)
Date: Thu Feb  8 12:19:02 2007
Subject: [Helix-producer-dev] Helix Producer SDK - Some
	Licensing	clarifications
In-Reply-To: <758592.12180.qm@web51109.mail.yahoo.com>
References: <758592.12180.qm@web51109.mail.yahoo.com>
Message-ID: <45CB7B81.7020501@real.com>

You can distribute the application in the way you are looking to do.

For details, see the "Commercial Distribution License" section in the 
following page:
https://helixcommunity.org/content/licenses

On 2/6/2007 1:15 AM, Vishnuprasad M.C. wrote:
> Dear Helix Team, 
>
> Could you please clarify some doubts regarding licence. 
>
> In our product, we need to encode media using Real Producer. 
> For that we need all the components in the "bin" directory of Helix Producer SDK to be distributed along with our product. 
> We just need the binaries with in this "bin" folder for encoding. 
>
> Any particular licence is required for distributing these files with in "bin" folder ? 
> If yes, what type of licence that we need to purchase? And what is its cost? Where do I obtain this licence? 
>
> I have downloaded the SDK from "http://forms.helixcommunity.org/helix/producersdk/index.html" v10. 
> But latest version (v11.0.1)is available in "https://helix-producer.helixcommunity.org/downloads".
> Is there any difference between these two SDKs? Is separate licence required for distributing these two SDK files? 
>
> About upgrade - shall we incorporate the latest SDK files along with our product on each release of new Producer SDK?
>
> Regards, 
> Vishnuprasad M.C.
>  				
> ---------------------------------
>  Here?s a new way to find what you're looking for - Yahoo! Answers 
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev@helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>   

From alanli at ivstream.com  Fri Feb  9 10:47:32 2007
From: alanli at ivstream.com (Alan Li)
Date: Fri Feb  9 11:30:55 2007
Subject: [Helix-producer-dev] Producer 11 SDK Plugin problems
In-Reply-To: 
Message-ID: <528903.81153.qm@web709.biz.mail.mud.yahoo.com>

Hi, 

I have tried to use two sample plugins (PrefilterPlugin and InputPlugin) on my SUSE Linux 10.1 box. After succesfully compiled both plugins as shared library and copied over to bin/plugins directory, they are working. After the RMACreateInstance are called, only QueryInterface are called with many iid's not being implemented. After that,  the  agents's objects are simply destructed by the producers' core and the shared library is shut down.

It seems like the reason for shutting down is due to all the unknow riid passed in for failed QI calls for the plugins, but why the actually implemented interfaces by the plugins such as IID_IHXTConfigurationAgent, IID_IHXTTransformFilter, or IID_IHXTInputFilter are never queried? thanks for any suggestions.

alan
From focus6888 at yahoo.com  Sun Feb 11 22:58:53 2007
From: focus6888 at yahoo.com (on focus)
Date: Sun Feb 11 23:41:37 2007
Subject: [Helix-producer-dev] how to create IHXTOutputFilter Plugin
Message-ID: <812809.15572.qm@web62110.mail.re1.yahoo.com>

Hello, Helix Producer plugin developers:

while ProducerSDK 11 has sample codes in mediasinkencoder.cpp show how to create IHXTPrefilter instance by

res = m_pFactory->BuildInstance(IID_IHXTPrefilter, pInitParams, (IUnknown**)&pPrefilter). but a similar call with IID_IHXTOutputFilter will fail miserably. Here are my questions:

1. How to use an Output Filter plugin to do output processing such as sending 
encoded data via a propietary network for the encoded samples?
2. How to create an IID_IHXTOutputFilter instance assuming it could be used 
by the system in some way?

thanks for any comments or sample codes, 

Frank,

 
---------------------------------
Never Miss an Email
Stay connected with Yahoo! Mail on your mobile. Get started!
From focus6888 at yahoo.com  Thu Feb 15 13:58:39 2007
From: focus6888 at yahoo.com (on focus)
Date: Thu Feb 15 15:17:31 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <812809.15572.qm@web62110.mail.re1.yahoo.com>
Message-ID: <343994.26880.qm@web62106.mail.re1.yahoo.com>

Hi, 
 
 On Windows platform, I am using both Producer 11 and Sever 11_1 to do acount-based unicast broadcsting following the documention. After setup, I launched server and then  issue the commend
 
 producer.exe -i c:\test.avi -o test.rm -sp producer:producer@192.168.1.3:50001/live.rm
 
 But the producer immediately outputs the error message:
 
 BroadcastDist: Unrecognized option config. BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval
 Error: Failed to establish a TCP connection with server 192.168.1.3 for authentication.
 
 Both my producer and server are on the same machine 192.168.1.3 and I turned off the firewall compeletely. I also tried this with server sitting on different machine, but it is same result. I don't know what is going on. And didn't find any documents that describe the problem either. 
 
 thanks for any suggestions.
 
 Frank
 
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
From skharkar at real.com  Thu Feb 15 22:57:21 2007
From: skharkar at real.com (Sujeet Kharkar)
Date: Thu Feb 15 23:39:07 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <343994.26880.qm@web62106.mail.re1.yahoo.com>
Message-ID: 


In command line that you are using -sp
username:password@ipaddress:port/streamname the port specified should be
HTTP port of the server.

Since default installation of server uses 50001-50050 as ports for receivers
dynamically created by mount point encfs, my assumption is that is not the
configured HTTP port.

Example config entries in rmserver.cfg file specifying concerned ports.

        
        
        



You should be able to find more information in help file installed with
producer (producer -m) in following chapters.
Chapter 14: Using the Command-Line Application 
Chapter 11: Running a Broadcast

Thanks,
Sujeet





-----Original Message-----
From: helix-producer-dev-bounces@helixcommunity.org
[mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
Sent: Friday, February 16, 2007 3:29 AM
To: helix-producer-dev@helixcommunity.org
Subject: [Helix-producer-dev] Live broadcasting issue

Hi, 
 
 On Windows platform, I am using both Producer 11 and Sever 11_1 to do
acount-based unicast broadcsting following the documention. After setup, I
launched server and then  issue the commend
 
 producer.exe -i c:\test.avi -o test.rm -sp
producer:producer@192.168.1.3:50001/live.rm
 
 But the producer immediately outputs the error message:
 
 BroadcastDist: Unrecognized option config.
BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval
 Error: Failed to establish a TCP connection with server 192.168.1.3 for
authentication.
 
 Both my producer and server are on the same machine 192.168.1.3 and I
turned off the firewall compeletely. I also tried this with server sitting
on different machine, but it is same result. I don't know what is going on.
And didn't find any documents that describe the problem either. 
 
 thanks for any suggestions.
 
 Frank
 
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
_______________________________________________
Helix-producer-dev mailing list
Helix-producer-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev


From focus6888 at yahoo.com  Fri Feb 16 16:54:16 2007
From: focus6888 at yahoo.com (on focus)
Date: Fri Feb 16 17:35:50 2007
Subject: [Helix-producer-dev] Live broadcasting issue
Message-ID: <911166.29922.qm@web62110.mail.re1.yahoo.com>

Hi, Sujeet,

first thanks for the reply. A couple clarification based on your message:

1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
2. I didn't find any section in *.cfg file that has those definitions in your email.

Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
 producer.exe -i c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm

It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,

The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,

error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)

access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12

I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user name/password.

Any suggestion to diagnose the problem will greatly appreciated.

Frank


Sujeet Kharkar  wrote: 
In command line that you are using -sp
username:password@ipaddress:port/streamname the port specified should be
HTTP port of the server.

Since default installation of server uses 50001-50050 as ports for receivers
dynamically created by mount point encfs, my assumption is that is not the
configured HTTP port.

Example config entries in rmserver.cfg file specifying concerned ports.


        
        
        



You should be able to find more information in help file installed with
producer (producer -m) in following chapters.
Chapter 14: Using the Command-Line Application 
Chapter 11: Running a Broadcast

Thanks,
Sujeet





-----Original Message-----
From: helix-producer-dev-bounces@helixcommunity.org
[mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
Sent: Friday, February 16, 2007 3:29 AM
To: helix-producer-dev@helixcommunity.org
Subject: [Helix-producer-dev] Live broadcasting issue

Hi, 
 
 On Windows platform, I am using both Producer 11 and Sever 11_1 to do
acount-based unicast broadcsting following the documention. After setup, I
launched server and then  issue the commend
 
 producer.exe -i c:\test.avi -o test.rm -sp
producer:producer@192.168.1.3:50001/live.rm
 
 But the producer immediately outputs the error message:
 
 BroadcastDist: Unrecognized option config.
BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval
 Error: Failed to establish a TCP connection with server 192.168.1.3 for
authentication.
 
 Both my producer and server are on the same machine 192.168.1.3 and I
turned off the firewall compeletely. I also tried this with server sitting
on different machine, but it is same result. I don't know what is going on.
And didn't find any documents that describe the problem either. 
 
 thanks for any suggestions.
 
 Frank
 
---------------------------------
Never miss an email again!
Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
_______________________________________________
Helix-producer-dev mailing list
Helix-producer-dev@helixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev



  
---------------------------------
Looking for earth-friendly autos? 
 Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.  
 
---------------------------------
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
From stevemc at real.com  Fri Feb 16 17:11:16 2007
From: stevemc at real.com (Steve McMillen)
Date: Fri Feb 16 17:52:46 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <911166.29922.qm@web62110.mail.re1.yahoo.com>
References: <911166.29922.qm@web62110.mail.re1.yahoo.com>
Message-ID: <45D65634.1050700@real.com>

Here are some things to try (from the Producer Release Notes).  #4 is 
most relevant I think.

   1. If you are unable to establish a player connection to a live
      broadcast, and you want to determine whether the problem is a
      configuration problem in RealProducer, try the following:
         1. To confirm that the stream has reached the server, check
            that the stream appears in the Server Monitor's connections
            tab.  You should see an entry of Type 'encoder' along with
            the proper filename.
         2. If you are using the Legacy Server broadcast method, ensure
            that you have the correct Server mount point ("/encoder/" by
            default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/encoder/live.rm
         3. If you are using any of the Server 9 Push broadcast methods,
            ensure that you have the correct Server mount point
            ("/broadcast/" by default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/broadcast/live.rm
         4. If you are using the Pull broadcast method, ensure that you
            have the correct Server mount point ("/broadcast/pull/" by
            default) in your player URL.  For example,
            rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm 
   2. You must use a password when using the Pull broadcast method from
      the command line application (-si).  If you wish to broadcast
      using the Pull broadcast method and not require a password, use a
      server file with the server definition option (-sd).
   3. When using the *Account-Based Push* broadcast method, be sure the
      username and password are added to the correct realm on the Helix
      Server. For the *Account-based Push* broadcast method, users
      should be added to the Helix Server *SecureRBSEncoder* realm.
   4. When using the *Account-based Push* broadcast method with Helix
      Server 9, you may experience problems making new Account-based
      Push connections if the Helix Server Administrator is used to
      reconfigure the Helix Server while existing Account-based Push
      encodes are running. To avoid this problem, do not reconfigure the
      Helix Server while Account-based Push encodes are active. You can
      identify Account-based Push encodes by looking for pairs of
      entries as follows in the Helix Server Monitor:
      IP ADDRESS 	TYPE 	DURATION 	FILENAME
        	encoder 	00:02:27 	live.rm
      172.23.104.111 	player 	00:02:27 	encfs/servvar.set

      Each of these entries represent a single Account-based Push
      broadcast session.


Note: I can't recall if the Helix Server monitor page 
(http://:/monitor.html) is available thru the 
hc.org build.  If not, then I'm not sure how to do the equivalent w/o 
it.  Could do it via the registry but that's a little complicated.

Thx, Steve

On 2/16/2007 4:54 PM, on focus wrote:
> Hi, Sujeet,
>
> first thanks for the reply. A couple clarification based on your message:
>
> 1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
> 2. I didn't find any section in *.cfg file that has those definitions in your email.
>
> Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
>  producer.exe -i c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm
>
> It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,
>
> The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,
>
> error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)
>
> access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12
>
> I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user name/password.
>
> Any suggestion to diagnose the problem will greatly appreciated.
>
> Frank
>
>
> Sujeet Kharkar  wrote: 
> In command line that you are using -sp
> username:password@ipaddress:port/streamname the port specified should be
> HTTP port of the server.
>
> Since default installation of server uses 50001-50050 as ports for receivers
> dynamically created by mount point encfs, my assumption is that is not the
> configured HTTP port.
>
> Example config entries in rmserver.cfg file specifying concerned ports.
>
>
>         
>         
>         
>
>
>
> You should be able to find more information in help file installed with
> producer (producer -m) in following chapters.
> Chapter 14: Using the Command-Line Application 
> Chapter 11: Running a Broadcast
>
> Thanks,
> Sujeet
>
>
>
>
>
> -----Original Message-----
> From: helix-producer-dev-bounces@helixcommunity.org
> [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
> Sent: Friday, February 16, 2007 3:29 AM
> To: helix-producer-dev@helixcommunity.org
> Subject: [Helix-producer-dev] Live broadcasting issue
>
> Hi, 
>  
>  On Windows platform, I am using both Producer 11 and Sever 11_1 to do
> acount-based unicast broadcsting following the documention. After setup, I
> launched server and then  issue the commend
>  
>  producer.exe -i c:\test.avi -o test.rm -sp
> producer:producer@192.168.1.3:50001/live.rm
>  
>  But the producer immediately outputs the error message:
>  
>  BroadcastDist: Unrecognized option config.
> BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval
>  Error: Failed to establish a TCP connection with server 192.168.1.3 for
> authentication.
>  
>  Both my producer and server are on the same machine 192.168.1.3 and I
> turned off the firewall compeletely. I also tried this with server sitting
> on different machine, but it is same result. I don't know what is going on.
> And didn't find any documents that describe the problem either. 
>  
>  thanks for any suggestions.
>  
>  Frank
>  
> ---------------------------------
> Never miss an email again!
> Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev@helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>
>
>   
> ---------------------------------
> Looking for earth-friendly autos? 
>  Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.  
>  
> ---------------------------------
> It's here! Your new message!
> Get new email alerts with the free Yahoo! Toolbar.
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev@helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>
>   

From nikko666 at gmail.com  Mon Feb 19 02:21:28 2007
From: nikko666 at gmail.com (nikko666)
Date: Mon Feb 19 03:02:27 2007
Subject: [Helix-producer-dev] input file from the WEB
Message-ID: <4bf3dd380702190221i29d4d67ep720d432d299969e2@mail.gmail.com>

Hi,

I would like to encode a file that is on the WEB but when I start the
command "producer -i http://mms1/music.mp3 -o C:\music.rm" an error occurs.
It says me that the file "C:\Documents and
Settings\nikko\http:\mms1\music.mp3" can't be found.

What's the problem? Is it possible to encode a file that's come from the
WEB?

Thanks, Nicolas
From stevemc at real.com  Mon Feb 19 09:28:44 2007
From: stevemc at real.com (Steve McMillen)
Date: Mon Feb 19 10:09:32 2007
Subject: [Helix-producer-dev] input file from the WEB
In-Reply-To: <4bf3dd380702190221i29d4d67ep720d432d299969e2@mail.gmail.com>
References: <4bf3dd380702190221i29d4d67ep720d432d299969e2@mail.gmail.com>
Message-ID: <45D9DE4C.5010200@real.com>

There is no HTTP file input support in Producer.  You'll need to 
download the file first and then encode it.    I'm sure there are some 
command line utilities that run on Windows that do this if you are 
scripting the process.

On 2/19/2007 2:21 AM, nikko666 wrote:
> Hi,
>
> I would like to encode a file that is on the WEB but when I start the
> command "producer -i http://mms1/music.mp3 -o C:\music.rm" an error 
> occurs.
> It says me that the file "C:\Documents and
> Settings\nikko\http:\mms1\music.mp3" can't be found.
>
> What's the problem? Is it possible to encode a file that's come from the
> WEB?
>
> Thanks, Nicolas
> _______________________________________________
> Helix-producer-dev mailing list
> Helix-producer-dev@helixcommunity.org
> http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev
>


From focus6888 at yahoo.com  Mon Feb 19 11:09:31 2007
From: focus6888 at yahoo.com (on focus)
Date: Mon Feb 19 12:46:47 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <45D65634.1050700@real.com>
Message-ID: <55106.35100.qm@web62104.mail.re1.yahoo.com>

Steve, I tried to verify all the steps you have suggested, but none of them suggests where the problem is. Particularly, I checked my Helix Server (again 11-1 version) monitor session, it doesn't show there is connection from producer (Helix producer 11). I am using account based push method without any further old installation (all brand new machine with first installation of Helix server and producer). Here is what exactly I did:

1. Install Helix Server 11-1 and create the SecureRBSEncoder Realm and add a new user and password pair to the new Realm, test:testnow

2. Fire up the server and then start the Helix Producer 11 with the following command:

server:~/helixstuff/producer> producer -i testi420l.avi -o test.rm -sp :testnow@192.168.1.4:1554/live.rm
Helix DNA(TM) Producer 11.0 Build number: 11.0.0.2013
Info: Preparing to encode file "testi420l.avi" to file "test.rm"
Warning: Ignoring enableTwoPass for live encoding
Info: Starting encode
.........
........ Keep encoding until it finishes with test.rm (correctly), but there is NO live.rm connection from Helix Server MOnitoing or by using the realplayer to try to play it

realplay rtsp://192.168.1.4:1554/broadcast/live.rm

with server's log saying: 16-Feb-2007 09:16:22.UNKNOWN tmplgpln(4607): 52: Error retrieving URL `broadcast/live.rm' (Invalid path)

I tried on both Windows and Linux platform but none of them works. And read all the documents or online help I can find.  I am quite frustrated with what is going on. Questions:

1. Does Real know if Helix Server 11_1 release work with Helix Producer 11 release in live broadcasting, in either PUSH or PULL mode?

2. If it works in your internal test, could you give me a configuration of machine and software setup to precisely make the simplist and most reliable live broadcasting?

thanks very much,

Frank,

Steve McMillen  wrote:        Here are some things to try (from the Producer Release Notes).  #4 is most relevant I think.
 
    
   If you are unable to establish a player connection to a live broadcast, and you want to determine whether the problem is a configuration problem in RealProducer, try the following:            
      To confirm that the stream has reached the server, check that the stream appears in the Server Monitor's connections tab.  You should see an entry of Type 'encoder' along with the proper filename.        
      If you are using the Legacy Server broadcast method, ensure that you have the correct Server mount point ("/encoder/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/encoder/live.rm        
      If you are using any of the Server 9 Push broadcast methods, ensure that you have the correct Server mount point ("/broadcast/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/broadcast/live.rm        
      If you are using the Pull broadcast method, ensure that you have the correct Server mount point ("/broadcast/pull/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm       
      
   You must use a password when using the Pull broadcast method from the command line application (-si).  If you wish to broadcast using the Pull broadcast method and not require a password, use a server file with the server definition option (-sd).    
   When using the Account-Based Push broadcast method, be sure the username and password are added to the correct realm on the Helix Server. For the Account-based Push broadcast method, users should be added to the Helix Server SecureRBSEncoder realm.    
   When using the Account-based Push broadcast method with Helix Server 9, you may experience problems making new Account-based Push connections if the Helix Server Administrator is used to reconfigure the Helix Server while existing Account-based Push encodes are running. To avoid this problem, do not reconfigure the Helix Server while Account-based Push encodes are active. You can identify Account-based Push encodes by looking for pairs of entries as follows in the Helix Server Monitor:
                                IP ADDRESS           TYPE           DURATION           FILENAME                                         encoder           00:02:27           live.rm                             172.23.104.111           player           00:02:27           encfs/servvar.set                          Each of these entries represent a single Account-based Push broadcast session.
    
 
 Note: I can't recall if the Helix Server monitor page (http://:/monitor.html) is available thru the hc.org build.  If not, then I'm not sure how to do the equivalent w/o it.  Could do it via the registry but that's a little complicated.
 
 Thx, Steve
 
 On 2/16/2007 4:54 PM, on focus wrote:    
Hi, Sujeet,

first thanks for the reply. A couple clarification based on your message:

1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
2. I didn't find any section in *.cfg file that has those definitions in your email.

Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
 producer.exe -i c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm

It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,

The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,

error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)

access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12

I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user name/password.

Any suggestion to diagnose the problem will greatly appreciated.

Frank


Sujeet Kharkar  wrote: 
In command line that you are using -sp
username:password@ipaddress:port/streamname the port specified should be
HTTP port of the server.

Since default installation of server uses 50001-50050 as ports for receivers
dynamically created by mount point encfs, my assumption is that is not the
configured HTTP port.

Example config entries in rmserver.cfg file specifying concerned ports.


        
        
        



You should be able to find more information in help file installed with
producer (producer -m) in following chapters.
Chapter 14: Using the Command-Line Application 
Chapter 11: Running a Broadcast

Thanks,
Sujeet





-----Original Message-----
From: helix-producer-dev-bounces@helixcommunity.org [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
Sent: Friday, February 16, 2007 3:29 AM
To: helix-producer-dev@helixcommunity.org Subject: [Helix-producer-dev] Live broadcasting issue  Hi,     On Windows platform, I am using both Producer 11 and Sever 11_1 to do acount-based unicast broadcsting following the documention. After setup, I launched server and then  issue the commend    producer.exe -i c:\test.avi -o test.rm -sp producer:producer@192.168.1.3:50001/live.rm    But the producer immediately outputs the error message:    BroadcastDist: Unrecognized option config. BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval  Error: Failed to establish a TCP connection with server 192.168.1.3 for authentication.    Both my producer and server are on the same machine 192.168.1.3 and I turned off the firewall compeletely. I also tried this with server sitting on different machine, but it is same result. I don't know what is going on. And didn't find any documents that describe the problem either.     thanks for any suggestions.    Frank  
 --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev       --------------------------------- Looking for earth-friendly autos?   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.     --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev    
  
 

 
---------------------------------
Now that's room service! Choose from over 150,000 hotels 
in 45,000 destinations on Yahoo! Travel to find your fit.
 
---------------------------------
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
From stevemc at real.com  Mon Feb 19 20:13:06 2007
From: stevemc at real.com (Steve McMillen)
Date: Mon Feb 19 20:53:52 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <55106.35100.qm@web62104.mail.re1.yahoo.com>
References: <55106.35100.qm@web62104.mail.re1.yahoo.com>
Message-ID: <45DA7552.7030306@real.com>

Since you were trying to do account-based push, I figured you were using 
the commercial server.  If you are using the helix community server, 
then you'll need to stick with password-only method.  Following link 
provides instructions on how:
https://producerapps.helixcommunity.org/cmdproducer/docs/howto-broadcast-to-helixserver.html

If you are using the commercial server, then you may just have your 
syntax wrong.
I have server 11.1 installed on my laptop (windows).  I just fired up 
producer 11 and started a stream using:

    producer -ac 0 -sp username:password@localhost/live.rm

I then saw the two streams in the server monitor and was able to connect 
using rtsp://localhost/broadcast/live.rm.

I noticed you are not supplying a username (before the colon).  Oddly 
the producer continues w/o error but never connects to the server.  If 
you add the username you will find that the producer will connect and 
you will see the two streams in the server monitor described in the 
troubleshooting tips.

Thx, Steve

On 2/19/2007 11:09 AM, on focus wrote:
> Steve, I tried to verify all the steps you have suggested, but none of 
> them suggests where the problem is. Particularly, I checked my Helix 
> Server (again 11-1 version) monitor session, it doesn't show there is 
> connection from producer (Helix producer 11). I am using account based 
> push method without any further old installation (all brand new 
> machine with first installation of Helix server and producer). Here is 
> what exactly I did:
>
> 1. Install Helix Server 11-1 and create the SecureRBSEncoder Realm and 
> add a new user and password pair to the new Realm, test:testnow
>
> 2. Fire up the server and then start the Helix Producer 11 with the 
> following command:
>
> server:~/helixstuff/producer> producer -i testi420l.avi -o test.rm -sp 
> :testnow@192.168.1.4:1554/live.rm
> Helix DNA(TM) Producer 11.0 Build number: 11.0.0.2013
> Info: Preparing to encode file "testi420l.avi" to file "test.rm"
> Warning: Ignoring enableTwoPass for live encoding
> Info: Starting encode
> .........
> ........ Keep encoding until it finishes with test.rm (correctly), but 
> there is NO live.rm connection from Helix Server MOnitoing or by using 
> the realplayer to try to play it
>
> realplay rtsp://192.168.1.4:1554/broadcast/live.rm
>
> with server's log saying: 16-Feb-2007 09:16:22.UNKNOWN tmplgpln(4607): 
> 52: Error retrieving URL `broadcast/live.rm' (Invalid path)
>
> I tried on both Windows and Linux platform but none of them works. And 
> read all the documents or online help I can find.  I am quite 
> frustrated with what is going on. Questions:
>
> 1. Does Real know if Helix Server 11_1 release work with Helix 
> Producer 11 release in live broadcasting, in either PUSH or PULL mode?
>
> 2. If it works in your internal test, could you give me a 
> configuration of machine and software setup to precisely make the 
> simplist and most reliable live broadcasting?
>
> thanks very much,
>
> Frank,
>
> */Steve McMillen /* wrote:
>
>     Here are some things to try (from the Producer Release Notes).  #4
>     is most relevant I think.
>
>        1. If you are unable to establish a player connection to a live
>           broadcast, and you want to determine whether the problem is
>           a configuration problem in RealProducer, try the following:
>              1. To confirm that the stream has reached the server,
>                 check that the stream appears in the Server Monitor's
>                 connections tab.  You should see an entry of Type
>                 'encoder' along with the proper filename.
>              2. If you are using the Legacy Server broadcast method,
>                 ensure that you have the correct Server mount point
>                 ("/encoder/" by default) in your player URL.  For
>                 example,
>                 rtsp://yourserver.yourcompany.com:554/encoder/live.rm
>              3. If you are using any of the Server 9 Push broadcast
>                 methods, ensure that you have the correct Server mount
>                 point ("/broadcast/" by default) in your player URL. 
>                 For example,
>                 rtsp://yourserver.yourcompany.com:554/broadcast/live.rm
>              4. If you are using the Pull broadcast method, ensure
>                 that you have the correct Server mount point
>                 ("/broadcast/pull/" by default) in your player URL. 
>                 For example,
>                 rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm 
>
>        2. You must use a password when using the Pull broadcast method
>           from the command line application (-si).  If you wish to
>           broadcast using the Pull broadcast method and not require a
>           password, use a server file with the server definition
>           option (-sd).
>        3. When using the *Account-Based Push* broadcast method, be
>           sure the username and password are added to the correct
>           realm on the Helix Server. For the *Account-based Push*
>           broadcast method, users should be added to the Helix Server
>           *SecureRBSEncoder* realm.
>        4. When using the *Account-based Push* broadcast method with
>           Helix Server 9, you may experience problems making new
>           Account-based Push connections if the Helix Server
>           Administrator is used to reconfigure the Helix Server while
>           existing Account-based Push encodes are running. To avoid
>           this problem, do not reconfigure the Helix Server while
>           Account-based Push encodes are active. You can identify
>           Account-based Push encodes by looking for pairs of entries
>           as follows in the Helix Server Monitor:
>           IP ADDRESS 	TYPE 	DURATION 	FILENAME
>             	encoder 	00:02:27 	live.rm
>           172.23.104.111 	player 	00:02:27 	encfs/servvar.set
>
>           Each of these entries represent a single Account-based Push
>           broadcast session.
>
>
>     Note: I can't recall if the Helix Server monitor page
>     (http://:/monitor.html) is available thru
>     the hc.org build.  If not, then I'm not sure how to do the
>     equivalent w/o it.  Could do it via the registry but that's a
>     little complicated.
>
>     Thx, Steve
>
>     On 2/16/2007 4:54 PM, on focus wrote:
>>     Hi, Sujeet,
>>
>>     first thanks for the reply. A couple clarification based on your message:
>>
>>     1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
>>     2. I didn't find any section in *.cfg file that has those definitions in your email.
>>
>>     Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
>>      producer.exe -i
>>      c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm
>>
>>     It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,
>>
>>     The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,
>>
>>     error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)
>>
>>     access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12
>>
>>     I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user
>>      name/password.
>>
>>     Any suggestion to diagnose the problem will greatly appreciated.
>>
>>     Frank
>>
>>
>>     Sujeet Kharkar  wrote: 
>>     In command line that you are using -sp
>>     username:password@ipaddress:port/streamname the port specified should be
>>     HTTP port of the server.
>>
>>     Since default installation of server uses 50001-50050 as ports for receivers
>>     dynamically created by mount point encfs, my assumption is that is not the
>>     configured HTTP port.
>>
>>     Example config entries in rmserver.cfg file specifying concerned ports.
>>
>>
>>             
>>             
>>             
>>
>>
>>
>>     You should be able to find more information in help file installed with
>>     producer (producer -m) in following chapters.
>>     Chapter 14: Using the Command-Line Application 
>>     Chapter 11: Running a Broadcast
>>
>>     Thanks,
>>     Sujeet
>>
>>
>>
>>
>>
>>     -----Original
>>      Message-----
>>     From: helix-producer-dev-bounces@helixcommunity.org [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
>>     Sent: Friday, February 16, 2007 3:29 AM
>>     To: helix-producer-dev@helixcommunity.org Subject: [Helix-producer-dev] Live broadcasting issue  Hi,     On Windows platform, I am using both Producer 11 and Sever 11_1 to do acount-based unicast broadcsting following the documention. After setup, I launched server and then  issue the commend    producer.exe -i c:\test.avi -o test.rm -sp producer:producer@192.168.1.3:50001/live.rm    But the producer
>>      immediately outputs the error message:    BroadcastDist: Unrecognized option config. BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval  Error: Failed to establish a TCP connection with server 192.168.1.3 for authentication.    Both my producer and server are on the same machine 192.168.1.3 and I turned off the firewall compeletely. I also tried this with server sitting on different machine, but it is same result. I don't know what is going on. And didn't find any documents that describe the problem either.     thanks for any suggestions.    Frank   --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev       --------------------------------- Looking for earth-friendly autos?   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.     --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev    
>

From focus6888 at yahoo.com  Thu Feb 22 13:27:04 2007
From: focus6888 at yahoo.com (on focus)
Date: Thu Feb 22 14:07:11 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <45DA7552.7030306@real.com>
Message-ID: <623211.77560.qm@web62106.mail.re1.yahoo.com>

Hi, Steve, 

thanks for help. As you mentioned, I am using Helix server and producer, not commercial ones, so using the link you provided, it does work with password only push method. I also tried to use commercial's rmserver.cfg with hlxserver executable, it also works. So here are follow-up questions:

1. Why there is such difference between these two releases determined by the configuration file?
2. In what extent, Helix Server11-1&Producer11 mirrors the functionalities of commercial release of RM server and producer? are there any documents that I can refer to?

3. If they don't match up with each other, is there anyway we can build a full Helix server and producer from Helix source codes base to match the RM commercial release? or it is simply impossible because RM commercial release is internally difference from the public Helix source release?

thanks a lot,

Frank,

Steve McMillen  wrote:        Since you were trying to do account-based push, I figured you were using the commercial server.  If you are using the helix community server, then you'll need to stick with password-only method.  Following link provides instructions on how:
 https://producerapps.helixcommunity.org/cmdproducer/docs/howto-broadcast-to-helixserver.html
 
 If you are using the commercial server, then you may just have your syntax wrong.
 I have server 11.1 installed on my laptop (windows).  I just fired up producer 11 and started a stream using:
 
     producer -ac 0 -sp username:password@localhost/live.rm
 
 I then saw the two streams in the server monitor and was able to connect using rtsp://localhost/broadcast/live.rm.
 
 I noticed you are not supplying a username (before the colon).  Oddly the producer continues w/o error but never connects to the server.  If you add the username you will find that the producer will connect and you will see the two streams in the server monitor described in the troubleshooting tips.
 
 Thx, Steve
 
 On 2/19/2007 11:09 AM, on focus wrote: Steve, I tried to verify all the steps you have suggested, but none of them suggests where the problem is. Particularly, I checked my Helix Server (again 11-1 version) monitor session, it doesn't show there is connection from producer (Helix producer 11). I am using account based push method without any further old installation (all brand new machine with first installation of Helix server and producer). Here is what exactly I did:
   
 1. Install Helix Server 11-1 and create the SecureRBSEncoder Realm and add a new user and password pair to the new Realm, test:testnow
   
 2. Fire up the server and then start the Helix Producer 11 with the following command:
   
 server:~/helixstuff/producer> producer -i testi420l.avi -o test.rm -sp :testnow@192.168.1.4:1554/live.rm
 Helix DNA(TM) Producer 11.0 Build number: 11.0.0.2013
 Info: Preparing to encode file "testi420l.avi" to file "test.rm"
 Warning: Ignoring enableTwoPass for live encoding
 Info: Starting encode
 .........
 ........ Keep encoding until it finishes with test.rm (correctly), but there is NO live.rm connection from Helix Server MOnitoing or by using the realplayer to try to play it
   
 realplay rtsp://192.168.1.4:1554/broadcast/live.rm
   
 with server's log saying: 16-Feb-2007 09:16:22.UNKNOWN tmplgpln(4607): 52: Error retrieving URL `broadcast/live.rm' (Invalid path)
   
 I tried on both Windows and Linux platform but none of them works. And read all the documents or online help I can find.  I am quite frustrated with what is going on. Questions:
   
 1. Does Real know if Helix Server 11_1 release work with Helix Producer 11 release in live broadcasting, in either PUSH or PULL mode?
   
 2. If it works in your internal test, could you give me a configuration of machine and software setup to precisely make the simplist and most reliable live broadcasting?
   
 thanks very much,
   
 Frank,
   
   Steve McMillen  wrote:         Here are some things to try (from the Producer Release Notes).  #4 is most relevant I think.
     
            
   If you are unable to establish a player connection to a live broadcast, and you want to determine whether the problem is a configuration problem in RealProducer, try the following:                    
      To confirm that the stream has reached the server, check that the stream appears in the Server Monitor's connections tab.  You should see an entry of Type 'encoder' along with the proper filename.            
      If you are using the Legacy Server broadcast method, ensure that you have the correct Server mount point ("/encoder/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/encoder/live.rm                      
      If you are using any of the Server 9 Push broadcast methods, ensure that you have the correct Server mount point ("/broadcast/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/broadcast/live.rm                      
      If you are using the Pull broadcast method, ensure that you have the correct Server mount point ("/broadcast/pull/" by default) in your player URL.  For example, rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm                     
              
   You must use a password when using the Pull broadcast method from the command line application (-si).  If you wish to broadcast using the Pull broadcast method and not require a password, use a server file with the server definition option (-sd).        
   When using the Account-Based Push broadcast method, be sure the username and password are added to the correct realm on the Helix Server. For the Account-based Push broadcast method, users should be added to the Helix Server SecureRBSEncoder realm.        
   When using the Account-based Push broadcast method with Helix Server 9, you may experience problems making new Account-based Push connections if the Helix Server Administrator is used to reconfigure the Helix Server while existing Account-based Push encodes are running. To avoid this problem, do not reconfigure the Helix Server while Account-based Push encodes are active. You can identify Account-based Push encodes by looking for pairs of entries as follows in the Helix Server Monitor:
                                                IP ADDRESS               TYPE               DURATION               FILENAME                                                         encoder               00:02:27               live.rm                                         172.23.104.111               player               00:02:27               encfs/servvar.set                                          Each of these entries represent a single Account-based Push broadcast session.
            
     
 Note: I can't recall if the Helix Server monitor page (http://:/monitor.html) is available thru the hc.org build.  If not, then I'm not sure how to do the equivalent w/o it.  Could do it via the registry but that's a little complicated.
     
 Thx, Steve
     
 On 2/16/2007 4:54 PM, on focus wrote:            
Hi, Sujeet,

first thanks for the reply. A couple clarification based on your message:

1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
2. I didn't find any section in *.cfg file that has those definitions in your email.

Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
 producer.exe -i
 c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm

It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,

The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,

error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)

access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb] [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12

I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user
 name/password.

Any suggestion to diagnose the problem will greatly appreciated.

Frank


Sujeet Kharkar  wrote: 
In command line that you are using -sp
username:password@ipaddress:port/streamname the port specified should be
HTTP port of the server.

Since default installation of server uses 50001-50050 as ports for receivers
dynamically created by mount point encfs, my assumption is that is not the
configured HTTP port.

Example config entries in rmserver.cfg file specifying concerned ports.


        
        
        



You should be able to find more information in help file installed with
producer (producer -m) in following chapters.
Chapter 14: Using the Command-Line Application 
Chapter 11: Running a Broadcast

Thanks,
Sujeet





-----Original
 Message-----
From: helix-producer-dev-bounces@helixcommunity.org [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
Sent: Friday, February 16, 2007 3:29 AM
To: helix-producer-dev@helixcommunity.org Subject: [Helix-producer-dev] Live broadcasting issue  Hi,     On Windows platform, I am using both Producer 11 and Sever 11_1 to do acount-based unicast broadcsting following the documention. After setup, I launched server and then  issue the commend    producer.exe -i c:\test.avi -o test.rm -sp producer:producer@192.168.1.3:50001/live.rm    But the producer  immediately outputs the error message:    BroadcastDist: Unrecognized option config. BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval  Error: Failed to establish a TCP connection with server 192.168.1.3 for authentication.    Both my producer and server are on the same machine 192.168.1.3 and I turned off the firewall compeletely. I also tried this with server sitting on different machine, but it is same result. I don't know what is going on. And didn't find any documents that describe the problem either.     thanks for any suggestions.    Frank  
 --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev       --------------------------------- Looking for earth-friendly autos?   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.     --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev    
          
 

 
---------------------------------
Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.
 
---------------------------------
Be a PS3 game guru.
Get your game face on with the latest PS3 news and previews at Yahoo! Games.
From stevemc at real.com  Thu Feb 22 14:29:40 2007
From: stevemc at real.com (Steve McMillen)
Date: Thu Feb 22 15:09:40 2007
Subject: [Helix-producer-dev] Live broadcasting issue
In-Reply-To: <623211.77560.qm@web62106.mail.re1.yahoo.com>
References: <623211.77560.qm@web62106.mail.re1.yahoo.com>
Message-ID: <45DE1954.3080607@real.com>

The Helix Server commercial product is intentionally different from the 
package you can build thru Helix Community.  There are some details on 
the differences here:
https://helix-server.helixcommunity.org/2006/devdocs/helix_server_comparision

There are quite a few more details on the Helix Server community source 
and binary packages in the helix-server project.

The Producer is essentially same as the commercial product.

Steve

On 2/22/2007 1:27 PM, on focus wrote:
> Hi, Steve,
>
> thanks for help. As you mentioned, I am using Helix server and 
> producer, not commercial ones, so using the link you provided, it does 
> work with password only push method. I also tried to use commercial's 
> rmserver.cfg with hlxserver executable, it also works. So here are 
> follow-up questions:
>
> 1. Why there is such difference between these two releases determined 
> by the configuration file?
> 2. In what extent, Helix Server11-1&Producer11 mirrors the 
> functionalities of commercial release of RM server and producer? are 
> there any documents that I can refer to?
>
> 3. If they don't match up with each other, is there anyway we can 
> build a full Helix server and producer from Helix source codes base to 
> match the RM commercial release? or it is simply impossible because RM 
> commercial release is internally difference from the public Helix 
> source release?
>
> thanks a lot,
>
> Frank,
>
> */Steve McMillen /* wrote:
>
>     Since you were trying to do account-based push, I figured you were
>     using the commercial server.  If you are using the helix community
>     server, then you'll need to stick with password-only method. 
>     Following link provides instructions on how:
>     https://producerapps.helixcommunity.org/cmdproducer/docs/howto-broadcast-to-helixserver.html
>
>     If you are using the commercial server, then you may just have
>     your syntax wrong.
>     I have server 11.1 installed on my laptop (windows).  I just fired
>     up producer 11 and started a stream using:
>
>         producer -ac 0 -sp username:password@localhost/live.rm
>
>     I then saw the two streams in the server monitor and was able to
>     connect using rtsp://localhost/broadcast/live.rm.
>
>     I noticed you are not supplying a username (before the colon). 
>     Oddly the producer continues w/o error but never connects to the
>     server.  If you add the username you will find that the producer
>     will connect and you will see the two streams in the server
>     monitor described in the troubleshooting tips.
>
>     Thx, Steve
>
>     On 2/19/2007 11:09 AM, on focus wrote:
>>     Steve, I tried to verify all the steps you have suggested, but
>>     none of them suggests where the problem is. Particularly, I
>>     checked my Helix Server (again 11-1 version) monitor session, it
>>     doesn't show there is connection from producer (Helix producer
>>     11). I am using account based push method without any further old
>>     installation (all brand new machine with first installation of
>>     Helix server and producer). Here is what exactly I did:
>>
>>     1. Install Helix Server 11-1 and create the SecureRBSEncoder
>>     Realm and add a new user and password pair to the new Realm,
>>     test:testnow
>>
>>     2. Fire up the server and then start the Helix Producer 11 with
>>     the following command:
>>
>>     server:~/helixstuff/producer> producer -i testi420l.avi -o
>>     test.rm -sp :testnow@192.168.1.4:1554/live.rm
>>     Helix DNA(TM) Producer 11.0 Build number: 11.0.0.2013
>>     Info: Preparing to encode file "testi420l.avi" to file "test.rm"
>>     Warning: Ignoring enableTwoPass for live encoding
>>     Info: Starting encode
>>     .........
>>     ........ Keep encoding until it finishes with test.rm
>>     (correctly), but there is NO live.rm connection from Helix Server
>>     MOnitoing or by using the realplayer to try to play it
>>
>>     realplay rtsp://192.168.1.4:1554/broadcast/live.rm
>>
>>     with server's log saying: 16-Feb-2007 09:16:22.UNKNOWN
>>     tmplgpln(4607): 52: Error retrieving URL `broadcast/live.rm'
>>     (Invalid path)
>>
>>     I tried on both Windows and Linux platform but none of them
>>     works. And read all the documents or online help I can find.  I
>>     am quite frustrated with what is going on. Questions:
>>
>>     1. Does Real know if Helix Server 11_1 release work with Helix
>>     Producer 11 release in live broadcasting, in either PUSH or PULL
>>     mode?
>>
>>     2. If it works in your internal test, could you give me a
>>     configuration of machine and software setup to precisely make the
>>     simplist and most reliable live broadcasting?
>>
>>     thanks very much,
>>
>>     Frank,
>>
>>     */Steve McMillen /* wrote:
>>
>>         Here are some things to try (from the Producer Release
>>         Notes).  #4 is most relevant I think.
>>
>>            1. If you are unable to establish a player connection to a
>>               live broadcast, and you want to determine whether the
>>               problem is a configuration problem in RealProducer, try
>>               the following:
>>                  1. To confirm that the stream has reached the
>>                     server, check that the stream appears in the
>>                     Server Monitor's connections tab.  You should see
>>                     an entry of Type 'encoder' along with the proper
>>                     filename.
>>                  2. If you are using the Legacy Server broadcast
>>                     method, ensure that you have the correct Server
>>                     mount point ("/encoder/" by default) in your
>>                     player URL.  For example,
>>                     rtsp://yourserver.yourcompany.com:554/encoder/live.rm
>>
>>                  3. If you are using any of the Server 9 Push
>>                     broadcast methods, ensure that you have the
>>                     correct Server mount point ("/broadcast/" by
>>                     default) in your player URL.  For example,
>>                     rtsp://yourserver.yourcompany.com:554/broadcast/live.rm
>>
>>                  4. If you are using the Pull broadcast method,
>>                     ensure that you have the correct Server mount
>>                     point ("/broadcast/pull/" by default) in your
>>                     player URL.  For example,
>>                     rtsp://yourserver.yourcompany.com:554/broadcast/pull/live.rm 
>>
>>            2. You must use a password when using the Pull broadcast
>>               method from the command line application (-si).  If you
>>               wish to broadcast using the Pull broadcast method and
>>               not require a password, use a server file with the
>>               server definition option (-sd).
>>            3. When using the *Account-Based Push* broadcast method,
>>               be sure the username and password are added to the
>>               correct realm on the Helix Server. For the
>>               *Account-based Push* broadcast method, users should be
>>               added to the Helix Server *SecureRBSEncoder* realm.
>>            4. When using the *Account-based Push* broadcast method
>>               with Helix Server 9, you may experience problems making
>>               new Account-based Push connections if the Helix Server
>>               Administrator is used to reconfigure the Helix Server
>>               while existing Account-based Push encodes are running.
>>               To avoid this problem, do not reconfigure the Helix
>>               Server while Account-based Push encodes are active. You
>>               can identify Account-based Push encodes by looking for
>>               pairs of entries as follows in the Helix Server Monitor:
>>               IP ADDRESS 	TYPE 	DURATION 	FILENAME
>>                 	encoder 	00:02:27 	live.rm
>>               172.23.104.111 	player 	00:02:27 	encfs/servvar.set
>>
>>               Each of these entries represent a single Account-based
>>               Push broadcast session.
>>
>>
>>         Note: I can't recall if the Helix Server monitor page
>>         (http://:/monitor.html) is available
>>         thru the hc.org build.  If not, then I'm not sure how to do
>>         the equivalent w/o it.  Could do it via the registry but
>>         that's a little complicated.
>>
>>         Thx, Steve
>>
>>         On 2/16/2007 4:54 PM, on focus wrote:
>>>         Hi, Sujeet,
>>>
>>>         first thanks for the reply. A couple clarification based on your message:
>>>
>>>         1. I suppose your rmserver.cfg, is hlxserver.cfg in the current release.
>>>         2. I didn't find any section in *.cfg file that has
>>>          those definitions in your email.
>>>
>>>         Anyway, I made a little progress by using password only authentication (port number doesn't really matter here, i can specify 8080 which is my Helix http port, or not specify at all),
>>>          producer.exe -i
>>>          c:\test.avi -o test.rm -sp :producerpassword@192.168.1.3/live.rm
>>>
>>>         It seems the authentication error is gone, but when I use a RealPlayer to try to play the live stream, realplayer rtsp://192.168.1.3/broadcast/live.rm,
>>>
>>>         The player says the link doesn't exist. And I checked Helix server logs, both error.log and access.log,
>>>
>>>         error.log:   16-Feb-2007 07:02:46.UNKNOWN tmplgpln(4607): 50: Error retrieving URL `broadcast/live.rm' \(Invalid path)
>>>
>>>         access.log has the error:  "GET broadcast/live.rm RTSPT/1.0" 404 0 [Lin\ux_2.6_10.0.0.0_play32_RN01_EN_586] [512ae9b1-bdc7-11db-f665-4d97144fcbdb]
>>>          [Stat3:187|0|ST\OP|;][Stat4:0 0 0 0|0|0| 0 2] 0 0 0 0 0 12
>>>
>>>         I don't know what is going. I thought the /broadcast in Helix Server 11 is the default mount point which works with with Helix Producer 11's Push broadcasting. BTW, I also set the SecureRBSEncoder Realm and correpsonding user
>>>          name/password.
>>>
>>>         Any suggestion to diagnose the problem will greatly appreciated.
>>>
>>>         Frank
>>>
>>>
>>>         Sujeet Kharkar  wrote: 
>>>         In command line that you are using -sp
>>>         username:password@ipaddress:port/streamname the port specified should be
>>>         HTTP port of the server.
>>>
>>>         Since default installation of server uses 50001-50050 as ports for receivers
>>>         dynamically created by mount point encfs, my assumption is that is not the
>>>         configured HTTP port.
>>>
>>>         Example config entries in rmserver.cfg file specifying concerned ports.
>>>
>>>         You should be able to find more information in help file installed with
>>>         producer (producer -m) in following chapters.
>>>         Chapter 14: Using the Command-Line Application 
>>>         Chapter 11: Running a Broadcast
>>>
>>>         Thanks,
>>>         Sujeet
>>>
>>>         -----Original
>>>          Message-----
>>>         From: helix-producer-dev-bounces@helixcommunity.org [mailto:helix-producer-dev-bounces@helixcommunity.org] On Behalf Of on focus
>>>         Sent: Friday, February 16, 2007 3:29 AM
>>>         To: helix-producer-dev@helixcommunity.org Subject: [Helix-producer-dev] Live broadcasting issue  Hi,     On Windows platform, I am
>>>          using both Producer 11 and Sever 11_1 to do acount-based unicast broadcsting following the documention. After setup, I launched server and then  issue the commend    producer.exe -i c:\test.avi -o test.rm -sp producer:producer@192.168.1.3:50001/live.rm    But the producer  immediately outputs the error message:    BroadcastDist: Unrecognized option config. BroadcastDistribution.Destinations.19216813.Authentication.StatsInterval  Error: Failed to establish a TCP connection with server 192.168.1.3 for authentication.    Both my producer and server are on the same machine 192.168.1.3 and I turned off the firewall compeletely. I also tried this with server sitting on different machine, but it is same result. I don't know what is going on. And didn't find any documents that describe the problem either.     thanks for any suggestions.    Frank  
>>>          --------------------------------- Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev       --------------------------------- Looking for earth-friendly autos?   Browse Top Cars by "Green Rating" at Yahoo! Autos' Green Center.     --------------------------------- It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. _______________________________________________ Helix-producer-dev mailing list Helix-producer-dev@helixcommunity.org http://lists.helixcommunity.org/mailman/listinfo/helix-producer-dev    
>>
> 
 

Site Map   |   Terms of Use   |   Privacy Policy   |   Contact Us

Copyright © 1995-2007 RealNetworks, Inc. All rights reserved. RealNetworks and Helix are trademarks of RealNetworks.
All other trademarks or registered trademarks are the property of their respective holders.