Hello, here is not the router problems. Because i checked and the outgoing stream (the stream that is getting out after wowza transcoding), and at this moment start the problem of the packet lost.
You have the first transcoder block set to false which means it wont be active and the second block “_360p” is set to transcode the stream to 850(kbps), I’d say this is quite high but that would depend on the bitrate of the source.
Can you post what it says in the Wowza logs when you’re transcoding?
Take a look in the logs again and see if you get some kind of SKIPPED message where a frame was missed. It should look similar to “Video behind filter state change. New state: ALLFRAMESOFF”.
I assume you have taken some of the transcoding off in order to get this far?
This is probably the reason for white noise and possibly a keyframe was being skipped as well.
It’s not because its a trial license this only makes the overly compulsory.
So as you can see you have had a big improvement when lowering the number of transcodes, as this is only a single quad-core CPU and you are still experiencing problems (possibly skipping frames), I would lower the transcodes further to test whether lowering the number of transcodes resolves this issue.
Did you see anything else in the Access logs about skipping frames?
You originally had a problem with “program1.stream” and “program3.stream” but I can’t see anything to do with program1/3.stream in the access log which we were tracking yesterday. Lets fix one problem before moving on to any others, Is the transcoded stream still giving a intermittent pixel problem?
If it is you can add some debug to the access log by following this tutorial,
In my opinion the best thing to do from here is change the encoder to stop running on all channels except one as you currently have it running mulitcast to multiple channels.
Test on the one channel you are now sending the stream to and see if you have any issues, the debug hasn’t displayed anything and may have been added incorrectly.