at 3 PM I start FFMPEQ and have it use UDP to stream mpegTS to wowza 4.0.3 and the transcoder . It streams and records to D:\Recordings\CouncilMeetings.stream_source.mp4 and a few other streams.
Most days at 12:30 AM ffmpeg stops and wowza closes the file. I rename these files at 1:05 AM to store them as daily archives.
Some days (about 50% of the time) wowza creates a new recording at 12:32. It creates a new file CouncilMeetings.stream_source.mp4 and so renames my original file to CouncilMeetings.stream_source_0.mp4.
These new files are very small. In the last week they have been 4K , 8k, and 33k.
When they are opened in VLC they have 1 second or less of audio. It might be audio coming from my capture card but it's to short for me to tell.
When I compare the files CouncilMeetings.stream_160p.mp4 CouncilMeetings.stream_486p.mp4 and alll the other stream files they are binary identical. This is likely because there is no video and only audio.
Any thoughts on what might cause wowza to think a stream is incoming and create these files?
My event logs for 12:32:
The WinHTTP Web Proxy Auto-Discovery Service service entered the running state.
Sorry I guess I wasn't clear. I have video and audio in my normal files. The files that are created later on are audio only. It seems to be pulling the audio from some buffer after the video stream has been stopped in ffmpeg.