Well AAC support is shiny new for us. It’s only available since the version released yesterday so hmm, yes it’s possible that there are still a few limitations.
By the video The video studders back and forth can you please describe this or share a sample ?
I have noticed some similar effects by trying to use high resolution h264/aac videos during my tests and the reason that some of those videos do does not have the frames in a consecutive order: as example 1,2,7,8,9,3,4,7,5,6,8, … due to different references frames.
Our filter / rtsp decoder will actually not reorder the frames and display them in the decoded order (actually I’ve tried but it uses considerably more memory), since I have never met a camera that actually uses more than 1 reference frame and saw this only on movies / local files, I had the feeling that It wasn’t required to implement a re-ordering at this stage however it’s maybe the problem you are facing.
Actually I’m also not familiar to Wowza, are your streams coming from Wowza? We would need more information to try reproducing your scenarios in order to support you properly.
Regarding Baseline support, we limit the Baseline (to 2.0) for our output streams / recording. This is in order to be natively supported even old Android devices but for incoming streams we rely on pretty standard and recent version of FFMPEG so it should support more or less anything…