Let’s use case this out. Putting aside implementation, is this what you mean?
A: Publish client
B: Wowza
C: Playback client
-
Publish client publishes a live stream to Wowza
-
Playback client subscribes to the live stream
-
Publish client inserts an image by some user action/command
-
Playback client displays that image
Images are stored in Wowza?
What is the publisher client?
What is the playback client?
If the playback client is Flash RTMP only, you can use cuepoints (time text) on the NetStream. You can develop Flash app that streams and reads your cue-points (which can be named whatever you want) and do some overlay client-side. You would probably store images on a web server to do this. It’s not that complicated but would take some work.
If the playback client might be a HTTP client, e.g. iOS device, or if it is a RTSP client, then you will have to take another approach, which might be easier than the above. You could convert the static images to .mp4 files and use the Stream class streams, for example what is used in the scheduler and the LoopUntilLive example, which might be the best starting place.
In any case, it will take some work. If you need help with it you can post a job description in the Find a Consultant forum, or write to support@wowza.com and ask for the list of independent consultants.
Richard