On Sat, Feb 6, 2010 at 11:34 AM, Tom Pepper wrote:
> Jeremy:
>
> Thanks for the quick response. I've had difficulty locating a good source
of information on what the parameter sets should look like, so that's
probably the issue.
>
> MainConcept provides them via h264OutVideoGetParSets(). Here's
Jeremy:
Thanks for the quick response. I've had difficulty locating a good source of
information on what the parameter sets should look like, so that's probably the
issue.
MainConcept provides them via h264OutVideoGetParSets(). Here's the code I use
to retrieve them and parse:
On Sat, Feb 6, 2010 at 10:39 AM, Tom Pepper wrote:
> The parameter set as I encode and report it:
>
> a=fmtp:96
> packetization-mode=1;profile-level-id=41;sprop-parameter-sets=AWdNQCmWUgCgFz5cBUIAAAfSAAHUwTtCxbLAAWjrc1I=
>
>
Something about your sprop-parameter-sets looks wrong--there sho
Duh. Thanks, Ross - after moving from Windows to Ubuntu for development I
stupidly assumed they'd enable multicast in Ubuntu by default.
If anyone else should encounter this problem, the solution that worked for me
was the following:
1) modify /etc/sysctl.d/10-network-security.conf, change the
I'm attempting to feed an H.264 stream from a live capture and
encoder application we've written into Wowza 2 via live. I've
managed to create a custom H264VideoStreamFramer
(STH264VideoStreamFramer ) and DeviceSource (STMCVSource) that
successfully forwards frames from our encoder (MainConcep
I'm attempting to feed an H.264 stream from a live capture and
encoder application we've written into Wowza 2 via live. I've
managed to create a custom H264VideoStreamFramer
(STH264VideoStreamFramer ) and DeviceSource (STMCVSource) that
successfully forwards frames from our encoder (MainConcep
