Can't use Media Encoder SDK,How else stream my ASF to Media Servic
- From: Colin MacKenzie <Colin MacKenzie@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 20 Apr 2009 20:26:01 -0700
I have a C# application that will be recording audio from conferences to disk
and also a server if an Internet or LAN connection is present (for remote
conference monitoring). An operator will also "Monitor" the channels locally
so low latency monitoring is important or the Operators complain of
"feedback" (tho it is technically Latency), inability to annotate and general
dizziness! Thus I am using ASIO api to generate buffers with (I would guess)
about a 1ms to 5ms of latency...real nice!
I have looked into Media Encoder but it seems too simplistic. I cannot
manipulate the audio buffers, or source from memory streams so it can't
accept my ASIO buffers. The stream path is just too closed. Also, if I set it
to archive locally and push to a server, what if the server connectivity goes
down? What will happen to the stream? Will it try to reconnect later?
I plan on using Windows Media Format SDK to create the ASF container and
probably for Codec too, otherwise probably Winacm maybe.
But, how can I then send my ASF stream to Windows Media Services? I see in
the WMS SDK I can create a publishing point. From the client I must have to
create some sort of config profile and send it, then I assume I send RTP
packets. I probably use RTSP to config the profile and control the encoder? I
found the RTP and RTSP API in the Conferencing API and that doesnt look
difficult. Just not sure how to glue it all together.
I can't find any docs on how Windows Media Encoder push/pull technology
works to implement yourself.
Thanks,
Colin
.
- Prev by Date: Re: Remote admin of w2003 WMS from xp machine
- Next by Date: Re: Remote admin of w2003 WMS from xp machine
- Previous by thread: Remote admin of w2003 WMS from xp machine
- Next by thread: Multicast not working after switch
- Index(es):
Relevant Pages
|
