Playback does not work

[dennisjac]

I'm trying to get a basic setup working and so far it seems the publishing side is ok. I can stream to the server and I see the publishing stream in the stats. When I try to connect with players though I just get error after a timeout.
ffplay says this:

ffplay -i "rtmp://192.168.2.25/live/myStream live=1"

RTMP_ReadPacket, failed to read RTMP packet header
rtmp://192.168.2.25/live/myStream live=1: Invalid data found when processing input

The config is fairly straightforward:

rtmp {
    server {
        listen 1935;
        chunk_size 4000;

        application live {
            live on;
            allow publish all;
            allow play all;
        }
    }
}

[arut]

please configure with --with-debug and show error log

[dennisjac]

In this log I started nginx and then tried to play a stream using ffplay:
https://gist.github.com/2764363

Notice that I didn't publish a stream this time but the same problem still occurs. That should keep things simple (publishing a stream floods the debug log with data). Notice the 30 second gap after 22:09:33. That's where the timeout occurs and the error mentioned above is displayed.

[arut]

Your log has absolutely no problems . Moreover the client closes playback with deleteStream call after the error. The error does not mean there was a protocol problem. ffmpeg outputs this error on read timeout (when nothing comes in within certain period of time - 30sec for this case) I should see the full log (with publisher) to see if anything is actually being published and sent to playback client.

[dennisjac]

I've setup a completely seperate vm and used the config from the test directory and now it works. I still have trouble playing streams from xsplit but that is probably a problem with the stream itself (audio works but video doesn't unless you restart the stream when the player is already listening). Closing this issue.

[dodolzg]

same problem, it works well when I set "worker_processes 1"

[gregorykau]

same problem, it works well when I set "worker_processes 1"

I also experienced the same problem on Ubuntu 22.10 Desktop, this change also resolved it for me... Bizarre.