IIS 7 and Above
Running SSFBasicMuxer sample and getting 0x80040265 (VFW_E_UNSUPPORTE...
Last post May 04, 2012 09:55 AM by seba588587
Apr 24, 2012 08:00 PM|tarjr67|LINK
Apr 25, 2012 07:13 PM|thalesc|LINK
The muxer sample app uses DShow as the input pipeline. Windows doesn't come with a H.264 demuxer for DShow out-of-the-box, the one it comes with is for Media Foundation only (which is what Windows 7 uses by default when you play a .mp4 file containing H.264
video). Therefore, to use the app with H.264 you'll need a 3rd party demuxer. The one we've tested the app with is the Haali Media Splitter (http://haali.su/mkv/).
Apr 26, 2012 01:47 AM|tarjr67|LINK
Apr 30, 2012 09:22 AM|Mamba Dai - MSFT|LINK
, I need to Push the output from a Directshow Capture Device (which is a camera that has encoded h.264 raw video output from it's pin) to Live Smooth Streaming on IIS server. Is this possible?
Yes. Since I have no experience on SSFBasicMuxer, I have no good comments for your quesiton. However, if you use the Microsft Expression Encoder directly to encode your video file comig from camera, you surely can do what you want to implement. Please check
this paragraph "Pushing a Stream to the Live Smooth Streaming Publishing Point" within this artitcle:
Apr 30, 2012 04:40 PM|tarjr67|LINK
May 02, 2012 03:49 AM|Mamba Dai - MSFT|LINK
Well, currently I only consider the EE4. You said "the hard work is done in hardward", if possible please try using EE4 directly to encode your video file.
May 03, 2012 04:58 AM|thalesc|LINK
EE might be an easy solution but it's not necessarily a simple solution from the point of view of application design. From what I know EE will transcode rather than transmux the video in this case. Basically that means it'll decompress and recompress the
video, and although it does that efficiently using the GPU, that's unnecessary processing given the camera already outputs a compressed H.264 stream. The real benefit of the GPU is in the encoding, but this video stream is already encoded. In that sense going
with EE is a little bit of overkill. The SDK is likely to result in a simpler solution (i.e., fewer 'moving parts') that'll be less resource-intensive. Of course the trade-off is it requires writting and testing a lot of code. Moreover EE is a finished product
while the SDK is still in Beta 2 :(
May 04, 2012 09:55 AM|seba588587|LINK
are there any plans to release SDK in near (or far) future (with more samples)?